Thanks Stephen - had to set MAVEN_OPTS to "-Xms512m -Xmx1024m - XX:PermSize=256m -XX:MaxPermSize=512m" to get it to build without the JVM puking, but I finally have a jenkins.war! :)
On May 18, 4:28 pm, Stephen Connolly <[email protected]> wrote: > Some aspects of the Jenkins build are not the Maven way... > > you will need to invoke the lifecycle to at least the "package" phase > in order to build the whole thing. > > If you only want to build specific modules, one at a time, then you > will have to run up to the "install" phase at least once so that the > artifacts from other modules are available from your local cache... > once in the cache each individual module will be runnable *on its own* > by going only as far as "compile", but for other modules to see change > you've made you will need to "install" that module into your local > cache. > > I would recommend running during development mostly with -DskipTests > until you have established that your changes compile... running the > full test suite can be time consuming... but you will want to run the > test suite before attempting to push your changes upstream > > HTH > > -Stephen > > On 18 May 2012 12:10, Ian Kemp <[email protected]> wrote: > > > > > > > > > When I execute "mvn compile" on the Jenkins repository I receive the > > following error: > > > [ERROR] Failed to execute goal org.apache.maven.plugins:maven- > > dependency-plugin:2.3:copy (resgen) on project jenkins-war: Error > > copying artifact from C:\Users\Ian\Desktop\jenkins\cli\target\classes > > to C:\Users\Ian\Desktop\jenkins\war\target\jenkins\WEB-INF\jenkins- > > cli.jar: C:\Users\Ian\Desktop\jenkins\cli\target\classes (Access is > > denied) > > > Looking in C:\Users\Ian.KRSLAN\Desktop\jenkins\ik-jenkins\cli\target > > \classes I find a "hudson\cli" directory containing some class files, > > and a "jenkins\cli" directory containing only a "jenkins-cli- > > version.properties" file. > > > I have very limited experience with Maven, so please advise if I'm > > doing something wrong...
