Re: [jboss-dev] Changes to JBoss AS Build

Ok, I can try to set it up so a separate maven installation is not needed. Dimitris Andreadis wrote: > Shouldn't the AS checkout be self-sufficient? I.e. both including it > own version of maven & be configured by default to let you build a > jboss distro with the only requirement of having a JAVA_HOME set? > > Paul Gier wrote: >> The missing artifacts might have to do with adding the jboss >> repositories to your settings.xml file. >> (http://wiki.jboss.org/wiki/Wiki.jsp?page=MavenSettings) >> >> I'll add the repositories to the app server parent pom, so that this >> isn't an issue anymore. >> >> Alexey Loubyansky wrote: >>> It seems to be broken now. >>> >>> build.bat from build failed for me with >>> >>> trunk\build\build.xml:915: Execute failed: java.io.IOException: >>> CreateProcess: mvn package error=2 >>> >>> Launching mvn package from thirdparty directly revealed >>> >>> 66 required artifacts are missing. >>> >>> Dimitris Andreadis wrote: >>>> So how is this supposed to work now; I mean the obvious stuff like >>>> build the as, update dependencies, run the testsuite. >>>> >>>> Is there a wiki to document it? All the hudson runs look very much >>>> screwed up. >>>> >>>> Paul Gier wrote: >>>>> >>>>> Hi Everyone, >>>>> >>>>> As a step in the ongoing effort to mavenize the app server, I am >>>>> replacing the >>>>> build-thirdparty.xml with a maven build. There is a new pom.xml >>>>> in the >>>>> thirdparty directory that will now manage the app server >>>>> dependencies. So >>>>> starting tomorrow, you will need to update the pom in the root >>>>> directory of the >>>>> app server and the pom in the thirdparty directory. >>>>> >>>>> All new dependencies will have to be added to the maven section of >>>>> our >>>>> repository (http://repository.jboss.org/maven2) because this is >>>>> where the new >>>>> thirdparty stuff will be downloaded from. >>>>> >>>>> The pom in the thirdparty directory will be called automatically >>>>> by the main >>>>> build script build/build.xml and you can also call it directly >>>>> using "mvn >>>>> package". The thirdparty maven build then uses a plugin that >>>>> reads the >>>>> dependencies from the pom, and then generates a thirdparty >>>>> dependencies >>>>> directory that matches what was generated by the >>>>> build-thirdparty.xml. I'm also >>>>> working on some documentation for the plugin, and I will post it >>>>> as soon as it >>>>> is somewhat complete. >>>>> >>>>> Please let me know if there are any questions/concerns. >>>>> >>>>> Thanks! >>>>> _______________________________________________ >>>>> jboss-development mailing list >>>>> jboss-development(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jboss-development >>>> _______________________________________________ >>>> jboss-development mailing list >>>> jboss-development(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jboss-development >>> _______________________________________________ >>> jboss-development mailing list >>> jboss-development(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-development >> >> _______________________________________________ >> jboss-development mailing list >> jboss-development(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-development > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development