[
https://issues.jboss.org/browse/JBIDE-8518?page=com.atlassian.jira.plugin...
]
Denis Golovin resolved JBIDE-8518.
----------------------------------
Resolution: Done
building build/parent/pom.xml is no longer required
default scenario to build whole jbosstools repo is:
{noformat}
mkdir jbosstools
cd jbosstools
svn checkout
https://anonsvn.jboss.org/repos/jbosstools/trunk
.
mvn install -Dmaven.test.skip
{noformat}
fix pom.xml files in JBT and JBDS repo such that only component root
poms reference parent pom (all others just look up to .. for parent)
-----------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8518
URL:
https://issues.jboss.org/browse/JBIDE-8518
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Denis Golovin
Fix For: 3.3.0.M2
Attachments: as.patch
Currently, there are many plugin pom.xml files which reference the parent pom directly.
This is bad.
Instead, only ~/trunk/<component>/pom.xml should reference the parent pom, which
can then be pulled from nexus:
Downloading:
http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o...
Downloaded:
http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o...
(383 B at 0.2 KB/sec)
Downloading:
http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o...
Downloaded:
http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o...
(20 KB at 21.5 KB/sec)
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira