[jbosstools-issues] [JBoss JIRA] (JBIDE-11157) Explore publishing parent pom to nexus
Mickael Istria (JIRA)
jira-events at lists.jboss.org
Tue Mar 13 06:10:47 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-11157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676332#comment-12676332 ]
Mickael Istria commented on JBIDE-11157:
----------------------------------------
WIP:
See https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.parent/ and https://repository.jboss.org/nexus/index.html#nexus-search;quick~org.jboss.tools.parent.pom
Next steps:
1. rename org.jboss.tools.parent.pom into parent (to conform with Maven conventions)
2. Add nexus Snapshot and release repo to all components (to resolve parent when not available locally)
3. Remove build of parent in jobs.
> 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
More information about the jbosstools-issues
mailing list