Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-wtp-dev] m2e-wtp API status

Hi Fred.

We can discuss this in today's call, but I must admit we have learned some good lessons from evolving API @ WTP.  My vote would be only changing API that is truly private to "internal".
If any package has a possibility of becoming API, you can leave it as is, and add Javadoc declaring it as "provisional" - and expectations are clear changes are coming.  
This will ensure in future releases, that any adopter isn't broken simply because of the namespace change.


Thanks - Chuck

Senior Architect, RAD Java EE Tools, WTP PMC Lead
IBM Software Lab - Research Triangle Park, NC




From:        Fred Bricon <fbricon@xxxxxxxxx>
To:        M2E-WTP Developers mailing list <m2e-wtp-dev@xxxxxxxxxxx>
Date:        07/20/2012 04:31 AM
Subject:        [m2e-wtp-dev] m2e-wtp API status
Sent by:        m2e-wtp-dev-bounces@xxxxxxxxxxx




Hi,

for various (good and bad) reasons, m2eclipse-wtp development in the past has not be ... perfect.
It means that, in terms of code, javadoc, <whatever>, quality, we're far from approaching the level of mature Eclipse projects.
Well, it's not complete crap either, or we wouldn't have (hundred of?) thousands users happily hacking their javaee apps with it.

Anyway, after reading  http://wiki.eclipse.org/Eclipse_Quality I feel that, given we're about to release a new m2e-wtp Milestone, I can't commit to 
providing stable APIs for 3rd party adopters to build upon. That means I'm seriously thinking about taking some drastic measures : 
move *all* code from public to *.internal.* packages, until we can determine what would make sense to provide good API for client consumption.

Currently, the only classes that I believe could be made publicly available are :

org.eclipse.m2e.wtp.overlay.modulecore.IOverlayVirtualComponent : virtual component used to mimic Maven's war overlays
org.eclipse.m2e.wtp.overlay.modulecore.OverlayComponentCore : overlay component factory

So, if you're an adopter and use or plan to use m2e-wtp's API, it's time to speak up and make your demands. 
We can and will discuss the matter on today's call.

Regards,

Fred Bricon

--
"Have you tried turning it off and on again" - The IT Crowd
_______________________________________________
m2e-wtp-dev mailing list
m2e-wtp-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev


Back to the top