Glad to hear I was of any help! I updated the post with the steps you've done. Hopefully it will help other people too :) Thanks
Cheers Bruno P. Kinoshita http://kinoshita.eti.br http://tupilabs.com >________________________________ > From: Matthieu Vincent <[email protected]> >To: [email protected] >Sent: Tuesday, 10 April 2012 4:20 AM >Subject: Re: [Jenkins] Building on Eclipse Indigo > > >Hello Bruno, > > > this last advice has done the trick, all erros have gone away ! > > >Thanks a lot. > > >Cheers, >Matt > > >Le 6 avril 2012 23:26, Bruno P. Kinoshita <[email protected]> a écrit >: > > >>You're very welcome Matthieu, try the following now: >> >>- Look for src/main/groovy (in core project). >>- Then again, right click on it, Build Path => Use as Source Folder >> >>Your build should be fine now (hopefully heh) :) >> >>Thanks for the comment in the blog by the way, I will update the post once >>you say your environment is working fine. >> >>Cheers, >> >> >>On 04/06/2012 06:22 AM, Matthieu Vincent wrote: >> >>Thanks, i'm getting very close to build ! :) >>> >>>I just got to remaining errors on jenkins-core : >>> >>>* import jenkins.util.ServerTcpPort; --> cannot be resolved >>>* MarkFindingOutputStream --> cannot be resolved >>> >>>Matt >>> >>>Le 6 avril 2012 09:56, Bruno P. Kinoshita <[email protected] >>> <mailto:[email protected]>> a écrit : >>> >>> >>> Hey Matthieu! >>> >>> Try the following: >>> >>> - run mvn generate-sources >>> - this will generate many source files under >>> target/generated-sources subdirectories >>> - now go to each project and look for >>> target/generated-sources/localizer, right click on it and 'Build >>> Path' => 'Use as Source Folder'. >>> - I think the core project generates other files too. Like >>> antlr,taglib-interfaces and other sources. Right click on these >>> folders and use them as source too. >>> - do the usual Project => Clean, Project => Build Project, F5 your >>> projects, and your environment must be fine >>> >>> You may have to execute these steps again. It's troublesome, but for >>> some reason Jenkins generated-sources are not being included by m2e. >>> Probably some m2e connector would do the trick, but I haven't found >>> time to look at this issue yet. Perhaps somebody else has already >>> found a workaround and posted somewhere. I'll take a look on this >>> during this weekend. >>> >>> Hope that helps :-) >>> >>> Cheers, >>> Bruno P. Kinoshita >>> http://kinoshita.eti.br >>> http://tupilabs.com >>> >>> ------------------------------------------------------------------------ >>> *From:* Matthieu Vincent <[email protected] >>> <mailto:[email protected]>> >>> *To:* [email protected] >>> <mailto:[email protected]> >>> *Sent:* Friday, 6 April 2012 4:33 AM >>> >>> *Subject:* Re: [Jenkins] Building on Eclipse Indigo >>> >>> >>> Hi, >>> >>> I'm getting closer. I've followed your instructions, but now >>> i've got some compilation errors about the classes Messages that >>> cannot be found... >>> >>> I'm tried to compile using mvn out of eclipse, and build is >>> successfull but when I refresh my workspace, still got the >>> errors.... >>> >>> Any ideas ? >>> >>> Matt >>> >>> Le 6 avril 2012 07:46, Bruno P. Kinoshita >>> <[email protected] <mailto:[email protected]>> >>> >>> a écrit : >>> >>> I'm using Eclipse Indigo with m2e and building Jenkins (did >>> it yesterday, actually). I simply ignore the messages >>> regarding the missing m2e connectors (though you can fix >>> that [1]). >>> >>> Usually I change the code in Eclipse, but with Jenkins I >>> prefer execute mvn hudson-dev:run from command line. I guess >>> while I'm building Jenkins I almost never invoke maven, I >>> only let m2e download the dependencies for me :) However, >>> I'm able to compile the code, see warnings and errors, as >>> well as debug Jenkins. >>> >>> >>>But when i import the projects on Eclipse after >>> running mvn -DdownloadSources=true eclipse:eclipse, I get >>> plenty of errors about some plugins and their lifecycle. >>> >>> Could you provide the result of mvn -e -X clean >>> eclipse:eclipse -DdownloadSources=true ? If it's too long, >>> you can use pastebin or other site like that too. >>> >>> Hope that helps. >>> >>> [1] >>> >>>http://www.kinoshita.eti.br/2011/09/20/building-jenkins-with-eclipse-and-m2e-plug-in/ >>> >>> Bruno P. Kinoshita >>> http://kinoshita.eti.br >>> http://tupilabs.com >>> >>> >>> >________________________________ >>> > From: Matthieu VINCENT <[email protected] >>> <mailto:[email protected]>> >>> >To: "[email protected] >>> <mailto:[email protected]>" >>> <[email protected] >>> <mailto:[email protected]>> >>> >Cc: "[email protected] >>> <mailto:[email protected]>" >>> <[email protected] >>> <mailto:[email protected]>> >>> >>> >Sent: Friday, 6 April 2012 2:28 AM >>> >Subject: Re: [Jenkins] Building on Eclipse Indigo >>> > >>> > >>> >m2eclipse is bundled in Éclipse distribution since Indigo. >>> The last version is quite stable. >>> > >>> >Is it really necessary to uninstall it to switch to >>> another plugin ? >>> >Mat >>> > >>> >Le 6 avr. 2012 à 00:36, Jeff MAURY >>> <[email protected] <mailto:[email protected]>> a >>> >>> écrit : >>> > >>> > >>> >You should not use m2e but rather the maven eclipse plugin >>> >> >>> >> >>> >>Jeff >>> >> >>> >>Le vendredi 6 avril 2012, Matthieu Vincent a écrit : >>> >> >>> >>Hi, >>> >>> >>> >>> >>> >>> i've tried for 2 days to build Jenkins under Eclipse >>> Indigo with no success. >>> >>> >>> >>> >>> >>>I followed all informations on >>> https://wiki.jenkins-ci.org/display/JENKINS/Building+Jenkins >>> >>>But when i import the projects on Eclipse after >>> running mvn -DdownloadSources=true eclipse:eclipse, I get >>> plenty of errors about some plugins and their lifecycle. >>> >>> >>> >>> >>> >>>I also had a loog to >>> >>>https://wiki.jenkins-ci.org/display/JENKINS/Setting+up+Eclipse+to+build+Jenkins, >>> and everything looks fine on my environment. >>> >>> >>> >>> >>> >>>Problem seems to be that m2eclipse cannot find m2e >>> connectors >>> >>> >>> >>> >>> >>>Does anyone successfully build Jenkins (SNAPSHOT 1.460) >>> on Eclipse Indigo ?? >>> >>> >>> >>> >>> >>>here are some examples : >>> >>> >>> >>> >>> >>>Plugin execution not covered by lifecycle configuration: >>> com.cloudbees:maven-license-plugin:1.3:process (execution: >>> default, phase: compile)pom.xml/jenkins-warline 28Maven >>> Project Build Lifecycle Mapping Problem >>> >>>Plugin execution not covered by lifecycle configuration: >>> com.cloudbees:maven-license-plugin:1.3:process (execution: >>> default, phase: compile)pom.xml/maven-pluginline 29Maven >>> Project Build Lifecycle Mapping Problem >>> >>>Plugin execution not covered by lifecycle configuration: >>> org.apache.maven.plugins:maven-dependency-plugin:2.3:list >>> (execution: list-dependencies, phase: >>> generate-resources)pom.xml/jenkins-warline 180Maven Project >>> Build Lifecycle Mapping Problem >>> >>>Plugin execution not covered by lifecycle configuration: >>> >>>org.apache.maven.plugins:maven-dependency-plugin:2.3:unpack-dependencies >>> (execution: executable-war-header, phase: >>> generate-resources)pom.xml/jenkins-warline 190Maven Project >>> Build Lifecycle Mapping Problem >>> >>>Plugin execution not covered by lifecycle configuration: >>> >>>org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1:display-info >>> (execution: default, phase: >>> validate)pom.xml/notification-pluginline 3Maven Project >>> Build Lifecycle Mapping Problem >>> >>>Plugin execution not covered by lifecycle configuration: >>> org.codehaus.groovy.maven:gmaven-plugin:1.0-rc-5:generateTestStubs >>> (execution: test-in-groovy, phase: >>> generate-test-sources)pom.xml/notification-pluginline 3Maven >>> Project Build Lifecycle Mapping Problem >>> >>>Plugin execution not covered by lifecycle configuration: >>> org.codehaus.groovy.maven:gmaven-plugin:1.0-rc-5:testCompile >>> (execution: test-in-groovy, phase: >>> test-compile)pom.xml/notification-pluginline 3Maven Project >>> Build Lifecycle Mapping Problem >>> >>>Plugin execution not covered by lifecycle configuration: >>> org.jenkins-ci.tools:maven-hpi-plugin:1.78:insert-test >>> (execution: default-insert-test, phase: >>> generate-test-sources)pom.xml/maven-pluginline 398Maven >>> Project Build Lifecycle Mapping Problem >>> >>>>>>Unknownpom.xmlUnknownUnknownorg.eclipse.core.internal.resources.Marker@8ae6fb3 >>> is not of a displayable type >>> >>>Plugin execution not covered by lifecycle configuration: >>> >>>org.jenkins-ci.tools:maven-hpi-plugin:1.78:resolve-test-dependencies >>> (execution: default-resolve-test-dependencies, phase: >>> test-compile)pom.xml/maven-pluginline 398Maven Project Build >>> Lifecycle Mapping Problem >>> >>>>>>Unknownpom.xmlUnknownUnknownorg.eclipse.core.internal.resources.Marker@8ae6fb5 >>> is not of a displayable type >>> >>>Plugin execution not covered by lifecycle configuration: >>> org.jenkins-ci.tools:maven-hpi-plugin:1.78:test-hpl >>> (execution: default-test-hpl, phase: >>> test-compile)pom.xml/maven-pluginline 398Maven Project Build >>> Lifecycle Mapping Problem >>> >>>>>>Unknownpom.xmlUnknownUnknownorg.eclipse.core.internal.resources.Marker@8ae6fb4 >>> is not of a displayable type >>> >>>Plugin execution not covered by lifecycle configuration: >>> org.jenkins-ci.tools:maven-hpi-plugin:1.78:validate >>> (execution: default-validate, phase: >>> validate)pom.xml/maven-pluginline 398Maven Project Build >>> Lifecycle Mapping Problem >>> >>>>>>Unknownpom.xmlUnknownUnknownorg.eclipse.core.internal.resources.Marker@8ae6fb2 >>> is not of a displayable type >>> >>>Plugin execution not covered by lifecycle configuration: >>> org.jvnet.hudson.tools:maven-hpi-plugin:1.57:apt-compile >>> (execution: default-apt-compile, phase: >>> compile)pom.xml/notification-pluginline 3Maven Project Build >>> Lifecycle Mapping Problem >>> >>>Plugin execution not covered by lifecycle configuration: >>> org.jvnet.hudson.tools:maven-hpi-plugin:1.57:insert-test >>> (execution: default-insert-test, phase: >>> generate-test-sources)pom.xml/notification-pluginline 3Maven >>> Project Build Lifecycle Mapping Problem >>> >>>Plugin execution not covered by lifecycle configuration: >>> >>>org.jvnet.hudson.tools:maven-hpi-plugin:1.57:resolve-test-dependencies >>> (execution: default-resolve-test-dependencies, phase: >>> test-compile)pom.xml/notification-pluginline 3Maven Project >>> Build Lifecycle Mapping Problem >>> >>>Plugin execution not covered by lifecycle configuration: >>> org.jvnet.hudson.tools:maven-hpi-plugin:1.57:test-hpl >>> (execution: default-test-hpl, phase: >>> test-compile)pom.xml/notification-pluginline 3Maven Project >>> Build Lifecycle Mapping Problem >>> >>>Plugin execution not covered by lifecycle configuration: >>> org.jvnet.localizer:maven-localizer-plugin:1.8:generate >>> (execution: default, phase: >>> generate-sources)pom.xml/notification-pluginline 3Maven >>> Project Build Lifecycle Mapping Problem >>> >>>Plugin execution not covered by lifecycle configuration: >>> org.kohsuke:access-modifier-checker:1.0:enforce (execution: >>> default-enforce, phase: >>> process-classes)pom.xml/notification-pluginline 12Maven >>> Project Build Lifecycle Mapping Problem >>> >>>Plugin execution not covered by lifecycle configuration: >>> org.kohsuke.gmaven:gmaven-plugin:1.0-rc-5-patch-2:execute >>> (execution: preset-packager, phase: >>> process-resources)pom.xml/jenkins-test-harnessline 184Maven >>> Project Build Lifecycle Mapping Problem >>> >>>Plugin execution not covered by lifecycle configuration: >>> org.kohsuke.gmaven:gmaven-plugin:1.0-rc-5-patch-2:testCompile >>>(execution: >>> test-in-groovy, phase: >>> test-compile)pom.xml/jenkins-test-harnessline 194Maven >>> Project Build Lifecycle Mapping Problem >>> >>> >>> >>> >>> >>> >>> >>> >>> >>>Thanks in advance !! >>> >>>Matt >>> >> >>> >>-- >>> >>Jeff MAURY >>> >> >>> >> >>> >>"Legacy code" often differs from its suggested >>> alternative by actually working and scaling. >>> >> - Bjarne Stroustrup >>> >> >>> >>http://www.jeffmaury.com >>> >>http://riadiscuss.jeffmaury.com >>> >>http://www.twitter.com/jeffmaury >>> >> >>> > >>> > >>> >>> >>> >>> >>> >>> >> >>-- >>Bruno P. Kinoshita >>http://www.kinoshita.eti.br >>http://www.tupilabs.com >> > > >
