[jbosstools-issues] [JBoss JIRA] (JBIDE-11157) Explore publishing parent pom to nexus

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-11157:
------------------------------------

1. Desire to have multiple TPs which are combined: see JBIDE-10915. We can have 1 top-level org.jboss.tools.target-platform.all.feature which includes everything, and child features like org.jboss.tools.target-platform.webtools.feature or org.jboss.tools.target-platform.maven.feature included in that feature.

Then we build a site from that feature, and all its included features/plugins will be on the site. Sorta-kinda-exactly like the existing Target Platform sites we have today, except that instead of being built from .target -> xslt transform w/ ant -> p2.mirror, they're simply built using Tycho, a simple pom.xml, and a simple site.xml. No more XSLT, no more Ant, no more calling Eclipse to run p2.mirror. Way more cross-platform portable, and a smaller .m2 repo footprint.

2. Desire to have contents of TP be locked down to explicit versions: see JBIDE-10915. The org.jboss.tools.target-platform.*.feature will define explicit versions of IUs to be included. Same as the .target files do today, but in a format that's more easily editable / maintainable in Eclipse. AND which allows - should we way - a RANGE of acceptable versions rather than a single version.

3. Desire to have TP offline (eg., as a zip or built locally): since Tycho is more than happy to generate an update site as a zip, this requirement won't change. In fact, it'll be simpler because now I can reuse the same code in ~/trunk/build/aggregate/ to build the site and optionally insert or remove references to other sites (eg., add jboss.org URLs, remove eclipse.org URLs). This also means that the speed boost we get from caching the TP outside Jenkins and using that instead of the copy on download.jb.org ot www.qa will continue.

4. Would the site.xml control the content? NO. The feature.xml(s) would do that. Site.xml will just use 0.0.0 to fetch the versions defined in the features.

5. Does any of this talk about TPs have anything to do w/ putting the parent pom in Nexus? No, not really. Please restrict that conversation to JBIDE-10915.

                
> Explore publishing parent pom to nexus
> --------------------------------------
>
>                 Key: JBIDE-11157
>                 URL: https://issues.jboss.org/browse/JBIDE-11157
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng
>    Affects Versions: 3.3.0.Beta2
>            Reporter: Nick Boldt
>            Assignee: Mickael Istria
>             Fix For: 3.3.0.Beta2
>
>
> We tried this a year ago and it wasn't very successful, but it's worth considering it again.
> We can use `mvn deploy` to push the parent pom (and perhaps the target platform's pom) to nexus for reuse by downstream components.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira