[
http://jira.jboss.com/jira/browse/JBSEAM-2338?page=comments#action_12390335 ]
Dan Allen commented on JBSEAM-2338:
-----------------------------------
I see what you are saying. Part of the issue is that the generated project does not store
the settings that were used by seam-gen in the project itself. I mean, the information is
there, it's just scattered throughout the configuration files (as it was applied).
To me, this is one of those cases where it is easy to add the flexibility to what exists,
but long term perhaps there is a bigger design change to be addressed. I don't like to
put small changes behind big ones, so my feeling is let's give the option to get out
of this hole first, then we can decide how to get the settings out of the seam
distribution directory.
As I make this argument, my thought is shifting...it really does make sense to get the
build.properties file out of the seam-gen directory. What sucks through is that you are
going to have to enter the whole path to the existing project. Ah, but we could store
"recently opened" projects and have a menu system to select them by number. All
I have to say to that is *$@# Ant. That would be a PITA to implement.
allow seam-gen to manage multiple projects
------------------------------------------
Key: JBSEAM-2338
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2338
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.GA
Reporter: Dan Allen
Assigned To: Dan Allen
Fix For: 2.0.1.GA
Attachments: JBSEAM-2338-v1.txt
Original Estimate: 10 minutes
Remaining Estimate: 10 minutes
Currently seam-gen only has the ability to manage one project at a time. This limitation
is due to the fact that it sources build.properties from the seam-gen directory to read
settings about the managed project. I propose that we make the name of the settings file
dynamic so that it is possible for seam-gen to select it based on the name of a property
supplied to the command line.
Example:
./seam -Dbuild=projecta explode
./seam explode
The first command would source build-projecta.properties. The second command would fall
back to the existing behavior and source build.properties.
--
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