Re: [castor-dev] Mvn build and Eclipse
Andras Hatvani <[email protected]> Mon, 3 May 2010 08:23:23 +0200
| Newsgroups | gmane.comp.java.castor.devel |
|---|---|
| Message-ID | <[email protected]> |
--Apple-Mail-2-355344615 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Hello, Although I'm not an official committer, but within the scope of a university course I'm involved in the development and am affected, too I'd like to share my thoughts. I completely agree that IDE-specific files shouldn't be part of any project's source tree, but I also don't like, if one project's modules fill half of my workspace. Whether one decides for the single- or for the multi-project method, both require trade-offs: - clean and compact workspace vs manual classpath maintenance and - automated classpath maintenance vs "polluted" workspace. These two factors are which I can think of at first, but I'd be glad to see a more complete list of benefits and drawbacks. Btw, did anyone already contact the maven mailing list for further information? Andras On 1 May 2010, at 16:20, Werner Guttmann <[email protected]> wrote: > Hi everybody, > > I'd really like to see .classpath and .project being removed from > our SVN repository. I know there's some resistance, so let's use > this thread to get an complete overview on any objections. > > Cheers > Werner > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --Apple-Mail-2-355344615 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><body bgcolor=3D"#FFFFFF"><div><span class=3D"Apple-style-span" = style=3D"font-size: 15px; -webkit-tap-highlight-color: rgba(26, 26, 26, = 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, = 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, = 0.230469); "><span>Hello,</span><br><span></span><br><span>Although I'm = not an official committer, but within the scope of = a </span><br><span>university course I'm involved in the = development and am affected, too </span><br><span>I'd like to share = my thoughts.</span><br><span>I completely agree that IDE-specific files = shouldn't be part of any </span><br><span>project's source tree, = but I also don't like, if one project's = modules </span><br><span>fill half of my workspace. Whether one = decides for the single- or for </span><br><span>the multi-project = method, both require trade-offs:</span><br><span>- clean and compact = workspace vs manual classpath maintenance and</span><br><span>- = automated classpath maintenance vs "polluted" = workspace.</span><br><span>These two factors are which I can think of at = first, but I'd be glad to </span><br><span>see a more complete list = of benefits and drawbacks.</span><br><span>Btw, did anyone already = contact the maven mailing list for = further </span><br><span>information?</span><br><span></span><br><spa= n>Andras</span></span><br><br>On 1 May 2010, at 16:20, Werner Guttmann = <<a href=3D"mailto:[email protected]">[email protected]</a>> = wrote:<br><br></div><div></div><blockquote type=3D"cite"><div><span>Hi = everybody,</span><br><span></span><br><span>I'd really like to see = .classpath and .project being removed from our SVN repository. I know = there's some resistance, so let's use this thread to get an complete = overview on any = objections.</span><br><span></span><br><span>Cheers</span><br><span>Werner= </span><br><span></span><br><span>----------------------------------------= -----------------------------</span><br><span>To unsubscribe from this = list, please visit:</span><br><span></span><br><span> <a = href=3D"http://xircles.codehaus.org/manage_email"><a = href=3D"http://xircles.codehaus.org/manage_email">http://xircles.codehaus.= org/manage_email</a></a></span><br><span></span><br><span></span><br></div= ></blockquote></body></html>= --Apple-Mail-2-355344615--