| License management in Eclipse [message #198746] |
Fri, 20 February 2004 15:08  |
Eclipse User |
|
|
|
Originally posted by: spam.oneparticularharbor.net
All,
I've been asked to look at commercial product license
management solutions that are compatible with Eclipse.
I'm hoping that I can get some recommendations and
suggestions on the matter from foilks who have looked
at this already.
Short term, I've been asked to look for a product
that will allow us to enforce runtime licensing for
our Eclipse plugins - ideally, one that we can deploy/
use without having to make code changes or rebuild.
I think this is technically impossible without altering
the stock Eclipse runtime environment; do I understand
this correctly?
Long term, we need a solution that will allow us to
do node-locked and floating license management. We're
probably going to go with a commercial solution; right
now, the two main contenders are:
EasyLicenser (ezlm) <http://www.agilis-software.com>
Flex (flexlm) <http://www.macrovision.com>
So, my questions:
0) Is there a non-intrusive method (no code recompile
required) for adding runtime license enforcement to
Eclipse plugins?
1) Aside from ezlm and flexlm, are there other license
management solutions I've overlooked?
2) Any anecdotal information about using ezlm/flexlm
with Eclipse-based products? With Java projects in
general?
TIA for your comments!
-Samrobb
-TimeSys Corporation
|
|
|
|
|
|
| Re: License management in Eclipse [message #260549 is a reply to message #260233] |
Mon, 12 July 2004 06:31  |
| Eclipse User |
|
|
|
Hi Myles
Thanks for your feedback.
1. I don't want to prevent access to Eclipse. I merely want to prevent
access to my plugin. I am thinking that I will carry out license validation
whenever a certain significant singleton object is accessed in my plugin
code. This means that the plug-in views can probably all be opened, but it
will be difficult for the user to do much. The intention is to make my
plugin of no value to an unlicensed user, rather than making it totally
unusable. I do not want to prevent acess to other Elipse plugins.
2. For now, the license will not be node-locked or floating, so that a
license can be used by any user in the customer's organisation.
3.A low level of security is sufficient.
4. Two levels: 1. Evaluation, 2. Professional. Evaluation is meant for
people to try the plugin before deciding to license it. It will have be
limited in two ways: (1) number of days, (2) usage. Usage refers to the
number of times a command in the plugin is executed. This is difficult
because the usage must be saved, probably in the user's workspace.
Michael
"Myles Jeffery" <myles_jeffery@hotmail.com> wrote in message
news:ccmj7b$mm7$1@eclipse.org...
> Michael,
>
> Of course, it all depends on what you want to do:
>
> 1. Do you want to prevent access to Eclipse if a license key has not been
> provided?
> 2. Do you want node locked or floating?
> 3. What level of security are you looking for?
> 4. Do you want the ability to specify license options (ie. entry,
> professional)
>
> Point 1. is technically challenging but feasible. We have done this. The
> other points affect the amount of money you are willing to part with. The
> more particular you are the more it will cost.
>
> Regards,
>
> Myles
>
>
> "Michael Doorley" <michael.doorley@eeng.dcu.ie> wrote in message
> news:ccmc28$8ku$1@eclipse.org...
> > I also need to implement License Management for a plugin. I have come
> > across:
> >
> > Java License Manager: http://alphase.com/
> >
> > Websina JLicense: http://www.websina.com/products/index.html
> >
> > Java License Kit:
> > http://members.chello.at/stefan-schneider/JavaLicenseKit.htm l
> >
> >
> >
> > Prices are about $50 for the first two and $200 for the third (but you
> must
> > also buy an obfuscator to use it)
> >
> >
> > If anyone has addressed this problem before I would be very interested
to
> > hear about their approach.
> >
> > thanks
> > Michael
> >
> > "Sam Robb" <spam@oneparticularharbor.net> wrote in message
> > news:c15pe5$phf$2@eclipse.org...
> > > Sam Robb wrote:
> > >
> > > > ...right now, the two main contenders are:
> > > >
> > > > EasyLicenser (ezlm) <http://www.agilis-software.com>
> > > > Flex (flexlm) <http://www.macrovision.com>
> > >
> > > That'll teach me to type in URLs from memory.
> > >
> > > Agilis Software is at <http://www.agilis-sw.com/> - my
> > > apologies for any confusion.
> > >
> > > -Samrobb
> > > -TimeSys Corporation
> >
> >
>
>
|
|
|
| Re: License management in Eclipse [message #261276 is a reply to message #260549] |
Tue, 13 July 2004 15:02 |
| Eclipse User |
|
|
|
Originally posted by: myles_jeffery.hotmail.com
For a first iteration of your license implementation, I don't think you can
go far wrong with the cheaper licensing products you mentioned. They will
certainly meet your criteria.
As you have identified, the real work and the real decisions are about in
what way to limit functionality. Be sure you are clear on this before you
begin development. Also, as a word of advice, don't make it too complex
otherwise your subsequent development and testing process will become that
much more awkward.
Regards,
Myles
"Michael Doorley" <michael.doorley@eeng.dcu.ie> wrote in message
news:cctp7k$e60$1@eclipse.org...
> Hi Myles
>
> Thanks for your feedback.
>
> 1. I don't want to prevent access to Eclipse. I merely want to prevent
> access to my plugin. I am thinking that I will carry out license
validation
> whenever a certain significant singleton object is accessed in my plugin
> code. This means that the plug-in views can probably all be opened, but
it
> will be difficult for the user to do much. The intention is to make my
> plugin of no value to an unlicensed user, rather than making it totally
> unusable. I do not want to prevent acess to other Elipse plugins.
>
> 2. For now, the license will not be node-locked or floating, so that a
> license can be used by any user in the customer's organisation.
>
> 3.A low level of security is sufficient.
>
> 4. Two levels: 1. Evaluation, 2. Professional. Evaluation is meant for
> people to try the plugin before deciding to license it. It will have be
> limited in two ways: (1) number of days, (2) usage. Usage refers to the
> number of times a command in the plugin is executed. This is difficult
> because the usage must be saved, probably in the user's workspace.
>
> Michael
>
> "Myles Jeffery" <myles_jeffery@hotmail.com> wrote in message
> news:ccmj7b$mm7$1@eclipse.org...
> > Michael,
> >
> > Of course, it all depends on what you want to do:
> >
> > 1. Do you want to prevent access to Eclipse if a license key has not
been
> > provided?
> > 2. Do you want node locked or floating?
> > 3. What level of security are you looking for?
> > 4. Do you want the ability to specify license options (ie. entry,
> > professional)
> >
> > Point 1. is technically challenging but feasible. We have done this. The
> > other points affect the amount of money you are willing to part with.
The
> > more particular you are the more it will cost.
> >
> > Regards,
> >
> > Myles
> >
> >
> > "Michael Doorley" <michael.doorley@eeng.dcu.ie> wrote in message
> > news:ccmc28$8ku$1@eclipse.org...
> > > I also need to implement License Management for a plugin. I have come
> > > across:
> > >
> > > Java License Manager: http://alphase.com/
> > >
> > > Websina JLicense: http://www.websina.com/products/index.html
> > >
> > > Java License Kit:
> > > http://members.chello.at/stefan-schneider/JavaLicenseKit.htm l
> > >
> > >
> > >
> > > Prices are about $50 for the first two and $200 for the third (but you
> > must
> > > also buy an obfuscator to use it)
> > >
> > >
> > > If anyone has addressed this problem before I would be very interested
> to
> > > hear about their approach.
> > >
> > > thanks
> > > Michael
> > >
> > > "Sam Robb" <spam@oneparticularharbor.net> wrote in message
> > > news:c15pe5$phf$2@eclipse.org...
> > > > Sam Robb wrote:
> > > >
> > > > > ...right now, the two main contenders are:
> > > > >
> > > > > EasyLicenser (ezlm) <http://www.agilis-software.com>
> > > > > Flex (flexlm) <http://www.macrovision.com>
> > > >
> > > > That'll teach me to type in URLs from memory.
> > > >
> > > > Agilis Software is at <http://www.agilis-sw.com/> - my
> > > > apologies for any confusion.
> > > >
> > > > -Samrobb
> > > > -TimeSys Corporation
> > >
> > >
> >
> >
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.13880 seconds
Home