| How does the amalgamation project create the DSL Toolkit product? [message #561227] |
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
|
|
|
Powered by
FUDForum. Page generated in 0.01734 seconds
] 
Search
Help
Register
Login
Home
