Targetplatform and running

Open
#3 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
build-system, tooling

Research direction

Start by reviewing the goomph Eclipse plugin and the target platform setup described in trgdef.target and platform/plugins/*.jar. Determine whether prj1 can use the local target files without downloads and whether prj2 can be built and run during the build; done should clearly define the supported behavior for both projects.

Written by the indexing model from the issue text.

Description

In my understand gradle "out-of-the-box" does not support PDE projects. Hence an 'eclipse' gradle project does not know about the target platform.

In my project build, i have several eclipse plugins and a directory with the target platform files.

platform/plugins/*.jar

prj1, has a trgdef.target file, which is an Eclipse target platform definition.
Can i use it to make this targetplatform be a p2 or maven thing? Or can i make the directory directly a p2? No downloads shall take place, only the contained files and the project (like 'prj1' 'prj2' shall exist for the build)

prj2, references prj1 and is a osgi console application.
Can i build it and run it in the build?

Dominant language
Java
Stars
1
Forks
2
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from diffplug/goomph-eclipse-plugin

All issues in diffplug/goomph-eclipse-plugin

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.