Re: "[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

2009-11-29 Thread Brett Randall
Hi Ellecer, Just scanning through this thread I'm not sure if anyone has asked you to run "mvn help:effective-pom" in the problem environment. Does that show the correct variable substitution? Brett On Tue, Nov 24, 2009 at 5:39 PM, Ellecer Valencia wrote: > Hi Other Brett, > > It's a similar p

Re: "[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

2009-11-23 Thread Ellecer Valencia
Hi Other Brett, It's a similar problem, except that the environment settings are coming from the shell environment and not a setttings.xml Ellecer On Mon, Nov 23, 2009 at 6:16 PM, Brett Randall wrote: > Hi Ellecer, > > Is there a chance you are seeing http://jira.codehaus.org/browse/MNG-4148

Re: "[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

2009-11-22 Thread Brett Randall
Hi Ellecer, Is there a chance you are seeing http://jira.codehaus.org/browse/MNG-4148 , which is duplicated by http://jira.codehaus.org/browse/MNG-2626 ? Does that fit your parent POM hierarchy? Other Brett On Mon, Nov 23, 2009 at 2:17 PM, Ellecer Valencia wrote: > On Mon, Nov 23, 2009 at 11:1

Re: "[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

2009-11-22 Thread Ellecer Valencia
On Mon, Nov 23, 2009 at 11:18 AM, Brett Porter wrote: > Did you also "export WL_HOME"? > > I tried something similar here and it works fine in 2.2.1. > > - Brett Hi Brett, I'd presume the environment variable being there means that's already happened. =) This entry is in .bashrc so I'm pretty s

Re: "[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

2009-11-22 Thread Brett Porter
Did you also "export WL_HOME"? I tried something similar here and it works fine in 2.2.1. - Brett On 23/11/2009, at 10:08 AM, Ellecer Valencia wrote: > But that's exactly the problem - it *is* defined in the environment. :( > > $ls -l $WL_HOME/server/lib/webservices.jar > -rwxr-xr-x. 1 dev dev

Re: "[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

2009-11-22 Thread Ellecer Valencia
But that's exactly the problem - it *is* defined in the environment. :( $ls -l $WL_HOME/server/lib/webservices.jar -rwxr-xr-x. 1 dev dev 1696324 2009-10-30 16:55 /usr/java/weblogic/server/lib/webservices.jar $echo $WL_HOME /usr/java/weblogic The Maven project I am trying to build has a pom.xm

Re: "[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

2009-11-22 Thread Brian Fox
Well Maven sees it just like the message: [DEBUG] For managed dependency Dependency {groupId=weblogic, artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency must specify an absolute path systemPath. So since the first one works and the second one doesn't, that leads me to believe

Re: "[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

2009-11-22 Thread Ellecer Valencia
Hi Brian, Could you please clarify what's actually "plain wrong" about it? Going back to the example I posted: com.sun rt 1.5.0.11 system ${java.home}/lib/rt.jar weblogic weblogic 10.0 system ${env.WL_HOME}/server/lib/webl

Re: "[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

2009-11-20 Thread Brian E. Fox
Maybe 2.2.2 will fix it. =) Not likely. The pom is plain wrong an it was a bug in 2.x which allowed it to go unnoticed. On Fri, Nov 20, 2009 at 3:42 PM, Brett Randall wrote: http://jira.codehaus.org/browse/MNG-4379 ... or did your team log that :). On Fri, Nov 20, 2009 at 2:59 PM, E

Re: "[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

2009-11-19 Thread Ellecer Valencia
No, not my team. I think a more sensible fix is to just put the weblogic jars in Artifactory, but it's in a pom that I don't have much control over. Maybe 2.2.2 will fix it. =) On Fri, Nov 20, 2009 at 3:42 PM, Brett Randall wrote: > http://jira.codehaus.org/browse/MNG-4379 ... or did your team l

Re: "[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

2009-11-19 Thread Brett Randall
http://jira.codehaus.org/browse/MNG-4379 ... or did your team log that :). On Fri, Nov 20, 2009 at 2:59 PM, Ellecer Valencia wrote: > Hi Brett, > > Thanks for the suggestion. I may have found the issue. Would it be this: > > > Validation Errors: > [DEBUG] For dependency Dependency {groupId=weblo

Re: "[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

2009-11-19 Thread Ellecer Valencia
Hi Brett, Thanks for the suggestion. I may have found the issue. Would it be this: Validation Errors: [DEBUG] For dependency Dependency {groupId=weblogic, artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency must specify an absolute path systemPath. [DEBUG] For managed dependen

Re: "[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

2009-11-19 Thread Brett Randall
Hi Ellecer What is the output of mvn -e -X ... Brett On Fri, Nov 20, 2009 at 11:41 AM, Ellecer Valencia wrote: > Hi, > > How come when I try a build using Maven 2.2.1 I get multiple messages like > this: > > "[WARNING] POM for 'mypackage.artifact:pom:1.0.2-SNAPSHOT:compile' is > invalid. > > It

"[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

2009-11-19 Thread Ellecer Valencia
Hi, How come when I try a build using Maven 2.2.1 I get multiple messages like this: "[WARNING] POM for 'mypackage.artifact:pom:1.0.2-SNAPSHOT:compile' is invalid. Its dependencies (if any) will NOT be available to the current build." These errors weren't displaying when I was using Maven 2.0.1