Re: [OT] Re: keeping Eclipse files in our repo [was Re: Package removal with new Digester]

2004-12-03 Thread David Graham
--- Matt Bathje [EMAIL PROTECTED] wrote: David Graham wrote: Eclipse classpath variables don't solve the issue because each developer may be using different variable names. Further, the name of the jar file may be different (ie. have version number in it). In my experience, forcing

Re: [OT] Re: keeping Eclipse files in our repo [was Re: Package removal with new Digester]

2004-12-03 Thread Matt Bathje
David Graham wrote: --- Matt Bathje [EMAIL PROTECTED] wrote: Why would a developer use different variable names? If .classpath/.project for eclipse were included, there must be documentation saying you must setup VARIABLEX to point to RESOURCEX and so forth. IMO, dictating the one true way to

Re: Package removal with new Digester

2004-12-02 Thread Martin Cooper
Hmm, that's odd. How are you trying to build? I can run 'ant clean dist' just fine with Digester 1.6, and that builds tiles-documentation.war. -- Martin Cooper On Thu, 2 Dec 2004 09:54:36 -0500, James Mitchell [EMAIL PROTECTED] wrote: I can't compile the tiles-documentation sources with

Re: Package removal with new Digester

2004-12-02 Thread James Mitchell
Software Engineer / Open Source Evangelist EdgeTech, Inc. 678.910.8017 AIM: jmitchtx - Original Message - From: Martin Cooper [EMAIL PROTECTED] To: Struts Developers List [EMAIL PROTECTED] Sent: Thursday, December 02, 2004 1:14 PM Subject: Re: Package removal with new Digester Hmm, that's odd

Re: Package removal with new Digester

2004-12-02 Thread James Mitchell
]; Martin Cooper [EMAIL PROTECTED] Sent: Thursday, December 02, 2004 1:52 PM Subject: Re: Package removal with new Digester Wow, I was missing something. I just noticed this in build-webapp.xml: ... ... !-- Excludes for tiles-documentation to reflect the fact that Commons Digester 1.6 no longer ships

RE: Package removal with new Digester

2004-12-02 Thread Deadman, Hal
and have all the various sub-projects automatically checked out and setup as projects in Eclipse. -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED] Sent: Thursday, December 02, 2004 2:25 PM To: Struts Developers List Subject: Re: Package removal with new Digester

RE: Package removal with new Digester

2004-12-02 Thread Joe Germuska
PROTECTED] Sent: Thursday, December 02, 2004 2:25 PM To: Struts Developers List Subject: Re: Package removal with new Digester That change was made at the end of October. So now what? Instead of ignoring those classes, shouldn't we fix the problem? Like include the examples from digester or remove

Re: Package removal with new Digester

2004-12-02 Thread Martin Cooper
:[EMAIL PROTECTED] Sent: Thursday, December 02, 2004 2:25 PM To: Struts Developers List Subject: Re: Package removal with new Digester That change was made at the end of October. So now what? Instead of ignoring those classes, shouldn't we fix the problem? Like include

keeping Eclipse files in our repo [was Re: Package removal with new Digester]

2004-12-02 Thread Mike Kienenberger
Martin Cooper [EMAIL PROTECTED] wrote: Other issues with keeping Eclipse files in our repo: 1) The expectation would be that they would be kept up to date. If a particular committer doesn't use Eclipse, I don't think it's fair to expect them to keep Eclipse config files up to date when they

Re: keeping Eclipse files in our repo [was Re: Package removal with new Digester]

2004-12-02 Thread David Graham
Thanks for changing the subject line so I noticed this thread again. I am very much against keeping IDE specific files in the repository. Even if you're using the same IDE, no two developer's environment will be the same so paths will be wrong, etc. This will be painful because checking out

Re: keeping Eclipse files in our repo [was Re: Package removal with new Digester]

2004-12-02 Thread Michael Rasmussen
I am very much against keeping IDE specific files in the repository. +1 Michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: keeping Eclipse files in our repo [was Re: Package removal with new Digester]

2004-12-02 Thread Matt Bathje
With eclipse at least, this limitation can be easily worked around. Anything that uses a machine-specific path (or whatever else that may be machine specific) is referenced to by a variable that each developer can set on their machine. What gets committed only has references to those variables,

Re: keeping Eclipse files in our repo [was Re: Package removal with new Digester]

2004-12-02 Thread David Graham
Eclipse classpath variables don't solve the issue because each developer may be using different variable names. Further, the name of the jar file may be different (ie. have version number in it). In my experience, forcing developers to use the one true setup is a recipe for disaster. After

[OT] Re: keeping Eclipse files in our repo [was Re: Package removal with new Digester]

2004-12-02 Thread Matt Bathje
David Graham wrote: Eclipse classpath variables don't solve the issue because each developer may be using different variable names. Further, the name of the jar file may be different (ie. have version number in it). In my experience, forcing developers to use the one true setup is a recipe for

Re: Package removal with new Digester

2004-12-02 Thread Niall Pemberton
Have you got the latest build-webapp.xml? Craig commented out the tiles-documentation build to stop this failing (Revision 56019) Niall - Original Message - From: James Mitchell [EMAIL PROTECTED] To: Struts Developers List [EMAIL PROTECTED] Sent: Thursday, December 02, 2004 2:54 PM