Eclipse and Portage

Message

walrus_55 · Post by **walrus_55** » Fri Jul 28, 2006 1:18 pm

After numerous tries and failure, i have notised that many people have tried and failed to install eclipse via portage. Why is it that everyone chooses to use the eclipse update manager? Have the portage team given up on eclipse? It seams so considering that version 3.2 has been out for a while yet 3.0 still cannot be installed via portage. I love portage and always use it to update software, most notibaly azureus and limewire, so should i surcome to temtation and install eclipse via the tar download file, or wait till eclipse is fully functional via portage?

Philantrop · Post by **Philantrop** » Fri Jul 28, 2006 2:13 pm

At the time of writing, I can install all versions of dev-util/eclipse-sdk in Portage by simply emerging them. If you have problems with either of those versions, please post about them.

The available versions: 3.0.1-r2 3.0.1-r3 3.0.2 3.0.2-r1 3.1.2-r3 3.2 (You might need to package.keyword some to emerge them.)

As of 3.2 you'll get the following text displayed after emerging it:

Users can now install plugins via Update Manager without any
tweaking.

Eclipse plugin packages (ie eclipse-cdt) will likely go away in
the near future until they can be properly packaged. Update Manager
is prefered in the meantime.

Why not use Update Manager for installing plugins? It's easy, convinient and, at the time of writing again, more reliable than emerging those add-ons. Personally, I think we don't need ebuilds for Eclipse plugins at all because Eclipse is perfectly capable of managing them itself.

My recommendation: Install Eclipse by emerging eclipse-sdk-3.2 (it's marked as testing but it's working flawlessly for me) and use its Update Manager to manage any plugins you might need. If that fails for any reason, please post about it.

genfive · Post by **genfive** » Fri Jul 28, 2006 6:57 pm

I personally found a few things better installed OUTSIDE of portage, and eclipse being one of them. Not to mention the fact that to get the latest eclipse, I must make some changes to the keywords, but more importantly, Eclipse installed via portage depends on the blackdown JDK, which is considered less stable than the SUN JDK.

Philantrop · Post by **Philantrop** » Fri Jul 28, 2006 7:32 pm

It doesn't depend on Blackdown but on virtual/jdk and virtual/jre. That includes sun-jdk and sun-jre. I don't even have Blackdown installed.

And the change to package.keywords is just one line.

genfive · Post by **genfive** » Fri Jul 28, 2006 8:25 pm

Philantrop wrote:It doesn't depend on Blackdown but on virtual/jdk and virtual/jre. That includes sun-jdk and sun-jre. I don't even have Blackdown installed.

And the change to package.keywords is just one line.

can you show me what the change is? I tried to emerge sun-jdk, and it won't let me ... so I had to manually download the file and then install it manually as well.

Philantrop · Post by **Philantrop** » Fri Jul 28, 2006 8:44 pm

Ok, I just realised if you're running x86 it's not just one line. Sorry.

You should follow the Gentoo Java Upgrade Guide to update to Sun-JDK 1.5.

Skywacker · Post by **Skywacker** » Fri Aug 04, 2006 9:13 pm

well if you are running amd64, what is the one line?

can you post working configs please?

Thanks.

Earthwings · Post by **Earthwings** » Fri Aug 04, 2006 9:31 pm

genfive wrote:I personally found a few things better installed OUTSIDE of portage, and eclipse being one of them.

True. The Eclipse guys however are working on a better Linux integration, which means a more convenient installation in upcoming releases. See http://www.eclipse.org/proposals/linux-distro/

Gergan Penkov · Post by **Gergan Penkov** » Fri Aug 04, 2006 9:41 pm

Well I hope for one that some of the things in this link would be resolved, and of course I'd be happy if they resolve at first the idiotic java packaging system they now use, it is just shame how this language boosts as resolving so many issues (interoperability, stability, compile-once-run-everywhere and so on - bullshit), and at the end one could not install two plugins without fully breaking eclipse.
I for one find that netbeans has made much more progress for the last two years than eclipse, bad that I could not use the plugins I need - it is faster, uses ant for the project files and so on...

Earthwings · Post by **Earthwings** » Sat Aug 05, 2006 7:49 am

Gergan Penkov wrote:and of course I'd be happy if they resolve at first the idiotic java packaging system they now use, it is just shame how this language boosts as resolving so many issues (interoperability, stability, compile-once-run-everywhere and so on - bullshit), and at the end one could not install two plugins without fully breaking eclipse.

Care to elaborate on that? I'm working with Eclipse and Java for some time now and I'm not sure what you mean.

Bill Cosby · Post by **Bill Cosby** » Sat Aug 05, 2006 8:19 am

I downloaded eclipse, unpacked it, made a litttle script in bin and voila ready, no need to emerge all the packages which come with emerge.

genfive · Post by **genfive** » Sat Aug 05, 2006 12:41 pm

Bill Cosby wrote:I downloaded eclipse, unpacked it, made a litttle script in bin and voila ready, no need to emerge all the packages which come with emerge.

can't agree more!

Gergan Penkov · Post by **Gergan Penkov** » Sat Aug 05, 2006 2:00 pm

Earthwings wrote:
Gergan Penkov wrote:and of course I'd be happy if they resolve at first the idiotic java packaging system they now use, it is just shame how this language boosts as resolving so many issues (interoperability, stability, compile-once-run-everywhere and so on - bullshit), and at the end one could not install two plugins without fully breaking eclipse.
Care to elaborate on that? I'm working with Eclipse and Java for some time now and I'm not sure what you mean.

just some examples install jboss-ide and myeclipse on eclipse - they both install standard eclipse jars for some of the eclipse-extensions, which conflict with each other, causing the ide to crawl or the jvm to die with internal error.
Now first why is it possible for third-party plugins to install standard extension eclipse-jars, they should be downloaded from eclipse (for example), if needed.
why there is no possibility to install versions of these jars, whithout real conflicts, in reasonable way.
now the last thing is just java problem, why all of this plugins should install standard jars - for example xdoclet, the commons, the jboss client jars and so on.
All this is a problem with java in fact, because it fails to dictate a reasonable way to package and version the things installed (and here I should note that nichoj and the whole gentoo-java team, should receive big credits and publicity for their work, which alleviates most of these java problems).
And so on frustrations...