We have project that have the following structure:
[Project]
-[etc]
-maven.xml
-project.xml
-project.properties
-[modules]
-[moduleA]
-maven.xml
-project.xml
-project.properties
-[moduleB]
-maven.xml
-project.xml
-project.properties
-[moduleC]
-maven.xml
-project.xml
-project.properties
-[logs]
-maven.xml
-project.xml
-project.properties
Where [Project] project.xml contained the following:
<project>
<pomVersion>3</pomVersion>
<extend>${basedir}/etc/project.xml</extend>
<id>activemq-root</id>
<build>
<sourceDirectory></sourceDirectory>
<unitTestSourceDirectory></unitTestSourceDirectory>
</build>
</project>
I tried to build it with Continuum alpha 2 and it does succeed, used the
default setting of alpha 2. Installed in Win XP with Sun jdk1.4.2 and maven
1.0.2.
Regards,
Merwin
-----Original Message-----
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 13, 2005 8:15 PM
To: continuum-users@maven.apache.org
Subject: Re: Alpha 3
On Wed, 2005-07-13 at 11:23 +0800, Merwin Yap wrote:
> Hi! I’ve downloaded alpha 3 and got it running. While trying to build a
> maven 1 project, I got the following error:
[snip]
> I have the same project running in alpha 2 and it seems that it does allow
> the ‘extend’ element. Will the ‘extend’ element of the POM be allowed in
> next version?
I'm not sure how you got this project to build. If you checkout a leaf
project in maven1, there isn't any way for m1 to find the necessary
parent POM. We need to make an m1 project building that is intelligent
about find projects within a checked out m1 directory structure for this
to work properly.
Out of curiosity what settings did you use while running alpha-2?
>
>
> Thanks!
>
>
>
> Regards,
>
> Merwin
>
>
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apache.org
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.8.13/47 - Release Date: 7/12/2005
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.8.14/48 - Release Date: 7/13/2005
