My apologies for the delay. I added the new defect. Here is the pointer:

http://team.ops4j.org/browse/PAXWEB-423

thanks again,
Gareth

On Mon, Sep 10, 2012 at 3:23 AM, Achim Nierbeck <[email protected]> wrote:
> Hi Gareth,
>
> you're probably right the export is missing, mind creating an issue for it :)
>
> About the backport, hmm this is a change worth for a minor upgrade and one
> of the reasons it's in the 3.0 line of Pax-Web. I have to think about
> it a bit more :)
>
> regards, Achim
>
> 2012/9/9 Gareth Collins <[email protected]>:
>> Hello Achim,
>>
>> If I understand the pom correctly (I don't use maven - I guess the
>> bundles are combined via the Embed-Dependency directive?), it may be
>> just that the org.ops4j.pax.web.utils export is missing from the
>> pax-web-jetty-bundle project. I only see the following
>> org.ops4j.pax.web exports defined:
>>
>>               org.ops4j.pax.web.service; version="${project.version}",
>>               org.ops4j.pax.web.service.spi; version="${project.version}",
>>               org.ops4j.pax.web.service.spi.model; 
>> version="${project.version}",
>>               org.ops4j.pax.web.service.spi.util; 
>> version="${project.version}"
>>
>> If PAXWEB-417 is fixed by PAXWEB-367, that would be great! I will give
>> it a try. I will probably be interested in backporting this fix
>> (hopefully this wasn't fixed by a major architectural change).
>>
>> thanks again,
>> Gareth
>>
>>
>> On Sat, Sep 8, 2012 at 7:43 PM, Achim Nierbeck <[email protected]> 
>> wrote:
>>> Hi Gareth,
>>>
>>> well the bundle should be included in the jetty-bundle.
>>> A first glance didn't show anything missing.
>>> Could you check what's really is missing?
>>>
>>> regarding PAXWEB-417, this should be handled with PAXWEB-367 on trunk (3.0).
>>>
>>> regards, Achim
>>>
>>>
>>> 2012/9/5 Gareth Collins <[email protected]>:
>>>> Hello Achim,
>>>>
>>>> Previously (pre-2.1 official) I could start up pax-web with just four 
>>>> bundles:
>>>>
>>>> pax-web-extender-war
>>>> pax-web-extender-whiteboard
>>>> pax-web-jetty-bundle
>>>> pax-web-jsp
>>>>
>>>> Now it appears that a fifth is required:
>>>>
>>>> pax-web-api -> to get org.ops4j.pax.web.utils (required by the jsp and
>>>> extender-war).
>>>>
>>>> Do you know if that an intentional change (e.g. it shouldn't get
>>>> bundled up with the "jetty-bundle, should it)?
>>>> Just making sure as the Pax Web 2.1.0 release notes don't provide a
>>>> link to this bundle in "Download distribution".
>>>>
>>>> BTW - I opened up a new defect:
>>>>
>>>> http://team.ops4j.org/browse/PAXWEB-417
>>>>
>>>> I can see what's wrong...but it is not obvious (at least to me) how to 
>>>> solve it.
>>>>
>>>> thanks in advance,
>>>> Gareth
>>>>
>>>> _______________________________________________
>>>> general mailing list
>>>> [email protected]
>>>> http://lists.ops4j.org/mailman/listinfo/general
>>>
>>>
>>>
>>> --
>>>
>>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>>> Committer & Project Lead
>>> OPS4J Pax for Vaadin
>>> <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project
>>> Lead
>>> blog <http://notizblog.nierbeck.de/>
>>>
>>> _______________________________________________
>>> general mailing list
>>> [email protected]
>>> http://lists.ops4j.org/mailman/listinfo/general
>>
>> _______________________________________________
>> general mailing list
>> [email protected]
>> http://lists.ops4j.org/mailman/listinfo/general
>
>
>
> --
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
> Committer & Project Lead
> OPS4J Pax for Vaadin
> <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project
> Lead
> blog <http://notizblog.nierbeck.de/>
>
> _______________________________________________
> general mailing list
> [email protected]
> http://lists.ops4j.org/mailman/listinfo/general

_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to