Re: Relative path to local repository?

My gut is that the configuration in settings.xml should always be an absolute path. The way this user (in MECLIPSE-404) is using the configuration is simply an anti-pattern. Wayne On 3/18/08, Benjamin Bentmann <[EMAIL PROTECTED]> wrote: > Hi, > > the recent release of maven-eclipse-plugin:2.5 bro

[RESULT][VOTE] Release apache-jar-resource-bundle version 1.4

This vote passes: +1 binding: jvanzyl, brianf, olamy, vsiveton +1 non-binding: jdillon, mtalevi, dkulp Thanks! Dan On Monday 17 March 2008, Daniel Kulp wrote: > To comply with the latest requirements discussed on legal-discuss, we > need a new version of the apache-jar-resource-bundle. > > Th

[RESULT][VOTE] Release maven-shade-plugin 1.0.1

This vote passes: +1 binding from jvanzyl, brianf, jdcasey, vsiveton +1 non-binding from dkulp, malevi, jdillon No other votes. Thanks! Dan On Monday 17 March 2008, Daniel Kulp wrote: > There is a critical bug in 1.0 where the resulting merged NOTICE files > may not be correct. This release

[RESULT][VOTE] Release maven-remote-resources version 1.0

This vote passes: +1 binding from jvanzyl, olamy, vsiveton +1 non-binding from dkulp, jdillon Thanks! Dan On Monday 17 March 2008, Daniel Kulp wrote: > Several projects are sucessfully using remote-resources so it's time > pull it out of beta and do the 1.0 release. :-) > > This version provi

[jira] Subscription: Design & Best Practices

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-3313NetBeans projects, more than ant project, more than fre

Re: import scope questions

Tom Huybrechts wrote: I read about the new import scope in the 2.0.9 release notes. This looks very promising to me, but I have a questions on the details of how this works. I looked in the mailing list history for discussions on this feature, but couldn't find anything. There is a wiki page, b

RE: import scope questions

>The design pattern I would recommend is one where the pom being imported >contains nothing but the managed dependencies, i.e. it defines a library >of related artifacts. You wouldn't use such a pom in any other way so I >don't see this as a compatibility problem. But any poms that are consu

Re: import scope questions

Brian E. Fox wrote: I read about the new import scope in the 2.0.9 release notes. This looks very promising to me, but I have a questions on the details of how this works. I looked in the mailing list history for discussions on this feature, but couldn't find anything. There is a wiki page, but i

Re: Eclipse plugin .factorypath generation

Yes Google does.. Thanks Brian, I guess mvnrepository doesn't index snapshot repos. On Thu, Mar 20, 2008 at 2:49 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > Google knows all: > http://www.google.com/search?sourceid=mozclient&ie=utf-8&oe=utf-8&q=apt- > maven-plugin

RE: Eclipse plugin .factorypath generation

Google knows all: http://www.google.com/search?sourceid=mozclient&ie=utf-8&oe=utf-8&q=apt- maven-plugin Looks like it's at codehaus. -Original Message- From: Evan Worley [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2008 5:40 PM To: Maven Developers List Subject: Re: Eclipse plugin

Re: Eclipse plugin .factorypath generation

Does anyone know where the apt-maven-plugin can be found? mvnrepository.comhas no entries for it. Thanks, Evan On Thu, Mar 20, 2008 at 12:07 PM, Evan Worley <[EMAIL PROTECTED]> wrote: > Very cool! Thanks for sharing mark. > > > On Thu, Mar 20, 2008 at 1:47 AM, Mark Hobson <[EMAIL PROTECTED]> wr

RE: [Pre-Vote] release maven 2.0.9

We uncovered a regression in 2.0.9 somehow related to the plugin tools: http://jira.codehaus.org/browse/MNG-3473 John is helping me to track it down, but we'll end up respinning this release again. -Original Message- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19,

Re: Eclipse plugin .factorypath generation

