Hi Werner,

I created that defect and attached the requested files, schema, source
and stacktraces

The jira number is CASTOR-2329, I didn't link it to 1948, there was no
link option in the operations menu for me

Thanks,
Alex.

-----Original Message-----
From: Werner Guttmann [mailto:[EMAIL PROTECTED] 
Sent: 11 April 2008 09:16
To: [email protected]
Subject: Re: [castor-user] castor 1.2.1 release date?

Okay, I think I have got an idea what the problem is .. ;-(. It's - of 
course - related to the fact that the facets allowed on the member 
descriptor generated need to cater for int values as well (and not just 
long values).

Can I please ask you to create a new Jira issue (and maybe link it to 
CASTOR-1948). And please attach a complete (albeit minimal) XML schema, 
the stack traces and the classes as generated with 0.9.4.3.

Thanks in advance
Wenrer

Alex Herriott wrote:
> Hi Werner,
> 
> I tried the new snapshot build, Unfortunately I am getting an
exception
> which seems to be related to Castor-1948
> 
> The exception I am seeing using version 1.2.1 is different from the
> exception thrown by version 1.2, however both exceptions seem to be as
a
> result of the same problem.
> 
> The source for the xml I am trying to unmarshal was generated using
> 0.9.4.3, I have attached the two exceptions and also the xsd of the
> field that seems to be causing the problem
> 
> Thanks,
> Alex.
> 
> -----Original Message-----
> From: Werner Guttmann [mailto:[EMAIL PROTECTED] 
> Sent: 10 April 2008 11:58
> To: [email protected]
> Subject: Re: [castor-user] castor 1.2.1 release date?
> 
> Which is what I'd expect, given that we have moved all core XML 
> functionality from 1.2.1 and above to a new xml module.
> 
> In other words, please have a look at
> 
>
http://snapshots.repository.codehaus.org/org/codehaus/castor/castor-xml/
> 1.2.1-SNAPSHOT/
> 
> for the remaining module.
> 
> I hope this helps.
> 
> Regards
> Werner
> 
> Alex Herriott wrote:
>> Hi Werner,
>>
>> Just getting that snapshot release now, I have downloaded some of the
>> jars such as codegen, xml-schema etc but there is no jar for castor
>> 1.2.1 in the following location:
>>
>
http://snapshots.repository.codehaus.org/org/codehaus/castor/castor/1.2.
>> 1-SNAPSHOT/
>> Where do I get the castor-1.2.1 .jar?
>>
>> Thanks again,
>> Alex.
>>
>>
>>
>> -----Original Message-----
>> From: Werner Guttmann [mailto:[EMAIL PROTECTED] 
>> Sent: 10 April 2008 10:05
>> To: [email protected]
>> Subject: Re: [castor-user] castor 1.2.1 release date?
>>
>> Just pushed out the announcement as discussed.
>>
>> Werner
>>
>> Werner Guttmann wrote:
>>> Alex Herriott wrote:
>>>> Hi Werner,
>>>>
>>>> Thanks for the quick responses,
>>>>
>>>> Could we go ahead with a snapshot release then,
>>> Yes, can do.
>>>
>>>> Will you send the link to this mailing list once it is built?
>>> Yes, I will push out a short email once a snapshot release has been 
>>> deployed.
>>>
>>>> Thanks again,
>>>> Alex.
>>>>
>>>> -----Original Message-----
>>>> From: Werner Guttmann [mailto:[EMAIL PROTECTED] Sent: 09
> April
>>>> 2008 15:22
>>>> To: [email protected]
>>>> Subject: Re: [castor-user] castor 1.2.1 release date?
>>>>
>>>> Alex
>>>>
>>>> Alex Herriott wrote:
>>>>> Hi Werner,
>>>>>
>>>>> A snapshot release would be useful to get us by the issue we are
>>>> facing
>>>>> at the moment. It would keep us going until the official release
of
>>>>> 1.2.1
>>>>>
>>>>> When you say manage as properly as a golden one, what does that
>>>> include?
>>>> No difference to the main ones, in terms of testing. We have an 
>>>> integraztion test suite that we use before committing any code. As
>> such,
>>>> no negative side effects if an area of functionality is completely 
>>>> covered by the test suite. But please do not expect 100% coverage
..
>>>> ;-).
>>>>
>>>>> Is it a supported release? 
>>>> Yes, an no. We will support it, in that we reply to questions and
>> accept
>>>> Jira issues. But there's gotta be a difference in what we offer (in

>>>> terms of commitment and time). As always, a snapshot release is a 
>>>> snapshot of the current code base. Tested, yes. But it could be
that
> 
>>>> things will change until we make a release. Not very frequently,
and
> 
>>>> hopefully not on the public interfaces, but we are dealing with
bugs
> 
>>>> that break old contracts, etc.
>>>>
>>>> To what level will it be tested?
>>>> See above.
>>>>
>>>>> When could this release be available? 
>>>> Within one or two days. It's for myself (or any committer) just a 
>>>> mattr of building it and deploying it to the Maven snapshot repo.
>>>>> How do I get a snapshot release
>>>>> from maven snapshot repository?
>>>> If you don't use Maven, simply download the JARs using HTTP.
>>>>
>>>>> Thanks,
>>>>> Alex.
>>>>>
>>>>> -----Original Message-----
>>>>> From: Werner Guttmann [mailto:[EMAIL PROTECTED] Sent: 09
>> April 
>>>>> 2008 13:07
>>>>> To: [email protected]
>>>>> Subject: Re: [castor-user] castor 1.2.1 release date?
>>>>>
>>>>> Hi,
>>>>>
>>>>> not 100% sure, but looking at the number of open issues in Jira, I

>>>>> reckon this will be away a few weeks of time.
>>>>>
>>>>> Having said that, I do acknowledge that there's some interesting
>> bugs 
>>>>> that have been fixed since 1.2 has been made available, and that
an
> 
>>>>> early 1.2.1 release might make sense.
>>>>>
>>>>> Question: would you be happy to leave with a snapshot release,
i.e.
>> a 
>>>>> release that we manage as properly as a golden one, but that is
> only
>>>>> made available through the Maven snapshot repository of the
> Codehaus
>> ?
>>>>> If that's an option to you, that could be made available easily.
>>>>>
>>>>> Regards
>>>>> Werner
>>>>>
>>>>> Alex Herriott wrote:
>>>>>> Hi,
>>>>>>
>>>>>>  
>>>>>>
>>>>>> Can you tell me when castor 1.2.1 is due for release? If you
don't
>>>>> have
>>>>>> an exact date, could you give me a rough estimate please
>>>>>>
>>>>>>  
>>>>>>
>>>>>> There is a bug fix (CASTOR-1948) in this release which is
> affecting
>>>> us
>>>>>> at present
>>>>>>
>>>>>>  
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Alex.
>>>>>>
>> ---------------------------------------------------------------------
>>>>> To unsubscribe from this list, please visit:
>>>>>
>>>>>     http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>>
>>>>>
>> ---------------------------------------------------------------------
>>>>> To unsubscribe from this list, please visit:
>>>>>
>>>>>     http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>>
>>>>
> ---------------------------------------------------------------------
>>>> To unsubscribe from this list, please visit:
>>>>
>>>>     http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>>
> ---------------------------------------------------------------------
>>>> To unsubscribe from this list, please visit:
>>>>
>>>>     http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>
---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
>     http://xircles.codehaus.org/manage_email
> 
> 
> 
> 
>
------------------------------------------------------------------------
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
>     http://xircles.codehaus.org/manage_email


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to