Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » [target] Using a target platform definition to create an installation?
[target] Using a target platform definition to create an installation? [message #61203] Tue, 12 May 2009 23:02 Go to next message
Eric Jain is currently offline Eric JainFriend
Messages: 266
Registered: July 2009
Senior Member
Where does a target platform definition download it's bundles (those
listed in software sites) to? Would be useful if there was an option to
dump them in a specific location/installation, especially since the target
platform definitions can't be used in headless builds
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=266311]...
Re: [target] Using a target platform definition to create an installation? [message #61302 is a reply to message #61203] Wed, 13 May 2009 04:02 Go to previous messageGo to next message
Chris Aniszczyk is currently offline Chris AniszczykFriend
Messages: 674
Registered: July 2009
Senior Member
Eric Jain wrote:
> Where does a target platform definition download it's bundles (those
> listed in software sites) to? Would be useful if there was an option to
> dump them in a specific location/installation, especially since the
> target platform definitions can't be used in headless builds
> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=266311]...

Why would this be useful :)?

If your target definition is based off of 'Software Sites' and point to
a p2 repo and IU, you can replicate this in your build.

As of Eclipse 3.5M5, PDE Build supports fetching artifacts from p2 repos:

http://download.eclipse.org/eclipse/downloads/drops/S-3.5M5- 200902021535/eclipse-news-M5.html#PDE

If you listed the same IUs in your target definition and in your PDE
Build map file... you should get the same things. In theory at least ;)

