You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall" <he...@ungoverned.org> on 2005/12/21 17:55:20 UTC
[VOTE] Repository structure
I think it is about time we made a final decision on our SVN repository
structure. According to my understanding of the situation, it seems like
we have gravitated toward a Maven-like subproject structure. Thus, I
propose we finalize the overall repository structure as follows (example
subproject shown):
felix/
trunk/
org.apache.felix.framework/
org.apache.felix.shell/
org.apache.felix.shell.tui/
org.apache.felix.prefs.jndi/
...
releases/
org.apache.felix.framework-0.8.0/
org.apache.felix.shell-1.0.0/
org.apache.felix.shell-1.0.1/
...
sandbox/
tbennett/
erodriquez/
akarasulu/
...
The trunk/ directory contains a subdirectory for each subproject with
the subproject's directory being named after the subproject's root
package. The releases/ directory contains release snapshots of the
subprojects. The sandbox/ directory contains directories for developer
experimentation.
Each individual subproject will have the following Maven 2 structure:
org.apache.felix.<subproject>/
src/
main/
java/
org/apache/felix/...
resources/
test/
java/
org/apache/felix/...
resources/
[ ] +1 Accept SVN repository structure.
[ ] 0 Does not matter to me.
[ ] -1 Reject SVN repository structure.
-> richard
Re: [VOTE] Repository structure
Posted by Enrique Rodriguez <en...@gmail.com>.
On 12/21/05, Richard S. Hall <he...@ungoverned.org> wrote:
> I think it is about time we made a final decision on our SVN repository
> structure ...
[ X ] +1 Accept SVN repository structure.
[ ] 0 Does not matter to me.
[ ] -1 Reject SVN repository structure.
Enrique
Re: [VOTE] Repository structure
Posted by Marcel Offermans <ma...@luminis.nl>.
+1
Richard S. Hall wrote:
> [ ] +1 Accept SVN repository structure.
> [ ] 0 Does not matter to me.
> [ ] -1 Reject SVN repository structure.
My main concern about the structure is that I'm not 100% convinced that
there should be a very strong relationship between a subproject and a
bundle. My most important argument is that the bundling of code is a
deployment issue that might be dependent on the situation. In one case
you would perhaps bundle all the code in one OSGi bundle, in another you
might split it into several bundles. I could even see completely
different deployments where you would not create OSGi bundles at all. In
a scenario where a project contains a "service" that can be deployed in
one of several service oriented frameworks for example.
Greetings, Marcel
Re: [VOTE] Repository structure
Posted by Clement Escoffier <cl...@gmail.com>.
+1
Rob Walker a écrit :
> +1 from me
>
> -- Rob
>
> Richard S. Hall wrote:
>
>> I think it is about time we made a final decision on our SVN
>> repository structure. According to my understanding of the situation,
>> it seems like we have gravitated toward a Maven-like subproject
>> structure. Thus, I propose we finalize the overall repository
>> structure as follows (example subproject shown):
>>
>> felix/
>> trunk/
>> org.apache.felix.framework/
>> org.apache.felix.shell/
>> org.apache.felix.shell.tui/
>> org.apache.felix.prefs.jndi/
>> ...
>> releases/
>> org.apache.felix.framework-0.8.0/
>> org.apache.felix.shell-1.0.0/
>> org.apache.felix.shell-1.0.1/
>> ...
>> sandbox/
>> tbennett/
>> erodriquez/
>> akarasulu/
>> ...
>>
>> The trunk/ directory contains a subdirectory for each subproject with
>> the subproject's directory being named after the subproject's root
>> package. The releases/ directory contains release snapshots of the
>> subprojects. The sandbox/ directory contains directories for
>> developer experimentation.
>>
>> Each individual subproject will have the following Maven 2 structure:
>>
>> org.apache.felix.<subproject>/
>> src/
>> main/
>> java/
>> org/apache/felix/...
>> resources/
>> test/
>> java/
>> org/apache/felix/...
>> resources/
>>
>> [ ] +1 Accept SVN repository structure.
>> [ ] 0 Does not matter to me.
>> [ ] -1 Reject SVN repository structure.
>>
>> -> richard
>>
>
Re: [VOTE] Repository structure
Posted by Rob Walker <ro...@ascert.com>.
+1 from me
-- Rob
Richard S. Hall wrote:
> I think it is about time we made a final decision on our SVN
> repository structure. According to my understanding of the situation,
> it seems like we have gravitated toward a Maven-like subproject
> structure. Thus, I propose we finalize the overall repository
> structure as follows (example subproject shown):
>
> felix/
> trunk/
> org.apache.felix.framework/
> org.apache.felix.shell/
> org.apache.felix.shell.tui/
> org.apache.felix.prefs.jndi/
> ...
> releases/
> org.apache.felix.framework-0.8.0/
> org.apache.felix.shell-1.0.0/
> org.apache.felix.shell-1.0.1/
> ...
> sandbox/
> tbennett/
> erodriquez/
> akarasulu/
> ...
>
> The trunk/ directory contains a subdirectory for each subproject with
> the subproject's directory being named after the subproject's root
> package. The releases/ directory contains release snapshots of the
> subprojects. The sandbox/ directory contains directories for developer
> experimentation.
>
> Each individual subproject will have the following Maven 2 structure:
>
> org.apache.felix.<subproject>/
> src/
> main/
> java/
> org/apache/felix/...
> resources/
> test/
> java/
> org/apache/felix/...
> resources/
>
> [ ] +1 Accept SVN repository structure.
> [ ] 0 Does not matter to me.
> [ ] -1 Reject SVN repository structure.
>
> -> richard
>
--
Ascert - Taking systems to the Edge
robw@ascert.com
+44 (0)20 7488 3470
www.ascert.com
Re: [VOTE] Repository structure
Posted by "Richard S. Hall" <he...@ungoverned.org>.
I think we can wrap up the vote on the repository structure...I realize
that I forgot to vote...I vote +1. :-)
So, it looks like the proposed [see below] repository structure is
accepted. The votes were as follows:
* Fourteen +1 votes (from myself, Timothy Bennett, Enrique
Rodriguez, Alex Karasulu, Francesco Furfari, Stefano Lenzi, Brett
Porter, Upayavira, BJ Hargrave, Trustin Lee, Marcel Offermans,
Alan Cabrera, Rob Walker, Clement Escoffier),
* No -1 votes, and
* No abstains.
I will try to update the Wiki with this information and I will make the
framework portion of the repository conform to this structure this week.
-> richard
Richard S. Hall wrote:
> I think it is about time we made a final decision on our SVN
> repository structure. According to my understanding of the situation,
> it seems like we have gravitated toward a Maven-like subproject
> structure. Thus, I propose we finalize the overall repository
> structure as follows (example subproject shown):
>
> felix/
> trunk/
> org.apache.felix.framework/
> org.apache.felix.shell/
> org.apache.felix.shell.tui/
> org.apache.felix.prefs.jndi/
> ...
> releases/
> org.apache.felix.framework-0.8.0/
> org.apache.felix.shell-1.0.0/
> org.apache.felix.shell-1.0.1/
> ...
> sandbox/
> tbennett/
> erodriquez/
> akarasulu/
> ...
>
> The trunk/ directory contains a subdirectory for each subproject with
> the subproject's directory being named after the subproject's root
> package. The releases/ directory contains release snapshots of the
> subprojects. The sandbox/ directory contains directories for developer
> experimentation.
>
> Each individual subproject will have the following Maven 2 structure:
>
> org.apache.felix.<subproject>/
> src/
> main/
> java/
> org/apache/felix/...
> resources/
> test/
> java/
> org/apache/felix/...
> resources/
>
> [ ] +1 Accept SVN repository structure.
> [ ] 0 Does not matter to me.
> [ ] -1 Reject SVN repository structure.
>
> -> richard
>
>
Re: [VOTE] Repository structure
Posted by Trustin Lee <tr...@gmail.com>.
+1 here, too.
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
PGP Key ID: 0x854B996C
Re: [VOTE] Repository structure
Posted by Alex Karasulu <ao...@bellsouth.net>.
+1 as well.
Alex
Upayavira wrote:
>+1
>
>Upayavira
>
>Richard S. Hall wrote:
>
>
>>I think it is about time we made a final decision on our SVN repository
>>structure. According to my understanding of the situation, it seems like
>>we have gravitated toward a Maven-like subproject structure. Thus, I
>>propose we finalize the overall repository structure as follows (example
>>subproject shown):
>>
>> felix/
>> trunk/
>> org.apache.felix.framework/
>> org.apache.felix.shell/
>> org.apache.felix.shell.tui/
>> org.apache.felix.prefs.jndi/
>> ...
>> releases/
>> org.apache.felix.framework-0.8.0/
>> org.apache.felix.shell-1.0.0/
>> org.apache.felix.shell-1.0.1/
>> ...
>> sandbox/
>> tbennett/
>> erodriquez/
>> akarasulu/
>> ...
>>
>>The trunk/ directory contains a subdirectory for each subproject with
>>the subproject's directory being named after the subproject's root
>>package. The releases/ directory contains release snapshots of the
>>subprojects. The sandbox/ directory contains directories for developer
>>experimentation.
>>
>>Each individual subproject will have the following Maven 2 structure:
>>
>> org.apache.felix.<subproject>/
>> src/
>> main/
>> java/
>> org/apache/felix/...
>> resources/
>> test/
>> java/
>> org/apache/felix/...
>> resources/
>>
>>[ ] +1 Accept SVN repository structure.
>>[ ] 0 Does not matter to me.
>>[ ] -1 Reject SVN repository structure.
>>
>>-> richard
>>
>>
>>
>>
>
>
>
>
Re: [VOTE] Repository structure
Posted by Upayavira <uv...@odoko.co.uk>.
+1
Upayavira
Richard S. Hall wrote:
> I think it is about time we made a final decision on our SVN repository
> structure. According to my understanding of the situation, it seems like
> we have gravitated toward a Maven-like subproject structure. Thus, I
> propose we finalize the overall repository structure as follows (example
> subproject shown):
>
> felix/
> trunk/
> org.apache.felix.framework/
> org.apache.felix.shell/
> org.apache.felix.shell.tui/
> org.apache.felix.prefs.jndi/
> ...
> releases/
> org.apache.felix.framework-0.8.0/
> org.apache.felix.shell-1.0.0/
> org.apache.felix.shell-1.0.1/
> ...
> sandbox/
> tbennett/
> erodriquez/
> akarasulu/
> ...
>
> The trunk/ directory contains a subdirectory for each subproject with
> the subproject's directory being named after the subproject's root
> package. The releases/ directory contains release snapshots of the
> subprojects. The sandbox/ directory contains directories for developer
> experimentation.
>
> Each individual subproject will have the following Maven 2 structure:
>
> org.apache.felix.<subproject>/
> src/
> main/
> java/
> org/apache/felix/...
> resources/
> test/
> java/
> org/apache/felix/...
> resources/
>
> [ ] +1 Accept SVN repository structure.
> [ ] 0 Does not matter to me.
> [ ] -1 Reject SVN repository structure.
>
> -> richard
>
>
Re: [VOTE] Repository structure
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
+1
Brett's comments reflect my sentiments as well.
Regards,
Alan
On 12/21/2005 2:29 PM, Brett Porter wrote:
>+1, with comments (things to watch out for, not necessarily issues):
>
>- the choice of "releases" over the conventional "tags" and "branches"
>may be confusing to some people
>
>- I'm not sure I'd allot people their own sandbox. If you must have a
>sandbox, it should still uphold collaborative development (J Aaron
>Farr had a great quote in his ApacheCon lightening talk about this, if
>only I could remember it)
>
>- the use of a fully qualified name could be problematic in terms of
>length on Windows (I don't know how long these get, but I have had
>problems with a 255 character limit from time to time)
>
>HTH,
>Brett
>
>On 12/22/05, Stefano Lenzi <ki...@interfree.it> wrote:
>
>
>>+1
>>
>>Stefano Lenzi
>>
>>[ X ] +1 Accept SVN repository structure.
>>[ ] 0 Does not matter to me.
>>[ ] -1 Reject SVN repository structure.
>>
>>Richard S. Hall wrote:
>>
>>
>>>I think it is about time we made a final decision on our SVN repository
>>>structure. According to my understanding of the situation, it seems like
>>>we have gravitated toward a Maven-like subproject structure. Thus, I
>>>propose we finalize the overall repository structure as follows (example
>>>subproject shown):
>>>
>>> felix/
>>> trunk/
>>> org.apache.felix.framework/
>>> org.apache.felix.shell/
>>> org.apache.felix.shell.tui/
>>> org.apache.felix.prefs.jndi/
>>> ...
>>> releases/
>>> org.apache.felix.framework-0.8.0/
>>> org.apache.felix.shell-1.0.0/
>>> org.apache.felix.shell-1.0.1/
>>> ...
>>> sandbox/
>>> tbennett/
>>> erodriquez/
>>> akarasulu/
>>> ...
>>>
>>>The trunk/ directory contains a subdirectory for each subproject with
>>>the subproject's directory being named after the subproject's root
>>>package. The releases/ directory contains release snapshots of the
>>>subprojects. The sandbox/ directory contains directories for developer
>>>experimentation.
>>>
>>>Each individual subproject will have the following Maven 2 structure:
>>>
>>> org.apache.felix.<subproject>/
>>> src/
>>> main/
>>> java/
>>> org/apache/felix/...
>>> resources/
>>> test/
>>> java/
>>> org/apache/felix/...
>>> resources/
>>>
>>>[ ] +1 Accept SVN repository structure.
>>>[ ] 0 Does not matter to me.
>>>[ ] -1 Reject SVN repository structure.
>>>
>>>-> richard
>>>
>>>
>>>
>>>
>>>
>>
>>
Re: [VOTE] Repository structure
Posted by Marcel Offermans <ma...@luminis.nl>.
Richard S. Hall wrote:
>> - the use of a fully qualified name could be problematic in terms of
>> length on Windows (I don't know how long these get, but I have had
>> problems with a 255 character limit from time to time)
>
> Who uses Windows? ;-)
Well... not me but... :)
> Yes, this could become an issue, we will have to keep an eye on it...
Windows does have issues with long paths and checking out into one's
home directory (under XP for example) does not help since just the home
directory is already quite a long path. So one could always check out
into some drive root (or short path) or simply check out one single
sub-project at at time (assuming the build system(s) we choose can
handle building only a single subproject).
Greetings, Marcel
Re: [VOTE] Repository structure
Posted by Trustin Lee <tr...@gmail.com>.
2005/12/23, Richard S. Hall <he...@ungoverned.org>:
>
> > - the use of a fully qualified name could be problematic in terms of
> > length on Windows (I don't know how long these get, but I have had
> > problems with a 255 character limit from time to time)
>
> Who uses Windows? ;-)
I use. ;)
Koreans cannot live without Windows, because we cannot buy anything without
ActiveX here. Sad, eh?
Cheers,
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
PGP Key ID: 0x854B996C
Re: [VOTE] Repository structure
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Brett Porter wrote:
> +1, with comments (things to watch out for, not necessarily issues):
>
> - the choice of "releases" over the conventional "tags" and "branches"
> may be confusing to some people
>
I got used to "tags", but at first it was a confusing name for me. In
this case, "releases" makes more sense since it will only contain
releases and the name makes this very clear. However, I wasn't the
original person that argued for this, so maybe there is a better
justification out there. :-)
> - I'm not sure I'd allot people their own sandbox. If you must have a
> sandbox, it should still uphold collaborative development (J Aaron
> Farr had a great quote in his ApacheCon lightening talk about this, if
> only I could remember it)
>
I don't really have an opinion...it seems that the precise nature of
sandboxes can probably be deferred until a need arises. For now, we just
need to agree on the major structural elements of the repo.
> - the use of a fully qualified name could be problematic in terms of
> length on Windows (I don't know how long these get, but I have had
> problems with a 255 character limit from time to time)
Who uses Windows? ;-)
Yes, this could become an issue, we will have to keep an eye on it...
-> richard
Re: [VOTE] Repository structure
Posted by Brett Porter <br...@gmail.com>.
+1, with comments (things to watch out for, not necessarily issues):
- the choice of "releases" over the conventional "tags" and "branches"
may be confusing to some people
- I'm not sure I'd allot people their own sandbox. If you must have a
sandbox, it should still uphold collaborative development (J Aaron
Farr had a great quote in his ApacheCon lightening talk about this, if
only I could remember it)
- the use of a fully qualified name could be problematic in terms of
length on Windows (I don't know how long these get, but I have had
problems with a 255 character limit from time to time)
HTH,
Brett
On 12/22/05, Stefano Lenzi <ki...@interfree.it> wrote:
> +1
>
> Stefano Lenzi
>
> [ X ] +1 Accept SVN repository structure.
> [ ] 0 Does not matter to me.
> [ ] -1 Reject SVN repository structure.
>
> Richard S. Hall wrote:
> > I think it is about time we made a final decision on our SVN repository
> > structure. According to my understanding of the situation, it seems like
> > we have gravitated toward a Maven-like subproject structure. Thus, I
> > propose we finalize the overall repository structure as follows (example
> > subproject shown):
> >
> > felix/
> > trunk/
> > org.apache.felix.framework/
> > org.apache.felix.shell/
> > org.apache.felix.shell.tui/
> > org.apache.felix.prefs.jndi/
> > ...
> > releases/
> > org.apache.felix.framework-0.8.0/
> > org.apache.felix.shell-1.0.0/
> > org.apache.felix.shell-1.0.1/
> > ...
> > sandbox/
> > tbennett/
> > erodriquez/
> > akarasulu/
> > ...
> >
> > The trunk/ directory contains a subdirectory for each subproject with
> > the subproject's directory being named after the subproject's root
> > package. The releases/ directory contains release snapshots of the
> > subprojects. The sandbox/ directory contains directories for developer
> > experimentation.
> >
> > Each individual subproject will have the following Maven 2 structure:
> >
> > org.apache.felix.<subproject>/
> > src/
> > main/
> > java/
> > org/apache/felix/...
> > resources/
> > test/
> > java/
> > org/apache/felix/...
> > resources/
> >
> > [ ] +1 Accept SVN repository structure.
> > [ ] 0 Does not matter to me.
> > [ ] -1 Reject SVN repository structure.
> >
> > -> richard
> >
> >
> >
>
>
Re: [VOTE] Repository structure
Posted by Stefano Lenzi <ki...@interfree.it>.
+1
Stefano Lenzi
[ X ] +1 Accept SVN repository structure.
[ ] 0 Does not matter to me.
[ ] -1 Reject SVN repository structure.
Richard S. Hall wrote:
> I think it is about time we made a final decision on our SVN repository
> structure. According to my understanding of the situation, it seems like
> we have gravitated toward a Maven-like subproject structure. Thus, I
> propose we finalize the overall repository structure as follows (example
> subproject shown):
>
> felix/
> trunk/
> org.apache.felix.framework/
> org.apache.felix.shell/
> org.apache.felix.shell.tui/
> org.apache.felix.prefs.jndi/
> ...
> releases/
> org.apache.felix.framework-0.8.0/
> org.apache.felix.shell-1.0.0/
> org.apache.felix.shell-1.0.1/
> ...
> sandbox/
> tbennett/
> erodriquez/
> akarasulu/
> ...
>
> The trunk/ directory contains a subdirectory for each subproject with
> the subproject's directory being named after the subproject's root
> package. The releases/ directory contains release snapshots of the
> subprojects. The sandbox/ directory contains directories for developer
> experimentation.
>
> Each individual subproject will have the following Maven 2 structure:
>
> org.apache.felix.<subproject>/
> src/
> main/
> java/
> org/apache/felix/...
> resources/
> test/
> java/
> org/apache/felix/...
> resources/
>
> [ ] +1 Accept SVN repository structure.
> [ ] 0 Does not matter to me.
> [ ] -1 Reject SVN repository structure.
>
> -> richard
>
>
>
Re: [VOTE] Repository structure
Posted by Francesco Furfari <fr...@isti.cnr.it>.
+1
best,
francesco
Richard S. Hall ha scritto:
> I think it is about time we made a final decision on our SVN
> repository structure. According to my understanding of the situation,
> it seems like we have gravitated toward a Maven-like subproject
> structure. Thus, I propose we finalize the overall repository
> structure as follows (example subproject shown):
>
> felix/
> trunk/
> org.apache.felix.framework/
> org.apache.felix.shell/
> org.apache.felix.shell.tui/
> org.apache.felix.prefs.jndi/
> ...
> releases/
> org.apache.felix.framework-0.8.0/
> org.apache.felix.shell-1.0.0/
> org.apache.felix.shell-1.0.1/
> ...
> sandbox/
> tbennett/
> erodriquez/
> akarasulu/
> ...
>
> The trunk/ directory contains a subdirectory for each subproject with
> the subproject's directory being named after the subproject's root
> package. The releases/ directory contains release snapshots of the
> subprojects. The sandbox/ directory contains directories for developer
> experimentation.
>
> Each individual subproject will have the following Maven 2 structure:
>
> org.apache.felix.<subproject>/
> src/
> main/
> java/
> org/apache/felix/...
> resources/
> test/
> java/
> org/apache/felix/...
> resources/
>
> [ ] +1 Accept SVN repository structure.
> [ ] 0 Does not matter to me.
> [ ] -1 Reject SVN repository structure.
>
> -> richard
>
>
Re: [VOTE] Repository structure
Posted by "Richard S. Hall" <he...@ungoverned.org>.
BJ Hargrave wrote:
> +1 if you change:
>
> "with the subproject's directory being named after the subproject's root
> package"
>
> to
>
> "with the subproject's directory being named after the subproject's
> *bundle symbolic name*"
>
> which I think was previously discussed. There is also no clear definition
> of what a "root" package is anyway :-)
I agree, this is what we intend, but not every subproject will be a
bundle, so we cannot define it to be the bundle symbolic name either. I
think we are all in agreement here, but this is probably a non-issue for
this vote, since we are not deciding on any subproject names at this point.
-> richard
Re: [VOTE] Repository structure
Posted by BJ Hargrave <ha...@us.ibm.com>.
+1 if you change:
"with the subproject's directory being named after the subproject's root
package"
to
"with the subproject's directory being named after the subproject's
*bundle symbolic name*"
which I think was previously discussed. There is also no clear definition
of what a "root" package is anyway :-)
BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance
hargrave@us.ibm.com
Office: +1 407 849 9117 Mobile: +1 386 848 3788
"Richard S. Hall" <he...@ungoverned.org>
2005-12-21 11:55 AM
Please respond to
felix-dev@incubator.apache.org
To
felix-dev@incubator.apache.org
cc
Subject
[VOTE] Repository structure
I think it is about time we made a final decision on our SVN repository
structure. According to my understanding of the situation, it seems like
we have gravitated toward a Maven-like subproject structure. Thus, I
propose we finalize the overall repository structure as follows (example
subproject shown):
felix/
trunk/
org.apache.felix.framework/
org.apache.felix.shell/
org.apache.felix.shell.tui/
org.apache.felix.prefs.jndi/
...
releases/
org.apache.felix.framework-0.8.0/
org.apache.felix.shell-1.0.0/
org.apache.felix.shell-1.0.1/
...
sandbox/
tbennett/
erodriquez/
akarasulu/
...
The trunk/ directory contains a subdirectory for each subproject with
the subproject's directory being named after the subproject's root
package. The releases/ directory contains release snapshots of the
subprojects. The sandbox/ directory contains directories for developer
experimentation.
Each individual subproject will have the following Maven 2 structure:
org.apache.felix.<subproject>/
src/
main/
java/
org/apache/felix/...
resources/
test/
java/
org/apache/felix/...
resources/
[ ] +1 Accept SVN repository structure.
[ ] 0 Does not matter to me.
[ ] -1 Reject SVN repository structure.
-> richard