On 3/19/07, Cla Emanuel Monsch <[EMAIL PROTECTED]> wrote:
I'm using 'jdom 1.0'. But I've the problem that this pom which comes from the remote repository contains false dependencies. Therefore I will include the corrected jdom pom.xml into our company wide internal repository. - Does it suffice to insert just the pom (without any artifacts) into the internal repository? Because the artifacts are already available in the remote repository.
Probably not, since you don't have control of what order Maven searches repositories. Are developers able to contact both your internal repo *and* central? If instead you are proxying central, then you have the chance to "correct" problems like this. In general it's not a good idea for there to be different files with the same groupId/artifactId/version number. You might want to deploy it with a different version number, such as 1.0-[mycompany].
- How can I insert a pom.xml into the internal repository?
What are you using to serve your internal repository? mvn deploy:deploy-file should work. I find that using both -Dfile= and -DpomFile is easiest, though it does deploy the file twice. The alternative is specifying -DgroupId, -DartifactId, etc., etc., which is more error prone. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
