Eclipse Community Forums: Oomph » Extending 'Eclipse IDE for Java EE Developers' brings in fewer features than expected

Home » Eclipse Projects » Oomph » Extending 'Eclipse IDE for Java EE Developers' brings in fewer features than expected

Show: Today's Messages :: Show Polls :: Message Navigator

Extending 'Eclipse IDE for Java EE Developers' brings in fewer features than expected [message #1750220]

Sun, 18 December 2016 22:32

Robert Munteanu

Messages: 30
Registered: July 2009

Member

Hi,

I'm trying to create a simple product setup where I extend the 'Eclipse IDE for Java EE Developers ' package with some additional plug-ins.

I started by adding http://download.eclipse.org/releases/oxygen as a repository and then epp.package.jee as a requirement.

However, this seems to pull in fewer features than the ones I find in my Oxygen install downloaded from eclipse.org . A couple of notable ones that are missing:

- m2e
- mylyn bugzilla connector
- Java EE perspective missing
- code recommenders

Is there any way to include an existing EPP package without manually keeping in sync the list of features included on that package?

Thanks,

Robert

Report message to a moderator

Re: Extending 'Eclipse IDE for Java EE Developers' brings in fewer features than expected [message #1750229 is a reply to message #1750220]

Mon, 19 December 2016 07:16

Ed Merks

Messages: 33258
Registered: July 2009

Senior Member

The root package requirements, as of Neon, has far fewer transitive requirements than it did for Mars or earlier. This is by design so that features can be uninstalled from the package...

We've been prototyping a new type of scope tentatively called an Extension such that an Installation could reference a product version along with zero or more Extensions, but it will be quite some time before that's committed.

We do already have support for Configurations (and a wizard to create them). It's essentially a container for an Installation and a Workspace (both optional). With one of those having only an Installation that references a Product Version and contains a p2 task to install additional things you could reuse the existing product version and extend it. The Installation in the Configuration is used to initialize the Installation created by the installer, i.e., it will use a copy of the Configuration's Installation. A Configuration can be dragged and dropped to the installer or can be copied to the clipboard and applied to the installer. Unfortunately I'm not written the wiki page documentation for it yet. Hopefully before the new year...

Of course the requirements in the generated product catalog don't change all that often, i.e., rarely if at all, so making a copy of the p2 task in your own product version isn't a big deal...

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: Extending 'Eclipse IDE for Java EE Developers' brings in fewer features than expected [message #1750248 is a reply to message #1750229]

Mon, 19 December 2016 10:14

Robert Munteanu

Messages: 30
Registered: July 2009

Member

Hi Ed,

Indeed, I ended up duplicating the config - not a big deal, but would've liked to avoid it.

For the record, the simplest way to do this was to expand the 'index:/org.eclipse.setup' node in the editor, locate the 'P2 Director' node that contained what I needed and drag the requirements and the repositories into my own 'P2 Director' node.

Thanks,

Robert

Report message to a moderator

Previous Topic:	Can we use Oomph to share and enforce company code format?
Next Topic:	setup with git clone and project import of non-Eclipse project

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sun Dec 08 18:57:36 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter