Re: [equinox-dev] How to set activate on startup to 'true' in bundles.info file

2011-08-16 Thread Yousouf, Shenol
Hi Pradeep,

Whether a bundle will be marked for start or not in the bundles.info is 
determined by the metadata, published for this bundle in the p2 repository, 
from where it is installed. The description of the bundle's IU in the repo can 
include a touchpoint action (see the documentation about 
org.eclipse.equinox.p2.touchpoint.eclipse.markStarted on [1]) that explicitly 
instructs the p2 framework to mark the bundle to be started.

There are a few ways to add such actions for your components but the most 
straightforward one is through the configuration section in your .product 
file. There is a Configuration tab in the Product Editor in Eclipse IDE for 
this purpose, and since I was not able to find any specification about the 
contents of the .product file, I give a very basic example for reference:

?xml version=1.0 encoding=UTF-8?
?pde version=3.5?

product name=Simple Product uid=SimpleProduct version=1.0.0 
useFeatures=false includeLaunchers=true

   configIni use=default
   /configIni

   plugins
  plugin id=Bundle/
   /plugins

   configurations
  plugin id=Bundle autoStart=true startLevel=0 /
   /configurations

/product


Regarding your second question - if it is possible for all the bundles in a 
product to be started, there is a trick in p2 which can make this happen, 
although, as Neil pointed out, it is not recommended and not needed in most 
cases. Product publishing generates a special configuration unit 
('tooling.osgi.bundle.default') in the repository which instruments the default 
behavior of all bundles in the product ([2]). You can override this unit by 
means of a special p2.inf file ([3]) that customizes the product and replaces 
the osgi.bundle.default with another version which is capable of forcing the 
start of all bundles (unless the bundle comes with its own touchpoint action or 
CU that prevents the start).

[1] 
http://help.eclipse.org/helios/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/p2_actions_touchpoints.html
 
[2] http://wiki.eclipse.org/Equinox/p2/Setting_Start_Levels 
[3] 
http://help.eclipse.org/helios/topic/org.eclipse.platform.doc.isv/guide/p2_customizing_metadata.html
 


HTH
Shenol Yousouf
SAP Labs Bulgaria


-Original Message-
From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] 
On Behalf Of Pradeep Fernando
Sent: 16 август 2011 г. 09:23 ч.
To: Equinox development mailing list
Subject: Re: [equinox-dev] How to set activate on startup to 'true' in 
bundles.info file

Hi Neil/devs,

On Tue, Aug 16, 2011 at 8:56 AM, Neil Bartlett njbartl...@gmail.com wrote:
 I don't actually know the answer to your question, but I'm hoping the
 answer is no, that's not possible.

Yes I got your point. I too think you are correct here.
But I'm not clear the what makes it 'true' or 'true' in the bundles.info file.

like, all bundles that has an activator will be activated by startup.

may be this is a trivial question, but I couldnt find a document
explaining that.


thanks,
--Pradeep


 Your bundle probably does not need to be activated when Eclipse is
 started. If you and all other plug-in authors were able to do this,
 then Eclipse would take hours to start.

 Please consider other ways to achieve what you want to do.

 Rgds,
 Neil

 On Tue, Aug 16, 2011 at 4:11 AM, Pradeep Fernando pradee...@gmail.com wrote:
 Hi devs,

 I have a p2-aware product that uses simpleconfigurator. In the
 bundles.info file the activate on startup field is set to 'false' for
 most of the bundles.
 How simpleconfigurator decides weather to put to 'false' or 'true' in
 bundles.info. Is it possible to make the default value to 'true'.
 (activate bundle at startup)


 Thanks,
 --Pradeep Fernando
 ___
 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




-- 
Pradeep Fernando.
http://pradeepfernando.blogspot.com/
___
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


Re: [equinox-dev] Eclipse 3.7M2a problem Do I need to do configuration to get dropins folder to work?

2010-11-03 Thread Yousouf, Shenol
Hi,

As far as I know, bundles are not installed automatically from the dropins 
folder. The folder is scanned on start of bundle 
org.eclipse.equinox.p2.reconciler.dropins, which usually happens with the start 
of Eclipse. So either you can restart the IDE for changes to take effect or 
open the OSGi  console and restart the bundle manually.

Best regards,
Shenol Yousouf
SAP Labs Bulgaria

From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] 
On Behalf Of Richard Catlin
Sent: Wednesday, November 03, 2010 12:28 AM
To: equinox-dev@eclipse.org
Subject: Re: [equinox-dev] Eclipse 3.7M2a problem Do I need to do configuration 
to get dropins folder to work?

I am using Eclipse eclipse-SDK-3.7M2a-macosx-cocoa-x86_64 for the Mac.

When Eclipse is running, I put a plugin in the dropins folder.  The running 
OSGI system does not scan that directory, which I thought it was supposed to by 
default.

Do I need to do some configuration?

Richard
___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev


