[jbossseam-issues] [JBoss JIRA] Resolved: (JBSEAM-3529) use more representive names for hot and standard classpath entries
[
https://jira.jboss.org/jira/browse/JBSEAM-3529?page=com.atlassian.jira.pl...
]
Dan Allen resolved JBSEAM-3529.
-------------------------------
Fix Version/s: 2.0.3.CR2
Resolution: Done
Changed. Will likely (but not necessarily) need the same change in JBossTools. The seam
script still retains the concept of an "action" and "model" directory
since, in terms of code generation, that is the function of the src/hot and src/main
directories, respectively. It's just that now the developer can feel free to move
classes based on deployment type rather than function.
use more representive names for hot and standard classpath entries
------------------------------------------------------------------
Key: JBSEAM-3529
URL: https://jira.jboss.org/jira/browse/JBSEAM-3529
Project: Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.1.0.CR1
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 2.0.3.CR2
Original Estimate: 1 hour
Remaining Estimate: 1 hour
The classpath entry for hot deployable components is currently src/action and the path
for non-hot deployable components is src/model. That problem is that we are mixing the
function of the classes with the way they get deployed. The classpath entries should have
names which represent how they are handled.
The suggested mapping is as follows:
src/action -> src/hot
src/model -> src/main
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira