Disappearing Maven resources? (beanutils, xalan, rampart)
I'm maintaining a legacy Java project. I setup a Maven pom.xml a while ago, and it used to work, but now, several dependencies that used to automatically download and work perfectly, have just stopped working on the standard Maven servers. The three dependencies are: commons-beanutils:commons-beanutils:jar:1.6.1 xalan:xalan:jar:2.6.0 org.apache.rampart:rampart-core:jar:1.3 (dependency failure on bouncycastle:bcprov-jdk15:jar:132) I get errors like this: [INFO] Unable to find resource 'bouncycastle:bcprov-jdk15:jar:132' in repository central (http://repo1.maven.org/maven2) These are valid dependencies, they show up on mvnrepository.com and seem to be there when web browsing to http://repo1.maven.org/ (like in http://repo1.maven.org/maven2/xalan/xalan/2.6.0/) I've manually setup my copied these dependencies from an old build server into my local repository cache for now, but ideally this server glitch would be resolved, where new systems could automatically download these dependencies like they are supposed to.
Maven 2.2.1 Question
Any idea why I would get these types of warnings and errors with Maven 2.2.1? The POM ... is invalid warnings sound fairly straight forward, but those were just downloaded from the default Maven repo, and this happens on multiple build systems, so I suspect it's a n issue with Maven's servers rather than a corrupted download or file issue. Here are the warnings and errors: [WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] Copying 292 resources [WARNING] POM for 'javax.servlet:servlet-api:pom:2.3:compile' is invalid. Its dependencies (if any) will NOT be available to the current build. [WARNING] POM for 'commons-logging:commons-logging:pom:1.0.4:compile' is invalid. Its dependencies (if any) will NOT be available to the current build. [WARNING] POM for 'commons-codec:commons-codec:pom:1.2:compile' is invalid. Its dependencies (if any) will NOT be available to the current build. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: commons-fileupload:commons-fileupload:jar:1.2 Reason: Cannot find parent: org.apache.commons:commons-parent for project: commons-fileupload:commons-fileupload:jar:1.2 for project commons-fileupload:commons-fileupload:jar:1.2
Re: Newbie Question: Dependencies among Sibling Projects?
Wayne Fay wrote: It seems that I need to install librarya before libraryb will compile. This is correct. Unless you are running mvn compile from the top parent/aggregation pom. I am running mvn compile from the top aggregation pom and I still get the dependency failure. I'm using a super simple dummy project setup to test this... Is this behavior documented anywhere? Wayne Fay wrote: Yes, but make sure you are using x.y.z-SNAPSHOT until you ready to freeze a version number. In the Maven world (and its a good policy in general), there is only ONE true artifact for a given groupId/artifactId/version (GAV) combination. That makes perfect. There should only be one true build of a released version, but development snapshots are moving targets. Is Maven treating the text SNAPSHOT as a special-case in the version string? Is this behavior documented? Thanks so much for the response! -- View this message in context: http://n2.nabble.com/Newbie-Question%3A-Dependencies-among-Sibling-Projects--tp2477109p2484210.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Newbie Question: Dependencies among Sibling Projects?
I have a software project that is roughly organized like this: master (aggregation project) librarya libraryb (depends on librarya) It seems that I need to install librarya before libraryb will compile. Is there any way to define dependencies among sibling projects like this (that are part of the same aggregation group) so that they do not need to be individually installed (preferably not installed at all) and Maven can auto-detect dependencies and properly build/rebuild? Also, during development, I do not update the version tag during every single build/debug cycle. Will Maven properly detect source changes, rebuild necessary libraries, and update the local repository? -- View this message in context: http://n2.nabble.com/Newbie-Question%3A-Dependencies-among-Sibling-Projects--tp2477109p2477109.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
