This was an accident and not a way to teach you about poms. If you're using at least Maven 2.0.9, this won't affect you as we provide default versions of the lifecycle plugins for you. Otherwise, unfortunately the only way to fix it is to define the versions yourself. The enforcer requirePluginVersions rule will assist you in doing this.
-----Original Message----- From: heapifyman [mailto:[EMAIL PROTECTED] Sent: Friday, October 17, 2008 9:59 AM To: users@maven.apache.org Subject: [MAVEN-CORE-IT-LOG] Hello. Since yesterday several of my maven builds are failing. E.g. the install:install goal fails and doesn't install the built artifact into my local repo but instead just gives log output starting with the subject line and creates some empty txt files. As far as I understand (see: http://www.nabble.com/Unintended-usage-of-core-plugin-stubs-td19633933.html), some genius uploaded to the central repo some stub-xy versions of all maven-xyz-plugins which don't do anything. Now maven loads these plugins because it's taking the latest version for all plugins. The only workaround for this seems to be to add group artifact and version elements for all the plugins used in a normal maven lifecycle to the pom. This is tedious and should not be necessary in my opinion at least not for the "official" maven plugins. Is there another way to get my builds working again? Anyway, even if this is supposed to educate people to write better poms I would appreciate some kind of warning before someone messes around with the official repos in such a way. Thanks in advance.
