just use -DskipTests as that will skip running the tests but not compiling
or packaging them... oh and it's shorter than its alias
-Dmaven.skip.test.exec=true as well as the bigger skip that you are using
-Dmaven.skip.test=true
-Stephen
On 3 September 2010 02:28, Andrew Hughes ahhug...@gmail.com
Hi!
I'm currently working on a packaging=jar project. In addition to the plain jar,
by using the assembly plugin I also generate a jar-with-dependencies, and -
using a custom assembly - a zip file (with the bin classifier). The zip file
contains:
* the plain jar
* a batch file to run
On Fri, Sep 3, 2010 at 4:15 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
just use -DskipTests as that will skip running the tests but not compiling
or packaging them... oh and it's shorter than its alias
-Dmaven.skip.test.exec=true as well as the bigger skip that you are using
and you don't need the =true for -DskipTests
On 3 September 2010 08:17, Barrie Treloar baerr...@gmail.com wrote:
On Fri, Sep 3, 2010 at 4:15 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
just use -DskipTests as that will skip running the tests but not
compiling
or packaging
create the zip and the jar-with-dependencies in separate modules that pull
in the plain jar with scope=provided
On 3 September 2010 04:36, Shannon Hickey shic...@adobe.com wrote:
Hi!
I'm currently working on a packaging=jar project. In addition to the plain
jar, by using the assembly plugin
It turns out that I have another plugin facing a similar problem:
I want to compile the java source first, and generate some resources
to be included in final JAR base on the compiled class.
I can only put that on or after process-classes phase. However, from
the experience stated in the
Hi Guys,
The problem is not that we're skipping the tests. I really don't want to run
the tests... but I do want the jar:test-jar to still run and build...
moduleA-0.0.0-test.jar so that other module dependencies still resolve
this.
On Fri, Sep 3, 2010 at 5:08 PM, Stephen Connolly
Hi,
I don't think it's justified for you to write to dev list. This sound like a
typical user problem, not a dev one.
Note a lot of developers also follow the users list, so writing to dev list
is not always going to help you, if not worse.
First, try answering the question that're being asked to
-DskipTests only skips running the tests not building the test-jar
On 3 September 2010 09:58, Andrew Hughes ahhug...@gmail.com wrote:
Hi Guys,
The problem is not that we're skipping the tests. I really don't want to
run
the tests... but I do want the jar:test-jar to still run and build...
On Thu, Aug 26, 2010 at 7:36 PM, nishant@hsbcib.com wrote:
Just that unable to find clientModule
That's just not enough. Provide the output of mvn dependency:list and the
log of your build (mvn package output.log)
Stephane Nicoll stephane.nic...@gmail.com
Aug 26 2010 18:35
Mail
I need the jboss-ejb3x-4.2.3.GA.jar. And I find it under
http://repository.jboss.org/maven2;.
How can I set this in the settings.xml to download this jar?
I've tried set this repo as mirror/ and in repository/. But as I run mvn
eclipse:eclipse it shows the mvn just connect to
I am trying to release a project using release:perform. When it is
checking out the project from subversion I get the error
svn: Your .svn/tmp directory may be missing or corrupt; run 'svn cleanup'
and try again
svn: Can't open file
Hi,
It looks there is probably an issue with handling spaces in the cli.
Which version are u using of release and scm ?
Can you try with changing your -Djava.io.tmpdir= in MAVEN_OPTS env var ?
Perso, I have changed this on my windows box to something without spaces.
MAVEN_OPTS=-Xms512m -Xmx512m
This problem is solved. Please don't answer
--
View this message in context:
http://maven.40175.n5.nabble.com/How-to-set-the-settings-xml-so-that-the-jboss-ejb3x-jar-be-downloaed-tp2802095p2802182.html
Sent from the Maven - Users mailing list archive at Nabble.com.
There are a number of pitfalls with test jars. My entirely personal
suggestion is this: any time you are tempted to put a test jar configuration
into a POM, just go and make a new, ordinary, project with the shared test
code in it, and use it with scopetest/scope. You won't regret it.
On Fri, Sep
That is my personal preference as well, but sometimes people do what they
want to do ;-)
On 3 September 2010 15:14, Benson Margulies bimargul...@gmail.com wrote:
There are a number of pitfalls with test jars. My entirely personal
suggestion is this: any time you are tempted to put a test jar
All,
[I've done a quick search and haven't seen anything, so I'm hoping someone can
point me in the right direction.]
I have a need to run some integration tests externally to Maven (under a
continuous integration environment) . That is, physically run the tests (and
the
system under test)
Using maven 3.0-beta-3 and the maven-site-plugin 3.0-beta-2-SNAPSHOT
and specifying the reportPlugins configuration as shown on
https://cwiki.apache.org/MAVEN/maven-3x-and-site-plugin.html
I get the following error:
[ERROR] Failed to execute goal
I haven't tried maven 3.0-beta-3 with the site plugin yet, but based on the
conversations I've read (on the dev list) maven-site-plugin
3.0-beta-2-SNAPSHOT should be updated to work.
The release process for maven-site-plugin 3.0-beta-2 is supposed to start
shortly, so I advice you to monitor the
Hi,
Thanks for reporting this.
It's now fixed and I have deployed a new SNAPSHOT.
2010/9/3 Raphael Ackermann rtac...@gmail.com:
Using maven 3.0-beta-3 and the maven-site-plugin 3.0-beta-2-SNAPSHOT
and specifying the reportPlugins configuration as shown on
I am using version 2.0 of the release plugin to tag a new version of my
multi-module application, but at the end when it goes to commit to SVN SCM, I
get the following:
[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Path 'svn://SVN
On Fri, Sep 3, 2010 at 6:16 PM, Neil Chaudhuri
nchaudh...@potomacfusion.com wrote:
I am using version 2.0 of the release plugin to tag a new version of my
multi-module application, but at the end when it goes to commit to SVN SCM, I
get the following:
What command did you execute?
What
I was avoiding this, but you're both only re-enforcing what I was thinking
of doing.
I have raised this as an issue (improvement) for the jar plugin
http://jira.codehaus.org/browse/MJAR-138 at least it's on the radar that
way. Please feel encouraged to comment/edit the issue if you can add
23 matches
Mail list logo