karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Freeman Fang <freeman.f...@gmail.com>
Subject Re: Another issue with 2.2.4....
Date Thu, 13 Oct 2011 04:12:16 GMT
I agree that this isn't a blocker issue, add it into the release-notes  
should be ok.

Freeman
On 2011-10-13, at 上午9:04, mikevan wrote:

>
> I agree that this isn't a blocker.  That said, we should make it  
> very clear
> that this exists for folks who want to use JDK 1.5 and this feature.
>
>
>
> jgoodyear wrote:
>>
>> Considering this issue has been present in 2.2.1, 2.2.2, and 2.2.3, I
>> think 2.2.4 can go ahead with the release note.
>>
>> Cheers,
>> Jamie
>>
>> On Wed, Oct 12, 2011 at 6:16 PM, Achim Nierbeck &lt;bcanhome@&gt;  
>> wrote:
>>> I could live with it like you said, only the web part is java6  
>>> dependent.
>>>
>>> regards, Achim
>>>
>>> 2011/10/12 Jean-Baptiste Onofré &lt;jb@&gt;
>>>
>>>> Thanks Dan.
>>>>
>>>> FYI, this issue is present in Karaf 2.2.3, 2.2.2, 2.2.1.
>>>>
>>>> The only "correct" version is Karaf 2.2.0 which use Pax Web 1.0.1.
>>>>
>>>> So it's an "old" issue :/
>>>>
>>>> As Dan said, I will take a look tomorrow morning (and eventually  
>>>> release
>>>> a
>>>> new version of Pax Web).
>>>>
>>>> If it takes time to fix that, or if the impact is too important,  
>>>> I would
>>>> just release note that war feature is Java 6 compliant only and  
>>>> release
>>>> Karaf 2.2.4 as it is.
>>>>
>>>> Regards
>>>> JB
>>>>
>>>>
>>>> On 10/12/2011 10:35 PM, Daniel Kulp wrote:
>>>>
>>>>>
>>>>> While doing some testing with 2.2.4-SNAPSHOT, I ran into another  
>>>>> issue.
>>>>>  The
>>>>> "war" feature no longer supports Java 5.  You cannot install the
>>>>> feature
>>>>> due
>>>>> to pax-web-jsp pulling in classes only available in Java6.      
>>>>> Since
>>>>> 2.2.x
>>>>> is
>>>>> supposed to support Java5, this is an issue for me.
>>>>>
>>>>> https://issues.apache.org/**jira/browse/KARAF-933&lt;https://issues.apache.org/jira/browse/KARAF-933&gt

>>>>> ;
>>>>>
>>>>>
>>>>> JB is going to look a bit at pax-web tomorrow morning to see if  
>>>>> there
>>>>> is
>>>>> anything that can be done.   If not, we may need to do something  
>>>>> like:
>>>>>
>>>>> 1) release note that war is Java6 only.    (btw: this issue  
>>>>> exists in
>>>>> 2.2.3 as
>>>>> well)
>>>>>
>>>>> 2) Remove jsp from the war feature and maybe add a "war-jsp"  
>>>>> feature
>>>>> that
>>>>> would include it.  (or something similar)
>>>>>
>>>>> 3) Rollback to pax-web-jsp 1.0.1 (last version that doesn't have  
>>>>> the
>>>>> problem)
>>>>>
>>>>> 4)  others?
>>>>>
>>>>>
>>>>> Anyway, at this point, I'd like to wait and see what JB finds out.
>>>>>
>>>>>
>>>>>
>>>> --
>>>> Jean-Baptiste Onofré
>>>> jbonofre@
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>
>>>
>>>
>>> --
>>> --
>>> *Achim Nierbeck*
>>>
>>>
>>> Apache Karaf &lt;http://karaf.apache.org/&gt; Committer & PMC
>>> OPS4J Pax Web &lt;http://wiki.ops4j.org/display/paxweb/Pax+Web/&gt;
>>>  Committer &
>>> Project Lead
>>> blog &lt;http://notizblog.nierbeck.de/&gt;
>>>
>>
>
>
> -----
> Mike Van
> Mike Van's Open Source Technologies Blog
> --
> View this message in context: http://karaf.922171.n3.nabble.com/Another-issue-with-2-2-4-tp3416845p3417417.html
> Sent from the Karaf - Dev mailing list archive at Nabble.com.

---------------------------------------------
Freeman Fang

FuseSource
Email:ffang@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com










Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message