RE: [equinox-dev] Could not install bundle ... Bundle ... hasalready been installed from ... errors in log
Thanks, that did the trick. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ext Pascal Rapicault Sent: Wednesday, July 16, 2008 7:25 PM To: Equinox development mailing list Cc: equinox-dev@eclipse.org; [EMAIL PROTECTED] Subject: Re: [equinox-dev] Could not install bundle ... Bundle ... hasalready been installed from ... errors in log This happens when the reconciliation behavior of update.configurator is not turned off or if you ship update.configurator. Two ways around this: 1) do not ship update.configurator 2) add to the following propery to the config.ini org.eclipse.update.reconcile=false HTH, PaScaL ---07/16/2008 06:51:40 PM---We're creating our product using the headless product build. When I launch it I see an error like t From: [EMAIL PROTECTED] To: equinox-dev@eclipse.org Date: 07/16/2008 06:51 PM Subject: [equinox-dev] Could not install bundle ... Bundle ... has already been installed from ... errors in log We're creating our product using the headless product build. When I launch it I see an error like this in the error log for each plugin: !ENTRY org.eclipse.update.configurator 4 0 2008-07-16 17:20:33.320 !MESSAGE Could not install bundle plugins/org.eclipse.compare_3.4.0.I20080604.jar Bundle org.eclipse.compare version 3.4.0.I20080604 has already been installed from: reference: file:plugins\org.eclipse.compare_3.4.0.I20080604.jar file://plugins/org.eclipse.compare_3.4.0.I20080604.jar It appears to be coming from the org.eclipse.equinox.simpleconfigurator/bundles.info file. I've had a look at the ConfigurationActivator.installBundles method but it's not clear exactly what's going on. Ideas? Thanks, Warren ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev graycol.gifecblank.gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Code move timeline
I like this and agree that bundles had unfortunately become a dumping ground. The separation you guys have done looks good to me. One nit... I think we probably want org.eclipse.equinox.http.servlet in the osgi-compendium as it's what really provides the Http Service implementation and also is a dependency of org.eclipse.equinox.http.jetty. -Simon | | From: | | --| |Thomas Watson [EMAIL PROTECTED] | --| | | To:| | --| |Equinox development mailing list equinox-dev@eclipse.org | --| | | Date: | | --| |07/17/2008 02:05 PM | --| | | Subject: | | --| |Re: [equinox-dev] Code move timeline | --| 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
Re: [equinox-dev] Code move timeline
Thanks Simon. Yes org.eclipse.equinox.http.servlet belongs in osgi-compendium. Tom From: Simon Kaegi [EMAIL PROTECTED] To: Equinox development mailing list equinox-dev@eclipse.org Date: 07/17/2008 03:14 PM Subject:Re: [equinox-dev] Code move timeline I like this and agree that bundles had unfortunately become a dumping ground. The separation you guys have done looks good to me. One nit... I think we probably want org.eclipse.equinox.http.servlet in the osgi-compendium as it's what really provides the Http Service implementation and also is a dependency of org.eclipse.equinox.http.jetty. -Simon Inactive hide details for Thomas Watson ---07/17/2008 02:05:59 PM---We discussed this at the Tuesday Equinox call. It looks likThomas Watson ---07/17/2008 02:05:59 PM---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. T. From:Thomas Watson [EMAIL PROTECTED] To: Equinox development mailing list equinox-dev@eclipse.org Date:07/17/2008 02:05 PM Subject: Re: [equinox-dev] Code move timeline 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
Re: [equinox-dev] Code move timeline
So I assume that the cvs history will be retained when the bundles are moved to the RT project's repository? The 3.4.x map files will need to be updated with the new location too so we don't have build breakage Kim Thomas Watson [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 07/17/2008 02:04 PM Please respond to Equinox development mailing list equinox-dev@eclipse.org To Equinox development mailing list equinox-dev@eclipse.org cc Subject Re: [equinox-dev] Code move timeline 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 Pascal 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 image/gifimage/gifimage/gifimage/gifimage/gifimage/gifimage/gifimage/gifimage/gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
