[ http://jira.codehaus.org/browse/MPREPO-12?page=comments#action_54297 ]
Brian Fox commented on MPREPO-12: --------------------------------- First comment on the warnings etc, that is annoying, but there is a fix for 2.0.2 that will ignore warnings in dependencies. Since you don't have control over them, there is no point in telling you about them. On the other issue, I can give you a real example: I run the cewolf project on sourceforge. I took it over when the previous admin disappeared. cewolf is dependent on (among other things) jfreechart. Jfreechart is dependent on gnujaxp. Now I can go and upload cewolf to ibiblio and I go a step further and upload jfreechart to ibiblio also. Besides gnujaxp, all the other dependencies are on ibiblio. Now if someone wants to use cewolf, they list it in their pom, it finds jfc and then eventually fails on gnujaxp. But it TELLS them what version of gnujaxp it wants. They must put this into their repo manually. (i provide scripts to do it for them as part the cewolf source but that's besides the point). What you are saying is that because this one dependency is not in ibiblio, neither cewolf, nor jfc should be allowed on ibiblio. If that were the case, what happens if someone wants to use cewolf anyway? Now they need to find it and install it. Then they need to figure out what dependencies it has (because it's not on ibiblio, it presumably won't have a pom to tell you..just because its on ibiblio doesn't mean it's built with maven, it just means someone took the time to figure it out already and share it). When they figure out jfc, now they need to go install that too (and dependencies, etc). How is that easier than just having to find gnujaxp (especially since it tells you what it needs and what version it is)? This whole thing avoids the fact that many things are dependent on sun jars that can't be on ibiblio. Does that mean none of them can ever be there? It just doesn't seem to help anything. In a perfect world, everyone would use maven and upload their stuff, but that's never going to happen so I would rather find something is 95% in there than 0%. BTW, this jira is under an M1 component, it should be in the 2.x stuff. > 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]
