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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-11157:
---------------------------------------------

Please don't use updatesites as TP - it has been proven again and again that we risk those sites to disappear/not be the same - even our own, so we need something versionable that is not changable.

The target platform is *not* something that should be released as part of jboss tools parent - the TP is something that gets released *before* jboss tools parent, since jboss tools parent *uses* the TP.

And there will be multiple TP's in the future, used at the same time so it cannot and should not be linked to lifecycle of the parent IMO.

Publishing of this shouldn't happen from a jenkins job should it ? a bit confused about that ?

>1. rename org.jboss.tools.parent.pom into parent (to conform with Maven conventions)

Not following what this is about ? what does this fix ? change ?

>2. Add nexus Snapshot and release repo to all components (to resolve parent when not available locally)

release what repo to all components ?

We really should not publish anything to nexus release before we have validated this via snapshots and staging sites - we don't want to pollute nexus release with our "experiements".

>3. Remove build of parent in jobs.

+1000


                
> 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