On Fri, 2003-06-20 at 09:57, Mark H. Wilkinson wrote:
> On Thu, 2003-06-19 at 16:15, Jason van Zyl wrote:
> > On Thu, 2003-06-19 at 11:03, David Walend wrote:
> > > (Odd that maven is still able to search up
> > > the source tree to find some project.xml file on it's own, but doesn't
> > > reset the base directory. Is that a bug?)
> >
> > That's why you need to use ${basedir} in your file references. As far as
> > I know there is no consistent way in Java to set the current working
> > directory.
>
> I think you can only set the current working directory for new processes
> created with Runtime.exec, and that only with JDK 1.3. But I guess you
> knew that.
>
> Would it be sufficient to store a value for ${basedir} when the POM was
> read, then to prepend it to relative paths when necessary?
That's what we attempt. It is always recommended to use ${basedir} when
any paths are used so things work especially in the context of the
reactor where you kick off in one directory and process many sub
directories.
> Plugins would
> need to be aware of when they need absolute pathnames and when they can
> manage with the text the user put in the POM, but I'd guess most uses
> should be absolute with the possible exception of diagnostic messages.
There definitely may be some inconsistencies in the plugins as some were
written before adopting the ${basedir} policy.
> -Mark.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
