Yes,
as long as 1_1_0 is ok to change (by convention tags are not
modified, only branches).
All I'm looking for is a place to change the release only enough to
get the faces-config.xml file in place (as well as the other missing
bits because that file is not found) and then get a new release
pushed out.
Martin M is planning on doing another release from the trunk after I
finish my commit. That is fine but risky.
TTFN,
-bd-
On Sep 23, 2005, at 5:53 AM, Sean Schofield wrote:
-1
Note that after I tagged the 1.1 release I created a external in the
"release" dir so if you use
http://svn.apache.org/repos/asf/myfaces/release/1_1_0/ you will get
"current" but for the release. It doesn't include sandbox so its not
quite the same but sandbox is not part of the official release.
Doesn't this give you what you need?
sean
On 9/23/05, Martin Marinschek <[EMAIL PROTECTED]> wrote:
I agree with Martin on this - if you need everything, you can always
checkout MyFaces, right?
regards,
Martin
On 9/23/05, Martin Cooper <[EMAIL PROTECTED]> wrote:
On Thu, 22 Sep 2005, Bill Dudney wrote:
Well the idea is that people would then be using current/trunk
to checkout
instead of just current.
But by definition, what's in branches and tags is not current, so
why does
it make sense to include them under 'current'? The structure you
described
is exactly what you have without using the 'current' external in
the first
place, isn't it?
--
Martin Cooper
TTFN,
-bd-
On Sep 22, 2005, at 12:31 PM, Martin Cooper wrote:
On Thu, 22 Sep 2005, Bill Dudney wrote:
Hi All,
I'd like to propose that we change current to be;
current
/branches
/tags
/trunk
Still all externals but tracking the group of tags & branches
that are
common across all the subprojects.
current/trunk -> becomes what we currently call current
current/branches -> currently empty
current/tags -> 1_1_0 with externals to each subproject's
1_1_0 tag
I would recommend against doing that. It would mean that
everyone checking
out 'current' would end up with multiple copies of the entire
source tree,
which is unlikely to be something that they would want.
Most people are unlikely to want more than one version of the
source at any
given time, so I don't see a need to clump together multiple
versions in a
single checkout.
--
Martin Cooper
To fix the faces-config.xml bug that's been identified in the
1_1_0
release we can create a branch in current/branches/1_1_0 that
uses
externals to the tags for everything but 'build' which would
point to the
1_1_0 branch in build (not yet created but I'd be glad to do
that).
Thoughts?
TTFN,
-bd-
--
http://www.irian.at
Your JSF powerhouse -
JSF Trainings in English and German
