Well, it's not that difficult. And for those of us using it it's a key
thing IMO.
I think there is something strange in v2.0 that's causing it to not work. I
didn't have time to investigate as I wrote earlier, but possibly it could
be due to the classpath fiddling.
/Anders
On Wed, Apr 22, 2015 a
Nopes. I don't use eclipse so can't really validate this.
2015-04-22 21:20 GMT+02:00 Anders Hammar :
> Have you also looked into the m2e compatibility issue?
>
> /Anders (mobile)
> Den 22 apr 2015 20:34 skrev "Lennart Jörelid" :
>
>> Hello folks,
>>
>> Well, I have done some further fixing in the
Have you also looked into the m2e compatibility issue?
/Anders (mobile)
Den 22 apr 2015 20:34 skrev "Lennart Jörelid" :
> Hello folks,
>
> Well, I have done some further fixing in the plugin.
> Currently a single problem remains regarding the classpath manipulation
> required to get XJC and Schem
Hello folks,
Well, I have done some further fixing in the plugin.
Currently a single problem remains regarding the classpath manipulation
required to get XJC and SchemaGen to pick up classes in submodules.
I'll try to fix it and release this week.
2015-04-22 19:43 GMT+02:00 Mirko Friedenhagen :
Hello everyone,
so what's the state right now. We have one -1 by Anders and obviously
one +1 by Lennart. I do not know about the Eclipse problem but could
imagine to resolve the logging issues in a later release. Having
support for JDK8 is IMO more valuable then good logging or Eclipse
integration
Lennart,
Just want to let you know that I looked into this and can't see why it
doesn't work. There are some changes though in the code.
I'm swamped with other things right know so I will not be able to look more
into this currently. It should be easy to test though by just downloading
an Eclipse
@Lennart: is it a coincidence that your email signature follows the same
format pattern? ;)
Anyway, I agree with Anders: instead of dumping a huge multi line message into
the log, can you please split it into one log statement per line?
The advantages are:
1) you don't need to take care of emit
Sure, I see your point. However, there is nothing that forces you to have
everything logged in one line but you can always separate it on multiple
rows. But then with the standard format with log level info in the
beginning (of every row). For example, this is what is done in the
maven-compiler-plu
The difference is one of accessibility and usability.
Terse logs which contain statements on the form seen below are rather
difficult to browse, if you want to find some kind of grouped information.
I would stretch as far as to say they are rather unreadable; the last
statement, for example, stretc
I'll have a look.
Also, I'm confused by the new type of debug logging. Many of the debug
logging output chunks are formatted totally different from any Maven plugin
I've seen. Any reason for this? What's wrong with the existing style?
With different I mean that there are many separating lines (i.e
Ah.
Since I don't use Eclipse, I am unsure about how to test or validate this.
There is no change in the file
(src/main/resources/META-INF/m2e/lifecycle-mapping-metadata.xml) or goals
that it uses, so I suspect something else is afoot.
Could I get some assistance from someone who uses eclipse so
-1
The m2e integration doesn't work. I've only tested the xjc mojo so far
though. The problem can be seen by importing IT 'xjc-main' for example.
/Anders
On Mon, Feb 9, 2015 at 7:35 AM, Lennart Jörelid
wrote:
> Hi all,
>
> I'd like to release version 2.0 of the JAXB2 Maven Plugin, which is a
>
Hi all,
I'd like to release version 2.0 of the JAXB2 Maven Plugin, which is a major
plugin
upgrade that contains rewritten plugin mechanics, updates to the JAXB2
toolset
and several bug fixes.
The JAXB2-Maven-Plugin uses the Java API for XML Binding (JAXB), version
2+, to
generate Java classes fr
13 matches
Mail list logo
