[ http://jira.codehaus.org/browse/MPREPO-12?page=comments#action_54294 ]
Bengt-Erik Fröberg commented on MPREPO-12: ------------------------------------------ Hi! Can you explain "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?" If foo depends on the 10 projects, the 10 projects must be good, and at least exist in repository. What do you mean "1 that isn't?" The way I see it, if 3 of foo's dependencies are broken, and say 2 dependencies of the dependencies are broken, you might as well download all the libraries yourself, Maven2 does no good. If developer Bar wants too deploy foo with the absolute latest whoppety-whippety-version of some dependency that is released in some obscure website, but not in maven repository, then I think he/she should be stopped until this dependency exist in repository. It is very much in his/her interest as well to get the code into immediate production. Why else bother to code anything? It is far from satisfying to work with broken dependencies in POMs, 'WARNING's and 'relocated' all over the place, or even dependencies that exist in som /pub/-directory under ibiblio, but not at the POMed location. Why even bother to put them there when they have got to be manually installed? If the developers deploying to maven repository cannot check theit own goods, well then maven must do it. To take the approach that the users report and patch to JIRA in order to correct things seems like an awkvards solution. Like selling cars and let the drivers walk with the broken clutch or steering-wheel on Route66 and leave them in the nearest car service. Why not try to deliver the car as perfect as possible? As I see it, this is a crucial functionality for Maven2 impact on the developer community beyond the Happy Home Hacker that likes to solve obscure and inexplicable problems for hours on end. For the commercial developer, this is no option, and as I believe Maven2 should and want to be called a professional tool this must be solved. > 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]
