You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Kristian Rosenvold <kr...@gmail.com> on 2010/01/05 13:47:11 UTC

Junit

I make the occasional submissions to the junit project, and I wanted to
submit a pom.xml that'd convert it into a proper maven project.

My real question is what/if anything should be done to the groupId of junit.
it should probably be org.junit but has since "the beginning of time" been
just junit. I know at least surefire would need to be updated if the
artifact id changed. I thought I'd put something into the pom.xml I submit
to them, I'm just not sure what..

I don't know who actually publishes junit to the repos, but 4.8 and 4.8.1
have been released. If you vote for the following junit issue we might be
able to make them release 4.9 themselves;

http://github.com/KentBeck/junit/issues#issue/66

Kristian

Re: Junit

Posted by Benjamin Bentmann <be...@udo.edu>.
Justin Edelson wrote:

> I think the problem Kristian is identifying is that the junit:junit group
> and artifact ids are hard-coded in the SurefirePlugin class. Relocation
> won't help with this AFAICT.

It's already configurable [0] and could probably be extended to 
recognize the new ids by default as well in future versions.


Benjamin


[0] 
http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#junitArtifactName

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Junit

Posted by Justin Edelson <ju...@gmail.com>.
On Tue, Jan 5, 2010 at 9:15 AM, Peter Lynch <pe...@peterlynch.ca> wrote:

> On Tue, Jan 5, 2010 at 7:47 AM, Kristian Rosenvold <
> kristian.rosenvold@gmail.com> wrote:
>
> > it should probably be org.junit but has since "the beginning of time"
> been
> > just junit. I know at least surefire would need to be updated if the
> > artifact id changed. I thought I'd put something into the pom.xml I
> submit
> > to them, I'm just not sure what..
> >
> > I guess you mean adding a relocation element to their 'old' pom?
> http://maven.apache.org/pom.html#Relocation
>
> I think the problem Kristian is identifying is that the junit:junit group
and artifact ids are hard-coded in the SurefirePlugin class. Relocation
won't help with this AFAICT.

Justin

Re: Junit

Posted by Peter Lynch <pe...@peterlynch.ca>.
On Tue, Jan 5, 2010 at 7:47 AM, Kristian Rosenvold <
kristian.rosenvold@gmail.com> wrote:

> I make the occasional submissions to the junit project, and I wanted to
> submit a pom.xml that'd convert it into a proper maven project.
>
> My real question is what/if anything should be done to the groupId of
> junit.
> it should probably be org.junit but has since "the beginning of time" been
> just junit. I know at least surefire would need to be updated if the
> artifact id changed. I thought I'd put something into the pom.xml I submit
> to them, I'm just not sure what..
>
> I guess you mean adding a relocation element to their 'old' pom?
http://maven.apache.org/pom.html#Relocation


> I don't know who actually publishes junit to the repos, but 4.8 and 4.8.1
> have been released. If you vote for the following junit issue we might be
> able to make them release 4.9 themselves;
>
> http://github.com/KentBeck/junit/issues#issue/66
>
> Kristian
>