Hi,
I am trying Integration testing for the first time in Maven.
I need to write a profile to integrate test dependencies into build and
deploy build locally and then run integration tests with Clover ON for code
coverage.
Any examples or ideas on achieving the same?
Thanks and regards
Raju
--
I simply misspoke. Cobertura requires site to run so the site is
generated, including the cobertura report.
Wayne
On 3/25/07, Baz <[EMAIL PROTECTED]> wrote:
After I have done that, "mvn site", seems invoke cobertura but not
"mvn package", am i doing anything wrong?
On 3/25/07, Baz <[EMAIL PROT
After I have done that, "mvn site", seems invoke cobertura but not
"mvn package", am i doing anything wrong?
On 3/25/07, Baz <[EMAIL PROTECTED]> wrote:
It seems like section 2 and 3 can be overlayed right? Meaning adding
from section 3 to section 2, then put it into build section in
pom.xml?
O
It seems like section 2 and 3 can be overlayed right? Meaning adding
from section 3 to section 2, then put it into build section in
pom.xml?
On 3/25/07, Baz <[EMAIL PROTECTED]> wrote:
Fay, sorry if i am being "slow"...
I see three sections in
http://mojo.codehaus.org/cobertura-maven-plugin/usa
Fay, sorry if i am being "slow"...
I see three sections in
http://mojo.codehaus.org/cobertura-maven-plugin/usage.html
1. Do i put section 1, "basic cobertura configuration" in reporting
section of pom.xml?
2. Section 2, "Configuring Instrumentation" in build section of pom.xml?
3. Section 3, "Co
Sorry, my fuzziness.
Strictly a corporate repo.
-John R.
On Sun, 2007-03-25 at 20:56 -0600, Wayne Fay wrote:
> Depends on what kind of repo you're deploying to...
>
> If you just want to have Maven2 download and install a plugin (into
> your local machine repo) so you can use it, just add it t
All,
What is the best practice for handling build outputs, reports and
archives? Here are the brief environments:
1. Build scheduling systerm such as CruiseControl.
2. Maven 2.0.
3. #1 and #2 running nightly, continuous and ad-hoc builds.
Outputs:
1. Build tree.
2. Build outputs.
3. Junit outp
No, this is not the correct way.
You need both the node in the section as well as the
instrumentation node in the section.
Additionally, you should run "mvn package". By specifying the
cobertura plugin in the pom, it will automatically run cobertura at
the proper time.
Wayne
On 3/25/07, Baz
Fay, Vincent,
Sorry for the repeated questions. I am just new to maven. Yes i am
adding the following lines, then run "mvn cobertura:cobertura". Is it
the correct way? Is there a goal that include build, report and
deploy?
The lines added to pom.xml:
org.codehaus.mojo
You can most likely build what you need using the assembly plugin.
Wayne
On 3/25/07, Valerio Schiavoni <[EMAIL PROTECTED]> wrote:
maybe you can write your own archetype.
see if this is what you want to do:
http://maven.apache.org/guides/mini/guide-creating-archetypes.html
and when you say: d
Depends on what kind of repo you're deploying to...
If you just want to have Maven2 download and install a plugin (into
your local machine repo) so you can use it, just add it to your
pom.xml and Maven will automatically take care of things. If you're
behind a proxy, you need to configure the pro
As suggested by Vincent, the plugin docs are the place to find the
answers you seek...
http://mojo.codehaus.org/cobertura-maven-plugin/usage.html
http://maven.apache.org/plugins/maven-clover-plugin/usage.html
Wayne
On 3/25/07, Baz <[EMAIL PROTECTED]> wrote:
Vincent,
Thank you for your reply.
Hi community,
I uploaded a new SNAPSHOT of the 1.1 RC1 here :
http://people.apache.org/repo/m1-snapshot-repository/maven/distributions/20070326/
This SNAPSHOT is a little bit special because I replaced all snapshots by
timestamped dependencies.
With this, maven startup will be enormously acceler
More on this.
If you try maven deploy:deploy-file with just this setup, it will fail
(unless the user your running happens to be the same as the remote
repo). The reason is that the comand line, deploy:deploy-file does not
have an option to set the user. The work around for this entails an
addi
Vincent,
Thank you for your reply. I looked through the page, got some idea in
including new plugin. However, I will need to know the correct
groupId, artifactId right? Cobertura for m2 seems to be in another
website, http://repo1.maven.org/maven2/cobertura/cobertura/
So my question now is: What
Hi,
On Mar 25, 2007, at 11:47 PM, Baz wrote:
Hi,
How can I run test code coverage tools as part of my build? What
changes do i need to make in the pom.xml?
I ran "mvn cobertura:cobertura" and seems like it is generating the
reports.
Please advise.
You can check the plugin documentation
Hi,
How can I run test code coverage tools as part of my build? What
changes do i need to make in the pom.xml?
I ran "mvn cobertura:cobertura" and seems like it is generating the reports.
Please advise.
Thanks.
B.
-
To unsub
I use it without pb. What is your windows?
Jay Goldman a écrit :
mvn.bat does not appear to work ... it creates a command line with
double-quotes, e.g.,
java ... "-Dxxx=yyy" ...
which the java exe does not support. That is, the dos command processor
does not remove the double-quotes (as linu
related JIRA
http://jira.codehaus.org/browse/MRELEASE-100
please vote
-D
On 3/25/07, Tom Huybrechts <[EMAIL PROTECTED]> wrote:
I have a very simple patch for the release-manager from trunk. It
let's you specify defaults for the release version and the new
version. Combined with -B you can c
mvn.bat does not appear to work ... it creates a command line with
double-quotes, e.g.,
java ... "-Dxxx=yyy" ...
which the java exe does not support. That is, the dos command processor
does not remove the double-quotes (as linux/unix shells do).
If I remove the double-quotes mvn.bat work
maybe you can write your own archetype.
see if this is what you want to do:
http://maven.apache.org/guides/mini/guide-creating-archetypes.html
and when you say: directory structure, you mean only the directory or
also files within them ?
On 3/25/07, Rahamim, Zvi (Zvi) <[EMAIL PROTECTED]> wrote
I have a very simple patch for the release-manager from trunk. It
let's you specify defaults for the release version and the new
version. Combined with -B you can completely automate your release.
These are the properties you need to set:
-Dmaven.release.version=
-Dmaven.release.new=
start of p
Hi all,
I have a very interesting issue with M2 tests...
The project structure looks like this:
Parent-1.0-alpha-3-SNAPSHOT
+A-1.0-alpha-3-SNAPSHOT
+B-1.0-alpha-3-SNAPSHOT
A-1.0-alpha-3-SNAPSHOT depends on B-1.0-alpha-2 (not on the SNAPSHOT!)
B-1.0-alpha-3-SNAPSHOT has some cha
23 matches
Mail list logo