I am in the process of porting a Maven 1.x project over to Maven 2. There are several third party dependencies that are internal to our company. So we have a "regional" repository (speaking Maven-1 lingo here) to house these JARs. I have now created a Maven2-compliant regional repository. I have a couple of questions:
1. The Eclipse plug-in does not seem to recognize an active profile specified in my settings.xml. The implication is that it reports unresolved dependencies; since I have activated my regional repository via a profile. The only way around this that I have found is to specify this additional repository in the pom.xml. This is less than ideal. Do you know a way around this problem? Am I doing something wrong? 2. With the regional repository specified, all the dependencies are now being resolved correctly. However, there are reams of warnings stating dependency's pom could not be retrieved. This is indeed true since most of these JARs are from non-Maven projects and so they don't include a pom. Is there a way to suppress these warnings. I don't want to raise the log level since I do want the usual INFO level messages. Thanks Sri --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
