[ANN] l10n-maven-plugin 1.0-alpha-1 released
The Mojo team is pleased to announce the release of the Localization Tools Maven Plugin version 1.0-alpha-1. This is the first release of this plugin. The Localization Tools Maven Plugin helps with internationalization and localization of your projects. Read more about it on the website: http://mojo.codehaus.org/l10n-maven-plugin/ -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dependencyManagement, pluginManagement, artifactManagement?
dependencyManagement doesn't work for this scenario. I get this:
[INFO] [dependency:unpack {execution: default}]
[INFO] Configured Artifact: my.group.id:my-artifact:?:zip
I should have seen this:
[INFO] [dependency:unpack {execution: default}]
[INFO] Configured Artifact: my.group.id:my-artifact:1.2.3:zip
On Fri, Mar 14, 2008 at 6:14 PM, Brian E. Fox [EMAIL PROTECTED] wrote:
DepMgt is the right way...
-Original Message-
From: simon [mailto:[EMAIL PROTECTED]
Sent: Friday, March 14, 2008 4:14 PM
To: Maven Users List
Subject: Re: dependencyManagement, pluginManagement, artifactManagement?
I expect you can define a property in a parent pom and reference it from
a child:
properties
myArtifactVersion1.2.3/myArtifactVersion
/properties
then later
version${myArtifactVersion}/version
Is this not enough?
Regards, Simon
On Fri, 2008-03-14 at 14:07 -0600, deckrider wrote:
Hi,
I have the following two snippets in my pom.xml, but what I really
want to do is define the version of my-artifact in something like
'dependencyManagement' or similar inside 'godfather-parent' so that it
can be inherited. Is there a way to do this?
Thanks,
pom.xml snippets follow:
parent
groupIdmy.godfather/groupId
artifactIdgodfather-parent/artifactId
version4.5.6/version
/parent
...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
configuration
artifactItems
artifactItem
groupIdmy.group.id/groupId
artifactIdmy-artifact/artifactId
version1.2.3/version
typezip/type
overWritefalse/overWrite
outputDirectory${project.build.directory}/unpack/outputDirectory
/artifactItem
/artifactItems
overWriteReleasesfalse/overWriteReleases
overWriteSnapshotstrue/overWriteSnapshots
/configuration
executions
execution
phasegenerate-sources/phase
goals
goalunpack/goal
/goals
/execution
/executions
/plugin
-
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]
--
ASCII ribbon campaign:
() against HTML email
/\ against Microsoft attachments
Information: http://www.expita.com/nomime.html
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: dependencyManagement, pluginManagement, artifactManagement?
Oops, I spoke too soon, even though there was ? it still used the
correct version. Thanks.
On Sat, Mar 15, 2008 at 7:21 AM, deckrider [EMAIL PROTECTED] wrote:
dependencyManagement doesn't work for this scenario. I get this:
[INFO] [dependency:unpack {execution: default}]
[INFO] Configured Artifact: my.group.id:my-artifact:?:zip
I should have seen this:
[INFO] [dependency:unpack {execution: default}]
[INFO] Configured Artifact: my.group.id:my-artifact:1.2.3:zip
On Fri, Mar 14, 2008 at 6:14 PM, Brian E. Fox [EMAIL PROTECTED] wrote:
DepMgt is the right way...
-Original Message-
From: simon [mailto:[EMAIL PROTECTED]
Sent: Friday, March 14, 2008 4:14 PM
To: Maven Users List
Subject: Re: dependencyManagement, pluginManagement, artifactManagement?
I expect you can define a property in a parent pom and reference it from
a child:
properties
myArtifactVersion1.2.3/myArtifactVersion
/properties
then later
version${myArtifactVersion}/version
Is this not enough?
Regards, Simon
On Fri, 2008-03-14 at 14:07 -0600, deckrider wrote:
Hi,
I have the following two snippets in my pom.xml, but what I really
want to do is define the version of my-artifact in something like
'dependencyManagement' or similar inside 'godfather-parent' so that it
can be inherited. Is there a way to do this?
Thanks,
pom.xml snippets follow:
parent
groupIdmy.godfather/groupId
artifactIdgodfather-parent/artifactId
version4.5.6/version
/parent
...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
configuration
artifactItems
artifactItem
groupIdmy.group.id/groupId
artifactIdmy-artifact/artifactId
version1.2.3/version
typezip/type
overWritefalse/overWrite
outputDirectory${project.build.directory}/unpack/outputDirectory
/artifactItem
/artifactItems
overWriteReleasesfalse/overWriteReleases
overWriteSnapshotstrue/overWriteSnapshots
/configuration
executions
execution
phasegenerate-sources/phase
goals
goalunpack/goal
/goals
/execution
/executions
/plugin
-
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]
--
ASCII ribbon campaign:
() against HTML email
/\ against Microsoft attachments
Information: http://www.expita.com/nomime.html
--
ASCII ribbon campaign:
() against HTML email
/\ against Microsoft attachments
Information: http://www.expita.com/nomime.html
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [POLL] Why are you not able to use the most recent maven release?
I'm responsible for the technical architecture of many projects at my location. One project in particular (still in active development with code released to production) will likely never upgrade past 2.0.4 because of the changes to dependency resolution. Although these changes are a good thing, problems will not show up in a build, but in the runtime environment; the most problematic ones are class loading issues with WebSphere, but occasionally I have had to deal with invalid class errors because somehow commons-collections 2.0 made it into the war when the project was compiled and tested against 3.2. Anyway, I'm rambling. The project does not want to upgrade because we would likely need to stop all work for at least two days for a complete system test / regression test / fix pom cycle. After spending many weeks overall resolving issues that were deemed to be maven brain damage nobody wants the hassle. I am having success at convincing newer projects to start out using 2.0.8; so I am wondering how to easily maintain two maven versions for us developers on the technical architecture team -- is it as simple as swapping out MAVEN_HOME? Thanks -trevor - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Copy:unpack
Well these questions are directed at the entire mailing list. I do appreciate all the energy you've put into this. We started work on a series of plugins because of how little is known about this particular one (can I submit changes to the documentation that helped me?), but I'd hate to manage a plugin that is pretty much a duplicate of what is offered out of the box (but we just can't figure out how to use it). -Original Message- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Fri 3/14/2008 8:54 PM To: Maven Users List Subject: RE: Copy:unpack The maven build is using it, as are lots of other builds at apache to handle the NOTICE and LICENSE files, so I know it works a little bit...but alas I haven't actually used it to filter anything myself. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2008 8:41 PM To: Maven Users List Subject: RE: Copy:unpack Done: http://jira.codehaus.org/browse/MRRESOURCES-33 No suggestions or pointers on getting this bugger working? I could live with the duplicated version number. What I can't deal with is this NOT processing resources like it says it's supposed to. When run with -X -e, btw, the output shows the resources like this: (f) resources = [EMAIL PROTECTED], [EMAIL PROTECTED] I'm guessing this could have been something more like resources.getName() or getPath() or something. Not the memory address or w/e... -Original Message- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2008 8:17 PM To: Maven Users List Subject: RE: Copy:unpack 2 - verified that I can pull it down (still not thrilled about listing version twice in the same pom). The plugin should look up the version like dependency:unpack Can you file a jira? - 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]
Re: Ojdbc Dependency Issue
I do want to point out that 14 is not the version of ojdbc. It's the J2SE version that that jar supports; classes12 is for java 1.2, ojdbc14 is for java 1.4, ojdbc5 and ojdbc 6 are for java 5 and 6 respectively. You should probably be referencing the jars as dependency groupIdcom.oracle/groupId artifactIdojdbc14/artifactId version10.2.0.3.0/version /dependency But as mentioned above you will need to deploy the jar to a repository that you control. Short of that is creating a simple batch / shell script that developers can run to install the jar to their local repositories. On Mon, Mar 10, 2008 at 12:12 PM, TJ Greenier [EMAIL PROTECTED] wrote: I am trying to find the Oracle Ojdbc14.jar file in the maven repository so that I can successfully add this as a dependency in my pom.xml. I have searched online and through the archives and all references point to the following: dependency groupIdojdbc/groupId artifactIdojdbc/artifactId version14/version /dependency However, when I browse the repo ( http://repo1.maven.org/maven2/ojdbc/ojdbc/14/) the pom file exists, but not the jar file. Likewise I considered using classes12.jar and found the same problem. The pom file exists but there is no jar file. Am I going about this the right way? Does anyone know of a repository where this file exists? I did use the install plugin to push the file locally, but I want to simplify the process for my development team. Any thoughts would be appreciated. Thanks, TJ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Multiple source tree in maven 2
Hello, am trying to mavenize an existing ant based projet. One of the caracteristics of the project is it's source tree organization modules/x/src/... modules/y/src/... modules/z/src/... I thought first of using maven modules for this, but the dependency graph makes it impossible (x depends on y which depends on z which depends on x, it's just an example). The current ant task just build all modules at same time in a single jar. So we'd like to make that too with maven2 (the mavenization should not imply a code reorg, whe just want that project to provide a pom + jar + dependencies informations). I tried to put multiple sourceDirectory entries, but maven complains there can be only one. Anyone has a suggestion on how to put multiple tree in compilation? It seems possible to put multiple resource trees, but not multiple source trees? Maybe using the generate-source goal and some copy goals, someone has suggestions? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Copy:unpack
(can I submit changes to the documentation that helped me?), Yes, we love patches to docs. Naturally the users are best at pointing out what's wrong or confusing. Just attach the patch to a jira. but I'd hate to manage a plugin that is pretty much a duplicate of what is offered out of the box (but we just can't figure out how to use it). Your best bet is to grab the code and look at it instead of writing a new one from scratch. You can ask questions about the code on dev@ -Original Message- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Fri 3/14/2008 8:54 PM To: Maven Users List Subject: RE: Copy:unpack The maven build is using it, as are lots of other builds at apache to handle the NOTICE and LICENSE files, so I know it works a little bit...but alas I haven't actually used it to filter anything myself. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2008 8:41 PM To: Maven Users List Subject: RE: Copy:unpack Done: http://jira.codehaus.org/browse/MRRESOURCES-33 No suggestions or pointers on getting this bugger working? I could live with the duplicated version number. What I can't deal with is this NOT processing resources like it says it's supposed to. When run with -X -e, btw, the output shows the resources like this: (f) resources = [EMAIL PROTECTED], [EMAIL PROTECTED] I'm guessing this could have been something more like resources.getName() or getPath() or something. Not the memory address or w/e... -Original Message- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2008 8:17 PM To: Maven Users List Subject: RE: Copy:unpack 2 - verified that I can pull it down (still not thrilled about listing version twice in the same pom). The plugin should look up the version like dependency:unpack Can you file a jira? - 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]
Re: Multiple source tree in maven 2
Hi, I had this problem earlier trying to migrate from ant. I had sources in src/java and src/util. What I did is put the sourceDirectory to src and put includes and excludes in the maven-compiler-plugin configuration. So for you it would be modules in sourceDirectory and then includes includex/src/**/*.java/include includey/src/**/*.java/include includez/src/**/*.java/include /includes in the configuration element of maven-compiler-plugin. The only problem I have so far is that doing mvn eclipse:eclipse result in having only src as source directory so I have to edit my eclipse build path by hand. Having said that I must add that I'm a maven newby and that there's maybe a better way to do it. Cyril. On Sat, Mar 15, 2008 at 5:21 PM, david.delbecq [EMAIL PROTECTED] wrote: Hello, am trying to mavenize an existing ant based projet. One of the caracteristics of the project is it's source tree organization modules/x/src/... modules/y/src/... modules/z/src/... I thought first of using maven modules for this, but the dependency graph makes it impossible (x depends on y which depends on z which depends on x, it's just an example). The current ant task just build all modules at same time in a single jar. So we'd like to make that too with maven2 (the mavenization should not imply a code reorg, whe just want that project to provide a pom + jar + dependencies informations). I tried to put multiple sourceDirectory entries, but maven complains there can be only one. Anyone has a suggestion on how to put multiple tree in compilation? It seems possible to put multiple resource trees, but not multiple source trees? Maybe using the generate-source goal and some copy goals, someone has suggestions? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Copy:unpack
My gut feeling is that remote-resources is NOT the plugin to be used for this. remote-resources will only process specific files in the bundle and only if the bundle is properly created with the remote-resources:bundle goal. It also only fills in properties/values that are specifically set in the plugins configuration, not everything in the pom. remote-resources targets a specific need, and this really doesn't sound like it. Most likely, you should add a feature request to the dependency plugin to allow filtering of stuff that is unpacked. I think a new filtering component was created recently that could make it pretty easy to do. Not really sure though. Dan On Saturday 15 March 2008, EJ Ciramella wrote: Well these questions are directed at the entire mailing list. I do appreciate all the energy you've put into this. We started work on a series of plugins because of how little is known about this particular one (can I submit changes to the documentation that helped me?), but I'd hate to manage a plugin that is pretty much a duplicate of what is offered out of the box (but we just can't figure out how to use it). -Original Message- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Fri 3/14/2008 8:54 PM To: Maven Users List Subject: RE: Copy:unpack The maven build is using it, as are lots of other builds at apache to handle the NOTICE and LICENSE files, so I know it works a little bit...but alas I haven't actually used it to filter anything myself. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2008 8:41 PM To: Maven Users List Subject: RE: Copy:unpack Done: http://jira.codehaus.org/browse/MRRESOURCES-33 No suggestions or pointers on getting this bugger working? I could live with the duplicated version number. What I can't deal with is this NOT processing resources like it says it's supposed to. When run with -X -e, btw, the output shows the resources like this: (f) resources = [EMAIL PROTECTED], [EMAIL PROTECTED] I'm guessing this could have been something more like resources.getName() or getPath() or something. Not the memory address or w/e... -Original Message- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2008 8:17 PM To: Maven Users List Subject: RE: Copy:unpack 2 - verified that I can pull it down (still not thrilled about listing version twice in the same pom). The plugin should look up the version like dependency:unpack Can you file a jira? - 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] -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple source tree in maven 2
have a look at the buildhelper-maven-plugin at org.codehaus.mojo it has the ability to add multiple source paths the right way rather than your hack Sent from my iPod On 15 Mar 2008, at 16:55, Cyril Ledru [EMAIL PROTECTED] wrote: Hi, I had this problem earlier trying to migrate from ant. I had sources in src/java and src/util. What I did is put the sourceDirectory to src and put includes and excludes in the maven-compiler-plugin configuration. So for you it would be modules in sourceDirectory and then includes includex/src/**/*.java/include includey/src/**/*.java/include includez/src/**/*.java/include /includes in the configuration element of maven-compiler-plugin. The only problem I have so far is that doing mvn eclipse:eclipse result in having only src as source directory so I have to edit my eclipse build path by hand. Having said that I must add that I'm a maven newby and that there's maybe a better way to do it. Cyril. On Sat, Mar 15, 2008 at 5:21 PM, david.delbecq [EMAIL PROTECTED] wrote: Hello, am trying to mavenize an existing ant based projet. One of the caracteristics of the project is it's source tree organization modules/x/src/... modules/y/src/... modules/z/src/... I thought first of using maven modules for this, but the dependency graph makes it impossible (x depends on y which depends on z which depends on x, it's just an example). The current ant task just build all modules at same time in a single jar. So we'd like to make that too with maven2 (the mavenization should not imply a code reorg, whe just want that project to provide a pom + jar + dependencies informations). I tried to put multiple sourceDirectory entries, but maven complains there can be only one. Anyone has a suggestion on how to put multiple tree in compilation? It seems possible to put multiple resource trees, but not multiple source trees? Maybe using the generate-source goal and some copy goals, someone has suggestions? - 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: [POLL] Why are you not able to use the most recent maven release?
Jack this is a critical point in my 2.0.8 distro located at $M2_HOME/archetype/pom.xml I have this maven2.0 I have the following profile configuration.. project xmlns=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; modelVersion4.0.0/modelVersion ...parentPoms etc.. profiles profile idmaven2.0/id //which contains the dependency.. dependency groupIdcommons-collections/groupId artifactIdcommons-collections/artifactId version3.2/version /dependency does this confirm your understanding ? Martin - Original Message - From: Trevor Torrez [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Saturday, March 15, 2008 9:10 AM Subject: Re: [POLL] Why are you not able to use the most recent maven release? I'm responsible for the technical architecture of many projects at my location. One project in particular (still in active development with code released to production) will likely never upgrade past 2.0.4 because of the changes to dependency resolution. Although these changes are a good thing, problems will not show up in a build, but in the runtime environment; the most problematic ones are class loading issues with WebSphere, but occasionally I have had to deal with invalid class errors because somehow commons-collections 2.0 made it into the war when the project was compiled and tested against 3.2. Anyway, I'm rambling. The project does not want to upgrade because we would likely need to stop all work for at least two days for a complete system test / regression test / fix pom cycle. After spending many weeks overall resolving issues that were deemed to be maven brain damage nobody wants the hassle. I am having success at convincing newer projects to start out using 2.0.8; so I am wondering how to easily maintain two maven versions for us developers on the technical architecture team -- is it as simple as swapping out MAVEN_HOME? Thanks -trevor - 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: Bug within Maven ANT Tasks?
Hi Matthew,
Authentication defined in settings.xml is a supported feature: your problem is
surprising.
Can you attach your pom.xml, simplified as much as possible, and settings.xml
(and strike your password, of course) to let me see?
Can you send the ant -v output too? It should contain Using remote
repositories: message, then a description of every repository used: if
authentication is detected, you'll have authentication=...username...
content.
regards,
Hervé
Le mardi 11 mars 2008, Matthew Tordoff a écrit :
Hi Herve,
Thanks for this response. I have replaced my old maven-ant-tasks-2.0.8.jar
with the one you pointed me to. The substitution of the property works fine
now, however, it keeps giving me a 401 error (access denied).
I am specifying my authentication details (username and password) inside of
my settings.xml.
Any help or means by which I can debug this more would be greatly
appreciated (i'm currently using -v to get ANT to give me verbose output,
however, the 401 message is not as detailed as I would like useful).
Cheers,
Matt
Le lundi 10 mars 2008, Matthew Tordoff a écrit :
Hi all,
It looks like this could have been fixed in 2.0.9 which introduces
support for default profiles. I am guessing because I am defining my
properties within a profile , this is why it is not being read by the
Maven ANT tasks.
I just put a SNAPSHOT on
http://people.apache.org/~hboutemy/maven-ant-tasks-2.0.9-SNAPSHOT.jar to
let you check if it works for you.
Does anyone know when or how to find out when this version will be
available? I have looked on their roadmap and it seems like all issues
have been resolved for 2.0.9.
Maven Ant Tasks 2.0.9 will be released 1 or 2 weeks after Maven 2.0.9.
regards,
Hervé
Matt
-Original Message-
From: Matthew Tordoff [mailto:[EMAIL PROTECTED]
Sent: 10 March 2008 16:26
To: users@maven.apache.org
Subject: Bug within Maven ANT Tasks?
Hi all,
I am using Maven ANT tasks to deploy a number of JAR files I produce as
part of my build. For each JAR file I have a corresponding pom.xml file
(not called pom.xml however:) ).
I define references to these files in my build script as follows:
artifact:pom id=xxx.pom file=xxx.xml/
And later refer to them when I want to deploy as follows:
artifact:deploy file=xxx.jar
remoteRepository refid=my-repository/
pom refid=xxx.pom/
/artifact:deploy
Since I have multiple pom files (one for each JAR file to deploy) I need
to set the version of the JAR artifacts in every pom file. To avoid
having to do this I tried adding a property deploy.version inside of my
settings.xml as follows:
settings
...
profiles
profile
iddefault/id
activation
activeByDefaulttrue/activeByDefault
/activation
...
properties
deploy.versionversion_number/deploy.version
/properties
...
/profile
/profiles
...
/settings
I have then put ${deploy.version} inside of the version tag of each of my
poms. The issue is that when I run my ANT deploy task this variable is
not translated from ${deploy.version}, however, if I rename each of the
pom files to pom.xml and run mvn help:effective-pom then the property
name is appropriately substituted with whatever I have set
deploy.version to in settings.xml.
My question is... why is there this inconsistency in substitution?
Any help would be greatly appreciated.
Kind Regards,
Matt
_
Telly addicts unite!
http://www.searchgamesbox.com/tvtown.shtml
_
Free games, great prizes - get gaming at Gamesbox.
http://www.searchgamesbox.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_
Telly addicts unite!
http://www.searchgamesbox.com/tvtown.shtml
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] m2eclipse 0.9.0 Released
Eugene Kuleshov on 14/03/08 19:41, wrote: deckrider wrote: By the way, I like have a multi-module project like this: pom.xml foo/pom.xml bar/pom.xml ... I like that I can check this out of Subversion as a Maven project using this same structure so that it does not become individual Eclipse projects scattered about my workspace! [snipped] Also note that, using name patterns you can keep all projects from the same root next to each other in your Eclipse workspace. you can use also 'working sets' to hide projects that are not currently relevant for you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [POLL] Why are you not able to use the most recent maven release?
I don't follow...what's the bug here? -Original Message- From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Saturday, March 15, 2008 4:57 PM To: [EMAIL PROTECTED] Cc: Maven Users List Subject: Re: [POLL] Why are you not able to use the most recent maven release? Jack this is a critical point in my 2.0.8 distro located at $M2_HOME/archetype/pom.xml I have this maven2.0 I have the following profile configuration.. project xmlns=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; modelVersion4.0.0/modelVersion ...parentPoms etc.. profiles profile idmaven2.0/id //which contains the dependency.. dependency groupIdcommons-collections/groupId artifactIdcommons-collections/artifactId version3.2/version /dependency does this confirm your understanding ? Martin - Original Message - From: Trevor Torrez [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Saturday, March 15, 2008 9:10 AM Subject: Re: [POLL] Why are you not able to use the most recent maven release? I'm responsible for the technical architecture of many projects at my location. One project in particular (still in active development with code released to production) will likely never upgrade past 2.0.4 because of the changes to dependency resolution. Although these changes are a good thing, problems will not show up in a build, but in the runtime environment; the most problematic ones are class loading issues with WebSphere, but occasionally I have had to deal with invalid class errors because somehow commons-collections 2.0 made it into the war when the project was compiled and tested against 3.2. Anyway, I'm rambling. The project does not want to upgrade because we would likely need to stop all work for at least two days for a complete system test / regression test / fix pom cycle. After spending many weeks overall resolving issues that were deemed to be maven brain damage nobody wants the hassle. I am having success at convincing newer projects to start out using 2.0.8; so I am wondering how to easily maintain two maven versions for us developers on the technical architecture team -- is it as simple as swapping out MAVEN_HOME? Thanks -trevor - 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]
RE: [POLL] Why are you not able to use the most recent maven release?
I'm responsible for the technical architecture of many projects at my location. One project in particular (still in active development with code released to production) will likely never upgrade past 2.0.4 because of the changes to dependency resolution. Although these changes are a good thing, problems will not show up in a build, but in the runtime environment; the most problematic ones are class loading issues with WebSphere, but occasionally I have had to deal with invalid class errors because somehow commons-collections 2.0 made it into the war when the project was compiled and tested against 3.2. We made a tool in the dependency plugin to help detect and correct these. Even if you aren't upgrading, you might want to run the tool as you might have problems you don't know about. I understood the problem enough to write the tool and was shocked how many issues I had in my own corp builds. Anyway, I'm rambling. The project does not want to upgrade because we would likely need to stop all work for at least two days for a complete system test / regression test / fix pom cycle. After spending many weeks overall resolving issues that were deemed to be maven brain damage nobody wants the hassle. Not entirely try if you use the tool mentioned above. You will be able to fix your poms before moving over to the next version. That's how I did it with 60+ developer and 100s of modules. I am having success at convincing newer projects to start out using 2.0.8; so I am wondering how to easily maintain two maven versions for us developers on the technical architecture team -- is it as simple as swapping out MAVEN_HOME? And path, yes. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
