[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] XJC Plugin Problems
|
Just fyi, Run-As->Maven-Build just forks Maven in external JVM. It does
not use m2e internal logging configuration but it is possible to
specify standard Maven logging configuration parameters (-X, -e) in the
launch configuration dialog.
Another useful trick, if you install Maven Development Tools [1], you
will be able to debug Run-As->Maven-Build pretty much as a plain java
application.
[1] https://github.com/ifedorenko/com.ifedorenko.m2e.mavendev
--
Regards,
Igor
On 2/17/2014, 16:57, Keith Barlow wrote:
Something in my workspace must be off... I just compiled the same code
in a clean workspace and it works fine.
Thanks for your help.
Keith
On Mon, Feb 17, 2014 at 4:47 PM, Keith Barlow <kbarlow@xxxxxxxxx
<mailto:kbarlow@xxxxxxxxx>> wrote:
Igor,
Thank you. Yes, this is when using Run-As->Maven-Build. I can see
the debug messages in the 0.log file in the
.metadata/.plugins/org.__eclipse.m2e.logback.__configuration. There
was nothing of interest in the debuging information but I can see
that m2e is simply invoking the external maven command:
2014-02-17 16:36:53,855 [main] INFO
o.e.m2e.actions.ExecutePomAction - Using existing launch configuration
2014-02-17 16:36:54,099 [Worker-51] INFO
o.e.m.i.launch.MavenLaunchDelegate -
/home/kbarlow/workspace/connector-database-4.4.30
2014-02-17 16:36:54,099 [Worker-51] INFO
o.e.m.i.launch.MavenLaunchDelegate - mvn -B -s
/home/kbarlow/.m2/settings.xml clean install
I was able to run that command successfully outside of eclipse. I
am wondering if something just got bjorked in my workspace.
I might try a clean workspace and, if that fails, I'll see if the
generic XJC plugin does it so I can provide a sample.
Thanks again.
Keith
On Mon, Feb 17, 2014 at 3:24 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx
<mailto:igor@xxxxxxxxxxxxxx>> wrote:
See inline
On 2/17/2014, 14:11, Keith Barlow 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?
You should see debug messages in m2e log file in
.metadata/.plugins/org.__eclipse.m2e.logback.__configuration
Also, my output shows the following warnings, I am not sure
if they may
be relevant:
[INFO]
------------------------------__------------------------------__------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------__------------------------------__------------
[INFO] Compilation failure
I am confused now. Does the problem happen during Eclipse
workspace build or when you do Run-As->Maven-Build?
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?
I am not sure at this point. Please provide small standalone example
project and exact steps to reproduce the problem and I will have
a look.
--
Regards,
Igor
Thanks.
Keith
On Mon, Feb 17, 2014 at 1:25 PM, Igor Fedorenko
<igor@xxxxxxxxxxxxxx <mailto:igor@xxxxxxxxxxxxxx>
<mailto:igor@xxxxxxxxxxxxxx <mailto:igor@xxxxxxxxxxxxxx>>>
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
m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
<mailto:m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>>
https://dev.eclipse.org/____mailman/listinfo/m2e-users
<https://dev.eclipse.org/__mailman/listinfo/m2e-users>
<https://dev.eclipse.org/__mailman/listinfo/m2e-users
<https://dev.eclipse.org/mailman/listinfo/m2e-users>>
___________________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
<mailto:m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>>
https://dev.eclipse.org/____mailman/listinfo/m2e-users
<https://dev.eclipse.org/__mailman/listinfo/m2e-users>
<https://dev.eclipse.org/__mailman/listinfo/m2e-users
<https://dev.eclipse.org/mailman/listinfo/m2e-users>>
--
Keith Barlow
/Software Engineer/
*Dell Boomi*
_________________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
https://dev.eclipse.org/__mailman/listinfo/m2e-users
<https://dev.eclipse.org/mailman/listinfo/m2e-users>
_________________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
https://dev.eclipse.org/__mailman/listinfo/m2e-users
<https://dev.eclipse.org/mailman/listinfo/m2e-users>
--
Keith Barlow
/Software Engineer/
*Dell Boomi*
--
Keith Barlow
/Software Engineer/
*Dell Boomi*
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
