Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » FYI: Target Platform Changes
FYI: Target Platform Changes [message #48169] Wed, 25 February 2009 17:44 Go to next message
Chris Aniszczyk is currently offline Chris AniszczykFriend
Messages: 674
Registered: July 2009
Senior Member
Dear Plug-in Developers... there was significant changes to the target
platform story recently in PDE:

http://eclipsesource.com/blogs/2009/02/24/target-platform-ch anges/

Hope you like it!

Cheers,

Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/caniszczyk | http://twitter.com/eclipsesource
Re: FYI: Target Platform Changes [message #48306 is a reply to message #48169] Wed, 25 February 2009 20:45 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: eclipse-news.rizzoweb.com

On 2/25/2009 12:44 PM, Chris Aniszczyk wrote:
> Dear Plug-in Developers... there was significant changes to the target
> platform story recently in PDE:
>
> http://eclipsesource.com/blogs/2009/02/24/target-platform-ch anges/
>
> Hope you like it!

I do, but...
I posted a comment asking about whether PDE Build could use the new
configuration. You replied "not at this time." So, is that planned for
3.5 GA or not?

[I prefer to have the discussion here because I find blog comments a
poor mechanism for an ongoing discussion]

Eric
Re: FYI: Target Platform Changes [message #48365 is a reply to message #48306] Wed, 25 February 2009 20:55 Go to previous messageGo to next message
Chris Aniszczyk is currently offline Chris AniszczykFriend
Messages: 674
Registered: July 2009
Senior Member
Eric Rizzo wrote:
> On 2/25/2009 12:44 PM, Chris Aniszczyk wrote:
>> Dear Plug-in Developers... there was significant changes to the target
>> platform story recently in PDE:
>>
>> http://eclipsesource.com/blogs/2009/02/24/target-platform-ch anges/
>>
>> Hope you like it!
>
> I do, but...
> I posted a comment asking about whether PDE Build could use the new
> configuration. You replied "not at this time." So, is that planned for
> 3.5 GA or not?

There isn't a bug open for it, but if you want it in for 3.5, I suggest
opening a bug. It's a bit more complicated than you think to have PDE
Build use this new format, but we should have a bug open to kickstart
the discussion. How about that?

Cheers,

Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/caniszczyk | http://twitter.com/eclipsesource
Re: FYI: Target Platform Changes [message #48439 is a reply to message #48365] Thu, 26 February 2009 14:50 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: eclipse-news.rizzoweb.com

On 2/25/2009 3:55 PM, Chris Aniszczyk wrote:
> Eric Rizzo wrote:
>> On 2/25/2009 12:44 PM, Chris Aniszczyk wrote:
>>> Dear Plug-in Developers... there was significant changes to the target
>>> platform story recently in PDE:
>>>
>>> http://eclipsesource.com/blogs/2009/02/24/target-platform-ch anges/
>>>
>>> Hope you like it!
>>
>> I do, but...
>> I posted a comment asking about whether PDE Build could use the new
>> configuration. You replied "not at this time." So, is that planned for
>> 3.5 GA or not?
>
> There isn't a bug open for it, but if you want it in for 3.5, I suggest
> opening a bug. It's a bit more complicated than you think to have PDE
> Build use this new format, but we should have a bug open to kickstart
> the discussion. How about that?

Done. https://bugs.eclipse.org/bugs/show_bug.cgi?id=266311

By the way, I do understand that this is not trivial. But I hope the
point is clear that using this new mechnaism would mean we have to
maintain two different targets (one for IDE and one for headless) and
that is a complete show-stopper for us in adopting the new feature.

Eric
Re: FYI: Target Platform Changes [message #48459 is a reply to message #48439] Thu, 26 February 2009 16:45 Go to previous messageGo to next message
Chris Aniszczyk is currently offline Chris AniszczykFriend
Messages: 674
Registered: July 2009
Senior Member
Eric Rizzo wrote:
> On 2/25/2009 3:55 PM, Chris Aniszczyk wrote:
> Done. https://bugs.eclipse.org/bugs/show_bug.cgi?id=266311
>
> By the way, I do understand that this is not trivial. But I hope the
> point is clear that using this new mechnaism would mean we have to
> maintain two different targets (one for IDE and one for headless) and
> that is a complete show-stopper for us in adopting the new feature.

I would be curious how you maintain your target now?

Cheers,

~ Chris
Re: FYI: Target Platform Changes [message #48614 is a reply to message #48459] Fri, 27 February 2009 16:52 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: eclipse-news.rizzoweb.com

On 2/26/2009 11:45 AM, Chris Aniszczyk wrote:
> Eric Rizzo wrote:
>> On 2/25/2009 3:55 PM, Chris Aniszczyk wrote:
>> Done. https://bugs.eclipse.org/bugs/show_bug.cgi?id=266311
>>
>> By the way, I do understand that this is not trivial. But I hope the
>> point is clear that using this new mechnaism would mean we have to
>> maintain two different targets (one for IDE and one for headless) and
>> that is a complete show-stopper for us in adopting the new feature.
>
> I would be curious how you maintain your target now?

By hand. It actually is structured so that I can use a .target file in
the IDE and the headless build just flattens everything out into a
single features/ and single plugins/ directory after it checks it out of
CVS.

So, we have this (checked in to CVS):

TargetPlatform/
eclipse/
features/
plugins/
<etc.>
ext/
m2eclipse/
RSA/
<other third-party extensions that we depend on>

The .target file assumes target_home is set to TargetPlatform/eclipse/
and then specifies <extraLocations> such as
"${target_home}/../ext/Maven2Eclipse/eclipse"

The headless build copies the contents of those extraLocations'
features/ and plugins/ into eclipse/features/ and eclipse/plugins and
off it goes.
From my reading of the new target definition features, using it would
mean a lot more work for our headless build - no?

By the way, I'm not saying this is the best or easiest way to do this,
but it works for us. Of course, if you'd be willing to help this fellow
PMC member and Eclipse Foundation Member company do a better job of
this, I'd be thrilled ;-)

Eric
Re: FYI: Target Platform Changes [message #48644 is a reply to message #48614] Fri, 27 February 2009 17:16 Go to previous message
Chris Aniszczyk is currently offline Chris AniszczykFriend
Messages: 674
Registered: July 2009
Senior Member
Eric Rizzo wrote:
> By hand. It actually is structured so that I can use a .target file in
> the IDE and the headless build just flattens everything out into a
> single features/ and single plugins/ directory after it checks it out of
> CVS.
>
> So, we have this (checked in to CVS):
>
> TargetPlatform/
> eclipse/
> features/
> plugins/
> <etc.>
> ext/
> m2eclipse/
> RSA/
> <other third-party extensions that we depend on>
>
> The .target file assumes target_home is set to TargetPlatform/eclipse/
> and then specifies <extraLocations> such as
> "${target_home}/../ext/Maven2Eclipse/eclipse"
>
> The headless build copies the contents of those extraLocations'
> features/ and plugins/ into eclipse/features/ and eclipse/plugins and
> off it goes.
> From my reading of the new target definition features, using it would
> mean a lot more work for our headless build - no?
>
> By the way, I'm not saying this is the best or easiest way to do this,
> but it works for us. Of course, if you'd be willing to help this fellow
> PMC member and Eclipse Foundation Member company do a better job of
> this, I'd be thrilled ;-)

So one important thing to note, your workflow won't change at all
because this is still supported by the new target definition story.

Why are you flattening things out? PDE Build should support additional
locations via the 'pluginPath' property (see the template build.properties):

#pluginPath is a list of locations in which to find plugins and
features. This list is separated by the platform file separator (; or :)
#a location is one of:
#- the location of the jar or folder that is the plugin or feature :
/path/to/foo.jar or /path/to/foo
#- a directory that contains a /plugins or /features subdirectory
#- the location of a feature.xml, or for 2.1 style plugins, the
plugin.xml or fragment.xml
#pluginPath=

Cheers,

Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/caniszczyk | http://twitter.com/eclipsesource
Re: FYI: Target Platform Changes [message #592413 is a reply to message #48169] Wed, 25 February 2009 20:45 Go to previous message
Eric Rizzo is currently offline Eric RizzoFriend
Messages: 3071
Registered: July 2009
Senior Member
On 2/25/2009 12:44 PM, Chris Aniszczyk wrote:
> Dear Plug-in Developers... there was significant changes to the target
> platform story recently in PDE:
>
> http://eclipsesource.com/blogs/2009/02/24/target-platform-ch anges/
>
> Hope you like it!

I do, but...
I posted a comment asking about whether PDE Build could use the new
configuration. You replied "not at this time." So, is that planned for
3.5 GA or not?

[I prefer to have the discussion here because I find blog comments a
poor mechanism for an ongoing discussion]

Eric
Re: FYI: Target Platform Changes [message #592432 is a reply to message #48306] Wed, 25 February 2009 20:55 Go to previous message
Chris Aniszczyk is currently offline Chris AniszczykFriend
Messages: 674
Registered: July 2009
Senior Member
Eric Rizzo wrote:
> On 2/25/2009 12:44 PM, Chris Aniszczyk wrote:
>> Dear Plug-in Developers... there was significant changes to the target
>> platform story recently in PDE:
>>
>> http://eclipsesource.com/blogs/2009/02/24/target-platform-ch anges/
>>
>> Hope you like it!
>
> I do, but...
> I posted a comment asking about whether PDE Build could use the new
> configuration. You replied "not at this time." So, is that planned for
> 3.5 GA or not?

There isn't a bug open for it, but if you want it in for 3.5, I suggest
opening a bug. It's a bit more complicated than you think to have PDE
Build use this new format, but we should have a bug open to kickstart
the discussion. How about that?

Cheers,

Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/caniszczyk | http://twitter.com/eclipsesource
Re: FYI: Target Platform Changes [message #592454 is a reply to message #48365] Thu, 26 February 2009 14:50 Go to previous message
Eric Rizzo is currently offline Eric RizzoFriend
Messages: 3071
Registered: July 2009
Senior Member
On 2/25/2009 3:55 PM, Chris Aniszczyk wrote:
> Eric Rizzo wrote:
>> On 2/25/2009 12:44 PM, Chris Aniszczyk wrote:
>>> Dear Plug-in Developers... there was significant changes to the target
>>> platform story recently in PDE:
>>>
>>> http://eclipsesource.com/blogs/2009/02/24/target-platform-ch anges/
>>>
>>> Hope you like it!
>>
>> I do, but...
>> I posted a comment asking about whether PDE Build could use the new
>> configuration. You replied "not at this time." So, is that planned for
>> 3.5 GA or not?
>
> There isn't a bug open for it, but if you want it in for 3.5, I suggest
> opening a bug. It's a bit more complicated than you think to have PDE
> Build use this new format, but we should have a bug open to kickstart
> the discussion. How about that?

Done. https://bugs.eclipse.org/bugs/show_bug.cgi?id=266311

By the way, I do understand that this is not trivial. But I hope the
point is clear that using this new mechnaism would mean we have to
maintain two different targets (one for IDE and one for headless) and
that is a complete show-stopper for us in adopting the new feature.

Eric
Re: FYI: Target Platform Changes [message #592468 is a reply to message #48439] Thu, 26 February 2009 16:45 Go to previous message
Chris Aniszczyk is currently offline Chris AniszczykFriend
Messages: 674
Registered: July 2009
Senior Member
Eric Rizzo wrote:
> On 2/25/2009 3:55 PM, Chris Aniszczyk wrote:
> Done. https://bugs.eclipse.org/bugs/show_bug.cgi?id=266311
>
> By the way, I do understand that this is not trivial. But I hope the
> point is clear that using this new mechnaism would mean we have to
> maintain two different targets (one for IDE and one for headless) and
> that is a complete show-stopper for us in adopting the new feature.

I would be curious how you maintain your target now?

Cheers,

~ Chris
Re: FYI: Target Platform Changes [message #592516 is a reply to message #48459] Fri, 27 February 2009 16:52 Go to previous message
Eric Rizzo is currently offline Eric RizzoFriend
Messages: 3071
Registered: July 2009
Senior Member
On 2/26/2009 11:45 AM, Chris Aniszczyk wrote:
> Eric Rizzo wrote:
>> On 2/25/2009 3:55 PM, Chris Aniszczyk wrote:
>> Done. https://bugs.eclipse.org/bugs/show_bug.cgi?id=266311
>>
>> By the way, I do understand that this is not trivial. But I hope the
>> point is clear that using this new mechnaism would mean we have to
>> maintain two different targets (one for IDE and one for headless) and
>> that is a complete show-stopper for us in adopting the new feature.
>
> I would be curious how you maintain your target now?

By hand. It actually is structured so that I can use a .target file in
the IDE and the headless build just flattens everything out into a
single features/ and single plugins/ directory after it checks it out of
CVS.

So, we have this (checked in to CVS):

TargetPlatform/
eclipse/
features/
plugins/
<etc.>
ext/
m2eclipse/
RSA/
<other third-party extensions that we depend on>

The .target file assumes target_home is set to TargetPlatform/eclipse/
and then specifies <extraLocations> such as
"${target_home}/../ext/Maven2Eclipse/eclipse"

The headless build copies the contents of those extraLocations'
features/ and plugins/ into eclipse/features/ and eclipse/plugins and
off it goes.
From my reading of the new target definition features, using it would
mean a lot more work for our headless build - no?

By the way, I'm not saying this is the best or easiest way to do this,
but it works for us. Of course, if you'd be willing to help this fellow
PMC member and Eclipse Foundation Member company do a better job of
this, I'd be thrilled ;-)

Eric
Re: FYI: Target Platform Changes [message #592530 is a reply to message #48614] Fri, 27 February 2009 17:16 Go to previous message
Chris Aniszczyk is currently offline Chris AniszczykFriend
Messages: 674
Registered: July 2009
Senior Member
Eric Rizzo wrote:
> By hand. It actually is structured so that I can use a .target file in
> the IDE and the headless build just flattens everything out into a
> single features/ and single plugins/ directory after it checks it out of
> CVS.
>
> So, we have this (checked in to CVS):
>
> TargetPlatform/
> eclipse/
> features/
> plugins/
> <etc.>
> ext/
> m2eclipse/
> RSA/
> <other third-party extensions that we depend on>
>
> The .target file assumes target_home is set to TargetPlatform/eclipse/
> and then specifies <extraLocations> such as
> "${target_home}/../ext/Maven2Eclipse/eclipse"
>
> The headless build copies the contents of those extraLocations'
> features/ and plugins/ into eclipse/features/ and eclipse/plugins and
> off it goes.
> From my reading of the new target definition features, using it would
> mean a lot more work for our headless build - no?
>
> By the way, I'm not saying this is the best or easiest way to do this,
> but it works for us. Of course, if you'd be willing to help this fellow
> PMC member and Eclipse Foundation Member company do a better job of
> this, I'd be thrilled ;-)

So one important thing to note, your workflow won't change at all
because this is still supported by the new target definition story.

Why are you flattening things out? PDE Build should support additional
locations via the 'pluginPath' property (see the template build.properties):

#pluginPath is a list of locations in which to find plugins and
features. This list is separated by the platform file separator (; or :)
#a location is one of:
#- the location of the jar or folder that is the plugin or feature :
/path/to/foo.jar or /path/to/foo
#- a directory that contains a /plugins or /features subdirectory
#- the location of a feature.xml, or for 2.1 style plugins, the
plugin.xml or fragment.xml
#pluginPath=

Cheers,

Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/caniszczyk | http://twitter.com/eclipsesource
Previous Topic:Generate pack200 versions of plugin JARs using P2?
Next Topic:Versioning on dependent features?
Goto Forum:
  


Current Time: Sun Jun 20 23:09:46 GMT 2021

Powered by FUDForum. Page generated in 0.02350 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top