[
http://jira.codehaus.org/browse/QDOX-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181538#action_181538
]
Benjamin Bentmann commented on QDOX-170:
----------------------------------------
bq. seems like the maven-resources-plugin was the only one without a version.
No, the QDox POM does not specify versions for maven-clean-plugin,
maven-surefire-plugin, maven-install-plugin and maven-deploy-plugin. So, for
Maven 2.0.8-, these plugins get resolved to their latest release, while in
Maven 2.0.9+ you get whatever has been set in the super POM. In both cases,
your build depends on external settings and a different Maven version could
produce different outputs from the same POM. Locking down plugin versions is
not limited to just the plugins explicitly declared in the POM, it should be
done for each plugin your build uses, including the implicitly used plugins for
the default lifecycle bindings.
> Maven prerequisite is required in the build
> -------------------------------------------
>
> Key: QDOX-170
> URL: http://jira.codehaus.org/browse/QDOX-170
> Project: QDox
> Issue Type: Bug
> Affects Versions: 1.10
> Reporter: Vincent Siveton
> Assignee: Robert Scholte
> Fix For: 1.10
>
> Attachments: prerequisite.patch
>
>
> You cant build the project with a Maven version < 2.0.10, easy patch provided.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
