Re: maven release plugin issue
no, I'm suggesting that you use the dependency plugin to unpack your jar for
you.
That way you will not care if it has not beein installed into the repository
*yet*
2009/5/4 huser mpinj...@atxg.com
I am fairly new to maven. So I guess I need a plugin to copy the
abc-interface-api.jar to my local repository ? Are you suggesting I do this
by dependency plugin. I tried adding this.
Basically, abc-interface-api-$project.parent.version} should get copied to
local .m2 repository under com/abc/t3/abc-interface=api/1.6
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idcopy/id
phasepackage/phase
goals
goalcopy/goal
/goals
configuration
artifactItems
artifactItem
groupIdcom.abc.t3/groupId
artifactIdabc-interface-api/artifactId
version${project.parent.version}/version
typejar/type
overWritetrue/overWrite
outputDirectory${env.M2_REPO}/com/abc/t3/outputDirectory
destFileNameabc-interface-api-${project.parent.version}.jar/destFileName
/artifactItem
/artifactItems
!-- other configurations here --
/configuration
/execution
/executions
/plugin
but, then I get this error:
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO]
--
--
[INFO] [INFO] Unable to find artifact.
[INFO]
[INFO] Embedded error: Unable to download the artifact from any repository
[INFO]
[INFO] Try downloading the file manually from the project website.
[INFO]
[INFO] Then, install it using the command:
[INFO] mvn install:install-file -DgroupId=com.abc.t3
-DartifactId=abc-inter
face-api -Dversion=1.6 -Dpackaging=jar -Dfile=/path/to/file
[INFO]
[INFO] Alternatively, if you host your own repository you can deploy the
file th
ere:
[INFO] mvn deploy:deploy-file -DgroupId=com.abc.t3
-DartifactId=abc-interfa
ce-api -Dversion=1.6 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-Dreposito
ryId=[id]
[INFO]
[INFO]
[INFO] com.abc.t3:abc-interface-api:jar:1.6
[INFO]
[INFO] from the specified remote repositories:
[INFO] nexus
(http://abcsvn001.na.abcglobal.com:8081/nexus/content/groups/publi
c),
[INFO] snapshots
(http://abcsvn001.na.abcglobal.com:8081/nexus/content/reposito
ries/snapshotshttp://abcsvn001.na.abcglobal.com:8081/nexus/content/reposito%0Aries/snapshots
)
[INFO]
[INFO] [INFO]
--
Stephen Connolly-2 wrote:
ugh!
that sounds hacky hacky hack
you probably should try having the dependency plugin unpack for you
-Stephen
On 04/05/2009, huser mpinj...@atxg.com wrote:
Hi,
I am running maven release plugin by:
mvn -f pom.xml -Pabc.debug.release --batch-mode -Dtag=REL1.5-TEST
-DtagBase=https://abcsvn001.na.abcglobal.com/abc_repos/T3/tags;
-DreleaseVersion=1.5 -DdevelopmentVersion=1.6-SNAPSHOT release:prepare
And I get this build error.
[INFO] [INFO] An Ant BuildException has occured: The following error
occurred wh
ile executing this line:
[INFO]
C:\mvn_rel\int_002_dev_test\services-api\abc-interface-api\xsd-extract.xm
l:19: Error while expanding C:\Documents and
Settings\huser\.m2\repository\co
m\abc\t3\abc-websvc-api\1.5\abc-websvc-api-1.5.jar
[INFO] java.io.FileNotFoundException: C:\Documents and
Settings\huser\.m2\rep
ository\com\abc\t3\abc-websvc-api\1.5\abc-websvc-api-1.5.jar (The system
cannot
find the path specified)
I do not get this error if I do not use the release plugin i.e.
mvn -f pom.xml -Pabc.debug.release clean install deploy
In my xsd-extract.xml, I have an environment variable $verinfo which
unjar
src=${env.M2_REPO}/com/abc/t3/abc-websvc-api/${verinfo}/abc-websvc-api-${verinfo}.jar
gets its value defined in abc-interface-api
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idextract-xsds/id
phaseinitialize/phase
configuration
tasks
property name=verinfo value=${project.parent.version} /
echo message=My dependency name: ${verinfo} /
ant antfile=${basedir}/xsd-extract.xml
target name=retrieve-xsds /
/ant
/tasks
/configuration
goals
goalrun/goal
[release/scm] Can system locale change release:prepare behavior ?
Hey, I posted this one to dev@ by mistake, here it is again to us...@. I'm facing weird problems with the maven-release-plugin and friends. I use maven-release-plugin-2.0-beta-9 and get the same results with either maven 2.1.0 or 2.2.0-RC1. I tried with two subversion clients with the same results too : 1.4.6 and 1.6.1. I'm issuing the following instruction : mvn -B clean release:prepare -DreleaseVersion=0.4.0 - DdevelopmentVersion=0.5.0-SNAPSHOT I'm getting the following error (full execution log is attached to this email): [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Impossible de trouver la localisation dans le dépôt de 'svn://acme.net/trunk/ekPom' pour la révision 0 So, a little bit upset I tried bizarre things and found something interesting, IOW: back to roots :) My default locale is fr_FR.UTF-8, if I use LC_ALL as C or en_US.UTF-8 everything is working as expected !! What do you think ? /Paul p...@dosadi $ mvn -B clean release:prepare -DreleaseVersion=0.4.0 -DdevelopmentVersion=0.5.0-SNAPSHOT + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [INFO] Building ekPom [INFO]task-segment: [clean] [INFO] [INFO] [clean:clean] [INFO] Deleting file set: /home/paul/src/ekPom/target (included: [**], excluded: []) [INFO] [INFO] Building ekPom [INFO]task-segment: [release:prepare] (aggregator-style) [INFO] [INFO] [release:prepare] [INFO] Verifying that there are no local modifications... [INFO] Executing: /bin/sh -c cd /home/paul/src/ekPom svn --non-interactive status [INFO] Working directory: /home/paul/src/ekPom [INFO] Checking dependencies and plugins for snapshots ... [INFO] Transforming 'ekPom'... [INFO] Not generating release POMs [INFO] Executing goals 'clean install'... [INFO] [INFO] Scanning for projects... [INFO] [INFO] [INFO] [INFO] Building ekPom [INFO] [INFO]task-segment: [clean, install] [INFO] [INFO] [INFO] [INFO] [clean:clean] [INFO] [INFO] [site:attach-descriptor] [INFO] [INFO] [install:install] [INFO] [INFO] Installing /home/paul/src/ekPom/target/pom-transformed.xml to /home/paul/.m2/repository/ek/tools/ekPom/0.4.0/ekPom-0.4.0.pom [INFO] [INFO] [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] [INFO] [INFO] Total time: 2 seconds [INFO] [INFO] Finished at: Mon May 04 14:45:56 CEST 2009 [INFO] [INFO] Final Memory: 11M/70M [INFO] [INFO] [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /home/paul/src/ekPom svn --non-interactive commit --file /tmp/maven-scm-637804792.commit --targets /tmp/maven-scm-8796652735550861631-targets [INFO] Working directory: /home/paul/src/ekPom [INFO] Unknown line: 'Envoi pom.xml' [INFO] Unknown line: 'Transmission des données .' [INFO] Unknown line: 'Révision 7443 propagée.' [INFO] Tagging release with the label ekPom-0.4.0... [INFO] Executing: /bin/sh -c cd /home/paul/src/ekPom svn --non-interactive copy --file /tmp/maven-scm-2029772501.commit --revision 0 svn://acme.net/trunk/ekPom svn://acme.net/tags/ekPom-0.4.0 [INFO] Working directory: /home/paul/src/ekPom [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Impossible de trouver la localisation dans le dépôt de 'svn://acme.net/trunk/ekPom' pour la révision 0 [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Impossible de trouver la localisation dans le dépôt de 'svn://acme.net/trunk/ekPom' pour la révision 0 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:699) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523) at
Re: Automagically update scm tag
Well, not many answers. I guess I'll file an improvement request. I think I'm going to put it into the maven-scm-plugin tracker ( http://jira.codehaus.org/browse/SCM). What do you think? Cheers. 2009/5/4 Baptiste MATHUS m...@batmat.net Hi all, I'm looking for a simple a quick way to update my scm tags. I'm currently refactoring my projects, and I find it cumbersome to manually update ths scm tag to the new although the information is already present in the svn metadata. I took a quick look at scm:*** goals but can't find the one that fits my need corresponding (moreover I think this plugin is more designed to be used as a dependency to front-end plugin, so there's not a lot documentation for each goals :)). What I'd like is a goal that would retrieved the svn info . command output and update the scm *connection tags in the pom. Does this goal already exist or should I file an improvement request about it? Thanks a lot. Cheers. -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: Automagically update scm tag
Filed: http://jira.codehaus.org/browse/SCM-468 Tchüss. 2009/5/5 Baptiste MATHUS m...@batmat.net Well, not many answers. I guess I'll file an improvement request. I think I'm going to put it into the maven-scm-plugin tracker ( http://jira.codehaus.org/browse/SCM). What do you think? Cheers. 2009/5/4 Baptiste MATHUS m...@batmat.net Hi all, I'm looking for a simple a quick way to update my scm tags. I'm currently refactoring my projects, and I find it cumbersome to manually update ths scm tag to the new although the information is already present in the svn metadata. I took a quick look at scm:*** goals but can't find the one that fits my need corresponding (moreover I think this plugin is more designed to be used as a dependency to front-end plugin, so there's not a lot documentation for each goals :)). What I'd like is a goal that would retrieved the svn info . command output and update the scm *connection tags in the pom. Does this goal already exist or should I file an improvement request about it? Thanks a lot. Cheers. -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
AW: Automagically update scm tag
Hi Baptiste! It isn't clear to me what you mean with 'update tag'. Do you like to re-tag in the SCM? LieGrue, strub - Ursprüngliche Mail Von: Baptiste MATHUS m...@batmat.net An: Maven Users List users@maven.apache.org Gesendet: Dienstag, den 5. Mai 2009, 09:34:51 Uhr Betreff: Re: Automagically update scm tag Well, not many answers. I guess I'll file an improvement request. I think I'm going to put it into the maven-scm-plugin tracker ( http://jira.codehaus.org/browse/SCM). What do you think? Cheers. 2009/5/4 Baptiste MATHUS Hi all, I'm looking for a simple a quick way to update my scm tags. I'm currently refactoring my projects, and I find it cumbersome to manually update ths scm tag to the new although the information is already present in the svn metadata. I took a quick look at scm:*** goals but can't find the one that fits my need corresponding (moreover I think this plugin is more designed to be used as a dependency to front-end plugin, so there's not a lot documentation for each goals :)). What I'd like is a goal that would retrieved the svn info . command output and update the *connection tags in the pom. Does this goal already exist or should I file an improvement request about it? Thanks a lot. Cheers. -- Baptiste MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- Baptiste MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Automagically update scm tag
I think he wants to update the scm section in the pom to match what is displayed from svn info 2009/5/5 Mark Struberg strub...@yahoo.de Hi Baptiste! It isn't clear to me what you mean with 'update tag'. Do you like to re-tag in the SCM? LieGrue, strub - Ursprüngliche Mail Von: Baptiste MATHUS m...@batmat.net An: Maven Users List users@maven.apache.org Gesendet: Dienstag, den 5. Mai 2009, 09:34:51 Uhr Betreff: Re: Automagically update scm tag Well, not many answers. I guess I'll file an improvement request. I think I'm going to put it into the maven-scm-plugin tracker ( http://jira.codehaus.org/browse/SCM). What do you think? Cheers. 2009/5/4 Baptiste MATHUS Hi all, I'm looking for a simple a quick way to update my scm tags. I'm currently refactoring my projects, and I find it cumbersome to manually update ths scm tag to the new although the information is already present in the svn metadata. I took a quick look at scm:*** goals but can't find the one that fits my need corresponding (moreover I think this plugin is more designed to be used as a dependency to front-end plugin, so there's not a lot documentation for each goals :)). What I'd like is a goal that would retrieved the svn info . command output and update the *connection tags in the pom. Does this goal already exist or should I file an improvement request about it? Thanks a lot. Cheers. -- Baptiste MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- Baptiste MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Automagically update scm tag
Exactly. I don't want this new goal to try and commit anything. Just retrieve the svn info output from the working copy and update scm connection and developerConnection accordingly. I guess there could an option to update connection, developerConnection or both with the retrieved value. For example, we always have the same value there. Cheers. 2009/5/5 Stephen Connolly stephen.alan.conno...@gmail.com I think he wants to update the scm section in the pom to match what is displayed from svn info 2009/5/5 Mark Struberg strub...@yahoo.de Hi Baptiste! It isn't clear to me what you mean with 'update tag'. Do you like to re-tag in the SCM? LieGrue, strub - Ursprüngliche Mail Von: Baptiste MATHUS m...@batmat.net An: Maven Users List users@maven.apache.org Gesendet: Dienstag, den 5. Mai 2009, 09:34:51 Uhr Betreff: Re: Automagically update scm tag Well, not many answers. I guess I'll file an improvement request. I think I'm going to put it into the maven-scm-plugin tracker ( http://jira.codehaus.org/browse/SCM). What do you think? Cheers. 2009/5/4 Baptiste MATHUS Hi all, I'm looking for a simple a quick way to update my scm tags. I'm currently refactoring my projects, and I find it cumbersome to manually update ths scm tag to the new although the information is already present in the svn metadata. I took a quick look at scm:*** goals but can't find the one that fits my need corresponding (moreover I think this plugin is more designed to be used as a dependency to front-end plugin, so there's not a lot documentation for each goals :)). What I'd like is a goal that would retrieved the svn info . command output and update the *connection tags in the pom. Does this goal already exist or should I file an improvement request about it? Thanks a lot. Cheers. -- Baptiste MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- Baptiste MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: Automagically update scm tag
You'd probably also want to update the url providing that it follows an identified rule, since moste viewsvn equivalents follow a path rule in their uri, this should not be a big issue 2009/5/5 Baptiste MATHUS m...@batmat.net Exactly. I don't want this new goal to try and commit anything. Just retrieve the svn info output from the working copy and update scm connection and developerConnection accordingly. I guess there could an option to update connection, developerConnection or both with the retrieved value. For example, we always have the same value there. Cheers. 2009/5/5 Stephen Connolly stephen.alan.conno...@gmail.com I think he wants to update the scm section in the pom to match what is displayed from svn info 2009/5/5 Mark Struberg strub...@yahoo.de Hi Baptiste! It isn't clear to me what you mean with 'update tag'. Do you like to re-tag in the SCM? LieGrue, strub - Ursprüngliche Mail Von: Baptiste MATHUS m...@batmat.net An: Maven Users List users@maven.apache.org Gesendet: Dienstag, den 5. Mai 2009, 09:34:51 Uhr Betreff: Re: Automagically update scm tag Well, not many answers. I guess I'll file an improvement request. I think I'm going to put it into the maven-scm-plugin tracker ( http://jira.codehaus.org/browse/SCM). What do you think? Cheers. 2009/5/4 Baptiste MATHUS Hi all, I'm looking for a simple a quick way to update my scm tags. I'm currently refactoring my projects, and I find it cumbersome to manually update ths scm tag to the new although the information is already present in the svn metadata. I took a quick look at scm:*** goals but can't find the one that fits my need corresponding (moreover I think this plugin is more designed to be used as a dependency to front-end plugin, so there's not a lot documentation for each goals :)). What I'd like is a goal that would retrieved the svn info . command output and update the *connection tags in the pom. Does this goal already exist or should I file an improvement request about it? Thanks a lot. Cheers. -- Baptiste MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- Baptiste MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: Automagically update scm tag
I just discovered that subtag of scm :). Well, then yes. Although you'd have to provide some viewscm root url to start from. 2009/5/5 Stephen Connolly stephen.alan.conno...@gmail.com You'd probably also want to update the url providing that it follows an identified rule, since moste viewsvn equivalents follow a path rule in their uri, this should not be a big issue 2009/5/5 Baptiste MATHUS m...@batmat.net Exactly. I don't want this new goal to try and commit anything. Just retrieve the svn info output from the working copy and update scm connection and developerConnection accordingly. I guess there could an option to update connection, developerConnection or both with the retrieved value. For example, we always have the same value there. Cheers. 2009/5/5 Stephen Connolly stephen.alan.conno...@gmail.com I think he wants to update the scm section in the pom to match what is displayed from svn info 2009/5/5 Mark Struberg strub...@yahoo.de Hi Baptiste! It isn't clear to me what you mean with 'update tag'. Do you like to re-tag in the SCM? LieGrue, strub - Ursprüngliche Mail Von: Baptiste MATHUS m...@batmat.net An: Maven Users List users@maven.apache.org Gesendet: Dienstag, den 5. Mai 2009, 09:34:51 Uhr Betreff: Re: Automagically update scm tag Well, not many answers. I guess I'll file an improvement request. I think I'm going to put it into the maven-scm-plugin tracker ( http://jira.codehaus.org/browse/SCM). What do you think? Cheers. 2009/5/4 Baptiste MATHUS Hi all, I'm looking for a simple a quick way to update my scm tags. I'm currently refactoring my projects, and I find it cumbersome to manually update ths scm tag to the new although the information is already present in the svn metadata. I took a quick look at scm:*** goals but can't find the one that fits my need corresponding (moreover I think this plugin is more designed to be used as a dependency to front-end plugin, so there's not a lot documentation for each goals :)). What I'd like is a goal that would retrieved the svn info . command output and update the *connection tags in the pom. Does this goal already exist or should I file an improvement request about it? Thanks a lot. Cheers. -- Baptiste MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- Baptiste MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: maven 2.1.0 not passing on system properties to java virtual machine
I don't think is a problem in either maven or surefire plugin. Else the surefire is behaving differently. It looks like now, when surefire forks the jvm, will not take all the system properties from the parent jvm. That's why you should pass whatever system properties you want for the tests, using argLine. So, both these should work mvn2.1 -Dsystem.test.property=test test -DforkMode=never or mvn2.1 test -DargLine=-Dsystem.test.property=test , costin -- View this message in context: http://www.nabble.com/maven-2.1.0-not-passing-on-system-properties-to-java-virtual-machine-tp23133501p23383667.html Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Automagically update scm tag
I'm assuming that there is a valid url already present and that the url matches the same code as linked by the connection and developerConnection... so all you need to do is get the common trailing part and update it to match the changes to the connection and developerConnection urls 2009/5/5 Baptiste MATHUS m...@batmat.net I just discovered that subtag of scm :). Well, then yes. Although you'd have to provide some viewscm root url to start from. 2009/5/5 Stephen Connolly stephen.alan.conno...@gmail.com You'd probably also want to update the url providing that it follows an identified rule, since moste viewsvn equivalents follow a path rule in their uri, this should not be a big issue 2009/5/5 Baptiste MATHUS m...@batmat.net Exactly. I don't want this new goal to try and commit anything. Just retrieve the svn info output from the working copy and update scm connection and developerConnection accordingly. I guess there could an option to update connection, developerConnection or both with the retrieved value. For example, we always have the same value there. Cheers. 2009/5/5 Stephen Connolly stephen.alan.conno...@gmail.com I think he wants to update the scm section in the pom to match what is displayed from svn info 2009/5/5 Mark Struberg strub...@yahoo.de Hi Baptiste! It isn't clear to me what you mean with 'update tag'. Do you like to re-tag in the SCM? LieGrue, strub - Ursprüngliche Mail Von: Baptiste MATHUS m...@batmat.net An: Maven Users List users@maven.apache.org Gesendet: Dienstag, den 5. Mai 2009, 09:34:51 Uhr Betreff: Re: Automagically update scm tag Well, not many answers. I guess I'll file an improvement request. I think I'm going to put it into the maven-scm-plugin tracker ( http://jira.codehaus.org/browse/SCM). What do you think? Cheers. 2009/5/4 Baptiste MATHUS Hi all, I'm looking for a simple a quick way to update my scm tags. I'm currently refactoring my projects, and I find it cumbersome to manually update ths scm tag to the new although the information is already present in the svn metadata. I took a quick look at scm:*** goals but can't find the one that fits my need corresponding (moreover I think this plugin is more designed to be used as a dependency to front-end plugin, so there's not a lot documentation for each goals :)). What I'd like is a goal that would retrieved the svn info . command output and update the *connection tags in the pom. Does this goal already exist or should I file an improvement request about it? Thanks a lot. Cheers. -- Baptiste MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- Baptiste MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: [release/scm] Can system locale change release:prepare behavior ?
I already had this kind of problem. From what I remember, I just removed all the localization files from the subversion installation directory. Actually, I think that the maven-scm-api reads the output of the CLI, and it doesn't understand when it doesn't display the output in english... Cheers. 2009/5/5 Paul MERLIN p...@nosphere.org Hey, I posted this one to dev@ by mistake, here it is again to us...@. I'm facing weird problems with the maven-release-plugin and friends. I use maven-release-plugin-2.0-beta-9 and get the same results with either maven 2.1.0 or 2.2.0-RC1. I tried with two subversion clients with the same results too : 1.4.6 and 1.6.1. I'm issuing the following instruction : mvn -B clean release:prepare -DreleaseVersion=0.4.0 - DdevelopmentVersion=0.5.0-SNAPSHOT I'm getting the following error (full execution log is attached to this email): [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Impossible de trouver la localisation dans le dépôt de 'svn://acme.net/trunk/ekPom' pour la révision 0 So, a little bit upset I tried bizarre things and found something interesting, IOW: back to roots :) My default locale is fr_FR.UTF-8, if I use LC_ALL as C or en_US.UTF-8 everything is working as expected !! What do you think ? /Paul - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: Error transferring file: repo1.maven.org, Repository 'central' will be blacklisted
Thanks for reply, I omitted that if maven run as a super-user task all works correctly, and so was with normal-user runs until a few days ago, when suddenly (and without any evident cause) maven was no more able to perform builds as a normal-user... The problem isn't vital, because I can do everything as root, but I'd like to know what happened. Andrea
Re: [release/scm] Can system locale change release:prepare behavior ?
Le mardi 05 mai 2009 11:09:37, Baptiste MATHUS a écrit : I already had this kind of problem. From what I remember, I just removed all the localization files from the subversion installation directory. Actually, I think that the maven-scm-api reads the output of the CLI, and it doesn't understand when it doesn't display the output in english... Cheers. Thanks for your answer Baptiste. Someone answered in the dev@ list too : Le mardi 05 mai 2009 11:05:13, Grzegorz Slowikowski a écrit : Maven parses scm output. I don't remember details, but I've had the same problem. My solution was permanent setting LC_MESSAGES to C. Greetings Grzegorz Slowikowski I don't know yet how I will handle this accross developers. Thanks. /Paul - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Error transferring file: repo1.maven.org, Repository 'central' will be blacklisted
False alarm, the second build was made without 'sudo'. Under root all works correctly. Sorry.
Re: Error transferring file: repo1.maven.org, Repository 'central' will be blacklisted
Update: now root-builds do not work anymore. first it succesfully created a camel-service-unit then the Error transferring file: repo1.maven.org problem raised again, but this time under root. I continue to not understand why: Here is the mvn commands output: Thanks again, Andrea /* service-unit (successful) */ and...@martin:~/Programmi/apache-servicemix-3.3/tutorials/3_camel$ sudo mvn archetype:create -DarchetypeArtifactId=servicemix-camel-service-unit -DarchetypeGroupId=org.apache.servicemix.tooling -DartifactId=tutorial-camel-su [sudo] password for andrea: [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [INFO] org.codehaus.mojo: checking for updates from central [INFO] artifact org.apache.maven.plugins:maven-archetype-plugin: checking for updates from central [Various downloads...] [INFO] BUILD SUCCESSFUL [...] /* Now the service-assembly (build error) */ and...@martin:~/Programmi/apache-servicemix-3.3/tutorials/3_camel$ mvn -e archetype:create -DarchetypeArtifactId=servicemix-service-assembly -DarchetypeGroupId=org.apache.servicemix.tooling -DartifactId=tutorial-camel-sa + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] SMX-Camel :: Tutorial [INFO] A Camel based JBI Service Unit [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retrieved from repository: central due to an error: Error transferring file: repo1.maven.org [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1546) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1786) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:446) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:176) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:229) at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:91) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:172) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1517) ... 14 more
Re: Error transferring file: repo1.maven.org, Repository 'central' will be blacklisted
I am not sure, but when you run as root, doesn't maven take the settings.xml from /root/.m2/settings.xml and when not as root from ~/.m2/settings.xml. Maybe there is a difference between those files? Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Tue, May 5, 2009 at 11:58 AM, Andrea Libero Valori andrealibero.val...@gmail.com wrote: False alarm, the second build was made without 'sudo'. Under root all works correctly. Sorry. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Apache snapshot repository metadata incorrect.
Thanks Brian. /James Thanks for finding that. It's been fixed now. The old repo had some junk versions that were being proxied. It's been cleaned out. We schedule daily cleanups of the snapshots, leaving behind 3 copies for a minimum of 10 days, the snapshots are removed when a release is published. Otherwise, we don't have it setup to actively recreate the metadata as under normal conditions it should be managed by maven, but in situations like this it's certainly handy to repair with a few clicks. On May 1, 2009, at 12:09 PM, Nord, James wrote: Hi all, The metadata served by nexus for http://repository.apache.org/snapshots/ is incorrect for the archetype plugin. (https://repository.apache.org/content/groups/snapshots/org/apache/mav en /plugins/maven-archetype-plugin/) metadata contains lots of snapshot versions but only 2.0-alpha-5-SNAPSHOT is available. (and hence running mvn archetype:generate from the command line fails as it tries to get 12-SNAPSHOT /James ?xml version=1.0 encoding=UTF-8 ? - https://repository.apache.org/content/groups/snapshots/org/apache/mav en /plugins/maven-archetype-plugin/maven-metadata.xml# metadata xsi:schemaLocation=http://maven.apache.org/METADATA/1.0.0 http://maven.apache.org/xsd/metadata-1.0.0.xsd; xmlns=http://maven.apache.org/METADATA/1.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; groupIdorg.apache.maven.plugins/groupId artifactIdmaven-archetype-plugin/artifactId version2.0-alpha-4-SNAPSHOT/version - https://repository.apache.org/content/groups/snapshots/org/apache/mav en /plugins/maven-archetype-plugin/maven-metadata.xml# versioning latest12-SNAPSHOT/latest release / - https://repository.apache.org/content/groups/snapshots/org/apache/mav en /plugins/maven-archetype-plugin/maven-metadata.xml# versions version2.0-alpha-4-SNAPSHOT/version version2.0-alpha-5-SNAPSHOT/version version0.3.0-SNAPSHOT/version version1.0-SNAPSHOT/version version1.0-alpha-2-SNAPSHOT/version version1.0-alpha-3-SNAPSHOT/version version1.0-beta-3-SNAPSHOT/version version1.0.2-SNAPSHOT/version version1.1-SNAPSHOT/version version1.1.1-SNAPSHOT/version version1.2-SNAPSHOT/version version1.2.2-SNAPSHOT/version version1.3-SNAPSHOT/version version2.0-beta-9-SNAPSHOT/version version2.0-beta-10-SNAPSHOT/version version2.0.11-SNAPSHOT/version version2.1.0-SNAPSHOT/version version2.1-SNAPSHOT/version version2.1.0-M2-SNAPSHOT/version version2.2-SNAPSHOT/version version2.3-SNAPSHOT/version version2.4.4-SNAPSHOT/version version2.5-SNAPSHOT/version version3.0-alpha-2-SNAPSHOT/version version11-SNAPSHOT/version version12-SNAPSHOT/version /versions lastUpdated20090417213533/lastUpdated /versioning /metadata ** This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify the postmas...@nds.com and destroy the original message. Messages sent to and from NDS may be monitored. NDS cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS. To protect the environment please do not print this e-mail unless necessary. NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00 ** - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org ** This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify the postmas...@nds.com and destroy the original message. Messages sent to and from NDS may
maven-assembly-plugin
Maven Users Is there a way to specify what goes on the Classpath that is created by the Archive tag when using the jar-with-dependencies descriptor? I want to add some *.xml configuration files to the classpath so I can find them when the application starts. Mike Karrys
Providing external jar file as part of a larger project
Hello, Is there a way to provide a jar file that is not available in a Maven repository as part of a multi-module project? For example, if in a multi-module project (groupId=example,artifactId=exampleroot), a sub-module (groupId=example,artifactId=mainapp) depends on a jar that's not available in any repository -- the dependency being expressed as (groupId=example,artifactId=extlib), it's possible to resolve this dependency using mvn install:install-file -DgroupId=example -DartifactId=extlib ... beforehand. However, I wonder if there would be a way to provide this jar within a sub-module, without having to use mvn install:install-file manually, so that mvn clean package works from the top of the multi-module project directly. The structure would be like this: |-- pom.xml (groupId=example,artifactId=exampleroot) |-- mainapp |-- pom.xml (groupId=example,artifactId=mainapp) |-- src ... |-- extlib |-- pom.xml (groupId=example,artifactId=extlib) |-- lib |-- extlib.jar One way to solve this could be to unjar extlib.jar into extlib/target/classes during its 'compile' phase, but this doesn't seem very clean. Any better solution? Best wishes, Bruno. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven password encryption and usage in a CI server
Hi, I was reading about the recent enhancements to the management of server passwords in settings.xml at http://maven.apache.org/guides/mini/guide-encryption.html A few questions arose around the actual security provided by these enhancements in the context of a build/CI server. Agreed, this is an enhancement over passwords in clear text in settings.xml, where any developer can run the help:effective-settings goal in a custom build definition to gain access to the passwords configured there on the server. But can it be considered a safe protection in the context of a build server? For instance, what prevents a developer from running a build definition that runs a command through the exec or antrun plugin that outputs the content of the settings-security.xml, thereby compromising the encryption? Unless I miss the obvious (or the less obvious) I am under the impression that this enhancement makes it harder to get to the passwords, but does not make it impossible (and maybe this was never the goal). Thank you in advance for your insights/pointers. -Olivier - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: unable to deploy site with webdav
Hello Ross, I have the same problem as you had. Did you get resolve the problem? I would appreciate your help. Kind regards, Michael rossputin wrote: Hi, I am using maven 2.0.9, and everything is working great except for site deployment with webdav. I have not tried any other kind of deployment yet, as I do it manually, so it may not be just site deployment that is not working for me. I have an apache webdav setup in place, and can access it in a browser or in Cadaver via command line. When I execute my maven site:deploy command, I always get a '500 Internal Server Error' with wagon-webdav 1.0-beta-2, and with wagon-webdav 1.0-beta-1 nothing much seems to happen, the process executes successfully, but nothing is copied across. Has anyone successfully deployed with any recent version of maven over webdav? One of the books I have on it suggests using it. I have not seen much on the mailing list though. Thanks in advance for your help. Ross -- View this message in context: http://www.nabble.com/unable-to-deploy-site-with-webdav-tp17276670p23386321.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
DefaultMavenProjectBuilder throws NPE
Hello, I am using the Maven Project jar 2.1.0. I get the following exception when I use it: Exception in thread main java.lang.NullPointerException at org .apache .maven.project.ProjectUtils.buildArtifactRepository(ProjectUtils.java: 115) at org .apache .maven .project.ProjectUtils.buildArtifactRepositories(ProjectUtils.java:56) at org .apache .maven .project .DefaultMavenProjectBuilder .buildArtifactRepositories(DefaultMavenProjectBuilder.java:951) at org .apache .maven .project .DefaultMavenProjectBuilder .buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:508) at org .apache .maven .project .DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:227) at org .apache .maven .project .DefaultMavenProjectBuilder .buildWithDependencies(DefaultMavenProjectBuilder.java:357) at org .apache .maven .project .DefaultMavenProjectBuilder .buildWithDependencies(DefaultMavenProjectBuilder.java:345) at torque .tasks .TestJDBCtoXMLTransformationTask .test(TestJDBCtoXMLTransformationTask.java:47) at torque .tasks .TestJDBCtoXMLTransformationTask .main(TestJDBCtoXMLTransformationTask.java:80) I see in the source code of DefaultMavenProjectBuilder.java, the private member private ArtifactRepositoryFactory artifactRepositoryFactory; is never initialized. Hence resulting in the above mentioned NPE. Can anyone point me how to resolve this issue? I am using the Maven2 plugin of Torque project from Apache DB project in my application as given below: MavenProjectBuilder builder = (MavenProjectBuilder) lookup(MavenProjectBuilder.ROLE); ArtifactRepositoryLayout localRepositoryLayout = (ArtifactRepositoryLayout) lookup( ArtifactRepositoryLayout.ROLE, default); ArtifactRepository localRepository = new DefaultArtifactRepository( local, file:// + getBasedir() + File.separator + target/test-classes/repository, localRepositoryLayout); MavenProject mavenProject = builder.buildWithDependencies( new File( getBasedir(), target/test-classes/projects/ TestJDBCtoXMLTransformationTask/pom.xml), localRepository, null); Thank you in advance, Regards, Amar
RE: unable to deploy site with webdav
Ross- which container are you attempting to upload to ? Martin __ Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung / Note de déni et de confidentialité This message is confidential. If you should not be the intended receiver, then we ask politely to report. Each unauthorized forwarding or manufacturing of a copy is inadmissible. This message serves only for the exchange of information and has no legal binding effect. Due to the easy manipulation of emails we cannot take responsibility over the the contents. Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Tue, 5 May 2009 05:16:31 -0700 From: mail4s...@arcor.de To: users@maven.apache.org Subject: Re: unable to deploy site with webdav Hello Ross, I have the same problem as you had. Did you get resolve the problem? I would appreciate your help. Kind regards, Michael rossputin wrote: Hi, I am using maven 2.0.9, and everything is working great except for site deployment with webdav. I have not tried any other kind of deployment yet, as I do it manually, so it may not be just site deployment that is not working for me. I have an apache webdav setup in place, and can access it in a browser or in Cadaver via command line. When I execute my maven site:deploy command, I always get a '500 Internal Server Error' with wagon-webdav 1.0-beta-2, and with wagon-webdav 1.0-beta-1 nothing much seems to happen, the process executes successfully, but nothing is copied across. Has anyone successfully deployed with any recent version of maven over webdav? One of the books I have on it suggests using it. I have not seen much on the mailing list though. Thanks in advance for your help. Ross -- View this message in context: http://www.nabble.com/unable-to-deploy-site-with-webdav-tp17276670p23386321.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ Hotmail® goes with you. http://windowslive.com/Tutorial/Hotmail/Mobile?ocid=TXT_TAGLM_WL_HM_Tutorial_Mobile1_052009
Re: Maven password encryption and usage in a CI server
You are correct. If someone is able to read the maven code and find the default password, decrypt the master password, then they could decrypt the user password. It's also decrypted on the wire if you aren't using https with your repos. The trick with a build server is to make a special account for that system, the real danger comes when you use a corporate password and someone gets that. If you have real concerns about the build server, don't give people permissions to change the jobs and then it will be harder for them to get at these files. Olivier Dehon wrote: Hi, I was reading about the recent enhancements to the management of server passwords in settings.xml at http://maven.apache.org/guides/mini/guide-encryption.html A few questions arose around the actual security provided by these enhancements in the context of a build/CI server. Agreed, this is an enhancement over passwords in clear text in settings.xml, where any developer can run the help:effective-settings goal in a custom build definition to gain access to the passwords configured there on the server. But can it be considered a safe protection in the context of a build server? For instance, what prevents a developer from running a build definition that runs a command through the exec or antrun plugin that outputs the content of the settings-security.xml, thereby compromising the encryption? Unless I miss the obvious (or the less obvious) I am under the impression that this enhancement makes it harder to get to the passwords, but does not make it impossible (and maybe this was never the goal). Thank you in advance for your insights/pointers. -Olivier - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: unable to deploy site with webdav
Hello Martin, I try to upload to the apache-webserver 2.2. I've configured webdav as described in the httpd.conf and the httpd-dav.conf. I tested it via windows web folder and it works fine. Michael mgainty wrote: Ross- which container are you attempting to upload to ? Martin __ Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung / Note de déni et de confidentialité This message is confidential. If you should not be the intended receiver, then we ask politely to report. Each unauthorized forwarding or manufacturing of a copy is inadmissible. This message serves only for the exchange of information and has no legal binding effect. Due to the easy manipulation of emails we cannot take responsibility over the the contents. Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Tue, 5 May 2009 05:16:31 -0700 From: mail4s...@arcor.de To: users@maven.apache.org Subject: Re: unable to deploy site with webdav Hello Ross, I have the same problem as you had. Did you get resolve the problem? I would appreciate your help. Kind regards, Michael rossputin wrote: Hi, I am using maven 2.0.9, and everything is working great except for site deployment with webdav. I have not tried any other kind of deployment yet, as I do it manually, so it may not be just site deployment that is not working for me. I have an apache webdav setup in place, and can access it in a browser or in Cadaver via command line. When I execute my maven site:deploy command, I always get a '500 Internal Server Error' with wagon-webdav 1.0-beta-2, and with wagon-webdav 1.0-beta-1 nothing much seems to happen, the process executes successfully, but nothing is copied across. Has anyone successfully deployed with any recent version of maven over webdav? One of the books I have on it suggests using it. I have not seen much on the mailing list though. Thanks in advance for your help. Ross -- View this message in context: http://www.nabble.com/unable-to-deploy-site-with-webdav-tp17276670p23386321.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ Hotmail® goes with you. http://windowslive.com/Tutorial/Hotmail/Mobile?ocid=TXT_TAGLM_WL_HM_Tutorial_Mobile1_052009 -- View this message in context: http://www.nabble.com/unable-to-deploy-site-with-webdav-tp17276670p23387749.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven2 javadoc warnings report
Hi, I'm trying to move from maven 1 to maven 2, but I've noticed that I no longer get the javadoc warnings report generated. Is there any way to get this report from maven 2 (additional plugin perhaps?). Cheers, Joe - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Retrieving current revision from SCM
Hi all, I'm trying to do the following: We're using subversion and we need to extract the revision number of the working copy and put that in a properties file. Is there an existing plugin available to do this? I looked at the documentation for the SCM plugin and it doesn't seem to quite fit the bill in order to do this. Thanks! Allan
Re: Retrieving current revision from SCM
Hi, Have a look here : http://mojo.codehaus.org/buildnumber-maven-plugin/ HTH, -- Olivier 2009/5/5 Allan Ditzel allan.dit...@gmail.com: Hi all, I'm trying to do the following: We're using subversion and we need to extract the revision number of the working copy and put that in a properties file. Is there an existing plugin available to do this? I looked at the documentation for the SCM plugin and it doesn't seem to quite fit the bill in order to do this. Thanks! Allan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: release:perform of an EAR gives error with maven-source-plugin:2.1
On Thursday 30 April 2009 Martin Höller wrote: The question I now have is, why is source:jar mojo executed at all? According to the lifecycle reference [1] this mojo shouldn't be executed (for packaging EAR). How can I deactivate this mojo? The release-profile seems to introduce the m-source-p into my build. Is this a good idea for EAR packaging? EARs usually don't have java files attached. Any thoughts? - martin PS: For the moment I switched back to maven-source-plugin 2.0.4. signature.asc Description: This is a digitally signed message part.
Re: Retrieving current revision from SCM
Thanks Olivier!
That _almost_ does it. If I don't specify format and items then I see
the correct revision printed on screen when the module builds. But I can't
seem to find the right format and items to read the buildNumber in the file.
Here is what I have in my configuration block for the plugin:
format{0,number}/format
itemsitembuildNumber/item/items
And the file output is:
#maven.buildNumber.plugin properties file
#Tue May 05 11:16:55 EDT 2009
buildNumber=1
I know I have to be missing something rather simple here. Any thoughts?
Thanks again!
Allan
On Tue, May 5, 2009 at 10:24 AM, Olivier Lamy ol...@apache.org wrote:
Hi,
Have a look here : http://mojo.codehaus.org/buildnumber-maven-plugin/
HTH,
--
Olivier
2009/5/5 Allan Ditzel allan.dit...@gmail.com:
Hi all,
I'm trying to do the following:
We're using subversion and we need to extract the revision number of the
working copy and put that in a properties file. Is there an existing
plugin
available to do this? I looked at the documentation for the SCM plugin
and
it doesn't seem to quite fit the bill in order to do this.
Thanks!
Allan
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
prevent absolute file path in project assembly
I'm trying to use the assembly plugin with the project descriptorId and when I run this the zip file it creates contains the absolute directory on my file system to the project - in the zip file is c:\an\absolute\path\to\my\project How do I configure the plugin to only have the project directory in the zip file? plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId version2.2-beta-3/version executions execution idcreate-src-distribution/id phasepackage/phase goals goalsingle/goal /goals configuration descriptorRefs descriptorRefproject/descriptorRef /descriptorRefs /configuration /execution /executions /plugin - This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto, including its subsidiaries. The recipient of this e-mail is solely responsible for checking for the presence of Viruses or other Malware. Monsanto, along with its subsidiaries, accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven2 - Where to put script files?
I've put a file in this directory, ran mvn clean install, but the script file isn't copied anywhere in target. What am I supposed to do after adding a file to src/main/scripts? Nick Stolwijk-4 wrote: If you take a look at the superpom [1] you'll see there is a default script directory: scriptSourceDirectorysrc/main/scripts/scriptSourceDirectory So I would say convention over configuration and use that one. (If you'll write a maven plugin to handle the scripts, use the scriptSourceDirectory instead of making your own variable setting. Hth, [1] http://maven.apache.org/guides/introduction/introduction-to-the-pom.html Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl -- View this message in context: http://www.nabble.com/Maven2---Where-to-put-script-files--tp5594755p23389966.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [PLEASE TEST] Maven 2.2.0-RC2
Hey, I had no issue building my projects. release:prepare is working but release:perform is not (see the trace below). I switched to 2.1.0 right after that and the release:perform went well. I'm using the javasvn scm provider here but I get the same error using the native one. /Paul p...@dosadi $ mvn release:perform + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [INFO] Building ekPom [INFO]task-segment: [release:perform] (aggregator-style) [INFO] [INFO] [release:perform] [INFO] Change the default 'svn' provider implementation to 'javasvn'. [INFO] Checking out the project to perform the release ... [INFO] SVN checkout directory: /home/paul/tmp/ekPom/target/checkout [INFO] Executing goals 'deploy'... [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to re-parse additional arguments for Maven invocation. Unrecognized option: -f [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to re-parse additional arguments for Maven invocation. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to
Re: Maven2 - Where to put script files?
To put the files in src/main/scripts is the convention. It is then up to the plugins to do something with them. Which plugin did you expect to take your files? Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Tue, May 5, 2009 at 5:34 PM, Blackbird panzrku...@yahoo.fr wrote: I've put a file in this directory, ran mvn clean install, but the script file isn't copied anywhere in target. What am I supposed to do after adding a file to src/main/scripts? Nick Stolwijk-4 wrote: If you take a look at the superpom [1] you'll see there is a default script directory: scriptSourceDirectorysrc/main/scripts/scriptSourceDirectory So I would say convention over configuration and use that one. (If you'll write a maven plugin to handle the scripts, use the scriptSourceDirectory instead of making your own variable setting. Hth, [1] http://maven.apache.org/guides/introduction/introduction-to-the-pom.html Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl -- View this message in context: http://www.nabble.com/Maven2---Where-to-put-script-files--tp5594755p23389966.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [PLEASE TEST] Maven 2.2.0-RC2
+1. Just noticed the same problem while mvn releasing a multimodule project. The rest is fine (mvn clean deploy is ok). Cheers. 2009/5/5 Paul MERLIN p...@nosphere.org Hey, I had no issue building my projects. release:prepare is working but release:perform is not (see the trace below). I switched to 2.1.0 right after that and the release:perform went well. I'm using the javasvn scm provider here but I get the same error using the native one. /Paul p...@dosadi $ mvn release:perform + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [INFO] Building ekPom [INFO]task-segment: [release:perform] (aggregator-style) [INFO] [INFO] [release:perform] [INFO] Change the default 'svn' provider implementation to 'javasvn'. [INFO] Checking out the project to perform the release ... [INFO] SVN checkout directory: /home/paul/tmp/ekPom/target/checkout [INFO] Executing goals 'deploy'... [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to re-parse additional arguments for Maven invocation. Unrecognized option: -f [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to re-parse additional arguments for Maven invocation. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to re-parse additional arguments for Maven invocation. at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:133) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) ... 16 more Caused by: org.apache.maven.shared.release.ReleaseExecutionException: Failed to re-parse additional arguments for Maven invocation. at org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:89) at org.apache.maven.shared.release.phase.RunPerformGoalsPhase.execute(RunPerformGoalsPhase.java:67) at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:336) at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:282) at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:262) at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:129) ... 18 more Caused by: org.apache.maven.shared.release.exec.MavenExecutorException: Failed to re-parse additional arguments for Maven invocation. at org.apache.maven.shared.release.exec.InvokerMavenExecutor.setupRequest(InvokerMavenExecutor.java:335) at org.apache.maven.shared.release.exec.InvokerMavenExecutor.executeGoals(InvokerMavenExecutor.java:377) at org.apache.maven.shared.release.exec.InvokerMavenExecutor.executeGoals(InvokerMavenExecutor.java:413) at org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:81) ... 23 more Caused
Re: Managing Modified Dependencies
Anders Hammar wrote: In any case, the two important things I think are to keep the original groupId and artifactId I run into the sticky situation that not all of those are known. The person that wrote the previous versions of the poms (that I'm currently renovating) stored everything locally and set all the versions to '1' and the artifact/groupids to something not inline with what is commonly used. How would I discover the needed settings, given just a jar? Anders Hammar wrote: As the initial scenario doesn't mention it, I would like to stress the step of submitting the patch to the owner. This should as least make it feasible to get fixed quickly at the source. In any case, the two important things I think are to keep the original groupId and artifactId (which was NOT the recommended way some time ago), and also to define dependency versions through dependencyManagament (so that there is just one place to change). /Anders On Mon, May 4, 2009 at 19:10, Geoffrey Wiseman geoffrey.wise...@gmail.com wrote: On Mon, May 4, 2009 at 1:01 PM, Nick Stolwijk nick.stolw...@gmail.comwrote: Normally I just check out the source, apply my patches, update the deploymentManament section to point to our inhouse repository, update the version to x.y.z-companyname-1 and do a maven deploy. Then update the documentation to mention which revision you checked out (preferably a tag) and for which issues you have applied a patch, so that the build is reproducible. That'd would be roughly similar to how I would typically handle it. If the changes are significant, I might also check in to local source control. In all scenarios, I'd be hoping to get back on a public version ASAP. - Geoffrey -- Geoffrey Wiseman http://www.geoffreywiseman.ca/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Managing-Modified-Dependencies-tp23371539p23392097.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven and Blaze Advisor?
Is anyone doing anything with Maven and Blaze Advisor? (The company used to be Fair Isaac, now it's FICO.) http://www.fico.com/en/Products/DMTools/Pages/FICO-Blaze-Advisor-System.aspx I'm not that familiar with it, but apparently there is some build time processing to be done, and I just wondered if anyone might know of a plugin hiding somewhere. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Managing Modified Dependencies
If you still have the original jar, you can do an md5sum search on Sonatype Repository [1] or else a classname search on the same repository with one of the original classes. [1] http://repository.sonatype.org/index.html Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Tue, May 5, 2009 at 7:21 PM, daniel.green october...@gmail.com wrote: Anders Hammar wrote: In any case, the two important things I think are to keep the original groupId and artifactId I run into the sticky situation that not all of those are known. The person that wrote the previous versions of the poms (that I'm currently renovating) stored everything locally and set all the versions to '1' and the artifact/groupids to something not inline with what is commonly used. How would I discover the needed settings, given just a jar? Anders Hammar wrote: As the initial scenario doesn't mention it, I would like to stress the step of submitting the patch to the owner. This should as least make it feasible to get fixed quickly at the source. In any case, the two important things I think are to keep the original groupId and artifactId (which was NOT the recommended way some time ago), and also to define dependency versions through dependencyManagament (so that there is just one place to change). /Anders On Mon, May 4, 2009 at 19:10, Geoffrey Wiseman geoffrey.wise...@gmail.com wrote: On Mon, May 4, 2009 at 1:01 PM, Nick Stolwijk nick.stolw...@gmail.comwrote: Normally I just check out the source, apply my patches, update the deploymentManament section to point to our inhouse repository, update the version to x.y.z-companyname-1 and do a maven deploy. Then update the documentation to mention which revision you checked out (preferably a tag) and for which issues you have applied a patch, so that the build is reproducible. That'd would be roughly similar to how I would typically handle it. If the changes are significant, I might also check in to local source control. In all scenarios, I'd be hoping to get back on a public version ASAP. - Geoffrey -- Geoffrey Wiseman http://www.geoffreywiseman.ca/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Managing-Modified-Dependencies-tp23371539p23392097.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: prevent absolute file path in project assembly
There are two other configuration files that you'll want to investigate besides your pom for assemblies. I usually have a /main/assembly directory with a component.xml and then an assembly descriptor file. If you can't get what you need from this URL (http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html ), let me know and I can provide some examples. Mike Corum -Original Message- From: REMIJAN, MICHAEL J [AG/1000] [mailto:michael.j.remi...@monsanto.com] Sent: Tuesday, May 05, 2009 10:12 AM To: Maven Users List Subject: prevent absolute file path in project assembly I'm trying to use the assembly plugin with the project descriptorId and when I run this the zip file it creates contains the absolute directory on my file system to the project - in the zip file is c:\an\absolute\path\to\my\project How do I configure the plugin to only have the project directory in the zip file? plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId version2.2-beta-3/version executions execution idcreate-src-distribution/id phasepackage/phase goals goalsingle/goal /goals configuration descriptorRefs descriptorRefproject/descriptorRef /descriptorRefs /configuration /execution /executions /plugin - This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto, including its subsidiaries. The recipient of this e-mail is solely responsible for checking for the presence of Viruses or other Malware. Monsanto, along with its subsidiaries, accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
site deploy SiteToolException: Error parsing site descriptor
We start getting this error today. Anyone know what causes this error? [INFO] [ERROR] BUILD ERROR [INFO] [INFO] SiteToolException: Error parsing site descriptor Expected root element 'project' but found 'html' (position: START_TAG seen ...html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en lang=en... @7:68) [INFO] [INFO] For more information, run Maven with the -e switch Thanks. LJ
Re: Managing Modified Dependencies
Fantastic! Thank you :-) Strange, I'm using the GNU coreutils md5sum program, but I'm not getting any search results for the checksum... $ md5sum apache/commons-dbcp.jar 590f45b612433a50665bc4f369fc77d0 apache/commons-dbcp.jar I've tried it with others too... Does the filename affect the sum? Nick Stolwijk-4 wrote: If you still have the original jar, you can do an md5sum search on Sonatype Repository [1] or else a classname search on the same repository with one of the original classes. [1] http://repository.sonatype.org/index.html Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Tue, May 5, 2009 at 7:21 PM, daniel.green october...@gmail.com wrote: Anders Hammar wrote: In any case, the two important things I think are to keep the original groupId and artifactId I run into the sticky situation that not all of those are known. The person that wrote the previous versions of the poms (that I'm currently renovating) stored everything locally and set all the versions to '1' and the artifact/groupids to something not inline with what is commonly used. How would I discover the needed settings, given just a jar? Anders Hammar wrote: As the initial scenario doesn't mention it, I would like to stress the step of submitting the patch to the owner. This should as least make it feasible to get fixed quickly at the source. In any case, the two important things I think are to keep the original groupId and artifactId (which was NOT the recommended way some time ago), and also to define dependency versions through dependencyManagament (so that there is just one place to change). /Anders On Mon, May 4, 2009 at 19:10, Geoffrey Wiseman geoffrey.wise...@gmail.com wrote: On Mon, May 4, 2009 at 1:01 PM, Nick Stolwijk nick.stolw...@gmail.comwrote: Normally I just check out the source, apply my patches, update the deploymentManament section to point to our inhouse repository, update the version to x.y.z-companyname-1 and do a maven deploy. Then update the documentation to mention which revision you checked out (preferably a tag) and for which issues you have applied a patch, so that the build is reproducible. That'd would be roughly similar to how I would typically handle it. If the changes are significant, I might also check in to local source control. In all scenarios, I'd be hoping to get back on a public version ASAP. - Geoffrey -- Geoffrey Wiseman http://www.geoffreywiseman.ca/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Managing-Modified-Dependencies-tp23371539p23392097.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Managing-Modified-Dependencies-tp23371539p23394052.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Managing Modified Dependencies
Filename should not affect the checksum. You could take a look at the META-INF directory inside the jar file. Sometimes there is also a version number there. With regards, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Tue, May 5, 2009 at 9:13 PM, daniel.green october...@gmail.com wrote: 590f45b612433a50665bc4f369fc77d0 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: site deploy SiteToolException: Error parsing site descriptor
Take a look at your site descriptor. (src/site/site.xml) It should follow the decorations schema [1] It looks like yours start with html instead of project. [1] http://maven.apache.org/doxia/doxia-sitetools-1.0.x/doxia-decoration-model/decoration.html Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Tue, May 5, 2009 at 9:02 PM, L. J. apache.maill...@gmail.com wrote: Expected root element 'project' but found 'html' - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Retrieving current revision from SCM
I've been using this:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuildnumber-maven-plugin/artifactId
version1.0-beta-1/version
executions
execution
phasevalidate/phase
goals
goalcreate/goal
/goals
/execution
/executions
configuration
doCheckfalse/doCheck
doUpdatefalse/doUpdate
/configuration
/plugin
And in a resource properties file that's filtered:
scm.version=${buildNumber}
On 06/05/2009, at 1:20 AM, Allan Ditzel wrote:
Thanks Olivier!
That _almost_ does it. If I don't specify format and items then
I see
the correct revision printed on screen when the module builds. But I
can't
seem to find the right format and items to read the buildNumber in
the file.
Here is what I have in my configuration block for the plugin:
format{0,number}/format
itemsitembuildNumber/item/items
And the file output is:
#maven.buildNumber.plugin properties file
#Tue May 05 11:16:55 EDT 2009
buildNumber=1
I know I have to be missing something rather simple here. Any
thoughts?
Thanks again!
Allan
On Tue, May 5, 2009 at 10:24 AM, Olivier Lamy ol...@apache.org
wrote:
Hi,
Have a look here : http://mojo.codehaus.org/buildnumber-maven-plugin/
HTH,
--
Olivier
2009/5/5 Allan Ditzel allan.dit...@gmail.com:
Hi all,
I'm trying to do the following:
We're using subversion and we need to extract the revision number
of the
working copy and put that in a properties file. Is there an existing
plugin
available to do this? I looked at the documentation for the SCM
plugin
and
it doesn't seem to quite fit the bill in order to do this.
Thanks!
Allan
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
with regards,
--
Lachlan Deck
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Create dependencies between Maven 2 and JBoss, JBoss-Seam
Hi, I am working on EJB3 with JBoss and also to spread that JBoss-Seam, I am searching solution to solve this situation which create dependencies on JBoss server and JBoss-Seam in order to deploy and run my application with last server. What are there possibility? I hope to obtain help at this situation. Thanks -- View this message in context: http://www.nabble.com/Create-dependencies-between-Maven-2-and-JBoss%2C-JBoss-Seam-tp23396370p23396370.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
test data location question
This is a basic question about how to run Java unit tests that require file names. I use maven to develop a program that reads an input file names from the command line. It's working fine, but now I want to share the code with someone else. The test programs live in ../src/test/java, and the test data lives in ../src/test/data. Until now, I've used fully- qualified paths hard-coded into my test programs, like /Users/siemsen/ TranslateCIM/src/test/data/cim/testArrayTypeOnNonArray/testATONA.mof. If I tar up my development directory and give it to someone else, the fully-qualified paths obviously don't work. I want to make the paths relative somehow. The program reads an input file that may contain include statements that cause the program to open other files relative to the first input file. It seems to my newbie eyes that using resources and getResourceAsStream won't allow me to open subfiles. What I think I want is a runtime environment variable or something that tells me the path to the maven development directory. Any suggestion would be appreciated. -- Pete - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Retrieving current revision from SCM
Allan, In our company we also need to know exact revision number of each file in project. The proposed buildnumber doesn't suit well, we need exactly revision numbers! We have created a custom version of maven-scm-plugin which supports this feature. I am going to commit patch to maven-scm 1.3-SNAPSHOT soon. Andrei Solntsev, Software Developer HireRight Estonia AS -Original Message- From: Allan Ditzel [mailto:allan.dit...@gmail.com] Sent: Tuesday, May 05, 2009 5:12 PM To: users@maven.apache.org Subject: Retrieving current revision from SCM Hi all, I'm trying to do the following: We're using subversion and we need to extract the revision number of the working copy and put that in a properties file. Is there an existing plugin available to do this? I looked at the documentation for the SCM plugin and it doesn't seem to quite fit the bill in order to do this. Thanks! Allan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: test data location question
You should store your files under src/test/resources and load your files using getResourceAsStream Regards Jeff MAURY On Tue, May 5, 2009 at 11:37 PM, Pete Siemsen siem...@ucar.edu wrote: This is a basic question about how to run Java unit tests that require file names. I use maven to develop a program that reads an input file names from the command line. It's working fine, but now I want to share the code with someone else. The test programs live in ../src/test/java, and the test data lives in ../src/test/data. Until now, I've used fully-qualified paths hard-coded into my test programs, like /Users/siemsen/TranslateCIM/src/test/data/cim/testArrayTypeOnNonArray/testATONA.mof. If I tar up my development directory and give it to someone else, the fully-qualified paths obviously don't work. I want to make the paths relative somehow. The program reads an input file that may contain include statements that cause the program to open other files relative to the first input file. It seems to my newbie eyes that using resources and getResourceAsStream won't allow me to open subfiles. What I think I want is a runtime environment variable or something that tells me the path to the maven development directory. Any suggestion would be appreciated. -- Pete - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- La mélancolie c’est communiste Tout le monde y a droit de temps en temps La mélancolie n’est pas capitaliste C’est même gratuit pour les perdants La mélancolie c’est pacifiste On ne lui rentre jamais dedans La mélancolie oh tu sais ça existe Elle se prend même avec des gants La mélancolie c’est pour les syndicalistes Il faut juste sa carte de permanent Miossec (2006) http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.lastfm.fr/listen/user/jeffmaury/personal
mvn classpath weirdness with eclipse plugin
Hi, I've been using mvn for a lot of years now, but I've just encountered a bizarre issue that I have no explanation for. I am having trouble with the following dependencies dependency groupIdaspectj/groupId artifactIdaspectjrt/artifactId version1.5.3/version /dependency dependency groupIdaspectj/groupId artifactIdaspectjweaver/artifactId version1.5.3/version /dependency We are using Archiva -- and these are cached. If I run: $ mvn -X eclipse:eclipse I can see the following in the output: [DEBUG] Adding managed dependencies for com.example:drm [DEBUG] aspectj:aspectjrt:jar:1.5.3 [DEBUG] aspectj:aspectjweaver:jar:1.5.3 The jars are in my local repo. However, these jars are not added to the .classpath file, nor do they show up in Reference Libraries under eclipse. I have verified that this happens on multiple developer machines, so it isn't localized to a single environment. What is even stranger is that if you run the same project with mvn idea:idea, the aspectj jars show up in the classpath for Intellij. I am at a loss. We have no exclusions in the pom. Where should I look next? Thanks in advance, Davis - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Retrieving current revision from SCM
Thanks, everyone! We were finally able to get the resources filtered in our war pom, and the version is now being inserted into a properties file. Thanks again! Allan On Tue, May 5, 2009 at 5:46 PM, Andrei Solntsev asolnt...@hireright.eewrote: Allan, In our company we also need to know exact revision number of each file in project. The proposed buildnumber doesn't suit well, we need exactly revision numbers! We have created a custom version of maven-scm-plugin which supports this feature. I am going to commit patch to maven-scm 1.3-SNAPSHOT soon. Andrei Solntsev, Software Developer HireRight Estonia AS -Original Message- From: Allan Ditzel [mailto:allan.dit...@gmail.com] Sent: Tuesday, May 05, 2009 5:12 PM To: users@maven.apache.org Subject: Retrieving current revision from SCM Hi all, I'm trying to do the following: We're using subversion and we need to extract the revision number of the working copy and put that in a properties file. Is there an existing plugin available to do this? I looked at the documentation for the SCM plugin and it doesn't seem to quite fit the bill in order to do this. Thanks! Allan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [maven-eclipse-plugin] We need your help to test the future 2.7
Anything else? Should we start the release process again then? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Surefire report
Hi all,
I want to build a surefire report test unit and performance, so I config
surefire plugin like this :
[...]
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-report-plugin/artifactId
reportSets
reportSet
idunit/id
configuration
reportsDirectory
${project.build.directory}/surefire-reports/unit
/reportsDirectory
outputNamesurefire-report-unit/outputName
/configuration
reports
reportreport/report
/reports
/reportSet
reportSet
idperf/id
configuration
reportsDirectory
${project.build.directory}/surefire-reports/perf
/reportsDirectory
outputNamesurefire-report-perf/outputName
/configuration
reports
reportreport/report
/reports
/reportSet
/reportSets
/plugin
/plugins
/reporting
[...]
Then I run mvn site command :
[INFO] Generating Surefire Report report.
[INFO] Generating Surefire Report report.
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 15 minutes 45 seconds
[INFO] Finished at: Tue May 05 11:57:25 ICT 2009
[INFO] Final Memory: 66M/127M
[INFO]
Message below said that mvn site generate 2 links for Surefire Report.Whats
this problem??
And when I click both of links ,the result displays :
Surefire Report
Summary
Tests Errors Failures Skipped Success Rate Time
0 0 0 0 0% 0
Note: failures are anticipated and checked for with assertions while errors
are unanticipated.
Thats all I see.No Package List, no Test Cases,...Whats wrong??
Thanks and Regards!
--
View this message in context:
http://www.nabble.com/Surefire-report-tp23398521p23398521.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: unable to deploy site with webdav
500 errors will show up in the Apache error log which might help you nail down the problem. You might also try Maven 2.1.0 and the wagon-webdav-jackrabbit 1.0- beta-5 wagon as an alternative if you are still having problems. Cheers, Brett On 06/05/2009, at 12:00 AM, Michael K. wrote: Hello Martin, I try to upload to the apache-webserver 2.2. I've configured webdav as described in the httpd.conf and the httpd-dav.conf. I tested it via windows web folder and it works fine. Michael mgainty wrote: Ross- which container are you attempting to upload to ? Martin __ Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung / Note de déni et de confidentialité This message is confidential. If you should not be the intended receiver, then we ask politely to report. Each unauthorized forwarding or manufacturing of a copy is inadmissible. This message serves only for the exchange of information and has no legal binding effect. Due to the easy manipulation of emails we cannot take responsibility over the the contents. Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Tue, 5 May 2009 05:16:31 -0700 From: mail4s...@arcor.de To: users@maven.apache.org Subject: Re: unable to deploy site with webdav Hello Ross, I have the same problem as you had. Did you get resolve the problem? I would appreciate your help. Kind regards, Michael rossputin wrote: Hi, I am using maven 2.0.9, and everything is working great except for site deployment with webdav. I have not tried any other kind of deployment yet, as I do it manually, so it may not be just site deployment that is not working for me. I have an apache webdav setup in place, and can access it in a browser or in Cadaver via command line. When I execute my maven site:deploy command, I always get a '500 Internal Server Error' with wagon-webdav 1.0-beta-2, and with wagon-webdav 1.0-beta-1 nothing much seems to happen, the process executes successfully, but nothing is copied across. Has anyone successfully deployed with any recent version of maven over webdav? One of the books I have on it suggests using it. I have not seen much on the mailing list though. Thanks in advance for your help. Ross -- View this message in context: http://www.nabble.com/unable-to-deploy-site-with-webdav-tp17276670p23386321.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ Hotmail® goes with you. http://windowslive.com/Tutorial/Hotmail/Mobile?ocid=TXT_TAGLM_WL_HM_Tutorial_Mobile1_052009 -- View this message in context: http://www.nabble.com/unable-to-deploy-site-with-webdav-tp17276670p23387749.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to use maven to gather all (or some) dependent jar files
Hi, When maven builds a project, it figures out all the dependent jar files, adds them to the classpath, produces the project's jar file under target/. My question is -- is there a way to ask maven also puts all (or some) those dependent jar files under target/ too. The origin of the issue is that we have a project that builds a jar for Mule. However, when deploying this jar file to Mule, we still have to collect all the dependent jar files that Mule does not have and place them under Mule's lib/user/ folder. So every time we upgrade a dependency, for instance, json-lib from 2.2.2 to 2.2.3, we not only have to modify the pom.xml, but also look for json-lib 2.2.3 jar and make sure we upgrade it in lib/user/. Wouldn't it be easier if maven can figure these all out for us since it is all in pom.xml ? Thanks, Steve - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: How to use maven to gather all (or some) dependent jar files
Hi Steve, There is a simple answer: mvn dependency:copy-dependencies Please refer to http://maven.apache.org/plugins/maven-dependency-plugin/ Andrei Solntsev, Software Developer HireRight Estonia AS -Original Message- From: Steve Lihn [mailto:stevel...@gmail.com] Sent: Wednesday, May 06, 2009 6:10 AM To: Maven Users List Subject: How to use maven to gather all (or some) dependent jar files Hi, When maven builds a project, it figures out all the dependent jar files, adds them to the classpath, produces the project's jar file under target/. My question is -- is there a way to ask maven also puts all (or some) those dependent jar files under target/ too. The origin of the issue is that we have a project that builds a jar for Mule. However, when deploying this jar file to Mule, we still have to collect all the dependent jar files that Mule does not have and place them under Mule's lib/user/ folder. So every time we upgrade a dependency, for instance, json-lib from 2.2.2 to 2.2.3, we not only have to modify the pom.xml, but also look for json-lib 2.2.3 jar and make sure we upgrade it in lib/user/. Wouldn't it be easier if maven can figure these all out for us since it is all in pom.xml ? Thanks, Steve - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
deploy:deploy Hangs in Release
While performing a deployment from the release plugin, I see [INFO] [INFO] [install:install] [INFO] [INFO] Installing C:\eclipse-workspaces\...\x.war to C:\...\.m2\repository\com\...\x.war [INFO] [INFO] Installing C:\eclipse-workspaces\...\x-sources.jar to C:\...\.m2\repository\com\x-sources.jar [INFO] [INFO] Installing C:\eclipse-workspaces\...\x.zip to C:\...\x.zip [INFO] [INFO] [deploy:deploy] And that's it. Re-running with -X gives . . . [INFO] [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy' -- [INFO] [DEBUG] (f) artifact = x:war:1.0.4 [INFO] [DEBUG] (f) attachedArtifacts = [com.y:x:java-source:sources:1.0.4, com.y:x:zip:1.0.4] [INFO] [DEBUG] (f) deploymentRepository = Repository[internal|scp://dev-deploy/web-dev-repos/releases] [INFO] [DEBUG] (s) localRepository = Repository[local|file://C:\...\.m2\repository] [INFO] [DEBUG] (f) packaging = war [INFO] [DEBUG] (f) pomFile = C:\eclipse-workspaces\...\x\target\checkout\pom.xml [INFO] [DEBUG] (f) skip = false [INFO] [DEBUG] (f) updateReleaseInfo = true [INFO] [DEBUG] -- end configuration -- [INFO] [INFO] [deploy:deploy] [INFO] [DEBUG] not adding permissions to wagon connection I've recently moved from maven 2.0.8 to 2.1.0 with a completely new local [.m2] repo. Any thoughts? Is the not adding permissions message a clue? Thanks. Brad
Re: Maven password encryption and usage in a CI server
Even removing permissions may not help since anyone that can write a unit test to read that file. If you give Maven access to deploy, you give anyone with access to write code for that project to know the credentials to deploy with. As Brian said the best thing to do here is to use a CI specific account, and I'd add you might restrict requests to deploy to coming from that particular build server's IP. As long as the scope of those credentials is only to deploy snapshots of code then there should be little issue with someone gaining access to them more than committing some arbitrary code to the built tree. Cheers, Brett On 05/05/2009, at 11:16 PM, Brian Fox wrote: You are correct. If someone is able to read the maven code and find the default password, decrypt the master password, then they could decrypt the user password. It's also decrypted on the wire if you aren't using https with your repos. The trick with a build server is to make a special account for that system, the real danger comes when you use a corporate password and someone gets that. If you have real concerns about the build server, don't give people permissions to change the jobs and then it will be harder for them to get at these files. Olivier Dehon wrote: Hi, I was reading about the recent enhancements to the management of server passwords in settings.xml at http://maven.apache.org/guides/mini/guide-encryption.html A few questions arose around the actual security provided by these enhancements in the context of a build/CI server. Agreed, this is an enhancement over passwords in clear text in settings.xml, where any developer can run the help:effective-settings goal in a custom build definition to gain access to the passwords configured there on the server. But can it be considered a safe protection in the context of a build server? For instance, what prevents a developer from running a build definition that runs a command through the exec or antrun plugin that outputs the content of the settings-security.xml, thereby compromising the encryption? Unless I miss the obvious (or the less obvious) I am under the impression that this enhancement makes it harder to get to the passwords, but does not make it impossible (and maybe this was never the goal). Thank you in advance for your insights/pointers. -Olivier - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
