|
| Re: Help needed in how to get started with Oomph [message #1751589 is a reply to message #1751586] |
Wed, 11 January 2017 17:21   |
 Ed Merks
Messages: 33264
Registered: July 2009 |
Senior Member |
|
|
Assuming what you have for source code control support a project set file, you could use a project set file to import the projects. But it sounds like you're mostly focused on purely an installation, not on getting something into the workspace.
I've been doing some prototyping on product extensions, but yes, if you want to define purely a product, copying a base product and adding to it makes sense. You might want to keep your p2 task separate from the one you copy in case you want to copy it again later. The two p2 tasks will be merged automatically.
If you have your product setup open, you can use the toolbar button to record preferences into that setup. Yes it is possible in a product setup. A project setup is useful if you also want to provision the workspace with content. E.g., you might import a project set file that imports the projects from the source code repository (assuming that Accurev supports that). You can store the setup anywhere you like but of course you want it to be accessible to all the clients, so at some http accessible location would be ideal.
What's special about a project setup is that there is a workspace task (generally in the project catalog), and that ensures that the installation is launched with a specific workspace that's created during installation. It also makes the workspace.location variable available to define tasks that apply to the workspace location. (If you look at other threads though, you can access this location via the OSGi variable for it; I'd have to find the thread and it's late now for me)...
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Help needed in how to get started with Oomph [message #1751593 is a reply to message #1751589] |
Wed, 11 January 2017 17:37 |
Joshua Street
Messages: 8
Registered: April 2013 |
Junior Member |
|
|
Thanks for your reply. I ended up following the text on the wiki for adding WST servers but when I installed the product, no servers showed up and there was no project for the server information created.
I think it would be nice to have a workspace and projects all setup automatically. I am not sure how importing projects through oomph and gradle will interact.
Thinking about it more, I am envisioning a user doing the following:
- Use accurev to create the local workspace area (workspace in Accurev not in Eclipse) and download the sources
- Use the eclipse installer to select either a specific product setup, or a project setup that can somehow enforce a specific eclipse version (J2EE).
- Enter the location of where the accurev workspace is when doing the install
- The eclipse installer would then install eclipse, setup a workspace with the gradle-based projects in place and setup the necessary server
I hope that makes sense and I hope I have the right thinking on this. Frankly, Accurev has a terrible plugin for eclipse so I'm not sure if its usable to have eclipse download the projects first. And there's gradle to consider...
[Updated on: Wed, 11 January 2017 17:39] Report message to a moderator |
|
|
| Re: Help needed in how to get started with Oomph [message #1751641 is a reply to message #1751593] |
Thu, 12 January 2017 07:43 |
Ed Merks
Messages: 33264
Registered: July 2009 |
Senior Member |
|
|
Note that there is relatively new support for configurations:
https://wiki.eclipse.org/Eclipse_Oomph_Authoring#Automation_and_Specialization_with_Configurations
This would let you specify a product version selection and one or more project stream selections to ensure that the combination you want to have used, is used.
Of course if you're using the Eclipse products as a basis, in your project setup you can always specify all the requirements for the things you want to have installed regardless of what might be installed because of the product version selection. The Eclipse product catalog provides the Eclipse Platform product (org.eclipse.platform.ide) which is the smallest Eclipse base against which you could install. It doesn't even provide JDT, or PDE, only the IDE with support for a workspace, e.g., the Navigator. You could test that when your project stream is selected, that even in this case, all the features you want to have installed are present.
I don't know much about Gradle, but I know the Xtext project uses Oomph and uses Gradle...
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.04337 seconds
] 
Search
Help
Register
Login
Home
