[ http://jira.codehaus.org/browse/MPREPO-12?page=comments#action_54286 ]
Brian Fox commented on MPREPO-12: --------------------------------- I disagree with this. If you have a project foo that depends on 10 things in ibiblio, but 1 that isn't , it shouldn't be able to be deployed? So in that case if someone wants to use foo, they not only have to figure out the dependencies themselves, they now have to install foo AND go install the 1 missing dependency. The way it is now, they just have to install the 1 missing dependency. I don't see how this change would actually make things better, it would make it harder. > Repository plugin should not publish and upload unless all dependencies exist > in repository > ------------------------------------------------------------------------------------------- > > Key: MPREPO-12 > URL: http://jira.codehaus.org/browse/MPREPO-12 > Project: maven-repository-plugin > Type: Improvement > Environment: Windows XP, Java 1.5 > Reporter: Bengt-Erik Fröberg > > > Today there are a lot of errors and non-available transitive dependencies in > some POMs. This result in failed builds etc from the Maven2 environment, and > makes one of Mavens top features, handling of dependencies, worthless. > repository:bundle-create should check that the dependencies of the project > are valid and exist in repository. > After this validation, the bundle can be created and uploaded. This would > prevent a lot of annoying warnings, not-founds and broken dependencies. > Better the goal is aborted with a message to fix the dependencies of the > bundle you want to publish. -- 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, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
