We use subversion and we have structured the modules as separate
projects. This was, according to our development environment manager
:-), necessary for good working with eclipse.
However when I create the parent project in continuum the submodules are
also created (as they should) but the
Yes, I do. The parent is only a pom, describing which modules actually
need to be built and in which order.
Emmanuel Venisse wrote:
By default, continuum doesn't use maven in reactor mode to build
project, so it doens't use modules.
Do you need to build all modules when you build your
Continuum know the order of each module, it's the reason we don't use the
reactor mode by default.
But if you need it absolutly, you need to create a project in the parent directory of your modules that have only one module, your parent project, and add it in continuum with the reactor mode, so
Mmmm, then, why do you want to stop transitivity? If you depend on a war
module which depends on implJarModule at runtime, then your final module
will also depend on it. Maybe your final module includes another
implementation?
Anyway, I guess what you need is to declare the dependency as:
Hi Todd,
I'm not sure but it's perhaps because you link the maven-assembly-plugin to
a phase.
Generally it's better to avoid this[1].
Try this instead:
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
Hi Rodrigo,
Thanks for your reply,
Mmmm, then, why do you want to stop transitivity? If you depend on a war
module which depends on implJarModule at runtime, then your final module
will also depend on it. Maybe your final module includes another
implementation?
It's not rely that I want to
hi, how to make system dependency added entries in manifest? I mean, this is
my dependency in the pom:
...
dependency
groupIdlit-commons/groupId
artifactIdctgclient/artifactId
version1.0/version
scopesystem/scope
systemPath${env.LITTOOLSDIR}/${env.SOURCEDIR}/lit-sl-comm/ctgclient-
Hello.
I have a problem building my Maven 2 submodules in Continuum. My parent
module is at the same level as my submodules (for easy IDE support
reasons) and building locally goes fine. But when I try to build on the
build server the module folder names are changed into numbers so the
How are they organized in your CVS?
Ronald Pieterse a écrit :
Hello.
I have a problem building my Maven 2 submodules in Continuum. My parent
module is at the same level as my submodules (for easy IDE support
reasons) and building locally goes fine. But when I try to build on the
build
How can I add a directory to my test classpath without putting it in
the target/test-classes directory?
Basically I have a conf directory for bootstrapping embedded jboss in
my JUnit test. Then I deploy the target/test-classes directory to
jboss to deploy my code. If the conf files for
Hello aging,
Just to replay to my own email, I have found a solution. There seems to
be an issue with the plugin when retrieved from Mergers mirror of
central. When I removed all references to the plugin and it's parents
and swapped mirror settings the problem resolved it self.
Regards
Tomas
Hi,
I have an ant plugin running in my pom,xml. When I run mvn idea:idea, it
throws the following exception. Can anyone tell me what is missing in my
setup..
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1768)
Hi,
I have a problem with the cobertura plugin version 2.1. It does not generate
correct reports.
I use maven 2.0.5 and java 1.5 on linux.
If I configure version 2.0 it works. Unfortunately this version does not report
the lines of code.
Bernd
The current snapshot of the m1 multichanges plugin has a goal to
generate a page with all changes since the last release of each
sub-project, see eg
http://maven.apache.org/maven-1.x/plugins/bundled/multichanges-report-next.html
Apart from that, I am not aware of any such functionality. AFAIK
I have created an issue for that : http://jira.codehaus.org/browse/MSITE-211
On Wednesday 21 February 2007 13:27, David J. M. Karlsen wrote:
Elid OR wrote:
Hi all,
When I execute the site deployment : mvn site:deploy that work with maven
2.0.4 I got this error on maven 2.0.5 :
Same
I am receiving the following error while trying to package my project
into an ear using the assembly-plugin.
Error creating assembly: appxml attribute is required
I am unable to find any information on how to incorporate an
application.xml using this plugin. We have one in source code
Hi,
not sure if there's a seperate mailinglist for surefire, I haven't found one
(with google). Is there a specific reason why the TOP 5 issues of the surefire
plugin are all unassigned?
There's about to be a big push on fixing issues in surefire. The main
ones will be taken care of, and we'll see what falls out from that (as
there are a number of interrelated issues). Testing will also be
added. Please continue to vote and comment on issues so that this can
be done most
I've had the same problem. Just giving this a bump as there are no replies.
davidkarlsen wrote:
Hi List!
I got some resources for the testing phase that should exist on the
classpath while testing with surefire.
If I merely add
testResources
testResource
Hi,
-Original Message-
From: ext Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 23 February, 2007 15:05
To: Maven Users List
Subject: Re: TOP 5 surefire issues all unassigned?
There's about to be a big push on fixing issues in surefire.
The main ones will be taken care of, and we'll see
Wayne Fay wrote:
You are looking for Profiles in conjunction with Resource Filtering.
Thanks for the tip.
It seems this will solve my problem if I find a way to pass the
properties to a schemaexport-task run from the antrun-plugin.
--
Regards
Erik
build your test jar in a separate project, and run it in a test project with
those resources
-D
On 2/23/07, apill [EMAIL PROTECTED] wrote:
I've had the same problem. Just giving this a bump as there are no
replies.
davidkarlsen wrote:
Hi List!
I got some resources for the testing
Hi Johann,
I patched the plugin to make it work. I'll attach it to MOJO-530. The
one currently there won't work with the head revision.
I'd like to help you figure out how to integrate the hbm2doc goal into
Maven's site generation. Have you considered that?
Thanks,
Jim
-Original
Hi,
I pasted below part of my pom file. I'd like the EJB jar file to be called
myEjbJar.jar.
Instead the file is named {artifactId}-{version}.jar.
Is there a way to make it work? I thought finalName inside build should
override the default jar file name.
Any help on the subject would be greatly
This is one of the quirks of system scoped dependencies... and these
quirks are why we generally recommend that you NOT use system scope
except in a handful of situations.
Leverage your local Maven repo, perform a proper install of the
ctgclient artifact, and convert that system scope to
perhaps make a request to to surefire plugin to allow addition of classpath
-D
On 2/23/07, Dan Tran [EMAIL PROTECTED] wrote:
build your test jar in a separate project, and run it in a test project
with those resources
-D
On 2/23/07, apill [EMAIL PROTECTED] wrote:
I've had the same
The greeting field should be declared inside the class.
Interesting, I would have expected a Java compile error instead of a
qdox exception.
..David..
-Original Message-
From: Kiruba Suthan [mailto:[EMAIL PROTECTED]
Sent: Friday, February 23, 2007 12:26 AM
To: users@maven.apache.org
I Remy,
Thanks for the reply. I had to link it to a phase explicitly to get it to
deploy the zip when performing an install or release. I have tried removing
the specific lifecycle execution, but this does not alleviate the issue.
Thanks,
Todd
On 2/23/07, Rémy Sanlaville [EMAIL PROTECTED]
It seems this will solve my problem if I find a way to pass the
properties to a schemaexport-task run from the antrun-plugin.
It is a quite simple:
configuration
tasks
ant antfile=build.xml
property
file={basedir}/project/relative/path/to/properties.file /
I figured it out, it seem to be a source control problem. I already had the
tag mortgageware-1.0.0, I thought if I re-created the tag during my
deployment testing, it would simply overwrite the previous tag in
subversion, however that is not the case. If I explicitly delete the tag
from
I have a pom.xml with basic distributionManagement settings which should
copy an artifact to a directory on my local filesystem, however, no artifact
is being sent there. The child id element value under
distributionManagement section matches an id value in my settings.xml
file.
Why is this
Greets,
How do I go about setting the value of a variable from 1 plugin and passing
that variable to another plugin. If I'm being vague, here are the
details:-) I have a custom plugin (buildtools-tag-plugins) where I set
the buildNumber instance variable to the current date and time and then
Something is wrong with the current snapshot update policy:
I have a several projects going on concurrently; the first is intended to be
a common components type project for the others, all are in concurrent
development. The upstream project SNAPSHOT jars are *never* getting
downloaded. I think
Hi all,
I cannot generate xdoclet from my EJB classes because my classes extend
one class from an external jar, that needs to be in classpath when the
ejbdoclet task is defined. How do I do this in the m2 xdoclet plugin
configuration?
Here is my actual plugin configuration:
Hi, I've added the Cobertura plugin to my pom.xml build, using the examples
at:
http://mojo.codehaus.org/cobertura-maven-plugin/usage.html
However, when I run 'mvn clean site', it shows that I have 100% line
coverage. I know for certain that all of the methods in our DAOs are not
exercised.
btw, my plugin definition in reporting is:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdcobertura-maven-plugin/artifactId
/plugin
Brian
--
View this message in context:
All (but Brett in particular, I think),
I'm trying to test some SQL queries in my EJB3/JPA app. To do this, I'd
like for my unit tests to run against an in-memory Hypersonic database.
I configured a persistence unit appropriately in
src/test/resources/META-INF/persistence.xml, but alas Surefire
On 2/23/07, bkbonner [EMAIL PROTECTED] wrote:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdcobertura-maven-plugin/artifactId
/plugin
mvn clean by default doesn't clean the
Sounds like simply a bug in Cobertura. Submit a unit test and someone
will surely take a look at it.
Wayne
On 2/23/07, bkbonner [EMAIL PROTECTED] wrote:
btw, my plugin definition in reporting is:
plugin
groupIdorg.codehaus.mojo/groupId
I am trying to convert a project from Maven1 to Maven2. Should be simple,
but I am getting a ClassNotFoundException on the following line in my code
when running JUnit tests through Maven:
XMLReaderFactory.createXMLReader(org.apache.xerces.parsers.SAXParser)
This class is in xerces-2.4.0.jar, I
Since the Cobertura plugin does not properly execute 'clean' by default,
add the following declaration in build to bind its 'clean' goal:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdcobertura-maven-plugin/artifactId
executions
execution
Hello,
You may want to try the following configuration
build
!-- indique les plugin qui seront utilisés dans le projet lors de la
compilation --
plugins
!-- clean coverage data before collecting --
plugin
artifactIdcobertura-maven-plugin/artifactId
Hi to all,
Following some discussions on the agile-testing mailing list, I
revived an old project of mine named Patchwork, that aims to provide a
general purpose and extensible code coverage framework. In the spirit
of release early, release often, I just released first public
version of this
On 2/20/07, Dennis Lundberg [EMAIL PROTECTED] wrote:
Roland Asmann skrev:
Hi,
I want to write an APT document, split over several files.
Yes, I'd like to do that as well.
Please see this link for more info on this subject:
http://maven.apache.org/doxia/format.html
Thanks for the
There is some other version of xerces in your classpath?
Kind Regards,
On 2/23/07, Siegmann Daniel, NY [EMAIL PROTECTED] wrote:
I am trying to convert a project from Maven1 to Maven2. Should be simple,
but I am getting a ClassNotFoundException on the following line in my code
when running
Hi,
It's perhaps a cray question, but why not... I'ts a question involving the
compiler of maven2.
I have one Project, with a lot of classes. Some class use another class of
the same Project. So they are classes dependencies. It work's fine. I
compile with maven, no problems.
Now, if i compile a
use version2.0/version
latest 2.1 is bad, and it should be taken out of repo1
-D
On 2/23/07, Arnaud Bailly [EMAIL PROTECTED] wrote:
Hello,
You may want to try the following configuration
build
!-- indique les plugin qui seront utilisés dans le projet lors de la
compilation --
plugins
Thank you all for the suggestions. I apologize, but I am new to running
cobertura. I looked at the msgs in the log and they indicated that they
didn't have instrumentation for the classes in question.
[cobertura] INFO [main] net.sourceforge.cobertura.reporting.html.HTMLReport
- D
ata file
OK, I'll revert back to 2.0, thanks for the tip.
dan tran wrote:
use version2.0/version
latest 2.1 is bad, and it should be taken out of repo1
-D
On 2/23/07, Arnaud Bailly [EMAIL PROTECTED] wrote:
Hello,
You may want to try the following configuration
build
!-- indique les
Hi
Doesn't maven require all the direct dependencies to be mentioned
explicitly in the pom or parent poms. Direct dependency means those are
required for compilation.
But in my case, one of the dependency required for compilation is set as
transitive.
Example, my component A needs C to compile.
No this will not error out. Transitive dependencies are added to the compile
classpath, so compilation will succeed.
However, it is best practice to explicitly declare all direct dependencies for
a project.
I think the *typically* in your reference refers to just this case. Typically a
How do you run a plugin the parent pom only once and have its configuration
inherited by its children. I'm using the maven-buildnumber-plugin in my
parent pom and when I run my build, this plugin gets executed on every
child pom and I end up with different buildNumber ID.
plugin
Any idea ?
$ mvn dependency:build-classpath
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'dependency'.
[INFO]
[ERROR] BUILD FAILURE
[INFO]
According to
http://maven.apache.org/plugins/maven-dependency-plugin/usage.html the
build-classpath goal is new, since 2.0-alpha-2. That version is not
available on ibiblio yet, only 2.0-alpha-1 is. Looks like you will have
to check out the source code and build it if you need that goal.
If you
54 matches
Mail list logo