mvn release:perform does not honor //servers/server in alternate settings location
Hi All- I am trying to perform a maven release by invoking the following: mvn -B -s /my/alternate/maven2/home/settings.xml release:prepare release:perform The problem that occurs is during the deploy of the release artifact, it seems it is not picking up the username/password in /my/alternate/maven2/home/settings.xml--I get a 401 authentication error. However, when I place settings.xml in the default location ($HOME/.m2/settings.xml), then the deploy works perfectly. Does anyone know how to get around this issue? or is there a newer release of the appropriate plugin that does not have this problem? Thanks, David
Re: mvn release:perform does not honor //servers/server in alternate settings location
On Wed, Apr 21, 2010 at 1:42 PM, David Siefert siefert.da...@gmail.comwrote: Hi All- I am trying to perform a maven release by invoking the following: mvn -B -s /my/alternate/maven2/home/settings.xml release:prepare release:perform The problem that occurs is during the deploy of the release artifact, it seems it is not picking up the username/password in /my/alternate/maven2/home/settings.xml--I get a 401 authentication error. However, when I place settings.xml in the default location ($HOME/.m2/settings.xml), then the deploy works perfectly. Does anyone know how to get around this issue? or is there a newer release of the appropriate plugin that does not have this problem? Thanks, David Ah, found my answer... mvn -B -s /my/alternate/maven2/home/settings.xml release:prepare release:perform -Darguments=/my/alternate/maven2/home/settings.xml Not very elegant, but works like a charm! Thanks, David
creating eclipse project from ejb maven project
Hi All- I have a Maven2 POM and need to generate an Eclipse (specifically MyEclipse) IDE project. The POM specifies an EJB project (project.packaging: ejb) but it seems that MyEclipse is loading it as a Java Project (not recognized as a JAR that can be deployed to an application server). Any ideas, or suggestions working with the Maven2 eclipse plugin? Thanks in advance, David
Re: creating eclipse project from ejb maven project
Solved it with the help of a coworker. Need to add the following nature: com.genuitec.eclipse.j2eedt.core.ejbnature to the maven-eclipse-plugin configuration. Thanks, David From: David Siefert davidsiefert.play...@yahoo.com To: users@maven.apache.org Sent: Mon, December 7, 2009 1:53:09 PM Subject: creating eclipse project from ejb maven project Hi All- I have a Maven2 POM and need to generate an Eclipse (specifically MyEclipse) IDE project. The POM specifies an EJB project (project.packaging: ejb) but it seems that MyEclipse is loading it as a Java Project (not recognized as a JAR that can be deployed to an application server). Any ideas, or suggestions working with the Maven2 eclipse plugin? Thanks in advance, David
Re: running a single integration test during integration-test-phase
On Thu, Feb 21, 2008 at 12:26 PM, David Siefert [EMAIL PROTECTED] wrote: Hello, Is there a way to configure a POM to run a single test during the integration-test-phase via command line? ie, mvn verify -Dtest=MyIntegrationTest That way I can do the necessary build work in pre-integration-test to prepare to run the integration-test phase. Thanks, David Ok, I am going to solve this myself. :) While trying to solve another problem, I found out there is a property in the maven-invoker-plugin that will let you run a single test. Although I am not using the maven-invoker-plugin to run the build (instead I am just running the project directly at command line), the property still works. Here it is: mvn phase -Dinvoker.test=classname -David
Re: running a single integration test during integration-test-phase
2008/2/22 Jeff MAURY [EMAIL PROTECTED]:
You need to configure the Maven surefire plugin in your POM and set the
test
configuration property for it.
Here is a sample:
project
[...]
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
configuration
testMyIntegrationTest/test
/configuration
/plugin
/plugins
/build
[...]
/project
Jeff
On Thu, Feb 21, 2008 at 6:26 PM, David Siefert
[EMAIL PROTECTED] wrote:
Hello,
Is there a way to configure a POM to run a single test during the
integration-test-phase via command line?
ie,
mvn verify -Dtest=MyIntegrationTest
That way I can do the necessary build work in pre-integration-test to
prepare to run the integration-test phase.
Thanks,
David
--
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
What system property do I use in test${???}/test to get the test name
that was specified in the -Dtest parameter?
-David
running a single integration test during integration-test-phase
Hello, Is there a way to configure a POM to run a single test during the integration-test-phase via command line? ie, mvn verify -Dtest=MyIntegrationTest That way I can do the necessary build work in pre-integration-test to prepare to run the integration-test phase. Thanks, David
Re: Maven Invoker Plugin help
I have come across an interesting issue:
Following the example in the maven-jar-plugin, I have my artifact deployed
to a dynamically created local repository which its path is passed to the
maven-invoker-plugin for the integration test projects. I am finding that
the maven-dependency-plugin:copy is still downloading the last snapshot from
the inhouse repository regardless if it is newer or older, and then being
copied to a directory of my choosing from which it is deployed to a running
jboss server for testing.
I have a workaround: I manually specified the path
(${basedir}/../../../local-repo/groupid/artifactid/version-snapshot/filename.jar)
and that got it working the way I wanted--but of course this is not ideal
since i'll have to update the version identifier everytime i do a release,
or the path if the location of the integration project changes (i could
probably use the interpolated pom filtering feature to resolve the version
identifier issue).
What do you think should be the case to solve this kind of issue? Perhaps I
am doing something wrong? I tried tweaking some of the repository snapshot
update settings (tried setting to always update), and overwriting the
dependencies (via dependency:copy) to false (so they dont overwrite), but
nothing seems to work correctly.
-David
On Wed, Jan 23, 2008 at 12:41 PM, Olivier Lamy [EMAIL PROTECTED] wrote:
Hi,
You can have a look at the its in some maven plugins (jar plugin [1])
to see how we organize execution of the maven-invoker-plugin.
Look at the pom and the profile called integration-tests.
But IMHO the maven-invoker-plugin is for maven plugins not for jar
artifacts.
--
Olivier
|1] https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-jar-plugin/
2008/1/23, David Siefert [EMAIL PROTECTED]:
Hi,
I am trying to get my integration tests to run as part of the main
project
build using the maven-invoker-plugin. However it is impossible (at
least
without some hacking) to have the IT projects run because of the maven
build
lifecycle.
compile
package -- JAR created
integration-test -- invoke maven it projects [FAILS: Cannot load
artifact
that was built during package phase]
verify -- Reports success anyway even though build has failed due to
above
artifact issue!
I could see a possible solution: use ant task to copy the project
artifact,
or use a systemPath dependency--however this could be error prone
(location
of the artifact).
Any suggestions?
Thanks,
David
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Invoker Plugin help
Okay, on one machine I am running maven-2.0.7 and when the i.t. project fails, the main project still reports success. On another machine I am using maven-2.0.8 and when the i.t. project fails, the main project build correctly reports failure. I am mentioning it here for anyone who searches the mailing lists with failing i.t. projects being reported as success--the solution is to upgrade to maven-2.0.8 :) Thanks again Olivier for your help. -David On Feb 1, 2008 4:41 PM, Olivier Lamy [EMAIL PROTECTED] wrote: If building your maven project failed, the invoker will report this (line starting with : ...FAILED) If not we have an issue here in the invoker plugin. -- Olivier 2008/2/1, David Siefert [EMAIL PROTECTED]: Thank you very much Olivier, I am now able to invoke the integration test projects from my main project just like the maven-jar-plugin does. I have another issue: a beanshell script is required to report whether or not the build has failed or succeeded. Why can't the build failure of the maven project be reported to the invoker plugin so I do not have to do this? Thanks! -David On Jan 23, 2008 12:41 PM, Olivier Lamy [EMAIL PROTECTED] wrote: Hi, You can have a look at the its in some maven plugins (jar plugin [1]) to see how we organize execution of the maven-invoker-plugin. Look at the pom and the profile called integration-tests. But IMHO the maven-invoker-plugin is for maven plugins not for jar artifacts. -- Olivier |1] https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-jar-plugin/ 2008/1/23, David Siefert [EMAIL PROTECTED]: Hi, I am trying to get my integration tests to run as part of the main project build using the maven-invoker-plugin. However it is impossible (at least without some hacking) to have the IT projects run because of the maven build lifecycle. compile package -- JAR created integration-test -- invoke maven it projects [FAILS: Cannot load artifact that was built during package phase] verify -- Reports success anyway even though build has failed due to above artifact issue! I could see a possible solution: use ant task to copy the project artifact, or use a systemPath dependency--however this could be error prone (location of the artifact). Any suggestions? Thanks, David - 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 Invoker Plugin help
Seems to be working okay--I upgraded to maven-2.0.8, and I didn't check if the error existed prior to the change. One other issue I am finding now: I tried doing an offline build (with -o option) and the maven invoker plugin does not carry it through, so all the integration test projects download all dependencies regardless... -David On Feb 1, 2008 4:41 PM, Olivier Lamy [EMAIL PROTECTED] wrote: If building your maven project failed, the invoker will report this (line starting with : ...FAILED) If not we have an issue here in the invoker plugin. -- Olivier 2008/2/1, David Siefert [EMAIL PROTECTED]: Thank you very much Olivier, I am now able to invoke the integration test projects from my main project just like the maven-jar-plugin does. I have another issue: a beanshell script is required to report whether or not the build has failed or succeeded. Why can't the build failure of the maven project be reported to the invoker plugin so I do not have to do this? Thanks! -David On Jan 23, 2008 12:41 PM, Olivier Lamy [EMAIL PROTECTED] wrote: Hi, You can have a look at the its in some maven plugins (jar plugin [1]) to see how we organize execution of the maven-invoker-plugin. Look at the pom and the profile called integration-tests. But IMHO the maven-invoker-plugin is for maven plugins not for jar artifacts. -- Olivier |1] https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-jar-plugin/ 2008/1/23, David Siefert [EMAIL PROTECTED]: Hi, I am trying to get my integration tests to run as part of the main project build using the maven-invoker-plugin. However it is impossible (at least without some hacking) to have the IT projects run because of the maven build lifecycle. compile package -- JAR created integration-test -- invoke maven it projects [FAILS: Cannot load artifact that was built during package phase] verify -- Reports success anyway even though build has failed due to above artifact issue! I could see a possible solution: use ant task to copy the project artifact, or use a systemPath dependency--however this could be error prone (location of the artifact). Any suggestions? Thanks, David - 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 Invoker Plugin help
Thank you very much Olivier, I am now able to invoke the integration test projects from my main project just like the maven-jar-plugin does. I have another issue: a beanshell script is required to report whether or not the build has failed or succeeded. Why can't the build failure of the maven project be reported to the invoker plugin so I do not have to do this? Thanks! -David On Jan 23, 2008 12:41 PM, Olivier Lamy [EMAIL PROTECTED] wrote: Hi, You can have a look at the its in some maven plugins (jar plugin [1]) to see how we organize execution of the maven-invoker-plugin. Look at the pom and the profile called integration-tests. But IMHO the maven-invoker-plugin is for maven plugins not for jar artifacts. -- Olivier |1] https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-jar-plugin/ 2008/1/23, David Siefert [EMAIL PROTECTED]: Hi, I am trying to get my integration tests to run as part of the main project build using the maven-invoker-plugin. However it is impossible (at least without some hacking) to have the IT projects run because of the maven build lifecycle. compile package -- JAR created integration-test -- invoke maven it projects [FAILS: Cannot load artifact that was built during package phase] verify -- Reports success anyway even though build has failed due to above artifact issue! I could see a possible solution: use ant task to copy the project artifact, or use a systemPath dependency--however this could be error prone (location of the artifact). Any suggestions? Thanks, David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven Invoker Plugin help
Hi, I am trying to get my integration tests to run as part of the main project build using the maven-invoker-plugin. However it is impossible (at least without some hacking) to have the IT projects run because of the maven build lifecycle. compile package -- JAR created integration-test -- invoke maven it projects [FAILS: Cannot load artifact that was built during package phase] verify -- Reports success anyway even though build has failed due to above artifact issue! I could see a possible solution: use ant task to copy the project artifact, or use a systemPath dependency--however this could be error prone (location of the artifact). Any suggestions? Thanks, David
Re: howto include library for defined task in antrun-plugin?
You should also check out the example source code provided in the book 'SOA
using Java Web Services' by Mark Hansen (http://soabook.com). I used the
Maven+Ant build scripts as a basis for generating web service clients and
contract-based service generation using the JBoss wstools script (which
already sets up the classpath based on your JBOSS_HOME environment--which
would be available for any JBoss installation/setup). The book's source
code is built using Glassfish libraries.
-David
On 1/23/08, aldana [EMAIL PROTECTED] wrote:
i solved it with a workaround: i included jaxws-tools as optional
depedency
in pom.xml and referenced it from ant-buildfile through
${maven.compile.classpath}.
aldana wrote:
for reasons as explained in
http://forums.java.net/jive/thread.jspa?threadID=35708tstart=15 i need
to
generate my jax-ws sources through antrun plugin.
for that i need to include the jax-ws library. how is the import of
neccessary ant-task libraries for the antrun plugin done? as explained
in
http://maven.apache.org/plugins/maven-antrun-plugin/examples/classpaths.html
i could reference classpath through id ${maven.plugin.classpath}, but i
will replace the wsimport maven2 plugin with the ant task so the
jaxws-tools library won't be included any longer in pom.xml.
what is the best practice to include third party libraries for ant tasks
which are not included through pom.xml? i can only think of copying the
library of the ant build.xml, but doubt that this is the right way...
--
View this message in context:
http://www.nabble.com/howto-include-library-for-defined-task-in-antrun-plugin--tp15038204s177p15047047.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]
