You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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.
This is an enhancement request: as Tycho will fail the build if the
Bundle-SymbolicName
doesn’t match theartifactId
, 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 amvn 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).
The text was updated successfully, but these errors were encountered: