[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-6724) Move aggregator pom.xml and parent-pom.xml from root of project to build component

[ https://jira.jboss.org/browse/JBIDE-6724?page=com.atlassian.jira.plugin.s... ] Denis Golovin updated JBIDE-6724: --------------------------------- Description: To let checkout and build separate component(s) aggregator pom.xml and parent-pom.xml should be moved from root of project. So anyone can just checkout only what he needs and build it. in current implementation while there is no public jbosstools repo to build against it should be done through checking out component and its dependencies and build them. For instance to build as several simple steps should be done: 1. ~$mkdir as 2. ~$cd as 3. ~/as$ svn co https://svn.jboss.org/repos/jbosstools/trunk/build 4. ~/as$ svn co https://svn.jboss.org/repos/jbosstools/trunk/tests 5. ~/as$ svn co https://svn.jboss.org/repos/jbosstools/trunk/jmx 6. ~/as$ svn co https://svn.jboss.org/repos/jbosstools/trunk/archives 7. ~/as$ svn co https://svn.jboss.org/repos/jbosstools/trunk/as 8. ~/as$ mvn clean install -f build/parent/pom.xml -Dmaven.repo.local=.repository -Phelios-no-target -Dmaven.test.skip 9. ~/as$ mvn clean install -f build/component/as.xml -Dmaven.repo.local=.repository -Phelios-no-target -Dmaven.test.skip As soon as public release/snapshot repositories are available steps 3-6 and 8 are not needed. After that as can be built like ~/as$ mvn clean install -f as/pom.xml -Dmaven.repo.local=.repository -Phelios-no-target -Dmaven.test.skip if tests should be executed then extra step required ~/as$ svn co https://svn.jboss.org/repos/jbosstools/trunk/requirements and then to run tests remove -Dmaven.test.skip from kommand line and execute ~/as$ mvn clean install -f as/pom.xml -Dmaven.repo.local=.repository -Phelios-no-target was: To let checkout and build separate component(s) aggregator pom.xml and parent-pom.xml should be moved from root of project. So anyone can just checkout only what he needs and build it. in current implementation while there is no public jbosstools repo to build against it should be done through checking out component and its dependencies and build them. For instance to build as several simple steps should be done: 1. ~$mkdir as 2. ~$cd as 3. ~/as$ svn co https://svn.jboss.org/repos/jbosstools/trunk/build 4. ~/as$ svn co https://svn.jboss.org/repos/jbosstools/trunk/tests 5. ~/as$ svn co https://svn.jboss.org/repos/jbosstools/trunk/jmx 6. ~/as$ svn co https://svn.jboss.org/repos/jbosstools/trunk/archives 7. ~/as$ svn co https://svn.jboss.org/repos/jbosstools/trunk/as 8. ~/as$ mvn clean install -f build/parent/pom.xml -Dmaven.repo.local=.repository -Phelios-no-target -Dmaven.test.skip 9. ~/as$ mvn clean install -f build/component/as.xml -Dmaven.repo.local=.repository -Phelios-no-target -Dmaven.test.skip As soon as public release/snapshot repositories are available steps 3-6 and 8 are not needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira