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
While implementing de-jcup/eclipse-asciidoctor-editor#371, the reference to eclipse-commons 1.1.1 did end up with a failing Asciidoctor Editor plugin on startup, because the activator from the testcase was not found...
The plugin.xml was inside the deployed version of eclipse-commons on maven central!
Wanted
Other plugins using eclipse-commons from maven central shall work
Solution
Drop plugin.xml before publishing to maven central - tested locally and this solves the problem.
The text was updated successfully, but these errors were encountered:
- plugin.xml is now replaced on build with a replacement_plugin.xml
(which is empty)
- maven github workflow does not also archives artifacts of
target-jar, so libs can be inspected before final release
Situation
While implementing de-jcup/eclipse-asciidoctor-editor#371, the reference to eclipse-commons 1.1.1 did end up with a failing Asciidoctor Editor plugin on startup, because the activator from the testcase was not found...
The
plugin.xml
was inside the deployed version of eclipse-commons on maven central!Wanted
Other plugins using eclipse-commons from maven central shall work
Solution
Drop plugin.xml before publishing to maven central - tested locally and this solves the problem.
The text was updated successfully, but these errors were encountered: