Arnaud Bailly-3 wrote:
I will setup a ML (or better, move the thing to sourceforge ASAP0
I find sourceforge painfull, if you are going to go with external hosting,
what about these:
- http://code.google.com/
- http://www.devjavu.com/ (hosted Trac and SVN)
- http://www.javaforge.com
The stripping of the hostname from full URLs, and then getting it wrong,
drove me mad too.
I've got it all working now. Maven 2.0.4, maven-site-plugin 2.0-beta5
What do you have in your url/ in your sub poms? I only set the url in the
parent pom, and don't mention it in the sub poms.
David
It could be your internet proxy is blocking some of the jars. That's what
happens at my work place. Some get though, but I found the architype ones
were blocked.
Try running mvn with the -X parameter then you'll be able to see the urls
that are being accessed. You can then try them in your
You don't say what doesn't work when you run if from maven? Is it that the
tests don't run at all? Or that the setup gets called too many times?
Could it be to do with forking the JVM for each test?
Your testSuite() method looks stange to me, surely it should return
something to the test
I looked at the pom a while ago, and it looked like it had been automatically
converted to maven 2.
I didn't know that was possible, and I didn't try it. But now people here
are saying it works I might give it a go.
Anyone else used it with success?
David
Wendy Smoak-3 wrote:
On
What is a reactor build in maven2?
People seem to use the term to mean building a super project and allowing
maven to recurse into the sub-modules. And indeed that is how I build by
project... mvn clean install
However there is a command line argument called --reactor, what does it
do?
If I
I'm not an expert, but I'd expect that you could configure the maven compiler
plugin to run the compile goal twice with two different configs.
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
executions
execution
Great, I get alot further now. You are very helpful Tom.
All my jars build ok and get signed.
It's just when it gets to the EJBs that is falls over now.
There exists a jar TATTestEJB\target\TATTestEJB.jar
But the jarsigner is looking for TATTestEJB\target\TATTestEJB.ejb
I'm using
I version bumped my project to use the new maven-jar-plugin 2.1, and now I
have access to the jar signing feature. It works very well, I just added
the following, and now all my jars are signed. This is great because if two
developers create what then think is the same build on their own
probably why surefire is usign the signed jar.
If you want to avoid this, assign a classifier to the signed jar.
Tom
On 1/10/07, Christian Goetze [EMAIL PROTECTED] wrote:
diroussel wrote:
The question is, why is surefire not using the un-signed jar. I have
two
jars:
target\MyJar.jar
Great post. Your right, maven is a great tool, but still has a way to go to
make if perfect for most people.
Part of the problem is that release processes are shaped by forces outside
of the development team, such as legacy systems, existing team structures,
and other sorts of company history.
Christian Goetze-3 wrote:
... get screwed by one guy outside accidentally including a dependency
with encumbering licensing. That's the big drawback of the automatic
inclusion of transitive dependencies.
But maven is powerful enough to allow you to report on the licenses of all
Do your module names match the directory names which match the artifact ids?
Adam Lally-2 wrote:
On 11/16/06, Marc Prud'hommeaux [EMAIL PROTECTED] wrote:
Adam-
I've experienced that as well. My workaround is to first run mvn
install and then mvn javadoc:javadoc, and it seems to work.
use the ear plugin?
http://maven.apache.org/plugins/maven-ear-plugin/
Zeitlin, Michael wrote:
I found out that the ejb plugin for maven 2 does not allow you to bundle
jars within the EJB like in maven 1.
http://jira.codehaus.org/browse/MEJB-3
Does anyone know of a good
I've not managed to get integration tests working myself, but
Where have you put your tests? I've noticed the surefire pluin itself has
it's tests in src/it/testX.
Do:
svn checkout
https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-surefire-plugin
maven-surefire-plugin
and have a
I'm just guessing here, but since only string properties are passed you need
to define a string property which is based on the non-string property.
Perhaps you could define:
outDir=${project.build.outputDirectory}
Perhaps you could define this in a profile, or in project.properties or
How are you setting your property?
we use: mvn -DbuildVersion=MYAPP_01234 clean install
and the substitution ${buildVersion} works fine.
David
--
View this message in context:
Jan, did you find a solution to this? It looks to me that the exclude
feature doesn't work, which is why others seem to be using more elaborate
techniques to getting integration tests working (separate module, or using
profiles).
I found this comment in SurefirePlugin.java
This, and the previous fop thread, has made me think about what happens with
versioning and simple fixes.
For example
A-1.5 depends on B-1.0
B-1.0 depends on C-2.0
Now there is an API compatible fix in C, and the version is changed to
C-2.0.1. Now for A to get the bennifit of this change
Carlos Sanchez-4 wrote:
When you build A you don't know anything about C-2.0.1 because it does
not exist.
Versions in repository explicitly define what versions the have been
released against or tested with.
If I release A 2.0 depending in C 2.0
and then I want to say i'm compatible
There are some listed here...
http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide
I'd like to know how to dump a list of all properties to a build log. Is
this possible?
Eric Brown-14 wrote:
How do I get a list of these?
Clearly I can reference anything in settings.xml and
Define the jdk1.3 specific stuff in a profile...
profiles
profile
activation
jdk1.3/jdk
/activation
...
/profile
/profiles
See here for an intro:
http://maven.apache.org/guides/introduction/introduction-to-profiles.html
Note that pretty much any thing in the pom project
What version are you using? I'm using jxr-maven-plugin\2.0-beta-1 and I
don't seem to have that problem.
CodingPlayer wrote:
Hi All,
I'm currently trying to get the maven-jxr-plugin running.
But there seems to be a bug in the plugIn or something missing in my
configuration.
The
Is the fix out yet? I'm using jxr-maven-plugin\2.0-beta-1 and I'm getting
the wrong link. Does the issue need reopening?
Mike Perham wrote:
I believe this is fixed in svn but has not been released yet.
http://jira.codehaus.org/browse/JXR-6
-Original Message-
From: Alexandre
24 matches
Mail list logo
