You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Niclas Hedhman <ni...@hedhman.org> on 2004/05/20 10:08:54 UTC
Avalon is now under SVN...
Avaloners around the Planet !
The Avalon codebase has now been migrated to Subversion, and the CVS has been
locked for any further commits. Reading from CVS will be possible for the
fore-seeable future.
Please get your own copy of Subversion. Aaron has posted links earlier.
There is an on-going discussion of the exact new project layout, which will
encompass the Avalon Vision of the Future. Until that layout is bolted down,
you will find new directories under the "avalon/" project directory, AND ALL
EXISTING Avalon codebase under avalon/legacy.
So the official directory layout for Avalon is;
/avalon
/branches
/releases
/trunk
/central
/discovery
/legacy
/avalon
/activation
/buildsystem
/composition
/framework
/logging
/maven-plugins
/merlin
/meta
/repository
/tutorials
/util
/versioning
/avalon-components
/avalon-excalibur
/avalon-logkit
/avalon-phoenix
/avalon-sandbox
/avalon-site
/planet
/runtime
/studio
/tools
More information of the "new directories" will follow over time.
********* IMPORTANT *****************
Recommended for checkout;
svn co https://svn.apache.org/repos/asf/avalon/trunk/avalon
*************************************
which will checkout everything in the 'trunk', i.e. where the latest
development will occur.
With Subversion it is possible to check out any part of the tree (ASF has a
single SVN tree for all projects). So if you are only interested in getting
the legacy Avalon parts (to save on some downloads), you can do
svn co https://svn.apache.org/repos/asf/avalon/trunk/avalon/legacy/avalon
avalon
If you do, then expect material to 'disappear' as we move stuff into the new
layout later.
We all hope that this transition will be smooth and beneficial to all parties,
but recognizes that there will be individual 'obstacles' along the way. If
anyone has anything to report, please do so on the dev@avalon.apache.org
mailing list, and we will all try to help each other out.
Cheers
Niclas
P.S. The local diskspace requirement under Subversion is significantly higher
than under CVS, it seems that each directory (.svn directory) requires a
~40kb - 100kB additional space on my system, which adds up to quite a lot.
--
+------//-------------------+
/ http://www.bali.ac /
/ http://niclas.hedhman.org /
+------//-------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Avalon is now under SVN...
Posted by Stephen McConnell <mc...@apache.org>.
Niclas Hedhman wrote:
> ********* IMPORTANT *****************
> Recommended for checkout;
> svn co https://svn.apache.org/repos/asf/avalon/trunk/avalon
> *************************************
I think this should be:
https://svn.apache.org/repos/asf/avalon/trunk
Steve.
--
|---------------------------------------|
| Magic by Merlin |
| Production by Avalon |
| |
| http://avalon.apache.org |
|---------------------------------------|
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: Avalon is now under SVN...
Posted by "Noel J. Bergman" <no...@devtech.com>.
> the 'ttb' notion is a construct by individuals, not native to
> subversion itself
Correct. You have lots of freedom to layout the repository anyway you want.
See: http://svnbook.red-bean.com/svnbook/ch04s07.html#svn-ch-4-sect-7.1. I
just think you're going to run into difficulties, but as the book says: "you
can reorganize your repository at any time."
In terms of best practice, I don't believe that the proposed layout is good,
but I'll let others, like Fitz or Greg who have far more experience, comment
as they see fit.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Avalon is now under SVN...
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Thursday 20 May 2004 23:54, Noel J. Bergman wrote:
> > So the official directory layout for Avalon is:
> You realize that this is bad, right?
> Does this make sense to you now?
I understand what you are saying, but I think I disagree to a large degree.
AFAIUI, the 'ttb' notion is a construct by individuals, not native to
subversion itself, but that is irrelevant to the discussion now.
I want a unified tree, without any 'ttb's all over the place, and without
splitting into separate checkouts. The unified tree is IMNSHO very
important!!
It has also been said that tags and branches are virtually free of charge, and
I am leveraging on this fact. Which would mean, I copy the whole tree - so
what - sue me - it is free of charge.
Furthermore,
I can do;
svn cp trunk/avalon/runtime/framework branches/niclas/af5
if I like to, and then merge back where it was spawned from.
Once my branches are old, and perhaps crashed experiments, I delete them out
of view...
As for Releases; Assuming we keep the current model (which is a completely
different debate in itself, more about that in the coming weeks), I don't see
that you need to put the version number at the immediate level below
"releases", but could put artifact first, such as avalon/framework/4.3/ or in
a few other ways...
I did spend some thought on this :o) and weighed one thing against another.
Cheers
Niclas
--
+------//-------------------+
/ http://www.bali.ac /
/ http://niclas.hedhman.org /
+------//-------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: Avalon is now under SVN...
Posted by "Noel J. Bergman" <no...@devtech.com>.
> So the official directory layout for Avalon is:
You realize that this is bad, right?
> /avalon
> /branches
> /releases
> /trunk
That means that the thing being versioned is /avalon, at the root. That is
not what you want. You want to organize by versionable/releaseable
component, and then have trunk/, tags/ and branches/ below each. These
"ttb" directories are the convention by which you manage versioning:
trunk/ - a directory containing the main development tree
tags/ - a directory containing DIRECTORIES, each of which
is a copy of the development tree.
branches/ - a directory containing DIRECTORIES, each of which
is a copy of the development tree.
Notice that tags and branches are given the same description. Yes, I did
that on purpose. Here is the difference: if you change something after you
make it a copy, it is a branch. If you don't, it is a tag. These things
are nothing more than naming conventions using lightweight copies. Even the
names "trunk", "tags" and "branches" are just conventions. But they are
good conventions.
If we are developing the foo widget in trunk, and I want to create a branch
for some exploration, I would COPY foo/trunk to foo/branches/myplaypen, do
some work there, and eventually merge my changes back into foo/trunk. If I
want to checkout Phoenix version XYZ, I'd checkout /avalon/phoenix/tags/XYZ.
Does this make sense to you now?
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org