]
Nick Boldt commented on JBDS-2345:
----------------------------------
Could this not be achieved more easily by parameterizing the value of the
<target><classifier>jbds-unified</classifier></target> and passing
that in via -D flag to the JBT parent pom? What's unique here that can't just be a
-D override to the stuff in JBT?
Also, you have the same multiple.target profile in there twice.
Maybe we should look at adding more stuff (if needed) to
Create a JBDS parent pom
------------------------
Key: JBDS-2345
URL:
https://issues.jboss.org/browse/JBDS-2345
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Build
Reporter: Mickael Istria
Assignee: Nick Boldt
Labels: ece2012
Fix For: 6.0.0.CR1
Attachments: jbds-parent-pom.xml
Having a JBDS parent pom would be very comfortable. It would inherit from JBT parent pom,
but would override some properties (such as local.site) and target-platform definitions.
This is currently done in configuration in Jenkins, so it requires lots of parameters to
build. Having a parent pom would allow to build JBDS with the same required parameters as
JBT.
It would also help to make the JBT parent pom cleaner: a lot of complexity in JBT parent
pom comes from the fact that we want to be able to override everything since we use it for
multiple purposes (JBT & JBDS).
A parent pom would move this complexity to another file (JBDS parent), and won't
pollute JBT.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: