- This topic has 7 replies, 5 voices, and was last updated 20 years, 4 months ago by
.
-
Posts
-
I’m just about starting to work on Struts and have created a different workspace for playing around with Struts examples I see on the web. I have both my workspaces open so as I try something in my sandbox workspace, I can update my real workspace with these changes.
The problem is that MyEclipse starts complaining about the licence being used simultaneously. Could you fix the licence checker to not bump up the use count if the IP address is the same?
Regards
MilindMilind,
Could you fix the licence checker to not bump up the use count if the IP address is the same?
The problem with that approach is that it wouldn’t prevent someone setting up a large server and having an entire team run instances remotely on it. The license checker behaves this way by design as a result, since each subscription is a *single use* license.
That said, if you drop the nice folks at subscriptions@genuitec.com an email and tell them of your plight, they can probably find a way to help you out.
Hmmm. Not sure I followed how you can run Eclipse remotely. And surely not for $30! In any case, I’ll contact the subscription folks. Thanks.
os2baba,
the preferred method of doing this is to have only a single workspace per developer, but 1) close projects you’re not actively working on or that aren’t required on the build path and 2) creating “working sets” which effectively filter what you see in your workspace.
Then you can open multiple windows in eclipse “Window | New Window” and choose different working sets per window if needs be. This approach works very well and is also less memory and CPU intensive than opening up two separate JVMs both running copies of the same application.
I suggest you try this out and take advantage of working sets. Your CPU and memory will thank you 🙂
Okay, so you’re worried about a bunch of developers running remote instances. At $30 I don’t think anyone would be that inventive. The price of the hardware would cost far more then the developer licenses. This is a real issue for me since my remote client and server are in seperate workspaces but I develop on them in parallel. At the very least allow “TWO” instances per IP, I think that will make the problem go away for most people and you don’t have to worry about several hundred instances running off of one machine.
Okay, so you’re worried about a bunch of developers running remote instances. At $30 I don’t think anyone would be that inventive.
Don’t be so sure. We’ve already seen much worse.
Send an email over to subscriptions@genuitec.com, explain what you’re doing, and I’m sure they can help you out.
Jason, that is a really good idea. I like to keep my physical workspace directories separate in the file system and since I can create projects in directories outside the workspace, this would work well.
Having said that, it won’t work well for me in this instance, since I want to be able to run and refer to two systems simultaneously and opening and closing working sets or even cluttering up to see the entire workspace would be no fun.
But this does work well for the workspace I was using as a CVS front end to non Java resources like documents, data models etc.
