Framework should build on JDK 1.4

• Key: SHALE-375
• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Priority: Major
• Assignee: Rahul Akolkar
• Reporter: Rahul Akolkar
• Fix Version/s: 1.0.4

Description

'mvn -Papps install' on JDK 1.4 should result in a successful build.

Comments

[Wendy Smoak]

The build itself (not the Shale code) may require JDK 1.5. At one point the taglib plugin would not work on JDK 1.4. I'm not sure if it's been released since this was fixed.

   http://sourceforge.net/tracker/index.php?func=detail&aid=1483561&group_id=93991&atid=606303

The compiler plugin is configured to target 1.4 (except for a few modules) so it should be fine in any case.

[Rahul Akolkar]

Thanks for the feedback. The <reporting> bits are not as important from my perspective. I'm OK if the site doesn't build or the release related plugins (javadoc, source etc.) are tuned for 1.5, but I'd like to be able to locally install JDK 1.4 built binaries. This is useful since most of the app servers I can use are still pegged at 1.4 (and I'd like to build with 1.4 as such).

To give some examples to the kind of stuff I'd like to do with this ticket:
 * Remove shale-tiger from parent <modules> (seems a mistake, its already in the JDK 1.5 activated profile)
 * Conditional compile shale-test bits (shale-test depends on Java EE 5 bits, which hoses JDK 1.4 compat). I plan to drop in two JDK activated profiles so when built on 1.4 shale-test will only cater to the JSF 1.1 crowd.

I plan to finish this today, lets see.

I should add that shale-test is well-designed to gracefully fall back on JSF 1.1 bits if 1.2 is not present (just that there is no way to do a 'mvn install' using JDK 1.4 ATM, which I plan to look into now).

[Rahul Akolkar]

'mvn -Papps install' in framework trunk works on JDK 1.4 (obviously, modules/apps requiring JDK 1.5 or Java EE 5 are not built in such a scenario).