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

Max Rydahl Andersen (JIRA) jira-events at lists.jboss.org
Thu Oct 18 02:44:01 EDT 2012


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

Max Rydahl Andersen commented on JBDS-2345:
-------------------------------------------

Not following how this would work ?

A parent pom doesn't get used unless other modules refer to this parent - which modules would refer to this parent ?
                
> 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
>             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


More information about the jbosstools-issues mailing list