You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jason Dillon (JIRA)" <ji...@apache.org> on 2007/01/11 19:41:27 UTC
[jira] Created: (GERONIMO-2725) Remove geronimo-qname_1.1_spec
usage
Remove geronimo-qname_1.1_spec usage
-------------------------------------
Key: GERONIMO-2725
URL: https://issues.apache.org/jira/browse/GERONIMO-2725
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Affects Versions: 2.0-M1
Reporter: Jason Dillon
Assigned To: Jason Dillon
Fix For: 2.0-M2
Do not need the geronimo-qname_1.1_spec anymore since it is included in the standard edition 5, which is now required to run Geronimo.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Created: (GERONIMO-2725) Remove geronimo-qname_1.1_spec usage
Posted by Jason Dillon <ja...@planet57.com>.
I think that if users need to retrotranslate/weave they can add that
jar, but since the default users will be required to use java 5, then
the default assembly should not include bits it does not need.
The edge cases may need to make a few changes to the assembly to get
it to work, but it should still be possible.
--jason
On Jan 12, 2007, at 3:31 AM, Alan D. Cabrera wrote:
> I think that we still need this. I didn't mind the move to JDK15
> because users could always use retroweaver for earlier JDKs. We
> still need this version of the spec for just such an occasion.
>
> In any case, the retirement of the a previously supported spec
> needs a little more time on the dev list than a three hour window.
>
>
> Regards,
> Alan
>
> On Jan 11, 2007, at 10:41 AM, Jason Dillon (JIRA) wrote:
>
>> Remove geronimo-qname_1.1_spec usage
>> -------------------------------------
>>
>> Key: GERONIMO-2725
>> URL: https://issues.apache.org/jira/browse/
>> GERONIMO-2725
>> Project: Geronimo
>> Issue Type: Improvement
>> Security Level: public (Regular issues)
>> Affects Versions: 2.0-M1
>> Reporter: Jason Dillon
>> Assigned To: Jason Dillon
>> Fix For: 2.0-M2
>>
>>
>> Do not need the geronimo-qname_1.1_spec anymore since it is
>> included in the standard edition 5, which is now required to run
>> Geronimo.
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> If you think it was sent incorrectly contact one of the
>> administrators: https://issues.apache.org/jira/secure/
>> Administrators.jspa
>> -
>> For more information on JIRA, see: http://www.atlassian.com/
>> software/jira
>>
>>
>>
>
Re: [jira] Created: (GERONIMO-2725) Remove geronimo-qname_1.1_spec usage
Posted by anita kulshreshtha <a_...@yahoo.com>.
Java 5 SE runtime is a prerequisite for servlet 2.5 containers and
hence for jee 5 and G 2.0. The users can not expect to run jee 5 on
java 1.4. Please see an earlier discussion -
http://www.nabble.com/Make-trunk-1.5-only%21-p7561513.html
Thanks
Anita
--- Jason Dillon <ja...@planet57.com> wrote:
> On Jan 12, 2007, at 8:53 AM, Kevan Miller wrote:
> > On Jan 12, 2007, at 3:31 AM, Alan D. Cabrera wrote:
> >
> >> I think that we still need this. I didn't mind the move to JDK15
>
> >> because users could always use retroweaver for earlier JDKs. We
> >> still need this version of the spec for just such an occasion.
> >
> > Interesting. I certainly hadn't been thinking along these lines.
> > When I last looked at Retroweaver it would provide most Java 5
> > language features, but not Java 5 SE runtime features. So, taken to
>
> > a logical conclusion, we'd be saying that G 2.0 cannot be dependent
>
> > upon any Java 5 SE unique runtime features (e.g. xml extensions,
> > jmx, concurrency, ...). I'm pretty to commit to any backward
> > compatibility for our J2EE assembly...
>
> I think we should be able to rely on the Java 5 SE features... since
>
> most users will be running in that environment, that is the
> supported/
> required JVM level for 2.0.
>
> Users can *probably* get Java 1.4 to work, but its not gonna be
> working out of the box.
>
> --jason
>
>
>
>
____________________________________________________________________________________
Sucker-punch spam with award-winning protection.
Try the free Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/features_spam.html
Re: [jira] Created: (GERONIMO-2725) Remove geronimo-qname_1.1_spec usage
Posted by Jason Dillon <ja...@planet57.com>.
On Jan 12, 2007, at 8:53 AM, Kevan Miller wrote:
> On Jan 12, 2007, at 3:31 AM, Alan D. Cabrera wrote:
>
>> I think that we still need this. I didn't mind the move to JDK15
>> because users could always use retroweaver for earlier JDKs. We
>> still need this version of the spec for just such an occasion.
>
> Interesting. I certainly hadn't been thinking along these lines.
> When I last looked at Retroweaver it would provide most Java 5
> language features, but not Java 5 SE runtime features. So, taken to
> a logical conclusion, we'd be saying that G 2.0 cannot be dependent
> upon any Java 5 SE unique runtime features (e.g. xml extensions,
> jmx, concurrency, ...). I'm pretty to commit to any backward
> compatibility for our J2EE assembly...
I think we should be able to rely on the Java 5 SE features... since
most users will be running in that environment, that is the supported/
required JVM level for 2.0.
Users can *probably* get Java 1.4 to work, but its not gonna be
working out of the box.
--jason
Re: [jira] Created: (GERONIMO-2725) Remove geronimo-qname_1.1_spec usage
Posted by Kevan Miller <ke...@gmail.com>.
On Jan 12, 2007, at 3:31 AM, Alan D. Cabrera wrote:
> I think that we still need this. I didn't mind the move to JDK15
> because users could always use retroweaver for earlier JDKs. We
> still need this version of the spec for just such an occasion.
Interesting. I certainly hadn't been thinking along these lines. When
I last looked at Retroweaver it would provide most Java 5 language
features, but not Java 5 SE runtime features. So, taken to a logical
conclusion, we'd be saying that G 2.0 cannot be dependent upon any
Java 5 SE unique runtime features (e.g. xml extensions, jmx,
concurrency, ...). I'm pretty to commit to any backward compatibility
for our J2EE assembly...
>
> In any case, the retirement of the a previously supported spec
> needs a little more time on the dev list than a three hour window.
The spec hasn't been retired, it's no longer included in our modules/
assembly. I think that's inline with a CTR process...
--kevan
Re: [jira] Created: (GERONIMO-2725) Remove geronimo-qname_1.1_spec usage
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
I think that we still need this. I didn't mind the move to JDK15
because users could always use retroweaver for earlier JDKs. We
still need this version of the spec for just such an occasion.
In any case, the retirement of the a previously supported spec needs
a little more time on the dev list than a three hour window.
Regards,
Alan
On Jan 11, 2007, at 10:41 AM, Jason Dillon (JIRA) wrote:
> Remove geronimo-qname_1.1_spec usage
> -------------------------------------
>
> Key: GERONIMO-2725
> URL: https://issues.apache.org/jira/browse/
> GERONIMO-2725
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public (Regular issues)
> Affects Versions: 2.0-M1
> Reporter: Jason Dillon
> Assigned To: Jason Dillon
> Fix For: 2.0-M2
>
>
> Do not need the geronimo-qname_1.1_spec anymore since it is
> included in the standard edition 5, which is now required to run
> Geronimo.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the
> administrators: https://issues.apache.org/jira/secure/
> Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/
> software/jira
>
>
>
[jira] Closed: (GERONIMO-2725) Remove geronimo-qname_1.1_spec usage
Posted by "Jason Dillon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Dillon closed GERONIMO-2725.
----------------------------------
Resolution: Fixed
> Remove geronimo-qname_1.1_spec usage
> -------------------------------------
>
> Key: GERONIMO-2725
> URL: https://issues.apache.org/jira/browse/GERONIMO-2725
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Affects Versions: 2.0-M1
> Reporter: Jason Dillon
> Assigned To: Jason Dillon
> Fix For: 2.0-M2
>
>
> Do not need the geronimo-qname_1.1_spec anymore since it is included in the standard edition 5, which is now required to run Geronimo.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira