Difference between revisions of "WTP Readiness For CBI"

From Eclipsepedia

Jump to: navigation, search
Line 66: Line 66:
 
| [[Image:Checkmark.gif]]  
 
| [[Image:Checkmark.gif]]  
 
| [[Image:Checkmark.gif]]  
 
| [[Image:Checkmark.gif]]  
| [[Image:Questionmark.gif]]  
+
| [[Image:Checkmark.gif]]  
 
| Source features (''org.eclipse.jsf.feature.source'', ''org.eclipse.jst.jsf.apache.trinidad.tagsupport.feature.source'', ''org.eclipse.jst.webpageeditor.feature.source'') contain '''build.properties''' in CBI, where they did not in legacy build.
 
| Source features (''org.eclipse.jsf.feature.source'', ''org.eclipse.jst.jsf.apache.trinidad.tagsupport.feature.source'', ''org.eclipse.jst.webpageeditor.feature.source'') contain '''build.properties''' in CBI, where they did not in legacy build.
 
Extra plug-in in CBI: ''org.eclipse.jst.jsf.doc.user.source''.
 
Extra plug-in in CBI: ''org.eclipse.jst.jsf.doc.user.source''.

Revision as of 17:42, 14 May 2014

This wiki page captures the the readiness of WTP projects to move from PDE to CBI builds.

Instructions: Find your project in the table below and mark each task and overall readiness with either a "checkmark" or "cross". The Comment column is meant to capture differences, or overall comments in each projects analysis of build artifacts.

The Build comparison should be done using same day builds (I used 5/8 builds) This bug is driving this task

Smoketests should be done on a recent build (like 5/8) - builds are located here - I used the repository

Your vote in the below table will not trigger any immediate action. The information collected will be used for further discussions and plans on using the CBI output in the Luna aggregation builds.

Checkmark.gif = I feel comfortable moving to CBI for Luna release
Fail.gif = I don't feel comfortable moving to CBI yet - more work to be done
Questionmark.gif= Readiness status pending
Project Lead Build Comparison CBI Build Smoketest Overall Readiness Comments
Common Tools
Carl Anderson Questionmark.gif Questionmark.gif Questionmark.gif
Dali
Neil Hauge Questionmark.gif Questionmark.gif Questionmark.gif
EJB Tools
Kaloyan Raev Questionmark.gif Questionmark.gif Questionmark.gif
Java EE Tools
Chuck Bridgham Checkmark.gif Checkmark.gif Questionmark.gif Other than changes in size because of jar signing... The one major difference in CBI is the generation of xxx.userdoc.feature.source jar's - these are a waste - and should be removed, but doesn't prevent moving forward.
JavaScript Development Tools
Christopher Jaun Questionmark.gif Questionmark.gif Questionmark.gif
JavaServer Faces
Raghunathan Srinivasan Checkmark.gif Checkmark.gif Checkmark.gif Source features (org.eclipse.jsf.feature.source, org.eclipse.jst.jsf.apache.trinidad.tagsupport.feature.source, org.eclipse.jst.webpageeditor.feature.source) contain build.properties in CBI, where they did not in legacy build.

Extra plug-in in CBI: org.eclipse.jst.jsf.doc.user.source.

These should be investigated, but are not reason to prevent moving to CBI.

Release Engineering
Carl Anderson Questionmark.gif Questionmark.gif Questionmark.gif
Server Tools
Elson Yuen Questionmark.gif Questionmark.gif Questionmark.gif
Source Editing
Nick Sandonato Questionmark.gif Questionmark.gif Questionmark.gif
Web Services Tools
Keith Chong Questionmark.gif Questionmark.gif Questionmark.gif