Yes, that's the content - I'm looking for the original with the
change history.
On 05/08/2007, at 1:10 PM, Brian E. Fox wrote:
Is it different than what's at the bottom of the page?
"As identified in Repository Security by several authors, there is a
need to improve the security of the Maven
Is it different than what's at the bottom of the page?
"As identified in Repository Security by several authors, there is a
need to improve the security of the Maven repository ecosystem. We have
an opportunity to encourage users to consider security (and later other
aspects such as licensing) by
Hi Jason,
Is there a way we could get back the original Repository Security
Improvements page I made (to keep the change history), and set that
as the proposal? I had already taken into account the 3 articles from
Nat, John and Julian when I wrote mine, and they're best left as a
document
The client should take care of this. Not sure who put this in but
it's the client's responsibility. The only place we're using this is
in our ITs and our test case can take care of this. The invoker
shouldn't inherently care about whether something is cleaned or not.
Just take it out comple
"Brian E. Fox" <[EMAIL PROTECTED]> writes:
> Take a look at the maven-archetypeng-plugin (currently in mojo/sandbox) in
> the plugin piece you will see the lifecycles.
>
Thanks for the pointer.
As already said, the net conclusion is that one can define its own
lifecycle, with mojo bindings as sh
