[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: ---------------------------------------- Basically, a TP is just a difficult to maintain composite update-site. Having the list of sites in a pom.xml and the list of features we want in a site.xml (or category.xml) would provide us the same control as we have for TP, and would be much more Maven-friendly and easy to maintain. About renaming to "parent" that changes nothing except that JBoss Tools now looks more "normal" when trying to find the parent in the M2 repo. IT is now done and nothing has changed except the name. We would not release anything on component, we will add a referece to JBoss Nexus repo in components to ensure they will be able to locate their parent from here. The release of parent or TP or whatever is done on staging repository, and we'll have to go through the process of promoting it to "release" to get components consume releases. I don't think this is an experiment any more ;) -- 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