Very cool! Thanks for sharing mark. On Thu, Mar 20, 2008 at 1:47 AM, Mark Hobson <[EMAIL PROTECTED]> wrote: > I was curious about this too. Note that there is a goal in the > apt-maven-plugin that aims to achieve this: > > http://mojo.codehaus.org/apt-maven-plugin/eclipse-mojo.html > > Mark > >

RE: surefire and testng integration issues with surefire-2.4.2

I think part of the disconnect might be in the understanding of what TestNG calls a "test". A test, in testNG terminology, is a logical grouping of testMethods within a suite. A single "test" will span all of the classes in the src/test/java directory unless something is done to break them up. T

RE: surefire and testng integration issues with surefire-2.4.2

Thanks Dana for the nice summary. Dan, one thing I did not take into account is that my company my be using TestNG in a different way, such as group of tests, that allows this to work for me and would cause different output for a "standard" user. Think this was a good summary that helped to point

RE: surefire and testng integration issues with surefire-2.4.2

Jason Chaffee wrote: Thanks Dan, I will take a look at it and make sure we are clear and there aren't any misunderstandings before I make any more comments. :) For future reference, this is SUREFIRE-457. Vote for it if you like, but as far as I know, we can't fix it on the Surefire side (wi

RE: surefire and testng integration issues with surefire-2.4.2

Thanks Dan, I will take a look at it and make sure we are clear and there aren't any misunderstandings before I make any more comments. :) -Original Message- From: Dan Fabulich [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2008 10:43 AM To: Maven Developers List Cc: Maven Users Lis

Re: surefire and testng integration issues with surefire-2.4.2

Dan Fabulich wrote: Jason Chaffee wrote: I did not run your project. Well, try it and get back to me. You can use that as a starting point for reproducing the effect you actually want. Oops, you can't, because the mailing list software stripped my attachment. You can get a copy here:

Re: surefire and testng integration issues with surefire-2.4.2

Jason Chaffee wrote: I did not run your project. Well, try it and get back to me. You can use that as a starting point for reproducing the effect you actually want. -Dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For add

Re: surefire and testng integration issues with surefire-2.4.2

Jason Chaffee wrote: Maybe our disconnect is about callbacks after the class vs. the method. That could be where the misunderstanding is coming from. Sure, that could be. I claim that logging per-method is *way* too much logging. Don't you agree? In JUnit we can log per-class or per-metho

RE: Re: surefire and testng integration issues with surefire-2.4.2

I did not run your project. I created my own listener and ran it in testng, outside of maven in a test environment at my company. I will have to create a different one before I can share it with a wider audience and I would like to actually test it in maven and with surefire to see if the behavio

RE: RE: Re: surefire and testng integration issues with surefire-2.4.2

Maybe our disconnect is about callbacks after the class vs. the method. That could be where the misunderstanding is coming from. -Original Message- From: Jason Chaffee [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2008 10:11 AM To: [EMAIL PROTECTED]; Maven Developers List Cc: Maven

RE: Re: surefire and testng integration issues with surefire-2.4.2

I did try it. I created my own listener and got the exact output I was looking for. I am not sure where our disconnect is here, but we certainly are seeing two different things with respect to the code. -Original Message- From: Dan Fabulich [mailto:[EMAIL PROTECTED] Sent: Thursday, Marc

RE: surefire and testng integration issues with surefire-2.4.2

Yeah, I have no problem writing my own. However, if this is to be expected of TestNG users to get similar output as previous versions of surefire, then it should be WELL documented as such. My issue is that the behavior changed between surefire versions. This caused all kinds of confusion for de

RE: import scope questions

>I read about the new import scope in the 2.0.9 release notes. This >looks very promising to me, but I have a questions on the details of >how this works. >I looked in the mailing list history for discussions on this feature, >but couldn't find anything. There is a wiki page, but it has few >detai

RE: surefire and testng integration issues with surefire-2.4.2

I have recently been dealing with a similar issue. I wanted Junit style reports and did not want to use ant run to run the JunitConverter task, so I added reportng as a test scoped dependency and configured a listener. As an interim solution, you could write a listener that does what you want.

import scope questions

I read about the new import scope in the 2.0.9 release notes. This looks very promising to me, but I have a questions on the details of how this works. I looked in the mailing list history for discussions on this feature, but couldn't find anything. There is a wiki page, but it has few details (and

Re: maven-eclipse-plugin problems with jee5 ears coming

Hi, i also agree with Arnaud that this would be great but i think it is almost not do-able. I tried for example to use the plexus manifest generator (= service reuse) but failed because the dependencies are not yet resolved (or something simulator) when the eclipse plugin starts. Now to the diffi

RE: [Pre-Vote] release maven 2.0.9

There's already a jira for it, scheduled for 2.1 as it introduces new elements to the poms. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of nicolas de loof Sent: Thursday, March 20, 2008 4:07 AM To: Maven Developers List Subject: Re: [Pre-Vote] release ma

Re: maven-eclipse-plugin problems with jee5 ears coming

Richard, I've noticed the plugin does invoke ear:generate-application-xmlgoal - may be the lifecycle isn't a problem here? I agree with Arnaud, that way we could keep up with plugins and be more consistent. Siar

Re: maven-eclipse-plugin problems with jee5 ears coming

We could also think to extract some part of ear/war/... plugins to reuse some services throught a shared library Arnaud On Thu, Mar 20, 2008 at 9:03 AM, Richard van Nieuwenhoven <[EMAIL PROTECTED]> wrote: > Hi, > > The problem here is the phase in the life cycle.. The best thing would > be to u

surefire and testng integration issues with surefire-2.4.2

I brought this up in the past the maven guys were adamant that they were not able to get per test information to output on the console unless testng changed. I felt all along that this was not correct and I finally had a chance to look into it. Surefire could simply register a listener to get cal

surefire and testng integration issues with surefire-2.4.2

I brought this up in the past the maven guys were adamant that they were not able to get per test information to output on the console unless testng changed. I felt all along that this was not correct and I finally had a chance to look into it. Surefire could simply register a listener to get cal

Re: Eclipse plugin .factorypath generation

I was curious about this too. Note that there is a goal in the apt-maven-plugin that aims to achieve this: http://mojo.codehaus.org/apt-maven-plugin/eclipse-mojo.html Mark On 19/03/2008, Evan Worley <[EMAIL PROTECTED]> wrote: > Hi All, > > I was wondering who the active developers are on the m

Re: maven-eclipse-plugin problems with jee5 ears coming

Hi, The problem here is the phase in the life cycle.. The best thing would be to use the generated application.xml from the ear plugin but thats generated very late in the packaging phase. The eclipse plugin runs in a very early phase to be able to generate eclipse config files also for broken pro

Re: Maven's future repository support

When discussing about mirroring, you could also consider http://www.metalinker.org/ Also, the full control of the repository (or mirrors) you use is a critical security feature. You must be sure that you can trust the repositories you use, and the authenticity of the jar that are on this reposito

Re: [Pre-Vote] release maven 2.0.9

I agree this should be fixed, as there is no section in POM to force the report plugin versions and the element is optional in . Nico. 2008/3/20, Geoffrey De Smet <[EMAIL PROTECTED]>: > > The reporting section ignores pluginManagement, which is said to be a > feature, but IMHO it violates the p

Re: [Pre-Vote] release maven 2.0.9

The reporting section ignores pluginManagement, which is said to be a feature, but IMHO it violates the principle of least suprise and it's a bug. With kind regards, Geoffrey De Smet Jörg Schaible schreef: [EMAIL PROTECTED] wrote: nicolas, I won't speak for Brian, but I thought his intention

RE: [Pre-Vote] release maven 2.0.9

[EMAIL PROTECTED] wrote: > nicolas, > > I won't speak for Brian, but I thought his intention was to lock down > plug-ins that only affect the build cycle. Shouldn't the generated reports of a release also be reproducable? However, anone noticed that a plugin with a locked version in the pluginMa