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: Bug within Maven ANT Tasks?
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
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
RE: Bug within Maven ANT Tasks?
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.
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.
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
Re: Bug within Maven ANT Tasks?
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]
