Ray Krueger wrote:
> Ooh, here's an idea!
> Have Maven generate a new .classpath file and check that in.
>   
The plugin nicely doesn't generate one for the parent POM.  Otherwise we 
wouldn't still be having this discussion ;-)
The way to handle the flat structure is extremely kludgy: 
http://maven.apache.org/plugins/maven-eclipse-plugin/reactor.html (its 
on the bottom).

The easiest thing for me to do now is just update the .classpath file 
locally and not check it in.  I'll let the more core team figure out the 
whole Eclipse project issue and then just update to whatever you guys 
decide ;-)

On a completely different side note, in updating the .classpath file, 
we're depending on commons-logging 1.0.4.  Should we upgrade to 1.1?

-Scott
>
> On 9/10/07, Scott Battaglia <[EMAIL PROTECTED]> wrote:
>   
>> I'm not trying to get into a discussion on how one should use Eclipse
>> (if I was working with a multi-module project I'd actually use IDEA).
>> My point was that this behavior and Eclipse project structure would be
>> different then what it is now by using mvn eclipse:eclipse.
>>
>> My immediate need is to get Eclipse to  have the appropriate
>> dependencies and I offered to put the correct version into Subversion.
>> Anything beyond that scope is a different discussion.
>>
>> -Scott
>>
>> Ray Krueger wrote:
>>     
>>> Why isn't it?
>>>
>>> If you're only interested in working on core then...
>>> cd core
>>> mvn eclipse:eclipse
>>>
>>>
>>>
>>> On 9/10/07, Scott Battaglia <[EMAIL PROTECTED]> wrote:
>>>
>>>       
>>>> Executing mvn eclipse:eclipse creates projects for each of the modules,
>>>> which is probably not what we want.
>>>>
>>>> -Scott
>>>>
>>>> Ray Krueger wrote:
>>>>
>>>>         
>>>>> I think the .classpath files should be removed. They are doomed to be 
>>>>> stale.
>>>>> The project is now built with maven2 completely. Maven can create the
>>>>> .classpath files as needed.
>>>>>
>>>>> Executing "mvn eclipse:eclipse" from the project root will create
>>>>> everything needed.
>>>>>
>>>>>
>>>>> On 9/10/07, Scott Battaglia <[EMAIL PROTECTED]> wrote:
>>>>>
>>>>>
>>>>>           
>>>>>> I'm doing some work on some of the JIRA issues assigned to me (finally
>>>>>> getting a chance) and I checked out the project and noticed that the
>>>>>> .classpath was referring to Spring 1.2.9 while the pom refers to 2.0.6.
>>>>>> Anyone have any issues if I update the .classpath file to reflect the
>>>>>> latest Spring version?
>>>>>>
>>>>>> Thanks
>>>>>> -Scott
>>>>>>
>>>>>> -------------------------------------------------------------------------
>>>>>> This SF.net email is sponsored by: Microsoft
>>>>>> Defy all challenges. Microsoft(R) Visual Studio 2005.
>>>>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>>>>> _______________________________________________
>>>>>> Home: http://acegisecurity.org
>>>>>> Acegisecurity-developer mailing list
>>>>>> Acegisecurity-developer@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
>>>>>>
>>>>>>
>>>>>>
>>>>>>             
>>>>> -------------------------------------------------------------------------
>>>>> This SF.net email is sponsored by: Microsoft
>>>>> Defy all challenges. Microsoft(R) Visual Studio 2005.
>>>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>>>> _______________________________________________
>>>>> Home: http://acegisecurity.org
>>>>> Acegisecurity-developer mailing list
>>>>> Acegisecurity-developer@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
>>>>>
>>>>>
>>>>>           
>>>> -------------------------------------------------------------------------
>>>> This SF.net email is sponsored by: Microsoft
>>>> Defy all challenges. Microsoft(R) Visual Studio 2005.
>>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>>> _______________________________________________
>>>> Home: http://acegisecurity.org
>>>> Acegisecurity-developer mailing list
>>>> Acegisecurity-developer@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
>>>>
>>>>
>>>>         
>>> -------------------------------------------------------------------------
>>> This SF.net email is sponsored by: Microsoft
>>> Defy all challenges. Microsoft(R) Visual Studio 2005.
>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>> _______________________________________________
>>> Home: http://acegisecurity.org
>>> Acegisecurity-developer mailing list
>>> Acegisecurity-developer@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
>>>
>>>       
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2005.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Home: http://acegisecurity.org
>> Acegisecurity-developer mailing list
>> Acegisecurity-developer@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
>>
>>     
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Home: http://acegisecurity.org
> Acegisecurity-developer mailing list
> Acegisecurity-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
>   

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Home: http://acegisecurity.org
Acegisecurity-developer mailing list
Acegisecurity-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer

Reply via email to