Re: code re-use (svn commit: r473412)

[Brett Porter <br...@apache.org>]

John,

There's a lot of stuff there. Can you write a doc for how to use it?  
I can't really grok what all the local repository shuffling etc is  
meant for. And mangling POMs for testing sounds like a bad thing :)

Also, should it be part of the existing testing harness?

A lot of this code also appears like it could land elsewhere (the  
invocation stuff in there seems fairly generic).

We very seriously need to start consolidating and making our code  
accessible to other developers rather than churning out module after  
module into the sandbox, I think.

- Brett

On 11/11/2006, at 5:25 AM, jdcasey@apache.org wrote:

> Author: jdcasey
> Date: Fri Nov 10 10:25:56 2006
> New Revision: 473412
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=473412
> Log:
> Creating new project to stage plugin artifacts to a testing  
> localRepo, execute maven builds via the maven-invoker, and other  
> similar things used to test plugin projects.
>

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

Re: code re-use (svn commit: r473412)

[John Casey <ca...@gmail.com>]

I have every intention of documenting and releasing this for use in plugin
integration-testing. I'm not sure why we'd put this in the testing harness,
as it's a very different type of testing that this enables. As for mangling
the pom, I'm only doing at most two things:

1. changing the version to a known value, so you can make absolute reference
to a plugin-and-mojo when executing a build, or when referencing the plugin
in a test POM.

2. turning off surefire, for cases where the tests are actually run in the
unit-testing phase of the build (otherwise, it'd wind up in a recursive loop
when it tries to package and stage the plugin jar to the test
local-repository).

I only just got this code fully working today, so I haven't had the time to
write up documentation yet...but I will be documenting this, as I think it's
going to be a key part of my own plugin-testing strategy going forward. It
simplifies things that I'm already doing in the assembly plugin, and keeps
the local repository clean in the process.

I've got several new libraries in the sandbox, I know. Everything that I've
put out there - with the exception of this last library - is well-tested and
just needs some overview documentation. And, all of it is in use somewhere
in the assembly plugin, the Buckminster integration I'm working on, or the
eclipse plugin...so it's not like this stuff is of theoretical use.

-j

On 11/10/06, Brett Porter <br...@apache.org> wrote:
>
> John,
>
> There's a lot of stuff there. Can you write a doc for how to use it?
> I can't really grok what all the local repository shuffling etc is
> meant for. And mangling POMs for testing sounds like a bad thing :)
>
> Also, should it be part of the existing testing harness?
>
> A lot of this code also appears like it could land elsewhere (the
> invocation stuff in there seems fairly generic).
>
> We very seriously need to start consolidating and making our code
> accessible to other developers rather than churning out module after
> module into the sandbox, I think.
>
> - Brett
>
> On 11/11/2006, at 5:25 AM, jdcasey@apache.org wrote:
>
> > Author: jdcasey
> > Date: Fri Nov 10 10:25:56 2006
> > New Revision: 473412
> >
> > URL: http://svn.apache.org/viewvc?view=rev&rev=473412
> > Log:
> > Creating new project to stage plugin artifacts to a testing
> > localRepo, execute maven builds via the maven-invoker, and other
> > similar things used to test plugin projects.
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>