Adrian Custer a écrit :
> The Maven site says:
> There are just two subdirectories of this structure: src and
> target. The only other directories that would be expected here
> are metadata like CVS or .svn, and any subprojects in a
> multiproject build (each of which would be laid out as above).
I believe that this paragraph applies to JAR packaging only (or "leaf"
modules).
I believe that it doesn't apply to POM packaging (i.e. parent modules), which
usually don't have a "src" directory.
> Are we going to have nothing but 'subprojects' and conserve our
> demo
> ext
> module
> plugin
> unsupported
> structure?
Yes, it was my intention. Maybe some modules will move and some other modules
may be splitted in many, but the directory structure change rather apply at the
'src' level.
> If so, I'd like you to consider making the subproject directories more
> explicitly
> (1) code holding folders,
> (2) equivalent but with different purpose.
> I'm thinking of pluralized, whole words like
> demonstrations
> extensions
> plugins
> modules
> unsupported (!)
I'm fine with that. Does anyone agree with explicit names?
> or even
> modules_demonstration
> modules_extension
> modules_core
> modules_plugin
> modules_unsupported
Well, in such case we could even choose to create a "modules" directory and put
"demonstrations", "extensions", etc. submodules in it. I'm fine with that too.
What other peoples think?
Martin
-------------------------------------------------------------------------
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
