You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shale.apache.org by "Craig McClanahan (JIRA)" <ji...@apache.org> on 2006/09/16 01:38:31 UTC
[jira] Created: (SHALE-285) Test whether shale-tiger can be
postprocessed for use on JDK 1.4 systems
Test whether shale-tiger can be postprocessed for use on JDK 1.4 systems
------------------------------------------------------------------------
Key: SHALE-285
URL: http://issues.apache.org/struts/browse/SHALE-285
Project: Shale
Issue Type: New Feature
Components: Tiger
Reporter: Craig McClanahan
Several Apache projects have started using postprocessors like RetroWeaver and RetroTranslater to take code that uses Java SE 5 syntax and semantics (including annotations) and make it work on a JDK 1.4 JVM. Analyze whether this approach will work for shale-tiger (and applications built with it), and (if so) decide whether to release it as a supported feature (or perhaps as a sandbox feature).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SHALE-285) Test whether shale-tiger can be
postprocessed for use on JDK 1.4 systems
Posted by "Craig McClanahan (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/SHALE-285?page=comments#action_38238 ]
Craig McClanahan commented on SHALE-285:
----------------------------------------
At this point, the important thing is to verify whether the resulting code actually works (the Tiger extensions rely on runtime analysis of annotations, so I'm very curious how the "retro" converters actually handle this). If it works, we'll want to ultimately use plugins for both shale-tiger itself, and for any application that wants to use these annotations but work on JDK 1.4. A good test case would be the shale-sql-browser app.
In the short term, to do this kind of testing, a command line approach would be fine.
> Test whether shale-tiger can be postprocessed for use on JDK 1.4 systems
> ------------------------------------------------------------------------
>
> Key: SHALE-285
> URL: http://issues.apache.org/struts/browse/SHALE-285
> Project: Shale
> Issue Type: New Feature
> Components: Tiger
> Reporter: Craig McClanahan
>
> Several Apache projects have started using postprocessors like RetroWeaver and RetroTranslater to take code that uses Java SE 5 syntax and semantics (including annotations) and make it work on a JDK 1.4 JVM. Analyze whether this approach will work for shale-tiger (and applications built with it), and (if so) decide whether to release it as a supported feature (or perhaps as a sandbox feature).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SHALE-285) Test whether shale-tiger can be
postprocessed for use on JDK 1.4 systems
Posted by "James Mitchell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/SHALE-285?page=comments#action_38236 ]
James Mitchell commented on SHALE-285:
--------------------------------------
Craig, do we have a preferred technique for this? ( Maven vs Command line)
With Ted's help, I added the 1.5 -> 1.4 backport to the nightly build for s2 a while ago:
http://people.apache.org/builds/struts/nightlies/2.0.x/java-1.4/
It's pretty trivial and I can help with that if we go with a command line approach first. My assumption (like with s2) is that we eventually move this process to handled by the Maven plugin.
> Test whether shale-tiger can be postprocessed for use on JDK 1.4 systems
> ------------------------------------------------------------------------
>
> Key: SHALE-285
> URL: http://issues.apache.org/struts/browse/SHALE-285
> Project: Shale
> Issue Type: New Feature
> Components: Tiger
> Reporter: Craig McClanahan
>
> Several Apache projects have started using postprocessors like RetroWeaver and RetroTranslater to take code that uses Java SE 5 syntax and semantics (including annotations) and make it work on a JDK 1.4 JVM. Analyze whether this approach will work for shale-tiger (and applications built with it), and (if so) decide whether to release it as a supported feature (or perhaps as a sandbox feature).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (SHALE-285) Test whether shale-tiger can be
postprocessed for use on JDK 1.4 systems
Posted by "Craig McClanahan (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/SHALE-285?page=all ]
Craig McClanahan resolved SHALE-285.
------------------------------------
Resolution: Not A Problem
Thanks to James Mitchell's testing during ApacheCon last week, we now have evidence that the shale-sql-browser webapp (including the shale-tiger library) can run succssfully on a JDK 1.4 system, once both have been translated. Therefore, marking this one as "not a problem", since it actually does work :-).
> Test whether shale-tiger can be postprocessed for use on JDK 1.4 systems
> ------------------------------------------------------------------------
>
> Key: SHALE-285
> URL: http://issues.apache.org/struts/browse/SHALE-285
> Project: Shale
> Issue Type: New Feature
> Components: Tiger
> Reporter: Craig McClanahan
>
> Several Apache projects have started using postprocessors like RetroWeaver and RetroTranslater to take code that uses Java SE 5 syntax and semantics (including annotations) and make it work on a JDK 1.4 JVM. Analyze whether this approach will work for shale-tiger (and applications built with it), and (if so) decide whether to release it as a supported feature (or perhaps as a sandbox feature).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira