Personally, I found the the shitty plugin easier to setup than others
plugin.
You just add it in your pom and it works. The counterpart is that there are
many less settings compared to others, but I thing that the ones added to
the shitty plugin are enough for a lot of plugins.
Another thing, why
>Am I right in thinking that right now it's using the
>"maven-plugin-testing-harness?" (I've never understood that either,
>though I haven't tried very hard.)
Yes. It actually works quite nicely. I'm having issues with not getting
the error code on windows, but this is a plexus-cli issue and n
+1
-Original Message-
From: Hervé BOUTEMY [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 13, 2007 2:06 PM
To: Maven Developers List
Subject: Re: [VOTE] Maven Ant Tasks 2.0.8 (take 2)
I still miss 2 PMC votes: anybody interested in MANTTASKS?
This time, I promise I won't cancel the vo
>AFAIK, shitty is similar to invoker, but does more : it install the
current
>artifact in local repo with version "testing" and invoke a maven build.
>Seems to be what the invoker it-test do. Shitty alos use groovy scripts
to
>test the result.
This is _exactly_ what the plugin testing harness (cu
Issue Subscription
Filter: Design & Best Practices (29 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
htt
worked for me but i had to use maven-shade trunk to build surefire-api
successfully
NOTE: i built on java6... java4 failed on the junit4 support
On Tue, 11 Dec 2007 14:18:51 Dan Tran wrote:
> No problem found in my build using 2.4 SNAPSHOT, good work. But I
> can't put it on production build th
On Thursday 13 December 2007, Brett Porter wrote:
> Sounds familiar now... should we continue to consider this a failure
> then until it is added?
I would say yes. You could disable it for the time being since we know
it doesn't build with 1.4.
Dan
>
> On 14/12/2007, at 2:00 PM, Daniel Kulp w
Sounds familiar now... should we continue to consider this a failure
then until it is added?
On 14/12/2007, at 2:00 PM, Daniel Kulp wrote:
On Thursday 13 December 2007, Brett Porter wrote:
is PMD JDK 5 only now?
Yes. But they are working on getting a retrotranslated version
submitted
t
On Thursday 13 December 2007, Brett Porter wrote:
> is PMD JDK 5 only now?
Yes. But they are working on getting a retrotranslated version submitted
to central the the plugin can use.
Dan
> - Brett
>
> On 14/12/2007, at 1:35 PM, [EMAIL PROTECTED] wrote:
> > Online report :
> > http://maven.z
is PMD JDK 5 only now?
- Brett
On 14/12/2007, at 1:35 PM, [EMAIL PROTECTED] wrote:
Online report :
http://maven.zones.apache.org/continuum/buildResult.action?buildId=38882&projectId=27
Build statistics:
State: Failed
Previous State: Failed
Started at: Fri 14 Dec 2007 02:35:26 +
Finished
Anyone know what caused this error? I see it on my macbook as well.
- Brett
On 14/12/2007, at 10:55 AM, [EMAIL PROTECTED] wrote:
Online report :
http://maven.zones.apache.org/continuum/buildResult.action?buildId=38854&projectId=55
Build statistics:
State: Failed
Previous State: Failed
Starte
On Thu, 13 Dec 2007 05:59:18 Benjamin Bentmann wrote:
> Mauro Talevi wrote:
> > firstly, nothing prevents us from releasing a 2.3.2 right after a 2.3.1.
>
> If an ordinary user may disturb:
> I really appreciate Mauro's attitude. For my taste, there could be more
> maintenance releases. Please cons
I still miss 2 PMC votes: anybody interested in MANTTASKS?
This time, I promise I won't cancel the vote :)
Hervé
Le lundi 10 décembre 2007, Hervé BOUTEMY a écrit :
> Hi,
>
> Following Maven release, I'd like to release (again) Maven Ant Tasks 2.0.8.
> Problem with dependencies order has been fixe
I've never used invoker or verifier, so still have to make my opinion.
I just had many issues configuring testing-harness with required maven
components : I added new feature to my mojos but tests cannot be updated due
to some new dependencies introduced that have no stub in testing-harness (or
no
olivier lamy wrote:
But this means we have to wait the end of the discussions before
releasing something ?
No, don't wait. I haven't voted (I've never used Maven Invoker Plugin)
but these discussions shouldn't hold up the vote.
+0, if that helps. [I haven't tried the new version, but I'm
nicolas de loof wrote:
shitty is a very simple way to it-test plugins.
So I've heard... But I've also heard good things about
maven-invoker-plugin. And I've said a lot of good things about
maven-verifier tests. Why use SHITTY and not one of the others?
Or, let me phrase my question a di
I check your take 2 at work, and i didn't find mistake.
+1
--
View this message in context:
http://www.nabble.com/-VOTE--Maven-Ant-Tasks-2.0.8-%28take-2%29-tp14260773s177p14322253.html
Sent from the Maven Developers mailing list archive at Nabble.com.
-
Daniel Kulp wrote:
Crap. Second time I've done this in the last couple weeks. :-( Why
the 1.5 javac doesn't flag these things with source/targe set to 1.4 is
beyond me. Eclipse doesn't even flag them when using 1.5 but project
is set to 1.4.
That said, I just figured out how to get the
One repo test use testing-harness.
Other ones require to have many maven stubs, and a Project with an
ArtifactHandler (for language == java check) that is not (yet) supported bu
maven-plugin-testing-harness.
shitty is a very simple way to it-test plugins.
2007/12/13, Dan Fabulich <[EMAIL PROTECT
The Maven team is proud of announcing the new release of the Maven Remote
Resources Plugin 1.0-beta-2 for Maven 2.
Release Notes - Maven 2.x Remote Resources Plugin - Version 1.0-beta-2
** Bug
* [MRRESOURCES-26] - NPE in remote-resources:process while
sorting orgs
* [MRRESOUR
Hi,
I know there is some discussions about invoker versus verifier etc...
But this means we have to wait the end of the discussions before releasing
something ?
Some of you have voted +1 on the first try.
Thanks,
--
Olivier
12 Dec 2007 18:13:38 -, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
>
> H
John Casey wrote:
On Dec 12, 2007, at 9:47 PM, Dan Fabulich wrote:
I tweak the test to add a MAVEN_OPTS environment variable, including the
-Xrunjdwp string. (It would be easy to add some sugar to Verifier and/or
Invoker to make this easier; I didn't want to go fooling around with the
Veri
On Dec 12, 2007, at 9:47 PM, Dan Fabulich wrote:
I tweak the test to add a MAVEN_OPTS environment variable,
including the -Xrunjdwp string. (It would be easy to add some
sugar to Verifier and/or Invoker to make this easier; I didn't want
to go fooling around with the Verifier, so I just c
Crap. Second time I've done this in the last couple weeks. :-( Why
the 1.5 javac doesn't flag these things with source/targe set to 1.4 is
beyond me. Eclipse doesn't even flag them when using 1.5 but project
is set to 1.4.
That said, I just figured out how to get the eclipse project to
nicolas de loof wrote:
I tried to look at maven-eclipse-plugin tests and was really confused on
it's testing framework complexity.
Am I right in thinking that right now it's using the
"maven-plugin-testing-harness?" (I've never understood that either,
though I haven't tried very hard.)
Wh
I understand. I had the same problem at the beginning.
When it works you can also check that you didn't brake the continuous
integration.
http://maven.zones.apache.org/continuum/buildResults.action?projectId=17&projectGroupId=2
For the Shitty plugin I'm in favor to use it (I also uses it in other
p
To be honest, my initial goal was to fix some Jira issues, but as some tests
fail on my environment its difficult to know if I introduced some new issues
or not.
I've attached a patch on MECLIPSE-101 as a proof of concept on moving
project-01 IT test to SHITTY.
2007/12/13, Arnaud HERITIER <[EMAI
Tests defined in the eclipse plugin have to be completely refactored.
With the shitty plugin why not.
I already opened several issues to separate unit and integration tests and
also to refactor the plugin itself.
Actually, I don't want to begin all those changes if we didn't finish to
apply/reject
Vincent Siveton wrote:
-1 due to compilation failure with jdk1.4 on tag.
http://rafb.net/p/jVfAXG92.html
Right - I thought the maven plugins parent POM would have fixed the
target/source JDK to 1.4.
I'd continue with vote (would avoid issuing another one) and fix JDK
compat before releasin
Hello
I tried to look at maven-eclipse-plugin tests and was really confused on
it's testing framework complexity.
What about moving thoses IT tests to src/it via the Shitty maven plugin (
http://mojo.codehaus.org/shitty-maven-plugin/usage.html)
I allready used it and found it simple to use and ve
-1 due to compilation failure with jdk1.4 on tag.
http://rafb.net/p/jVfAXG92.html
Vincent
2007/12/12, Mauro Talevi <[EMAIL PROTECTED]>:
> Following fixes, new version 1.0-alpha-15 has been staged for release.
> Please for vote for its release and to move this version of the sandbox
> (and start d
31 matches
Mail list logo
