Consider changing the directory structure to comply with Maven 2 standard
-------------------------------------------------------------------------

         Key: GEOT-887
         URL: http://jira.codehaus.org/browse/GEOT-887
     Project: GeoTools
        Type: Wish

  Components: admin  
    Reporter: Martin Desruisseaux
 Assigned to: Martin Desruisseaux 
    Priority: Minor


This is issue is opened for discussion purpose. It may be closed as "Will not 
fix" if the inconvenients appear more important than the advantages.

Consider restructuring our directory layout in order to comply with Maven 2 
standard layout as described in the following page:

    
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html

For the Geotools code base, this mean that the following changes would need to 
be performed for each module:

  * Java source code currently in 'src' directory would need to move to 
'src/main/java' directory.
  * Test source code currently in 'test' directory would need to move to 
'src/test/java' directory.
  * Resources currently bundled in the 'src' directory (together with Java 
sources) would need to move to their own 'src/main/resources' directory.

Those changes would need to be done after all branches are merged to the trunk 
(coverage, FM...) and before any new branch is created (2.3.x...).

Advantages of doing such restructuration are:

  * Simplier 'pom.xml' file, since more default setting would apply.
  * Developpers new to Geotools would feel more confortable with Geotools 
directory structure if they were already familiar with other Maven 2 projects.
  * More room for future developments, for example adding C/C++ code for a GDAL 
or Proj.4 binding. The current Geotools directory layout left few room for 
non-Java source code, since there is only a 'src' directory with no 
sub-directory separating Java code from other languages.

Inconvenients of doing surch restructuration are:

  * Deeper directory structure, which is a little bit annoying for browsing and 
when working from the command line.
  * Every developpers would need to remount the Geotools project in their IDE.
  * Checking for differences between a branch with the old layout and the trunk 
with the new layout on a project-wide basis would be more difficult. It should 
not be more difficult if we only want to check for difference in a particular 
module however, except for the resources factored out of the Java source 
directory.


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



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to