|
|
|
|
| Re: AIO/Ultimate/Whatever Build [message #1736021 is a reply to message #1736018] |
Fri, 24 June 2016 12:46  |
 Ed Merks
Messages: 31553
Registered: July 2009 |
Senior Member |
|
|
We've talked about add an additional page that's essentially a shopping
list of additional things one can install. There are also .p2f files
for capturing what you want to install and Oomph has p2 tasks to
automatically install things. For example I have this in my user.setup
to always install vi.
<?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>
With Oomph anyone can design their own package that has exactly what
they want in it.
In the end, deciding what should all be in an installation is up to the
user and there are a number of ways to make this relatively easy with
..p2f files or with Oomph...
On 24.06.2016 08:36, Eric Rizzo wrote:
> For what purpose? I think such an installation wouldn't be
> particularly useful given the UI clutter it would probably result in.
> The packages are a mature concept that is designed specifically to
> group likely-used features together. And it's almost trivial to add
> what you need.
> I just don't see the purpose, and obviously neither does the EPP
> (Eclipse Packaging Project) or Oomph, as neither of them offer such an
> option.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.02842 seconds
Search
Help
Register
Login
Home
