Personally, I think that this is more trouble than it's worth. Once project files are created, they rarely change. However, if they have to, I much prefer to do that through the IDE settings, that to have to figure out how to do things through all the stages that are involved when everything is generated through Maven.
On 1/11/08, Tim Eck <[EMAIL PROTECTED]> wrote: > Cool, looks that plugin has grown up a bit since I last looked at it. Now > I have to get over is that involves maven :-) > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:tc-dev- > > [EMAIL PROTECTED] On Behalf Of Eugene Kuleshov > > Sent: Friday, January 11, 2008 12:39 PM > > To: [email protected] > > Subject: Re: [tc-dev] IDEA project file and modules for TC > > > > Tim Eck wrote: > > > That is correct. From what I've seen of the maven stuff in this area, > > it's > > > just about building the .classpath file from the pom dependencies. > > > > > That is not quite true. Maven Eclipse plugin allows to generate > > arbitrary configs under .settings. See additionalConfig parameter here > > http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html > > > > Then plugin configuration can be unified in the parent pom for your > > Eclipse projects. > > > > regards, > > Eugene > > > > > > >> -----Original Message----- > > >> From: [EMAIL PROTECTED] [mailto:tc-dev- > > >> [EMAIL PROTECTED] On Behalf Of Geert Bevin > > >> Sent: Friday, January 11, 2008 12:23 PM > > >> To: [email protected] > > >> Subject: Re: [tc-dev] IDEA project file and modules for TC > > >> > > >> Hi Eugene, > > >> > > >> the tools that Tim refers to is there to check and sanitize project > > >> files. To make sure that certain standards and approaches are always > > >> uniformly enforced. Is that correct Tim? > > >> > > >> Take care, > > >> > > >> Geert > > >> > > >> On 1/11/08, Eugene Kuleshov <[EMAIL PROTECTED]> wrote: > > >> > > >>> If you are going down the road supporting several IDEs, it may as > > >>> > > > well > > > > > >>> make sense to use what is already done in Maven for that instead of > > >>> writing whole new tool from scratch. > > >>> > > >>> Doing that with the baby steps, maybe we could convert > dependencies > > >>> > > > to > > > > > >>> be declared in maven poms instead of modules.def.yml and make > tcbuild > > >>> > > > to > > > > > >>> get it from there, then you could use maven plugins to generate or > > >>> update IDE projects. > > >>> > > >>> regards, > > >>> Eugene > > >>> > > >>> > > >>> Tim Eck wrote: > > >>> > > >>>> I agree with Steve -- as long as it doesn't prove disruptive, no > > >>>> > > >> reason > > >> > > >>>> why we shouldn't let IDEA into our world. Despite the things I'm > > >>>> > > > about > > > > > >> to > > >> > > >>>> outline, I'm more than happy to take a "try it and see" approach. > > >>>> > > >>>> It's probably obvious, but some of things to think about are: > > >>>> > > >>>> - Cross project dependencies --I don't know enough about IDEA > > >>>> > > >> structures > > >> > > >>>> to know if this is a problem, but the eclipse projects mirror > > >>>> > > > exactly > > > > > >> the > > >> > > >>>> dependency constraints defined/enforced by tcbuild (more > > >>>> > > > specifically > > > > > >>>> modules.def.yml). It'd be nice if this isn't lost for those working > > >>>> > > > in > > > > > >>>> IDEA > > >>>> > > >>>> - Formatting and import organization -- probably the least > important > > >>>> issue, but can cause lots of useless churn in source control if > > >>>> > > > things > > > > > >>>> aren't well unified. > > >>>> > > >>>> - Errors/warnings -- At best as we can, these should unified. The > > >>>> > > >> biggest > > >> > > >>>> issue I see is that an eclipse guy makes a change that is > considered > > >>>> > > >> an > > >> > > >>>> error on the IDEA side (or vice versa). It would be very > unfortunate > > >>>> > > >> if > > >> > > >>>> something like this led us to use some lowest common denominator. > > >>>> > > >>>> - JDK API visibility and compile target settings -- 1.4 modules > > >>>> > > > (most > > > > > >> of > > >> > > >>>> them are) get compiled against the 1.4 rt.jar and produce target > 1.4 > > >>>> classes. > > >>>> > > >>>> It might be worth evolving the eclipsegen thing I wrote a while > back > > >>>> > > >> to > > >> > > >>>> automagically generate the idea files from modules.def.yml and the > > >>>> > > > ivy > > > > > >>>> dependency information. > > >>>> > > >>>> > > >>>> > > >>>>> -----Original Message----- > > >>>>> From: [EMAIL PROTECTED] [mailto:tc-dev- > > >>>>> [EMAIL PROTECTED] On Behalf Of Steven Harris > > >>>>> Sent: Friday, January 11, 2008 6:32 AM > > >>>>> To: [email protected] > > >>>>> Subject: Re: [tc-dev] IDEA project file and modules for TC > > >>>>> > > >>>>> I don't see why not as long as they can coexist nicely. > > >>>>> > > >>>>> On Jan 11, 2008, at 5:48 AM, Geert Bevin wrote: > > >>>>> > > >>>>> > > >>>>> > > >>>>>> Hi, > > >>>>>> > > >>>>>> I finally got more than fed up with Eclipse (sorry Eugene, > nothing > > >>>>>> personal) and decided to see how easy it was with IDEA 7 to > > >>>>>> > > > migrate > > > > > >> to > > >> > > >>>>>> an IDEA setup. Seems it's very easy because you can create a new > > >>>>>> > > >> IDEA > > >> > > >>>>>> project from an existing Eclipse workspace. After that I did > still > > >>>>>> need to tweak language levels and code formatting, but I have > this > > >>>>>> working now for IDEA 7. Since Jonas got us all at Terracotta a > > >>>>>> > > > free > > > > > >>>>>> license, I was wondering if you think that I should commit the > > >>>>>> > > >> project > > >> > > >>>>>> files. They all live in a dedicated directory that I've placed at > > >>>>>> /code/base/idea > > >>>>>> > > >>>>>> What do you think? > > >>>>>> > > >>>>>> Geert > > >>>>>> > > >>>>>> -- > > >>>>>> Geert Bevin > > >>>>>> Terracotta - http://www.terracotta.org > > >>>>>> Uwyn "Use what you need" - http://uwyn.com > > >>>>>> RIFE Java application framework - http://rifers.org > > >>>>>> Music and words - http://gbevin.com > > >>>>>> _______________________________________________ > > >>>>>> tc-dev mailing list > > >>>>>> [email protected] > > >>>>>> http://lists.terracotta.org/mailman/listinfo/tc-dev > > >>>>>> > > >>>>>> > > >>>>> _______________________________________________ > > >>>>> tc-dev mailing list > > >>>>> [email protected] > > >>>>> http://lists.terracotta.org/mailman/listinfo/tc-dev > > >>>>> > > >>>>> > > >>>> _______________________________________________ > > >>>> tc-dev mailing list > > >>>> [email protected] > > >>>> http://lists.terracotta.org/mailman/listinfo/tc-dev > > >>>> > > >>>> > > >>> _______________________________________________ > > >>> tc-dev mailing list > > >>> [email protected] > > >>> http://lists.terracotta.org/mailman/listinfo/tc-dev > > >>> > > >>> > > >> -- > > >> Geert Bevin > > >> Terracotta - http://www.terracotta.org > > >> Uwyn "Use what you need" - http://uwyn.com > > >> RIFE Java application framework - http://rifers.org > > >> Music and words - http://gbevin.com > > >> _______________________________________________ > > >> tc-dev mailing list > > >> [email protected] > > >> http://lists.terracotta.org/mailman/listinfo/tc-dev > > >> > > > > > > _______________________________________________ > > > tc-dev mailing list > > > [email protected] > > > http://lists.terracotta.org/mailman/listinfo/tc-dev > > > > > > > _______________________________________________ > > tc-dev mailing list > > [email protected] > > http://lists.terracotta.org/mailman/listinfo/tc-dev > > _______________________________________________ > tc-dev mailing list > [email protected] > http://lists.terracotta.org/mailman/listinfo/tc-dev > -- Geert Bevin Terracotta - http://www.terracotta.org Uwyn "Use what you need" - http://uwyn.com RIFE Java application framework - http://rifers.org Music and words - http://gbevin.com _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
