[jbosstools-issues] [JBoss JIRA] (JBDS-2345) Create a JBDS parent pom

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734401#comment-12734401 ] 

Mickael Istria commented on JBDS-2345:
--------------------------------------

{quote}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?{quote}
I'm not sure about the "more easily". The overriding process we have set up to use JBT parent pom in JBDS (or SOA) adds a lot of non-JBT pollution to parent pom. The goal of having a JBDS parent pom, that would inherit from JBT parent pom, would be to have a better place to host JBDS properties and specific profiles, that may change on a different schedule than JBT.

If there are things we can already move from JBT parent to https://svn.jboss.org/repos/devstudio/trunk/product/pom.xml , we should do it. It could indeed be enough and replace usage of a JBDS parent pom.

The bug could be renamed in "move JBDS stuff out of JBT parent pom", using product/pom.xml may be a valid solution.
                
> 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: Mickael Istria
>              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: http://www.atlassian.com/software/jira