Skip to main content



      Home
Home » Eclipse Projects » GEF » Redistributing GEF
Redistributing GEF [message #80877] Mon, 26 May 2003 13:56 Go to next message
Eclipse UserFriend
Originally posted by: jpl.remotejava.com

Hello,

My plugin depends on GEF and draw2d. What would be the preferred way to
distribute it? Am I allowed to bundle the indicate the GEF feature in
dependencies of my plugin feature and redistribute the GEF code from
my site? If so, will it be convenient in all cases or will it cause
problems for users who have already installed GEF from elsewhere? I saw
another plugin which bundled the draw2d jars instead of declaring
a dependency - maybe this is the proper way to go?

Best regards -
Jan Ploski
Re: Redistributing GEF [message #80911 is a reply to message #80877] Mon, 26 May 2003 15:54 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: none.us.ibm.com

I think the normal way is to redistribute the entire *runtime* feature.
Features and plugins have a unique installation location for each Release
(for example, _2.1.0).
As long as you make sure you only redistribute official releases, and
everyone else does hte same, then any time you overwrite files, they will be
identical anyway.

"Jan Ploski" <jpl@remotejava.com> wrote in message
news:batkgq$fi7$1@rogue.oti.com...
> Hello,
>
> My plugin depends on GEF and draw2d. What would be the preferred way to
> distribute it? Am I allowed to bundle the indicate the GEF feature in
> dependencies of my plugin feature and redistribute the GEF code from
> my site? If so, will it be convenient in all cases or will it cause
> problems for users who have already installed GEF from elsewhere? I saw
> another plugin which bundled the draw2d jars instead of declaring
> a dependency - maybe this is the proper way to go?
>
> Best regards -
> Jan Ploski
>
Re: Redistributing GEF [message #95539 is a reply to message #80911] Fri, 26 September 2003 15:29 Go to previous message
Eclipse UserFriend
Originally posted by: jpl.remotejava.com

Hello,

My original question (posted in May 2003) concerned the preferred way to
redistribute GEF... Today I was pondering the subject again:

Randy Hudson wrote:

> I think the normal way is to redistribute the entire *runtime* feature.
> Features and plugins have a unique installation location for each Release
> (for example, _2.1.0).
> As long as you make sure you only redistribute official releases, and
> everyone else does hte same, then any time you overwrite files, they will be
> identical anyway.

Do I understand correctly that it would be ok to make the GEF runtime
feature downloadable from my own Update Site (along with my own feature,
which will use another license)?

Even if so, I still have a little problem. I can repackage the GEF
plugins/*
and features/* myself into a "feature JAR" as expected by the Eclipse
update
mechanism. However, when installing such a feature, Eclipse will eventually
display a warning about a missing digital signature. While I am probably
going
to buy a certificate with which I can sign my own code/feature, I feel it
would be more appropriate if the GEF feature was signed by its own authors,
much like other core features are.

Sure, I could tell the user to go install the GEF runtime from the official
Eclipse site (from the zip file), but I would very much prefer the
installation
of my product to take advantage of the Eclipse update mechanism and not
require
any additional setup.

I think it all comes down to the question: can you provide a nicely
packaged,
digitally signed version of GEF in the Eclipse update format?

Best regards -
Jan Ploski
Previous Topic:DnD: UI freezes when after drop
Next Topic:IAdaptable Interface Concept.
Goto Forum:
  


Current Time: Mon Sep 15 16:13:22 EDT 2025

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

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

Back to the top