Re: [equinox-dev] List of installable units or log - using p2 director to automate Subclipse, M2eclipse, and M2eclipse Extra for OpenMRS developers

2010-09-15 Thread Yousouf, Shenol
Hello Misha,

Concerning your first question, I assume that you have your IU already 
published in a repository but are now wondering how to install it because of 
references to some known external repositories.

One direction to follow is to build a composite repository which refers to all 
the repositories that you need and install from there.
http://wiki.eclipse.org/Equinox/p2/Composite_Repositories_%28new%29

Passing your IU and the composite repository URL to p2director will cause the 
metadata from the child repositories to get merged and your external 
dependencies will be successfully resolved.

The format of composite repository is quite simple and there are also ant tasks 
to automate its creation:
http://wiki.eclipse.org/Equinox/p2/Ant_Tasks#Composite_Repository_Task

Hope this helps !

Best regards,
Shenol Yousouf
SAP Labs Bulgaria

-Original Message-
From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] 
On Behalf Of misha680
Sent: Wednesday, September 15, 2010 6:28 PM
To: equinox-dev@eclipse.org
Subject: Re: [equinox-dev] List of installable units or log - using p2 director 
to automate Subclipse, M2eclipse, and M2eclipse Extra for OpenMRS developers


Two quick question, if you can help much apperciated.

1. I would like to set up an IU that depends on IU's at _other_
repositories. Thus, user adds _our_ repository, clicks on _our_ IU, and all
the IUs from other repositories that _need_ to be installed are installed.

I read all P2 wikis but could not find anything I could understand to be
relevant.
This seemed to be helpful:
http://wiki.eclipse.org/Equinox/p2/Repository_Association
but I did not really understand how to implement the scenario above in
practice. If there are any guides or working examples in the wild much
appreciated.

Currently, my solution is to make a GUI plug-in as below, which works, but I
feel like there must be a simpler solution:

http://old.nabble.com/file/p29718999/devstudio-simple.zip
devstudio-simple.zip 
http://old.nabble.com/file/p29718999/InstallAction.java InstallAction.java 

2. Thank you so much for your helpful hint about the installed IU
information location.

I have taken this information and made the following command;

./eclipse -nosplash -application org.eclipse.equinox.p2.director -repository
http://subclipse.tigris.org/update_1.6.x,http://m2eclipse.sonatype.org/sites/m2e/,http://m2eclipse.sonatype.org/sites/m2e-extras/
-installIU
org.maven.ide.eclipse,org.maven.ide.eclipse.scm,org.maven.ide.eclipse.subclipse,org.tigris.subversion.clientadapter,org.tigris.subversion.clientadapter.javahl,org.tigris.subversion.subclipse.feature.group
-profile epp.package.jee

This _does_ install those IUs, but _even if I add the eclipse 3.6 and helios
update_ repositories on the command line, I notice that this _does not_
upgrade org.eclipse IUs that a GUI install _does_.

In other words, this command, even with eclipse 3.6 and helios update
repositories added, does _not_ reproduce the GUI action of installing these
same IUs in terms of _upgrading org.eclipse dependencies_

Is there a command line switch I am missing to do this?

Thank you very much

Yours
Misha Koshelev


Pascal Rapicault-3 wrote:
 
 A complete list of all the IUs that have been installed is available in
 the most recent profile file located in
 install/p2/org.eclipse.equinox.p2.engine/profileRegistry/someName/
 
 In order to facilitate things for you users, you may want to create one IU
 that refers to all the elements you need.
 This way your end user only has one thing to install
 
 On 2010-09-12, at 5:47 PM, misha680 wrote:
 
 
 Dear All:
 
 I am trying to automate the install process for OpenMRS developers 
 http://wiki.openmrs.org/display/docs/Step+by+Step+Installation+for+Developers
 
 I have found a helpful reference here:
 http://help.eclipse.org/helios/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/p2_director.html
 
 And have created a command line:
 ./eclipse -nosplash -application org.eclipse.equinox.p2.director
 -repository
 http://subclipse.tigris.org/update_1.6.x,http://m2eclipse.sonatype.org/sites/m2e/,http://m2eclipse.sonatype.org/sites/m2e-extras/
 -installIU
 org.maven.ide.eclipse,org.maven.ide.eclipse.scm,org.maven.ide.eclipse.subclipse,org.tigris.subversion.clientadapter,org.tigris.subversion.clientadapter.javahl,org.tigris.subversion.subclipse.core
 
 That _seems_ to mirror my Eclipse install.
 
 However, on further investigation, it seems that certain things are not
 installed. Notably, all _features_ related to the application seem
 completely missing under the features/ folder.
 
 Is there a good way to _see a list of all installable units_ in Eclipse?
 
 The logs seem to record _features_, there is a bundles.list file that
 record
 _bundles = plugins_,
 but where can I see a log of installable units in Eclipse?
 
 Thank you
 Misha
 -- 
 View this message in context: