Home » Eclipse Projects » Plugin Development Environment (PDE) » PDE doesn't recognize dropins folder in 3.4 target (p2)
| PDE doesn't recognize dropins folder in 3.4 target (p2) [message #14828] |
Fri, 01 August 2008 15:25  |
Eclipse User |
|
|
|
Originally posted by: none.ibm.com
I've created a custom target using the dropins folder. I launched the
custom target directly once, and it started up fine with all of the plugins
and features recognized that I unzipped into the $eclipse_root$/dropins
folder. But when I try to use it as my PDE target from another R3.4 IDE,
only the plug-ins in eclipse/plugins are recognized.
Does the PDE support p2 yet? What about using links?
|
|
| |
| Re: PDE doesn't recognize dropins folder in 3.4 target (p2) [message #14911 is a reply to message #14858] |
Mon, 04 August 2008 14:08  |
| Eclipse User |
|
|
|
Randy,
I believe the 'new target platform preference' is non-functional in Eclipse
3.4 based on what's documented in these bug reports
https://bugs.eclipse.org/bugs/show_bug.cgi?id=233670 ,
https://bugs.eclipse.org/bugs/show_bug.cgi?id=238949 and in particular this
comment https://bugs.eclipse.org/bugs/show_bug.cgi?id=238949#c14
Chris, please correct this assertion if you believe it to be in err.
Regards,
Todd
"Chris Aniszczyk" <zx@code9.com> wrote in message
news:g70ipb$bks$1@build.eclipse.org...
> Randy Hudson wrote:
>> I've created a custom target using the dropins folder. I launched the
>> custom target directly once, and it started up fine with all of the
>> plugins and features recognized that I unzipped into the
>> $eclipse_root$/dropins folder. But when I try to use it as my PDE target
>> from another R3.4 IDE, only the plug-ins in eclipse/plugins are
>> recognized.
>>
>> Does the PDE support p2 yet? What about using links?
>
> We support p2 and the old Update system. Are you aware of how the new
> target platform preference works?
>
> http://mea-bloga.blogspot.com/2008/04/new-target-platform-pr eference.html
>
> If checked, we will attempt to read the p2 configuration (or update
> configuration) and build the target platform based off of that. If not, we
> will revert to just scanning the directory for plug-ins.
>
> Cheers,
>
> ~ Chris
|
|
| | | |
| Re: PDE doesn't recognize dropins folder in 3.4 target (p2) [message #15227 is a reply to message #14911] |
Mon, 04 August 2008 15:55 |
| Eclipse User |
|
|
|
Originally posted by: none.ibm.com
Thanks Chris. Todd, it seems to work for me. I think there are still
issues or differences between what PDE detects and what gets auto-detected
when launching the target (233670 seemed along this line). For example,
simply unzipping plugins in the "plugins" folder will be detected by both
the launched target and the PDE. But unzipping plugins into the "dropins"
folder will not get detected by the PDE until the target is launched and
updates the installation. I think these differences are acceptible, but not
easy to understand in the current tooling. Also, there should be a way to
invoke the p2 auto-install via the PDE without having to launch the target
manually and then reloading the target from the PDE pref pages. Also, when
PDE launches a p2 target, it should somehow ask p2 whether or not any
auto-install tasks need to be done. If yes, it should prompt the user to
either:
1) Continue launch and prevent auto-install from doing anything
2) Abort launch, run auto-install, reload PDE target, recompile workspace,
relaunch
--Randy
"Todd Williams" <todd@genuitec.com> wrote in message
news:g77gis$l7d$1@build.eclipse.org...
> Randy,
>
> I believe the 'new target platform preference' is non-functional in
> Eclipse 3.4 based on what's documented in these bug reports
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=233670 ,
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=238949 and in particular
> this comment https://bugs.eclipse.org/bugs/show_bug.cgi?id=238949#c14
>
> Chris, please correct this assertion if you believe it to be in err.
>
> Regards,
> Todd
>
|
|
| |
| Re: PDE doesn't recognize dropins folder in 3.4 target (p2) [message #15291 is a reply to message #15227] |
Mon, 04 August 2008 16:12 |
| Eclipse User |
|
|
|
Originally posted by: zx.code9.com
Randy Hudson wrote:
> Thanks Chris. Todd, it seems to work for me. I think there are still
> issues or differences between what PDE detects and what gets auto-detected
> when launching the target (233670 seemed along this line). For example,
> simply unzipping plugins in the "plugins" folder will be detected by both
> the launched target and the PDE. But unzipping plugins into the "dropins"
> folder will not get detected by the PDE until the target is launched and
> updates the installation. I think these differences are acceptible, but not
> easy to understand in the current tooling. Also, there should be a way to
> invoke the p2 auto-install via the PDE without having to launch the target
> manually and then reloading the target from the PDE pref pages. Also, when
> PDE launches a p2 target, it should somehow ask p2 whether or not any
> auto-install tasks need to be done. If yes, it should prompt the user to
> either:
> 1) Continue launch and prevent auto-install from doing anything
> 2) Abort launch, run auto-install, reload PDE target, recompile workspace,
> relaunch
Randy, it's my hope to wean people off the target platform page and get
more people using target definition. With some additional enhancements
to the target definition file, we should have a solid story for building
and shared target platforms.
It's hard for PDE to figure out whether something you unzipped onto a
target install is something that we should poke p2 to install. We had
this exact same problem before with platform.xml files... if you
unzipped a fresh Ecilpse, started it... closed it. Downloaded EMF and
GEF, installed it by unzipping into plug-ins directory... PDE would
still miss EMF/GEF from the target platform because before 3.4, PDE
would find the platform.xml file and notice that it didn't contain
EMF/GEF yet since the target hasn't been launched.
Thanks for your feedback and I appreciate your patience.
Cheers,
~ Chris
|
|
|
| Re: PDE doesn't recognize dropins folder in 3.4 target (p2) [message #15323 is a reply to message #15291] |
Mon, 04 August 2008 18:21 |
| Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
Chris Aniszczyk schrieb:
> Randy Hudson wrote:
>> Thanks Chris. Todd, it seems to work for me. I think there are still
>> issues or differences between what PDE detects and what gets
>> auto-detected when launching the target (233670 seemed along this
>> line). For example, simply unzipping plugins in the "plugins" folder
>> will be detected by both the launched target and the PDE. But
>> unzipping plugins into the "dropins" folder will not get detected by
>> the PDE until the target is launched and updates the installation. I
>> think these differences are acceptible, but not easy to understand in
>> the current tooling. Also, there should be a way to invoke the p2
>> auto-install via the PDE without having to launch the target manually
>> and then reloading the target from the PDE pref pages. Also, when PDE
>> launches a p2 target, it should somehow ask p2 whether or not any
>> auto-install tasks need to be done. If yes, it should prompt the user
>> to either:
>> 1) Continue launch and prevent auto-install from doing anything
>> 2) Abort launch, run auto-install, reload PDE target, recompile
>> workspace, relaunch
>
> Randy, it's my hope to wean people off the target platform page and get
> more people using target definition.
this is also my experience. I'm using target definition and it works great.
With some additional enhancements
> to the target definition file, we should have a solid story for building
> and shared target platforms.
>
if one can work with multiple versions / locations of bundles in target
definition files this would be a great help. (bugzilla 233095) at the
moment I have to manage my different locations for a target definition
file that theres only a unique set of bundles over all
ekke
> It's hard for PDE to figure out whether something you unzipped onto a
> target install is something that we should poke p2 to install. We had
> this exact same problem before with platform.xml files... if you
> unzipped a fresh Ecilpse, started it... closed it. Downloaded EMF and
> GEF, installed it by unzipping into plug-ins directory... PDE would
> still miss EMF/GEF from the target platform because before 3.4, PDE
> would find the platform.xml file and notice that it didn't contain
> EMF/GEF yet since the target hasn't been launched.
>
> Thanks for your feedback and I appreciate your patience.
>
> Cheers,
>
> ~ Chris
|
|
|
| Re: PDE doesn't recognize dropins folder in 3.4 target (p2) [message #15356 is a reply to message #15291] |
Tue, 05 August 2008 10:41 |
| Eclipse User |
|
|
|
Originally posted by: none.ibm.com
> Randy, it's my hope to wean people off the target platform page and get
> more people using target definition. With some additional enhancements to
> the target definition file, we should have a solid story for building and
> shared target platforms.
If this is similar to sharing launch definitions, the real problem with
launch definitions is that they are negatives rather than positives (I've
reported bugzilla already). Please make targets additive rather than
subtractive.
It would also be nice if I could have two targets simultaneously available,
and I could simply run one launch profile or the other to determine not only
my workspace plug-ins, but my target plug-ins as well. This would be tricky
since recompilation is sometimes necessary (or maintaining multiple "./bin"
folders per active PDE target).
As an example use case, Rational Team Concert ships on eclipse 3.3, but
unofficially tolerates eclipse 3.4. Testing and maintaining this 3.4
compatibility is a challenge.
>
> It's hard for PDE to figure out whether something you unzipped onto a
> target install is something that we should poke p2 to install. We had
If launching the target would install it, then PDE should poke p2 to install
it.
> this exact same problem before with platform.xml files... if you unzipped
> a fresh Ecilpse, started it... closed it. Downloaded EMF and GEF,
> installed it by unzipping into plug-ins directory... PDE would still miss
> EMF/GEF from the target platform because before 3.4, PDE would find the
> platform.xml file and notice that it didn't contain EMF/GEF yet since the
> target hasn't been launched.
Really? That's not my experience. Maybe you mean if the new option is
turned on, then PDE would miss EMF/GEF because it doesn't simulate the
discovery?
|
|
|
| Re: PDE doesn't recognize dropins folder in 3.4 target (p2) [message #16227 is a reply to message #15194] |
Tue, 12 August 2008 03:45 |
| Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
sorry chris,
it took some days to find the time to test
and you know it always consumes much time
so i tested my scenarios from bugzilla 238950 (duplicate of 235336)
using 3.5.M1 and it works:
I made two shared installations,
then put someting in the dropins folder of one installation
and now PDE - TargetPlatform 'knows' the plugins from bundle pool
in both installations and from the dropins in one installation
:-)
ciao
ekke
Chris Aniszczyk schrieb:
> ekke wrote:
>> good news :-)
>
> Ekke, can you help out with testing a bit? I'm curious if this problem
> was fixed with this bug:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=235336
>
> Can you grab an Eclipse 3.5M1 build after 7/30?
>
> Like
>
> http://download.eclipse.org/eclipse/downloads/drops/I2008080 3-2135/index.php
>
>
> Thanks, I hope to track this guy down before 3.5M1 and 3.4.1 but
> reproducing this guy takes awhile.
>
> Cheers,
>
> ~ Chris
|
|
|
| Re: PDE doesn't recognize dropins folder in 3.4 target (p2) [message #575058 is a reply to message #14828] |
Fri, 01 August 2008 23:03 |
| Eclipse User |
|
|
|
Randy Hudson wrote:
> I've created a custom target using the dropins folder. I launched the
> custom target directly once, and it started up fine with all of the plugins
> and features recognized that I unzipped into the $eclipse_root$/dropins
> folder. But when I try to use it as my PDE target from another R3.4 IDE,
> only the plug-ins in eclipse/plugins are recognized.
>
> Does the PDE support p2 yet? What about using links?
We support p2 and the old Update system. Are you aware of how the new
target platform preference works?
http://mea-bloga.blogspot.com/2008/04/new-target-platform-pr eference.html
If checked, we will attempt to read the p2 configuration (or update
configuration) and build the target platform based off of that. If not,
we will revert to just scanning the directory for plug-ins.
Cheers,
~ Chris
|
|
|
| Re: PDE doesn't recognize dropins folder in 3.4 target (p2) [message #575116 is a reply to message #14858] |
Mon, 04 August 2008 14:08 |
| Eclipse User |
|
|
|
Randy,
I believe the 'new target platform preference' is non-functional in Eclipse
3.4 based on what's documented in these bug reports
https://bugs.eclipse.org/bugs/show_bug.cgi?id=233670 ,
https://bugs.eclipse.org/bugs/show_bug.cgi?id=238949 and in particular this
comment https://bugs.eclipse.org/bugs/show_bug.cgi?id=238949#c14
Chris, please correct this assertion if you believe it to be in err.
Regards,
Todd
"Chris Aniszczyk" <zx@code9.com> wrote in message
news:g70ipb$bks$1@build.eclipse.org...
> Randy Hudson wrote:
>> I've created a custom target using the dropins folder. I launched the
>> custom target directly once, and it started up fine with all of the
>> plugins and features recognized that I unzipped into the
>> $eclipse_root$/dropins folder. But when I try to use it as my PDE target
>> from another R3.4 IDE, only the plug-ins in eclipse/plugins are
>> recognized.
>>
>> Does the PDE support p2 yet? What about using links?
>
> We support p2 and the old Update system. Are you aware of how the new
> target platform preference works?
>
> http://mea-bloga.blogspot.com/2008/04/new-target-platform-pr eference.html
>
> If checked, we will attempt to read the p2 configuration (or update
> configuration) and build the target platform based off of that. If not, we
> will revert to just scanning the directory for plug-ins.
>
> Cheers,
>
> ~ Chris
|
|
| | | |
| Re: PDE doesn't recognize dropins folder in 3.4 target (p2) [message #575343 is a reply to message #14911] |
Mon, 04 August 2008 15:55 |
| Eclipse User |
|
|
|
Thanks Chris. Todd, it seems to work for me. I think there are still
issues or differences between what PDE detects and what gets auto-detected
when launching the target (233670 seemed along this line). For example,
simply unzipping plugins in the "plugins" folder will be detected by both
the launched target and the PDE. But unzipping plugins into the "dropins"
folder will not get detected by the PDE until the target is launched and
updates the installation. I think these differences are acceptible, but not
easy to understand in the current tooling. Also, there should be a way to
invoke the p2 auto-install via the PDE without having to launch the target
manually and then reloading the target from the PDE pref pages. Also, when
PDE launches a p2 target, it should somehow ask p2 whether or not any
auto-install tasks need to be done. If yes, it should prompt the user to
either:
1) Continue launch and prevent auto-install from doing anything
2) Abort launch, run auto-install, reload PDE target, recompile workspace,
relaunch
--Randy
"Todd Williams" <todd@genuitec.com> wrote in message
news:g77gis$l7d$1@build.eclipse.org...
> Randy,
>
> I believe the 'new target platform preference' is non-functional in
> Eclipse 3.4 based on what's documented in these bug reports
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=233670 ,
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=238949 and in particular
> this comment https://bugs.eclipse.org/bugs/show_bug.cgi?id=238949#c14
>
> Chris, please correct this assertion if you believe it to be in err.
>
> Regards,
> Todd
>
|
|
| |
| Re: PDE doesn't recognize dropins folder in 3.4 target (p2) [message #575406 is a reply to message #15227] |
Mon, 04 August 2008 16:12 |
| Eclipse User |
|
|
|
Randy Hudson wrote:
> Thanks Chris. Todd, it seems to work for me. I think there are still
> issues or differences between what PDE detects and what gets auto-detected
> when launching the target (233670 seemed along this line). For example,
> simply unzipping plugins in the "plugins" folder will be detected by both
> the launched target and the PDE. But unzipping plugins into the "dropins"
> folder will not get detected by the PDE until the target is launched and
> updates the installation. I think these differences are acceptible, but not
> easy to understand in the current tooling. Also, there should be a way to
> invoke the p2 auto-install via the PDE without having to launch the target
> manually and then reloading the target from the PDE pref pages. Also, when
> PDE launches a p2 target, it should somehow ask p2 whether or not any
> auto-install tasks need to be done. If yes, it should prompt the user to
> either:
> 1) Continue launch and prevent auto-install from doing anything
> 2) Abort launch, run auto-install, reload PDE target, recompile workspace,
> relaunch
Randy, it's my hope to wean people off the target platform page and get
more people using target definition. With some additional enhancements
to the target definition file, we should have a solid story for building
and shared target platforms.
It's hard for PDE to figure out whether something you unzipped onto a
target install is something that we should poke p2 to install. We had
this exact same problem before with platform.xml files... if you
unzipped a fresh Ecilpse, started it... closed it. Downloaded EMF and
GEF, installed it by unzipping into plug-ins directory... PDE would
still miss EMF/GEF from the target platform because before 3.4, PDE
would find the platform.xml file and notice that it didn't contain
EMF/GEF yet since the target hasn't been launched.
Thanks for your feedback and I appreciate your patience.
Cheers,
~ Chris
|
|
|
| Re: PDE doesn't recognize dropins folder in 3.4 target (p2) [message #575443 is a reply to message #15291] |
Mon, 04 August 2008 18:21 |
| Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
Chris Aniszczyk schrieb:
> Randy Hudson wrote:
>> Thanks Chris. Todd, it seems to work for me. I think there are still
>> issues or differences between what PDE detects and what gets
>> auto-detected when launching the target (233670 seemed along this
>> line). For example, simply unzipping plugins in the "plugins" folder
>> will be detected by both the launched target and the PDE. But
>> unzipping plugins into the "dropins" folder will not get detected by
>> the PDE until the target is launched and updates the installation. I
>> think these differences are acceptible, but not easy to understand in
>> the current tooling. Also, there should be a way to invoke the p2
>> auto-install via the PDE without having to launch the target manually
>> and then reloading the target from the PDE pref pages. Also, when PDE
>> launches a p2 target, it should somehow ask p2 whether or not any
>> auto-install tasks need to be done. If yes, it should prompt the user
>> to either:
>> 1) Continue launch and prevent auto-install from doing anything
>> 2) Abort launch, run auto-install, reload PDE target, recompile
>> workspace, relaunch
>
> Randy, it's my hope to wean people off the target platform page and get
> more people using target definition.
this is also my experience. I'm using target definition and it works great.
With some additional enhancements
> to the target definition file, we should have a solid story for building
> and shared target platforms.
>
if one can work with multiple versions / locations of bundles in target
definition files this would be a great help. (bugzilla 233095) at the
moment I have to manage my different locations for a target definition
file that theres only a unique set of bundles over all
ekke
> It's hard for PDE to figure out whether something you unzipped onto a
> target install is something that we should poke p2 to install. We had
> this exact same problem before with platform.xml files... if you
> unzipped a fresh Ecilpse, started it... closed it. Downloaded EMF and
> GEF, installed it by unzipping into plug-ins directory... PDE would
> still miss EMF/GEF from the target platform because before 3.4, PDE
> would find the platform.xml file and notice that it didn't contain
> EMF/GEF yet since the target hasn't been launched.
>
> Thanks for your feedback and I appreciate your patience.
>
> Cheers,
>
> ~ Chris
|
|
|
| Re: PDE doesn't recognize dropins folder in 3.4 target (p2) [message #575475 is a reply to message #15291] |
Tue, 05 August 2008 10:41 |
| Eclipse User |
|
|
|
> Randy, it's my hope to wean people off the target platform page and get
> more people using target definition. With some additional enhancements to
> the target definition file, we should have a solid story for building and
> shared target platforms.
If this is similar to sharing launch definitions, the real problem with
launch definitions is that they are negatives rather than positives (I've
reported bugzilla already). Please make targets additive rather than
subtractive.
It would also be nice if I could have two targets simultaneously available,
and I could simply run one launch profile or the other to determine not only
my workspace plug-ins, but my target plug-ins as well. This would be tricky
since recompilation is sometimes necessary (or maintaining multiple "./bin"
folders per active PDE target).
As an example use case, Rational Team Concert ships on eclipse 3.3, but
unofficially tolerates eclipse 3.4. Testing and maintaining this 3.4
compatibility is a challenge.
>
> It's hard for PDE to figure out whether something you unzipped onto a
> target install is something that we should poke p2 to install. We had
If launching the target would install it, then PDE should poke p2 to install
it.
> this exact same problem before with platform.xml files... if you unzipped
> a fresh Ecilpse, started it... closed it. Downloaded EMF and GEF,
> installed it by unzipping into plug-ins directory... PDE would still miss
> EMF/GEF from the target platform because before 3.4, PDE would find the
> platform.xml file and notice that it didn't contain EMF/GEF yet since the
> target hasn't been launched.
Really? That's not my experience. Maybe you mean if the new option is
turned on, then PDE would miss EMF/GEF because it doesn't simulate the
discovery?
|
|
|
| Re: PDE doesn't recognize dropins folder in 3.4 target (p2) [message #576123 is a reply to message #15194] |
Tue, 12 August 2008 03:45 |
| Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
sorry chris,
it took some days to find the time to test
and you know it always consumes much time
so i tested my scenarios from bugzilla 238950 (duplicate of 235336)
using 3.5.M1 and it works:
I made two shared installations,
then put someting in the dropins folder of one installation
and now PDE - TargetPlatform 'knows' the plugins from bundle pool
in both installations and from the dropins in one installation
:-)
ciao
ekke
Chris Aniszczyk schrieb:
> ekke wrote:
>> good news :-)
>
> Ekke, can you help out with testing a bit? I'm curious if this problem
> was fixed with this bug:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=235336
>
> Can you grab an Eclipse 3.5M1 build after 7/30?
>
> Like
>
> http://download.eclipse.org/eclipse/downloads/drops/I2008080 3-2135/index.php
>
>
> Thanks, I hope to track this guy down before 3.5M1 and 3.4.1 but
> reproducing this guy takes awhile.
>
> Cheers,
>
> ~ Chris
|
|
|
Goto Forum:
Current Time: Tue Apr 29 04:15:58 EDT 2025
Powered by FUDForum. Page generated in 0.14097 seconds |
Home