Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [epp-dev] Oomph, Automated Error Reporting, and other changes for EPP Mars M5

For completeness: This is the same what Yoxos does since a few years:

  https://yoxos.eclipsesource.com/discover.html

About Mickaels comments:

- "requires" instead of "includes" - I don't think this would change the update and the removal stories.

- *very* minimal branded products: If you add additional IUs by specifying these in the pom.xml or if you do the same in a .product configuration with the new "rootfeature" syntax: In both cases the additional IUs are installed as root features into Eclipse and my expectation is that it wouldn't make a difference.

Regards,
Markus



On 22 January 2015 at 19:43, Marcel Bruch <marcel.bruch@xxxxxxxxxxxxxx> wrote:
FWIW,

Yatta is working on a public service built on top of Oomph where users can 

1. configure their own Eclipse instance in a browser (which features they would like to have in their personal Eclipse), 
2. store and share their configuration with others
3. provision is in one click with Oomph.

It’s work in progress but has been announced on several the Eclipse Demo Camps in November.


Marcel

On 22 Jan 2015, at 19:20, Mickael Istria <mistria@xxxxxxxxxx> wrote:

On 01/22/2015 06:57 PM, Mike Milinkovich wrote:
I _think_ that what Chuck meant was different than the interpretation I've seen in several responses. I am pretty that he did not mean that people use the packages as the basis for a build which their complete product. But a lot of products are made available as plug-ins which are installed on top of an existing Eclipse package. Which means that the creators of such products will do their testing on top of a specific version of one or more specific packages.
+1 on that.
When doing IDE related plugins, you definitely get much much more users by shipping them as plugins that people install on top of their favourite EPP package, than by shipping yet-another-IDE that people won't even download. The I of IDE still means integrated, having tools integrated in their IDE is what they want, not a multiplication of IDEs.

Technically, here are a few questions/comments that would provide more flexibility to users of EPP packages:
* Wouldn't using "requires" instead of "includes" in feature allow updates of sub-features without rebuild of the main one?
* Could EPP products be *very* minimal branded products with additional features installed on them with regular p2 director? Instead of being set in the .product or feature.xml, versions would be set in a pom.xml.
Note that both of them would allow many variations of the packages, so from a user to another you could get many differences (it's already the case, but it would be more) and one wouldn't be guaranteed that Package X in version x.y.z contains feature A in version a.b.c.
In general, I don't believe this is an issue if project deals correctly with dependency versioning (in their feature.xml or MANIFEST.MF), and if it becomes an issue, it's more the issue of 1 project than the issue of the EPP package. So IMO, these loosely-coupled-to-features approach is acceptable.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/epp-dev

-- 
Codetrails GmbH
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-179-131-7721
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940


_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/epp-dev



--

###
EclipseSource Group
Telefon: +49 721 664733-0 (GMT +2)
Telefax: +49 721 66473329

http://eclipsesource.com


Innoopract Informationssysteme GmbH
Lammstrasse 21, 76133 Karlsruhe Germany
General Manager: Jochen Krause
Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883

Back to the top