On 1/8/10, Dan Fabulich wrote:
> Kristian Rosenvold wrote:
>
>> I will re-add your stuff, and I will also set it up to use my output
>> demultiplexer that causes output to appear in "normal" order.
>
> Does the demultiplexer do anything in weave mode when threads=1? Does it
> make the projects ap
Ok the vote is far past the minimum time and the votes are unanimous.
Welcome to the Maven project Kristian. Your account request has
already been submitted; it can take several days before the account is
created.
--Brian Fox
Maven PMC Chair
On Wed, Jan 6, 2010 at 4:19 AM, Petar Tahchiev wrote:
Issue Subscription
Filter: Design & Best Practices (23 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
Kristian Rosenvold wrote:
I will re-add your stuff, and I will also set it up to use my output
demultiplexer that causes output to appear in "normal" order.
Does the demultiplexer do anything in weave mode when threads=1? Does it
make the projects appear to unweave (as far as the log is conc
On Fri, Jan 8, 2010 at 10:10 AM, Stephen Connolly
wrote:
> On 7 Jan 2010, at 23:20, Barrie Treloar wrote:
>
>>> Currently you can only say "compile" is outputDependenant upon itself,
>>> meaning it'll wait for "compile" in all upstream projects to finish
>>> before proceeding. We also need to be
Sent from my [rhymes with tryPod] ;-)
On 7 Jan 2010, at 23:20, Barrie Treloar wrote:
Currently you can only say "compile" is outputDependenant upon
itself,
meaning it'll wait for "compile" in all upstream projects to finish
before proceeding. We also need to be able to specify the explicit
> Currently you can only say "compile" is outputDependenant upon itself,
> meaning it'll wait for "compile" in all upstream projects to finish
> before proceeding. We also need to be able to specify the explicit
> target of the dependency, so you could say "test" is outputDependant on
> "compile" i
+1
runs fine on my company and apache projects with no problems so far.
LieGrue,
strub
--- On Wed, 1/6/10, Benjamin Bentmann wrote:
> From: Benjamin Bentmann
> Subject: [VOTE] Release Apache Maven 3.0-alpha-6
> To: "Maven Developers List"
> Date: Wednesday, January 6, 2010, 12:17 PM
> Hi,
>
On 08/01/2010, at 1:55 AM, Brian Fox wrote:
>>
>> What is your proposal here - did you want to vote those 3 people in as
>> committers on the basis of the contribution, or will the existing committers
>> apply patches until the rest of us get to know them? (I don't know who they
>> are, so we
>
> What is your proposal here - did you want to vote those 3 people in as
> committers on the basis of the contribution, or will the existing committers
> apply patches until the rest of us get to know them? (I don't know who they
> are, so we may already). Funnily enough these alternatives hav
2010/1/7 Kristian Rosenvold :
> On Thu, 2010-01-07 at 10:17 +, Stephen Connolly wrote:
>
>> Side note:
>>
>> Now that sounds like the concurrency code I wrote to convert from
>> Accurev to Subversion
>>
>> I actually ended up creating the state of a stream at a specific
>> revision because
On Thu, 2010-01-07 at 10:17 +, Stephen Connolly wrote:
> Side note:
>
> Now that sounds like the concurrency code I wrote to convert from
> Accurev to Subversion
>
> I actually ended up creating the state of a stream at a specific
> revision because it was asked for (by a downstream stre
>> BTW, I'd like to generalize to our Hudson instance, but it seems
>> Hudson still didn't support maven 3.0 :(
>
> Just use free-style projects and you're free to use any Maven version you
> like.
i'd like to but about 250 projects to update ;(
---
Henri Gomez wrote:
BTW, I'd like to generalize to our Hudson instance, but it seems
Hudson still didn't support maven 3.0 :(
Just use free-style projects and you're free to use any Maven version
you like.
Benjamin
-
To un
+1, works for work projects
-Steohen
2010/1/6 Benjamin Bentmann :
> Hi,
>
> We solved 29 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=15996
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&p
Ok, thanks for all your inputs :) I'll look into these suggestions..
-Deng
On Thu, Jan 7, 2010 at 6:11 PM, Olivier Lamy wrote:
> Hi,
> I would prefer using the --parents option too.
> The issue already exists [1].
> I have reverted due to the svn 1.5 requirements.
>
> BTW, this change can be ad
2010/1/7 Kristian Rosenvold :
> On Thu, 2010-01-07 at 08:37 +, Stephen Connolly wrote:
>> > I realized that the prime subject of contention is the injected
>> > resources - maybe ONLY that. So "scheduling" attached to phases or
>> > plugins is really ultimately not the prime target. When think
No problem here.
Many projects build with m2eclipse (from trunk), with the maven3-alpha-6
BTW, I'd like to generalize to our Hudson instance, but it seems
Hudson still didn't support maven 3.0 :(
2010/1/7 Olivier Lamy :
> Hi,
> +1.
> Tested on company builds with success.
>
> Thanks,
> --
> Oliv
Hi,
I would prefer using the --parents option too.
The issue already exists [1].
I have reverted due to the svn 1.5 requirements.
BTW, this change can be added in this project [2]. And you can use
this provider (svnjava) instead of the svnexe one.
--
Olivier
[1] http://jira.codehaus.org/browse/S
Hi,
+1.
Tested on company builds with success.
Thanks,
--
Olivier
2010/1/6 Benjamin Bentmann :
> Hi,
>
> We solved 29 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=15996
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/Iss
On Thu, 2010-01-07 at 08:37 +, Stephen Connolly wrote:
> > I realized that the prime subject of contention is the injected
> > resources - maybe ONLY that. So "scheduling" attached to phases or
> > plugins is really ultimately not the prime target. When thinking of
> > Dan's Antrun plugin requ
On Wed, 2010-01-06 at 18:36 -0800, Dan Fabulich wrote:
> Kristian Rosenvold wrote:
>
> > In this process I removed your original implementation, simply because
> > it allowed me to work freely in simplifying my own implementation (and I
> > truly believe I managed to make some good simplifications
2010/1/7 Kristian Rosenvold :
> On Thu, 2010-01-07 at 08:26 +1100, Brett Porter wrote:
>> On 07/01/2010, at 1:16 AM, Kristian Rosenvold wrote:
>>
>> > On Wed, 2010-01-06 at 13:41 +, Stephen Connolly wrote:
>> >> however you might have to wait for "install" as the attached artifact
>> >> can be
On 07/01/2010, at 2:37 PM, Deng Ching wrote:
> After looking through the code, I came up with two possible fixes for this:
>
> 1. Fix it in wagon-scm by automatically creating the missing directories
> when an error is encountered during checkout when a deployment is performed.
> Instead of chan
24 matches
Mail list logo
