incubator-graffito-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Mark Donaghy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GRFT-91) Remove Eclipse .project and .classpath files from svn
Date Thu, 20 Jul 2006 23:06:14 GMT
    [ http://issues.apache.org/jira/browse/GRFT-91?page=comments#action_12422515 ] 
            
Philip Mark Donaghy commented on GRFT-91:
-----------------------------------------

I actually like having this feature. I would vote for removing each subproject .project and
.classpath and using a global .project and .classpath for the entire project.

For the source code and debugging a SOURCE_HOME which points to a directory where one checks
out all dependency projects with the subversion project, cvs project or tag name. Source paths
are then resolved in .classpath with $SOURCE_HOME/portals-jetspeed-2 where $SOURCE_HOME contains
folders with the same heirarchy as the repository http://svn.apache.org/repos/asf/.

> Remove Eclipse .project and .classpath files from svn
> -----------------------------------------------------
>
>                 Key: GRFT-91
>                 URL: http://issues.apache.org/jira/browse/GRFT-91
>             Project: Graffito
>          Issue Type: Improvement
>          Components: Project Build
>         Environment: Eclipse
>            Reporter: Jukka Zitting
>            Priority: Minor
>
> Some of the Graffito subprojects in svn contain Eclipse .project and .classpath files
presumably to simplify opening of the projects in Eclipse. While this is a nice feature, it
is also quite troublesome because it a) duplicates information from project.xml, and b) interferes
with svn operations when the user wants to modify the project settings in Eclipse.
> For example after checking out the entire Graffito trunk I imported all the subprojects
to Eclipse and replaced library dependencies to other Graffito subproject jars with project
dependencies to the actual subprojects. This makes it very easy to navigate Graffito sources,
but of course marks all .classpath files managed in svn as modified.
> It would be good to remove the .project and .classpath files from svn, especially since
they can be easily generated using "maven eclipse" from the Maven Eclipse plugin.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message