[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[wtp-dev] Faceted Project Framework API to use Java 5 language features

PMC just approved the plan to let Faceted Project Framework use Java 5 language features for WTP 2.0 release. This e-mail details the plan of action.

 

First of all, changes to the API to use generics are fully source and binary backwards compatible with existing clients. Wherever enhancing the API to use Java 5 language features would have caused API breakage, the changes were not made. I have the changes ready locally and we will roll them out as follows:

 

1. Fix the version ranges on all of the referring plugins so that they will be able to accept the new version of the Faceted Project Framework plugins. See my previous e-mail for information regarding this. I have made the necessary changes locally on my machine and can release them unless I hear objections from plugin owners. I’d like this step to be completed as soon as possible. How about right after this week’s I-build is declared?

 

2. Once #1 is complete and we have a build ready that includes that change, I will send an e-mail to this mailing list containing the new version of the Faceted Project Framework plugins. They will be compiled and ready to drop into an existing build for testing. The interested parties at this point can try out these plugins and report any problems.

 

3. Assuming that #2 goes smoothly and any reported problems are corrected, the changes to the Faceted Project Framework will be released into the build right after M5 is declared. Then we will have all of M6 to flush out any lingering issues.

 

Questions? Comments?

 

- Konstantin

 

 

_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.