Olà Felipe, I'm just trying to figure out how the groupId could become different from the path since it is Maven itself that generates the path... :O BTW thanks for the notification! Obrigado, até mais, Simo
http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Mar 8, 2011 at 4:06 PM, Filipe Sousa <[email protected]> wrote: > On Tue, Mar 8, 2011 at 11:49 AM, Simone Tripodi > <[email protected]> wrote: >> Olà Felipe, >> looks like the commons-daemon 1.0.3 IS on maven central repo, take a >> look at http://repo1.maven.org/maven2/commons-daemon/commons-daemon/1.0.3/ >> It seems to me that's more ivy-related problem, I'd ask to ivy ML why >> it is not resolved. >> Sorte, até >> Simo > > Hi, > > After having contacted the ivy mailing list, I was told that I'm > getting this this because the POM of commons-daemon is not correct. > It contains the following: > > <groupId>org.apache.commons</groupId> > <artifactId>commons-daemon</artifactId> > > However, according to the URL, it should be: > > <groupId>commons-daemon</groupId> > <artifactId>commons-daemon</artifactId> > > Thanks > -- > Filipe Sousa > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
