You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by Andrus Adamchik <an...@objectstyle.org> on 2007/01/19 10:52:52 UTC
New SVN is ready
We have a new TLP repo created for us:
https://svn.apache.org/repos/asf/cayenne/
Since repo migration will require everybody to re-import stuff in
Eclipse, I figured it is a good time to move a few other things
around. So here is the plan. If we can reach lazy consensus, I can
move the code on a designated date.
1. Migration date:
I suggest Sunday, January 21.
2. Trunk reorg:
With the new assembly strategy we have things all over the place.
There are "public" and "private" Maven modules ("private" are those
under cayenne/core that are repackaged into aggregated modules under
cayenne/framework). Then there are also platform-specific modeler
modules. You can check the existing structure in SVN. Here is what I
suggest to do to make it cleaner:
assembly/
build-tools/
maven-cayenne-build-plugin
cayenne-regression-profiler
framework/ /* All "library" modules */
cayenne-jdk1.4-private
cayenne-jdk1.5-private
cayenne-jpa-private
cayenne-legal-private
cayenne-agent
cayenne-client
cayenne-server
maven-plugin
cayenne-modeler
itests/ /* Integration Tests */
itest-common
jpa-chapter2
jpa-chapter3
jpa-chapter9
pojo
docs/
doc
quick-start-tutorial
quick-start-rop-tutorial
modeler/ /* Modeler Platform extensions and assemblies */
cayenne-modeler-java
cayenne-modeler-mac
cayenne-modeler-mac-ext
cayenne-modeler-win
Comments?
Andrus
Re: New SVN is ready
Posted by Michael Gentry <bl...@gmail.com>.
"project" or "subproject" or "module" or "component" or ... whatever. :-)
/dev/mrg
On 1/19/07, Andrus Adamchik <an...@objectstyle.org> wrote:
> Sounds ok. If there are no other suggestions till Sunday, I'll use
> "unpublished".
>
> Andrus
>
>
> On Jan 19, 2007, at 7:41 PM, Mike Kienenberger wrote:
>
> > How about unpublished instead of private?
> >
> >
> > On 1/19/07, Andrus Adamchik <an...@objectstyle.org> wrote:
> >>
> >> On Jan 19, 2007, at 7:16 PM, Michael Gentry wrote:
> >>
> >> > Seems fairly logical, but Subversion allows us to move things
> >> around
> >> > if it needs to be changed again.
> >>
> >> True, just trying not to do it too often to avoid upsetting local
> >> Eclipse workspaces.
> >>
> >>
> >> > I am a little confused by the "private" in the names, though.
> >> Maybe I
> >> > just don't understand what you were trying to do, but the term
> >> seems
> >> > to imply non-open source to me, which of course is not correct.
> >>
> >> Interesting, of course nothing like that was implied. "private" here
> >> means that the module at deployment time will be a part of another
> >> aggregated module. Such module should not be published as a
> >> standalone module in a public repository and should not be imported
> >> by Cayenne users directly. Just like a "private" variable in Java.
> >> Again, "private" == "do not publish in the repo".
> >>
> >> But then, I am not sure what Maven recommended practices are in this
> >> respect. This is totally my invention coming of a need to provide
> >> user-friendly modules (cayenne-client, cayenne-server) - the idea
> >> that breaks neat and clean Maven picture of the world :-)
> >>
> >> Andrus
> >>
> >>
> >
>
>
Re: New SVN is ready
Posted by Andrus Adamchik <an...@objectstyle.org>.
Sounds ok. If there are no other suggestions till Sunday, I'll use
"unpublished".
Andrus
On Jan 19, 2007, at 7:41 PM, Mike Kienenberger wrote:
> How about unpublished instead of private?
>
>
> On 1/19/07, Andrus Adamchik <an...@objectstyle.org> wrote:
>>
>> On Jan 19, 2007, at 7:16 PM, Michael Gentry wrote:
>>
>> > Seems fairly logical, but Subversion allows us to move things
>> around
>> > if it needs to be changed again.
>>
>> True, just trying not to do it too often to avoid upsetting local
>> Eclipse workspaces.
>>
>>
>> > I am a little confused by the "private" in the names, though.
>> Maybe I
>> > just don't understand what you were trying to do, but the term
>> seems
>> > to imply non-open source to me, which of course is not correct.
>>
>> Interesting, of course nothing like that was implied. "private" here
>> means that the module at deployment time will be a part of another
>> aggregated module. Such module should not be published as a
>> standalone module in a public repository and should not be imported
>> by Cayenne users directly. Just like a "private" variable in Java.
>> Again, "private" == "do not publish in the repo".
>>
>> But then, I am not sure what Maven recommended practices are in this
>> respect. This is totally my invention coming of a need to provide
>> user-friendly modules (cayenne-client, cayenne-server) - the idea
>> that breaks neat and clean Maven picture of the world :-)
>>
>> Andrus
>>
>>
>
Re: New SVN is ready
Posted by Mike Kienenberger <mk...@gmail.com>.
How about unpublished instead of private?
On 1/19/07, Andrus Adamchik <an...@objectstyle.org> wrote:
>
> On Jan 19, 2007, at 7:16 PM, Michael Gentry wrote:
>
> > Seems fairly logical, but Subversion allows us to move things around
> > if it needs to be changed again.
>
> True, just trying not to do it too often to avoid upsetting local
> Eclipse workspaces.
>
>
> > I am a little confused by the "private" in the names, though. Maybe I
> > just don't understand what you were trying to do, but the term seems
> > to imply non-open source to me, which of course is not correct.
>
> Interesting, of course nothing like that was implied. "private" here
> means that the module at deployment time will be a part of another
> aggregated module. Such module should not be published as a
> standalone module in a public repository and should not be imported
> by Cayenne users directly. Just like a "private" variable in Java.
> Again, "private" == "do not publish in the repo".
>
> But then, I am not sure what Maven recommended practices are in this
> respect. This is totally my invention coming of a need to provide
> user-friendly modules (cayenne-client, cayenne-server) - the idea
> that breaks neat and clean Maven picture of the world :-)
>
> Andrus
>
>
Re: New SVN is ready
Posted by Andrus Adamchik <an...@objectstyle.org>.
On Jan 19, 2007, at 7:16 PM, Michael Gentry wrote:
> Seems fairly logical, but Subversion allows us to move things around
> if it needs to be changed again.
True, just trying not to do it too often to avoid upsetting local
Eclipse workspaces.
> I am a little confused by the "private" in the names, though. Maybe I
> just don't understand what you were trying to do, but the term seems
> to imply non-open source to me, which of course is not correct.
Interesting, of course nothing like that was implied. "private" here
means that the module at deployment time will be a part of another
aggregated module. Such module should not be published as a
standalone module in a public repository and should not be imported
by Cayenne users directly. Just like a "private" variable in Java.
Again, "private" == "do not publish in the repo".
But then, I am not sure what Maven recommended practices are in this
respect. This is totally my invention coming of a need to provide
user-friendly modules (cayenne-client, cayenne-server) - the idea
that breaks neat and clean Maven picture of the world :-)
Andrus
Re: New SVN is ready
Posted by Michael Gentry <bl...@gmail.com>.
Seems fairly logical, but Subversion allows us to move things around
if it needs to be changed again.
I am a little confused by the "private" in the names, though. Maybe I
just don't understand what you were trying to do, but the term seems
to imply non-open source to me, which of course is not correct.
Thanks,
/dev/mrg
On 1/19/07, Andrus Adamchik <an...@objectstyle.org> wrote:
> We have a new TLP repo created for us:
>
> https://svn.apache.org/repos/asf/cayenne/
>
> Since repo migration will require everybody to re-import stuff in
> Eclipse, I figured it is a good time to move a few other things
> around. So here is the plan. If we can reach lazy consensus, I can
> move the code on a designated date.
>
> 1. Migration date:
> I suggest Sunday, January 21.
>
> 2. Trunk reorg:
> With the new assembly strategy we have things all over the place.
> There are "public" and "private" Maven modules ("private" are those
> under cayenne/core that are repackaged into aggregated modules under
> cayenne/framework). Then there are also platform-specific modeler
> modules. You can check the existing structure in SVN. Here is what I
> suggest to do to make it cleaner:
>
> assembly/
>
> build-tools/
> maven-cayenne-build-plugin
> cayenne-regression-profiler
>
> framework/ /* All "library" modules */
> cayenne-jdk1.4-private
> cayenne-jdk1.5-private
> cayenne-jpa-private
> cayenne-legal-private
> cayenne-agent
> cayenne-client
> cayenne-server
> maven-plugin
> cayenne-modeler
>
> itests/ /* Integration Tests */
> itest-common
> jpa-chapter2
> jpa-chapter3
> jpa-chapter9
> pojo
>
> docs/
> doc
> quick-start-tutorial
> quick-start-rop-tutorial
>
> modeler/ /* Modeler Platform extensions and assemblies */
> cayenne-modeler-java
> cayenne-modeler-mac
> cayenne-modeler-mac-ext
> cayenne-modeler-win
>
>
> Comments?
>
> Andrus
>