Home » Modeling » Amalgam » How does the amalgamation project create the DSL Toolkit product?
| How does the amalgamation project create the DSL Toolkit product? [message #525100] |
Wed, 28 January 2009 11:05  |
 Marc Moser
Messages: 66
Registered: July 2009 |
Member |
|
|
Hi,
I know that this is probably not the best newsgroup to ask this
question. But I've been fighting with this problem for quite some time
and given the downloads the amalgamation project offers, it must have
solved this problem already, so I thought I'll give it a try :-)
The problem is this: we have developed a small number of plug-ins, and
now we would like to give them away as part of an eclipse product. In
addition, we want to bundle several additional Eclipse (modeling)
plug-ins with the product. In fact, our product is "similar" to the
amalgamation projects DSL Toolkit, as it will also contain Eclipse SDK,
EMF, OCL, GEF, GMF... But it should contain some more projects (e.g.
CDO, QVTO) and our own plug-ins.
Now the question is: what is the preferred way to build/package such a
product? I really don't have much experience with these things, and any
help/idea are greatly appreciated. Currently, I'm doing it the
following way: 1) download and install Eclipse SDK, 2) download all
additional eclipse projects (EMF, OCL, ...) and put them to the dropins
folder, 3) open my product definition and add all features available in
the host eclipse to it, 4) export the product using the product export
wizard.
I often do have problems already with step 2). It seems to require some
"luck" to get a configuration that works and loads all plugins from the
dropins folder. So I started to wonder how the amalgamation project is
doing it, since it basically must solve the same problem.
Many thanks!
All the best,
Marc Moser
|
|
|
| Re: How does the amalgamation project create the DSL Toolkit product? [message #525101 is a reply to message #525100] |
Wed, 28 January 2009 12:02  |
Richard Gronback
Messages: 605
Registered: July 2009 |
Senior Member |
|
|
Hello,
I'd suggest you start by reading this blog entry from Andrew Niefer:
http://aniefer.blogspot.com/2008/06/example-headless-build-f or-rcp-product.h
tml
The easiest way to see how it's done in Amalgam is to open the Plug-in
Development perspective in the latest DSL Toolkit I-build. In the Plug-ins
view, right-click the org.eclipse.amalgam.releng.builder plug-in and Import
As... -> Source Project.
Here you'll find the build.ecore and product.ecore models used to drive the
included QVT and Xpand transformations that produce the build scripts used
to drive the product-based build. You may also want to check out the
org.eclipse.amalgam.releng project from dev.eclipse.org /cvsroot/modeling
and look at the build model for both the dsltk and modeler products.
I also use this builder for Galileo itself, which is documented here:
http://wiki.eclipse.org/Galileo/Build
Be warned that although this model-driven builder works well for Amalgam and
Galileo, I don't yet have it at the point where I'm able to recommend it to
someone not willing to dig into the details and figure out how much of it
works with minimal support ;)
HTH,
Rich
On 1/28/09 6:05 AM, in article glpe59$2c6$1@build.eclipse.org, "Marc Moser"
<moser@montages.com> wrote:
> Hi,
>
> I know that this is probably not the best newsgroup to ask this
> question. But I've been fighting with this problem for quite some time
> and given the downloads the amalgamation project offers, it must have
> solved this problem already, so I thought I'll give it a try :-)
>
> The problem is this: we have developed a small number of plug-ins, and
> now we would like to give them away as part of an eclipse product. In
> addition, we want to bundle several additional Eclipse (modeling)
> plug-ins with the product. In fact, our product is "similar" to the
> amalgamation projects DSL Toolkit, as it will also contain Eclipse SDK,
> EMF, OCL, GEF, GMF... But it should contain some more projects (e.g.
> CDO, QVTO) and our own plug-ins.
>
> Now the question is: what is the preferred way to build/package such a
> product? I really don't have much experience with these things, and any
> help/idea are greatly appreciated. Currently, I'm doing it the
> following way: 1) download and install Eclipse SDK, 2) download all
> additional eclipse projects (EMF, OCL, ...) and put them to the dropins
> folder, 3) open my product definition and add all features available in
> the host eclipse to it, 4) export the product using the product export
> wizard.
>
> I often do have problems already with step 2). It seems to require some
> "luck" to get a configuration that works and loads all plugins from the
> dropins folder. So I started to wonder how the amalgamation project is
> doing it, since it basically must solve the same problem.
>
> Many thanks!
>
> All the best,
> Marc Moser
>
|
|
|
| Re: How does the amalgamation project create the DSL Toolkit product? [message #561248 is a reply to message #525100] |
Wed, 28 January 2009 12:02 |
Richard Gronback
Messages: 605
Registered: July 2009 |
Senior Member |
|
|
Hello,
I'd suggest you start by reading this blog entry from Andrew Niefer:
http://aniefer.blogspot.com/2008/06/example-headless-build-f or-rcp-product.h
tml
The easiest way to see how it's done in Amalgam is to open the Plug-in
Development perspective in the latest DSL Toolkit I-build. In the Plug-ins
view, right-click the org.eclipse.amalgam.releng.builder plug-in and Import
As... -> Source Project.
Here you'll find the build.ecore and product.ecore models used to drive the
included QVT and Xpand transformations that produce the build scripts used
to drive the product-based build. You may also want to check out the
org.eclipse.amalgam.releng project from dev.eclipse.org /cvsroot/modeling
and look at the build model for both the dsltk and modeler products.
I also use this builder for Galileo itself, which is documented here:
http://wiki.eclipse.org/Galileo/Build
Be warned that although this model-driven builder works well for Amalgam and
Galileo, I don't yet have it at the point where I'm able to recommend it to
someone not willing to dig into the details and figure out how much of it
works with minimal support ;)
HTH,
Rich
On 1/28/09 6:05 AM, in article glpe59$2c6$1@build.eclipse.org, "Marc Moser"
<moser@montages.com> wrote:
> Hi,
>
> I know that this is probably not the best newsgroup to ask this
> question. But I've been fighting with this problem for quite some time
> and given the downloads the amalgamation project offers, it must have
> solved this problem already, so I thought I'll give it a try :-)
>
> The problem is this: we have developed a small number of plug-ins, and
> now we would like to give them away as part of an eclipse product. In
> addition, we want to bundle several additional Eclipse (modeling)
> plug-ins with the product. In fact, our product is "similar" to the
> amalgamation projects DSL Toolkit, as it will also contain Eclipse SDK,
> EMF, OCL, GEF, GMF... But it should contain some more projects (e.g.
> CDO, QVTO) and our own plug-ins.
>
> Now the question is: what is the preferred way to build/package such a
> product? I really don't have much experience with these things, and any
> help/idea are greatly appreciated. Currently, I'm doing it the
> following way: 1) download and install Eclipse SDK, 2) download all
> additional eclipse projects (EMF, OCL, ...) and put them to the dropins
> folder, 3) open my product definition and add all features available in
> the host eclipse to it, 4) export the product using the product export
> wizard.
>
> I often do have problems already with step 2). It seems to require some
> "luck" to get a configuration that works and loads all plugins from the
> dropins folder. So I started to wonder how the amalgamation project is
> doing it, since it basically must solve the same problem.
>
> Many thanks!
>
> All the best,
> Marc Moser
>
|
|
|
Goto Forum:
Current Time: Thu Apr 18 00:55:33 GMT 2024
Powered by FUDForum. Page generated in 0.02779 seconds |
] 
Search
Help
Register
Login
Home
