On Wed, 2003-01-08 at 16:34, Chan, Charles wrote:
> Hi, I am using CVSHEAD Maven. I am close to finish porting an Ant J2EE build
> to Maven but encounter a problem. My project is structured as follows:
>
> master/
> project.xml
> ejb/
> project.xml
> ui/
> project.xml
> startup/
> project.xml
>
> Each project.xml in the subcomponent "extends" the master project.xml by
> using <extend>../project.xml</extend> (similar to what Commons does). In my
> Master maven.xml, I have
Yes, this has changed slightly in the following way.
When using the <extend> element in conjunction with a POM in the
filesystem always use something like the following:
<extend>${basedir}../project.xml</extend>
Where ${basedir} is the base directory of the project being built. This
practice should allow builds to work regardless of where the build is
started from.
This practice will be put into effect in the commons build as well. I
made some changes that messed up using just ../project.xml so standard
practice will now be the use of ${basedir} for all file system
references. You can check out the touchstone build for some other
examples of ${basedir}.
--
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: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
