| Help needed in how to get started with Oomph [message #1751586] |
Wed, 11 January 2017 11:58  |
Eclipse User |
|
|
|
I am having trouble understanding how I should use Oomph to help our developers maintain a working IDE for a particular web application we develop. First, some specifics about the application development setup.
We are using gradle, and our application is broken into several projects (a multi-project build). We are not on Git and use Accurev. We test locally using websphere liberty. We will, however, be eventually moving to Git.
What I think I would like to have is Oomph setting up Eclipse for J2EE developers with some additional plugins for things like code coverage, sonarqube, and Websphere Developer Tooling. I managed create a Product setup that does this (I had to copy the P2 Director node of the J2EE developer setup to get all of the requirements since I didn't see the ability to extend an existing setup). I am not sure how to apply preferences and setting up servers however since the wiki doesn't state if this is possible in a product setup.
Is the product setup the right type to use? Should I store a project setup instead in our repository for the application and do everything there? A lot of documentation seems to use project setups and not product ones.
I guess I am a little lost on this..
|
|
|
| Re: Help needed in how to get started with Oomph [message #1751589 is a reply to message #1751586] |
Wed, 11 January 2017 12:21  |
| Eclipse User |
|
|
|
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)...
|
|
|
|
| Re: Help needed in how to get started with Oomph [message #1751641 is a reply to message #1751593] |
Thu, 12 January 2017 02:43 |
| Eclipse User |
|
|
|
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...
|
|
|
Powered by
FUDForum. Page generated in 0.07459 seconds
Home