Re: [equinox-dev] Installing a bundle from console does not make it available to the workspace?
Alex, Yep I can't write a bundle that depends on it. So I'll try the refresh option. Have a great day all. 2008/5/7 Alex Blewitt [EMAIL PROTECTED]: By not available, do you mean that it does not work, or that you can't write a PDE bundle that depends on it? If the latter, it's because PDE caches the target environment, and you have to refresh it. You can do that from window preferences pde target. Then your bundle should he available. Alex Sent from my iPhone On 7 May 2008, at 00:20, Mark [EMAIL PROTECTED] wrote: Installing a bundle after launching Eclipse using the -console, or using the Neils most excellent bundlemonitor (http://neilbartlett.name/downloads/bundlemonitor/ http://neilbartlett.name/downloads/bundlemonitor/) fails to make that bundle available in the WorkSpace / or as an available plugin dependency. It does however show up it the bundle monitor. (Eclispe 3.3.1.1 on Windows XP) I would have expected the functionality to be similar to adding a JAR, in that once the bundle has been installed, it should be available throughout the Eclipse Environment. I did get it to work by installing the plugin (using the links extension mechanism) prior to launching eclipse. Then the bundle is available and can be used in the workspace. Unless anyone has any bright ideas ? I will submit more information in the morning, if required. Regards Mark ___ 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
Re: [equinox-dev] How can I get the exact time of each class that JVM spent on loading them?
HI Tom, Very helpful. The case we met is the same as the one that you post the link. After reordering the invocation in the start method, now I have solved my problem. On Tue, May 6, 2008 at 4:14 AM, Thomas Watson [EMAIL PROTECTED] wrote: Hi Equinox does not have anything built in that can give you the amount of time it takes to load a class. But there are a couple of things I suggest you look into. - Does your classes have static initializers that may do a lot of work. All static initializers of a class are run before any code is executed in a class. This would happen before you execute a constructor. - Do you have lazy activated bundles? These bundles would have the Bundle-ActivationPolicy or Eclipse-LazyStart header. If a lazy start bundle has a BundleActivator class that does a lot of work then it will cause an initial slowdown the first time a class is loaded from the bundle. - Do you have anything in your logs that indicate a timeout occurred while activating a bundle? There are cases where the VM locks the classloader natively before entering the OSGi class loaders. This can cause deadlock in lazy activation. In Equinox we will detect the deadlock and will break it after a 5 second timeout. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=209920 for an example. I only mention this because you say the creation of one object took 5 seconds which is the same amount of time use for the timeout before we break the deadlock. If this is occurring you should see an exception in your log similar to the in bug 209920. Tom [image: Inactive hide details for Yu Bady ---05/04/2008 10:00:31 AM---We have an Eclipse-based application running on MAC OS X. Durin]Yu Bady ---05/04/2008 10:00:31 AM---We have an Eclipse-based application running on MAC OS X. During the startup process, we found that the creation of one object From: Yu Bady [EMAIL PROTECTED] To: equinox-dev@eclipse.org Date: 05/04/2008 10:00 AM Subject: [equinox-dev] How can I get the exact time of each class that JVM spent on loading them? -- We have an Eclipse-based application running on MAC OS X. During the startup process, we found that the creation of one object took 5 seconds. After print the time-stamp at the entrance of the class's constructor, we knew that most of the time were spent before the invoke of the constructor. So we deduce that the loading/verifying/resolving of the class consumed most of the time. On the other hand, this class has complex dependency trees. It may not be practicable for us to look at each related classes one by one. So we hope to use some tools to find the exact time that are spent to load/verify/resolve related classes when we create the object. With -verbose:class, we can only know the order that each related classes are loaded. There is no any time-stamps associating with them. Any suggestions or comments will be highly appreciated. ___ 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 graycol.gifecblank.gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] Equinox projects tagged for next RC1 build.
The map file has been updated for the following Bug changes: + Bug 230421. [registry] Translation not found when nl pack installed through dropins (FIXED) The following projects have changed: org.eclipse.equinox.registry org.eclipse.osgi Tom ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] [prov] p2 build contribution
The map file has been updated for the following Bug changes: + Bug 215924. [prov] Metadata for fix pack aka patches (FIXED) + Bug 219488. [prov] Build repos should not get added to the manager (FIXED) + Bug 226052. [ui] - first filter text keystroke in available IU list can hang UI if no repos have been loaded (FIXED) + Bug 228005. [updateSite] Possible NPE (FIXED) + Bug 228779. Don't download using ECF when update site is already local (FIXED) + Bug 228903. Repository manager creation should always add the repository (FIXED) + Bug 229096. OutOfMemoryError lost when verifying content (FIXED) + Bug 229641. Added Extension location repos in UI contain no features (FIXED) + Bug 229870. Translation Clarification - org.eclipse.equinox.p2.engine (FIXED) + Bug 229877. [ui] Unable to start after upgrade (FIXED) + Bug 230386. [ui] Processing of repository addition events blocking uninstall (FIXED) + Bug 230934. Bootstrap product needs eclipse as launcher; typo in config.ini (FIXED) + Bug 230982. Scary message in when reporting errors (FIXED) + Bug 231004. Wrong exception code when update site file is not found (FIXED) The following projects have changed: org.eclipse.equinox.p2.reconciler.dropins org.eclipse.equinox.p2.ui org.eclipse.equinox.p2.artifact.repository org.eclipse.equinox.p2.tests org.eclipse.equinox.p2.metadata.generator org.eclipse.equinox.p2.updatesite org.eclipse.equinox.p2.engine org.eclipse.equinox.p2.director___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] update site tests pass AND linux + .keyring file question
Hi all, As promised during the p2 dev call, we've run our update site tests and are happy to announce that everything passed! During the p2 dev call there was talk of linux + .keyring failures and a recent solution. Can anybody jump in an fill in the details for us? Thanks, jkca ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev