Hi all,
Not sure if this is the right list to ask this question, so if not,
please let me know where I should be asking.
The launcher.openFile feature allows you to open a file in an eclipse
instance from the command line. I'm wondering if this feature is
extensible. For example, something
I would like to get a handle on a source bundle, but they do not seem to be
installed in the running Eclipse. For example, I would like to be able to
do this:
Bundle jdtUiSource = Platform.getBundle(org.eclipse.jdt.ui.source);
However, this always returns null.
Indeed, when I look use the OSGi
.
** **
HTH
** **
Pascal
** **
*From:* equinox-dev-boun...@eclipse.org [mailto:
equinox-dev-boun...@eclipse.org] *On Behalf Of *Andrew Eisenberg
*Sent:* April-23-13 2:36 PM
*To:* Equinox development mailing list
*Subject:* [equinox-dev] Getting an instance of a source bundle
, 2013 at 12:07 PM, Andrew Eisenberg and...@eisenberg.aswrote:
Thanks Peter and Tom. You're right that I was confusing my terminology.
I'll try using a resolverHook. Perhaps using resolverHooks will be more
stable than enabling and disabling bundles through PDE's BundleInfo class
Hi all,
I have multiple versions of a bundle installed in my Eclipse installation.
After the workbench starts up, I need to make a decision as to which
version of the bundle should be started based on a system property that the
user passes in from the command line. Currently, I am doing this
On Thu, Apr 11, 2013 at 6:18 PM, Andrew Eisenberg and...@eisenberg.aswrote:
Hi all,
I have multiple versions of a bundle installed in my Eclipse
installation. After the workbench starts up, I need to make a decision as
to which version of the bundle should be started based on a system
versions before
transiently starting the selected version.
Neil
On Thu, Apr 11, 2013 at 6:42 PM, Andrew Eisenberg and...@eisenberg.aswrote:
Thanks, Neil. I'll have to try this to make sure, but starting the
bundle that I want doesn't prevent the bundle I don't want from starting.
Eg- if I
, Andrew Eisenberg and...@eisenberg.aswrote:
OK. Just tried something like this. The problem is that by the time the
downstream bundle gets into its start method, and tries to stop all of the
unwanted versions of the non-singleton bundle, a bunch of wiring has
already been done
be done quite easily with the OSGi api and saves some memory as
well.
Unfortunately, in Eclipse you will then be confronted with the little
problem of starting your management bundle ...
Kind regards,
Peter Kriens
Sent from my iPad
On 11 apr. 2013, at 20:54, Andrew Eisenberg
Hi Tom,
Thanks for taking a look at this. AJDT is one of the main consumers
of org.eclipse.equinox.weaving.hook through the
org.eclipse.equinox.weaving.aspectj bundle. It looks like you have
also updated the org.eclipse.equinox.weaving.aspectj bundle. I will
get a chance to try this out next
Hi all,
I have a framework adapter that I am creating. Other bundles in the
eclipse feature need to reference classes from the framework adapter.
In a runtime workbench, this is working fine. Similarly, I don't have
any problems at runtime. The bundles that require classes from the
framework
As the project lead of AJDT, I can say that Equinox Weaving is crucial
for what we need to do. That being said, in the past two years, we
have had very few problems with it and it has been serving our
purposes nicely as it is. So, I personally don't have a need for a
redesign. But reworking the
In the second version, both o.e.e.weaving.hook and
o.e.e.weaving.aspectj are started and activated (I can see that in the
logs). So, that means that the weaver is enabled in the second
version. This means that it is unable to find the bundle containing
the aspects. Or, more precisely, it is not
That's a question we've been struggling with for AJDT as we
incorporate EA into our project.
Bug 254606 https://bugs.eclipse.org/bugs/show_bug.cgi?id=254606
Discusses some part of this. Not unit testing per se, but how we can
ensure that advice matches where you want it to.
To quote from the
I have an update site for equinox aspects here:
http://download.eclipse.org/tools/ajdt/34/dev/equinox-aspects
You can try to install from there. The installation will
automatically update your config.ini for you. Should work, but you
need to have AspectJ pre-installed.
If Martin's suggestions
Please see bug 256016
On Thu, Nov 20, 2008 at 11:20 AM, Heiko Seeberger [EMAIL PROTECTED] wrote:
Hi Andrew,
Sounds like a good idea.
Heiko
Am 20.11.2008 um 00:02 schrieb Andrew Eisenberg:
Hi Martin and Heiko,
Do you have or are you planning on creating an update site for equinox
Hi Martin and Heiko,
Do you have or are you planning on creating an update site for equinox aspects?
___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
As I mentioned earlier in this thread, I think it has something to do
with the simple configurator bundle
(org.eclipse.equinox.simpleconfigurator_1.0.0.v20080604.jar) and how
it is used to bootstrap the loading of other bundles.
Here is the exception I get (the first line of the stack trace
Hi Martin,
Just tried out the latest version of equinox aspects and am
successfully weaving against OSGi head. That's great.
However, I am still getting an error when the equinox aspects weaver
is started at level 1. This problem goes away if I start it instead
at level 4.
Starting the
Nice. Thanks.
On Sat, Oct 25, 2008 at 1:39 PM, Martin Lippert [EMAIL PROTECTED] wrote:
Hi Andrew,
My question is, I would prefer to have the first option
([EMAIL PROTECTED]:start) are there any potential
problems with this? Consider that I only want to weave a select few
bundles that all
Right. Thanks.
Equinox Aspects contains a framework extension fragment
(org.eclipse.equinox.weaving.hook).
This is a fragment bundle which has to be co-located with the system bundle
(org.eclipse.osgi) which is a requirement from Equinox
I am applying equinox aspects to Eclipse 3.4.1. When I add this line
to my config.ini:
[EMAIL PROTECTED]:start,reference\:file\:[EMAIL PROTECTED]:start
I get an exception at startup:
org.osgi.framework.BundleException: The bundle could not be resolved.
Reason: Missing Constraint:
if your syntax is correct. I never have used
reference... or the full name including the bundle version in osgi.bundles.
Could you please try:
[EMAIL PROTECTED]:start,[EMAIL PROTECTED]:start
Please let me know your results.
Cheers
Heiko
Am 24.10.2008 um 17:39 schrieb Andrew Eisenberg:
I
Hi Martin and Heiko (or anyone else who can answer this),
Is there somewhere I can download the sources for aosgi or is there a
cvs repository I can grab it from?
thanks,
--a
___
equinox-dev mailing list
equinox-dev@eclipse.org
That's great news! Congratulations.
We are considering using Equinox Aspects with AJDT and so this could
possibly be a big help for us.
The reason why we are looking into Equinox Aspects is that for a long
time we had hoped that the JDT team would open up some of its inner
functionality to us
org.eclipse.ajdt.source.feature.feature.group (or something like that), or
if it is simpler and not too big the whole content.xml zipped.
Andrew Eisenberg ---07/10/2008 04:15:23 PM---I am making a P2 updater site
for AJDT. but I am running into some issues. It seems that the featur
From:
Andrew Eisenberg
I am making a P2 updater site for AJDT. but I am running into some
issues. It seems that the feature.properties file is not being used
in the content.jar. And therefore %featureName, %copyright.
%description, etc, is being used instead of the proper values that are
inside feature.properties.
27 matches
Mail list logo
