This seems to line up with what other plugins are doing, and the
terminology seems clear as well, so this sounds like the best choice.
It just took us a while to realize that. ;-)
Wayne
On 9/19/07, Mark Hobson [EMAIL PROTECTED] wrote:
On 18/09/2007, Paul Gier [EMAIL PROTECTED] wrote:
I think
On 18/09/2007, Paul Gier [EMAIL PROTECTED] wrote:
I think that's what I meant ;)
Anyway, the surefire report plugin uses report and report-only to do something
similar, so that seems consistent with Brian's suggestion of using analyze and
analyze-only.
Great, I think we're all in agreement
On 17/09/2007, Brian E. Fox [EMAIL PROTECTED] wrote:
Actually I missed that. Mark, what's the problem with analyze forking
the build if there is already a justAnalyze that doesn't?
Okay, I like Max's suggestion of following the assembly plugin's
convention. I'll put dependency:analyze back to
On 18/09/2007, Mark Hobson [EMAIL PROTECTED] wrote:
Okay, I like Max's suggestion of following the assembly plugin's
convention. I'll put dependency:analyze back to @execute
phase=test-compile and add dependency:analyze-attached with
@phase=verfiy, which will replace the previous JustAnalyze
Mark Hobson wrote:
On 17/09/2007, Brian E. Fox [EMAIL PROTECTED] wrote:
Actually I missed that. Mark, what's the problem with analyze forking
the build if there is already a justAnalyze that doesn't?
Okay, I like Max's suggestion of following the assembly plugin's
convention. I'll put
On 18/09/2007, Max Bowsher [EMAIL PROTECTED] wrote:
I think the convention really only goes as far as having two different
names in order to allow @execute and [EMAIL PROTECTED] versions.
attached makes sense for the assembly plugin, but for the dependency
plugin, the distinction is not to do
So analyze will still work the same as alpha-3 and JustAnalyze becomes
analyze-build? That works for me.
-Original Message-
From: Mark Hobson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 18, 2007 8:45 AM
To: Maven Developers List
Subject: Re: dependency:analyze changes
On 18/09
On 18/09/2007, Brian E. Fox [EMAIL PROTECTED] wrote:
So analyze will still work the same as alpha-3 and JustAnalyze becomes
analyze-build? That works for me.
Yep.
Actually analyze-build is still confusing because it could imply that it
is building, which it isn't. How about analyze-only?
I
: dependency:analyze changes
So analyze will still work the same as alpha-3 and JustAnalyze becomes
analyze-build? That works for me.
-Original Message-
From: Mark Hobson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 18, 2007 8:45 AM
To: Maven Developers List
Subject: Re: dependency:analyze changes
On 18/09/2007, Paul Gier [EMAIL PROTECTED] wrote:
I think he meant analyze would become analyze-build because you are doing both
analyze and a build. And just-analyze would become analyze.
But that way it breaks what people are used to. I like Brian's suggestion
analyze-only, that seems
. Fox wrote:
So analyze will still work the same as alpha-3 and JustAnalyze becomes
analyze-build? That works for me.
-Original Message-
From: Mark Hobson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 18, 2007 8:45 AM
To: Maven Developers List
Subject: Re: dependency:analyze changes
I think that's what I meant ;)
Anyway, the surefire report plugin uses report and report-only to do something
similar, so that seems consistent with Brian's suggestion of using analyze and
analyze-only.
Mark Hobson wrote:
On 18/09/2007, Paul Gier [EMAIL PROTECTED] wrote:
I think he meant
On 17/09/2007, Mark Hobson [EMAIL PROTECTED] wrote:
Brian and anyone else interested,
I'd like to make a couple of small changes to the analyze goal:
1) Remove @execute phase=test-compile and replace with @phase
verify. This will allow it to be used in the verification phase in a
similar
On 17/09/2007, Mark Hobson [EMAIL PROTECTED] wrote:
On 17/09/2007, Mark Hobson [EMAIL PROTECTED] wrote:
Brian and anyone else interested,
I'd like to make a couple of small changes to the analyze goal:
1) Remove @execute phase=test-compile and replace with @phase
verify. This will
Fine with me.
-Original Message-
From: Mark Hobson [mailto:[EMAIL PROTECTED]
Sent: Monday, September 17, 2007 9:29 AM
To: Maven Developers List
Subject: Re: dependency:analyze changes
On 17/09/2007, Mark Hobson [EMAIL PROTECTED] wrote:
On 17/09/2007, Mark Hobson [EMAIL PROTECTED] wrote
: dependency:analyze changes
On 17/09/2007, Mark Hobson [EMAIL PROTECTED] wrote:
On 17/09/2007, Mark Hobson [EMAIL PROTECTED] wrote:
Brian and anyone else interested,
I'd like to make a couple of small changes to the analyze goal:
1) Remove @execute phase=test-compile and replace with @phase
verify
On 17/09/2007, Brian E. Fox [EMAIL PROTECTED] wrote:
I'm thinking about pushing out another release this week so if there's
anything else you need to get in, this would be a good time.
Yeah, I really want to start using the branched dependency:tree work
in a stable release soon. If we release
Mark Hobson wrote:
On 17/09/2007, Mark Hobson [EMAIL PROTECTED] wrote:
On 17/09/2007, Mark Hobson [EMAIL PROTECTED] wrote:
Brian and anyone else interested,
I'd like to make a couple of small changes to the analyze goal:
1) Remove @execute phase=test-compile and replace with @phase
verify.
Brian,
I'm done with MDEP if you want to release 2.0-alpha-5. I'll merge
MDEP-100 in once you're done. There's a few prerequisites to be
released first - using dependency:tree: ;)
org.apache.maven.plugins:maven-dependency-plugin:maven-plugin:2.0-alpha-5-SNAPSHOT
+-
Oops, and again without my local MDEP-100 mods:
org.apache.maven.plugins:maven-dependency-plugin:maven-plugin:2.0-alpha-5-SNAPSHOT
+-
org.apache.maven.shared:maven-plugin-testing-tools:jar:1.0-alpha-3-SNAPSHOT:test
| \- org.apache.maven.shared:maven-invoker:jar:2.0.7-SNAPSHOT:test
+-
: dependency:analyze changes
Mark Hobson wrote:
On 17/09/2007, Mark Hobson [EMAIL PROTECTED] wrote:
On 17/09/2007, Mark Hobson [EMAIL PROTECTED] wrote:
Brian and anyone else interested,
I'd like to make a couple of small changes to the analyze goal:
1) Remove @execute phase=test-compile and replace
21 matches
Mail list logo
