Yes, I, or someone else on my team, will definitely work on producing a standalone test case. Fortunately or unfortunately, I managed to develop a workaround for the problem in v0.9.6 that made me want to try to upgrade, and I have two deadlines this week, so I can't make the test case high priority.
> -----Original Message----- > From: Kuns, Edward [mailto:[EMAIL PROTECTED] > Sent: Monday, January 15, 2007 9:23 AM > To: [email protected] > Subject: RE: [castor-user] Upgrade from v0.9.6 to v1.0.5 > unearths "cannot override unmarshal" errors that were > supposed to be fixed in v1.0.4 > > From: Karr, David [mailto:[EMAIL PROTECTED] > > So, I figured I would try upgrading to v1.0.5, the latest stable > release. > > > > I regenerated all of my code and compiled everything, and now I see > that > > some other generated code is getting compile errors like "cannot > override > > unmarshal". > > As Werner said, please do create a Jira issue with enough > information that we can reproduce this. If we have a test > case that reproduces this, then we can create a test for our > test suite which will guarantee that the fix stays fixed. > > Generally speaking, regressions get higher priority than the > "It's always been broken this way" bugs. > > If you have the opportunity to test with 1.1 M2, it would be > appreciated. But in any case please do create a Jira issue > with a schema and any properties files we need so we can > reproduce this. > > Eddie > > --------------------------------------------------------------------- > 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
