On 2009-11-27, at 4:32 PM, Stephen Connolly wrote:
Sent from my [rhymes with tryPod] ;-)
On 27 Nov 2009, at 21:03, Jason van Zyl wrote:
On 2009-11-27, at 3:48 PM, Robert Scholte wrote:
With the alpha releases of Maven 3 published we'll see how
developers react
on this issue.
I've i
Sent from my [rhymes with tryPod] ;-)
On 27 Nov 2009, at 21:03, Jason van Zyl wrote:
On 2009-11-27, at 3:48 PM, Robert Scholte wrote:
With the alpha releases of Maven 3 published we'll see how
developers react
on this issue.
I've introduced Maven during several projects and my experie
On 2009-11-27, at 3:48 PM, Robert Scholte wrote:
With the alpha releases of Maven 3 published we'll see how
developers react
on this issue.
I've introduced Maven during several projects and my experience is
that
newbies fear the settings.xml. They let a pro setup their
settings.xml for
With the alpha releases of Maven 3 published we'll see how developers react
on this issue.
I've introduced Maven during several projects and my experience is that
newbies fear the settings.xml. They let a pro setup their settings.xml for
the repository and from that moment on it's an avoided terri
Brian,
I'm not sure if you were replying to me or others, but you quoted me and
snipped my actual point:
"I'm fine with either more or less frequent releases... I'm not fine with
circumventing review or pushing releases outside the ASF."
I agree with everything you said below. I was saying we
I have now come a long way towards implementing a massively concurrent
maven. To whet some appetites before ifs/but/whens/problems come up:
Using 16 threads on my Intel i7, build time for my daytime project went
from 87 seconds to 19.7 seconds. An average of 500% CPU was consumed to
deliver this,
> I'm also not pushing for duration for "testing" purposes. That's part of it,
> but as Jason said
>automation can reduce the need over time (though it's never going to be 100%
>so there's some value
>in testing). However, it is mostly for an opportunity to review changes. If we
>do "8 releases
On Fri, Nov 27, 2009 at 1:59 PM, Jason van Zyl wrote:
>
> On 2009-11-27, at 7:45 AM, Milos Kleint wrote:
>
> On Fri, Nov 27, 2009 at 12:57 PM, Jason van Zyl wrote:
>>
>>
>>> On 2009-11-27, at 5:55 AM, Milos Kleint wrote:
>>>
>>> I agree with Robert here.
>>>
removal of profiles.xml file le
On 2009-11-27, at 7:45 AM, Milos Kleint wrote:
On Fri, Nov 27, 2009 at 12:57 PM, Jason van Zyl
wrote:
On 2009-11-27, at 5:55 AM, Milos Kleint wrote:
I agree with Robert here.
removal of profiles.xml file leaves maven with no non-sharable,
per-project
configuration option. I"ve added my
On Fri, Nov 27, 2009 at 12:57 PM, Jason van Zyl wrote:
>
> On 2009-11-27, at 5:55 AM, Milos Kleint wrote:
>
> I agree with Robert here.
>> removal of profiles.xml file leaves maven with no non-sharable,
>> per-project
>> configuration option. I"ve added my example to
>> the issue http://jira.cod
On 2009-11-27, at 5:55 AM, Milos Kleint wrote:
I agree with Robert here.
removal of profiles.xml file leaves maven with no non-sharable, per-
project
configuration option. I"ve added my example to
the issue http://jira.codehaus.org/browse/MNG-4060.
It would be doable with settings.xml but it
I agree with Robert here.
removal of profiles.xml file leaves maven with no non-sharable, per-project
configuration option. I"ve added my example to
the issue http://jira.codehaus.org/browse/MNG-4060.
It would be doable with settings.xml but it would be uber-cumbersome to do
so. It could partly wo
The Maven team is pleased to announce the release of Apache Maven
3.0-alpha-5.
Maven is a project comprehension and build tool, designed to simplify
the process of maintaining a healthy development lifecycle for your
project. You can read more here:
http://maven.apache.org/
Downloads of sour
13 matches
Mail list logo
