Could this be related to the bootstrap error? I found it in the eclipse log?
!ENTRY org.eclipse.m2e.logback.appender 2 0 2014-02-17 12:56:45.393 !MESSAGE Failure to transfer org.codehaus.mojo:buildnumber-maven-plugin/maven-metadata.xml from http://{localserver}/nexus/content/groups/m1-repos was cached in the local repository, resolution will not be reattempted until the update interval of nexus-m1-repos has elapsed or updates are forced. Original error: Could not transfer metadata org.codehaus.mojo:buildnumber-maven-plugin/maven-metadata.xml from/to nexus-m1-repos (http://{localserver}/nexus/content/groups/m1-repos): No connector available to access repository nexus-m1-repos (http://{localserver}/nexus/content/groups/m1-repos) of type legacy using the available factories AsyncRepositoryConnectorFactory, WagonRepositoryConnectorFactory Thanks again. Keith On Mon, Feb 17, 2014 at 2:11 PM, Keith Barlow <[email protected]> wrote: > Marcel, Java is 1.6.0_45 which I don't believe has changed in a while. > > Igor, > > I have tried 3.1.1 on the command line but that appears to build > correctly. I have also tried enabling the debug logs but I am not sure I > am doing it correctly. To do so, should I only have to update the level to > DEBUG in the <root level="INFO"> declaration: > > <root level="DEBUG"> > 34 <appender-ref ref="FILE" /> > 35 <appender-ref ref="STDOUT" /> > 36 <appender-ref ref="EclipseLog" /> > 37 <appender-ref ref="MavenConsoleLog" /> > 38 </root> > > I don't see debuging statements in either the maven console or the eclipse > log? > > Also, my output shows the following warnings, I am not sure if they may be > relevant: > > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Compilation failure > > could not parse error message: warning: [path] bad path element > "/home/kbarlow/.m2/repository/com/sun/xml/bind/jaxb-impl/2.1.12/jaxb-api.jar": > no such file or directory > warning: [path] bad path element > "/home/kbarlow/.m2/repository/com/sun/xml/bind/jaxb-impl/2.1.12/activation.jar": > no such file or directory > warning: [path] bad path element > "/home/kbarlow/.m2/repository/com/sun/xml/bind/jaxb-impl/2.1.12/jsr173_1.0_api.jar": > no such file or directory > warning: [path] bad path element > "/home/kbarlow/.m2/repository/com/sun/xml/bind/jaxb-impl/2.1.12/jaxb1-impl.jar": > no such file or directory > warning: [path] bad path element > "/home/kbarlow/.m2/repository/net/sourceforge/jtds/jtds/1.2/jcifs.jar": no > such file or directory > warning: [options] bootstrap class path not set in conjunction with > -source 1.6 > > The bootstrap warning seems like it might be relevant but I am not sure > what it means... Do you know? > > Thanks. > > Keith > > > > > On Mon, Feb 17, 2014 at 1:25 PM, Igor Fedorenko <[email protected]>wrote: > >> Can you try using maven 3.1.1 on command line? This is the version of >> maven used by m2e during workspace build, so maybe this can explain the >> different output you get. >> >> You can also enable debug log in >> .metadata/.plugins/org.eclipse.m2e.logback.configuration/logback*.xml, >> maybe this will explain the difference. >> >> Beyond that, you will need to debug your XJC plugin running inside m2e >> to see what is going on. >> >> -- >> Regards, >> Igor >> >> >> On 2/17/2014, 13:05, Keith Barlow wrote: >> >>> Hiyas, >>> >>> I started have a problem with my XJC plugin recently... for some reason, >>> when generating Java from XSD, boolean fields are getting generated as >>> getXXX() instead of isXXX(). We do use a customized version of the XJC >>> plugin, however the problem only happens when invoking the plugin >>> through M2E in eclipse. If run mvn on the command line, it generates >>> the isXXX() methods. To compound the enigma, M2E is configured to run >>> the same external instace of maven that I use on the command line. >>> >>> Is there something about the way m2e invokes the external maven instance >>> that could cause this? >>> It's only started happening recently. It used to work fine. >>> >>> Eclipse Version: 4.3.0.M20130911-1000 >>> m2e version: 0.15.0.20120709012 >>> maven version: Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400) >>> >>> Thanks. >>> >>> Keith >>> >>> -- >>> Keith Barlow >>> >>> /Software Engineer/ >>> *Dell Boomi* >>> >>> >>> >>> _______________________________________________ >>> m2e-users mailing list >>> [email protected] >>> https://dev.eclipse.org/mailman/listinfo/m2e-users >>> >>> _______________________________________________ >> m2e-users mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/m2e-users >> > > > > -- > Keith Barlow > > *Software Engineer* > *Dell Boomi* > -- Keith Barlow *Software Engineer* *Dell Boomi*
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
