[EMAIL PROTECTED] wrote on 3/13/06 4:53 PM:
Thanks, Zak. I follow you, but I'm still confused about one thing. How
are you creating the source directory, the one being accessed by APP in
your release.sh script?
I haven't made the leap to Svn so I have no idea how this would work (or
not) in that world. Here is what I do:
cd /path/to/some-committed-build-directory
cvs tag 1-0-4 .
cd /path/to/some-release-directory
cvs export -r 1-0-4 some_app -d some_app-1-0-4
cd some_app-1-0-4
ant build
/usr/local/bin/release.sh some_app.woa 1-0-4
In the CVS world, one could tag and then export, like you said, and you
might tag only a subset of the files that have actually been committed
since the last release.
When I tag for a release, I tag the whole tree, not just the files that
have changed since the last release. Given the tagging process you've
described, I'm not sure my process works with your release style.
Is it possible to follow
the process you're describing and yet not include the changes made to a
particular framework?
You can tag individual files, or use rtag to tag the repository as of
some date besides the present.
It appears that in Subversion that's not possible unless the code for a
project is broken up into multiple repositories, one for each logical
unit. Maybe that's the right thing to do?
That's how I've done it. Each library and app is a separate module.
Best,
zak.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
