You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Jean-Sebastien Delfino <js...@apache.org> on 2006/01/11 02:05:19 UTC
What are we doing with IDE specific files?
I just committed a fix to some dependencies in the .classpath files used
by the Eclipse IDE. I'd like to get the opinion of the people in the
group on how we should handle these files (and similar files for IDEA).
I looked at a few other Apache projects and they do not seem to check
these IDE specific files in their SVN repos. On the other hand, these
files are very useful... Without them it's going to be tough for
somebody to load the code in an IDE, he'll have to create the projects
by hand, adjust the dependencies etc. This is not very convenient...
What do people think? Should we keep these files under the main tree?
Keep them in SVN but under a different tree?
Try to generate them with Maven? (last time I tried with Maven 1 it
didn't work so well for me, but I'm not a Maven expert, and now we're
also moving to Maven 2...)
Any opinions?
--
Jean-Sebastien Delfino
Re: What are we doing with IDE specific files?
Posted by Srikanth Bhattiprolu <bs...@gmail.com>.
Thanks .. that worked, i was using the Maven 1.1 repository and thats why it
wasnt working.
Srikanth
On 1/13/06, Jean-Sebastien Delfino <js...@apache.org> wrote:
>
> Srikanth,
>
> Just define an M2_REPO buildpath variable in Eclipse, pointing to your
> $USER/.m2/repository. After you build the trunk with mvn all the JAR
> dependencies should be available there.
>
> More info on this thread from the maven-users mailing list:
>
> http://mail-archives.apache.org/mod_mbox/maven-users/200512.mbox/%3cop.s1avm5cvw71pkh@gundam%3e
>
> Hope this helps...
>
> --
> Jean-Sebastien
>
>
>
> Srikanth Bhattiprolu wrote:
> > I tried running the Maven 2 from the top of the trunk and i still see
> some
> > issues with the classpath. sca.spec project has the following
> classpath's
> > generated whereas the actual locations are different.
> >
> > <classpathentry kind="var" path="M2_REPO/junit/junit/3.8.1/junit-
> 3.8.1.jar
> > "/>
> > <classpathentry kind="var"
> > path="M2_REPO/org/eclipse/emf/commonj-sdo/2.1.0/commonj-sdo-2.1.0.jar"/>
> >
> > Were you guys successful in getting all the classpath's generated
> properly.
> >
> > Srikanth
> >
> > On 1/13/06, Jeremy Boynes <jb...@apache.org> wrote:
> >
> >> Jean-Sebastien Delfino wrote:
> >>
> >>> Maven 2 seems to generate the correct Eclipse project structure!
> >>>
> >>> To get all the Eclipse .project and .classpath files generated
> >>> correctly, you just need to run mvn eclipse:eclipse from the
> >>> contrib/java/trunk directory. The Maven Eclipse plugin correctly
> >>> translates the Maven artifact dependencies to Eclipse project
> >>> dependencies, so incremental compile, reference searching and
> >>> refactoring should work ok in Eclipse.
> >>>
> >>> Jeremy did you try to run the Idea plugin from the top of the tree as
> >>> well? Initially I ran mvn eclipse:eclipse from the individual project
> >>> directories and the generated .classpath files were not right,
> pointing
> >>> to the Maven repos instead of the other generated projects, this looks
> >>> similar to what you're observing with the Idea plugin. Maybe if you
> run
> >>> Maven from the top it'll do the trick?
> >>>
> >>>
> >> That is where I ran it from. From what it generated it looked like it
> >> basically treated each project as a separate thing and generated an
> Idea
> >> module for it, then added all those modules to one project.
> Inter-module
> >> dependencies were not generated and the Maven project dependencies were
> >> added as libraries for each module.
> >>
> >>
> >>> I'll test the samples and if everything works well in the IDE with the
> >>> generated projects then I'll remove the Eclipse .classpath and
> .project
> >>> files from SVN, it's much cleaner and maintainable this way.
> >>>
> >>>
> >> If it works for Eclipse then let's remove both and I will keep the Idea
> >> files somewhere separate.
> >>
> >> --
> >> Jeremy
> >>
> >>
> >
> >
>
Re: What are we doing with IDE specific files?
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Srikanth,
Just define an M2_REPO buildpath variable in Eclipse, pointing to your
$USER/.m2/repository. After you build the trunk with mvn all the JAR
dependencies should be available there.
More info on this thread from the maven-users mailing list:
http://mail-archives.apache.org/mod_mbox/maven-users/200512.mbox/%3cop.s1avm5cvw71pkh@gundam%3e
Hope this helps...
--
Jean-Sebastien
Srikanth Bhattiprolu wrote:
> I tried running the Maven 2 from the top of the trunk and i still see some
> issues with the classpath. sca.spec project has the following classpath's
> generated whereas the actual locations are different.
>
> <classpathentry kind="var" path="M2_REPO/junit/junit/3.8.1/junit-3.8.1.jar
> "/>
> <classpathentry kind="var"
> path="M2_REPO/org/eclipse/emf/commonj-sdo/2.1.0/commonj-sdo-2.1.0.jar"/>
>
> Were you guys successful in getting all the classpath's generated properly.
>
> Srikanth
>
> On 1/13/06, Jeremy Boynes <jb...@apache.org> wrote:
>
>> Jean-Sebastien Delfino wrote:
>>
>>> Maven 2 seems to generate the correct Eclipse project structure!
>>>
>>> To get all the Eclipse .project and .classpath files generated
>>> correctly, you just need to run mvn eclipse:eclipse from the
>>> contrib/java/trunk directory. The Maven Eclipse plugin correctly
>>> translates the Maven artifact dependencies to Eclipse project
>>> dependencies, so incremental compile, reference searching and
>>> refactoring should work ok in Eclipse.
>>>
>>> Jeremy did you try to run the Idea plugin from the top of the tree as
>>> well? Initially I ran mvn eclipse:eclipse from the individual project
>>> directories and the generated .classpath files were not right, pointing
>>> to the Maven repos instead of the other generated projects, this looks
>>> similar to what you're observing with the Idea plugin. Maybe if you run
>>> Maven from the top it'll do the trick?
>>>
>>>
>> That is where I ran it from. From what it generated it looked like it
>> basically treated each project as a separate thing and generated an Idea
>> module for it, then added all those modules to one project. Inter-module
>> dependencies were not generated and the Maven project dependencies were
>> added as libraries for each module.
>>
>>
>>> I'll test the samples and if everything works well in the IDE with the
>>> generated projects then I'll remove the Eclipse .classpath and .project
>>> files from SVN, it's much cleaner and maintainable this way.
>>>
>>>
>> If it works for Eclipse then let's remove both and I will keep the Idea
>> files somewhere separate.
>>
>> --
>> Jeremy
>>
>>
>
>
Re: What are we doing with IDE specific files?
Posted by Srikanth Bhattiprolu <bs...@gmail.com>.
I tried running the Maven 2 from the top of the trunk and i still see some
issues with the classpath. sca.spec project has the following classpath's
generated whereas the actual locations are different.
<classpathentry kind="var" path="M2_REPO/junit/junit/3.8.1/junit-3.8.1.jar
"/>
<classpathentry kind="var"
path="M2_REPO/org/eclipse/emf/commonj-sdo/2.1.0/commonj-sdo-2.1.0.jar"/>
Were you guys successful in getting all the classpath's generated properly.
Srikanth
On 1/13/06, Jeremy Boynes <jb...@apache.org> wrote:
>
> Jean-Sebastien Delfino wrote:
> > Maven 2 seems to generate the correct Eclipse project structure!
> >
> > To get all the Eclipse .project and .classpath files generated
> > correctly, you just need to run mvn eclipse:eclipse from the
> > contrib/java/trunk directory. The Maven Eclipse plugin correctly
> > translates the Maven artifact dependencies to Eclipse project
> > dependencies, so incremental compile, reference searching and
> > refactoring should work ok in Eclipse.
> >
> > Jeremy did you try to run the Idea plugin from the top of the tree as
> > well? Initially I ran mvn eclipse:eclipse from the individual project
> > directories and the generated .classpath files were not right, pointing
> > to the Maven repos instead of the other generated projects, this looks
> > similar to what you're observing with the Idea plugin. Maybe if you run
> > Maven from the top it'll do the trick?
> >
>
> That is where I ran it from. From what it generated it looked like it
> basically treated each project as a separate thing and generated an Idea
> module for it, then added all those modules to one project. Inter-module
> dependencies were not generated and the Maven project dependencies were
> added as libraries for each module.
>
> > I'll test the samples and if everything works well in the IDE with the
> > generated projects then I'll remove the Eclipse .classpath and .project
> > files from SVN, it's much cleaner and maintainable this way.
> >
>
> If it works for Eclipse then let's remove both and I will keep the Idea
> files somewhere separate.
>
> --
> Jeremy
>
Re: What are we doing with IDE specific files?
Posted by Jeremy Boynes <jb...@apache.org>.
Jean-Sebastien Delfino wrote:
> Maven 2 seems to generate the correct Eclipse project structure!
>
> To get all the Eclipse .project and .classpath files generated
> correctly, you just need to run mvn eclipse:eclipse from the
> contrib/java/trunk directory. The Maven Eclipse plugin correctly
> translates the Maven artifact dependencies to Eclipse project
> dependencies, so incremental compile, reference searching and
> refactoring should work ok in Eclipse.
>
> Jeremy did you try to run the Idea plugin from the top of the tree as
> well? Initially I ran mvn eclipse:eclipse from the individual project
> directories and the generated .classpath files were not right, pointing
> to the Maven repos instead of the other generated projects, this looks
> similar to what you're observing with the Idea plugin. Maybe if you run
> Maven from the top it'll do the trick?
>
That is where I ran it from. From what it generated it looked like it
basically treated each project as a separate thing and generated an Idea
module for it, then added all those modules to one project. Inter-module
dependencies were not generated and the Maven project dependencies were
added as libraries for each module.
> I'll test the samples and if everything works well in the IDE with the
> generated projects then I'll remove the Eclipse .classpath and .project
> files from SVN, it's much cleaner and maintainable this way.
>
If it works for Eclipse then let's remove both and I will keep the Idea
files somewhere separate.
--
Jeremy
Re: What are we doing with IDE specific files?
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Maven 2 seems to generate the correct Eclipse project structure!
To get all the Eclipse .project and .classpath files generated
correctly, you just need to run mvn eclipse:eclipse from the
contrib/java/trunk directory. The Maven Eclipse plugin correctly
translates the Maven artifact dependencies to Eclipse project
dependencies, so incremental compile, reference searching and
refactoring should work ok in Eclipse.
Jeremy did you try to run the Idea plugin from the top of the tree as
well? Initially I ran mvn eclipse:eclipse from the individual project
directories and the generated .classpath files were not right, pointing
to the Maven repos instead of the other generated projects, this looks
similar to what you're observing with the Idea plugin. Maybe if you run
Maven from the top it'll do the trick?
I'll test the samples and if everything works well in the IDE with the
generated projects then I'll remove the Eclipse .classpath and .project
files from SVN, it's much cleaner and maintainable this way.
--
Jean-Sebastien
Jeremy Boynes wrote:
> Jeremy Boynes wrote:
>
>> I'd suggest getting to m2 then try the generation again. If it works
>> then we are set and can just remove them, if not then let's figure out
>> how we can remove them from the trunk but still provide them for new users.
>>
>>
>
> I tried the idea generation and it seemed to generate a bunch of
> individual projects. Although the modules were all there, they were all
> isolated from each other which makes me think that things like global
> refectoring would not work properly.
>
> --
> Jeremy
>
>
Re: What are we doing with IDE specific files?
Posted by Jeremy Boynes <jb...@apache.org>.
Jeremy Boynes wrote:
>
> I'd suggest getting to m2 then try the generation again. If it works
> then we are set and can just remove them, if not then let's figure out
> how we can remove them from the trunk but still provide them for new users.
>
I tried the idea generation and it seemed to generate a bunch of
individual projects. Although the modules were all there, they were all
isolated from each other which makes me think that things like global
refectoring would not work properly.
--
Jeremy
Re: What are we doing with IDE specific files?
Posted by ja...@sybase.com.
Jeremy wrote:
> I'd suggest getting to m2 then try the generation again.
> If it works then we are set and can just remove them, if
> not then let's figure out how we can remove them from the
> trunk but still provide them for new users.
I will do some testing of Eclipse project generation as part
of the m2 port.
--
Jack Unrue
junrue@sybase.com
Re: What are we doing with IDE specific files?
Posted by Jeremy Boynes <jb...@apache.org>.
I would prefer we remove them from the main trunk and if possible remove
them all together. This emphasizes the canon that the one true build is
using the build system.
Having said that, having them available makes it easier for many people
to get started so there should be an easy way to get them. If, as
Guillame suggests, they can be generated by Maven then we should do
that; however, Sebastien said he had issues with what was generated for
Eclipse and (admittedly a long time ago) I previously had problems with
Idea.
I'd suggest getting to m2 then try the generation again. If it works
then we are set and can just remove them, if not then let's figure out
how we can remove them from the trunk but still provide them for new users.
--
Jeremy
Jean-Sebastien Delfino wrote:
> I just committed a fix to some dependencies in the .classpath files used
> by the Eclipse IDE. I'd like to get the opinion of the people in the
> group on how we should handle these files (and similar files for IDEA).
>
> I looked at a few other Apache projects and they do not seem to check
> these IDE specific files in their SVN repos. On the other hand, these
> files are very useful... Without them it's going to be tough for
> somebody to load the code in an IDE, he'll have to create the projects
> by hand, adjust the dependencies etc. This is not very convenient...
>
> What do people think? Should we keep these files under the main tree?
> Keep them in SVN but under a different tree?
> Try to generate them with Maven? (last time I tried with Maven 1 it
> didn't work so well for me, but I'm not a Maven expert, and now we're
> also moving to Maven 2...)
>
> Any opinions?
>
Re: What are we doing with IDE specific files?
Posted by Guillaume Nodet <gu...@worldonline.fr>.
Usually, these files are created by maven.
Using maven 1, you can run "maven eclipse" and this will generate the
files for you.
In case of multiprojects, you could use "maven -Dgoal=eclipse
multiproject:goal".
This can be simplified by defining a new goal in the root maven.xml that
will handle that.
The same is true for IDEA project and to be sure these files are
synchronized with the maven pom,
the easiest way is to not put them in svn.
Cheers,
Guillaume Nodet
Jean-Sebastien Delfino wrote:
> I just committed a fix to some dependencies in the .classpath files
> used by the Eclipse IDE. I'd like to get the opinion of the people in
> the group on how we should handle these files (and similar files for
> IDEA).
>
> I looked at a few other Apache projects and they do not seem to check
> these IDE specific files in their SVN repos. On the other hand, these
> files are very useful... Without them it's going to be tough for
> somebody to load the code in an IDE, he'll have to create the projects
> by hand, adjust the dependencies etc. This is not very convenient...
>
> What do people think? Should we keep these files under the main tree?
> Keep them in SVN but under a different tree?
> Try to generate them with Maven? (last time I tried with Maven 1 it
> didn't work so well for me, but I'm not a Maven expert, and now we're
> also moving to Maven 2...)
>
> Any opinions?
>