;>>
>>>>>>>
>>>>>>> SweeperPool: does anything use this? It would be somewhat scary to
>>>>>>> recreate.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
nd maven-3.0), then I'd say lets drop them now.
LieGrue,
strub
--- On Mon, 6/13/11, Stephen
Connolly
wrote:
From: Stephen Connolly
Subject: Re: Truly awful code in plexus...
To: "Maven Developers List"
Date: Monday, June 13, 2011, 5:55 AM
if we knew the provenance of the
plexus co
46 AM, Stephen Connolly
>>>>>> wrote:
>>>>>>>
>>>>>>> It's tempting... but I fear all that will happen is nobody will switch
>>>>>>> to the new impl...
>>>>>>>
>>>
.. but I fear all that will happen is nobody will switch
>>>>>> to the new impl...
>>>>>>
>>>>>> the WHOLE point of this bridge is to remove any dependency on
>>>>>> plexus-utils in core... and how we class-load plexus-utils is IIRC
>
a year now (or<
maven-2.2.1 and maven-3.0), then I'd say lets drop them now.
LieGrue,
strub
--- On Mon, 6/13/11, Stephen Connolly
wrote:
From: Stephen Connolly
Subject: Re: Truly awful code in plexus...
To: "Maven Developers List"
Date: Monday, June 13, 2011, 5:55 AM
if we
ll plugins no matter what they
>>>> use... so if we remove a deprecated method and a plugin is expecting
>>>> it then that plugin breaks.
>>>>
>>>> On 13 June 2011 10:41, Mark Struberg wrote:
>>>>>
>>>>> Hi!
>>>&
r now (or< maven-2.2.1
and maven-3.0), then I'd say lets drop them now.
LieGrue,
strub
--- On Mon, 6/13/11, Stephen Connolly wrote:
From: Stephen Connolly
Subject: Re: Truly awful code in plexus...
To: "Maven Developers List"
Date: Monday, June 13, 2011, 5:55 AM
if we knew
prove his ownership! So
>> in practice there is imo a kind of reversal of evidence in place thus it's
>> 'pretty' safe to use that code. Especially since this code is already in the
>> public domain since many years with the ALv2 sticker on it...
>>
>> LieGru
t...
>
> LieGrue,
> strub
>
> --- On Mon, 6/13/11, Benson Margulies wrote:
>
>> From: Benson Margulies
>> Subject: Re: Truly awful code in plexus...
>> To: "Maven Developers List"
>> Date: Monday, June 13, 2011, 1:15 PM
>> Mark,
>>
>
t...
LieGrue,
strub
--- On Mon, 6/13/11, Benson Margulies wrote:
> From: Benson Margulies
> Subject: Re: Truly awful code in plexus...
> To: "Maven Developers List"
> Date: Monday, June 13, 2011, 1:15 PM
> Mark,
>
> I think it appropriate to mix in the scale
>> the WHOLE point of this bridge is to remove
>> any dependency on
>> >>> plexus-utils in core... and how we class-load
>> plexus-utils is IIRC
>> >>> that we force the core version on all plugins
>> no matter what they
>> >>> use.
h an iCLA on file... for thew few cases we find where there is no
iCLA on file we can evaluate them as we find them.
>
> LieGrue,
> strub
>
> --- On Mon, 6/13/11, Benson Margulies wrote:
>
>> From: Benson Margulies
>> Subject: Re: Truly awful code in plexus...
>&g
haus.org Plexus
project, since all the history is available and 80% of the committers are
Apache committers (with an iCLA on file) anyway.
LieGrue,
strub
--- On Mon, 6/13/11, Benson Margulies wrote:
> From: Benson Margulies
> Subject: Re: Truly awful code in plexus...
> To: "Maven Dev
June 2011 10:41, Mark Struberg wrote:
>>>>> Hi!
>>>>>
>>>>> If those methods are already deprecated, then I'd say we should drop them
>>>>> now.
>>>>>
>>>>> Most times those methods didn't got dep
ot deprecated because they are 'unpretty'
>>>> but because they are seriously flawed. Like missing encoding parameter,
>>>> missing timezone, not multithreading capable, etc.
>>>>
>>>> So if those methods are deprecated for more than a yea
t;> now.
>>>
>>> Most times those methods didn't got deprecated because they are 'unpretty'
>>> but because they are seriously flawed. Like missing encoding parameter,
>>> missing timezone, not multithreading capable, etc.
>>>
>&g
cated because they are 'unpretty'
>>> but because they are seriously flawed. Like missing encoding parameter,
>>> missing timezone, not multithreading capable, etc.
>>>
>>> So if those methods are deprecated for more than a year now (or <
>>&
Hi all;
We have created new Maven screencast (Turkish version). This video anwers
below questions
1 - What is Maven
2 -How can you set up it
3 - Maven integration - pom.xml explanatation
Here is the link :
http://www.kodcu.com/2011/03/apache-maven-teknolojisine-giris-video/
How can we add this
oding parameter,
>> missing timezone, not multithreading capable, etc.
>>
>> So if those methods are deprecated for more than a year now (or <
>> maven-2.2.1 and maven-3.0), then I'd say lets drop them now.
>>
>> LieGrue,
>> strub
>>
>
> plexus-utils in core... and how we class-load plexus-utils is IIRC
> that we force the core version on all plugins no matter what they
> use... so if we remove a deprecated method and a plugin is expecting
> it then that plugin breaks.
no, this is not the case since Maven 2.0.6: see MNG-2892
FYI
say lets drop them now.
>
> LieGrue,
> strub
>
> --- On Mon, 6/13/11, Stephen Connolly wrote:
>
>> From: Stephen Connolly
>> Subject: Re: Truly awful code in plexus...
>> To: "Maven Developers List"
>> Date: Monday, June 13, 2011, 5:55 A
e, etc.
So if those methods are deprecated for more than a year now (or < maven-2.2.1
and maven-3.0), then I'd say lets drop them now.
LieGrue,
strub
--- On Mon, 6/13/11, Stephen Connolly wrote:
> From: Stephen Connolly
> Subject: Re: Truly awful code in plexus...
> To: &q
if we knew the provenance of the plexus code, yes... but we don't
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 13 Jun 2011 00:12, "Benson Margulies" wrote:
> If we want
If we want to keep the broken behavior of these already @Deprecated
classes, then I'd think we'd just copy them wholesale from plexus to
the bridge. There's no advantage in replacing an old broken version
with a new broken, and they're already deprecated, and the right thing
to do to callers is to
thanks
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 12 Jun 2011 23:25, "Hervé BOUTEMY" wrote:
> strategy added in the proposal [1], for future reference
>
> Regards,
>
>
strategy added in the proposal [1], for future reference
Regards,
Hervé
[1] https://cwiki.apache.org/confluence/display/MAVEN/Plexus-utils+replacement
Le lundi 13 juin 2011, Stephen Connolly a écrit :
> here is my thoughts, for first release we need to have a drop in
> replacement that works ex
Then we will need the bridged FastMap I described. I'll take care of it.
On Sun, Jun 12, 2011 at 6:03 PM, Stephen Connolly
wrote:
> here is my thoughts, for first release we need to have a drop in replacement
> that works exactly the same as the original... that gives us a way to kill
> the old v
here is my thoughts, for first release we need to have a drop in replacement
that works exactly the same as the original... that gives us a way to kill
the old version (otherwise people will just say, "I'm not going to fix my
code when it works fine with plexus utils... ok maybe I'll fix it later")
There are some deprecated classes in here that are completely busted
with respect to char encoding. Do we replace them with undeprecated
versions with the same bugs? Or with calls to commons IO that do
things right?
-
To unsubscri
29 matches
Mail list logo
