On Nov 29, 2012, at 1:22 AM, Stephane Nicoll <stephane.nic...@gmail.com> wrote:
> I would go for 2.2. Releasing something and then include it as the default
> version the same day seems a bit too much for me.

I would agree with this.  The fact that I was the first one to even notice that 
2.3 has issues on the Mac suggests it's not very widely tested.  :-(

Much like the compiler plugin, I'd let this bake a little more before making it 
the default.

Dan


> On Thursday, November 29, 2012, Jason van Zyl wrote:
> 
>> I'm going to re-spin it. Shall I just use 2.2 or wait for you guys to spin
>> 2.4?
>> 
>> On Nov 28, 2012, at 12:54 PM, Daniel Kulp <dk...@apache.org> wrote:
>> 
>>> 
>>> On Nov 28, 2012, at 12:33 PM, Jason van Zyl <ja...@tesla.io> wrote:
>>>> But what version of the plugin are users going to get?
>>> 
>>> If it's not locked down, they would get 2.3.  (maven 3.0.x users get
>> 2.1.3 I think)
>>> 
>>> 
>>> However, I want to be clear:
>>> 
>>> * The issue ONLY affects Mac users.  Other platforms are OK.
>>> 
>>> * The issue only affects users that use the war plugin.
>>> 
>>> * There is an easy workaround of locking down to 2.2 (or to 2.4 once 2.4
>> is released).
>>> 
>>> * Another work around: adding the -Djava.awt.headless=true flag to the
>> MAVEN_OPTS.
>>> 
>>> * The issue does NOT affect the output of the war plugin.  The plugin
>> does exactly what it's supposed to do and produces a proper war.
>>> 
>>> 
>>> The only "problem" is the Java Icon that would appear on the Mac Dock
>> for the duration of the build.   It doesn't affect the actual build at all.
>>> 
>>> So basically, it affects a relatively small number of maven users,
>> doesn't affect the actual build at all, and has a relatively easy
>> workaround for people that are annoyed by it.
>>> 
>>> 
>>> Dan
>>> 
>>> 
>>> 
>>>> On Nov 28, 2012, at 11:54 AM, Daniel Kulp <dk...@apache.org> wrote:
>>>> 
>>>>> 
>>>>> On Nov 28, 2012, at 11:46 AM, Arnaud Héritier <aherit...@gmail.com>
>> wrote:
>>>>> 
>>>>>> there is an issue opened about it ?
>>>>>> I didn't find it.
>>>>> 
>>>>> No, Olivier and I spent a chunk of time yesterday on IRC trying to
>> figure out what was going on.   Once we figured it out, he committed a fix
>> before I could even login to JIRA.  :-)
>>>>> 
>>>>> 
>>>>> r1414267 | olamy | 2012-11-27 12:09:54 -0500 (Tue, 27 Nov 2012) | 1
>> line
>>>>> back tp xstream 1.4.2 to avoid
>> http://jira.codehaus.org/browse/XSTR-709
>>>>> 
>>>>> 
>>>>> Dan
>>>>> 
>>>>> 
>>>>>> 
>>>>>> 
>>>>>> On Wed, Nov 28, 2012 at 5:33 PM, Daniel Kulp <dk...@apache.org>
>> wrote:
>>>>>> 
>>>>>>> 
>>>>>>> +1
>>>>>>> 
>>>>>>> I've tested this with a few projects and it seems to work.
>>>>>>> 
>>>>>>> I DON'T like that it updates the war plugin to 2.3 as that version
>> has
>>>>>>> issues on the Mac related to setting up an awt Toolkit.   However,
>> there is
>>>>>>> a simple workaround of locking the war version down to 2.2 in the
>> project
>>>>>>> pom (which is something the project in question should have done
>> anyway).
>>>>>>> 
>>>>>>> Dan
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>>> On Mon, Nov 26, 2012 at 7:24 AM, Jason van Zyl <ja...@tesla.io>
>> wrote:
>>>>>>>> 
>>>>>>>>> Hi,
>>>>>>>>> 
>>>>>>>>> Here is a link to Jira with 30 issues resolved:
>>>>>>>>> 
>>>>>>>>> 
>>>>>>> 
>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>>>>>>>>> 
>>>>>>>>> Staging repo:
>>>>>>>>> https://repository.apache.org/content/repositories/maven-073/
>>>>>>>>> 
>>>>>>>>> The distributable binaries and sources for testing can be found
>> here:
>>>>>>>>> 
>>>>>>>>> 
>>>>>>> 
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-<https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/>the
>> course of true love never did run smooth ...
>> 
>> -- Shakespeare
>> 
>> 
>> 
>> 
>> 
>> 

-- 
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to