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

I think I got it: <condition property="mvn.cmd" value="mvn.bat" else="mvn"> <os family="windows"/> </condition> <exec executable="${mvn.cmd}" dir="../thirdparty"> <arg line="package"/> </exec> Dimitris Andreadis wrote: > 'mvn' or 'mvn.bat' need to be executed conditionally. > I've added this, but it seems a later version of ant is required: > <target name="createthirdparty" unless="inhibit.downloads" > depends="check.inhibit.downloads, set.proxy"> > - <exec executable="mvn" dir="../thirdparty"> > + <exec executable="mvn" os="unix" dir="../thirdparty"> > <arg line="package"/> > </exec> > + <exec executable="mvn.bat" os="windows" dir="../thirdparty"> > + <arg line="package"/> > + </exec> > </target> > 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