Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark Bundle-SymbolicName/artifactId mismatches as errors #22

Open
sewe opened this issue Oct 22, 2014 · 1 comment
Open

Mark Bundle-SymbolicName/artifactId mismatches as errors #22

sewe opened this issue Oct 22, 2014 · 1 comment

Comments

@sewe
Copy link

sewe commented Oct 22, 2014

This is an enhancement request: as Tycho will fail the build if the Bundle-SymbolicName doesn’t match the artifactId, it would be great if the m2e/Tycho integration could mark this as an error in the IDE already. Discovering this kind of trivial problem only after a mvn clean install is just frustrating…

If it is appropriate for a m2e connector to add error markers (not sure) I’d be willing to give this a try and provide a patch (any pointers are still greatly appreciated).

@ifedorenko
Copy link
Contributor

I think this is a reasonable enhancement.

m2e already sends events about pom.xml changes and PDEMavenBundlePluginConfigurator can override #mavenProjectChanged method to react to such events. I don't know if PDE provides similar mechanism for bundle manifest changes. I also expect the patch to come with a test (or tests) that verify error markers are created and cleared in response to pom.xml and manifest.mf changes.

You'll need to sign and email us http://takari.io/support/takaricla.pdf before we can accept contributions from you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants