You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Stephane Bailliez (JIRA)" <di...@incubator.apache.org> on 2005/02/07 22:27:12 UTC
[jira] Created: (DIR-102) Add svn:externals to directory
Add svn:externals to directory
------------------------------
Key: DIR-102
URL: http://issues.apache.org/jira/browse/DIR-102
Project: Directory
Type: Improvement
Components: General
Reporter: Stephane Bailliez
Assigned to: Alex Karasulu
Priority: Minor
It is a bit weird to checkout 'directory' due to the multiplicity of subprojects which each has its own lifecycle (ie branches and tags).
Maybe it would be helpful to use the extremely poorly documented svn:externals option so that the trunk checks out the trunks of each subproject and not the whole trunk + branches + tags
Another option would probably be to move all submodules in the trunk if they don't such have a different lifecycle. TBC.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (DIR-102) Add svn:externals to directory
Posted by "Brett Porter (JIRA)" <di...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/DIR-102?page=comments#action_58691 ]
Brett Porter commented on DIR-102:
----------------------------------
the reason for the current layout is that each subproject has a different lifecycle.
> Add svn:externals to directory
> ------------------------------
>
> Key: DIR-102
> URL: http://issues.apache.org/jira/browse/DIR-102
> Project: Directory
> Type: Improvement
> Components: General
> Reporter: Stephane Bailliez
> Assignee: Alex Karasulu
> Priority: Minor
>
> It is a bit weird to checkout 'directory' due to the multiplicity of subprojects which each has its own lifecycle (ie branches and tags).
> Maybe it would be helpful to use the extremely poorly documented svn:externals option so that the trunk checks out the trunks of each subproject and not the whole trunk + branches + tags
> Another option would probably be to move all submodules in the trunk if they don't such have a different lifecycle. TBC.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (DIR-102) Add svn:externals to directory
Posted by "Stephane Bailliez (JIRA)" <di...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/DIR-102?page=comments#action_58700 ]
Stephane Bailliez commented on DIR-102:
---------------------------------------
Fair enough, but it looks like you might be going a bit far into decoupling things and thus creating more complexity than necessary in the structure.
It's nearly like instead of having java 'packages' you have been creating sub-modules with a different lifecycle.
I'm not sure there will be such a different lifecycle between sub-modules, especially as there are no resources to do backward compatibility testing and mixing. (there is no QA so it's always HEAD)
Therefore you will nearly always tag each trunk at the same time...which is exactly the same has having all under the same trunk, except that it is much more manageable..you might even get most of them into the main source tree :)
> Add svn:externals to directory
> ------------------------------
>
> Key: DIR-102
> URL: http://issues.apache.org/jira/browse/DIR-102
> Project: Directory
> Type: Improvement
> Components: General
> Reporter: Stephane Bailliez
> Assignee: Alex Karasulu
> Priority: Minor
>
> It is a bit weird to checkout 'directory' due to the multiplicity of subprojects which each has its own lifecycle (ie branches and tags).
> Maybe it would be helpful to use the extremely poorly documented svn:externals option so that the trunk checks out the trunks of each subproject and not the whole trunk + branches + tags
> Another option would probably be to move all submodules in the trunk if they don't such have a different lifecycle. TBC.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira