[
http://jira.jboss.com/jira/browse/JBSEAM-2050?page=comments#action_12380887 ]
Dan Allen commented on JBSEAM-2050:
-----------------------------------
Ah, I remember why the "java" folder is important. It is not that we will be
implementing other languages, but it distinguishes it from non-java artifacts. For
instance, we could move the *.xsd files into a directory called "schema" or the
like. Also, resources could be put in a "resources" folder. I'm sure it is
one of those "purity" things that the Maven guys get blamed for. Whatever makes
us be able to sleep at night, that's what I'm all about.
reorganize modules
------------------
Key: JBSEAM-2050
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2050
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.CR1
Reporter: Dan Allen
Fix For: 2.0.x
Original Estimate: 1 day
Remaining Estimate: 1 day
I would like to make "modules" a first order directory (renamed from
"src") and also organize tests so they are per-module. This will encourage
per-module tests and also prevent circular dependencies (because the folders are treated
as modules and not one big lump of source code). The ui module also once again finds
itself adjacent to the other modules.
jboss-seam/
examples/ <-- showing this just as a reference point
modules/
core/
main/java
test/java
ui/
main/java
test/java
(continue for debug, ioc, gen, pdf, mail, remoting)
Although Eclipse doesn't know the first think about multi-modules, this will be idea
for setting up a module-aware IDE like IntelliJ IDEA (and to some degree, NetBeans).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira