[jbosstools-issues] [JBoss JIRA] (JBIDE-11157) Explore publishing parent pom to nexus
[
https://issues.jboss.org/browse/JBIDE-11157?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11157:
----------------------------------------
No, snapshots are fine - staging too, its the release repo we should
not pollute.
Ok, fine. There is no plan to move stuff to release at this moment.
how does that change things ?
I allows us to control the set of dependencies we allow for components without using
target files. I think it is easier to maintain a site.xml than a target file. Please keep
in mind that I am just thinking about the Eclipse mirro "dependency" site.
Have we explored the options of tycho supporting multiple target
files allowing us to combine them ?
No, and it sounds more complicated than other alternatives ;)
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