[
https://jira.jboss.org/jira/browse/JBSEAM-3657?page=com.atlassian.jira.pl...
]
Valerie Griffin commented on JBSEAM-3657:
-----------------------------------------
Actually we DO put the deployable code into cvs. That way, it can be tagged with a release
that matches the source and can be retrieved for installation to our production systems.
(There may be be better, more modern ways to handle the process, but this is how my group
has done things for years.) The dist and exploded-archives directories are given CVS
directories automatically by myEclipse when the project is placed into cvs.
I've modified my build.xml file to use filesets and exclude in the clean process for
all directories.
Clean/deploy kills CVS
----------------------
Key: JBSEAM-3657
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3657
Project: Seam
Issue Type: Bug
Components: Tools
Affects Versions: 2.1.0.GA
Reporter: Valerie Griffin
We use cvs for version tracking and for releasing software to our users. We tell them
where to find the released code in our cvs area, and they get it. Unfortunately, the
deployment process in seam-gen deletes the entire directory, including the CVS directories
used to track version info, making it significantly more difficult to pur the released
software into our archive.
--
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