directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Karasulu <akaras...@apache.org>
Subject Re: All projects folder in svn
Date Wed, 19 Jan 2011 15:06:24 GMT
Yes I agree - this just to pull all down at once and import into the
IDE. Releases are done at each project level. Usually we just cd into
the project like shared and release each one separately.

Regards,
Alex

On Wednesday, January 19, 2011, Jesse McConnell
<jesse.mcconnell@gmail.com> wrote:
> I would recommend that anything you are using the maven release plugin
> with not use svn:externals because it makes it painful/breaks the
> normal apache maven release process.
>
> that is just internal to the tree that is using the release process
> though, if you want to bring in that top level via svn:externals
> someplace else that would be fine
>
> imo avoiding svn:externals altogether is best practice though unless
> its strictly to slurp stuff together to make it easier to load into an
> IDE and you never actually _use_ it for anything.
>
> cheers,
> jesse
>
> --
> jesse mcconnell
> jesse.mcconnell@gmail.com
>
>
>
> On Wed, Jan 19, 2011 at 08:21, Alex Karasulu <akarasulu@apache.org> wrote:
>> I guess we're going with a area where all dependencies are linked via
>> svn:externals at the top level instead of reproducing this structure
>> in each project: I.e. In studio area and apacheds areas. Here's what I
>> am thinking:
>>
>> https://svn.apache.org/repos/asf/directory/trunks
>>
>> Notice the ending 's' in trunks. This svn folder I propose we link to
>> all the trunks of directory projects. The link is short, easy to
>> remember and makes sense. We check this out to pull down all project
>> trunks together to build all and load all into the IDE in one shot.
>>
>> https://svn.apache.org/repos/asf/directory/branches
>>
>> Here we keep other branch specific svn:externals folders that
>> reference project branches in their respective areas under svn. We can
>> use a convention like <branch-name>-with-dependencies for such link
>> folders on branches. This may however be redundant, so maybe we can
>> just use the <branch-name> by itself. It's already understood to be a
>> "link folder" because of it's location. WDYT?
>>
>> We should also require a branch log file in this branches folder to
>> chronicle what we've creates and deleted over time an why. Subversion
>> log will show this too so this may also be redundant but it's nice to
>> just see this info via http without having to run svn log or sift
>> through changes. WDYT?
>>
>> Regards,
>> Alex
>>
>> --
>> Alex Karasulu
>> My Blog :: http://www.jroller.com/akarasulu/
>> Apache Directory Server :: http://directory.apache.org
>> Apache MINA :: http://mina.apache.org
>> To set up a meeting with me: http://tungle.me/AlexKarasulu
>>
>

-- 
Alex Karasulu
My Blog :: http://www.jroller.com/akarasulu/
Apache Directory Server :: http://directory.apache.org
Apache MINA :: http://mina.apache.org
To set up a meeting with me: http://tungle.me/AlexKarasulu

Mime
View raw message