Latest embedded Maven not expanding paths
|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
 |
Latest embedded Maven not expanding paths
by Daniel Mutch
::
Rate this Message:
Hi Milos
Probably just FYI but it seems the latest embedded maven in mevenide build #376 is not expanding paths that contain system variables e.g. ${JAVA_6_HOME}/bin/javac fails to resolve. Shame I really want to try out the new configurations functionality as I currently use a lot of custom goals to try and achieve a similar thing... Rolling back ;) |
|
|
Re: Latest embedded Maven not expanding paths
by Milos Kleint-2
::
Rate this Message:
you mean the http://deadlock.netbeans.org/hudson/job/mevenide/376/
build doesn't while any previous builds did? Milos On Tue, Apr 15, 2008 at 3:34 AM, Daniel Mutch <daniel.mutch@...> wrote: > > Hi Milos > > Probably just FYI but it seems the latest embedded maven in mevenide build > #376 is not expanding paths that contain system variables > > e.g. ${JAVA_6_HOME}/bin/javac > > fails to resolve. > > Shame I really want to try out the new configurations functionality as I > currently use a lot of custom goals to try and achieve a similar thing... > > Rolling back ;) > > > -- > View this message in context: http://www.nabble.com/Latest-embedded-Maven-not-expanding-paths-tp16693310p16693310.html > Sent from the mevenide - user mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Latest embedded Maven not expanding paths
by Daniel Mutch
::
Rate this Message:
Yes, our build files already contain these paths and have always happily used them.
|
|
|
Re: Latest embedded Maven not expanding paths
by Milos Kleint-2
::
Rate this Message:
hello Daniel,
I've checked with a maven dev (jdcasey) and he claimed that the ${JAVA_6_HOME} probably just worked by coincidence before and that the correct way of referencing env variables is ${env.JAVA_6_HOME} I've checked our embedded execution code and figured we don't add the env. variable properties to the execution so I fixed that. http://fisheye.codehaus.org/changelog/mevenide/?cs=5151 I'm wondering if you could try gettting the latest builds and check if it works now http://deadlock.netbeans.org/hudson/job/mevenide/ either with the previous setup you had and/or with the "env." string prepanded Thanks Milos On Tue, Apr 15, 2008 at 10:09 AM, Daniel Mutch <daniel.mutch@...> wrote: > > > Yes, our build files already contain these paths and have always happily > used them. > > > > > Milos Kleint wrote: > > > > you mean the http://deadlock.netbeans.org/hudson/job/mevenide/376/ > > build doesn't while any previous builds did? > > > > Milos > > > > On Tue, Apr 15, 2008 at 3:34 AM, Daniel Mutch > > <daniel.mutch@...> wrote: > >> > >> Hi Milos > >> > >> Probably just FYI but it seems the latest embedded maven in mevenide > >> build > >> #376 is not expanding paths that contain system variables > >> > >> e.g. ${JAVA_6_HOME}/bin/javac > >> > >> fails to resolve. > >> > >> Shame I really want to try out the new configurations functionality as I > >> currently use a lot of custom goals to try and achieve a similar > >> thing... > >> > >> Rolling back ;) > >> > >> > >> -- > >> View this message in context: > >> http://www.nabble.com/Latest-embedded-Maven-not-expanding-paths-tp16693310p16693310.html > >> Sent from the mevenide - user mailing list archive at Nabble.com. > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe from this list, please visit: > >> > >> http://xircles.codehaus.org/manage_email > >> > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > > > > > -- > View this message in context: http://www.nabble.com/Latest-embedded-Maven-not-expanding-paths-tp16693310p16697259.html > > > Sent from the mevenide - user mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Latest embedded Maven not expanding paths
by Daniel Mutch
::
Rate this Message:
Hi Milos
Ok if i now add env. it fixes the build process, however, I get a project marked as <Badly formed Maven project> which i guess means the env variables are not available to the parser? I think this is caused by our friend the system depenency defined as follows: <profiles> <profile> <id>default-tools.jar</id> <activation> <property> <name>java.vendor</name> <value>Sun Microsystems Inc.</value> </property> </activation> <dependencies> <dependency> <groupId>com.sun</groupId> <artifactId>tools</artifactId> <version>1.6.0</version> <scope>system</scope> <type>jar</type> <systemPath>${env.JAVA_6_HOME}/lib/tools.jar</systemPath> </dependency> </dependencies> </profile> </profiles> However all works fine at compile time. cheers Dan
|
|
|
Re: Latest embedded Maven not expanding paths
by Milos Kleint-2
::
Rate this Message:
hi daniel,
thanks for trying out so fast.. my bad. I haven't included the variables in the embedder instance that loads projects. I'll do that ASAP. Milos On Wed, Apr 16, 2008 at 11:13 AM, Daniel Mutch <daniel.mutch@...> wrote: > > Hi Milos > > Ok if i now add env. it fixes the build process, however, I get a project > marked as <Badly formed Maven project> which i guess means the env variables > are not available to the parser? > > I think this is caused by our friend the system depenency defined as > follows: > > <profiles> > <profile> > <id>default-tools.jar</id> > <activation> > <property> > <name>java.vendor</name> > <value>Sun Microsystems Inc.</value> > </property> > </activation> > <dependencies> > <dependency> > <groupId>com.sun</groupId> > <artifactId>tools</artifactId> > <version>1.6.0</version> > <scope>system</scope> > <type>jar</type> > > <systemPath>${env.JAVA_6_HOME}/lib/tools.jar</systemPath> > </dependency> > </dependencies> > </profile> > </profiles> > > However all works fine at compile time. > > cheers > Dan > > > > > Milos Kleint wrote: > > > > hello Daniel, > > > > I've checked with a maven dev (jdcasey) and he claimed that the > > ${JAVA_6_HOME} probably just worked by coincidence before and that the > > correct way of referencing env variables is ${env.JAVA_6_HOME} > > I've checked our embedded execution code and figured we don't add the > > env. variable properties to the execution so I fixed that. > > http://fisheye.codehaus.org/changelog/mevenide/?cs=5151 > > > > I'm wondering if you could try gettting the latest builds and check if > > it works now > > http://deadlock.netbeans.org/hudson/job/mevenide/ > > either with the previous setup you had and/or with the "env." string > > prepanded > > > > Thanks > > > > Milos > > > > > > On Tue, Apr 15, 2008 at 10:09 AM, Daniel Mutch > > <daniel.mutch@...> wrote: > >> > >> > >> Yes, our build files already contain these paths and have always happily > >> used them. > >> > >> > >> > >> > >> Milos Kleint wrote: > >> > > >> > you mean the http://deadlock.netbeans.org/hudson/job/mevenide/376/ > >> > build doesn't while any previous builds did? > >> > > >> > Milos > >> > > >> > On Tue, Apr 15, 2008 at 3:34 AM, Daniel Mutch > >> > <daniel.mutch@...> wrote: > >> >> > >> >> Hi Milos > >> >> > >> >> Probably just FYI but it seems the latest embedded maven in mevenide > >> >> build > >> >> #376 is not expanding paths that contain system variables > >> >> > >> >> e.g. ${JAVA_6_HOME}/bin/javac > >> >> > >> >> fails to resolve. > >> >> > >> >> Shame I really want to try out the new configurations functionality > >> as I > >> >> currently use a lot of custom goals to try and achieve a similar > >> >> thing... > >> >> > >> >> Rolling back ;) > >> >> > >> >> > >> >> -- > >> >> View this message in context: > >> >> > >> http://www.nabble.com/Latest-embedded-Maven-not-expanding-paths-tp16693310p16693310.html > >> >> Sent from the mevenide - user mailing list archive at Nabble.com. > >> >> > >> >> > >> >> > >> --------------------------------------------------------------------- > >> >> To unsubscribe from this list, please visit: > >> >> > >> >> http://xircles.codehaus.org/manage_email > >> >> > >> >> > >> >> > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe from this list, please visit: > >> > > >> > http://xircles.codehaus.org/manage_email > >> > > >> > > >> > > >> > > >> > >> -- > >> View this message in context: > >> http://www.nabble.com/Latest-embedded-Maven-not-expanding-paths-tp16693310p16697259.html > >> > >> > >> Sent from the mevenide - user mailing list archive at Nabble.com. > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe from this list, please visit: > >> > >> http://xircles.codehaus.org/manage_email > >> > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > > > > > -- > View this message in context: http://www.nabble.com/Latest-embedded-Maven-not-expanding-paths-tp16693310p16719503.html > > > Sent from the mevenide - user mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Latest embedded Maven not expanding paths
by Milos Kleint-2
::
Rate this Message:
it was a bit more complicated than that. Maven source base had to be
fixed as well. Should be working now in #383 and later. Milos On Wed, Apr 16, 2008 at 12:37 PM, Milos Kleint <mkleint@...> wrote: > hi daniel, > thanks for trying out so fast.. > > my bad. I haven't included the variables in the embedder instance that > loads projects. I'll do that ASAP. > > Milos > > On Wed, Apr 16, 2008 at 11:13 AM, Daniel Mutch > > > <daniel.mutch@...> wrote: > > > > Hi Milos > > > > Ok if i now add env. it fixes the build process, however, I get a project > > marked as <Badly formed Maven project> which i guess means the env variables > > are not available to the parser? > > > > I think this is caused by our friend the system depenency defined as > > follows: > > > > <profiles> > > <profile> > > <id>default-tools.jar</id> > > <activation> > > <property> > > <name>java.vendor</name> > > <value>Sun Microsystems Inc.</value> > > </property> > > </activation> > > <dependencies> > > <dependency> > > <groupId>com.sun</groupId> > > <artifactId>tools</artifactId> > > <version>1.6.0</version> > > <scope>system</scope> > > <type>jar</type> > > > > <systemPath>${env.JAVA_6_HOME}/lib/tools.jar</systemPath> > > </dependency> > > </dependencies> > > </profile> > > </profiles> > > > > However all works fine at compile time. > > > > cheers > > Dan > > > > > > > > > > Milos Kleint wrote: > > > > > > hello Daniel, > > > > > > I've checked with a maven dev (jdcasey) and he claimed that the > > > ${JAVA_6_HOME} probably just worked by coincidence before and that the > > > correct way of referencing env variables is ${env.JAVA_6_HOME} > > > I've checked our embedded execution code and figured we don't add the > > > env. variable properties to the execution so I fixed that. > > > http://fisheye.codehaus.org/changelog/mevenide/?cs=5151 > > > > > > I'm wondering if you could try gettting the latest builds and check if > > > it works now > > > http://deadlock.netbeans.org/hudson/job/mevenide/ > > > either with the previous setup you had and/or with the "env." string > > > prepanded > > > > > > Thanks > > > > > > Milos > > > > > > > > > On Tue, Apr 15, 2008 at 10:09 AM, Daniel Mutch > > > <daniel.mutch@...> wrote: > > >> > > >> > > >> Yes, our build files already contain these paths and have always happily > > >> used them. > > >> > > >> > > >> > > >> > > >> Milos Kleint wrote: > > >> > > > >> > you mean the http://deadlock.netbeans.org/hudson/job/mevenide/376/ > > >> > build doesn't while any previous builds did? > > >> > > > >> > Milos > > >> > > > >> > On Tue, Apr 15, 2008 at 3:34 AM, Daniel Mutch > > >> > <daniel.mutch@...> wrote: > > >> >> > > >> >> Hi Milos > > >> >> > > >> >> Probably just FYI but it seems the latest embedded maven in mevenide > > >> >> build > > >> >> #376 is not expanding paths that contain system variables > > >> >> > > >> >> e.g. ${JAVA_6_HOME}/bin/javac > > >> >> > > >> >> fails to resolve. > > >> >> > > >> >> Shame I really want to try out the new configurations functionality > > >> as I > > >> >> currently use a lot of custom goals to try and achieve a similar > > >> >> thing... > > >> >> > > >> >> Rolling back ;) > > >> >> > > >> >> > > >> >> -- > > >> >> View this message in context: > > >> >> > > >> http://www.nabble.com/Latest-embedded-Maven-not-expanding-paths-tp16693310p16693310.html > > >> >> Sent from the mevenide - user mailing list archive at Nabble.com. > > >> >> > > >> >> > > >> >> > > >> --------------------------------------------------------------------- > > >> >> To unsubscribe from this list, please visit: > > >> >> > > >> >> http://xircles.codehaus.org/manage_email > > >> >> > > >> >> > > >> >> > > >> > > > >> > --------------------------------------------------------------------- > > >> > To unsubscribe from this list, please visit: > > >> > > > >> > http://xircles.codehaus.org/manage_email > > >> > > > >> > > > >> > > > >> > > > >> > > >> -- > > >> View this message in context: > > >> http://www.nabble.com/Latest-embedded-Maven-not-expanding-paths-tp16693310p16697259.html > > >> > > >> > > >> Sent from the mevenide - user mailing list archive at Nabble.com. > > >> > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe from this list, please visit: > > >> > > >> http://xircles.codehaus.org/manage_email > > >> > > >> > > >> > > > > > > --------------------------------------------------------------------- > > > To unsubscribe from this list, please visit: > > > > > > http://xircles.codehaus.org/manage_email > > > > > > > > > > > > > > > > -- > > View this message in context: http://www.nabble.com/Latest-embedded-Maven-not-expanding-paths-tp16693310p16719503.html > > > > > > Sent from the mevenide - user mailing list archive at Nabble.com. > > > > > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Latest embedded Maven not expanding paths
by Daniel Mutch
::
Rate this Message:
Hi Milos
Thanks for the fixes. This all seems to working nicely now. There is however one final issue which is more of a maven issue but may be related to the maven changes you made. Everything compiles fine and there are no IDE issues but at runtime I get the following warning message [WARN]POM for 'com.barcap.sng:sng-engine-tools:pom:4.4-SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Failed to validate POM for project com.barcap.sng:sng-engine-tools at C:\dan\.m2\repository\com\barcap\sng\sng-engine-tools\4.4-SNAPSHOT\sng-engine-tools-4.4-SNAPSHOT.pom [DEBUG]Reason: Failed to validate POM for project com.barcap.sng:sng-engine-tools at C:\dan\.m2\repository\com\barcap\sng\sng-engine-tools\4.4-SNAPSHOT\sng-engine-tools-4.4-SNAPSHOT.pom [DEBUG] Validation Errors: [DEBUG]For dependency Dependency {groupId=com.sun, artifactId=tools, version=1.6.0, type=jar}: system-scoped dependency must specify an absolute path systemPath. [DEBUG] This is related to the tools.jar system reference included in the pom as follows: <profiles> <profile> <id>default-tools.jar</id> <activation> <property> <name>java.vendor</name> <value>Sun Microsystems Inc.</value> </property> </activation> <dependencies> <dependency> <groupId>com.sun</groupId> <artifactId>tools</artifactId> <version>1.6.0</version> <scope>system</scope> <type>jar</type> <systemPath>${env.JAVA_6_HOME}/lib/tools.jar</systemPath> </dependency> </dependencies> </profile> </profiles> So it would seem that maven isn't expanding the env variable at this point? thanks Dan
|
| Free embeddable forum powered by Nabble | Forum Help |
