eclipse-xtext / eclipse-xtext/xtext
Wizard: Experiment with the new Tycho P2 feature that support consuming maven artifacts from target platform
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 831
- Forks
- 330
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 12
Description
Wizard: Experiment with the new Tycho P2 feature that support consuming maven artifacts from target platform
cc @LorenzoBettini
in target
<location missingManifest="generate" type="Maven">
<groupId>org.eclipse.xtext</groupId>
<artifactId>xtext-antlr-generator</artifactId>
<version>2.1.1</version>
<type>jar</type>
</location>
<location missingManifest="generate" type="Maven">
<groupId>org.xtext</groupId>
<artifactId>antlr-generator</artifactId>
<version>3.2.1</version>
<type>jar</type>
</location>
in build.properties from mydsl
wrapped.org.eclipse.xtext.xtext-antlr-generator, \
wrapped.org.xtext.antlr-generator
seems to require org.eclipse.m2e.pde.feature.feature.group to work from eclipse.
the antlr generator then no longer needs to be consumed from exec plugin call in mydsl
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the target configuration and mydsl build.properties entries shown in the issue, then inspect how the Tycho P2 Maven locations and the org.eclipse.m2e.pde.feature.feature.group requirement are handled. Done means the ANTLR generator artifacts are consumed from the target platform and no longer need the exec plugin call in mydsl.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100