Description of problem: When I import the quickstarts to JBDS, it shows the following message: "Plugin execution not covered by lifecycle configuration: org.commonjava.maven.plugins:project-sources-maven-plugin:0.3:archive (execution: project-sources-archive, phase: initialize)" Since there's no m2e connectors for it, It forces me to disable the plugin to have the quickstarts working inside JBDS How reproducible: jboss-brms-bpmsuite-quickstarts quickstarts to JBDS Steps to Reproduce: 1. Inside JBDS, Open brms-helloworld-brms 2. Realize that there's an error on the <parent> (line 21) 3. Place your mouse over to read the error message. Actual results: Error message: Plugin execution not covered by lifecycle configuration: org.commonjava.maven.plugins:project-sources- maven-plugin:0.3:archive (execution: project-sources-archive, phase: initialize) Expected results: No error messages about this plugin. Additional info: To have it build fine, it may also need to enable brms and enable-test profiles clicking on Maven->Select Maven Profiles, but that's somehow expected.
This seems to me likely a bug in JBDS instead of BRMS quickstarts. should the "product" to be Jboss Developer Studio?
I'll send this question to jbossdeveloper list
Just to be clear - did the build really fail ? was it not just marking this plugin as not covered ?
I tried it and it doesn't really fail. I thought it did because of of the import error. I attached the screenshot that shows the test execution complete and the import error marker.
Created attachment 1034791 [details] Plugin execution not covered in JBDS by BRMS Quickstart
okey so to answer what recommendation is then it is (assuming this plugin is actually needed) is to mark in the pom.xml the execution should be ignored if it is not relevant for the general development. But this error does raise to me a few questions: a) why are they using something like version 0.3 for this plugin - that is ancient afaics. b) why is this plugin used in any quickstart ? what is the value of this plugin to quickstart user ? c) looks like it is coming from some overall product parent pom - I thought quickstarts were not supposed to have such parents ?
The reason it was added is that we use it to produce a source package which contains the real product version changes applied by Pom-Manipulator-Ext. It work with PME and has been applied to all project source we shipped to customer. I agree that the plugin is irrelevant to customer usage on quickstarts and we can provide the correct source based on assembly instead of relying on the project-source-plugin. So we decided we can drop it from quickstarts. (In reply to Max Rydahl Andersen from comment #7) > okey so to answer what recommendation is then it is (assuming this plugin is > actually needed) is to mark in the pom.xml the execution should be ignored > if it is not relevant for the general development. > > But this error does raise to me a few questions: > > a) why are they using something like version 0.3 for this plugin - that is > ancient afaics. > > b) why is this plugin used in any quickstart ? what is the value of this > plugin to quickstart user ? > > c) looks like it is coming from some overall product parent pom - I thought > quickstarts were not supposed to have such parents ? There are many properties sharing between quickstarts which is defined in quickstarts-parent. individual quickstarts should be able to build or import as long as it can assess a online or offiline maven repository .
I have modifed our tooling to allow removal of the proejct source plugin in quickstarts.
Verified on BRMS 6.2.0.ER4.