So, either the errors are corrected (by castor people working around the API changes, or by us doing the same), or the errors will be there until pluto moves to a more modern version of castor.
Very late answer, sorry
Santiago
On 9/1/06, Elliot Metsger <[EMAIL PROTECTED]> wrote:
Me neither!
I'm talking with folks on gump list to see what can be done.
Elliot
David H. DeWolf wrote:
>
> I have no idea. Unfortunately I don't know a first thing about the Gump
> configuration.
>
> Elliot Metsger wrote:
>>> [javac]
>>> /x1/gump/public/workspace/portals-pluto-1.0/portal/src/java/org/apache/pluto/portalImpl/services/portletdefinitionregistry/PortletDefinitionRegistryServiceContextImpl.java:113:
>>> exception java.io.IOException is never thrown in body of corresponding
>>> try statement
>>> [javac] } catch (IOException e) {
>>> [javac] ^
>>> [javac]
>>> /x1/gump/public/workspace/portals-pluto-1.0/portal/src/java/org/apache/pluto/portalImpl/services/portletdefinitionregistry/PortletDefinitionRegistryServiceContextImpl.java:115:
>>> exception org.exolab.castor.mapping.MappingException is never thrown
>>> in body of corresponding try statement
>>> [javac] } catch (MappingException e) {
>>> [javac] ^
>>
>> Apparently Gump is building with a version of Castor that doesn't throw
>> IOException or MappingException. Pluto 1.0.2 depends on Castor 0.9.5.3,
>> but Gump is building Pluto with Castor's trunk, which apparently doesn't
>> throw these exceptions anymore.
>>
>> Can/should we change Gump to build with 0.9.5.3?
>>
>> Elliot
>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Whack-a-mole-%3A-%29-tf2193883.html#a6092367
Sent from the Pluto - Dev forum at Nabble.com.
