Are you running mvn install:install-file and mvn package in the same machine? mvn install only put artifacts into the local repo and if you are trying to package from another machine (other developer's or CI's machine) then it will not find the artifact there.
1. Check your local repo and see if the artifact was succesfully installed. 2. Run mvn package -X and check if there are valuable information displayed concerning the missing artifact (are you sure the missing artifact is the one you are trying to install? Maybe it´s another artifact). About groupId, personally I use the company domain (if it´s an artifact built to the company) or my personal domain (if it´s an artifact built to personal use). If I am working in a project that delivers multiple artifacts, I include the project name into the groupId. It´s a similar approach to choosing package names. On Fri, May 20, 2011 at 8:49 AM, uday shankar <[email protected]> wrote: > Hi Wendy, > Generally how does one decide the groupid? > Can it be any value? > Here I gave the group id as org.mule.modules > > I just decided on this group Id randomly I just wanted to put the jar in > some folder so I chose this, are there any guidelines which are to be > followed while selecting a groupId > My pom.xml : > <dependency> > <groupId>org.mule.modules</groupId> > <artifactId>Ota_Sonata</artifactId> > <version>1.0</version> > <scope>provided</scope> > </dependency> > Command :mvn install:install-file -Dfile=D:\Ota_Sonata.jar > -DgroupId=org.mule.modules -DartifactId=Ota_Sonata -Dversion=1.0 > -Dpackaging=jar -DgeneratePom=true > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Problem-in-delpoying-an-external-jar-to-the-local-repo-tp4410234p4412377.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] > >
