Mykel Alvis wrote: > I have a profile in settings.xml that defines a remote repo. That profile > is > > <profile> > <id>eclipselink</id> > <activation> > <activeByDefault>false</activeByDefault> > </activation> > <repositories> > <repository> > <id>EclipseLink</id> > <url> > http://www.gtlib.gatech.edu/pub/eclipse/rt/eclipselink/maven.repo/</url> > <releases> > <enabled>true</enabled> > > <checksumPolicy>warn</checksumPolicy> > </releases> > <snapshots> > > <updatePolicy>daily</updatePolicy> > <enabled>true</enabled> > </snapshots> > </repository> > </repositories> > </profile> > > > When I execute > # mvn -P eclipselink compile > [INFO] Scanning for projects... > [WARNING] > Profile with id: 'eclipselink' has not been activated. > > [INFO] > ------------------------------------------------------------------------ > [INFO] Building Product Commmon > [INFO] task-segment: [compile] > [INFO] > ------------------------------------------------------------------------ > > > I was (reasonably) sure that when I specified a profile at the command > line, it SHOULD have been activated. Could someone tell me if I'm doing it > wrong?
Probably a corner case, but normally all profiles activated by default are deactivated if you specify a profile explicitly. Check with mvn help:active-profiles - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
