| Altering the Eclipse plugin - how to add to product build [message #332545] |
Tue, 28 October 2008 02:26  |
Eclipse User |
|
|
|
Originally posted by: NOBODY.NOSPAM.COM
Hello group,
I need some guidance on how to substitute a customized Eclipse plugin for a
build. I made some changes to the original org.eclipse.jface.databinding
plugin, and the app runs fine from Eclipse IDE, but now I need to build a
product from it.
I can think of 2 scenarios:
1. replace the original plugin in the Eclipse install directory (which means
exporting the customized plugin into a jar file), or
2. instruct the product build to use the customized plugin instead of the
one in the install directory.
I would much rather prefer option 2, but do not know if this is even
possible. An advice from someone with experience in this matter would be
greatly appreciated.
Thanks,
Alex Molochnikov
Kelman Technologies Inc.
|
|
|
| Re: Altering the Eclipse plugin - how to add to product build [message #332554 is a reply to message #332545] |
Tue, 28 October 2008 15:39  |
 Andrew Niefer
Messages: 990
Registered: July 2009 |
Senior Member |
|
|
First, make sure your jface.databinding has a different version from the
original. Then, the easiest way to make sure yours gets used is to base
your product on features. Then in the feature you can include the
jface.databinding plugin with a specific version instead of 0.0.0.
Note that jface.databinding is not a singleton bundle. If it was, then
it would be sufficient to have your custom version have a higher version
number and the OSGi state used by PDE/Build would then resolve the
higher version. Since it is not a singleton, both versions resolve and
you need to specify which one you want.
-Andrew
Alex Molochnikov wrote:
> Hello group,
>
> I need some guidance on how to substitute a customized Eclipse plugin for a
> build. I made some changes to the original org.eclipse.jface.databinding
> plugin, and the app runs fine from Eclipse IDE, but now I need to build a
> product from it.
>
> I can think of 2 scenarios:
>
> 1. replace the original plugin in the Eclipse install directory (which means
> exporting the customized plugin into a jar file), or
> 2. instruct the product build to use the customized plugin instead of the
> one in the install directory.
>
> I would much rather prefer option 2, but do not know if this is even
> possible. An advice from someone with experience in this matter would be
> greatly appreciated.
>
> Thanks,
>
> Alex Molochnikov
> Kelman Technologies Inc.
>
>
|
|
|
| Re: Altering the Eclipse plugin - how to add to product build [message #332566 is a reply to message #332554] |
Wed, 29 October 2008 05:51 |
| Eclipse User |
|
|
|
Originally posted by: NOBODY.NOSPAM.COM
Thanks, Andrew.
I ended up exporting my version of the plugin, and replacing the original
JAR in Eclipse install plugins folder. The only other thing that I had to do
was re-initialize Eclipse.
Alex
"Andrew Niefer" <aniefer@ca.ibm.com> wrote in message
news:ge7bn5$1lr$1@build.eclipse.org...
> First, make sure your jface.databinding has a different version from the
> original. Then, the easiest way to make sure yours gets used is to base
> your product on features. Then in the feature you can include the
> jface.databinding plugin with a specific version instead of 0.0.0.
>
> Note that jface.databinding is not a singleton bundle. If it was, then
> it would be sufficient to have your custom version have a higher version
> number and the OSGi state used by PDE/Build would then resolve the
> higher version. Since it is not a singleton, both versions resolve and
> you need to specify which one you want.
>
> -Andrew
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03223 seconds
] 
Search
Help
Register
Login
Home
