|
|
| Re: Including external bundles into the PDE/runtime/debug configuration [message #57768 is a reply to message #56087] |
Tue, 24 January 2006 04:35   |
Eclipse User |
|
|
|
Originally posted by: jeff_nospam_mcaffer.ca.ibm.com
Peter,
I'm not sure I follow this. Have you investigated the PDE/Target Platform
perference page? You might want to look at it in more recent builds as
there has been tremendous change there. If that is not satisfying your
usecase, please post back and let us know more detail on what you are
looking to do.
Jeff
"Peter Neubauer" <peter@neubauer.se> wrote in message
news:dprtdk$ic6$1@utils.eclipse.org...
> Hi,
> we are using the PDE for our OSGi bundle development. One of the major
> annoyances with that is that we are forced to create wrappers or mount the
> code for any plugins we want to include in a debug/run Equinox
> configuration.
> Is there any (planned) possibility to include "external" bundles by URL
into
> the launch configurations instead of having to install them once the
> console is started? I think that would ease pure OSGi development in the
> PDE a lot.
>
>
> /peter
|
|
|
| Re: Including external bundles into the PDE/runtime/debug configuration [message #58832 is a reply to message #57768] |
Sun, 29 January 2006 20:55 |
 Peter Neubauer
Messages: 21
Registered: July 2009 |
Junior Member |
|
|
Hi Jeff,
looking at least at eclipse 3.2M4 and some more I-builds after that, I still
find no possibility to solve my problem.
Referring to that PDE preference page, I would like to be able to add not
only Working Sets as a source of "non-built in" Eclipse plugins, but even
other locations except the workspace, like an OBR location, some bundle
storage on the local file system etc etc.
These locations of course probably contain binary plugins/bundles, but that
should be exactly the same logical usecase like the built in Eclipse
bundles?
The benefit of this would be that these external locations directly can be
used in the PDE for new plugin/bundle projects (exactly as the Eclipse
native ones) and be selected in the launch/run configurations. From the PDE
you then directly could use e.g. plugins from Oscar, Felix, KF, and even
other Eclipse projects without ever being forced to first include them
either in your PDE workspace as "wrapped" projects or install them with
your eclipse installation or via an extension location.
That making sense?
/peter
Jeff McAffer wrote:
> Peter,
>
> I'm not sure I follow this. Have you investigated the PDE/Target Platform
> perference page? You might want to look at it in more recent builds as
> there has been tremendous change there. If that is not satisfying your
> usecase, please post back and let us know more detail on what you are
> looking to do.
>
> Jeff
|
|
|
| Re: Including external bundles into the PDE/runtime/debug configuration [message #59028 is a reply to message #58832] |
Tue, 31 January 2006 14:53 |
| Eclipse User |
|
|
|
Originally posted by: jeff_nospam_mcaffer.ca.ibm.com
Hey Peter,
What you are asking for makes sense. The Target Platform exposes the notion
of having multiple locations for your target plugins. Notice there is a
check box that says "group plugins by location" at the bottom on the Plugins
tab. I suspect that the capability to actually define multiple locations is
not in yet or is somewhere that we can't see.
Can you enter a bug report for this in PDE/UI.
Note also that Wassim recently removed the requirement for plugins to be in
a "plugins" dir under the location specified. This was a great step.
Further to that, Pascal entered a great idea with a path to open up the way
PDE discovers plugins. See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=124542
Using this we would be able to plugin an extension that knows how to
discover plugins in a local Maven repo, or however KF lays out their world
or...
Jeff
"Peter Neubauer" <peter@neubauer.se> wrote in message
news:drja3u$2es$1@utils.eclipse.org...
> Hi Jeff,
> looking at least at eclipse 3.2M4 and some more I-builds after that, I
still
> find no possibility to solve my problem.
> Referring to that PDE preference page, I would like to be able to add not
> only Working Sets as a source of "non-built in" Eclipse plugins, but even
> other locations except the workspace, like an OBR location, some bundle
> storage on the local file system etc etc.
> These locations of course probably contain binary plugins/bundles, but
that
> should be exactly the same logical usecase like the built in Eclipse
> bundles?
>
> The benefit of this would be that these external locations directly can be
> used in the PDE for new plugin/bundle projects (exactly as the Eclipse
> native ones) and be selected in the launch/run configurations. From the
PDE
> you then directly could use e.g. plugins from Oscar, Felix, KF, and even
> other Eclipse projects without ever being forced to first include them
> either in your PDE workspace as "wrapped" projects or install them with
> your eclipse installation or via an extension location.
>
> That making sense?
>
> /peter
>
> Jeff McAffer wrote:
>
> > Peter,
> >
> > I'm not sure I follow this. Have you investigated the PDE/Target
Platform
> > perference page? You might want to look at it in more recent builds as
> > there has been tremendous change there. If that is not satisfying your
> > usecase, please post back and let us know more detail on what you are
> > looking to do.
> >
> > Jeff
>
|
|
|
|
| Re: Including external bundles into the PDE/runtime/debug configuration [message #59197 is a reply to message #59148] |
Wed, 01 February 2006 10:11 |
Peter Neubauer
Messages: 7
Registered: July 2009 |
Junior Member |
|
|
Peter Neubauer wrote:
> Hi Jeff,
> Jeff McAffer wrote:
>
>
>>Further to that, Pascal entered a great idea with a path to open up the
>>way PDE discovers plugins. See
>>https://bugs.eclipse.org/bugs/show_bug.cgi?id=124542
>>Using this we would be able to plugin an extension that knows how to
>>discover plugins in a local Maven repo, or however KF lays out their world
>>or...
>
> Yes, this is a great step towards truly adaptable plugin discoveries and
> layouts. Still, this covers the assembly of the Eclipse running instance
> plugins, not the ones used in the PDE to support plugin/bundle development.
> I will file a bug regarding having the same mechanism but within the PDE,
> without being forced to pollute your stable base Eclipse instance with
> development support bundles in one way or another.
>
> /peter
In fact, this is a combination of already existing requests, so my bug
was a duplicate. Anyway nice to get this working for both Eclipse itself
and bundle development!
/peter
|
|
|
Powered by
FUDForum. Page generated in 0.04499 seconds
] 
Search
Help
Register
Login
Home
