Please change the targeted upgrade to Eclipse 3.5.0.
--
Upgrade to Eclipse 3.4.2
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-bugs@lists.ubuntu.com
https://lis
Fedora 11 uses 3.4.2.
http://docs.fedoraproject.org/release-notes/f11/en-US/sect-
Release_Notes-Eclipse.html
--
Upgrade to Eclipse 3.4.2
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-b
Thanks for the information Karl, but this bug report is about packaging the
latest stable version of Eclipse.
On Mon, Jun 8, 2009 at 6:10 PM, karl michael
wrote:
> i use the latest version of eclipse in Ubuntu 8.04
> http://ubuntuforums.org/showthread.php?t=941461&highlight=eclipse
>
> --
> Upgra
i use the latest version of eclipse in Ubuntu 8.04
http://ubuntuforums.org/showthread.php?t=941461&highlight=eclipse
--
Upgrade to Eclipse 3.4.2
https://bugs.launchpad.net/bugs/123064
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
Mandriva isn't based on Ubuntu at all (Mandriva is a new name for
Mandrake, which in turn is based on Red Hat, and both are older than
Ubuntu).
Mandriva also uses RPMs whereas Ubuntu uses deb packages, and packaging
guidelines are quite different, so one of Debian or Ubuntu will have to
package Ec
Hello, seems like Mandriva ships the latest version of eclipse.
http://qense.nl/eclipse-34-on-ubuntu-is-tricky-but-possible/comment-
page-1#comment-6291
Being Mandriva based on Ubuntu couldn't Debian/Ubuntu grab the package
from them or join forces ?
--
Upgrade to Eclipse 3.4.2
https://bugs.lau
Matthias: can you work on fixing bug 312824 (i.e., sponsoring the move
of jetty from contrib to main) so that someone can actually get started
on decent eclipse packaging?
--
Upgrade to Eclipse 3.4.2
https://bugs.launchpad.net/bugs/123064
You received this bug notification because you are a membe
Status know, package isn't maintained in Debian anymore. Updating to a
new package version requires some effort. If somebody does want to start
this, please get in contact on the ubuntu-devel ML.
The current packaging in the PPA isn't suited for upload to
karmic/universe.
As long as the package i
I would like to help.
--
Upgrade to Eclipse 3.4.2
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-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/
On Tue, May 19, 2009 at 6:58 PM, Luca Saba wrote:
> I'd like too! Ready to learn!
Testing is great but what is missing right now is someone with enough free time
to do the actual work. I 'll hopefully have some free time in the beginnings of
July but not before.
--
Upgrade to Eclipse 3.4.2
http
I'd like too! Ready to learn!
--
Upgrade to Eclipse 3.4.2
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-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/l
I'm be willing to do testing, but I know nothing about Java or
packaging.
--
Upgrade to Eclipse 3.4.2
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-bugs@lists.u
Well, why not aim for 3.5 instead? It is not like the work required
to get 3.4.x in shape is any less, or that it would
be finished before 3.5 is out anyway. (Of course that is just imho).
--
Upgrade to Eclipse 3.4.2
https://bugs.launchpad.net/bugs/123064
You received this bug notification becau
** Description changed:
Binary package hint: eclipse
- Eclipse 3.4.2 is now out - maybe we could see this in Karmic?
-
- [was: Eclipse 3.3/3.4/3.4.1 is out, maybe we could see this in
- Gutsy/Intrepid/Jaunty?]
+ Eclipse 3.4.2 is now out
--
Upgrade to Eclipse 3.4.2
https://bugs.launchpad.ne
** Description changed:
Binary package hint: eclipse
- Eclipse 3.4.2 is now out - maybe we could see this in Jaunty?
+ Eclipse 3.4.2 is now out - maybe we could see this in Karmic?
[was: Eclipse 3.3/3.4/3.4.1 is out, maybe we could see this in
- Gutsy/Intrepid?]
+ Gutsy/Intrepid/Jaunty?]
I actually really like the example packages in the PPA from ~yogarine,
quite an interesting idea to package in this way
--
Upgrade to Eclipse 3.4.2
https://bugs.launchpad.net/bugs/123064
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Glad to see this is being proposed as blueprint foundations-karmic-
eclipse-update for karmic
https://blueprints.launchpad.net/ubuntu/+spec/foundations-karmic-
eclipse-update
--
Upgrade to Eclipse 3.4.2
https://bugs.launchpad.net/bugs/123064
You received this bug notification because you are a m
@Sergiy Zuban:
No there are no technical limitations to having mixed system-wide eclipse
updated through apt and local plugins installed through Eclipse's Update
Manager.
I have done lots of test with the packages in my PPA and in all cases
things just work perfectly. The approach I took was to
Caesar wrote:
> do you expect apt to be more reliable in installing eclipse and its
> numerous plugins than eclipse itself?
>
> When I need my workspace on the clean machine I simply unpack my eclipse
> installation with all its plugins. It is easier than installing
> everything with apt and it is
Fwiw:
1) The statement that eclipse doesn't need packaging and it is trivial
to install standalone is imho *a joke*.
The fact is, eclipse *does* have dependencies on other stuff that is
installed via the package system
(by far the most painful of which is, of course, mozilla/xulrunner).
Packaging
are there some technical issues that doesn't allow to install core of
eclipse via apt (and keep it updated when new releases of eclipse
occurs) and let the end user to install plugins via eclipse's build-in
mechanisms? I don't understand why you are packaging let's say perl +
tons of modules (the s
I made my own packages of Eclipse and a bunch of plugins using the
release tarballs from eclipse.org:
https://edge.launchpad.net/~yogarine/+archive/ppa
I did this because from my experience installing Eclipse and then
installing all the plugins you want is always a big hassle that can
take up a wh
do you expect apt to be more reliable in installing eclipse and its
numerous plugins than eclipse itself?
When I need my workspace on the clean machine I simply unpack my eclipse
installation with all its plugins. It is easier than installing
everything with apt and it is easier than fresh eclipse
Caesar, that's really dangerous thinking there. Those same arguments could
be levelled against lots of other mature apps that have their own
ecosystems... Surely you wouldn't suggest not packaging (for example)
Firefox?
We use packages for a good reason: it keeps things sturdy and constant
between
Somebody's working on it: https://launchpad.net/~eclipse-team/+archive/ppa
One could say that it isn't difficult to install eclipse manually, but imho
it's bad
school of thought: one could say that about 70% of software.
On Fri, Apr 17, 2009 at 3:29 PM, Oli wrote:
> We're quickly approaching two
Well... IMHO, the "own internal update, plugin installation and
dependency resolving system" is not that reliable. I cannot count the
number of problems and workarounds I had trying to install several
plugins with different (and incompatible) dependencies. It's so painful
that most plugin editors a
Oli, I think the reason this will never be done is really simple: not
having elcipse package is not a problem.
At all.
It's really easy to install eclipse manually, It have it's own internal
update, plugins installation and dependency resolving system. Same time,
any "external" update and plugins
We're quickly approaching two years since this bug was launched, many
people have said things but nothing has come from it to get a proper
package-build-process started. Considering how many developers use
Eclipse (for so many different things), I would have put money on this
being fixed 18 months
** Summary changed:
- Upgrade to Eclipse 3.4.1
+ Upgrade to Eclipse 3.4.2
** Description changed:
Binary package hint: eclipse
- Eclipse 3.4.1 is now out - maybe we could see this in Jaunty?
+ Eclipse 3.4.2 is now out - maybe we could see this in Jaunty?
- [was: Eclipse 3.3/3.4 is out, m
29 matches
Mail list logo
