[
http://jira.jboss.com/jira/browse/JBSEAM-2051?page=comments#action_12380795 ]
Max Andersen commented on JBSEAM-2051:
--------------------------------------
It solves some of it as i can see.
To run testng tests in JBossTools we have a structure for War's that looks like the
above (except we put META-INF into the src/model too)
That makes the classpath be as "correct" as possible and we can pick up the
WEB-INF/components.xml.
We do that also to avoid having to depend on a ant tasks doing duplicate work that the IDE
has already done.
please put WEB-INF under view instead of resources (seam-gen)
-------------------------------------------------------------
Key: JBSEAM-2051
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2051
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.CR1
Reporter: Dan Allen
Assigned To: Max Andersen
Fix For: 2.0.x
Original Estimate: 1 day
Remaining Estimate: 1 day
I am aware that there is no hotter issue than this one. But PAUSE before rejecting it and
hear me out.
The current seam-gen project structure is
src
action
model
resources
WEB-INF
META-INF
view
IDEs choke on this structure, but it really comes down to just one folder. The src/ and
resources/ directory really aren't a problem. The real problem is that WEB-INF/ just
needs to be under view/. Seriously, if that can happen, the IDEs really will be happier.
People are not arguing for the sake of arguing. This convention is the way that Sun laid
out more than a decade ago and vendors have catered to it ever since (even JBoss).
It's not like we woke up one day and said, gee, let's put WEB-INF/ in the folder
with web artifacts. Rather than try to change the whole world, can we just move this one
folder? I promise I am not arguing to read my own writing.
Proposed structure
src
action
model
resources
META-INF
view
WEB-INF
--
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