Hi Lennart,
I believe using String[] instead might do the trick. Or if the problem only
manifests itself under maven2, then it would make more sense to discontinue
support for maven2 instead of wasting resources on legacy platform.
Kind regards,
--
Sergei
>
>Wednesday, 4 February 2015 07:59 +
After a few hiccups, all ITs for Maven3 now execute well on the
jaxb2-maven-plugin.
However, one of the ITs is run by Maven2 on JDK 1.6, and the integration
tests there expose the exception shown in the snippet below.
I would suspect that the error is created by parameters like the two below:
@Pa
