[ http://jira.codehaus.org/browse/MEAR-45?page=comments#action_77772 ] Brian Topping commented on MEAR-45: -----------------------------------
If the child POMs were using release versions for parents, Maven could always resolve them against the central repo, regardless of how old they were. When snapshot versions are used, the snapshot repo needs to be configured, which is not obvious to some. Or, as you point out, the sources could be changed, but that feels a bit dirty and creates problems when the snapshot of a plugin is deployed to a corporate repository, since it isn't an accurate snapshot of the SCM source for the plugin when it was built. This seems like it would be easy to update tho, easier than applying patches. Am I missing something? > Building Apache-hosted plugins with empty repo fails > ---------------------------------------------------- > > Key: MEAR-45 > URL: http://jira.codehaus.org/browse/MEAR-45 > Project: Maven 2.x Ear Plugin > Issue Type: Bug > Reporter: Brian Topping > Original Estimate: 20 minutes > Remaining Estimate: 20 minutes > > Many of the Apache-hosted plugins depend on POM versions that don't exist in > HEAD and were never deployed. For instance, maven-ear-plugin depends on > parent POM version 2-SNAPSHOT. It wouldn't be an issue except that deploying > these compiled plugins then requires deploying the parent POM, which doesn't > really exist any more. > Presumably this is happening because developers haven't cleared their repo > and built in a while. :-) -- 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
