Thanks Rémy for helping. The POM present in the repository seems ok :
C:\Documents and Settings\joel.costigliola\.m2\repository\sapiens\SapiensCommonsCore\2.6.0>mvn -f SapiensCommonsCore-2.6.0.pom validate [INFO] Scanning for projects... [INFO] ---------------------------------------------------------------------------- [INFO] Building Sapiens Core [INFO] task-segment: [validate] [INFO] ---------------------------------------------------------------------------- [INFO] No goals needed for project - skipping [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: < 1 second [INFO] Finished at: Wed Jul 18 18:23:59 CEST 2007 [INFO] Final Memory: 2M/4M [INFO] ------------------------------------------------------------------------ I'm using parent/child module pattern for the project BASObjetTrouve which depends SapiensCommonsCore. Could this cause some trouble when validating SapiensCommonsCore ? (which is not in the project BASObjetTrouve but in another project ... ) Any ideas ? -----Message d'origine----- De : Rémy Sanlaville [mailto:[EMAIL PROTECTED] Envoyé : mercredi 18 juillet 2007 14:06 À : Maven Users List Objet : Re: Failed to validate POM warning > > [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] > Isn't it possible to run mvn validate directly on the sapiens:SapiensCommonsCore:pom:2.6.0 ? I never try but you can test. mvn -f -f,--file Force the use of an alternate POM file. Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
