Retrotranslator has been around for a few years AFAIK. Not sure it
will double your testing efforts... though if you wanted to run
integration tests on JDK 1.5 and 1.4 then ya, it would double those.
What additional stuff is there to check for the release? AFAIK the
jars contain the same legal bits as non-retro jars. So someone would
have to check that once, and then could forget... though there is a
goal to ensure artifacts have legal muck in them automatically, which
server is using in the default build.
Retro jars will live next to non-retro jars with a "jdk14"
classifier, everything else should be the same.
--jason
On Mar 21, 2007, at 11:38 AM, Alan D. Cabrera wrote:
> Retrotranslator is relatively new and we would only be doubling our
> testing and it's more stuff to check when we make release
> distributions. Also, how would our retro jars fit into the maven
> repository scheme of things?
>
>
> Regards,
> Alan
>
> On Mar 21, 2007, at 10:27 AM, Guillaume Nodet wrote:
>
>> Why are you both reluctant to publish retrotranslated jars ?
>>
>> On 3/21/07, Alan D. Cabrera <list@toolazydogs.com> wrote:
>>>
>>> -1 (not a veto but a cancelable vote) on publishing retro-jars.
>>>
>>>
>>> Regards,
>>> Alan
>>>
>>> On Mar 21, 2007, at 9:55 AM, David Jencks wrote:
>>>
>>> > +1 to 1.5 only
>>> > +0 to publishing retro-jars
>>> >
>>> > david jencks
>>> >
>>> > On Mar 20, 2007, at 11:16 PM, Jason Dillon wrote:
>>> >
>>> >> Looks like xbean-naming is still compiling for 1.4. Is there any
>>> >> specific reason for this? Can we switch all of xbean to compile
>>> >> for 1.5... and if you need 1.4 compat, then use the
>>> >> retrotranslator-maven-plugin's translate-project goal to make
>>> >> jdk14 artifacts?
>>> >>
>>> >> --jason
>>> >>
>>> >>
>>> >> On Mar 20, 2007, at 5:14 AM, David Jencks wrote:
>>> >>
>>> >>> geronimo-naming jar
>>> >>>
>>> >>> I think you'll find you need to update xbean-naming.
>>> >>>
>>> >>> thanks
>>> >>> david jencks
>>> >>> On Mar 20, 2007, at 4:03 AM, Jason Dillon wrote:
>>> >>>
>>> >>>> The server/trunk build is picking this up in configs/rmi-
>>> >>>> naming... but from where?
>>> >>>>
>>> >>>> Need to update this to use java.util.concurrent... its using
>>> >>>> backport-concurrent-util at the moment.
>>> >>>>
>>> >>>> --jason
>>> >>>
>>> >>
>>> >
>>> >
>>>
>>>
>>
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Architect, LogicBlaze (http://www.logicblaze.com/)
>> Blog: http://gnodet.blogspot.com/
>
|