On Tue, Apr 15, 2008 at 4:55 PM, Daniel Spiewak <djspiewak@gmail.com> wrote:
> Could Buildr potentially allow something like Mechanize as an alternative
> download mechanism for situations such as this? Oracle's "protection" of
> their JDBC driver would be fairly easy to get around automatically if
> Buildr
> were able to simulate a browser session calling different pages in
> sequence
> (which Mechanize allows).
You can definitely use mechanize. In fact, you can define an artifact to
download/create the file any way you want:
artifact(<spec>).enhance do |task|
... create the file task.name ...
end
Assaf
>
>
> Daniel
>
> On Tue, Apr 15, 2008 at 5:57 PM, Rhett Sutphin <rhett@detailedbalance.net>
> wrote:
>
> > Hi Harish,
> >
> >
> > On Apr 15, 2008, at 5:45 PM, Harish Krishnaswamy wrote:
> >
> > > I am having issues downloading the Oracle driver automatically from my
> > > build
> > > script. I know they require a username and password, but it still
> fails
> > > when
> > > I provide them in the url. Although that same URL works from within
> the
> > > browser. Here's the URL, username and password masked...
> > >
> > >
> > >
> https://profile.oracle.com/jsp/reg/loginHandler.jsp?username=XXX&password=XXX&redirectUrl=http://download.oracle.com/otn/utilities_drivers/jdbc/10204/ojdbc14.jar
> > >
> >
> > I suspect that Oracle is setting some sort of session cookie when you
> > visit the login page in your browser. I'm not sure if buildr's download
> > mechanism supports including cookies in a redirect.
> >
> > [FWIW, I always end up just putting the oracle JDBC driver somewhere on
> my
> > intranet (for internal projects) or providing download instructions (for
> > external). Too bad Oracle makes it so difficult to use their software.]
> >
> > Rhett
> >
>
--
CTO, Intalio
http://www.intalio.com
|