On a side note, the reason target definitions can't be used headlessly
yet because you can create target definitions that aren't really meant
to be used in a headless build (ie., pointing to some absolute path or
relative path that PDE Build can't resolve). In Eclipse 3.6/4.0, we'll
look at trying to unify the stories for both IDE/headless environments.
I think we're getting closer now that we have p2 and have revamped the
target definition model.

Thanks for your reports, it helps us to know people's use cases.

Cheers,

Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk
Re: [target] Using a target platform definition to create an installation? [message #61584 is a reply to message #61302] Wed, 13 May 2009 18:58 Go to previous messageGo to next message
Eric Jain is currently offline Eric JainFriend
Messages: 266
Registered: July 2009
Senior Member
Chris Aniszczyk wrote:
> As of Eclipse 3.5M5, PDE Build supports fetching artifacts from p2 repos:
>
>
http://download.eclipse.org/eclipse/downloads/drops/S-3.5M5- 200902021535/eclipse-news-M5.html#PDE

Saw that and it looks like it might help -- except that I haven't figured
out how to use the "map file" mechanism so far (complication: we use svn)
:-(

Now investigating Buckminster, maybe that's a better solution...
Re: [target] Using a target platform definition to create an installation? [message #65871 is a reply to message #61302] Sat, 27 June 2009 00:36 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: jconlon.apache.org

In Ganymede I used PDE Build pointing to a Target Platform that also
included the delta pack.
baseLocation=/opt/Eclipse/tracker-eclipse_target_platform-20 0905071512/eclipse

Now in Galileo taking advantage of all the latest cool features of
target definintion files, I have initially configured a file with two
software sites, a directory with misc bundles, and a
directory with the delta pack.

Using this target the IDE can
export my product for multiple platforms (all with p2 enabled) and
create a p2 repo as well. Great - Thanks PDE team!

But from Chris's comments in this thread, to use PDE Build it looks like
I will need to go back to a physical disk based Target Platform, similar
to the one I used on Ganymede (with an eclipse configuration overlayed
with the delta pack and spiced up with any other plugins and features I
need for my app. Referenced with the baseLocaton property in the
build.properties file.

Is that correct, or are there any alternatives?

thanks for any help,
John


Chris Aniszczyk wrote:
> Eric Jain wrote:
>> Where does a target platform definition download it's bundles (those
>> listed in software sites) to? Would be useful if there was an option
>> to dump them in a specific location/installation, especially since the
>> target platform definitions can't be used in headless builds
>> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=266311]...
>
> Why would this be useful :)?
>
> If your target definition is based off of 'Software Sites' and point to
> a p2 repo and IU, you can replicate this in your build.
>
> As of Eclipse 3.5M5, PDE Build supports fetching artifacts from p2 repos:
>
> http://download.eclipse.org/eclipse/downloads/drops/S-3.5M5- 200902021535/eclipse-news-M5.html#PDE
>
>
> If you listed the same IUs in your target definition and in your PDE
> Build map file... you should get the same things. In theory at least ;)
>
> On a side note, the reason target definitions can't be used headlessly
> yet because you can create target definitions that aren't really meant
> to be used in a headless build (ie., pointing to some absolute path or
> relative path that PDE Build can't resolve). In Eclipse 3.6/4.0, we'll
> look at trying to unify the stories for both IDE/headless environments.
> I think we're getting closer now that we have p2 and have revamped the
> target definition model.
>
> Thanks for your reports, it helps us to know people's use cases.
>
> Cheers,
>
> Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
> http://twitter.com/eclipsesource | http://twitter.com/caniszczyk
Re: [target] Using a target platform definition to create an installation? [message #65906 is a reply to message #65871] Sat, 27 June 2009 20:37 Go to previous message
Chris Aniszczyk is currently offline Chris AniszczykFriend
Messages: 674
Registered: July 2009
Senior Member
John E. Conlon wrote:
> In Ganymede I used PDE Build pointing to a Target Platform that also
> included the delta pack.
> baseLocation=/opt/Eclipse/tracker-eclipse_target_platform-20 0905071512/eclipse
>
>
> Now in Galileo taking advantage of all the latest cool features of
> target definintion files, I have initially configured a file with two
> software sites, a directory with misc bundles, and a
> directory with the delta pack.
>
> Using this target the IDE can
> export my product for multiple platforms (all with p2 enabled) and
> create a p2 repo as well. Great - Thanks PDE team!
>
> But from Chris's comments in this thread, to use PDE Build it looks like
> I will need to go back to a physical disk based Target Platform, similar
> to the one I used on Ganymede (with an eclipse configuration overlayed
> with the delta pack and spiced up with any other plugins and features I
> need for my app. Referenced with the baseLocaton property in the
> build.properties file.
>
> Is that correct, or are there any alternatives?

So, that's somewhat true. You can potentially find a way to use the PDE
Build support to fetch artifacts from p2 repositories.

" new extension has been added to PDE/Build that enables users to fetch
artifacts from p2 repositories. You can now add an entry to your map
file for build input and PDE/Build will retrieve the artifact and
include it in the build.
The map file entry needs to include the id and version of the
installable unit (IU), and the URI of the repository where the IU can be
found. The metadata and artifact repositories are assumed to be
co-located. An example is:

plugin@my.bundle.id ,1.0.0=p2IU,id=my.bundle.id,version=1.0.0,repository=http:/e xample.com/repo "

So you can fetch an IU that represents the SDK, deltapack and other
things. This would map to what you have specified in your target
definition for things that are based on 'software sites'

In Eclipse 3.6, we're looking at ways on making things more reusable
from a build point of view. It would be nice if you could reuse the
target definition at development time and build time. However, there are
some challenges that still need to be addressed.

Cheers,

Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk
Re: [target] Using a target platform definition to create an installation? [message #597340 is a reply to message #61203] Wed, 13 May 2009 04:02 Go to previous message
Chris Aniszczyk is currently offline Chris AniszczykFriend
Messages: 674
Registered: July 2009
Senior Member
Eric Jain wrote:
> Where does a target platform definition download it's bundles (those
> listed in software sites) to? Would be useful if there was an option to
> dump them in a specific location/installation, especially since the
> target platform definitions can't be used in headless builds
> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=266311]...

Why would this be useful :)?

If your target definition is based off of 'Software Sites' and point to
a p2 repo and IU, you can replicate this in your build.

As of Eclipse 3.5M5, PDE Build supports fetching artifacts from p2 repos:

http://download.eclipse.org/eclipse/downloads/drops/S-3.5M5- 200902021535/eclipse-news-M5.html#PDE

If you listed the same IUs in your target definition and in your PDE
Build map file... you should get the same things. In theory at least ;)

On a side note, the reason target definitions can't be used headlessly
yet because you can create target definitions that aren't really meant
to be used in a headless build (ie., pointing to some absolute path or
relative path that PDE Build can't resolve). In Eclipse 3.6/4.0, we'll
look at trying to unify the stories for both IDE/headless environments.
I think we're getting closer now that we have p2 and have revamped the
target definition model.

Thanks for your reports, it helps us to know people's use cases.

Cheers,

Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk
Re: [target] Using a target platform definition to create an installation? [message #597418 is a reply to message #61302] Wed, 13 May 2009 18:58 Go to previous message
Eric Jain is currently offline Eric JainFriend
Messages: 266
Registered: July 2009
Senior Member
Chris Aniszczyk wrote:
> As of Eclipse 3.5M5, PDE Build supports fetching artifacts from p2 repos:
>
>
http://download.eclipse.org/eclipse/downloads/drops/S-3.5M5- 200902021535/eclipse-news-M5.html#PDE

Saw that and it looks like it might help -- except that I haven't figured
out how to use the "map file" mechanism so far (complication: we use svn)
:-(

Now investigating Buckminster, maybe that's a better solution...
Re: [target] Using a target platform definition to create an installation? [message #598669 is a reply to message #61302] Sat, 27 June 2009 00:36 Go to previous message
Eclipse UserFriend
Originally posted by: jconlon.apache.org

In Ganymede I used PDE Build pointing to a Target Platform that also
included the delta pack.
baseLocation=/opt/Eclipse/tracker-eclipse_target_platform-20 0905071512/eclipse

Now in Galileo taking advantage of all the latest cool features of
target definintion files, I have initially configured a file with two
software sites, a directory with misc bundles, and a
directory with the delta pack.

Using this target the IDE can
export my product for multiple platforms (all with p2 enabled) and
create a p2 repo as well. Great - Thanks PDE team!

But from Chris's comments in this thread, to use PDE Build it looks like
I will need to go back to a physical disk based Target Platform, similar
to the one I used on Ganymede (with an eclipse configuration overlayed
with the delta pack and spiced up with any other plugins and features I
need for my app. Referenced with the baseLocaton property in the
build.properties file.

Is that correct, or are there any alternatives?

thanks for any help,
John


Chris Aniszczyk wrote:
> Eric Jain wrote:
>> Where does a target platform definition download it's bundles (those
>> listed in software sites) to? Would be useful if there was an option
>> to dump them in a specific location/installation, especially since the
>> target platform definitions can't be used in headless builds
>> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=266311]...
>
> Why would this be useful :)?
>
> If your target definition is based off of 'Software Sites' and point to
> a p2 repo and IU, you can replicate this in your build.
>
> As of Eclipse 3.5M5, PDE Build supports fetching artifacts from p2 repos:
>
> http://download.eclipse.org/eclipse/downloads/drops/S-3.5M5- 200902021535/eclipse-news-M5.html#PDE
>
>
> If you listed the same IUs in your target definition and in your PDE
> Build map file... you should get the same things. In theory at least ;)
>
> On a side note, the reason target definitions can't be used headlessly
> yet because you can create target definitions that aren't really meant
> to be used in a headless build (ie., pointing to some absolute path or
> relative path that PDE Build can't resolve). In Eclipse 3.6/4.0, we'll
> look at trying to unify the stories for both IDE/headless environments.
> I think we're getting closer now that we have p2 and have revamped the
> target definition model.
>
> Thanks for your reports, it helps us to know people's use cases.
>
> Cheers,
>
> Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
> http://twitter.com/eclipsesource | http://twitter.com/caniszczyk
Re: [target] Using a target platform definition to create an installation? [message #598690 is a reply to message #65871] Sat, 27 June 2009 20:37 Go to previous message
Chris Aniszczyk is currently offline Chris AniszczykFriend
Messages: 674
Registered: July 2009
Senior Member
John E. Conlon wrote:
> In Ganymede I used PDE Build pointing to a Target Platform that also
> included the delta pack.
> baseLocation=/opt/Eclipse/tracker-eclipse_target_platform-20 0905071512/eclipse
>
>
> Now in Galileo taking advantage of all the latest cool features of
> target definintion files, I have initially configured a file with two
> software sites, a directory with misc bundles, and a
> directory with the delta pack.
>
> Using this target the IDE can
> export my product for multiple platforms (all with p2 enabled) and
> create a p2 repo as well. Great - Thanks PDE team!
>
> But from Chris's comments in this thread, to use PDE Build it looks like
> I will need to go back to a physical disk based Target Platform, similar
> to the one I used on Ganymede (with an eclipse configuration overlayed
> with the delta pack and spiced up with any other plugins and features I
> need for my app. Referenced with the baseLocaton property in the
> build.properties file.
>
> Is that correct, or are there any alternatives?

So, that's somewhat true. You can potentially find a way to use the PDE
Build support to fetch artifacts from p2 repositories.

" new extension has been added to PDE/Build that enables users to fetch
artifacts from p2 repositories. You can now add an entry to your map
file for build input and PDE/Build will retrieve the artifact and
include it in the build.
The map file entry needs to include the id and version of the
installable unit (IU), and the URI of the repository where the IU can be
found. The metadata and artifact repositories are assumed to be
co-located. An example is:

plugin@my.bundle.id ,1.0.0=p2IU,id=my.bundle.id,version=1.0.0,repository=http:/e xample.com/repo "

So you can fetch an IU that represents the SDK, deltapack and other
things. This would map to what you have specified in your target
definition for things that are based on 'software sites'

In Eclipse 3.6, we're looking at ways on making things more reusable
from a build point of view. It would be nice if you could reuse the
target definition at development time and build time. However, there are
some challenges that still need to be addressed.

Cheers,

Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk
Previous Topic:PDE Build templates
Next Topic:[visualization] Unable to update
Goto Forum:
  


Current Time: Sun Jun 13 04:55:02 GMT 2021

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

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

Back to the top