ok, after this release i will make/take time for myself to create a new
patch that includes all patches of the 3 companies i know that use
patched versions.

This time i will make the time to include tests and documentation!!!
(maybe release 2.5 is not so far away)

Another question did anyone test the plugin with eclipse 3.3 (with and
without WTP) ?

Ritchie

Brian E. Fox wrote:
> Ritchie,
> I understand the issue but on the flip side, without tests to ensure the
> functionality works as expected, we can't verify it. I don't personally
> use this functionality of the plugin so I can't tell at a glance if it's
> right or not. As I see it, once we are this close to a release
> (discussion about preparing for it occurred mid-june) then only complete
> patches can be considered for inclusion. Otherwise we might have to wait
> another week or two until someone has time to analyze and complete the
> patch. It's a recurring cycle where we wait and wait and before you know
> it, it's 5 months like it is now with good functionality already sitting
> there.
>
> --Brian
>
> -----Original Message-----
> From: Richard van Nieuwenhoven [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, July 05, 2007 9:21 AM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4
>
> test are missing correct, but a fix for this ear problem is rather
> important because
> ear's won't work with WTP as they are.
>
> Ritchie
>
> Brian E. Fox wrote:
>   
>> Same thing with this one, the patch doesn't exist yet along with tests
>> or doc changes. If we have to respin the release because of the test
>> problems, then we can grab a few patches if they are complete,
>>     
> otherwise
>   
>> I say they wait. We've been discussing releasing for several weeks now
>> and need to pull the trigger at some point. We shouldn't wait another
>>     
> 5
>   
>> months before releasing again so this doesn't become a problem.
>>
>> -----Original Message-----
>> From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] 
>> Sent: Thursday, July 05, 2007 4:55 AM
>> To: Maven Developers List
>> Subject: Re: [VOTE] maven-eclipse-plugin 2.4
>>
>> We just received a comment about MECLIPSE-184 (it was in private
>> before).
>> WDYT ? I'm not a ear user...
>>
>> Arnaud
>>
>>
>> On 04/07/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
>>   
>>     
>>> It's been about 5 months since an eclipse plugin release and we have
>>> lots of fixes and a handful of enhancements:
>>>
>>> Bug
>>> * [MECLIPSE-108] - .wtpmodules with version 2.4 for
>>> javax.servlet:servlet-api:2.3
>>> * [MECLIPSE-109] - .component wb-resource source path incorrect for
>>>     
>>>       
>> ear
>>   
>>     
>>> packaging
>>> * [MECLIPSE-151] - Incorrect name for test sources jars
>>> * [MECLIPSE-198] - EJB version is not resloved
>>> * [MECLIPSE-215] - WTP 1.5 Documentation
>>> * [MECLIPSE-220] - Incorrect eclipse facet information when doing mvn
>>> eclipse:eclipse for war and ejb projects.
>>> * [MECLIPSE-225] - Invalid .classpath Entries.
>>> * [MECLIPSE-233] - Manifest attributes incorrectly treated as
>>> case-sensitive
>>> * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs() reuses
>>> String method argument causing maven-eclipse.xml copy-resources
>>>     
>>>       
>> problems
>>   
>>     
>>> * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
>>> resolution:=optional directive
>>> * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
>>> * [MECLIPSE-241] - Compiler settings in pluginManagement aren't used
>>>     
>>>       
>> in
>>   
>>     
>>> wtp facet
>>> * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory
>>>     
>>>       
>> Server
>>   
>>     
>>> to be built
>>> * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
>>> * [MECLIPSE-255] - WTP Settings does not use servlet-api version
>>>     
>>>       
>> defined
>>   
>>     
>>> in pom.xml
>>> * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0 in
>>>       
> a
>   
>>> Java 5.0 project
>>> * [MECLIPSE-278] - duplicated classpathentries
>>> * [MECLIPSE-279] - PDE projects should be considered java projects in
>>> all cases
>>> * [MECLIPSE-287] - Regression - fails to correctly construct
>>>       
> classpath
>   
>>> containing dependencies with classifiers
>>> Improvement
>>> * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
>>> * [MECLIPSE-267] - Resolve version ranges in make-artifacts
>>> * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
>>> version, jsp version, ... possible through pom configuration
>>> * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
>>> creation while executing eclipse:rad
>>> New Feature
>>> * [MECLIPSE-119] - Allow custom project name for eclipse projects
>>> * [MECLIPSE-189] - addVersionToProjectName property
>>> * [MECLIPSE-251] - Allows prefixing of eclipse project name
>>> * [MECLIPSE-271] - Ability to skip
>>>
>>> The site has been updated:
>>> http://maven.apache.org/plugins/maven-eclipse-plugin
>>>
>>> Plugin is staged here:
>>> http://people.apache.org/~brianf/staging-repository/
>>>
>>> Vote is open for 72hrs.
>>>
>>> +1
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>>     
>>>       
>>   
>>     
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>   


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to