Another simple approach.
We have added the line:
<pathelement path="${j2ee.jar}"/>
to classpath ref in build.xml and defined the property to point to a valid J2EE
jar(s). In our case it is just one, weblogic, but would also work with reference J2EE
jar or with multiple appropriate colon/semi-colon separated jars (jta, jca, etc).
Would be easy to then have ant fail if this property is not defined with instructions
on what to do, pointer to deps, etc.
This overcomes some of logistical/click through problems with ftp/http, you don't
impose assumptions about the packaging of the required J2EElibs on everyone, and it
helps avoid muliple copies of jars all over the place. And it is easy to detect an
undefined property, whereas not sure how you can reliably validate class path issues
without some extra work or base assumptions about file naming.
Just 2 cents.
> -----Original Message-----
> From: Brian McCallister [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 20, 2003 11:27 AM
> To: OJB Users List
> Subject: Re: building from CVS, problems
>
>
> Was there ever a decision made about how to make obtaining
> these easy?
> The big licensing hullabaloo seems to have died off with no official
> policy being decided.
>
> Is it acceptable to ftp them from within ant?
>
> Is it acceptable to take advantage of other open source projects who
> happen to require the same jars (Jboss comes to mind) to
> obtain the Sun
> jars without going through Sun's click-through?
>
> -Brian
>
> On Thursday, February 20, 2003, at 11:09 AM, Mahler Thomas wrote:
>
> > Hi Will,
> >
> > please use the libs from the 0.9.9 release.
> > We have removed several jars from cvs as they do not comply
> with the
> > apache
> > licence model.
> > for instance sun jar files and also (L)GPLed jar like jboss stuff.
> >
> > The file
> > http://cvs.apache.org/viewcvs/db-ojb/project.xml?rev=HEAD&content-
> > type=text/
> > vnd.viewcvs-markup (which is rendered by maven to
> > http://db.apache.org/ojb/dependencies.html)
> >
> > contains a list of all jars we depend on. it contains
> version info and
> > a
> > link where to obtain each jar file.
> >
> > cheers,
> > thomas
> >
> >> -----Original Message-----
> >> From: Will Jaynes [mailto:[EMAIL PROTECTED]]
> >> Sent: Thursday, February 20, 2003 3:02 PM
> >> To: OJB Users List
> >> Subject: Re: building from CVS, problems
> >>
> >>
> >> Well... I found these three jars in the OJB/lib of an old OJB
> >> directory
> >> that I had hidden away. After including these jars compiling still
> >> failed. Then I copied two jboss jars from the old to the
> new OJB/lib.
> >> Now compiling gets farther, still fails in
> >> org.jboss.ojb.pb.PBFactory.java.
> >>
> >> So, just what all do I need for building OJB that isn't
> >> included in the CVS?
> >>
> >> Will
> >>
> >> Will Jaynes wrote:
> >>> Today, I updated from the OJB CVS and found I couldn't
> >> compile, neither
> >>> within Eclipse, which used to work, nor using just Ant.
> >> According to the
> >>> Eclipse .classpath file in CVS there are three new jar
> >> files expected to
> >>> be in the OJB/lib directory:
> >>>
> >>> servlet.jar
> >>> ejb.jar
> >>> jts-spec1_0_1.jar
> >>>
> >>> I have a servlet.jar file. Where do the others come from?
> >>>
> >>> Regards, Will
> >>>
> >>
> >>
> >>
> ---------------------------------------------------------------------
> >> 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]
