+1
I personally prefer Stable as legacy is a little negative. If they have been formally deprecated we could use Eclipse Project for Deprecated APIs Steve Eclipse Project for Stable APIs? Eclipse Project for Sustained APIs? I am also good with Legacy. Hi, We agreed on the last PMC meeting that we will move legacy components listed below to a new project. We need to decide about this project name. I am starting this thread to discuss it. - Eclipse Project for Enterprise Management
- Eclipse Project for Enterprise Deployment
- Eclipse Project for JAX-RPC
- Eclipse Project for WADL
- Eclipse Project for JAXR
I am proposing Eclipse Project for legacy APIs. WDYT? Other options?
-- Java Champion, JCP EC/EG Member, EE4J PMC, JUG Leader _______________________________________________ee4j-pmc mailing listee4j-pmc@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://dev.eclipse.org/mailman/listinfo/ee4j-pmc
--- Mark Little
JBoss, by Red Hat Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, Kinsale Road, Co. Cork. Registered in the Companies Registration Office, Parnell House, 14 Parnell Square, Dublin 1, Ireland, No.304873 Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael O'Neill, Keith Phelan, Matt Parson (USA)
|