Hervé BOUTEMY wrote:
But anyway, how
does it make sense for [1.0.0,2.0.0) (with an *exclusive* upper bound of
2.0.0) to include anything from the 2.0.0. branch?
if you don"t want to include anything from the 2.0.0 branch, you have to write
you range as [1.0.0,2.0.0-SNAPSHOT), which is con
I agree, for a future version of Maven. What I think is needed is
reusable test lifecycles so you get the source directory, compilation
and resources sequence, and then the run.
You might also like to look at the slides from my talk at ApacheCon
that cover the two alternatives that are avai
>> -return projectDirectory != null;
>> +return projectDirectory != null && new File(projectDirectory,
>> "pom.xml").exists();
>> }
>Will that work in all cases? For instance, there is the concept of a
>release-pom.xml and furthermore users are free to specify POMs with
>a
On 17-Nov-08, at 5:19 PM, Benjamin Bentmann wrote:
Hi,
regarding JIRA issues for the Maven Ant Tasks, there is both a
component under MNG [0] and a standalone project MANTTASKS. Should
we move all issues from the component over to the standalone project
and delete the component from MNG?
Ok, I see it has been removed already.
Paul Gier wrote:
Oops, I guess I created a couple of issues in the wrong place. Thanks
for fixing this. Should the ant tasks jira component be removed
completely to prevent new issues being created there?
Brett Porter wrote:
yes... I think they must j
Oops, I guess I created a couple of issues in the wrong place. Thanks for
fixing this. Should the ant tasks jira component be removed completely to
prevent new issues being created there?
Brett Porter wrote:
yes... I think they must just be some left overs
On 18/11/2008, at 9:19 AM, Benjami
yes... I think they must just be some left overs
On 18/11/2008, at 9:19 AM, Benjamin Bentmann wrote:
Hi,
regarding JIRA issues for the Maven Ant Tasks, there is both a
component under MNG [0] and a standalone project MANTTASKS. Should
we move all issues from the component over to the stand
Hi,
regarding JIRA issues for the Maven Ant Tasks, there is both a component
under MNG [0] and a standalone project MANTTASKS. Should we move all
issues from the component over to the standalone project and delete the
component from MNG?
Benjamin
[0] http://jira.codehaus.org/browse/MNG/co
Hi Jason,
Author: jvanzyl
Date: Sun Nov 16 19:26:07 2008
New Revision: 718166
URL: http://svn.apache.org/viewvc?rev=718166&view=rev
Added:
maven/touchstone/
maven/touchstone/touchstone/
maven/touchstone/touchstone/.settings/
maven/touchstone/touchstone/.settings/org.eclipse.jdt
Hi Shane,
Author: sisbell
Date: Sun Nov 16 22:23:46 2008
New Revision: 718176
URL: http://svn.apache.org/viewvc?rev=718176&view=rev
Log:
Configured build extension listener to only fire on poms within the build.
[...]
Modified:
maven/components/trunk/maven-project/src/main/java/org/apache/mave
On 17-Nov-08, at 1:23 AM, [EMAIL PROTECTED] wrote:
Author: sisbell
Date: Sun Nov 16 22:23:46 2008
New Revision: 718176
URL: http://svn.apache.org/viewvc?rev=718176&view=rev
Log:
Configured build extension listener to only fire on poms within the
build.
It's not only with the current reac
It will pick up extensions in ancestry as well, since the search is applied
after inheritance has been completed.
Shane
On Mon, Nov 17, 2008 at 5:22 AM, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> On 17-Nov-08, at 1:23 AM, [EMAIL PROTECTED] wrote:
>
> Author: sisbell
>> Date: Sun Nov 16 22:23:
On 17-Nov-08, at 1:23 AM, [EMAIL PROTECTED] wrote:
Author: sisbell
Date: Sun Nov 16 22:23:46 2008
New Revision: 718176
URL: http://svn.apache.org/viewvc?rev=718176&view=rev
Log:
Configured build extension listener to only fire on poms within the
build.
It's not only with the current reac
13 matches
Mail list logo
