I found this page about people working to create Ubuntu packages for the
current version of eclipse:
https://launchpad.net/~eclipsers
"A collaboration to try to provide an up-to-date eclipse package for
Ubuntu (and possibly Debian in general)."
--
Upgrade to Eclipse 3.4.1
https://bugs.launchpad
Bloody hell, even my university has Ganymede on the Fedora 7 image.
--
Upgrade to Eclipse 3.4.1
https://bugs.launchpad.net/bugs/123064
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b...@lists.ubuntu.
You should ask a person / team before assigning bugs to them. A good
general rule is not to assign bugs to anyone but yourself.
The Ubuntu Eclipse upgrade has nothing to do with Medibuntu, so I have
removed the assign.
** Changed in: eclipse (Ubuntu)
Assignee: Medibuntu Packaging Team (medib
I assigned it to Medibuntu Packaging to see if they would include it -
up to them to review
--
Upgrade to Eclipse 3.4.1
https://bugs.launchpad.net/bugs/123064
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
I just noticed the Assignee changed to the Medibuntu Packaging team...
Does that mean Eclipse 3.4.1 is going to be included in Medibuntu?
--
Upgrade to Eclipse 3.4.1
https://bugs.launchpad.net/bugs/123064
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Changed in: eclipse (Ubuntu)
Assignee: (unassigned) => Michael Casadevall (mcasadevall)
** Changed in: eclipse (Ubuntu)
Assignee: Michael Casadevall (mcasadevall) => The Medibuntu Bot (medibuntu)
** Changed in: eclipse (Ubuntu)
Assignee: The Medibuntu Bot (medibuntu) => Medibunt
fwiw, in my PPA I have packages for Eclipse and a bunch of plugins that I built
using the release binaries from Eclipse.org:
https://launchpad.net/~yogarine/+archive
Obviously these packages aren't suitable for inclusion in the Ubuntu
repos, but they are stable and usable for everyone that just w
** Also affects: eclipse (Baltix)
Importance: Undecided
Status: New
--
Upgrade to Eclipse 3.4.1
https://bugs.launchpad.net/bugs/123064
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b...@lis
Thanks. Build seems to work nicely.
Had to do a complete uninstall of current eclipse first, in order to get it to
install.
Could have been the couple of addons I'd installed system wide (had to manually
remove those anyway).
Apart from that, works great. Oh, apart from eclipse w/ full ganyme
As a christmas present, a pre-pre-pre-alpha version of an eclipse 3.4.1 package
is now available in my
PPA;
http://launchpad.net/~pktoss/+archive
Details are available in this email to pkg-java-
maintain...@lists.alioth.debian.org:
http://lists.alioth.debian.org/pipermail/pkg-java-
maintainers/
s/releases/bugs/ ... I am not even able to add some ironic garbage to a
bug report it seems ...
--
Upgrade to Eclipse 3.4.1
https://bugs.launchpad.net/bugs/123064
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
No, in 2012 our world-domination plan will be more or less accomplished,
thus we will have the Ultimate Ubuntu. Howver, due to releases
introduced during the beta upgrades, it will be followed by the Very-
last Version, and finally, to fix bug #1, there will be the Wedding with
Windows. Then, there
>> Or, you could continue waiting patiently and (judging from history so far)
>> maybe by 2012, eclipse packages will be in ubuntu Vintage Vinegar or
>> something ;-)
>>
>
> In 2012, one can expect Ubuntu Porky Piglet (LTS release) and Queer
> Quacker (normal release), following the naming policy.
On 12/16/08, pkt wrote:
> I 'd like to invite all subscribers to this bug to maintain...@lists.alioth.debian.org>
>
> We are trying to start an effort to get eclipse-3.4 and its ilk in shape
> for debian. From there merging it to ubuntu will be much easier.
>
> The big problem is we don't have an
I 'd like to invite all subscribers to this bug to
We are trying to start an effort to get eclipse-3.4 and its ilk in shape
for debian. From there merging it to ubuntu will be much easier.
The big problem is we don't have anyone working full time on this, but I
think we can still make it happen
Simos Xenitellis wrote:
> On Wed, Nov 26, 2008 at 7:23 AM, Emilio Pozuelo Monfort
>> You should never start Eclipse as root.
> Emilio, such a terse statement does not help much.
People may read this bug report and then start Eclipse as root because someone
pointed it out. So this *does* help them
This bug report is an upgrade request for the Ubuntu repositories.
Discussion about alternative methods of upgrade/installation and the
workings of eclipse should be taken elsewhere. This is a large bug, and
each comment is generating a large amount of bugmail.
The upgrade request is already with
@Joel: if this is the case, then there is a lot less to talk about. I'm
sorry, I only had packages from PPA to play with, which, as I remember
now, do not have Software Updates (not even classic) enabled. Maybe we
should re-iterate which plugin installation problems we still have? I've
only seen tw
@Micah: bad idea, sorry. It is perfectly possible that there is some
kind of configuration which is "agreed on" (this is installed by the
admin) and then there might be some differences between developers, i.e.
someone wants to have a python plugin, which only s/he needs, someone
else prefers a sli
Nikolai,
I'm not understanding. Eclipse (Ganymede) *already* installs updates to
user directories (all except for Platform) and prefers those updates to
the system ones. There's nothing to be done here, it already works as it
should.
--
Upgrade to Eclipse 3.4.1
https://bugs.launchpad.net/bugs/12
I sent this by E-Mail, but it didn't show up, so here it is:
Olivier Bilodeau wrote:
> > I support Simos' suggestion. I would not normally agree with a
> > workaround like this but since it is a developer package it would be
> > tolerable.
> >
> > I also think current eclipse users would find it p
Simos, you are not helping much either. Running applications as root is
a no-go, no need to call a man a newbie. Just imaging every user of a
thin client doing this -- sudo rights for everyone? No way! There should
be a sane solution.
Eclipse should fix two things: installing updates to user direc
On Wed, Nov 26, 2008 at 7:23 AM, Emilio Pozuelo Monfort
<[EMAIL PROTECTED]>wrote:
> Olivier Bilodeau wrote:
> > Implementation suggestion: Since menu item comments show in tooltips, I
> > would suggest pointing out that when as root you can/should install
> > plugins.
>
> You should never start Ec
Rockwalrus' comment about not being to update plugins using the package
manager is incorrect (at least for the latest Eclipse release).
I was able to download Ganymede SR1, install it into /opt, run it as a
normal user, and update plugins (but not the core Platform). The plugins
went into my ~/.ec
Olivier Bilodeau wrote:
> Implementation suggestion: Since menu item comments show in tooltips, I
> would suggest pointing out that when as root you can/should install
> plugins.
You should never start Eclipse as root.
--
Upgrade to Eclipse 3.4.1
https://bugs.launchpad.net/bugs/123064
You receiv
I support Simos' suggestion. I would not normally agree with a
workaround like this but since it is a developer package it would be
tolerable.
I also think current eclipse users would find it pretty intuitive. In
the past (when eclipse was part of ubuntu) I always started eclipse as
root when I wa
I am not sure how the current discussion is related to this bug report.
In my humble opinion it would be better if we continue discussions which
are not directly related to a bug report on http://ubuntuforums.org/ or
http://brainstorm.ubuntu.com/
--
Upgrade to Eclipse 3.4.1
https://bugs.launchpa
How about adding in Applications/Programming two entries for Eclipse
1. Eclipse
2. Eclipse as root (or something like that).
The second option would then run "gksudo eclipse", and be able to
install updates in /usr/lib/eclipse/
--
Upgrade to Eclipse 3.4.1
https://bugs.launchpad.net/bugs/123064
> Some people use Eclipse for developing in other languages.
completely agree with that! I don't need everything related to java
development, since i'm using http://www.epic-ide.org/ only.
--
Upgrade to Eclipse 3.4.1
https://bugs.launchpad.net/bugs/123064
You received this bug notification becau
For those of you who say "Why does this need to be packaged? Just unzip
and run!", I think you're forgetting about package management.
To upgrade Eclipse to 3.4.1 would be a nightmare without package
management across a school board or business.
--
Upgrade to Eclipse 3.4.1
https://bugs.launchpad
@Rockwalrus: thanks for the insight!
So, suppose the .deb only includes the minimum necessary to install plug-ins (I
think that would be the platform install; a bit more than RCP). This base
wouldn't be update-able -- updates would install, but wouldn't be picked up by
Eclipse. I think that's ok
Guys, I don't see what the problem is.
Just provide the basic Java version
(http://www.eclipse.org/downloads/packages/eclipse-ide-java-developers/ganymedesr1)
and make sure there won't be permission problem when installing plugins via
eclipse plugin manager itself. This is it. You don't need to
It seems to me the .deb should include no plugins, or as close that as
possable. and have a plugin manager that hooks into eclipse's plugin manager
and causes, perhaps upon first use (ie if no .eclipse dir exists), the main
plugins to be installed for that user. This would be able to remain
consist
Probably in a perfect world it'd be possible to override the default
update manager behaviour to ask it to create a .deb for each plugin to
install... would it be feasible to do that? Just an idea, though.
--
Upgrade to Eclipse 3.4.1
https://bugs.launchpad.net/bugs/123064
You received this bug no
The classic update manager can't be used to update a plugin installed in
a global read-only location. It tries to install it to your user plugin
location, but when you restart, the global directory overrides the user-
specific one. But you can use the update manager to install new
plugins.
--
U
On 24.11.2008 20:11, Victor Costan wrote:
> In the interest of having this out quicker, I'd like to highlight that
> JDT is very easy to install using P2 (Eclipse's new package manager.) So
> I think the only component that needs to be included in the .deb is the
> platform, and the nice .xpm icon.
The package should be made for at least one reason, there are
dependencies (like java in ubuntu) which are not noted on the eclipse
installations page, but required for it to run properly.
Also users who are not experts with ubuntu (like me), are glad to have a
easy to use package manager.
I was
Let's avoid going in circles here:
"Rockwalrus wrote on 2008-09-17:
The new p2 update manager does not work in the PPA version. The classic
update manager can be enabled in Preferences under General/Capacities."
My suggestion would allow the classic update manager to be used instead
of the broke
In the interest of having this out quicker, I'd like to highlight that
JDT is very easy to install using P2 (Eclipse's new package manager.) So
I think the only component that needs to be included in the .deb is the
platform, and the nice .xpm icon. As far as I know, the platform isn't
update-able
Actually, when using the dropins directory to install plug-ins manually
in a system-wide installation (let's say, you have Eclipse 3.4.1
installed in /usr/lib/eclipse with root permissions, and install jdt and
pde in the dropins dir also with root permissions) then afaik those
plug-ins installed th
And what when a third-party plugin wants to upgrade the JDT? or a
similar core plugin that an Eclipse package would need to provide in
order to make Eclipse usable out of the box?
Eclipse's plugin manager can only "handle itself" correctly on a single-
user system, unless you start making system d
Sure, don't package plugins - I agree that Eclipse's plugin manager can
handle that itself. BUT - the convenience of a .deb package, which
handles JDK and JRT dependencies, puts a launcher in the menu, picks a
default directory, and so forth, is something I've gotten used to with
Ubuntu. I think th
I don't think it is good idea of packaging Eclipse as Ubuntu packages at
all. Base Eclipse platform is relatively easy to install - just unpack
it's archive to a directory. There is huge amount of plugins available
but Eclipse provides it's own plugin management system with dependency
resolving, po
43 matches
Mail list logo
