can we make the build script go get the jars if they are missing, or is that a 
violation of license too?

        -----Original Message----- 
        From: Hiran Chaudhuri [mailto:[EMAIL PROTECTED]] 
        Sent: Mon 2/17/2003 11:53 PM 
        To: OJB Users List 
        Cc: 
        Subject: Re: 0.9.9 doesn't build
        
        

        Maybe the build script (ant) could check for existence and make verbose
        messages like "The file lib\foo.jar" ist still missing. Please download it
        from http://www.foo.org";...?
        
        A readme must be read, and anyone just trying to build will spend time
        searching the error, but if such build error occur this time is saved.
        
        Hiran
        
        
        ----- Original Message -----
        From: "Thomas Mahler" <[EMAIL PROTECTED]>
        To: "OJB Users List" <[EMAIL PROTECTED]>
        Sent: Monday, February 17, 2003 9:35 PM
        Subject: Re: 0.9.9 doesn't build
        
        
        > Hi again Chris,
        >
        > You will have noticed, that the mentioned jars (and some others) are
        > include in the actual 0.9.9 relase.
        > We are currently preparing for a completely apache hosted distribution.
        > We are not allowed to have jars with certain licenses (GPL, LPGL, SUN
        > binary code license) in CVS or in our distributions.
        >
        > I'd also prefer to ship everything needed, but we are simply not allowed
        > to do so :-(
        >
        > But we will provide a dependency page listing all jars we depend on, and
        > where to get them.
        >
        > cheers,
        > Thomas
        >
        >
        >
        >
        > Chris Rossi wrote:
        > > Chris Rossi wrote:
        > >
        > >>
        > >> ok.  i'll see if i can pull latest.
        > >
        > >  >
        > > ok i've pulled the latest from CVS and can't build because it can't find
        > > some libraries:
        > >
        > >   javax.servlet.*
        > >   javax.transaction.*
        > >   javax.sql.*
        > >   javax.ejb.*
        > >
        > > maybe one or two others i didn't notice just now scrolling through the
        > > build errors.  anyway, while i can certainly now go track down these
        > > libraries and add them to my db-ojb/lib so i can build, it seems like it
        > > would be faster if ojb shipped with what it need to build out of the
        > > box.  is there a philosophical or technical reason not to do so?
        > >
        > > rossi
        > >
        > >
        > >
        > > ---------------------------------------------------------------------
        > > 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]
        >
        
        
        ---------------------------------------------------------------------
        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