Re: [ANNOUNCEMENT] - WAS6 Maven Plugin 1.0-alpha-2 released
2008/5/7 David J. M. Karlsen [EMAIL PROTECTED]: The WAS6 Maven Plugin team is pleased to announce the was6-maven-plugin-1.0-alpha-2 release! Nice job, but is there a link or something to get the documentation? Thanks Antonio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
release plugin : what's wrong in my release process ?
Hello, I'm planning my release process with help of the release plugin : 1. my project is version N-SNAPSHOT 2. running release:prepare tags my project as version N and commit POM for N+1-SNAPSHOT 3. running release:perform creates the binary distribution from tag 4. I deploy the binary to my validation server and start acceptance testing. If all is OK, I can distribute the release 5. If anything is wrong, running release:rollback reverts to N-SNAPSHOT and I can fix the code and go back to step 1. I just rename the Tag in SVN to N-rcX Looks good to me, but according to the documentation, release:perform removes the release.properties and pom.backup files, so I'll not be able to run the rollback. Any suggestion ? Nicolas.
WAR-Plugin: Manifest and optionaltrue/optional not working :-/
Hello everybody, I am currently having some trouble with the war plugin and could need some help. The issue is about the manifest file and adding the dependent jar to its classpath BUT excluding it from the WEB-INF/lib folder. http://maven.apache.org/plugins/maven-war-plugin/examples/war-manifest-guide.html I already read the war-manifest-guide and set the attribute optionaltrue/optional in the dependency. Having done this, the manifest file is being written absolutely correct. All the jars are being placed into the classpath. But the jars as well are being placed into the WEB-INF/lib folder which I expected not to happen, regarding the three cases at the bottom of the guide. The dependency I use is a pom that wraps all the dependent jars together. dependency groupIdcom.example.eap/groupId artifactIdEAP_3rd-party_Library/artifactId version0.0.1-SNAPSHOT/version typepom/type optionaltrue/optional /dependency The reason why I am doing this is that I have an EAR as the top level artifact that is being created. Within this EAR I have three WARs that all do use the same dependencies and need to share them. That?s why I want to set those jars to optional in the WARs and reinclude them in the EAR. This does all work perfectly fine except that the jars are being placed into the WEB-INF/lib though set to optional in the pom. I already tried to set the dependencie to provided aswell, but this just acted as if I had set only the provided scope. No jars in WEB-INF/lib BUT no Classpath inclusion in manifest file aswell. Does anyone have an idea or suggenstion how I could fix this or what I might be doing wrong? Thank you for any help, Alexander - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Executing only one test with Selenium
Mick Knutson a écrit : Are you using TestNG for your selenium tests, or JUnit? Hello, I'm using JUnit. Thanks, Marc. On Tue, May 6, 2008 at 9:17 AM, Marc Schneider [EMAIL PROTECTED] wrote: Hi, I'd like to run a selenium test but just for one class. Is it possible to do that (without changing the pom.xml) ? Maybe with an argument in the command line ? Thanks, Marc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven ant task, copy local libs
Hey!
Thanks for the help, everything is running fine except one last problem
I guess:
when I deploy the ear file, jboss throws this error:
org.jboss.deployment.DeploymentException: Failed to find module file:
jboss-seam.jar
jboss gets the module defintion from the application.xml file.
The funny thing is, that the jboss-seam.jar is in the ears' lib folder
and has the correct filename (because of the versionmapper).
Thanks again,
Greets
ok, if you don't want to use simple mapper type=flatten /
but prefer the VersionMapper (to remove version from filenames), you need to
add versionsId=dependency.versions to you dependencies task
Hervé
Le lundi 05 mai 2008, roman schoenbichler a écrit :
Hervé BOUTEMY schrieb:
Ok the archives arn't build right, the libs arn't copied into the new
archives
I'm using the following lines:
artifact:dependencies pomRefId=maven.project
filesetId=dependency.fileset useScope=runtime/
copy todir=${war.dir}/WEB-INF/lib
!--fileset dir=${lib.dir}
include name=richfaces-impl*.jar /
include name=richfaces-ui*.jar /
include name=oscache*.jar /
include name=commons-digester.jar /
include name=commons-beanutils.jar /
include name=jsf-facelets.jar /
include name=jboss-seam-*.jar /
exclude name=jboss-seam-gen.jar /
/fileset--
fileset refid=dependency.fileset/
mapper classpathref=maven-ant-tasks.classpath
classname=org.apache.maven.artifact.ant.VersionMapper
from=${dependency.versions} to=flatten /
/copy
notice that the fileset which is commented was the initial ant script,
which copied the libs from the local ./lib folder ...
Am I missing something, or is the code simply wrong..?
Think this would be the last problem!
Thanks,
Greets
yes, with pomRefId, it should work better:
artifact:dependencies pomRefId=maven filesetId=dependency.fileset
useScope=runtime/
Le lundi 05 mai 2008, roman schoenbichler a écrit :
Ok sry.. how should it work with an empty artifact:dependencies So
now he can resolve the dependencies... hope the rest will work..
Greets
Hey again!
Thanks for your reply, this basicly looks like what I need.. but
unfortunately the ant script isn't working. Maybe my Ant knowledge
isn't enough, but I think the documentation got a bit short on this.
Anyway.. my ant file includes
path id=maven-ant-tasks.classpath
path=lib/maven-ant-tasks-2.0.9.jar /
typedef resource=org/apache/maven/artifact/ant/antlib.xml
uri=urn:maven-artifact-ant classpathref=maven-ant-tasks.classpath
/ artifact:pom id=maven file=pom.xml /
and
artifact:dependencies filesetId=dependency.fileset
useScope=runtime/
to which I now refere when copying the libs to the .ear file.
But now ant fails during compilation because it simply can't resolve
any imports pointing to the libs included by maven (the pom).
Hm... I would realy appreciate some help!
Greets
Hi Roman,
If I understand what you're trying to do, I'd say it's the same as
the Declaring Dependencies section of the documentation:
http://maven.apache.org/ant-tasks.html
look at For example, to populate WEB-INF/lib with your dependencies
you could use the following:
If the doc is not clear, don't hesitate to propose other words to
explain the case and open a Jira issue: it's written with best
efforts, we need review and help to improve it. Source is here:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/ant-tasks.a
pt
regards,
Hervé
Le samedi 03 mai 2008, roman schoenbichler a écrit :
Hey Guys!
I'm currently working with seam. They have a project generation
script. This sets up a project, including a build.xml file. The
Problem with this script is, that it copies all libs in the generated
project which is not nice at all.
So I started using maven-ant-tasks.
The problem is, that I wasn't able to figure out how I can copy the
needed lib files to the generated .ear project from my local
repository.
The generated script uses:
fileset id=lib dir=${lib.dir}
include name=*.jar /
/fileset
with lib.dir pointing to ./lib, which of corse is not very usefull
since
my libs are in the .m2 repository.
The description on the website isn't very clear about such functions.
I hope you can help me on that,
Greets
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail:
Re: maven ant task, copy local libs
Hm the last post shouldn't be on this mailing list I guess sry,
but I've one last quesiton.
How can I copy one specific library from my local repository to the ear..?
or better, how can I access one specific lib from my repository..?
I need to unjar one of them, and I need to copy one of them to an extra
location.
Thanks guys!
Greets
Hey!
Thanks for the help, everything is running fine except one last
problem I guess:
when I deploy the ear file, jboss throws this error:
org.jboss.deployment.DeploymentException: Failed to find module file:
jboss-seam.jar
jboss gets the module defintion from the application.xml file.
The funny thing is, that the jboss-seam.jar is in the ears' lib folder
and has the correct filename (because of the versionmapper).
Thanks again,
Greets
ok, if you don't want to use simple mapper type=flatten /
but prefer the VersionMapper (to remove version from filenames), you
need to add versionsId=dependency.versions to you dependencies task
Hervé
Le lundi 05 mai 2008, roman schoenbichler a écrit :
Hervé BOUTEMY schrieb:
Ok the archives arn't build right, the libs arn't copied into the new
archives
I'm using the following lines:
artifact:dependencies pomRefId=maven.project
filesetId=dependency.fileset useScope=runtime/
copy todir=${war.dir}/WEB-INF/lib
!--fileset dir=${lib.dir}
include name=richfaces-impl*.jar /
include name=richfaces-ui*.jar /
include name=oscache*.jar /
include name=commons-digester.jar /
include name=commons-beanutils.jar /
include name=jsf-facelets.jar /
include name=jboss-seam-*.jar /
exclude name=jboss-seam-gen.jar /
/fileset--
fileset refid=dependency.fileset/
mapper classpathref=maven-ant-tasks.classpath
classname=org.apache.maven.artifact.ant.VersionMapper
from=${dependency.versions} to=flatten /
/copy
notice that the fileset which is commented was the initial ant script,
which copied the libs from the local ./lib folder ...
Am I missing something, or is the code simply wrong..?
Think this would be the last problem!
Thanks,
Greets
yes, with pomRefId, it should work better:
artifact:dependencies pomRefId=maven filesetId=dependency.fileset
useScope=runtime/
Le lundi 05 mai 2008, roman schoenbichler a écrit :
Ok sry.. how should it work with an empty
artifact:dependencies So
now he can resolve the dependencies... hope the rest will work..
Greets
Hey again!
Thanks for your reply, this basicly looks like what I need.. but
unfortunately the ant script isn't working. Maybe my Ant knowledge
isn't enough, but I think the documentation got a bit short on this.
Anyway.. my ant file includes
path id=maven-ant-tasks.classpath
path=lib/maven-ant-tasks-2.0.9.jar /
typedef resource=org/apache/maven/artifact/ant/antlib.xml
uri=urn:maven-artifact-ant
classpathref=maven-ant-tasks.classpath
/ artifact:pom id=maven file=pom.xml /
and
artifact:dependencies filesetId=dependency.fileset
useScope=runtime/
to which I now refere when copying the libs to the .ear file.
But now ant fails during compilation because it simply can't resolve
any imports pointing to the libs included by maven (the pom).
Hm... I would realy appreciate some help!
Greets
Hi Roman,
If I understand what you're trying to do, I'd say it's the same as
the Declaring Dependencies section of the documentation:
http://maven.apache.org/ant-tasks.html
look at For example, to populate WEB-INF/lib with your
dependencies
you could use the following:
If the doc is not clear, don't hesitate to propose other words to
explain the case and open a Jira issue: it's written with best
efforts, we need review and help to improve it. Source is here:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/ant-tasks.a
pt
regards,
Hervé
Le samedi 03 mai 2008, roman schoenbichler a écrit :
Hey Guys!
I'm currently working with seam. They have a project generation
script. This sets up a project, including a build.xml file. The
Problem with this script is, that it copies all libs in the
generated
project which is not nice at all.
So I started using maven-ant-tasks.
The problem is, that I wasn't able to figure out how I can copy
the
needed lib files to the generated .ear project from my local
repository.
The generated script uses:
fileset id=lib dir=${lib.dir}
include name=*.jar /
/fileset
with lib.dir pointing to ./lib, which of corse is not very usefull
since
my libs are in the .m2 repository.
The description on the website isn't very clear about such
functions.
I hope you can help me on that,
Greets
-
To unsubscribe, e-mail:
RE: release plugin : what's wrong in my release process ?
--- nicolas de loof [EMAIL PROTECTED] schrieb: Hello, I'm planning my release process with help of the release plugin : 1. my project is version N-SNAPSHOT 2. running release:prepare tags my project as version N and commit POM for N+1-SNAPSHOT 3. running release:perform creates the binary distribution from tag 4. I deploy the binary to my validation server and start acceptance testing. If all is OK, I can distribute the release 5. If anything is wrong, running release:rollback reverts to N-SNAPSHOT and I can fix the code and go back to step 1. I just rename the Tag in SVN to N-rcX Looks good to me, but according to the documentation, release:perform removes the release.properties and pom.backup files, so I'll not be able to run the rollback. Thats because you'll get a release-version (not a snapshot) deployed into your distribution repository after release:perform has been executed successfully. And it is not a good idea to overwrite existing releases as you surely know. Can't you live with 'unused' releases? If the answer is no, then you'll probably have to do the testing with snapshot versions. Or maybe a 'rc' or 'beta' staging solves this management problem. LieGrü, strub Lesen Sie Ihre E-Mails auf dem Handy. www.yahoo.de/go - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WAR-Plugin: Manifest and optionaltrue/optional not working :-/
Are you sure that your IDE has not put the jars in the WEB-INF/lib directory for you? That is the usual reason for this behaviour. Cheers On 07/05/2008, at 6:22 PM, [EMAIL PROTECTED] wrote: Hello everybody, I am currently having some trouble with the war plugin and could need some help. The issue is about the manifest file and adding the dependent jar to its classpath BUT excluding it from the WEB-INF/lib folder. http://maven.apache.org/plugins/maven-war-plugin/examples/war- manifest-guide.html I already read the war-manifest-guide and set the attribute optionaltrue/optional in the dependency. Having done this, the manifest file is being written absolutely correct. All the jars are being placed into the classpath. But the jars as well are being placed into the WEB-INF/lib folder which I expected not to happen, regarding the three cases at the bottom of the guide. The dependency I use is a pom that wraps all the dependent jars together. dependency groupIdcom.example.eap/groupId artifactIdEAP_3rd-party_Library/artifactId version0.0.1-SNAPSHOT/version typepom/type optionaltrue/optional /dependency The reason why I am doing this is that I have an EAR as the top level artifact that is being created. Within this EAR I have three WARs that all do use the same dependencies and need to share them. That?s why I want to set those jars to optional in the WARs and reinclude them in the EAR. This does all work perfectly fine except that the jars are being placed into the WEB-INF/lib though set to optional in the pom. I already tried to set the dependencie to provided aswell, but this just acted as if I had set only the provided scope. No jars in WEB- INF/lib BUT no Classpath inclusion in manifest file aswell. Does anyone have an idea or suggenstion how I could fix this or what I might be doing wrong? Thank you for any help, Alexander - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: release plugin : what's wrong in my release process ?
My release:perform goal is NOT deploy .I don't use a maven repository for delivery, as I build tar.gz and send it to my customer after testing. I also want to test the exact binary that will be delivered, so I CAN't use rc, beta or any other unused release. AFAIK apache releases use a staging repository for pre-release (RC) test versions (see for example http://cwiki.apache.org/GMOxPMGT/geronimo-release-process.html) Please note the manual step 4 : Make a copy of the checked out project in this state in case you need to roll back the release cd .. cp -r trunk trunk-prepared cd trunk Also take a look at the maven release process - it also use a staging repository (http://maven.apache.org/developers/release/releasing.html) but doesn't explain how to rollback if the vote didn't pass. I'm not the only one that expect to rollback to my initial SNAPSHOT trunk after a staging release. What about adding a removeReleaseFiles parameter (default-value=true) to the PerformRelease Mojo ? Or maybe a new release:stage Mojo would be better ? Nicolas. 2008/5/7 Mark Struberg [EMAIL PROTECTED]: --- nicolas de loof [EMAIL PROTECTED] schrieb: Hello, I'm planning my release process with help of the release plugin : 1. my project is version N-SNAPSHOT 2. running release:prepare tags my project as version N and commit POM for N+1-SNAPSHOT 3. running release:perform creates the binary distribution from tag 4. I deploy the binary to my validation server and start acceptance testing. If all is OK, I can distribute the release 5. If anything is wrong, running release:rollback reverts to N-SNAPSHOT and I can fix the code and go back to step 1. I just rename the Tag in SVN to N-rcX Looks good to me, but according to the documentation, release:perform removes the release.properties and pom.backup files, so I'll not be able to run the rollback. Thats because you'll get a release-version (not a snapshot) deployed into your distribution repository after release:perform has been executed successfully. And it is not a good idea to overwrite existing releases as you surely know. Can't you live with 'unused' releases? If the answer is no, then you'll probably have to do the testing with snapshot versions. Or maybe a 'rc' or 'beta' staging solves this management problem. LieGrü, strub Lesen Sie Ihre E-Mails auf dem Handy. www.yahoo.de/go - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
mvn install: add sources
Hi, can I make mvn install to install the sources, too? Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANNOUNCEMENT] - WAS6 Maven Plugin 1.0-alpha-2 released
On Wed, 7 May 2008, Antonio Petrelli wrote: 2008/5/7 David J. M. Karlsen [EMAIL PROTECTED]: The WAS6 Maven Plugin team is pleased to announce the was6-maven-plugin-1.0-alpha-2 release! Nice job, but is there a link or something to get the documentation? oh sorry - I need to config the announcement template. It lives here: http://mojo.codehaus.org/was6-maven-plugin/ -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mvn install: add sources
You need to use the maven assembly plug-in if you want to package and install sources; http://maven.apache.org/plugins/maven-assembly-plugin/ On Wed, May 7, 2008 at 1:13 PM, Jan Torben Heuer [EMAIL PROTECTED] wrote: Hi, can I make mvn install to install the sources, too? Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mvn install: add sources
Hi, Have a look here : http://maven.apache.org/plugins/maven-source-plugin/usage.html -- Olivier 2008/5/7 Jan Torben Heuer [EMAIL PROTECTED]: Hi, can I make mvn install to install the sources, too? Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Executing only one test with Selenium
Hi, I reply to myself : using JUnit you just have to type : mvn -Dtest=MyTestClass Marc. Mick Knutson a écrit : Are you using TestNG for your selenium tests, or JUnit? On Tue, May 6, 2008 at 9:17 AM, Marc Schneider [EMAIL PROTECTED] wrote: Hi, I'd like to run a selenium test but just for one class. Is it possible to do that (without changing the pom.xml) ? Maybe with an argument in the command line ? Thanks, Marc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: mvn install: add sources
yes, use following plugin config : plugin artifactIdmaven-source-plugin/artifactId executions execution idattach-sources/id phaseverify/phase goals goaljar/goal /goals /execution /executions /plugin Kuno -Ursprüngliche Nachricht- Von: news [mailto:[EMAIL PROTECTED] Im Auftrag von Jan Torben Heuer Gesendet: Mittwoch, 7. Mai 2008 13:14 An: users@maven.apache.org Betreff: mvn install: add sources Hi, can I make mvn install to install the sources, too? Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WAR-Plugin: Manifest and optionaltrue/optional not working :-/
G'Day, I'm not sure that you can use a pom dependency this way. I think that you need to specify each dependency (as a jar) separately. Furthermore, I think that you will need to specify them again as additional dependencies in the EAR project. Steve C On 07/05/2008, at 9:39 PM, [EMAIL PROTECTED] wrote: Hi, yes I am totaly sure about that. I do not build within the workspace but in a seperate folder where I checked out the sources with tortoise. The libs are not within the SVN repos. And when building with scope provided, the libs are not within the WEB-INF/lib aswell. regards, Alexander Zitat von Stephen Coy [EMAIL PROTECTED]: Are you sure that your IDE has not put the jars in the WEB-INF/lib directory for you? That is the usual reason for this behaviour. Cheers On 07/05/2008, at 6:22 PM, [EMAIL PROTECTED] wrote: Hello everybody, I am currently having some trouble with the war plugin and could need some help. The issue is about the manifest file and adding the dependent jar to its classpath BUT excluding it from the WEB-INF/lib folder. http://maven.apache.org/plugins/maven-war-plugin/examples/war- manifest-guide.html I already read the war-manifest-guide and set the attribute optionaltrue/optional in the dependency. Having done this, the manifest file is being written absolutely correct. All the jars are being placed into the classpath. But the jars as well are being placed into the WEB-INF/lib folder which I expected not to happen, regarding the three cases at the bottom of the guide. The dependency I use is a pom that wraps all the dependent jars together. dependency groupIdcom.example.eap/groupId artifactIdEAP_3rd-party_Library/artifactId version0.0.1-SNAPSHOT/version typepom/type optionaltrue/optional /dependency The reason why I am doing this is that I have an EAR as the top level artifact that is being created. Within this EAR I have three WARs that all do use the same dependencies and need to share them. That?s why I want to set those jars to optional in the WARs and reinclude them in the EAR. This does all work perfectly fine except that the jars are being placed into the WEB-INF/lib though set to optional in the pom. I already tried to set the dependencie to provided aswell, but this just acted as if I had set only the provided scope. No jars in WEB-INF/lib BUT no Classpath inclusion in manifest file aswell. Does anyone have an idea or suggenstion how I could fix this or what I might be doing wrong? Thank you for any help, Alexander - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: WAR-Plugin: Manifest and optionaltrue/optional not working :-/
Read this: http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html [EMAIL PROTECTED] wrote: Hello everybody, I am currently having some trouble with the war plugin and could need some help. The issue is about the manifest file and adding the dependent jar to its classpath BUT excluding it from the WEB-INF/lib folder. http://maven.apache.org/plugins/maven-war-plugin/examples/war- manifest-guide.html I already read the war-manifest-guide and set the attribute optionaltrue/optional in the dependency. Having done this, the manifest file is being written absolutely correct. All the jars are being placed into the classpath. But the jars as well are being placed into the WEB-INF/lib folder which I expected not to happen, regarding the three cases at the bottom of the guide. The dependency I use is a pom that wraps all the dependent jars together. dependency groupIdcom.example.eap/groupId artifactIdEAP_3rd-party_Library/artifactId version0.0.1-SNAPSHOT/version typepom/type optionaltrue/optional /dependency The reason why I am doing this is that I have an EAR as the top level artifact that is being created. Within this EAR I have three WARs that all do use the same dependencies and need to share them. That?s why I want to set those jars to optional in the WARs and reinclude them in the EAR. This does all work perfectly fine except that the jars are being placed into the WEB-INF/lib though set to optional in the pom. I already tried to set the dependencie to provided aswell, but this just acted as if I had set only the provided scope. No jars in WEB-INF/lib BUT no Classpath inclusion in manifest file aswell. Does anyone have an idea or suggenstion how I could fix this or what I might be doing wrong? Thank you for any help, Alexander - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven.repo.local, again
Yes! This property reflects ${maven.repo.local} when I pass
-Dmaven.repo.local=...,
and returns ~/.m2/repository if I do not. Exactly what I needed.
I was under the false impression that one had to define it in ~/.m2/settings.xml
in order to use it.
thanks -
-Russ
% mvn -Dmaven.repo.local=/tmp/foo validate
[INFO] Scanning for projects...
[INFO]
[INFO] Building Unnamed - foogroup:foo:jar:1.0
[INFO]task-segment: [validate]
[INFO]
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[echo] local repo=/tmp/foo
[INFO] Executed tasks
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Wed May 07 07:03:05 PDT 2008
[INFO] Final Memory: 3M/31M
[INFO]
% mvn validate
[INFO] Scanning for projects...
[INFO]
[INFO] Building Unnamed - foogroup:foo:jar:1.0
[INFO]task-segment: [validate]
[INFO]
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[echo] local repo=/export/home/testuser/.m2/repository
[INFO] Executed tasks
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Wed May 07 07:03:15 PDT 2008
[INFO] Final Memory: 3M/31M
[INFO]
% cat pom.xml
project
modelVersion4.0.0/modelVersion
groupIdfoogroup/groupId
artifactIdfoo/artifactId
version1.0/version
build
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phasevalidate/phase
goalsgoalrun/goal/goals
configuration
tasksecho message=local
repo=${settings.localRepository} //tasks
/configuration
/execution
/executions
/plugin
/plugins
/build
/project
% mvn --version
Maven version: 2.0.5
At 3:27 PM -0400 5/6/08, Brian E. Fox wrote:
${settings.localRepository} should work IIRC.
-Original Message-
From: Brewster, Richard [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 06, 2008 9:57 AM
To: Maven Users List
Subject: RE: maven.repo.local, again
Does Maven provide a property with the path to the local repo? I think
the answer is 'no'. I define a real property in my settings.xml,
redundantly with localRepository.
localRepositoryc:/m2/repository/localRepository
profile
idmy-profile/id
activation
activeByDefaulttrue/activeByDefault
/activation
properties
local.repositoryc:/m2/repository/local.repository
/properties
...
localRepository tells Maven where the repo is, but it is NOT a
property. You can access it like a property with ${localRepository},
but this does not resolve to the value you expect.
Richard Brewster
Senior Associate
Perrin Quarles Associates
[EMAIL PROTECTED]
(434) 817-2640
-Original Message-
From: Beelen, M. - SPLXL [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 06, 2008 3:42 AM
To: Maven Users List
Subject: RE: maven.repo.local, again
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, May 05, 2008 6:59 PM
To: users@maven.apache.org
Subject: maven.repo.local, again
Is there any property set by maven that tells me where the local build
repository is?
I.e., once it resolves where it is going to build, will it tell me?
I think the answer is just plain no, but I want to re-confirm.
tia,
-Russ
-
Hello Russ,
You local repository is in %USER_HOME%\.m2\repository unless your
specified otherwise in your settings.xml (located in %USER_HOME%\.m2) or
your maven config (settings.xml in %MAVEN_HOME%\conf)
When I run mvn install near the end the output shows:
[INFO] [jar:jar]
[INFO] Building jar:
%PROJECT_HOME%\target\${artifactId}-${pom-version}.jar
[INFO] [install:install]
[INFO] Installing %PROJECT_HOME%\target\${artifactId}-${pom-version}.jar
to
%LOCAL_M2_REPO%\${groupId}\${artifactId}\${pom-version}\${artifactId}-${
pom-version}.jar
[INFO]
[INFO] BUILD SUCCESSFUL
It doesn't set any environment settings, which
Re: problem using the buildnumber plugin with maven
You need to bind the execution of the buildnumber:create mojo to a
Maven phase prior to install, eg compile.
Wayne
On Tue, May 6, 2008 at 3:08 AM, Niranjan Deshpande
[EMAIL PROTECTED] wrote:
Hi all
I am using the buildnumber plugin in my pom. details of the plugin are here
http://mojo.codehaus.org/buildnumber-maven-plugin/index.html
http://www.mail-archive.com/users@maven.apache.org/msg60497.html
I have configured the plugin under the
build
pluginManagement tags
While taing the build i run this command:
*mvn buildnumber:create install*
The war file generated has name application_Name-Build-r2008-05-05.war
This name is a result of the finalName tag, in the POM:
*
finalName${project.artifactId}-${project.version}-r${buildNumber}/finalName
*
But when I run
*mvn install*
**
war file that is added to the maven local repository is
application_Name-Build.war, without the timestamp.
This is recult of the version tag in the POM
versionBuild/version
1.How do i make the intall task, aware of the plugin, and make it run only
after the plugin has been executed.
2. During war creation, build is tagged using the finalName element, but
during installation, its tagged using the version element.
I want it to be tagged using the finalName element in both cases. Is htere a
way to do so?
Please help me.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: problem using the buildnumber plugin with maven
execution
phase*compile*/phase
goals
goalcreate/goal
/goals
/execution
You mean to say I should do as above for hte mojo? I tried even that. but
you know what the mojo never runs unless u reun it explicitly as
*mvn buildnumber:create install*
*So the problem still remains: How do I make my install goal, aware of the
build number plugin?*
On 5/7/08, Wayne Fay [EMAIL PROTECTED] wrote:
You need to bind the execution of the buildnumber:create mojo to a
Maven phase prior to install, eg compile.
Wayne
On Tue, May 6, 2008 at 3:08 AM, Niranjan Deshpande
[EMAIL PROTECTED] wrote:
Hi all
I am using the buildnumber plugin in my pom. details of the plugin are
here
http://mojo.codehaus.org/buildnumber-maven-plugin/index.html
http://www.mail-archive.com/users@maven.apache.org/msg60497.html
I have configured the plugin under the
build
pluginManagement tags
While taing the build i run this command:
*mvn buildnumber:create install*
The war file generated has name application_Name-Build-r2008-05-05.war
This name is a result of the finalName tag, in the POM:
*
finalName${project.artifactId}-${project.version}-r${buildNumber}/finalName
*
But when I run
*mvn install*
**
war file that is added to the maven local repository is
application_Name-Build.war, without the timestamp.
This is recult of the version tag in the POM
versionBuild/version
1.How do i make the intall task, aware of the plugin, and make it run
only
after the plugin has been executed.
2. During war creation, build is tagged using the finalName element,
but
during installation, its tagged using the version element.
I want it to be tagged using the finalName element in both cases. Is
htere a
way to do so?
Please help me.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Regards,
Niranjan Deshpande
Shut yourself from the world and create the reality you want
Re: problem using the buildnumber plugin with maven
On Tue, May 6, 2008 at 1:08 AM, Niranjan Deshpande
[EMAIL PROTECTED] wrote:
The war file generated has name application_Name-Build-r2008-05-05.war
This name is a result of the finalName tag, in the POM:
*
finalName${project.artifactId}-${project.version}-r${buildNumber}/finalName
*
But when I run
*mvn install*
**
war file that is added to the maven local repository is
application_Name-Build.war, without the timestamp.
That's always going to be the case. The finalName only affects the
filename you see in the target directory. In the local and remote
repos, it will always be just $artifactId-$version.
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: problem using the buildnumber plugin with maven
Yeah, that was my conclusion too. Its surprising that maven developers
havent made it changeable at run itme. everytim a new build is taken, u go
and edit the pom's version.
On 5/7/08, Wendy Smoak [EMAIL PROTECTED] wrote:
On Tue, May 6, 2008 at 1:08 AM, Niranjan Deshpande
[EMAIL PROTECTED] wrote:
The war file generated has name application_Name-Build-r2008-05-05.war
This name is a result of the finalName tag, in the POM:
*
finalName${project.artifactId}-${project.version}-r${buildNumber}/finalName
*
But when I run
*mvn install*
**
war file that is added to the maven local repository is
application_Name-Build.war, without the timestamp.
That's always going to be the case. The finalName only affects the
filename you see in the target directory. In the local and remote
repos, it will always be just $artifactId-$version.
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Regards,
Niranjan Deshpande
Shut yourself from the world and create the reality you want
Re: problem using the buildnumber plugin with maven
Sorry, I didn't intend to mislead you. I was only trying to address
part of your question, the how do I get buildnumber to put its number
in my artifact's name during the build part, not the how do I get
that artifact installed with that same name which, as Wendy says, is
not possible.
Artifacts always go into the local repo cache using the groupId,
artifactId, and version you have declared in the pom -- it completely
ignores the finalName.
finalName is only useful for changing the name of a war/ear and then
pulling it out of /target to use it for something else directly.
Wayne
On Wed, May 7, 2008 at 9:27 AM, Niranjan Deshpande
[EMAIL PROTECTED] wrote:
Yeah, that was my conclusion too. Its surprising that maven developers
havent made it changeable at run itme. everytim a new build is taken, u go
and edit the pom's version.
On 5/7/08, Wendy Smoak [EMAIL PROTECTED] wrote:
On Tue, May 6, 2008 at 1:08 AM, Niranjan Deshpande
[EMAIL PROTECTED] wrote:
The war file generated has name application_Name-Build-r2008-05-05.war
This name is a result of the finalName tag, in the POM:
*
finalName${project.artifactId}-${project.version}-r${buildNumber}/finalName
*
But when I run
*mvn install*
**
war file that is added to the maven local repository is
application_Name-Build.war, without the timestamp.
That's always going to be the case. The finalName only affects the
filename you see in the target directory. In the local and remote
repos, it will always be just $artifactId-$version.
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Regards,
Niranjan Deshpande
Shut yourself from the world and create the reality you want
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Maven 2.0.7 and relativePath/
Hi all,
I did not find a good explanation about the usage of relativePath/ in the
net. I am interested if I have e.g.:
parent
groupIdcom.mycomp/groupId
artifactIdmycomp-parent-pom/artifactId
version${mycomp.version}/version
relativePath../../parent-pom/pom.xml/relativePath
/parent
If the relativePath will be checked first and then the repositories?
Currently I can see into the logs that Maven tries to download the artifact
from the repository, but there is no an artifact with version
${mycomp.version}. I am expecting that Maven should try the relative path?
Thank you in advance.
Regards, Dobri
Re: release plugin : what's wrong in my release process ?
I've created MRELEASE-341 and committed the associated release:stage Mojo please review. 2008/5/7 nicolas de loof [EMAIL PROTECTED]: My release:perform goal is NOT deploy .I don't use a maven repository for delivery, as I build tar.gz and send it to my customer after testing. I also want to test the exact binary that will be delivered, so I CAN't use rc, beta or any other unused release. AFAIK apache releases use a staging repository for pre-release (RC) test versions (see for example http://cwiki.apache.org/GMOxPMGT/geronimo-release-process.html) Please note the manual step 4 : Make a copy of the checked out project in this state in case you need to roll back the release cd .. cp -r trunk trunk-prepared cd trunk Also take a look at the maven release process - it also use a staging repository (http://maven.apache.org/developers/release/releasing.html) but doesn't explain how to rollback if the vote didn't pass. I'm not the only one that expect to rollback to my initial SNAPSHOT trunk after a staging release. What about adding a removeReleaseFiles parameter (default-value=true) to the PerformRelease Mojo ? Or maybe a new release:stage Mojo would be better ? Nicolas. 2008/5/7 Mark Struberg [EMAIL PROTECTED]: --- nicolas de loof [EMAIL PROTECTED] schrieb: Hello, I'm planning my release process with help of the release plugin : 1. my project is version N-SNAPSHOT 2. running release:prepare tags my project as version N and commit POM for N+1-SNAPSHOT 3. running release:perform creates the binary distribution from tag 4. I deploy the binary to my validation server and start acceptance testing. If all is OK, I can distribute the release 5. If anything is wrong, running release:rollback reverts to N-SNAPSHOT and I can fix the code and go back to step 1. I just rename the Tag in SVN to N-rcX Looks good to me, but according to the documentation, release:perform removes the release.properties and pom.backup files, so I'll not be able to run the rollback. Thats because you'll get a release-version (not a snapshot) deployed into your distribution repository after release:perform has been executed successfully. And it is not a good idea to overwrite existing releases as you surely know. Can't you live with 'unused' releases? If the answer is no, then you'll probably have to do the testing with snapshot versions. Or maybe a 'rc' or 'beta' staging solves this management problem. LieGrü, strub Lesen Sie Ihre E-Mails auf dem Handy. www.yahoo.de/go - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Exception in Javadoc plugin (v2.4)
javadoc 2.4 gives the same error Any other ideas? I'm using ubuntu 8.04 with sun jdk 1.6.0u6. The same command (with the same project) works on other computers (windows), as well as my previous ubuntu 7.10. Brian E Fox wrote: Try using javadoc 2.4...the logs show you're using 2.3: Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the mojo 'org.apache.maven.plugins:maven-javadoc-plugin:2.3:javadoc' in the plugin 'org.apache.maven.plugins:maven-javadoc-plugin' -Original Message- From: Arik Kfir [mailto:[EMAIL PROTECTED] Sent: Sunday, April 27, 2008 1:27 PM To: users@maven.apache.org Subject: [m2] Exception in Javadoc plugin (v2.4) Hi all, Has anyone encountered this error? (see below) The project is a POM designated as a parent POM for the other modules which are parallel to it. It does not extend any other parent and Maven is run from within its directory (in other words, no aggregation and no inheritance) Here's the execution (it's run with -X -e, so jump to the end to see the actual exception): [EMAIL PROTECTED]:~/Work/projects/parent$ mvn javadoc:javadoc -X -e + Error stacktraces are turned on. Maven version: 2.0.9 Java version: 1.6.0_06 OS name: linux version: 2.6.24-16-generic arch: i386 Family: unix [DEBUG] Building Maven user-level plugin registry from: '/home/arik/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/home/arik/Work/tools/apache-maven-2.0.9/conf/plugin-registry.xml' [INFO] Scanning for projects... [DEBUG] Adding managed dependencies for com.infolinks:infolinks-parent [DEBUG] com.thoughtworks.xstream:xstream:jar:1.2.2 [DEBUG] commons-codec:commons-codec:jar:1.3 [DEBUG] commons-beanutils:commons-beanutils:jar:1.7.0 [DEBUG] commons-cli:commons-cli:jar:1.1 [DEBUG] commons-collections:commons-collections:jar:3.2 [DEBUG] commons-digester:commons-digester:jar:1.8 [DEBUG] commons-dbcp:commons-dbcp:jar:1.2.1 [DEBUG] commons-el:commons-el:jar:1.0 [DEBUG] commons-fileupload:commons-fileupload:jar:1.2 [DEBUG] commons-httpclient:commons-httpclient:jar:3.1 [DEBUG] commons-io:commons-io:jar:1.3.1 [DEBUG] commons-lang:commons-lang:jar:2.3 [DEBUG] commons-pool:commons-pool:jar:1.3 [DEBUG] commons-validator:commons-validator:jar:1.3.1 [DEBUG] org.apache.velocity:velocity:jar:1.5 [DEBUG] org.apache.velocity:velocity-tools:jar:1.3 [DEBUG] commons-logging:commons-logging:jar:1.1 [DEBUG] org.slf4j:slf4j-api:jar:1.4.3 [DEBUG] org.slf4j:log4j-over-slf4j:jar:1.4.3 [DEBUG] org.slf4j:jcl104-over-slf4j:jar:1.4.3 [DEBUG] ch.qos.logback:logback-classic:jar:0.9.8 [DEBUG] org.slf4j:slf4j-jdk14:jar:1.4.3 [DEBUG] org.codehaus.groovy:groovy:jar:1.5.4 [DEBUG] javax.activation:activation:jar:1.1 [DEBUG] javax.transaction:jta:jar:1.1 [DEBUG] javax.mail:mail:jar:1.4 [DEBUG] javax.persistence:persistence-api:jar:1.0 [DEBUG] javax.servlet:servlet-api:jar:2.5 [DEBUG] javax.servlet.jsp:jsp-api:jar:2.1 [DEBUG] javax.servlet:jstl:jar:1.1.2 [DEBUG] taglibs:standard:jar:1.1.2 [DEBUG] opensymphony:sitemesh:jar:2.3 [DEBUG] org.mortbay.jetty:jetty:jar:6.1.5 [DEBUG] org.mortbay.jetty:jetty-ajp:jar:6.1.5 [DEBUG] org.mortbay.jetty:jetty-ajp:jar:6.1.5 [DEBUG] org.mortbay.jetty:jetty-plus:jar:6.1.5 [DEBUG] org.mortbay.jetty:jetty-management:jar:6.1.5 [DEBUG] org.mortbay.jetty:jetty-java5-threadpool:jar:6.1.5 [DEBUG] org.mortbay.jetty:servlet-api-2.5:jar:6.1.5 [DEBUG] org.mortbay.jetty:jsp-api-2.1:jar:6.1.5 [DEBUG] org.mortbay.jetty:jsp-2.1:jar:6.1.5 [DEBUG] org.hibernate:hibernate:jar:3.2.4.sp1 [DEBUG] org.hibernate:hibernate-annotations:jar:3.3.0.ga [DEBUG] org.hibernate:hibernate-commons-annotations:jar:3.3.0.ga [DEBUG] org.hibernate:hibernate-entitymanager:jar:3.3.1.ga [DEBUG] net.sf.ehcache:ehcache:jar:1.3.0 [DEBUG] org.springframework:spring:jar:2.5.3 [DEBUG] org.springframework:spring-webmvc:jar:2.5.3 [DEBUG] org.springframework:spring-test:jar:2.5.3:test [DEBUG] org.codehaus.mvel:mvel:jar:1.2.15.java6 [DEBUG] hsqldb:hsqldb:jar:1.8.0.7 [DEBUG] mysql:mysql-connector-java:jar:5.0.5 [DEBUG] org.tmatesoft.svnkit:svnkit:jar:1.1.4 [DEBUG] ch.ethz.ganymed:ganymed-ssh2:jar:build210 [DEBUG] concurrent:concurrent:jar:1.3.4 [DEBUG] oro:oro:jar:2.0.8 [DEBUG] jdom:jdom:jar:1.0 [DEBUG] org.htmlparser:htmlparser:jar:1.6 [DEBUG] opensymphony:quartz-all:jar:1.6.0 [DEBUG] cglib:cglib-nodep:jar:2.1_3 [DEBUG] asm:asm:jar:2.2.3 [DEBUG] asm:asm-analysis:jar:2.2.3 [DEBUG] asm:asm-attrs:jar:2.2.3 [DEBUG] asm:asm-commons:jar:2.2.3 [DEBUG] asm:asm-tree:jar:2.2.3 [DEBUG] asm:asm-util:jar:2.2.3 [DEBUG] asm:asm-xml:jar:2.2.3 [DEBUG] asm:asm-all:jar:2.2.3 [DEBUG] junit:junit:jar:4.4 [DEBUG] org.easymock:easymock:jar:2.3:test [DEBUG] org.easymock:easymockclassextension:jar:2.3:test [INFO] Searching repository for plugin with prefix:
RE: Can't run ant task in maven 2.0.9
Since this is a regression, we will fix it for 2.0.10, can you write a jira and
attach a sample project?
-Original Message-
From: Matt Milliss [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 06, 2008 8:13 PM
To: users@maven.apache.org
Subject: Re: Can't run ant task in maven 2.0.9
The problem only happens with maven 2.0.9. If I rollback maven to 2.0.8
it works fine with ant tasks 2.0.9. And maven 2.0.9 still doesn't work
with ant tasks 2.0.8. The maven antun plugin version is 1.1. I even
tried rolling ant back to 1.6.5 as I noticed that the antrun plugin has
a dependency on 1.6.5 and this didn't fix the problem either.
Regards
Matt
Hervé BOUTEMY wrote:
and give the exact version of the maven-antrun-plugin used
Le dimanche 04 mai 2008, Brian E. Fox a écrit :
Can you try to isolate this to the Ant task or Maven update? Ie don't
update them both at the same time and see which one actually causes the
breakage.
-Original Message-
From: Matthew Milliss [mailto:[EMAIL PROTECTED]
Sent: Sunday, May 04, 2008 5:14 AM
To: users@maven.apache.org
Subject: Can't run ant task in maven 2.0.9
I've just installed maven 2.0.9 and added the 2.0.9 Maven tasks for ant
into my ant install lib directory (ant 1.7) and now when I run my antrun
plugin it fails with the message:
Embedded error: The following error occurred while executing this line:
/home/development/workspace/backoffice/run-fit.xml:5: Could not create
task or type of type: antlib:org.apache.maven.artifact.ant:dependencies.
I didn't have this issue with maven 2.0.7 or 2.0.8 with either ant 1.6.5
or 1.7. Has anybody experienced this issue and know what the problem is?
here is the antrun config in my pom:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idTests Run by Ant/id
phasetest/phase
goals
goalrun/goal
/goals
configuration
tasks
ant antfile=${basedir}/run-fit.xml
dir=${basedir} inheritRefs=true /
/tasks
/configuration
/execution
/executions
/plugin
and the ant build file:
?xml version=1.0?
project name=run-fit default=run-tests
xmlns:artifact=antlib:org.apache.maven.artifact.ant
target name=setup
artifact:dependencies filesetId=aspectjweaver.fileset
dependency groupId=aspectj artifactId=aspectjweaver
version=1.5.3 /
/artifact:dependencies
/target
target name=run-tests depends=setup
echo message=I don't work /
/target
/project
os
fedora core 6 version 2.6.22.14-72.fc6
java version 1.6.0_04
Java(TM) SE Runtime Environment (build 1.6.0_04-b12)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing)
Cheers
Matt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
maven-default-skin artifact is failing our builds
[INFO] artifact org.apache.maven.skins:maven-default-skin: checking for updates from central [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '7f1b64b38fb9268def21e3808c0d44 8146d7bf37'; remote = 'fa58f552f7b0d2d697f7b006e4b007996bcbaae1' - RETRYING [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '7f1b64b38fb9268def21e3808c0d44 8146d7bf37'; remote = 'fa58f552f7b0d2d697f7b006e4b007996bcbaae1' - IGNORING [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] The skin does not exist: Unable to determine the release version This just started happening in multiple environments for our project. Maven 2.0.9 is in use. Any idea what's happening? We are using Artifactory as the company repo server. Richard Brewster Senior Associate Perrin Quarles Associates [EMAIL PROTECTED] (434) 817-2640
RE: Maven 2.0.7 and relativePath/
The relative path is used when building a child module to find the
parent. By default it looks in ../pom.xml but you can change this. If
the matching parent is not found on disk, it will be retrieved from the
repository.
You should not have properties in the g/a/v of either the parent section
or the primary declaration of an artifact (project.group...etc) as this
will surely cause you lots of headaches.
-Original Message-
From: Dobri Kitipov [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 07, 2008 7:50 AM
To: users@maven.apache.org
Subject: Maven 2.0.7 and relativePath/
Hi all,
I did not find a good explanation about the usage of relativePath/ in
the
net. I am interested if I have e.g.:
parent
groupIdcom.mycomp/groupId
artifactIdmycomp-parent-pom/artifactId
version${mycomp.version}/version
relativePath../../parent-pom/pom.xml/relativePath
/parent
If the relativePath will be checked first and then the repositories?
Currently I can see into the logs that Maven tries to download the
artifact
from the repository, but there is no an artifact with version
${mycomp.version}. I am expecting that Maven should try the relative
path?
Thank you in advance.
Regards, Dobri
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven-default-skin artifact is failing our builds
More information: This happens only with the site goal. Richard Brewster Senior Associate Perrin Quarles Associates [EMAIL PROTECTED] (434) 817-2640 -Original Message- From: Brewster, Richard [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 12:50 PM To: Maven Users List Subject: maven-default-skin artifact is failing our builds [INFO] artifact org.apache.maven.skins:maven-default-skin: checking for updates from central [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '7f1b64b38fb9268def21e3808c0d44 8146d7bf37'; remote = 'fa58f552f7b0d2d697f7b006e4b007996bcbaae1' - RETRYING [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '7f1b64b38fb9268def21e3808c0d44 8146d7bf37'; remote = 'fa58f552f7b0d2d697f7b006e4b007996bcbaae1' - IGNORING [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] The skin does not exist: Unable to determine the release version This just started happening in multiple environments for our project. Maven 2.0.9 is in use. Any idea what's happening? We are using Artifactory as the company repo server. Richard Brewster Senior Associate Perrin Quarles Associates [EMAIL PROTECTED] (434) 817-2640 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: *** Parse error reading POM ***
Hi,
The variable is buildNumber not timestamp which the value you gave to
buildNumber.
I use 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
format{0,date,MMdd-HHmmss}/format
items
itemtimestamp/item
/items
doCheckfalse/doCheck
doUpdatefalse/doUpdate
/configuration
/plugin
Then, I use ${buildNumber} in manifest files only, not to change the artifact name but you can use
something like this :
finalName${pom.artifactId}-${pom.version}-r${buildNumber}/finalName
Cheers,
Julien
RockRider a écrit :
Hi Julien ,
I have installed the plugin's jar file using the maven install install file
command
the plugin xml fragment, i have added to pom, under the pluginManagement
tag.
I am trying to access the timestaamp property as:
version${timestamp}/version, this is at the top of the xml, where in we
give projects group id, artifact id, description.
but the build generated is generated as applicationName-${timestamp}.
so the pom is not resolving the refernce to the timestamp variable generated
by the plugin.
As per this link
http://mojo.codehaus.org/buildnumber-maven-plugin/plugin-info.html
the ${timstamp} should work.
How may I debug this?
May I know how you are using the timstamp variable in ur pom?
Please let me know.
Julien CARSIQUE wrote:
RockRider a écrit :
As per my understanding, the artifactId is nothing but a directory name.
correct?
I am using the same name for the artifactid as well as directory where
the
plugin classes are present
makes snese??
No. Module is a directory name. ArtifactId is the artifactId given to the
artifact in its pom.xml
(in your case, the plugin's artifactId).
Directory where plugin classes are present? You do not need to manually
download the plugin, it's
done by maven (with the correct groupId, artifactId, etc.).
--
Julien CARSIQUE, Nuxeo (Paris, France)
www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
[EMAIL PROTECTED] | Tel: +33 1 40 33 79 87
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Julien CARSIQUE, Nuxeo (Paris, France)
www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
[EMAIL PROTECTED] | Tel: +33 1 40 33 79 87
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: *** Parse error reading POM ***
Hi Julien,
Well, I got that by accident :). The plugin's working now. :). But it runs
only if i run this command:
mvn buildnumber:create install (adding the create goal explicitly in the
command line)
logically, the plugin should run on it's own, if its bound to the install
phase as i did:
..
..
phasevalidate/phase
goals
goalcreate/goal
/goals
/execution
.
Julien CARSIQUE wrote:
Hi,
The variable is buildNumber not timestamp which the value you gave to
buildNumber.
I use 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
format{0,date,MMdd-HHmmss}/format
items
itemtimestamp/item
/items
doCheckfalse/doCheck
doUpdatefalse/doUpdate
/configuration
/plugin
Then, I use ${buildNumber} in manifest files only, not to change the
artifact name but you can use
something like this :
finalName${pom.artifactId}-${pom.version}-r${buildNumber}/finalName
Cheers,
Julien
RockRider a écrit :
Hi Julien ,
I have installed the plugin's jar file using the maven install install
file
command
the plugin xml fragment, i have added to pom, under the
pluginManagement
tag.
I am trying to access the timestaamp property as:
version${timestamp}/version, this is at the top of the xml, where in
we
give projects group id, artifact id, description.
but the build generated is generated as applicationName-${timestamp}.
so the pom is not resolving the refernce to the timestamp variable
generated
by the plugin.
As per this link
http://mojo.codehaus.org/buildnumber-maven-plugin/plugin-info.html
the ${timstamp} should work.
How may I debug this?
May I know how you are using the timstamp variable in ur pom?
Please let me know.
Julien CARSIQUE wrote:
RockRider a écrit :
As per my understanding, the artifactId is nothing but a directory
name.
correct?
I am using the same name for the artifactid as well as directory where
the
plugin classes are present
makes snese??
No. Module is a directory name. ArtifactId is the artifactId given to
the
artifact in its pom.xml
(in your case, the plugin's artifactId).
Directory where plugin classes are present? You do not need to manually
download the plugin, it's
done by maven (with the correct groupId, artifactId, etc.).
--
Julien CARSIQUE, Nuxeo (Paris, France)
www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
[EMAIL PROTECTED] | Tel: +33 1 40 33 79 87
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Julien CARSIQUE, Nuxeo (Paris, France)
www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
[EMAIL PROTECTED] | Tel: +33 1 40 33 79 87
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/***-Parse-error-reading-POM-***-tp17019499p17111002.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] New version (3.1) of Maven support for NetBeans IDE
The Mevenide team is proud to present new version (3.1) of Maven support for NetBeans 6.0 and 6.1. This new major release includes: * Updated maven embedder binaries * Local and remote repository indexing, including browsing and searching your artifacts. * Web frameworks support * Profiles support (aka configurations) for project loading and executing * Improved pom xml editor features Check the project website [1] and article at NetBeans.org [2] for description of these and more features in detail. The easiest way to install the new version is to start up NetBeans and the use Plugins dialog to download and install the binaries from NetBeans Update Center. Enjoy. The Mevenide team [1] http://mevenide.codehaus.org/m2-site [2] http://wiki.netbeans.org/MavenBestPractices - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven ant task, copy local libs
Le mercredi 07 mai 2008, roman schoenbichler a écrit :
Hm the last post shouldn't be on this mailing list I guess sry,
but I've one last quesiton.
How can I copy one specific library from my local repository to the ear..?
or better, how can I access one specific lib from my repository..?
(since 2.0.8) For each dependency resolved, the property
groupId:artifactId:type[:classifier] is defined pointing to the
corresponding file.
I need to unjar one of them, and I need to copy one of them to an extra
location.
Thanks guys!
Greets
Hey!
Thanks for the help, everything is running fine except one last
problem I guess:
when I deploy the ear file, jboss throws this error:
org.jboss.deployment.DeploymentException: Failed to find module file:
jboss-seam.jar
jboss gets the module defintion from the application.xml file.
The funny thing is, that the jboss-seam.jar is in the ears' lib folder
and has the correct filename (because of the versionmapper).
Thanks again,
Greets
ok, if you don't want to use simple mapper type=flatten /
but prefer the VersionMapper (to remove version from filenames), you
need to add versionsId=dependency.versions to you dependencies task
Hervé
Le lundi 05 mai 2008, roman schoenbichler a écrit :
Hervé BOUTEMY schrieb:
Ok the archives arn't build right, the libs arn't copied into the new
archives
I'm using the following lines:
artifact:dependencies pomRefId=maven.project
filesetId=dependency.fileset useScope=runtime/
copy todir=${war.dir}/WEB-INF/lib
!--fileset dir=${lib.dir}
include name=richfaces-impl*.jar /
include name=richfaces-ui*.jar /
include name=oscache*.jar /
include name=commons-digester.jar /
include name=commons-beanutils.jar /
include name=jsf-facelets.jar /
include name=jboss-seam-*.jar /
exclude name=jboss-seam-gen.jar /
/fileset--
fileset refid=dependency.fileset/
mapper classpathref=maven-ant-tasks.classpath
classname=org.apache.maven.artifact.ant.VersionMapper
from=${dependency.versions} to=flatten /
/copy
notice that the fileset which is commented was the initial ant script,
which copied the libs from the local ./lib folder ...
Am I missing something, or is the code simply wrong..?
Think this would be the last problem!
Thanks,
Greets
yes, with pomRefId, it should work better:
artifact:dependencies pomRefId=maven filesetId=dependency.fileset
useScope=runtime/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven-default-skin artifact is failing our builds
The checksum is a hint...perhaps there is garbage in Artifactory from a network glitch? Try clearing it and your local to see. -Original Message- From: Brewster, Richard [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 9:50 AM To: Maven Users List Subject: maven-default-skin artifact is failing our builds [INFO] artifact org.apache.maven.skins:maven-default-skin: checking for updates from central [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '7f1b64b38fb9268def21e3808c0d44 8146d7bf37'; remote = 'fa58f552f7b0d2d697f7b006e4b007996bcbaae1' - RETRYING [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '7f1b64b38fb9268def21e3808c0d44 8146d7bf37'; remote = 'fa58f552f7b0d2d697f7b006e4b007996bcbaae1' - IGNORING [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] The skin does not exist: Unable to determine the release version This just started happening in multiple environments for our project. Maven 2.0.9 is in use. Any idea what's happening? We are using Artifactory as the company repo server. Richard Brewster Senior Associate Perrin Quarles Associates [EMAIL PROTECTED] (434) 817-2640 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven ant task, copy local libs
Thanks!!
My build file works perfekt!
Thanks to all!
Greets
Le mercredi 07 mai 2008, roman schoenbichler a écrit :
Hm the last post shouldn't be on this mailing list I guess sry,
but I've one last quesiton.
How can I copy one specific library from my local repository to the ear..?
or better, how can I access one specific lib from my repository..?
(since 2.0.8) For each dependency resolved, the property
groupId:artifactId:type[:classifier] is defined pointing to the
corresponding file.
I need to unjar one of them, and I need to copy one of them to an extra
location.
Thanks guys!
Greets
Hey!
Thanks for the help, everything is running fine except one last
problem I guess:
when I deploy the ear file, jboss throws this error:
org.jboss.deployment.DeploymentException: Failed to find module file:
jboss-seam.jar
jboss gets the module defintion from the application.xml file.
The funny thing is, that the jboss-seam.jar is in the ears' lib folder
and has the correct filename (because of the versionmapper).
Thanks again,
Greets
ok, if you don't want to use simple mapper type=flatten /
but prefer the VersionMapper (to remove version from filenames), you
need to add versionsId=dependency.versions to you dependencies task
Hervé
Le lundi 05 mai 2008, roman schoenbichler a écrit :
Hervé BOUTEMY schrieb:
Ok the archives arn't build right, the libs arn't copied into the new
archives
I'm using the following lines:
artifact:dependencies pomRefId=maven.project
filesetId=dependency.fileset useScope=runtime/
copy todir=${war.dir}/WEB-INF/lib
!--fileset dir=${lib.dir}
include name=richfaces-impl*.jar /
include name=richfaces-ui*.jar /
include name=oscache*.jar /
include name=commons-digester.jar /
include name=commons-beanutils.jar /
include name=jsf-facelets.jar /
include name=jboss-seam-*.jar /
exclude name=jboss-seam-gen.jar /
/fileset--
fileset refid=dependency.fileset/
mapper classpathref=maven-ant-tasks.classpath
classname=org.apache.maven.artifact.ant.VersionMapper
from=${dependency.versions} to=flatten /
/copy
notice that the fileset which is commented was the initial ant script,
which copied the libs from the local ./lib folder ...
Am I missing something, or is the code simply wrong..?
Think this would be the last problem!
Thanks,
Greets
yes, with pomRefId, it should work better:
artifact:dependencies pomRefId=maven filesetId=dependency.fileset
useScope=runtime/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Issue with asm Dependancy and cxf
I keep getting the following errors: *Caused by: java.lang.NoSuchMethodError: org.objectweb.asm.ClassVisitor.visit(ILjava/lang/String;Ljava/lang/String;[Ljava/lang/String;Ljava/lang/String;)V * *at net.sf.cglib.core.ClassEmitter.begin_class(ClassEmitter.java:63)* The standard fix talks about cgi-full already having the asm classes in it. This means I need to exclude asm in my build I assume. So I have: dependency groupIdcglib/groupId artifactIdcglib-full/artifactId version2.0.2/version *exclusions exclusion groupIdasm/groupId artifactIdasm/artifactId /exclusion /exclusions* /dependency But I still get asm 1.5.3, 2.2.1 and 2.2.3 downloaded. Now when I look at my REPO and try to see what depends upon asm, I find that hibernate needs 1.5.3, and cobertura needs 2.2.1, and spring-2.5.2 needs 2.2.3 So should I just add excludes for asm on hibernate and cobertura? -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.linkedin.com/in/mickknutson http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/BLiNCMagazine http://tahoe.baselogic.com ---
Re: [m2] Issue with asm Dependancy and cxf
The fix for this normally is to exclude both asm and cglib from the hibernate dependency and then add cglib-nodeps as a dependency to your project. Thus, hibernate will use the cglib-nodeps stuff which includes the masked version it requires. The cobertura and spring deps are fine. CXF will work with any 2.x or 3.x version of asm so pulling that in is fine. Dan Kulp Mick Knutson-4 wrote: I keep getting the following errors: *Caused by: java.lang.NoSuchMethodError: org.objectweb.asm.ClassVisitor.visit(ILjava/lang/String;Ljava/lang/String;[Ljava/lang/String;Ljava/lang/String;)V * *at net.sf.cglib.core.ClassEmitter.begin_class(ClassEmitter.java:63)* The standard fix talks about cgi-full already having the asm classes in it. This means I need to exclude asm in my build I assume. So I have: dependency groupIdcglib/groupId artifactIdcglib-full/artifactId version2.0.2/version *exclusions exclusion groupIdasm/groupId artifactIdasm/artifactId /exclusion /exclusions* /dependency But I still get asm 1.5.3, 2.2.1 and 2.2.3 downloaded. Now when I look at my REPO and try to see what depends upon asm, I find that hibernate needs 1.5.3, and cobertura needs 2.2.1, and spring-2.5.2 needs 2.2.3 So should I just add excludes for asm on hibernate and cobertura? -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.linkedin.com/in/mickknutson http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/BLiNCMagazine http://tahoe.baselogic.com --- -- View this message in context: http://www.nabble.com/-m2--Issue-with-asm-Dependancy-and-cxf-tp17117334p17117618.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Issue with asm Dependancy and cxf
I did that.
*Here is the plugin:*
*dependency
groupIdorg.hibernate/groupId
artifactIdhibernate/artifactId
version${hibernate.version}/version
scopecompile/scope
exclusions
exclusion
groupIdasm/groupId
artifactIdasm/artifactId
/exclusion
exclusion
groupIdasm/groupId
artifactIdasm-attrs/artifactId
/exclusion
exclusion
groupIdcglib/groupId
artifactIdcglib/artifactId
/exclusion
/exclusions
/dependency
*
dependency
groupIdcglib/groupId
artifactIdcglib-nodep/artifactId
version2.1_3/version
/dependency
*Here is the error now*
![CDATA[org.springframework.beans.factory.BeanCreationException: Error
creating bean with name
*'org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor#0'
defined in class path resource [applicationContext-jpa.xml]: Initialization
of bean failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'entityManagerFactory' defined in class path resource
[applicationContext-jpa.xml]: Invocation of init method failed; nested
exception is java.lang.NoClassDefFoundError: org/objectweb/asm/CodeVisitor
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:470)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:404)
at java.security.AccessController.doPrivileged(Native Method)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:375)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:263)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:170)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:260)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:184)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:163)
at
org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:881)
at
org.springframework.context.support.AbstractApplicationContext.registerBeanPostProcessors(AbstractApplicationContext.java:597)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:366)
at
org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:96)
at
org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:44)
at
org.springframework.test.context.TestContext.buildApplicationContext(TestContext.java:198)
at
org.springframework.test.context.TestContext.getApplicationContext(TestContext.java:233)
at
org.springframework.test.context.support.DependencyInjectionTestExecutionListener.injectDependencies(DependencyInjectionTestExecutionListener.java:126)
at
org.springframework.test.context.support.DependencyInjectionTestExecutionListener.prepareTestInstance(DependencyInjectionTestExecutionListener.java:85)
at
org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:277)
at
org.springframework.test.context.testng.AbstractTestNGSpringContextTests.springTestContextPrepareTestInstance(AbstractTestNGSpringContextTests.java:117)
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.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:580)
at
org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:398)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:145)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:82)
at
org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:166)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:103)
at org.testng.TestRunner.runWorkers(TestRunner.java:689)
at org.testng.TestRunner.privateRun(TestRunner.java:566)
at org.testng.TestRunner.run(TestRunner.java:466)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:301)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:296)
at
Re: Can't run ant task in maven 2.0.9
I've found if I upgrade the antrun plugin to 1.2-SNAPSHOT the problem is
fixed. Should I still log a Jira?
Brian E. Fox wrote:
Since this is a regression, we will fix it for 2.0.10, can you write a jira and
attach a sample project?
-Original Message-
From: Matt Milliss [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 06, 2008 8:13 PM
To: users@maven.apache.org
Subject: Re: Can't run ant task in maven 2.0.9
The problem only happens with maven 2.0.9. If I rollback maven to 2.0.8
it works fine with ant tasks 2.0.9. And maven 2.0.9 still doesn't work
with ant tasks 2.0.8. The maven antun plugin version is 1.1. I even
tried rolling ant back to 1.6.5 as I noticed that the antrun plugin has
a dependency on 1.6.5 and this didn't fix the problem either.
Regards
Matt
Hervé BOUTEMY wrote:
and give the exact version of the maven-antrun-plugin used
Le dimanche 04 mai 2008, Brian E. Fox a écrit :
Can you try to isolate this to the Ant task or Maven update? Ie don't
update them both at the same time and see which one actually causes the
breakage.
-Original Message-
From: Matthew Milliss [mailto:[EMAIL PROTECTED]
Sent: Sunday, May 04, 2008 5:14 AM
To: users@maven.apache.org
Subject: Can't run ant task in maven 2.0.9
I've just installed maven 2.0.9 and added the 2.0.9 Maven tasks for ant
into my ant install lib directory (ant 1.7) and now when I run my antrun
plugin it fails with the message:
Embedded error: The following error occurred while executing this line:
/home/development/workspace/backoffice/run-fit.xml:5: Could not create
task or type of type: antlib:org.apache.maven.artifact.ant:dependencies.
I didn't have this issue with maven 2.0.7 or 2.0.8 with either ant 1.6.5
or 1.7. Has anybody experienced this issue and know what the problem is?
here is the antrun config in my pom:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idTests Run by Ant/id
phasetest/phase
goals
goalrun/goal
/goals
configuration
tasks
ant antfile=${basedir}/run-fit.xml
dir=${basedir} inheritRefs=true /
/tasks
/configuration
/execution
/executions
/plugin
and the ant build file:
?xml version=1.0?
project name=run-fit default=run-tests
xmlns:artifact=antlib:org.apache.maven.artifact.ant
target name=setup
artifact:dependencies filesetId=aspectjweaver.fileset
dependency groupId=aspectj artifactId=aspectjweaver
version=1.5.3 /
/artifact:dependencies
/target
target name=run-tests depends=setup
echo message=I don't work /
/target
/project
os
fedora core 6 version 2.6.22.14-72.fc6
java version 1.6.0_04
Java(TM) SE Runtime Environment (build 1.6.0_04-b12)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing)
Cheers
Matt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dependency licenses
Thanks, this is just what I wanted. I look forward to seeing it on central :-) Keith 2008/5/4 Sherali Karimov [EMAIL PROTECTED]: Just a clarification: Download - will download (and optionally deploy to maven repo) licenses of all the dependencies of the project. cheers, sherali 04/05/2008, в 13:35, James William Dumay писал(а): Keith, We are working on something like that at Atlassian right now. Checkout this plugin: https://svn.atlassian.com/svn/public/atlassian/maven-plugins/maven-licenses-plugin/trunk/ You would probably be interested in the following two goals: * List - This goal lists all of the licenses of all transitive dependencies of your project. * Download - This goal will download all of the transitive dependencies of your project. This plugin is still a work in progress but we hope to make it available on central shortly. Cheers James On 04/05/2008, at 8:39 AM, Keith Bonawitz wrote: Is there a way to create an assembly that includes a license file for each dependency (including transitive dependencies)? Thanks, Keith - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Keith, We are working on something like that at Atlassian right now. Checkout this plugin: https://svn.atlassian.com/svn/public/atlassian/maven-plugins/maven-licenses-plugin/trunk/ You would probably be interested in the following two goals: * List - This goal lists all of the licenses of all transitive dependencies of your project. * Download - This goal will download all of the transitive dependencies of your project. This plugin is still a work in progress but we hope to make it available on central shortly. Cheers James On 04/05/2008, at 8:39 AM, Keith Bonawitz wrote: Is there a way to create an assembly that includes a license file for each dependency (including transitive dependencies)? Thanks, Keith - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
archetype:crawl generates multiple entries when used on a snapshot repository
L.S., When you use archetype:crawl on local Maven repository that contains multiple snapshot builds (e.g. by Bamboo/Continuum), it generates multiple archetype/ entries in the catalog with the exact same groupId/artifactId/version. For now, I have used an XSL stylesheet in our ServiceMix build to deduplicate the entries, but I don't think the plugin should generate these kind of duplicates anyway. I would like to open a JIRA issue for it, but just checking here first to see if anyone has a good use case for having these duplicates somehow. Thanks - --- Gert Vanthienen http://www.anova.be -- View this message in context: http://www.nabble.com/archetype%3Acrawl-generates-multiple-entries-when-used-on-a-snapshot-repository-tp17120170p17120170.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
