Hi,
> Could you please try a recent nightly build to see whether it makes
> any difference?
I don't dare at the moment Stefan, we have customised it too heavily. I
managed to progress though by using the absolute path and not a symlink.
The next problem is that I need a regexp that will map from
iBox/inspectors/InspectorPageImports.jsp to
jrun__iBox__inspectors__InspectorPageImports2ejsp29.class
I have the directory part sorted thanks to earlier mails. The RE is
straightforward, ie change / to __ and add some crap at the beginning
and end. The problem is the 29 in the class name... that seems to be
completely random and is generated by the JRun compiler. So my question
is about the mapper element, do I have to make it map the source to an
exact destination class name (which I can't predict from the source file
name), or can it be bished so that it will, say, rebuild
iBox/inspectors/InspectorPageImports.jsp because
jrun__iBox__inspectors__InspectorPageImports2ejsp*.class is out of date?
Thanks for your help,
Jamie
> -----Original Message-----
> From: bodewig [mailto:[EMAIL PROTECTED]]
> Sent: 25 July 2001 11:58
> To: ant-user
> Cc: bodewig
> Subject: Re: Apply is looking in wrong place for target
>
>
> On Wed, 25 Jul 2001, Jamie Echlin <[EMAIL PROTECTED]> wrote:
>
> >> > However I don't know where it is getting this destination from,
> >> > it doesn't follow from the dest attribute.
> >>
> >> Are there any symbolic links involved?
> >
> > Yes.
> >
> > WEB-INF -> ../war/jetweb-app/WEB-INF/
> >
> > Seems obvious now. Guess I have to make it relative to the real
> > directory.
>
> Could you please try a recent nightly build to see whether it makes
> any difference?
>
> Stefan
>
Visit our website at http://www.ubswarburg.com
This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version. This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.
