Yep, that looks like the cause to me. if ${basedir} is mapping to ".",
then when maven tries to delete the "output directory" it would end up
deleting the "Project A" dir, just as shown.

Try removing the outputDirectory elemnt from the pom (so it defaults to
its normal value).

Cheers,

Simon

On Thu, 2006-04-27 at 11:12 +0200, Tom Joad wrote:
> Why do you have to set explicitly ${basedir} On project A pom.xml for
> different location.
> Try to give relative path so without ${basedir}
> Tom.
> 
> 2006/4/27, RobJac <[EMAIL PROTECTED]>:
> >
> > Yes I do. This is how my Project A pom.xml looks like
> >
> > <project xmlns="http://maven.apache.org/POM/4.0.0";
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> >   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> > http://maven.apache.org/maven-v4_0_0.xsd";>
> >   <modelVersion>4.0.0</modelVersion>
> >   <groupId>Project A</groupId>
> >   <artifactId>Project A</artifactId>
> >   <packaging>jar</packaging>
> >   <version>1.0</version>
> >   <name>Maven Quick Start Archetype</name>
> >   <parent>
> >     <groupId>Main</groupId>
> >     <artifactId>Main</artifactId>
> >     <version>1.0</version>
> >   </parent>
> >   <dependencies>
> >     <dependency>
> >       <groupId>antlr</groupId>
> >       <artifactId>antlr</artifactId>
> >       <version>2.7.5H3</version>
> >       <scope>provided</scope>
> >     </dependency>
> >
> >   </dependencies>
> >   <build>
> >     <directory>${basedir}</directory>
> >     <outputDirectory>classes</outputDirectory>
> >     <finalName>${project.artifactId}</finalName>
> >     <testOutputDirectory>test-classes</testOutputDirectory>
> >     <sourceDirectory>src</sourceDirectory>
> >     <testSourceDirectory>test</testSourceDirectory>
> >     <resources>
> >       <resource>
> >         <directory>${basedir}/resources</directory>
> >       </resource>
> >         <resource>
> >             <directory>src</directory>
> >             <filtering>false</filtering>
> >             <excludes>
> >               <exclude>**/*.java</exclude>
> >             </excludes>
> >           </resource>
> >
> >     </resources>
> >     <testResources>
> >       <testResource>
> >         <directory>test</directory>
> >       </testResource>
> >     </testResources>
> >         <plugins>
> >             <plugin>
> >               <groupId>org.apache.maven.plugins</groupId>
> >               <artifactId>maven-compiler-plugin</artifactId>
> >                 <configuration>
> >                   <source>1.5</source>
> >                   <target>1.5</target>
> >                 </configuration>
> >                </plugin>
> >         </plugins>
> >   </build>
> >
> >   <reporting>
> >     <outputDirectory>target/site</outputDirectory>
> >   </reporting>
> > </project>
> > --
> > View this message in context: 
> > http://www.nabble.com/issue-with-mvn-clean-install-t1516559.html#a4117154
> > Sent from the Maven - Users forum at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to