[csell]

Hello,

I am evaluating ME under linux with a manual, non-registered install. My eclipse directories are all owned by root, and the user I run eclipse under has only read permission to them. Now, as soon as I access any item related to myeclipse for the first time, I get an error “invalid thread access” with accompanying stack trace. After that, when accessing the second time, I get the evaluation expiry warning dialog. Interestingly, the expiry period is always 30 days.
Could it be that myeclipse is trying to write to the install directory and generates an error because it cannot? Will someone change that – write permissions will only be available below the users home directory, nowhere else.

thanks,
Christian

[Riyad Kalla]

Christian, please check out this FAQ entry: http://www.myeclipseide.com/FAQ+index-myfaq-yes-id_cat-4.html#154

[csell]

hmm, if I read the FAQ item correctly, I would have to reinstall *both* eclipse and myeclipse into my home directory, or run eclipse as root in order to continue the evaluation. I guess this is not for me, then. Thank you.

[Scott Anderson]

Actually, that’s not true. It’s simply that Eclipse and MyEclipse must be both installed and run as the same user when in “trial” mode. Once a license is purchased, this restriction is no longer the case.

[Riyad Kalla]

To clarify, for evaluation Eclipse and MyEclipse need to be installed with the same user privaleges and run as that user. Once you purchase a key there is flexibility here in that you can setup the permissions separately for the two items (some people on Gentoo I know like to emerge Eclipse and install MyEclipse in their home dir).

or run eclipse as root in order to continue the evaluation

Well no, just run it under whichever user you decide, but keep them both consistent. So basically go into the Eclipse or ME dir and use chown -R to switch their perms to another user.

I guess this is not for me, then. Thank you.

Hah, so I missed my 2-second window of opportunity to convince you hu? I’ll be faster next time 😉

[csell]

Well no, just run it under whichever user you decide, but keep them both consistent. So basically go into the Eclipse or ME dir and use chown -R to switch their perms to another user.

I certainly dont consider that a “simple” requirement – chown a system directory to be able to run some tool. I suppose its just one single file ME needs write access to, why dont you mention that?

thanks,
Christian

[Riyad Kalla]

I certainly dont consider that a “simple” requirement – chown a system director

I agree with you, this certainly isn’t the nicest solution ever but due to how the licesning system works, when ME is in trial mode, trying to run it and Eclipse as two different users freaks it out and thinks its being pirated. When you buy a ME license the licensing system relaxes a bit and I believe uses IP address to determine who’s running it. I’m not privvy to the details about this, but I think that’s the gist.

I admit I haven’t setup a central eclipse/multi-user ME system before so I can’t be too much help in this arena. Either way I hope you find the tool that fits your bill the best, I know that evaluating tools can be a PIA especially if each one has its own funky way that it needs to be installed and such.

[csell]

I admit I haven’t setup a central eclipse/multi-user ME system before so I can’t be too much help in this arena.

I dont want to stress this too much, but please understand that my configuration is the normal way of doing things on *X platforms, even on single-user workstations. Software installation goes into a system directory with restricted write access, typically owned by root. All user-specific data goes below the users home directory.
Eclipse even has mechanisms of keeping plugin-specific data (like licensing data) in a user directory that is always write enabled (below the .metadata directory, where eclipse keeps its workbench config). All you have to do is use the appropriate APIs.

Let me also mention that MyEclipse gives me a strange gut feeling. You are using all kinds of (sometimes half-baked) open source products , but rename the packages and fork the code (I assume). Are you giving anything back to the projects like SQLExplorer, XMen, etc.?
And now you are making such a fuss about licensing. I was considering to buy a subscription just to get rid of the errors, but your words (“the licensing system relaxes a bit” – huh?) make me hesitate.

regards,
Christian

[csell]

when ME is in trial mode, trying to run it and Eclipse as two different users freaks it out and thinks its being pirated.

let me also add that I am not running eclipse and ME as different users. The only problem is that ME cannot write to the directory where it keeps its license file (which it does in a place where it has no business). ME also does not “think” its being pirated, it just throws an exception and then goes on functioning. I could go like this forever, as the 30-day period never expires.

’nuff said.
christian

[Scott Anderson]

Christian,

I could go like this forever, as the 30-day period never expires.

Actually, that’s not really true. However, if you ignore the exception your 30-day trial should function properly.

I apologize that you found the requirements for the trial install to be so onerous. Truthfully, we’ve had tens of thousands of Linux version downloads and this issue has been mentioned about three times. In the other instances, simply letting the users know what the requirements were was all that was needed to resolve the issue.

In any case, we’re glad you’re up and running. Please let us know if you have any questions about the product functionality.

Let me also mention that MyEclipse gives me a strange gut feeling. You are using all kinds of (sometimes half-baked) open source products , but rename the packages and fork the code (I assume). Are you giving anything back to the projects like SQLExplorer, XMen, etc.?

We use open source to the degree that it helps us more rapidly deliver commercial quality products. Typically, the open source projects we use get us 20-40% of the functionality we need but also require rather substantial rework or enhancements. However, its still faster than starting from nothing, and that’s really the point of open source — use it as you wish. The end result is that we spend a lot of time extending and hardening the functionality in order to make it commerical quality in most cases.

Are you giving anything back to the projects like SQLExplorer, XMen, etc.?

Yes, we do. We’re good OSS citizens. We make financial contributions to all projects we use and typically also engage the authors in some level of paid enhancement or support arrangement. The most recent contribution from us went to SQLExplorer and I believe they’re currently updating their site to make note that their work will be partially sponsored by Genuitec going forward.

[Author]

Posts