Hi Oleg, In my previous note I only listed the projects from the current Bundles category that are getting split into new categories. The org.eclipse.equinox.startup and org.eclipse.equinox.servlet.api projects are obsolete and will not be moved. The rest belong to the Framework category.
You make a good point about the launcher but I think it has a close
relationship with the framework and I am not in favor of splitting it out
at this point. But I can be convinced otherwise if others think it should
be split out. That would make the Framework and tests a lonely couple of
project though.
Tom
From: Oleg Besedin <[EMAIL PROTECTED]>
To: Equinox development mailing list <equinox-dev@eclipse.org>
Date: 07/22/2008 03:02 PM
Subject: Re: [equinox-dev] Code move timeline
Looks very good, totally agree on "Bundles" being better as separate
categories.
It seems that several Equinox bundles are not in the list:
org.eclipse.equinox.executable
org.eclipse.equinox.launcher
org.eclipse.equinox.servlet.api
org.eclipse.equinox.startup.
org.eclipse.equinox.supplement
org.eclipse.osgi
org.eclipse.osgi.tests
(a couple of those bundles probably aren't relevant anymore).
In terms of placing bundles into categories, the "
org.eclipse.equinox.preferences" seems to be out of place in the "
osgi-compendum". Maybe, place it in the "components"?
One other point, depending on overhead involved, it might be worth having
launcher as a separate category. Today "framework" = "OSGi" + "launcher",
and those two items are different in just about every dimension. Then in
CVS structure below instead of "org.eclipse.equinox/framework" there would
be "org.eclipse.equinox/launcher" and all OSGi-related items would go into
"org.eclipse.equinox/osgi-compendium".
Thanks,
Oleg
Thomas Watson
<[EMAIL PROTECTED]>
Sent by: To
[EMAIL PROTECTED] Equinox development mailing
list
<equinox-dev@eclipse.org>
07/17/2008 02:04 PM cc
Subject
Please respond to Re: [equinox-dev] Code move
Equinox development mailing list timeline
<equinox-dev@eclipse.org>
We discussed this at the Tuesday Equinox call. It looks like a large part
of the team will be on vacation at the end of July. The proposal is to move
the equinox projects to RT during the week of July 28th.
We also discussed what to do with the equinox incubator. At this time we
are going to wait for the new Eclipse Development Process to be approved
(hopefully in August). The new process should allow us to create incubator
projects under any project in Eclipse. This will allow us to create an
incubator project for equinox directly under the equinox project in RT.
Jeff and I have been discussing the layout of the different components of
Equinox. Today we have Bundles, Framework, p2, Security. The Bundles
category has become kind of a dumping ground for many unrelated bundles. We
would like to split these bundles out into three categories:
osgi-compendium - All bundles that implement one of the osgi compendium
specifications. This includes the following projects:
org.eclipse.equinox.app
org.eclipse.equinox.cm
org.eclipse.equinox.device
org.eclipse.equinox.ds
org.eclipse.equinox.event
org.eclipse.equinox.http
org.eclipse.equinox.http.jetty (jetty5 and jetty6 impls)
org.eclipse.equinox.io
org.eclipse.equinox.ip
org.eclipse.equinox.log
org.eclipse.equinox.metatype
org.eclipse.equinox.preferences
org.eclipse.equinox.useradmin
org.eclipse.equinox.util
org.eclipse.equinox.wireadmin
org.eclipse.osgi.services
org.eclipse.osgi.util
components - The bundles that provide infrastructure to developing
components in Equinox. This includes the following projects:
org.eclipse.equinox.common
org.eclipse.equinox.registry
org.eclipse.equinox.transforms.hook
org.eclipse.equinox.transforms.xslt
server-side - The server side bundles.
org.eclipse.equinox.http.registry
org.eclipse.equinox.http.servlet
org.eclipse.equinox.http.servletbridge
org.eclipse.equinox.jsp.jasper
org.eclipse.equinox.jsp.jasper.registry
org.eclipse.equinox.servletbridge
This would result in the following CVS structure in RT
org.eclipse.equinox/components
org.eclipse.equinox/framework
org.eclipse.equinox/osgi-compendium
org.eclipse.equinox/p2
org.eclipse.equinox/security
org.eclipse.equinox/server-side
All commiters with rights to the projects contained in Bundles will
continue to have access to all the projects which got moved to the three
new categories. We are not trying to create more fine grained commit
rights. Instead we are just trying to create a layout that makes sense in
CVS and Bugzilla. Thoughts?
Tom
Inactive hide details for Pascal Rapicault ---07/15/2008 10:18:13 AM---Hi,
I would like to know what is the time line for movinPascal Rapicault
---07/15/2008 10:18:13 AM---Hi, I would like to know what is the time line
for moving the equinox code into
From: Pascal Rapicault <[EMAIL PROTECTED]>
To: Equinox development mailing list <equinox-dev@eclipse.org>
Date: 07/15/2008 10:18 AM
Subject: [equinox-dev] Code move timeline
Hi,
I would like to know what is the time line for moving the equinox code into
the runtime repository?
PaScaL_______________________________________________
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
<<inline: graycol.gif>>
<<inline: ecblank.gif>>
_______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
