You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by ChadDavis <ch...@gmail.com> on 2009/11/25 18:44:08 UTC
branch or tag
If I want to checkout a certain version of a release, say 1.6, to
peruse and build in my local workspace. Should I checkout from
branch/1.6 or tag/1.6? I assume it's tag, but I'm not accustomed to
an organized build process ;)
Isn't the branch/1.6 an moving target? I.e. this is where bug fixes
and other maintenance development get's done.
And isn't the tag/1.6 a frozen code snapshot?
Re: branch or tag
Posted by Alexander Klimetschek <ak...@day.com>.
On Wed, Nov 25, 2009 at 18:58, ChadDavis <ch...@gmail.com> wrote:
> But that explains why the 1.6 branch, that I check out, has SNAPSHOT
> artifact names in the pom?
SNAPSHOT as version suffix (it's not part of the artifactId) is a
maven feature for things under development. For example, an upcoming
1.7.3 release would be developed under 1.7.3-SNAPSHOT. For snapshot
versions, maven will simply use the newest one built (or downloaded).
If you just want to download an existing release from sources, you
should checkout the tags/1.6 folder.
Regards,
Alex
--
Alexander Klimetschek
alexander.klimetschek@day.com
Re: branch or tag
Posted by ChadDavis <ch...@gmail.com>.
But that explains why the 1.6 branch, that I check out, has SNAPSHOT
artifact names in the pom?
On Wed, Nov 25, 2009 at 11:19 AM, Alexander Klimetschek
<ak...@day.com> wrote:
> On Thu, Nov 26, 2009 at 01:44, ChadDavis <ch...@gmail.com> wrote:
>> If I want to checkout a certain version of a release, say 1.6, to
>> peruse and build in my local workspace. Should I checkout from
>> branch/1.6 or tag/1.6? I assume it's tag, but I'm not accustomed to
>> an organized build process ;)
>>
>> Isn't the branch/1.6 an moving target? I.e. this is where bug fixes
>> and other maintenance development get's done.
>>
>> And isn't the tag/1.6 a frozen code snapshot?
>
> Releases are tagged under jackrabbit/tags/<version-number> and must
> not change (although svn wouldn't prevent modification of that
> "folder").
>
> Branches are there for additional patch releases (eg. 1.6.x) and thus
> are a moving target, eg. the 1.5 branch at
> http://svn.apache.org/repos/asf/jackrabbit/branches/1.5/ had quite a
> lot of releases, up to 1.5.7 by now. See
> http://svn.apache.org/repos/asf/jackrabbit/tags/
>
> 1.6 didn't yet have a patch release.
>
> Regards,
> Alex
>
> --
> Alexander Klimetschek
> alexander.klimetschek@day.com
>
Re: branch or tag
Posted by Alexander Klimetschek <ak...@day.com>.
On Thu, Nov 26, 2009 at 01:44, ChadDavis <ch...@gmail.com> wrote:
> If I want to checkout a certain version of a release, say 1.6, to
> peruse and build in my local workspace. Should I checkout from
> branch/1.6 or tag/1.6? I assume it's tag, but I'm not accustomed to
> an organized build process ;)
>
> Isn't the branch/1.6 an moving target? I.e. this is where bug fixes
> and other maintenance development get's done.
>
> And isn't the tag/1.6 a frozen code snapshot?
Releases are tagged under jackrabbit/tags/<version-number> and must
not change (although svn wouldn't prevent modification of that
"folder").
Branches are there for additional patch releases (eg. 1.6.x) and thus
are a moving target, eg. the 1.5 branch at
http://svn.apache.org/repos/asf/jackrabbit/branches/1.5/ had quite a
lot of releases, up to 1.5.7 by now. See
http://svn.apache.org/repos/asf/jackrabbit/tags/
1.6 didn't yet have a patch release.
Regards,
Alex
--
Alexander Klimetschek
alexander.klimetschek@day.com