|
|
|
| Re: Forced update to Neon: Are you serious? [message #1736015 is a reply to message #1735990] |
Fri, 24 June 2016 12:30  |
 Ed Merks
Messages: 33137
Registered: July 2009 |
Senior Member |
|
|
Christian,
Comments below.
On 24.06.2016 04:36, Christian Fuss wrote:
> The Oomph installer forces an update to Neon and updates many other
> plugins without notice and without any chance to deactivate this. On
> every restart it is switching back to Neon.
As you noticed and Abel pointed out, there are two moving-product
version choices available: Latest and Latest Released. The former
tracks the latest development stream and will become Oxygen when the
first milestone for that becomes available. The later tracks releases
and just became Neon. But there are also versions for Neon, Mars, and
so on that will remain on that release forever. You can use Navigate ->
Open Setup -> Installation and use the properties view to change the
Product Version choice. You could even choose the Self product which
would never update your installation.
>
> I am a professional developer and I need some specific setups, so that
> I have good reasons to stick with Mars and Xtext 2.8.4, and decide on
> my own when I want to switch to Neon, but this is not possible with
> Oomph.
Certainly it is possible. It's your choice and you always have complete
control of that choice.
>
> Obviously, the Oomph installer is just for play-around coders.
What does that mean? It's used by serious developers who want to
completely automate the setups of their development environments and by
novices who need extra help to ensure that everything is configured
correctly (so no unzipping and now worries about the JVM not functioning).
> Dear Oomph committers, I always looked up to you and thought you were
> adorable pros, but this is ridiculous. Such a behaviour costs me hours
> to setup a new installation and is suicide for such a promising project.
Why haven't you completely automated the specific setup you need? It
should take 2-3 minutes to replicate and installation you've already
installed before.
> I am very sorry (and angry).
As an example, I always install vi into every installation so in my
user.setup I have this in my user.setup:
<?xml version="1.0" encoding="UTF-8"?>
<setup.p2:P2Task
xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:setup.p2="http://www.eclipse.org/oomph/setup/p2/1.0"
label="VI">
<requirement
name="com.mbartl.viplugin.eclipse.feature.group"
optional="true"/>
<repository
url="http://viplugin.com"/>
</setup.p2:P2Task>
So I don't have to do anything to ensure that each installation has that
installed.
You could automate your specific setup needs in this same way.
>
> Good bye Oomph!
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.01764 seconds
] 
Search
Help
Register
Login
Home
