Bug 1227861
| Summary: | Plugin execution not covered in JBDS by BRMS Quickstart | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Rafael Benevides <benevides> | ||||
| Component: | Quickstarts | Assignee: | Ryan Zhang <rzhang> | ||||
| Status: | CLOSED EOL | QA Contact: | Tomas David <tdavid> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.1.0 | CC: | kverlaen, max.andersen | ||||
| Target Milestone: | ER4 | ||||||
| Target Release: | 6.2.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-03-27 19:07:26 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1225698 | ||||||
| Attachments: |
|
||||||
|
Description
Rafael Benevides
2015-06-03 16:28:18 UTC
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. |