Hi Kelvin,

That works for me as long as it is specified in the build docs.

Thanks,

- Ron

----- Original Message ----
From: kelvin goodson <[EMAIL PROTECTED]>
To: [email protected]
Sent: Monday, October 2, 2006 3:20:32 PM
Subject: Re: Tuscany SDO compilation problems w/JDK 1.4


Hi again,

  I'm updating the BUILDING.txt instruction document that goes out with the
source distribution,  and I need to make a decision on what I say about JDK
levels.  Given that no one has piped up to say that 1.4.0 is a must-have,
I'm going to say you need 1.4.2 at minumum.  Hope that's OK,  shout very
quickly if its not please.

Regards, Kelvin.

On 29/09/06, kelvin goodson <[EMAIL PROTECTED]> wrote:
>
> Hi Ron,
>   re the 1.4.0 JDK issue, I think we'd kind of been assuming that 1.4.2was 
> going to be OK for all our users,  but if its going to be an issue for
> you then I'll take a look at making us clean for 1.4.
>
> As for Interface2JavaGenerator, this was definitely developed as a 1.5value 
> add item,  and relies on new syntax such as List<Foo> to carry the
> type of an isMany() property, so unless there's someone out ther who feels
> they want this kind of value-add function to work with JDK 1.4 and is
> prepared to develop it, we're stuck with prereq'ing JDK 1.5 for that one
> class.  As for the issue of amending the packaging to treat
> Interface2JavaGenerator separately, I'll have to put my thinking cap on to
> work out how best to do that.  Suggestions and/or best practice tips most
> welcome, thanks.
>
> Best Regards, Kelvin.
>
>
> On 28/09/06, Ron Gavlin <[EMAIL PROTECTED]> wrote:
> >
> > Brandon,
> >
> > Thanks for your reply.
> >
> > The SDO 2.01 spec requires the minimum JDK to be 1.4.0. So, it seems
> > that 1.4.2-specific features such as assert should be off-limits for
> > tuscany SDO code.
> >
> > Also, as a JDK 1.4.2 user, I would like to be able to generate SDO
> > classes from a Java interface. By deleting Interface2JavaGenerator.java,
> > I lose that ability. I think the few JDK 1.5-specific features of this
> > class should be packaged separately so that 1.4 users can still use the
> > tool.
> >
> > Thanks again,
> >
> > - Ron
> >
> >
> >
> > ----- Original Message ----
> > From: "[EMAIL PROTECTED]" < [EMAIL PROTECTED]>
> > To: [email protected]
> > Sent: Thursday, September 28, 2006 10:25:03 AM
> > Subject: Re: Tuscany SDO compilation problems w/JDK 1.4
> >
> >
> > Ron:
> >
> > You can safely delete the Interface2JavaGenerator.java and be JDK 1.4.2
> > compliant. I do not understand your "assert" keyword error, as that was
> > introduced in JDK 1.4.2
> >
> > Thanks!
> >
> > Brandon Werner
> >
> >
> >
> >
> > Ron Gavlin <[EMAIL PROTECTED]>
> > 09/28/2006 10:12 AM
> > Please respond to
> > [email protected]
> >
> >
> > To
> > tuscany-user tuscany-user <[email protected]>
> > cc
> >
> > Subject
> > Tuscany SDO compilation problems w/JDK 1.4
> >
> >
> >
> >
> >
> >
> > Greetings,
> >
> > I am attempting to build tuscany-sdo M2-RC1a w/JDK 1.4. This release of
> > Tuscany SDO should compile with JDK 1.4, correct? I am experiencing the
> > two problems listed below. What are the correct fixes for these problems
> >
> > and should I open JIRAs for them?
> >
> > 1). Line 188 of org.apache.tuscany.sdo.util.StAX2SAXAdapter.javaincludes
> > the JDK 1.5 keyword "assert".
> >
> > 2). Lines 23-24 and 182-186 of
> > org.apache.tuscany.sdo.generate.Interface2JavaGenerator.java include
> > references to JDK 1.5-only classes java.lang.reflect.ParameterizedTypeand
> > java.lang.reflect.Type.
> >
> > - Ron
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >
> >
> > -----------------------------------------
> > CONFIDENTIALITY STATEMENT:
> > This e-mail transmission contains information that is intended to
> > be confidential.  It is intended only for the addressee named
> > above.  If you receive this e-mail in error, please do not read,
> > copy, or disseminate it.  If you are not the intended recipient,
> > any disclosure, copying, distribution or use of the contents of
> > this information is prohibited.   Please reply to the message
> > immediately by informing the sender that the message was
> > misdirected.  After replying, please erase it from your computer
> > system.  Your assistance in correcting this error is appreciated.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to