You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by James Mitchell <jm...@apache.org> on 2005/06/24 19:41:33 UTC
Re: Eclipse .project & .classpath files (is he talking about Maven again?!?!?!)
I know I don't have a vote here ;) but if I did, it would be -1
Best case
---------
By doing this, you are forcing every developer to deal with files that will
always appear to have changes/differences. Yes, Eclipse will touch those
files.
In most projects that I've been involved in. You generally want to ignore
those files because they assume a certain IDE is being used by all.
Worst case
----------
What do you propose someone do if they need that spot (i.e. they are using a
different IDE and different format, which requires a ".classpath" file in
the place of the one under svn)?
Let's meet in the middle
------------------------
Not to beat the Maven drum any more than I have to....but that's actually
one of the cool features of Maven. With a proper Maven project.xml file
describing dependencies, creating the .project and .classpath files for
*any* IDE is as simple as...
http://maven.apache.org/reference/plugins/eclipse/
http://maven.apache.org/reference/plugins/idea/
http://maven.apache.org/reference/plugins/jbuilder/
...ah shucks, take your pick...
http://maven.apache.org/reference/plugins/index.html
FYI - I will be Mavenizing the MyFaces build within the next couple of
weeks. Whether it is accepted into SVN is another issue for another thread.
If not, I will make it available somewhere (wiki, docs, something).
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: jmitchell@apache.org
Skype: jmitchtx
----- Original Message -----
From: "Bill Dudney" <bd...@mac.com>
To: "MyFaces Development" <de...@myfaces.apache.org>
Sent: Friday, June 24, 2005 1:05 PM
Subject: Eclipse .project & .classpath files
> Hi All,
>
> i'd like to supply an Eclipse configuration for the projects that Sean is
> currently working to get set up in SVN. The projects would work assuming
> the dependencies are downloaded via 'download- dependencies'. That would
> get someone up and running easily in Eclipse. I'd like to put these files
> under each of the subprojects (i.e. api, impl, etc.) and under the
> projects (current, tomahawk etc.)
>
> So, once you download one of the projects you could define a variable and
> run 'ant download-dependencies' and you'd have a ready to go MyFaces
> project in eclipse.
>
> Thoughts?
>
> TTFN,
>
> -bd-
>
>
>
Re: Eclipse .project & .classpath files (is he talking about Maven again?!?!?!)
Posted by Sean Schofield <se...@gmail.com>.
I'm a little busy with the SVN reorg and build to concentrate on the
various arguments related to this issue. At this point I'm fine with
James (or anyone else) experimenting with IDE project files, Maven,
etc. but I reserve the right to be -1 once I get a chance to sit down
and think about it some.
Right now the top priority has to be square away SVN, the build, etc.
If we find that things that we have added (project files, Maven)
aren't working we can easily dump them or modify them as we see fit.
So no harm in adding them but lets consider them to be experimental
until we can see how things will shake out.
sean
On 6/27/05, Manfred Geiler <ma...@gmail.com> wrote:
> +1 for having these convenient project files available. hey, we are a
> community, why not share those files for convenience. but you are
> right in many points, and I don't think anymore that the svn repo is
> the right place for this kind of stuff. So one alternative would be
> the wiki, but we cannot have downloadable files there, right? So where
> should we put them if not into the repository?
> Therefore
> +0.5 for putting IDE project files in a special folder in the repo
> ("goodies", "experimental", ...?)
>
> WDYT?
>
> -Manfred
>
>
> 2005/6/24, Martin Cooper <ma...@apache.org>:
> >
> >
> > On Fri, 24 Jun 2005, James Mitchell wrote:
> >
> > > I know I don't have a vote here ;) but if I did, it would be -1
> >
> > I too would be -1, but for a different set of reasons.
> >
> > 1) Anyone not using Eclipse will break the Eclipse build any time they
> > make a change to the dependecies. You can't expect people to update IDE
> > specific files if they don't use that IDE.
> >
> > 2) Sharing these files almost invariably requires each user to set up
> > project and workspace variables. Either this quickly gets complicated, or
> > the user has limited flexibility in how to configure their system. Also,
> > the workspace variables can interfere with other projects.
> >
> > 3) It doesn't scale. Someone has already suggested doing the same thing
> > for IDEA. What about NetBeans, JBuilder, JDeveloper, WSAD, CodeWright,
> > MultiEdit, ...? Where do you stop, and how do you maintain them all?
> > Someone coming to project for the first time will expect them to work if
> > they're there.
> >
> > --
> > Martin Cooper
> >
> >
> > > Best case
> > > ---------
> > > By doing this, you are forcing every developer to deal with files that will
> > > always appear to have changes/differences. Yes, Eclipse will touch those
> > > files.
> > >
> > > In most projects that I've been involved in. You generally want to ignore
> > > those files because they assume a certain IDE is being used by all.
> > >
> > >
> > > Worst case
> > > ---------- What do you propose someone do if they need that spot (i.e. they
> > > are using a different IDE and different format, which requires a ".classpath"
> > > file in the place of the one under svn)?
> > >
> > >
> > > Let's meet in the middle
> > > ------------------------
> > > Not to beat the Maven drum any more than I have to....but that's actually one
> > > of the cool features of Maven. With a proper Maven project.xml file
> > > describing dependencies, creating the .project and .classpath files for *any*
> > > IDE is as simple as...
> > >
> > > http://maven.apache.org/reference/plugins/eclipse/
> > > http://maven.apache.org/reference/plugins/idea/
> > > http://maven.apache.org/reference/plugins/jbuilder/
> > >
> > >
> > > ...ah shucks, take your pick...
> > >
> > > http://maven.apache.org/reference/plugins/index.html
> > >
> > >
> > > FYI - I will be Mavenizing the MyFaces build within the next couple of weeks.
> > > Whether it is accepted into SVN is another issue for another thread. If not,
> > > I will make it available somewhere (wiki, docs, something).
> > >
> > >
> > > --
> > > James Mitchell
> > > Software Engineer / Open Source Evangelist
> > > Consulting / Mentoring / Freelance
> > > EdgeTech, Inc.
> > > http://www.edgetechservices.net/
> > > 678.910.8017
> > > AIM: jmitchtx
> > > Yahoo: jmitchtx
> > > MSN: jmitchell@apache.org
> > > Skype: jmitchtx
> > >
> > > ----- Original Message ----- From: "Bill Dudney" <bd...@mac.com>
> > > To: "MyFaces Development" <de...@myfaces.apache.org>
> > > Sent: Friday, June 24, 2005 1:05 PM
> > > Subject: Eclipse .project & .classpath files
> > >
> > >
> > >> Hi All,
> > >>
> > >> i'd like to supply an Eclipse configuration for the projects that Sean is
> > >> currently working to get set up in SVN. The projects would work assuming
> > >> the dependencies are downloaded via 'download- dependencies'. That would
> > >> get someone up and running easily in Eclipse. I'd like to put these files
> > >> under each of the subprojects (i.e. api, impl, etc.) and under the
> > >> projects (current, tomahawk etc.)
> > >>
> > >> So, once you download one of the projects you could define a variable and
> > >> run 'ant download-dependencies' and you'd have a ready to go MyFaces
> > >> project in eclipse.
> > >>
> > >> Thoughts?
> > >>
> > >> TTFN,
> > >>
> > >> -bd-
> > >>
> > >>
> > >>
> > >
> > >
> > >
> >
>
Re: Eclipse .project & .classpath files (is he talking about Maven again?!?!?!)
Posted by Manfred Geiler <ma...@gmail.com>.
+1 for having these convenient project files available. hey, we are a
community, why not share those files for convenience. but you are
right in many points, and I don't think anymore that the svn repo is
the right place for this kind of stuff. So one alternative would be
the wiki, but we cannot have downloadable files there, right? So where
should we put them if not into the repository?
Therefore
+0.5 for putting IDE project files in a special folder in the repo
("goodies", "experimental", ...?)
WDYT?
-Manfred
2005/6/24, Martin Cooper <ma...@apache.org>:
>
>
> On Fri, 24 Jun 2005, James Mitchell wrote:
>
> > I know I don't have a vote here ;) but if I did, it would be -1
>
> I too would be -1, but for a different set of reasons.
>
> 1) Anyone not using Eclipse will break the Eclipse build any time they
> make a change to the dependecies. You can't expect people to update IDE
> specific files if they don't use that IDE.
>
> 2) Sharing these files almost invariably requires each user to set up
> project and workspace variables. Either this quickly gets complicated, or
> the user has limited flexibility in how to configure their system. Also,
> the workspace variables can interfere with other projects.
>
> 3) It doesn't scale. Someone has already suggested doing the same thing
> for IDEA. What about NetBeans, JBuilder, JDeveloper, WSAD, CodeWright,
> MultiEdit, ...? Where do you stop, and how do you maintain them all?
> Someone coming to project for the first time will expect them to work if
> they're there.
>
> --
> Martin Cooper
>
>
> > Best case
> > ---------
> > By doing this, you are forcing every developer to deal with files that will
> > always appear to have changes/differences. Yes, Eclipse will touch those
> > files.
> >
> > In most projects that I've been involved in. You generally want to ignore
> > those files because they assume a certain IDE is being used by all.
> >
> >
> > Worst case
> > ---------- What do you propose someone do if they need that spot (i.e. they
> > are using a different IDE and different format, which requires a ".classpath"
> > file in the place of the one under svn)?
> >
> >
> > Let's meet in the middle
> > ------------------------
> > Not to beat the Maven drum any more than I have to....but that's actually one
> > of the cool features of Maven. With a proper Maven project.xml file
> > describing dependencies, creating the .project and .classpath files for *any*
> > IDE is as simple as...
> >
> > http://maven.apache.org/reference/plugins/eclipse/
> > http://maven.apache.org/reference/plugins/idea/
> > http://maven.apache.org/reference/plugins/jbuilder/
> >
> >
> > ...ah shucks, take your pick...
> >
> > http://maven.apache.org/reference/plugins/index.html
> >
> >
> > FYI - I will be Mavenizing the MyFaces build within the next couple of weeks.
> > Whether it is accepted into SVN is another issue for another thread. If not,
> > I will make it available somewhere (wiki, docs, something).
> >
> >
> > --
> > James Mitchell
> > Software Engineer / Open Source Evangelist
> > Consulting / Mentoring / Freelance
> > EdgeTech, Inc.
> > http://www.edgetechservices.net/
> > 678.910.8017
> > AIM: jmitchtx
> > Yahoo: jmitchtx
> > MSN: jmitchell@apache.org
> > Skype: jmitchtx
> >
> > ----- Original Message ----- From: "Bill Dudney" <bd...@mac.com>
> > To: "MyFaces Development" <de...@myfaces.apache.org>
> > Sent: Friday, June 24, 2005 1:05 PM
> > Subject: Eclipse .project & .classpath files
> >
> >
> >> Hi All,
> >>
> >> i'd like to supply an Eclipse configuration for the projects that Sean is
> >> currently working to get set up in SVN. The projects would work assuming
> >> the dependencies are downloaded via 'download- dependencies'. That would
> >> get someone up and running easily in Eclipse. I'd like to put these files
> >> under each of the subprojects (i.e. api, impl, etc.) and under the
> >> projects (current, tomahawk etc.)
> >>
> >> So, once you download one of the projects you could define a variable and
> >> run 'ant download-dependencies' and you'd have a ready to go MyFaces
> >> project in eclipse.
> >>
> >> Thoughts?
> >>
> >> TTFN,
> >>
> >> -bd-
> >>
> >>
> >>
> >
> >
> >
>
Re: Eclipse .project & .classpath files (is he talking about Maven again?!?!?!)
Posted by John Fallows <jo...@gmail.com>.
Generation of the various IDE-specific project files from a single
source of truth would get my vote. :-)
Kind Regards,
John Fallows.
On 6/24/05, Martin Cooper <ma...@apache.org> wrote:
>
>
> On Fri, 24 Jun 2005, James Mitchell wrote:
>
> > I know I don't have a vote here ;) but if I did, it would be -1
>
> I too would be -1, but for a different set of reasons.
>
> 1) Anyone not using Eclipse will break the Eclipse build any time they
> make a change to the dependecies. You can't expect people to update IDE
> specific files if they don't use that IDE.
>
> 2) Sharing these files almost invariably requires each user to set up
> project and workspace variables. Either this quickly gets complicated, or
> the user has limited flexibility in how to configure their system. Also,
> the workspace variables can interfere with other projects.
>
> 3) It doesn't scale. Someone has already suggested doing the same thing
> for IDEA. What about NetBeans, JBuilder, JDeveloper, WSAD, CodeWright,
> MultiEdit, ...? Where do you stop, and how do you maintain them all?
> Someone coming to project for the first time will expect them to work if
> they're there.
>
> --
> Martin Cooper
>
>
> > Best case
> > ---------
> > By doing this, you are forcing every developer to deal with files that will
> > always appear to have changes/differences. Yes, Eclipse will touch those
> > files.
> >
> > In most projects that I've been involved in. You generally want to ignore
> > those files because they assume a certain IDE is being used by all.
> >
> >
> > Worst case
> > ---------- What do you propose someone do if they need that spot (i.e. they
> > are using a different IDE and different format, which requires a ".classpath"
> > file in the place of the one under svn)?
> >
> >
> > Let's meet in the middle
> > ------------------------
> > Not to beat the Maven drum any more than I have to....but that's actually one
> > of the cool features of Maven. With a proper Maven project.xml file
> > describing dependencies, creating the .project and .classpath files for *any*
> > IDE is as simple as...
> >
> > http://maven.apache.org/reference/plugins/eclipse/
> > http://maven.apache.org/reference/plugins/idea/
> > http://maven.apache.org/reference/plugins/jbuilder/
> >
> >
> > ...ah shucks, take your pick...
> >
> > http://maven.apache.org/reference/plugins/index.html
> >
> >
> > FYI - I will be Mavenizing the MyFaces build within the next couple of weeks.
> > Whether it is accepted into SVN is another issue for another thread. If not,
> > I will make it available somewhere (wiki, docs, something).
> >
> >
> > --
> > James Mitchell
> > Software Engineer / Open Source Evangelist
> > Consulting / Mentoring / Freelance
> > EdgeTech, Inc.
> > http://www.edgetechservices.net/
> > 678.910.8017
> > AIM: jmitchtx
> > Yahoo: jmitchtx
> > MSN: jmitchell@apache.org
> > Skype: jmitchtx
> >
> > ----- Original Message ----- From: "Bill Dudney" <bd...@mac.com>
> > To: "MyFaces Development" <de...@myfaces.apache.org>
> > Sent: Friday, June 24, 2005 1:05 PM
> > Subject: Eclipse .project & .classpath files
> >
> >
> >> Hi All,
> >>
> >> i'd like to supply an Eclipse configuration for the projects that Sean is
> >> currently working to get set up in SVN. The projects would work assuming
> >> the dependencies are downloaded via 'download- dependencies'. That would
> >> get someone up and running easily in Eclipse. I'd like to put these files
> >> under each of the subprojects (i.e. api, impl, etc.) and under the
> >> projects (current, tomahawk etc.)
> >>
> >> So, once you download one of the projects you could define a variable and
> >> run 'ant download-dependencies' and you'd have a ready to go MyFaces
> >> project in eclipse.
> >>
> >> Thoughts?
> >>
> >> TTFN,
> >>
> >> -bd-
> >>
> >>
> >>
> >
> >
> >
>
Re: Eclipse .project & .classpath files (is he talking about Maven
again?!?!?!)
Posted by Martin Cooper <ma...@apache.org>.
On Fri, 24 Jun 2005, James Mitchell wrote:
> I know I don't have a vote here ;) but if I did, it would be -1
I too would be -1, but for a different set of reasons.
1) Anyone not using Eclipse will break the Eclipse build any time they
make a change to the dependecies. You can't expect people to update IDE
specific files if they don't use that IDE.
2) Sharing these files almost invariably requires each user to set up
project and workspace variables. Either this quickly gets complicated, or
the user has limited flexibility in how to configure their system. Also,
the workspace variables can interfere with other projects.
3) It doesn't scale. Someone has already suggested doing the same thing
for IDEA. What about NetBeans, JBuilder, JDeveloper, WSAD, CodeWright,
MultiEdit, ...? Where do you stop, and how do you maintain them all?
Someone coming to project for the first time will expect them to work if
they're there.
--
Martin Cooper
> Best case
> ---------
> By doing this, you are forcing every developer to deal with files that will
> always appear to have changes/differences. Yes, Eclipse will touch those
> files.
>
> In most projects that I've been involved in. You generally want to ignore
> those files because they assume a certain IDE is being used by all.
>
>
> Worst case
> ---------- What do you propose someone do if they need that spot (i.e. they
> are using a different IDE and different format, which requires a ".classpath"
> file in the place of the one under svn)?
>
>
> Let's meet in the middle
> ------------------------
> Not to beat the Maven drum any more than I have to....but that's actually one
> of the cool features of Maven. With a proper Maven project.xml file
> describing dependencies, creating the .project and .classpath files for *any*
> IDE is as simple as...
>
> http://maven.apache.org/reference/plugins/eclipse/
> http://maven.apache.org/reference/plugins/idea/
> http://maven.apache.org/reference/plugins/jbuilder/
>
>
> ...ah shucks, take your pick...
>
> http://maven.apache.org/reference/plugins/index.html
>
>
> FYI - I will be Mavenizing the MyFaces build within the next couple of weeks.
> Whether it is accepted into SVN is another issue for another thread. If not,
> I will make it available somewhere (wiki, docs, something).
>
>
> --
> James Mitchell
> Software Engineer / Open Source Evangelist
> Consulting / Mentoring / Freelance
> EdgeTech, Inc.
> http://www.edgetechservices.net/
> 678.910.8017
> AIM: jmitchtx
> Yahoo: jmitchtx
> MSN: jmitchell@apache.org
> Skype: jmitchtx
>
> ----- Original Message ----- From: "Bill Dudney" <bd...@mac.com>
> To: "MyFaces Development" <de...@myfaces.apache.org>
> Sent: Friday, June 24, 2005 1:05 PM
> Subject: Eclipse .project & .classpath files
>
>
>> Hi All,
>>
>> i'd like to supply an Eclipse configuration for the projects that Sean is
>> currently working to get set up in SVN. The projects would work assuming
>> the dependencies are downloaded via 'download- dependencies'. That would
>> get someone up and running easily in Eclipse. I'd like to put these files
>> under each of the subprojects (i.e. api, impl, etc.) and under the
>> projects (current, tomahawk etc.)
>>
>> So, once you download one of the projects you could define a variable and
>> run 'ant download-dependencies' and you'd have a ready to go MyFaces
>> project in eclipse.
>>
>> Thoughts?
>>
>> TTFN,
>>
>> -bd-
>>
>>
>>
>
>
>
Re: Antwort: Re: Eclipse .project & .classpath files (is he talking
about Maven again?!?!?!)
Posted by Werner Punz <we...@gmx.at>.
christian.rueedi@globus.ch wrote:
>
> Hi there,
>
> I just want to give my response aswell. As a rarely jsf developer, I'm
> always in the situation, that
> I've got to setup my myfaces enviroment from new, because I'm not always
> on track with the changes.
> Even Eclipse and its different web/jsf plugins change so quickly...
> It would save me alot of time if I could take the settings from one of
> the developers.
>
> It shouldn't be, that it is a must to use it. But for those who need a
> jump start.... it would be very comfortable...
>
> greets
>
> Chris
>
>
>
>
> *"James Mitchell" <jm...@apache.org>*
>
> 24.06.2005 19:41
> Bitte antworten an "MyFaces Development"
>
>
> An: "MyFaces Development" <de...@myfaces.apache.org>
> Kopie:
> Thema: Re: Eclipse .project & .classpath files (is he
> talking about Maven again?!?!?!)
>
>
>
>
> I know I don't have a vote here ;) but if I did, it would be -1
>
> Best case
> ---------
> By doing this, you are forcing every developer to deal with files that will
> always appear to have changes/differences. Yes, Eclipse will touch those
> files.
>
> In most projects that I've been involved in. You generally want to ignore
> those files because they assume a certain IDE is being used by all.
>
>
I am in the same league as you although being more than familiar with
ant, have been using it myself for several years and many projects, I
always prefer to do the builds from an IDE and use ant only for cross
platform project team synching (aka stable build check)
and packaging.
Having a simple save cycle like in eclipse is so much faster than having
to go through ant constantly.
Although ant has its merits, I would welcome eclipse templates in a
separate sidedir which could be used as a jumpstart for development.
Re: Eclipse .project & .classpath files (is he talking about Maven again?!?!?!)
Posted by James Mitchell <jm...@apache.org>.
Oh, I know. Been there, done that...remember.
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: jmitchell@apache.org
Skype: jmitchtx
----- Original Message -----
From: "Sean Schofield" <se...@gmail.com>
To: "MyFaces Development" <de...@myfaces.apache.org>
Sent: Friday, June 24, 2005 1:53 PM
Subject: Re: Eclipse .project & .classpath files (is he talking about Maven
again?!?!?!)
I'm willing to discuss the Maven option but I think we need to get Ant
working short term. James, its cool to work on your maven stuff just
be aware that the project is going to shift around these next couple
of days.
sean
On 6/24/05, Bill Dudney <bd...@mac.com> wrote:
> Hi James,
>
> Thanks for the feed-back. Good point about Eclipse touching the
> files. Other option is putting the files into a subdirectory as we
> used to have them. Also I could just post them on the wiki as you are
> thinking of doing with the POM.
>
> My issue with maven is upkeep. If we have the ant build that everyone
> else is using and a POM for maven that only some are using there will
> be stuff that goes stale.
>
> Getting a maven generated .project & .classpath is a major win of
> using maven agreed. I believe the maven/ant discussion has been
> beaten to death on this list though and I for one don't want to open
> that up again ;-)
>
> TTFN,
>
> -bd-
>
> On Jun 24, 2005, at 11:41 AM, James Mitchell wrote:
>
> > I know I don't have a vote here ;) but if I did, it would be -1
> >
> > Best case
> > ---------
> > By doing this, you are forcing every developer to deal with files
> > that will always appear to have changes/differences. Yes, Eclipse
> > will touch those files.
> >
> > In most projects that I've been involved in. You generally want to
> > ignore those files because they assume a certain IDE is being used
> > by all.
> >
> >
> > Worst case
> > ---------- What do you propose someone do if they need that spot
> > (i.e. they are using a different IDE and different format, which
> > requires a ".classpath" file in the place of the one under svn)?
> >
> >
> > Let's meet in the middle
> > ------------------------
> > Not to beat the Maven drum any more than I have to....but that's
> > actually one of the cool features of Maven. With a proper Maven
> > project.xml file describing dependencies, creating the .project
> > and .classpath files for *any* IDE is as simple as...
> >
> > http://maven.apache.org/reference/plugins/eclipse/
> > http://maven.apache.org/reference/plugins/idea/
> > http://maven.apache.org/reference/plugins/jbuilder/
> >
> >
> > ...ah shucks, take your pick...
> >
> > http://maven.apache.org/reference/plugins/index.html
> >
> >
> > FYI - I will be Mavenizing the MyFaces build within the next couple
> > of weeks. Whether it is accepted into SVN is another issue for
> > another thread. If not, I will make it available somewhere (wiki,
> > docs, something).
> >
> >
> > --
> > James Mitchell
> > Software Engineer / Open Source Evangelist
> > Consulting / Mentoring / Freelance
> > EdgeTech, Inc.
> > http://www.edgetechservices.net/
> > 678.910.8017
> > AIM: jmitchtx
> > Yahoo: jmitchtx
> > MSN: jmitchell@apache.org
> > Skype: jmitchtx
> >
> > ----- Original Message ----- From: "Bill Dudney" <bd...@mac.com>
> > To: "MyFaces Development" <de...@myfaces.apache.org>
> > Sent: Friday, June 24, 2005 1:05 PM
> > Subject: Eclipse .project & .classpath files
> >
> >
> >
> >> Hi All,
> >>
> >> i'd like to supply an Eclipse configuration for the projects that
> >> Sean is currently working to get set up in SVN. The projects
> >> would work assuming the dependencies are downloaded via
> >> 'download- dependencies'. That would get someone up and running
> >> easily in Eclipse. I'd like to put these files under each of the
> >> subprojects (i.e. api, impl, etc.) and under the projects
> >> (current, tomahawk etc.)
> >>
> >> So, once you download one of the projects you could define a
> >> variable and run 'ant download-dependencies' and you'd have a
> >> ready to go MyFaces project in eclipse.
> >>
> >> Thoughts?
> >>
> >> TTFN,
> >>
> >> -bd-
> >>
> >>
> >>
> >
> >
> >
>
>
Re: Eclipse .project & .classpath files (is he talking about Maven again?!?!?!)
Posted by Sean Schofield <se...@gmail.com>.
I'm willing to discuss the Maven option but I think we need to get Ant
working short term. James, its cool to work on your maven stuff just
be aware that the project is going to shift around these next couple
of days.
sean
On 6/24/05, Bill Dudney <bd...@mac.com> wrote:
> Hi James,
>
> Thanks for the feed-back. Good point about Eclipse touching the
> files. Other option is putting the files into a subdirectory as we
> used to have them. Also I could just post them on the wiki as you are
> thinking of doing with the POM.
>
> My issue with maven is upkeep. If we have the ant build that everyone
> else is using and a POM for maven that only some are using there will
> be stuff that goes stale.
>
> Getting a maven generated .project & .classpath is a major win of
> using maven agreed. I believe the maven/ant discussion has been
> beaten to death on this list though and I for one don't want to open
> that up again ;-)
>
> TTFN,
>
> -bd-
>
> On Jun 24, 2005, at 11:41 AM, James Mitchell wrote:
>
> > I know I don't have a vote here ;) but if I did, it would be -1
> >
> > Best case
> > ---------
> > By doing this, you are forcing every developer to deal with files
> > that will always appear to have changes/differences. Yes, Eclipse
> > will touch those files.
> >
> > In most projects that I've been involved in. You generally want to
> > ignore those files because they assume a certain IDE is being used
> > by all.
> >
> >
> > Worst case
> > ---------- What do you propose someone do if they need that spot
> > (i.e. they are using a different IDE and different format, which
> > requires a ".classpath" file in the place of the one under svn)?
> >
> >
> > Let's meet in the middle
> > ------------------------
> > Not to beat the Maven drum any more than I have to....but that's
> > actually one of the cool features of Maven. With a proper Maven
> > project.xml file describing dependencies, creating the .project
> > and .classpath files for *any* IDE is as simple as...
> >
> > http://maven.apache.org/reference/plugins/eclipse/
> > http://maven.apache.org/reference/plugins/idea/
> > http://maven.apache.org/reference/plugins/jbuilder/
> >
> >
> > ...ah shucks, take your pick...
> >
> > http://maven.apache.org/reference/plugins/index.html
> >
> >
> > FYI - I will be Mavenizing the MyFaces build within the next couple
> > of weeks. Whether it is accepted into SVN is another issue for
> > another thread. If not, I will make it available somewhere (wiki,
> > docs, something).
> >
> >
> > --
> > James Mitchell
> > Software Engineer / Open Source Evangelist
> > Consulting / Mentoring / Freelance
> > EdgeTech, Inc.
> > http://www.edgetechservices.net/
> > 678.910.8017
> > AIM: jmitchtx
> > Yahoo: jmitchtx
> > MSN: jmitchell@apache.org
> > Skype: jmitchtx
> >
> > ----- Original Message ----- From: "Bill Dudney" <bd...@mac.com>
> > To: "MyFaces Development" <de...@myfaces.apache.org>
> > Sent: Friday, June 24, 2005 1:05 PM
> > Subject: Eclipse .project & .classpath files
> >
> >
> >
> >> Hi All,
> >>
> >> i'd like to supply an Eclipse configuration for the projects that
> >> Sean is currently working to get set up in SVN. The projects
> >> would work assuming the dependencies are downloaded via
> >> 'download- dependencies'. That would get someone up and running
> >> easily in Eclipse. I'd like to put these files under each of the
> >> subprojects (i.e. api, impl, etc.) and under the projects
> >> (current, tomahawk etc.)
> >>
> >> So, once you download one of the projects you could define a
> >> variable and run 'ant download-dependencies' and you'd have a
> >> ready to go MyFaces project in eclipse.
> >>
> >> Thoughts?
> >>
> >> TTFN,
> >>
> >> -bd-
> >>
> >>
> >>
> >
> >
> >
>
>
Re: Eclipse .project & .classpath files (is he talking about Maven again?!?!?!)
Posted by Bill Dudney <bd...@mac.com>.
Hi James,
Thanks for the feed-back. Good point about Eclipse touching the
files. Other option is putting the files into a subdirectory as we
used to have them. Also I could just post them on the wiki as you are
thinking of doing with the POM.
My issue with maven is upkeep. If we have the ant build that everyone
else is using and a POM for maven that only some are using there will
be stuff that goes stale.
Getting a maven generated .project & .classpath is a major win of
using maven agreed. I believe the maven/ant discussion has been
beaten to death on this list though and I for one don't want to open
that up again ;-)
TTFN,
-bd-
On Jun 24, 2005, at 11:41 AM, James Mitchell wrote:
> I know I don't have a vote here ;) but if I did, it would be -1
>
> Best case
> ---------
> By doing this, you are forcing every developer to deal with files
> that will always appear to have changes/differences. Yes, Eclipse
> will touch those files.
>
> In most projects that I've been involved in. You generally want to
> ignore those files because they assume a certain IDE is being used
> by all.
>
>
> Worst case
> ---------- What do you propose someone do if they need that spot
> (i.e. they are using a different IDE and different format, which
> requires a ".classpath" file in the place of the one under svn)?
>
>
> Let's meet in the middle
> ------------------------
> Not to beat the Maven drum any more than I have to....but that's
> actually one of the cool features of Maven. With a proper Maven
> project.xml file describing dependencies, creating the .project
> and .classpath files for *any* IDE is as simple as...
>
> http://maven.apache.org/reference/plugins/eclipse/
> http://maven.apache.org/reference/plugins/idea/
> http://maven.apache.org/reference/plugins/jbuilder/
>
>
> ...ah shucks, take your pick...
>
> http://maven.apache.org/reference/plugins/index.html
>
>
> FYI - I will be Mavenizing the MyFaces build within the next couple
> of weeks. Whether it is accepted into SVN is another issue for
> another thread. If not, I will make it available somewhere (wiki,
> docs, something).
>
>
> --
> James Mitchell
> Software Engineer / Open Source Evangelist
> Consulting / Mentoring / Freelance
> EdgeTech, Inc.
> http://www.edgetechservices.net/
> 678.910.8017
> AIM: jmitchtx
> Yahoo: jmitchtx
> MSN: jmitchell@apache.org
> Skype: jmitchtx
>
> ----- Original Message ----- From: "Bill Dudney" <bd...@mac.com>
> To: "MyFaces Development" <de...@myfaces.apache.org>
> Sent: Friday, June 24, 2005 1:05 PM
> Subject: Eclipse .project & .classpath files
>
>
>
>> Hi All,
>>
>> i'd like to supply an Eclipse configuration for the projects that
>> Sean is currently working to get set up in SVN. The projects
>> would work assuming the dependencies are downloaded via
>> 'download- dependencies'. That would get someone up and running
>> easily in Eclipse. I'd like to put these files under each of the
>> subprojects (i.e. api, impl, etc.) and under the projects
>> (current, tomahawk etc.)
>>
>> So, once you download one of the projects you could define a
>> variable and run 'ant download-dependencies' and you'd have a
>> ready to go MyFaces project in eclipse.
>>
>> Thoughts?
>>
>> TTFN,
>>
>> -bd-
>>
>>
>>
>
>
>
Antwort: Re: Eclipse .project & .classpath files (is he talking about Maven
again?!?!?!)
Posted by ch...@globus.ch.
Hi there,
I just want to give my response aswell. As a rarely jsf developer, I'm
always in the situation, that
I've got to setup my myfaces enviroment from new, because I'm not always
on track with the changes.
Even Eclipse and its different web/jsf plugins change so quickly...
It would save me alot of time if I could take the settings from one of the
developers.
It shouldn't be, that it is a must to use it. But for those who need a
jump start.... it would be very comfortable...
greets
Chris
"James Mitchell" <jm...@apache.org>
24.06.2005 19:41
Bitte antworten an "MyFaces Development"
An: "MyFaces Development" <de...@myfaces.apache.org>
Kopie:
Thema: Re: Eclipse .project & .classpath files (is he talking
about Maven again?!?!?!)
I know I don't have a vote here ;) but if I did, it would be -1
Best case
---------
By doing this, you are forcing every developer to deal with files that
will
always appear to have changes/differences. Yes, Eclipse will touch those
files.
In most projects that I've been involved in. You generally want to ignore
those files because they assume a certain IDE is being used by all.
Worst case
----------
What do you propose someone do if they need that spot (i.e. they are using
a
different IDE and different format, which requires a ".classpath" file in
the place of the one under svn)?
Let's meet in the middle
------------------------
Not to beat the Maven drum any more than I have to....but that's actually
one of the cool features of Maven. With a proper Maven project.xml file
describing dependencies, creating the .project and .classpath files for
*any* IDE is as simple as...
http://maven.apache.org/reference/plugins/eclipse/
http://maven.apache.org/reference/plugins/idea/
http://maven.apache.org/reference/plugins/jbuilder/
...ah shucks, take your pick...
http://maven.apache.org/reference/plugins/index.html
FYI - I will be Mavenizing the MyFaces build within the next couple of
weeks. Whether it is accepted into SVN is another issue for another
thread.
If not, I will make it available somewhere (wiki, docs, something).
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: jmitchell@apache.org
Skype: jmitchtx
----- Original Message -----
From: "Bill Dudney" <bd...@mac.com>
To: "MyFaces Development" <de...@myfaces.apache.org>
Sent: Friday, June 24, 2005 1:05 PM
Subject: Eclipse .project & .classpath files
> Hi All,
>
> i'd like to supply an Eclipse configuration for the projects that Sean
is
> currently working to get set up in SVN. The projects would work
assuming
> the dependencies are downloaded via 'download- dependencies'. That would
> get someone up and running easily in Eclipse. I'd like to put these
files
> under each of the subprojects (i.e. api, impl, etc.) and under the
> projects (current, tomahawk etc.)
>
> So, once you download one of the projects you could define a variable
and
> run 'ant download-dependencies' and you'd have a ready to go MyFaces
> project in eclipse.
>
> Thoughts?
>
> TTFN,
>
> -bd-
>
>
>