To take full advantage of maven you are going to want a proxy/repo server for all your maven projects. I use Artifactory but there are a number of them available. With this in place the is a GUI page for dealing with what you are describing, you simply manually deploy these few artifacts in Artifactory and your build doesn't know or care that these were handled as a special case.
-Dave On Mon, Jul 20, 2009 at 8:16 AM, ykyuen <[email protected]> wrote: > > Hi all, > > i am new to maven and i just go thru the examples in the Maven: The > Definitive Guide. > > i am going to migrate a project to maven2. but i find that there are some > jars which are not found in the maven repository > http://repo1.maven.org/maven2/. > > for example. the java project needs activation-1.1.1.jar, > xmlsec-1.4.2.jar... etc. > so i cannot set them as a dependency in the pom.xml > > how can i deal with that? > > Thanks for your help =) > > Regards, > Kit > -- > View this message in context: > http://www.nabble.com/Migrate-existing-java-project-to-maven2-tp24570669p24570669.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
