Eliminate the system scoped dependencies by using mvn
install:install-file or mvn deploy:deploy-file to move those Weblogic
files into the proper Maven repository structure. Then change scope
system to scope compile, provided, runtime, or test as appropriate.
See if that eliminates the annoying log warnings. (You will need to
mvn install the updated parent pom file after changing the scope to
see the effect.)
Wayne
On 8/20/07, Joel COSTIGLIOLA (Services DPT SYSTEME D INFORMATION
METIER) <[EMAIL PROTECTED]> wrote:
>
> No, ${bea.server.home} is defined in the file settings.xml located in my .m2
> directory so it should be available for all my maven project, right?
>
> Anyway, I will make couple tests to remove system scope dependencies to see
> if that was the cause of warnings.
>
> settings.xml contents (without proxy section) :
>
> <settings>
> <proxies>
> <proxy>
> Proxy settings (deleted)
> </proxy>
> </proxies>
> <profiles>
> <profile>
> <id>default</id>
> <activation>
> <activeByDefault/>
> </activation>
> <properties>
> <!-- pour copier les jar clients necessaires au BAV -->
>
> <applicationModele.bav.home>D:/bea_dev/SAPIENS</applicationModele.bav.home>
> <!-- pour redeployer automatiquement le BAS (ear) -->
>
> <sapiens.domain.home>D:/bea_dev/domains/sapiensPortalDomain</sapiens.domain.home>
> <!-- pour recuperer les dependances sur les librairies weblogic -->
> <bea.server.home>D:/bea/weblogic81/server</bea.server.home>
> </properties>
> </profile>
> </profiles>
> <activeProfiles>
> <activeProfile>default</activeProfile>
> </activeProfiles>
> </settings>
>
>
> -----Message d'origine-----
> De : Tim Kettler [mailto:[EMAIL PROTECTED]
> Envoyé : lundi 20 août 2007 12:22
> À : Maven Users List
> Objet : Re: [Maven2] : Failed to validate POM warnings (making a lot of
> really annoying logs !)
>
> I did a qick test using your parent pom and I'm getting the same
> warnings. They go away when I delete the two weblogic system scoped
> dependencies. I don't have this libraries on my system, so that makes sense.
>
> Could it be that ${bea.server.home} is just defined in your sapiens
> multi-build but not in SapiensSpringCommon and so maven just can't find
> the jars?
>
> -Tim
>
> Joel COSTIGLIOLA (Services DPT SYSTEME D INFORMATION METIER) schrieb:
> > Hi Tim - thanks for replying :)
> >
> > I'm using dependencyManagement a lot to avoid duplicating dependency
> information, do you think the presence of SapiensCommonsCore this section
> causes the warning (I haven't got time to test that yet)
> >
> > Here's the parent pom (SocleSapiens) :
> >
> > <project>
> > <modelVersion>4.0.0</modelVersion>
> > <groupId>sapiens</groupId>
> > <artifactId>SocleSapiens</artifactId>
> > <packaging>pom</packaging>
> > <version>2.6.0</version>
> > <name>Socle Technique Sapiens</name>
> > <url>http://asa.anpe.fr/asa/index.php?page=documents#sapiens</url>
> > <description>Socle Technique Sapiens</description>
> > <developers>
> >
> > <developer>
> > <name>Joel Costigliola</name>
> > <id>jojo</id>
> > <email>[EMAIL PROTECTED]</email>
> > <organization>ANPE/ASA</organization>
> > <roles>
> > <role>Developper</role>
> > </roles>
> > </developer>
> >
> > <developer>
> > <name>Yoann Charpiot</name>
> > <id>yoyo</id>
> > <email>[EMAIL PROTECTED]</email>
> > <organization>ANPE/ASA</organization>
> > <roles>
> > <role>Developper</role>
> > </roles>
> > </developer>
> > </developers>
> > <dependencyManagement>
> > <!-- version des librairies preconisees -->
> > <dependencies>
> > <dependency>
> > <groupId>sapiens</groupId>
> > <artifactId>SapiensCommonsCore</artifactId>
> > <version>${project.version}</version>
> > </dependency>
> > <dependency>
> > <groupId>sapiens</groupId>
> > <artifactId>AuthentificationService</artifactId>
> > <version>${project.version}</version>
> > </dependency>
> > <dependency>
> > <groupId>sapiens</groupId>
> > <artifactId>SapiensServices</artifactId>
> > <version>${project.version}</version>
> > </dependency>
> > <dependency>
> > <groupId>sapiens</groupId>
> > <artifactId>SapiensCommonsWeb</artifactId>
> > <version>${project.version}</version>
> > </dependency>
> > <dependency>
> > <groupId>commons-net</groupId>
> > <artifactId>commons-net</artifactId>
> > <version>1.4.0</version>
> > </dependency>
> > <dependency>
> > <groupId>axis</groupId>
> > <artifactId>axis</artifactId>
> > <version>1.1</version>
> > </dependency>
> > <!--
> > le jar jaxrpc n'est pas disponible sur les
> > repository maven internet
> (ou du moins la version existante ne correspond pas a la version que l'on
> doit utiliser)
> > mvn install:install-file
> -Dfile=D:\bea_dev\domains\authentification\lib\jaxrpc-1.1.jar
> -DgroupId=javax.xml -DartifactId=jaxrpc -Dversion=1.1 -Dpackaging=jar
> -DgeneratePom=true
> > -->
> > <dependency>
> > <groupId>javax.xml</groupId>
> > <artifactId>jaxrpc</artifactId>
> > <version>1.1</version>
> > </dependency>
> > <dependency>
> > <groupId>commons-discovery</groupId>
> > <artifactId>commons-discovery</artifactId>
> > <version>0.2</version>
> > </dependency>
> > <dependency>
> > <groupId>commons-logging</groupId>
> > <artifactId>commons-logging</artifactId>
> > <version>1.0.3</version>
> > </dependency>
> > <dependency>
> > <groupId>weblogic</groupId>
> > <artifactId>webserviceclient</artifactId>
> > <version>8.1.5</version>
> > <type>jar</type>
> > <scope>system</scope>
> >
> > <systemPath>${bea.server.home}/lib/webserviceclient.jar</systemPath>
> > </dependency>
> > <dependency>
> > <groupId>weblogic</groupId>
> > <artifactId>weblogic</artifactId>
> > <type>jar</type>
> > <version>8.1.5</version>
> > <scope>system</scope>
> >
> > <systemPath>${bea.server.home}/lib/weblogic.jar</systemPath>
> > </dependency>
> > </dependencies>
> > </dependencyManagement>
> > <dependencies>
> > <dependency>
> > <groupId>junit</groupId>
> > <artifactId>junit</artifactId>
> > <version>3.8.1</version>
> > <scope>test</scope>
> > </dependency>
> > <dependency>
> > <groupId>log4j</groupId>
> > <artifactId>log4j</artifactId>
> > <version>1.2.12</version>
> > </dependency>
> > </dependencies>
> > <modules>
> > <module>SapiensCommonsCore</module>
> > <module>AuthentificationService</module>
> > <module>StructureServices</module>
> > <module>SapiensServices</module>
> > <module>SapiensCommonsWeb</module>
> > <module>SapiensCommonsPortal</module>
> > <module>SapiensAuthenticationProvider</module>
> > </modules>
> > <build>
> >
> > <plugins>
> > <plugin>
> > <groupId>org.apache.maven.plugins</groupId>
> > <artifactId>maven-surefire-plugin</artifactId>
> > <configuration>
> > <skip>true</skip>
> > </configuration>
> > </plugin>
> > <plugin>
> > <groupId>org.apache.maven.plugins</groupId>
> > <artifactId>maven-compiler-plugin</artifactId>
> > <configuration>
> > <source>1.4</source>
> > <target>1.4</target>
> > </configuration>
> > </plugin>
> > <plugin>
> > <groupId>org.apache.maven.plugins</groupId>
> > <artifactId>maven-site-plugin</artifactId>
> > <configuration>
> > <locales>fr</locales>
> > </configuration>
> > </plugin>
> > </plugins>
> > </build>
> >
> > <reporting>
> > <plugins>
> > <plugin>
> > <groupId>org.apache.maven.plugins</groupId>
> > <artifactId>maven-changes-plugin</artifactId>
> > <configuration>
> >
> > <xmlPath>${basedir}/src/site/xdoc/changes.xml</xmlPath>
> > </configuration>
> > <reportSets>
> > <reportSet>
> > <reports>
> >
> > <report>changes-report</report>
> > </reports>
> > </reportSet>
> > </reportSets>
> > </plugin>
> > </plugins>
> > </reporting>
> >
> > <!-- ajouter a la section reporting/plugins pour avoir la javadoc et les
> sources sur le site
> > <plugin>
> > <artifactId>maven-javadoc-plugin</artifactId>
> > </plugin>
> > <plugin>
> > <groupId>org.codehaus.mojo</groupId>
> > <artifactId>jxr-maven-plugin</artifactId>
> > </plugin>
> > -->
> > <distributionManagement>
> > <site>
> > <id>socle.sapiens.site</id>
> > <name>Site Web du Socle Technique Sapiens</name>
> > <url>d:/temp</url>
> > </site>
> > </distributionManagement>
> > </project>
> >
> >
> > -----Message d'origine-----
> > De : Tim Kettler [mailto:[EMAIL PROTECTED]
> > Envoyé : lundi 20 août 2007 10:30
> > À : Maven Users List
> > Objet : Re: [Maven2] : Failed to validate POM warnings (making a lot of
> really annoying logs !)
> >
> > Hi,
> >
> > is the parent pom referenced in the parent section producing the warning
> > available in your local/corporate repository?
> >
> > -Tim
> >
> > Joel COSTIGLIOLA (Services DPT SYSTEME D INFORMATION METIER) schrieb:
> >> Hi there,
> >>
> >>
> >>
> >> I have been reporting few weeks ago some VERY annoying warning like this
> >> one :
> >>
> >> [WARNING] POM for 'sapiens:SapiensCommonsCore:pom:2.6.0:test' is
> >> invalid. It will be ignored for artifact resolution. Reason: Failed to
> >> validate POM for project sapiens:SapiensCommonsCore at Artifact
> >> [sapiens:SapiensCommonsCore:pom:2.6.0:test]
> >>
> >>
> >>
> >> I haven't found any satisfactory explanation in mailing list archive but
> >> I think I may have the reason of such annoying warnings.
> >>
> >> To explain it I must give the overall context.
> >>
> >>
> >>
> >> I have a maven2 project called SapiensSpringCommon depending on
> >> sapiens:SapiensCommonsCore test jar.
> >>
> >> SapiensCommonsCore is a module of sapiens a maven2 multi-module project
> >> of mine.
> >>
> >>
> >>
> >> When I install sapiens modules in my local repository everything runs
> >> fine (no error, no warning).
> >>
> >>
> >>
> >> Warnings arise when I compile SapiensSpringCommon which depends on a
> >> child module of sapiens project (that is SapiensCommonsCore).
> >>
> >> (SapiensSpringCommon, despite his name, is not a module of sapiens !
> >> it's just a project depending on sapiens child module
> >> SapiensCommonsCore)
> >>
> >>
> >>
> >> I firstly examined SapiensCommonsCore generated pom, and it seems ok (I
> >> have successfully run "mvn validate" on it both in the project directory
> >> and in my local repository).
> >>
> >>
> >>
> >> Then I began modifying the SapiensCommonsCore generated pom (i.e.
> >> SapiensCommonsCore-2.6.0.pom) of my local repository until warnings
> >> disappears from SapiensSpringCommon compilation phase.
> >>
> >> --> It appears that deleting parent section did it <--
> >>
> >>
> >>
> >> To conclude, it seems that multi-module install goal produces invalid
> >> pom (or validate phase is not clever enough to validate dependencies on
> >> artefact of a multi-module project).
> >>
> >>
> >>
> >> What do you think ? maybe I just use badly maven ...
> >>
> >> Is there a way to fix that ?
> >>
> >>
> >>
> >> Regards,
> >>
> >>
> >>
> >> Joel
> >>
> >>
> >>
> >> FYI here's SapiensCommonsCore-2.6.0.pom version NOT producing warnings
> >>
> >>
> >>
> >> <project>
> >>
> >> <modelVersion>4.0.0</modelVersion>
> >>
> >> <groupId>sapiens</groupId>
> >>
> >> <artifactId>SapiensCommonsCore</artifactId>
> >>
> >> <packaging>jar</packaging>
> >>
> >> <version>2.6.0</version>
> >>
> >> <name>Sapiens Core</name>
> >>
> >> <!-- build and dependencies section omitted --> </project>
> >>
> >>
> >>
> >> Here's SapiensCommonsCore-2.6.0.pom original version (PRODUCING
> >> warnings)
> >>
> >>
> >>
> >> <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 section omitted -->
> >>
> >> </project>
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
> > ---------------------------------------------------------------------
> > 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]
>
>
> ---------------------------------------------------------------------
> 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]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
