Hi Joël, Have you tried using the -X option to mvn? It might give more details on the problem.
I checked your SapiensCommonsCore POM against maven-4.0.0.xsd, and it appears to be valid, but you don't have a groupId there - are you expecting to inherit it from the parent? It might also be useful to run "mvn help:effective-pom" agianst the SapiensCommonsCore POM, to see if its parent POM is introducing something that's causing a problem. Steve Joel COSTIGLIOLA (Services DPT SYSTEME D INFORMATION METIER) wrote: > Hi, > > One of my project (ObjetTrouveService) depends on another project of mine > (SapiensCommonsCore). > > When building ObjetTrouveService I have a warning telling me that > SapiensCommonsCore pom is not valid. > > Here's the trace : > [...] > [WARNING] POM for 'sapiens:SapiensCommonsCore:pom:2.6.0:compile' is invalid. > It will be ignored for artifact resolution. Reason: Failed to validate POM f > or project sapiens:SapiensCommonsCore at Artifact > [sapiens:SapiensCommonsCore:pom:2.6.0:compile] [...] > And here's SapiensCommonsCore-2.6.0.pom as found in local repository : > > <project> > <parent> > <groupId>sapiens</groupId> > <artifactId>SocleSapiens</artifactId> > <version>2.6.0</version> > </parent> > <modelVersion>4.0.0</modelVersion> > <artifactId>SapiensCommonsCore</artifactId> > <packaging>jar</packaging> > <name>Sapiens Core</name> > <dependencies> > <dependency> > <groupId>commons-net</groupId> > <artifactId>commons-net</artifactId> > </dependency> > </dependencies> > > <build> > <sourceDirectory>src/java</sourceDirectory> > <testSourceDirectory>src/test</testSourceDirectory> > </build> > </project> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
