|
|
|
| Re: command line [message #1720216 is a reply to message #1719887] |
Fri, 15 January 2016 09:41   |
 Ed Merks
Messages: 33137
Registered: July 2009 |
Senior Member |
|
|
Paweł,
That's a lot of stuff you want. The general theme seems to be to be
able to "script" many (all) of the actions done in the UI, e.g.,
additions to catalogs, selections of product versions and project
streams, and entry of values for variables. You could open a bugzilla
for that topic. Of course it's open source, so there's no guarantee
that anything will get done unless you do it yourself or you fund the
effort to do it.
On 12/01/2016 11:04 PM, Pawel Okas wrote:
> Hi,
>
> I'm also interested in passing some parameters by command line to
> eclipse installer.
> If you can add these features:
> - set default installation directory
> - flag that will disallow change installation directory by user
> - command that will add own *.setup file to user defined products or
> projects catalog
> - command that will run installation of specified product
> - ability to set product/project variable
> less important but also useful:
> - command that will force update of eclipse installer
> - command that will force storage eclipse installer in permanent
> location.
>
> I think these features can be very useful and can extend oomph
> installer functionality.
>
> If you implement these features its usage can look like these:
> eclipse.exe -add=myProduct.setup -add=myProject -installProd=myProduct
> -installProj=myProject -dir=C:\myFolder -dirNoChange
>
> calling these command should run eclipse installer and add myProduct
> and myProject to user defined catalogs. In next step it should run
> instalation of myProduct so page with product selection shouldn't be
> shown. If project installation is specified also page with project
> selection shouldn't be shown. myProduct should be installed in
> C:/myFolder and changing these directory by user is disabled.
> These command won't run installer in silent mode so all other pages
> like licence approval or installation progress should be visible.
>
> Example of eclipse installer command usage on windows :
> eclipse-inst.exe -install=<Directory> -update
> these will force storage of eclipse installer in permanent directory.
> If <Directory> parameter is not specified installer should ask user
> for these directory. After installation installer should try to update
> to newest version.
>
> Regards,
> Paweł
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: command line [message #1721842 is a reply to message #1720216] |
Mon, 01 February 2016 00:16 |
Duane Nielsen
Messages: 4
Registered: January 2016 |
Junior Member |
|
|
Just a note to follow on from this...
I have a use case where I want to setup eclipse to company standard for a bunch of field consultants all around the globe. The idea being that a pre-configured environment will save them a bunch of time.
I've got the setup file working. The next question is how to ship it out to a bunch of very busy people that continue to do things their way if I don't make things as easy as possible for them.
What I need is a process that is... go to this web page, download a file, execute it, and "WHAMO" development environment ready to go.
I thought setting up a catalog might be the answer to this, but after a couple days tangling with it, it's just not getting there, and it looks like there might be fundamental problems with it. (such as it requiring you to modify the oomph.ini file, which will get wiped on oomph update, or requiring the user to enter a long complex argument into the vm args manually).
A far simpler approach is to simply ship the setup file and have them add it to user products then run it. However this still adds an extra step of them needing to add it to the installer. Which is acceptable, but not perfect.
Anyway, long story short, I'm +1 for these two features. This would allow me to create a batch file/ shell script, that would install on mac or PC, with a single download and execution.
- command that will add own *.setup file to user defined products or projects catalog
- command that will run installation of specified product
Thanks again for the work the community has put into this product. Oomph has the potential to save the world millions of hours of IDE setup time.
|
|
|
| Re: command line [message #1722109 is a reply to message #1721842] |
Tue, 02 February 2016 18:57 |
Alexander Nittka
Messages: 1193
Registered: July 2009 |
Senior Member |
|
|
Duane Nielsen wrote on Mon, 01 February 2016 01:16Just a note to follow on from this...
...
I've got the setup file working. The next question is how to ship it out to a bunch of very busy people that continue to do things their way if I don't make things as easy as possible for them.
What I need is a process that is... go to this web page, download a file, execute it, and "WHAMO" development environment ready to go.
I thought setting up a catalog might be the answer to this, but after a couple days tangling with it, it's just not getting there, and it looks like there might be fundamental problems with it. (such as it requiring you to modify the oomph.ini file, which will get wiped on oomph update, or requiring the user to enter a long complex argument into the vm args manually).
...
Are you sure that the oomph.ini file gets lost if you update the installer using its internal update mechanism? I have never had that problem.
Can't you simply provide the "decompressed" version of the installer with the oomph.ini already modified, redirecting the index (or using the relatively new redirectable.projects.setup, a hook for adding a project catalog rather than shipping the entire index or replacing an existing one).
I advise against shipping a project setup as file (or catalogs). Once it is out there, you will have no chance to make sure it will be updated. Make the file available in a central location (file server, web). That way, you can update the setup there and changes are distributed automatically - without the users having to do anything.
Need training, onsite consulting or any other kind of help for Xtext?
Go visit http://xtext.itemis.com or send a mail to xtext@itemis.de
|
|
|
Powered by
FUDForum. Page generated in 0.03605 seconds
] 
Search
Help
Register
Login
Home
