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
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
I didn't say it's not possible without profiles.xml, but without it you have
to make a choice between the best of the worst.
Let's stick to the passwords. You don't want to expose them in the pom.xml,
right?
But what if project A en project B both have a ${password} in their pom.xml,
from the sett
Well, the mixin support should cover the profiles.xml and moreeven
better it should be possible to resolve the mixins from the repository which
means they are versioned and deployed artifacts like everything else.
On Wed, Jun 24, 2009 at 11:41 AM, Robert Scholte wrote:
>
> In the settings.xml
In the settings.xml it's not possible to activate a profile by project. Then
again: I believe settings.xml are actually maven-settings and not
project-settings. For most users it's a big step to dive into the
settings.xml. For them there are only a few reasons to access the settings
file:
- to se
: Brian Fox
To: Maven Developers List
Sent: Wed Jun 24 12:22:33 2009
Subject: Re: User's project-specific properties ability disabled after MNG-4060
Why not just put those values into the settings.xml?
On Wed, Jun 24, 2009 at 4:31 AM, Robert Scholte wrote:
>
> I heard some time a
Why not just put those values into the settings.xml?
On Wed, Jun 24, 2009 at 4:31 AM, Robert Scholte wrote:
>
> I heard some time ago that the profiles.xml were removed in Maven3. Although
> I'm still using 2.1.0 I want to be prepared for such changes.
>
> IMHO I think it's a bad choice to remove
I heard some time ago that the profiles.xml were removed in Maven3. Although
I'm still using 2.1.0 I want to be prepared for such changes.
IMHO I think it's a bad choice to remove this option.
Maven should provide some sort of way where developers can set/change project
properties without h
15 matches
Mail list logo