Hi Aleksei,
On 1/29/07, Aleksei Valikov <valikov_at_gmx.net> wrote:
> Hi.
>
> > Why is this patch necessary? Isn't the built-in <dependencies>
> > elements of the maven-plugin section enough?
> >
> > I'm asking because if there is a need for it, then i should also
> > update the maven-jaxb1-plugin.
>
> Yes it is.
>
> The thing is that Maven has currently got problems with plugin dependencies.
> Once the plugin is instantiated, its dependencies can no longer be updated. That
> is, when you have modules A and B, both using the maven-jaxb2-plugin, then in
> the module B you'll get a maven-jaxb2-plugin with dependencies as defined in
> module A. If you make a whole build where B is after A, the build will fail. If
> you build A and B separately, both build will succeed.
> This is one of the issues from Maven JIRA concerning the described problem:
> http://jira.codehaus.org/browse/MNG-1323
>
>
> The patch introduces an alternative mechanism for providing plugin dependencies
> to JAXB. These dependencies are guaranteed to be resolved each time the plugin
> runs and therefore builds will no longer suffer from the Maven bug I've
> described above.
Thank you for the time you devoted to explain this to me.
Nevertheless, I'm thinking of not embedding that patch to jaxb-1.x-plugin since:
a) nobody has asked for it, so far, and
b) the maven core developer Jason Van Zyl claims that the bug has
been fixed in maven 2.0.6
(look at the bottom of
http://jira.codehaus.org/browse/MNG-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel)
If you disagree though, i will take the time and do it.
Regards,
Kostis