Not at present, but its a good idea. Please make a feature request for
listeners.
However, if you want both success and failure moved to the shared
filesystem - maybe you should just set the working directory to the
shared filesystem?
- Brett
Gautham Pamu wrote:
Hi Everyone,
I am fairly new
It means that test can be reused in other projects, so you can extend
or use them from the tests in that project. What is the point of
runing the same tests again in another project?
On 3/31/06, Pablo [EMAIL PROTECTED] wrote:
Hello everyone
Is it possible to run tests using
+1 (user only)
raphaël
2006/3/31, Brett Porter [EMAIL PROTECTED]:
Vote open for 72 hours, based on:
maven-surefire-report-plugin 2.0-20060331.032648-2 (r390304)
[ ] +1
[ ] +0
[ ] -1
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11222styleName=Htmlversion=12481
*
On 3/31/06, Carlos Sanchez [EMAIL PROTECTED] wrote:
It means that test can be reused in other projects, so you can extend
or use them from the tests in that project. What is the point of
runing the same tests again in another project?
For example when you want to test some implementations of
-Original Message-
From: Brett Porter (JIRA) [mailto:[EMAIL PROTECTED]
Sent: vendredi 31 mars 2006 01:01
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (MNG-2184) Possible problem with @aggregator
and forked lifecycles
[snip]
This only happens as part of the site, because it
+1
FYI no regression bug discovered on my projects
Vincent
2006/3/30, John Casey [EMAIL PROTECTED]:
Hi,
It appears I introduced two regressions in the 2.0.3 release. See
MNG-2054 and MNG-2186 for more information. Since they have potentially
huge impact on our users (esp. MNG-2186), I'd
+1
Vincent
2006/3/31, Brett Porter [EMAIL PROTECTED]:
Please amend that to 2.0-20060331.052706-3 (r390329).
- Brett
Brett Porter wrote:
Vote open for 72 hours, based on:
maven-war-plugin 2.0-20060331.041208-2 (r390317)
[ ] +1
[ ] +0
[ ] -1
+1
Vincent
2006/3/30, Brett Porter [EMAIL PROTECTED]:
Vote open for 72 hours, based on:
maven-surefire-report-plugin 2.0-20060331.032648-2 (r390304)
[ ] +1
[ ] +0
[ ] -1
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11222styleName=Htmlversion=12481
* [MSUREFIREREP-2] -
On Mar 31, 2006, at 05:57, Tomasz Pik wrote:
On 3/31/06, Carlos Sanchez [EMAIL PROTECTED] wrote:
It means that test can be reused in other projects, so you can
extend or use them from the tests in that project. What is the
point of runing the same tests again in another project?
For
On Thu, 30 Mar 2006, John Casey wrote:
I'm tending towards -1, but I'll not vote just yet.
Please see MNG-2054 (still closed). I attached a sample project
that runs the same goals multiple times for a reactor project.
I'm not entirely sure that this is the exact same issue, since there's
just 1
Ok after discussing with Kenney here's the plan:
* A clover:instrument goal which forks a custom lifecycle and generate a
clover database
* All other mojos do not fork a lifecycle. This means users need to specify
the instrument goal in an execution in their pom
* The clover:check goal simply
Hi,
I finally was able to make heads and tails of the xdoc DTD as included
in the maven 1 xdoc plugin (thanks a lot for this, Lukas Arnaud!) . To
make XMLMind to automatically identify these files, we do need a DTD
public identifier. Do you already have one? Googling for this didn't
really help
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: vendredi 31 mars 2006 15:27
To: 'Maven Developers List'
Cc: 'Brett Porter'
Subject: RE: [jira] Commented: (MNG-2184) Possible problem with
@aggregator and forked lifecycles
Ok after discussing with Kenney
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: vendredi 31 mars 2006 17:51
To: 'Maven Developers List'
Cc: 'Brett Porter'
Subject: RE: [jira] Commented: (MNG-2184) Possible problem with
@aggregator and forked lifecycles
-Original Message-
Hi,
Just giving all devs a heads up that I discussed adding Milos as a
committer on Maven for his work on the embedder and the Netbeans plugin.
There were enough +1s on the PMC list to bring Milos in but wanted to
give other devs a chance to voice their opinion.
Milos has a very good
Hi Brett,
I had named it clover:report initially and I remember you changed it to
clover:clover. I really think that clover:report is better (more
self-explanatory).
What is the reason for the change you made? Can we change it?
Is there a goal aliasing feature implemented?
Thanks
-Vincent
+1
Brett Porter wrote:
Vote open for 72 hours, based on:
maven-surefire-report-plugin 2.0-20060331.032648-2 (r390304)
[ ] +1
[ ] +0
[ ] -1
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11222styleName=Htmlversion=12481
* [MSUREFIREREP-2] - test failures causes report not to be
+1
Brett Porter wrote:
Vote open for 72 hours, based on:
maven-war-plugin 2.0-20060331.041208-2 (r390317)
[ ] +1
[ ] +0
[ ] -1
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11150styleName=Htmlversion=12160
* [MWAR-1] - war:exploded removes content of .class files
* [MWAR-3] -
Hi,
For some reason I thought that the strictness in model parsing had been
turned off. I was playing around trying to add a custom/ element and
noticed it is still on.
Can we enable the lax parsing in order to make the POM extensible?
The POM will will still be validated at the object
Jason van Zyl wrote:
Hi,
For some reason I thought that the strictness in model parsing had been
turned off. I was playing around trying to add a custom/ element and
noticed it is still on.
Can we enable the lax parsing in order to make the POM extensible?
The POM will will still be
so, how do you gain access to the custom section? Would you have to
re-parse the whole pom? Also, would custom/ be subject to any sort of
inheritance, or would it simply be invisible to the project builder?
-john
Jason van Zyl wrote:
Jason van Zyl wrote:
Hi,
For some reason I thought that
No, there is none. The DTD is currently only available in SVN, it was
added in the 1.10 version of the maven-1 xdoc plugin which is not
released yet. As such, it is still work in progress, so I don't know if
it's a good idea to publish it at this point. However, as far as I'm
concerned, the
Hi Kenney,
I tried your test out, and all I can say is...weird. I'm not sure what
that's all about, but since it's not a regression, I'd personally like
to see it taken care of in 2.0.5 or 2.1, rather than hold up these two
large regressions being released. Dunno what you think, but I'm not
John Casey wrote:
so, how do you gain access to the custom section? Would you have to
re-parse the whole pom? Also, would custom/ be subject to any sort of
inheritance, or would it simply be invisible to the project builder?
Think the most convenient would to put the Xpp3DOM object in the
Hi, in fact it's not yet documented but the dtd is already online :
http://maven.apache.org/maven-1.x/plugins/xdoc/maven-xdoc.dtd
cheers
arnaud
On 3/31/06, Lukas Theussl [EMAIL PROTECTED] wrote:
No, there is none. The DTD is currently only available in SVN, it was
added in the 1.10 version
On Fri, 31 Mar 2006, Jason van Zyl wrote:
Some thoughts/ideas:
I didn't realize checking was on! You can specify multiple dependencies
sections etc, and it still works.
Also the namespace in the pom is not used.
The presence of the schema location tag is also ignored, but this is
usually the
John Casey wrote:
so, how do you gain access to the custom section? Would you have to
re-parse the whole pom? Also, would custom/ be subject to any sort of
inheritance, or would it simply be invisible to the project builder?
After some more chatting in IRC I think that if a custom/ element
Kenney Westerhof wrote:
On Fri, 31 Mar 2006, Jason van Zyl wrote:
Some thoughts/ideas:
I didn't realize checking was on! You can specify multiple dependencies
sections etc, and it still works.
Whoops.
Also the namespace in the pom is not used.
The presence of the schema location tag is
I'm getting test errors when I build MRM via 'mvn install'. I'm on OS
X, JDK 1.4, Maven 2.0.3.
Summary:
[INFO] Building Maven Repository Manager Artifact Applet
[INFO]task-segment: [install]
[INFO]
[INFO]
It requires 2.1-SNAPSHOT of the jar plugin fro the jar:sign goal. I've
deployed a new snapshot - hopefully this willl make it build out of the box.
- Brett
Henri Yandell wrote:
I'm getting test errors when I build MRM via 'mvn install'. I'm on OS
X, JDK 1.4, Maven 2.0.3.
Summary:
[INFO]
+1. Strict parsing is only on for projects you build, its off for poms
in the repository.
This should be a change on trunk only, and the model version should be
changed to 4.1.0, right? We need to now start looking into dealing with
projects differently based on the model version.
Given that
I think it might have been for consistency with m1, or I was going to
make them all consistent and then stopped.
There's no goal aliasing, but you can create another mojo that extends
the first and give it the original goal name.
- Brett
Vincent Massol wrote:
Hi Brett,
I had named it
Hey everyone,
I am noticing quite a few IT test failures on the latest SVN snapshot
from trunk, wondering if there are any refactorings/major changes taking
place??
Here's the bunch that failed:
69/100 passed
Failed tests: [it0099, it0092, it0089, it0088, it0087, it0086, it0077,
it0073,
Hi Everyone,
I am fairly new to continuum, I am using continuum for our daily builds. I
would like to copy the complete build (working copy directory include the
output directories generated by maven build) to a shared file system after
the builds fails/completes succesfully. Can you send me
Nope.
Rahul Thakur wrote:
Hey everyone,
I am noticing quite a few IT test failures on the latest SVN snapshot
from trunk, wondering if there are any refactorings/major changes taking
place??
Here's the bunch that failed:
69/100 passed
Failed tests: [it0099, it0092, it0089, it0088,
Rahul Thakur wrote:
Hey everyone,
I am noticing quite a few IT test failures on the latest SVN snapshot
from trunk, wondering if there are any refactorings/major changes taking
place??
Here's the bunch that failed:
69/100 passed
Failed tests: [it0099, it0092, it0089, it0088, it0087,
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: vendredi 31 mars 2006 00:26
To: Maven Developers List
Subject: Re: MavenProject.addArtifact()
That code looks fine, it also works in Cobertura. Can you get more
details about the dependency?
I got more
37 matches
Mail list logo
