[
http://jira.codehaus.org/browse/MRESOURCES-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128645#action_128645
]
Benjamin Bentmann commented on MRESOURCES-61:
---------------------------------------------
bq. The point of not locking it is that you get updates
If you ever cared about reproducible builds, then I can only emphasize to
follow Oliver's suggestion and lock plugin versions. While auto-update
originally seemed like a convenient feature, it makes your build dependent on
current time and machine/developer. The key point to keep in mind is that a new
plugin version simply might not be backwards compatible, may it for a new bug
or some refactoring to better support new/other use cases.
Last but not least, be warned that Maven 2.0.9 will lock down core plugins in
its super POM, see MNG-3395.
> PluginDescriptor not found
> --------------------------
>
> Key: MRESOURCES-61
> URL: http://jira.codehaus.org/browse/MRESOURCES-61
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Reporter: Brill Pappin
> Attachments: maven-eclipse-integration-plugin.txt
>
>
> The following error, every time I run a build has been ongoing for quite some
> time now.
> 3/21/08 3:34:06 PM EDT: Build error for /aleixo-console/pom.xml;
> java.lang.IllegalStateException: The PluginDescriptor for the plugin
> org.apache.maven.plugins:maven-resources-plugin was not found
> It seems to go away if I run with a -U to update the plugins but comes back
> regularly.
> Can somebody please fix whatever issue is causing this to occur?
--
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
