RE: [Maven2] : Failed to validate POM warnings (making a lot of really annoying logs !)
Yeah, I thought it was something like that ...
Thanks for the explanation.
-Message d'origine-
De : Stephane Nicoll [mailto:[EMAIL PROTECTED]
Envoyé : mardi 21 août 2007 22:42
À : Maven Users List
Objet : Re: [Maven2] : Failed to validate POM warnings (making a lot of really
annoying logs !)
On 8/21/07, Joel COSTIGLIOLA (Services DPT SYSTEME D INFORMATION METIER)
> I still have one system scoped dependency for sun's tools.jar but it does not
> generates warning maybe because ${java.home} is defined in maven core (?)
It's a standard System property in any JVM
http://java.sun.com/j2se/1.4.2/docs/api/java/lang/System.html
Regards,
Stéphane
>
> MANY thanks Wayne and Tim for your precious help !
>
> Regards,
>
> Joel
>
> -Message d'origine-
> De: Wayne Fay [mailto:[EMAIL PROTECTED]
> Envoyé: lundi 20 août 2007 16:28
> À: Maven Users List
> Objet: Re: [Maven2] : Failed to validate POM warnings (making a lot of really
> annoying logs !)
>
> 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) :
> >
> >
> >
> >
> > Proxy settings (deleted)
> >
> >
> >
> >
> > default
> >
> >
> >
> >
> >
> >
> > D:/bea_dev/SAPIENS
> >
> >
> > D:/bea_dev/domains/sapiensPortalDomain
> >
> > D:/bea/weblogic81/server
> >
> >
> >
> >
> > default
> >
> >
> >
> >
> > -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) :
> > >
> > >
> > > 4.0.0
> > > sapiens
> > > SocleSapiens
> > > pom
> > > 2.6.0
> > > Socle Technique Sapiens
> > > http://asa.anpe.fr/asa/index.php?page=documents#sapiens
> > > Socle Technique Sapiens
> > >
> > >
> > >
> > > Joel Costigliola
> > > jojo
> > > [EMAIL PROTECTED]
> > > ANPE/ASA
> > >
> > > Developper
> > >
> > >
> > >
> > >
> > > Yoann Charpiot
> > > yoyo
> > > [EMAIL PROTECTED]
> > > ANPE/ASA
> > >
> > > Developper
> > >
> > >
> > >
&
RE: [Maven2] : Failed to validate POM warnings (making a lot of really annoying logs !)
Hi,
Good news ! The annoying warnings have been eliminated after changing weblogic
system scoped dependencies to maven one by using mvn install:install-file
command.
I still have one system scoped dependency for sun's tools.jar but it does not
generates warning maybe because ${java.home} is defined in maven core (?)
MANY thanks Wayne and Tim for your precious help !
Regards,
Joel
-Message d'origine-
De : Wayne Fay [mailto:[EMAIL PROTECTED]
Envoyé : lundi 20 août 2007 16:28
À : Maven Users List
Objet : Re: [Maven2] : Failed to validate POM warnings (making a lot of really
annoying logs !)
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) :
>
>
>
>
> Proxy settings (deleted)
>
>
>
>
> default
>
>
>
>
>
>
> D:/bea_dev/SAPIENS
>
>
> D:/bea_dev/domains/sapiensPortalDomain
>
> D:/bea/weblogic81/server
>
>
>
>
> default
>
>
>
>
> -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) :
> >
> >
> > 4.0.0
> > sapiens
> > SocleSapiens
> > pom
> > 2.6.0
> > Socle Technique Sapiens
> > http://asa.anpe.fr/asa/index.php?page=documents#sapiens
> > Socle Technique Sapiens
> >
> >
> >
> > Joel Costigliola
> > jojo
> > [EMAIL PROTECTED]
> > ANPE/ASA
> >
> > Developper
> >
> >
> >
> >
> > Yoann Charpiot
> > yoyo
> > [EMAIL PROTECTED]
> > ANPE/ASA
> >
> > Developper
> >
> >
> >
> >
> >
> >
> >
> > sapiens
> > SapiensCommonsCore
> > ${project.version}
> >
> >
> > sapiens
> > AuthentificationService
> > ${project.version}
> >
> >
> > sapiens
> > SapiensServices
> > ${project.version}
> >
> >
> > sapiens
> > SapiensCommonsWeb
> > ${project.version}
> >
> >
> >
RE: [Maven2] : Failed to validate POM warnings (making a lot of really annoying logs !)
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) :
Proxy settings (deleted)
default
D:/bea_dev/SAPIENS
D:/bea_dev/domains/sapiensPortalDomain
D:/bea/weblogic81/server
default
-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) :
>
>
> 4.0.0
> sapiens
> SocleSapiens
> pom
> 2.6.0
> Socle Technique Sapiens
> http://asa.anpe.fr/asa/index.php?page=documents#sapiens
> Socle Technique Sapiens
>
>
>
> Joel Costigliola
> jojo
> [EMAIL PROTECTED]
> ANPE/ASA
>
> Developper
>
>
>
>
> Yoann Charpiot
> yoyo
> [EMAIL PROTECTED]
> ANPE/ASA
>
> Developper
>
>
>
>
>
>
>
> sapiens
> SapiensCommonsCore
> ${project.version}
>
>
> sapiens
> AuthentificationService
> ${project.version}
>
>
> sapiens
> SapiensServices
> ${project.version}
>
>
> sapiens
> SapiensCommonsWeb
> ${project.version}
>
>
> commons-net
> commons-net
> 1.4.0
>
>
> axis
> axis
> 1.1
>
>
>
> javax.xml
> jaxrpc
> 1.1
>
>
> commons-discovery
> commons-discovery
> 0.2
>
>
> commons-logging
> commons-logging
> 1.0.3
>
>
> weblogic
> webserviceclient
> 8.1.5
> jar
> system
>
> ${bea.server.home}/lib/webserviceclient.jar
>
>
> weblogic
> weblogic
> jar
> 8.1.5
> system
>
> ${bea.
RE: [Maven2] : Failed to validate POM warnings (making a lot of really annoying logs !)
fr
org.apache.maven.plugins
maven-changes-plugin
${basedir}/src/site/xdoc/changes.xml
changes-report
socle.sapiens.site
Site Web du Socle Technique Sapiens
d:/temp
-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
>
>
>
>
>
> 4.0.0
>
> sapiens
>
> SapiensCommonsCore
>
> jar
>
> 2.6.0
>
> Sapiens Core
>
>
>
>
>
> Here's SapiensCommonsCore-2.6.0.pom original version (PRODUCING
> warnings)
>
>
>
>
>
>
>
> sapiens
>
> SocleSapiens
>
> 2.6.0
>
>
>
> 4.0.0
>
> SapiensCommonsCore
>
> jar
>
> Sapiens Core
>
>
>
>
>
> commons-net
>
> commons-net
>
>
>
>
>
>
>
>
>
>
>
>
>
>
-
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]
[Maven2] : Failed to validate POM warnings (making a lot of really annoying logs !)
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 4.0.0 sapiens SapiensCommonsCore jar 2.6.0 Sapiens Core Here's SapiensCommonsCore-2.6.0.pom original version (PRODUCING warnings) sapiens SocleSapiens 2.6.0 4.0.0 SapiensCommonsCore jar Sapiens Core commons-net commons-net
RE: multi-module project generates invalid pom ?
Just want to add that SapiensSpringCommon, despite his name, is not a module of sapiens ! It's just a project depending on sapiens child module SapiensCommonsCore. Hope things are clearer now -Message d'origine- De : Joel COSTIGLIOLA (Services DPT SYSTEME D INFORMATION METIER) [mailto:[EMAIL PROTECTED] Envoyé : mardi 14 août 2007 15:05 À : Maven Users List Objet : multi-module project generates invalid pom ? 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 good explanation in maven mailing list archive but I think I may have the reason of such annoying warnings. To explain it I must give the context when it happens. 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). 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 produces invalid pom (or validate phase is not clever enough to validate dependancies 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 4.0.0 sapiens SapiensCommonsCore jar 2.6.0 Sapiens Core Here's SapiensCommonsCore-2.6.0.pom original version (PRODUCING warnings) sapiens SocleSapiens 2.6.0 4.0.0 SapiensCommonsCore jar Sapiens Core commons-net commons-net - 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]
multi-module project generates invalid pom ?
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 good explanation in maven mailing list archive but I think I may have the reason of such annoying warnings. To explain it I must give the context when it happens. 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). 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 produces invalid pom (or validate phase is not clever enough to validate dependancies 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 4.0.0 sapiens SapiensCommonsCore jar 2.6.0 Sapiens Core Here's SapiensCommonsCore-2.6.0.pom original version (PRODUCING warnings) sapiens SocleSapiens 2.6.0 4.0.0 SapiensCommonsCore jar Sapiens Core commons-net commons-net - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to use ${project.build.directory}?
Hi,
I have also have some "Failed to validate POM" warning on a dependency from a
project of mine. When I run mvn validate on this particular dependency, it's ok
so I'm still wondering why such warnings.
does anyone has solved this issue ? (its not so big deal but it produces a lot
of warning trace which makes maven execution trace hard to read).
Can this issue be solved by using an inhouse repository ?
-Message d'origine-
De : Tawfik, Sameh E [mailto:[EMAIL PROTECTED]
Envoyé : mardi 24 juillet 2007 21:12
À : Maven Users List
Objet : RE: How to use ${project.build.directory}?
Hi Michael,
Thanks for the information, I tried this approach and it worked, and
even though the jdm.interfaces module was built correctly with no errors
or warnings, when I tried to build another module that depends on the
jdm.interfaces module, it generated the following warning:
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[WARNING] POM for 'com.mbpa:jdm-interfaces:pom:2.0:compile' is invalid.
It will be ignored for artifact resolution. Reason: Failed to validate
POM
So, probably your second suggestion would work better, by using an
in-house repository.
Thanks,
Sameh
-Original Message-
From: Michael Meyer [mailto:[EMAIL PROTECTED]
Sent: Saturday, July 21, 2007 1:51 AM
To: Maven Users List
Subject: Re: How to use ${project.build.directory}?
Hi,
yes you can use maven properties. This should do what you want:
connector
connector
1_0
system
${basedir}/../ma-jdm-tck/lib/connector_1_0.jar
But please don't do it! If you use a continuus integration tool like
continuum or hudson they will try to build your modules individually.
This will not work if you have this kind of dependencies between your
modules. So if I where you I would really go for an inhouse repository
(It's only a webserver like apache after all). You can then deploy your
3rd party jars once to this repository with 'mvn deploy:deploy-file'. In
my opinion a much nicer solution :-)
Cheers, michael
Tawfik, Sameh E schrieb:
> Hi,
>
> I'm using the following code:
>
>
> connector
> connector
> 1_0
> system
>
>
${Build_base}/ma-jdm-tck/lib/connector_1_0.jar
>
>
> This code is working fine, but it requires everyone to define the
> "Build_base" system variable, so is there is another way, where I can
> reference the folder where this jar is located without using a system
> variable?
>
> For example, can I use something like ${project.build.directory}?
>
> I've a parent folder "Project" where all the build modules are under
it
> as sub projects, so it would be nice to be able to reference the
parent
> folder, and then point to any needed third party jar file in any one
of
> the subfolders.
>
> I know I can also use mvn install:install-file -DgroupId=connector
> -DartifactId=connector -Dversion=1_0 -Dpackaging=jar
> -Dfile=/path/to/file
>
> But, it would be nice to just reference specific files by pointing at
> them using their path, so does Maven support this feature?
>
> Thanks,
>
> Sameh
>
> This email and any files transmitted with it are confidential,
proprietary
> and intended solely for the individual or entity to whom they are
addressed.
> If you have received this email in error please delete it immediately.
>
>
>
> -
> 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]
This email and any files transmitted with it are confidential, proprietary
and intended solely for the individual or entity to whom they are addressed.
If you have received this email in error please delete it immediately.
-
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]
RE: Failed to validate POM warning
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]
RE: Failed to validate POM warning
I have run validate commands on my projects ObjetTrouveService and Sapiens Core (ObjetTrouveService depends on Sapiens Core), the result is ok but when I tried to compile ObjetTrouveService then the warning come back ... (see trace) [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: Tue Jul 17 13:08:50 CEST 2007 [INFO] Final Memory: 2M/4M [INFO] [INFO] Scanning for projects... [INFO] [INFO] Building ObjetTrouve Service [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: Tue Jul 17 13:09:12 CEST 2007 [INFO] Final Memory: 4M/8M [INFO] D:\bea_dev\ApplicationModele\BAS\ObjetTrouveService>mvn compile [INFO] Scanning for projects... [INFO] [INFO] Building ObjetTrouve Service [INFO]task-segment: [compile] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [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] [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Tue Jul 17 13:09:20 CEST 2007 [INFO] Final Memory: 6M/11M [INFO] Joël Costigliola -Message d'origine- De : Rémy Sanlaville [mailto:[EMAIL PROTECTED] Envoyé : lundi 16 juillet 2007 11:09 À : Maven Users List Objet : Re: Failed to validate POM warning > > By the way, is there a tool or plugin to validate a POM ? mvn validate ? Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Failed to validate POM warning
Does anyone has an idea of why Maven is producing such a warning : [DEBUG] Retrieving parent-POM: sapiens:SocleSapiens::2.6.0 for project: null:SapiensCommonsCore:jar:null from the repository. [WARNING] POM for 'sapiens:SapiensCommonsCore:pom:2.6.0:compile' 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:compile] [DEBUG] Reason: Failed to validate POM for project sapiens:SapiensCommonsCore at Artifact [sapiens:SapiensCommonsCore:pom:2.6.0:compile] To remind you of the context, I use only a local repository and as far as I know the SapiensCommonsCore POM seems correct to me ... By the way, is there a tool or plugin to validate a POM ? Joël Costigliola -Message d'origine- De : Joel COSTIGLIOLA (Services DPT SYSTEME D INFORMATION METIER) [mailto:[EMAIL PROTECTED] Envoyé : vendredi 13 juillet 2007 09:54 À : Maven Users List Objet : RE: Failed to validate POM warning Thanks Steven for the reply. The result of "mvn help:effective-pom" command seems good to me, it has a groupId with a correct value (sapiens), here's the output : Effective POM for project 'sapiens:SapiensCommonsCore:jar:2.6.0' SocleSapiens sapiens 2.6.0 4.0.0 sapiens SapiensCommonsCore Sapiens Core 2.6.0 Socle Technique Sapiens http://asa.anpe.fr/asa/index.php?page=documents#sapiens/SapiensCommonsCore jojo JoÙl Costigliola [EMAIL PROTECTED] ANPE/ASA Developper yoyo Yoann Charpiot [EMAIL PROTECTED] ANPE/ASA Developper D:\bea_dev\SocleSapiens\SapiensCommonsCore\src\java src/main/scripts D:\bea_dev\SocleSapiens\SapiensCommonsCore\src\test D:\bea_dev\SocleSapiens\SapiensCommonsCore\target\classes D:\bea_dev\SocleSapiens\SapiensCommonsCore\target\test-classes D:\bea_dev\SocleSapiens\SapiensCommonsCore\src\main\resources D:\bea_dev\SocleSapiens\SapiensCommonsCore\src\test\resources D:\bea_dev\SocleSapiens\SapiensCommonsCore\target SapiensCommonsCore-2.6.0 maven-surefire-plugin true maven-compiler-plugin 1.4 1.4 maven-site-plugin fr maven-help-plugin 2.0.1 false central Maven Repository Switchboard http://repo1.maven.org/maven2 never false central Maven Plugin Repository http://repo1.maven.org/maven2 junit junit 3.8.1 test commons-net commons-net 1.4.0 log4j log4j 1.2.8 target/site maven-changes-plugin D:\bea_dev\SocleSapiens\SapiensCommonsCore/src/site/xdoc/changes.xml changes-report sapiens SapiensCommonsCore 2.6.0 sapiens AuthentificationService 2.6.0 sapiens SapiensServices 2.6.0 commons-net commons-net 1.4.0 weblogic weblogic 8.1.5 system D:/bea/weblogic81/server/lib/weblogic.jar socle.sapiens.site Site Web du Socle Technique Sapiens d:/temp/SapiensCommonsCore D:/bea/weblogic81/server D:/bea_dev/domains/sapiensPortalDomain I have also tried the -X option on ObjetTrouveService project for compile goal "mvn -X compile" Do you think The DEBUG trace before the WARNING is normal ? : null:SapiensCommonsCore:jar:null from the repository [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [DEBUG] sapiens:ObjetTrouveService:jar:2.6.0 (selected for null) [DEBUG] commons-lang:commons-lang:jar:2.1:compile (selected for compile) [DEBUG] junit:junit:jar:3.8.1:test (selected for test) [DEBUG] Retrieving parent-POM: sapiens:SocleSapiens::2.6.0 for project: null:SapiensCommonsCore:jar:null from the repository. [WARNING] POM for 'sapiens:SapiensCommonsCore:pom:2.6.0:compile' is invalid. It will be ignored for artifact resolution. Reason: Failed to vali
RE: [Maven2] Adding transitive dependencies in EAR
Things works now ! :) In the EAR project I had forgotten to inherits from parent project. Joel -Message d'origine- De : Joel COSTIGLIOLA (Services DPT SYSTEME D INFORMATION METIER) [mailto:[EMAIL PROTECTED] Envoyé : vendredi 13 juillet 2007 11:39 À : Maven Users List; [EMAIL PROTECTED] Objet : [Maven2] Adding transitive dependencies in EAR Hi, I'm working on a project (ObjetTrouve) that offers services as EJB packaged in an EAR. ObjetTrouve structure : - ObjetTrouveEAR (depends on ObjetTrouveEJB and ObjetTrouveService) - ObjetTrouveEJB (depends on ObjetTrouveService) - ObjetTrouveService (depends on third party jar like Spring, log4j, ...) When buiding the EAR with maven it only packages the direct dependencies i.e. ObjetTrouveEJB and ObjetTrouveService, my application can not work without third party jar needed by ObjetTrouveService. Questions : 1 - how configure the EAR plugin to include the dependencies of ObjetTrouveService ? 2 - Is there an elegant solution to this problem ? One solution may be to repeat ObjetTrouveService dependencies in the EAR project pom.xml but it's an ugly solution as I need to duplicate information. For information here's EAR pom.xml : http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 sapiens ObjetTrouveEAR ear 2.6.0 ObjetTrouveEAR http://maven.apache.org sapiens ObjetTrouveEJB ejb 2.6.0 sapiens ObjetTrouveService jar 2.6.0 org.apache.maven.plugins maven-ear-plugin sapiens ObjetTrouveService true sapiens ObjetTrouveEJB Regards, Joël Costigliola - 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]
[Maven2] Adding transitive dependencies in EAR
Hi, I'm working on a project (ObjetTrouve) that offers services as EJB packaged in an EAR. ObjetTrouve structure : - ObjetTrouveEAR (depends on ObjetTrouveEJB and ObjetTrouveService) - ObjetTrouveEJB (depends on ObjetTrouveService) - ObjetTrouveService (depends on third party jar like Spring, log4j, ...) When buiding the EAR with maven it only packages the direct dependencies i.e. ObjetTrouveEJB and ObjetTrouveService, my application can not work without third party jar needed by ObjetTrouveService. Questions : 1 - how configure the EAR plugin to include the dependencies of ObjetTrouveService ? 2 - Is there an elegant solution to this problem ? One solution may be to repeat ObjetTrouveService dependencies in the EAR project pom.xml but it's an ugly solution as I need to duplicate information. For information here's EAR pom.xml : http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 sapiens ObjetTrouveEAR ear 2.6.0 ObjetTrouveEAR http://maven.apache.org sapiens ObjetTrouveEJB ejb 2.6.0 sapiens ObjetTrouveService jar 2.6.0 org.apache.maven.plugins maven-ear-plugin sapiens ObjetTrouveService true sapiens ObjetTrouveEJB Regards, Joël Costigliola - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Failed to validate POM warning
ar, C:\Documents and Settings\joel.costigliola\.m2\repository\sapiens\SapiensCommonsCore\2.6.0\SapiensCommonsCore-2.6.0.jar, D:\bea\weblogic81\server \ext\jdbc\oracle\10g\ojdbc14_g.jar, C:\Documents and Settings\joel.costigliola\.m2\repository\commons-lang\commons-lang\2.1\commons-lang-2.1.jar, C:\Docu ments and Settings\joel.costigliola\.m2\repository\aspectj\aspectjweaver\1.5.3\aspectjweaver-1.5.3.jar, C:\Documents and Settings\joel.costigliola\.m2\re pository\logkit\logkit\1.0.1\logkit-1.0.1.jar, C:\Documents and Settings\joel.costigliola\.m2\repository\avalon-framework\avalon-framework\4.1.3\avalon-f ramework-4.1.3.jar, C:\Documents and Settings\joel.costigliola\.m2\repository\asm\asm-all\2.2.3\asm-all-2.2.3.jar, C:\Documents and Settings\joel.costigl iola\.m2\repository\org\springframework\spring\2.0.6\spring-2.0.6.jar, C:\Documents and Settings\joel.costigliola\.m2\repository\aspectj\aspectjrt\1.5.3\ aspectjrt-1.5.3.jar] [DEBUG] (f) compileSourceRoots = [D:\bea_dev\ApplicationModele\BAS\ObjetTrouveService\src\main\java] [DEBUG] (f) compilerId = javac [DEBUG] (f) debug = true [DEBUG] (f) failOnError = true [DEBUG] (f) fork = false [DEBUG] (f) optimize = false [DEBUG] (f) outputDirectory = D:\bea_dev\ApplicationModele\BAS\ObjetTrouveService\target\classes [DEBUG] (f) outputFileName = ObjetTrouveService-2.6.0 [DEBUG] (f) projectArtifact = sapiens:ObjetTrouveService:jar:2.6.0 [DEBUG] (f) showDeprecation = false [DEBUG] (f) showWarnings = false [DEBUG] (f) source = 1.4 [DEBUG] (f) staleMillis = 0 [DEBUG] (f) target = 1.4 [DEBUG] (f) verbose = false [DEBUG] -- end configuration -- [INFO] [compiler:compile] [DEBUG] Using compiler 'javac'. [DEBUG] Source directories: [D:\bea_dev\ApplicationModele\BAS\ObjetTrouveService\src\main\java] [DEBUG] Classpath: [D:\bea_dev\ApplicationModele\BAS\ObjetTrouveService\target\classes D:\bea\weblogic81\server\lib\weblogic.jar C:\Documents and Settings\joel.costigliola\.m2\repository\commons-logging\commons-logging\1.1\commons-logging-1.1.jar C:\Documents and Settings\joel.costigliola\.m2\repository\javax\servlet\servlet-api\2.3\servlet-api-2.3.jar C:\Documents and Settings\joel.costigliola\.m2\repository\log4j\log4j\1.2.8\log4j-1.2.8.jar C:\Documents and Settings\joel.costigliola\.m2\repository\sapiens\SapiensCommonsCore\2.6.0\SapiensCommonsCore-2.6.0.jar D:\bea\weblogic81\server\ext\jdbc\oracle\10g\ojdbc14_g.jar C:\Documents and Settings\joel.costigliola\.m2\repository\commons-lang\commons-lang\2.1\commons-lang-2.1.jar C:\Documents and Settings\joel.costigliola\.m2\repository\aspectj\aspectjweaver\1.5.3\aspectjweaver-1.5.3.jar C:\Documents and Settings\joel.costigliola\.m2\repository\logkit\logkit\1.0.1\logkit-1.0.1.jar C:\Documents and Settings\joel.costigliola\.m2\repository\avalon-framework\avalon-framework\4.1.3\avalon-framework-4.1.3.jar C:\Documents and Settings\joel.costigliola\.m2\repository\asm\asm-all\2.2.3\asm-all-2.2.3.jar C:\Documents and Settings\joel.costigliola\.m2\repository\org\springframework\spring\2.0.6\spring-2.0.6.jar C:\Documents and Settings\joel.costigliola\.m2\repository\aspectj\aspectjrt\1.5.3\aspectjrt-1.5.3.jar] [DEBUG] Output directory: D:\bea_dev\ApplicationModele\BAS\ObjetTrouveService\target\classes [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Fri Jul 13 09:40:30 CEST 2007 [INFO] Final Memory: 6M/11M [INFO] Joël Costigliola -Message d'origine- De : Steven Rowe [mailto:[EMAIL PROTECTED] Envoyé : jeudi 12 juillet 2007 18:02 À : Maven Users List Objet : Re: Failed to validate POM warning 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 &
RE: Failed to validate POM warning
ObjetTrouveService is refering to SapiensCommonsCore, SapiensCommonsCore
artifact is in my local repo.
I had already executed "mvn install" command for SapiensCommonsCore project, is
that what you meant by doing a "manual install" ? anyway executing "mvn
install" on SapiensCommonsCore has not solved the warning.
In my local repository you can find this files :
- sapiens/SapiensCommonsCore
- 2.6.0
- SapiensCommonsCore-2.6.0.jar
- SapiensCommonsCore-2.6.0.pom
- maven-metadata-local.xml
I have already put the content of SapiensCommonsCore-2.6.0.pom.
Here's the content of maven-metadata-local.xml
sapiens
SapiensCommonsCore
2.6.0
2.6.0
20070712081818
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 12 juillet 2007 11:05
À : users@maven.apache.org; users@maven.apache.org
Objet : RE: Failed to validate POM warning
Hi,
There can be two reasons for the scenario:
1. If you are working with the global repo; then your specific
(SapiensCommonsCore) dependencies which might not be found by the POM
(ObjetTrouveService).
So you can provide a relative path for the same in your ObjetTrouveService POM
file.
2. Otherwise, if you are referring to your local repo then do a manual install
for your project dependency so that while executing the ObjetTrouveService POM
the dependency and thence the POM will be validated.
Try this out if it works.
thanks,
vaishali pande
Cognizant Technology Solutions Pvt Ltd.
____________
From: Joel COSTIGLIOLA (Services DPT SYSTEME D INFORMATION METIER)
[mailto:[EMAIL PROTECTED]
Sent: Thu 7/12/2007 2:03 PM
To: users@maven.apache.org
Subject: Failed to validate POM warning
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 :
[INFO] Scanning for projects...
[INFO]
[INFO] Building ObjetTrouveService
[INFO]task-segment: [compile]
[INFO]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[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]
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 2 seconds
[INFO] Finished at: Thu Jul 12 10:28:49 CEST 2007
[INFO] Final Memory: 5M/10M
[INFO]
Here's ObjetTrouveService pom.xml
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
sapiens
ObjetTrouveService
jar
2.6.0-SNAPSHOT
ObjetTrouveService
http://maven.apache.org <http://maven.apache.org/>
sapiens
SapiensCommonsCore
jar
2.6.0
org.springframework
spring
2.0.6
jar
asm
asm-all
2.2.3
jar
aspectj
aspectjrt
1.5.3
jar
aspectj
aspectjweaver
1.5.3
jar
log4j
log4j
1.2.8
jar
commons-lang
commons-lang
2.1
jar
commons-dbcp
commons-dbcp
1.2.1
jar
runtime
weblogic
weblogic
jar
8.1.5
system
${bea.server.home}/lib/weblogic.jar
weblogic
oracle-jdbc-driver
8.1.5
jar
system
${bea.server.home}/ext/jdbc/oracle/10g/ojdbc14_g.jar
junit
junit
3.8.1
test
org.apache.maven.plugins
maven-surefire-plugin
true
org.apache.maven.plugins
maven-compiler-plugin
1.4
1.4
Failed to validate POM warning
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 :
[INFO] Scanning for projects...
[INFO]
[INFO] Building ObjetTrouveService
[INFO]task-segment: [compile]
[INFO]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[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]
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 2 seconds
[INFO] Finished at: Thu Jul 12 10:28:49 CEST 2007
[INFO] Final Memory: 5M/10M
[INFO]
Here's ObjetTrouveService pom.xml
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
sapiens
ObjetTrouveService
jar
2.6.0-SNAPSHOT
ObjetTrouveService
http://maven.apache.org
sapiens
SapiensCommonsCore
jar
2.6.0
org.springframework
spring
2.0.6
jar
asm
asm-all
2.2.3
jar
aspectj
aspectjrt
1.5.3
jar
aspectj
aspectjweaver
1.5.3
jar
log4j
log4j
1.2.8
jar
commons-lang
commons-lang
2.1
jar
commons-dbcp
commons-dbcp
1.2.1
jar
runtime
weblogic
weblogic
jar
8.1.5
system
${bea.server.home}/lib/weblogic.jar
weblogic
oracle-jdbc-driver
8.1.5
jar
system
${bea.server.home}/ext/jdbc/oracle/10g/ojdbc14_g.jar
junit
junit
3.8.1
test
org.apache.maven.plugins
maven-surefire-plugin
true
org.apache.maven.plugins
maven-compiler-plugin
1.4
1.4
org.apache.maven.plugins
maven-eclipse-plugin
org.springframework.ide.eclipse.core.springnature
org.springframework.ide.eclipse.core.springbuilder
maven-antrun-plugin
copy-project-artifact-to-bav-objtrouve
package
run
org.apache.maven.plugins
maven-dependency-plugin
copy-dependencies-to-bav-objtrouve
package
copy-dependencies
../../../SAPIENS/APP-INF/lib/.
false
true
weblogic,junit,commons-dbcp
And here's SapiensCommonsCore-2.6.0.pom as found in local repository :
sapiens
SocleSapiens
2.6.0
4.0.0
SapiensCommonsCore
jar
Sapiens Core
commons-net
commons-net
src/java
src/test
I have searched on the web and haven't found a reason for such a warning.
Can somebody explain me the reason of warning ?
Thanks in advance,
Regards,
Joël Costigliola
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
