Announcements And Special Reports

Bob Fraser pointed out article in ITWorldCanada describing how a college course plans to expand their "open source course" to include WTP.

Tip of the week

When editing this wiki shortly before the meeting, please remember to edit only your specific section that is required ... preferably the "smallest" section possible. This reduces conflicts ... when I save something :)

WTP 3.1

Issues to watch moving up to M5 prereqs

Action required: change ICU pre-reqs to "span" version boundry, such as [3.8.0, 4.1.0) ... or, better yet, change to use import-packages, such as
Import-Package: com.ibm.icu.text
or
Import-Package: com.ibm.icu.text;version="3.8.1"

In general, the minimum requirement is that if you branch a plug-in, you need to branch all the plug-ins in the corresponding map file. This is to make it easier for others to know what to load, to "be current" in a maintenance branch. It is fine to branch everything in a sub-project if you choose to, but still need to correspond to what's in a map file, and the map file should be updated to explain what it's used for. Map files can be re-organized some, if that helps make it easier to organize and understand what teams are working on what.

The names for branches should follow the pattern of 'R3_0_maintenance'. This will be the name for all 3.0.x maintenance work (not just the first, 3.0.1 maintenance work). Note that JSF and JPA code may use R2_0_maintenance, but their map files, will still be branched using R3_0_maintenance.

Instructions for tagging existing and new WTP wiki pages can be found at WTP's Category page; remember, we can create subcategories as well