Your sub-project1 references base-project as it's parrent. This means it has
to inherit all configuration from base-project so it has to be downloaded.
If your sub-project1 does not inherit anyting from base, then omit <parrent>
tag.
It is perfectly legal to have multimodule project where sub-projects doesn't
reference base-project as parents.
2007/1/3, Martin Moser <[EMAIL PROTECTED]>:
Hi all,
I have troubles compiling my sub-projects.
I have following project-structure:
-base-project
--sub-project 1
--- subsub-project 1 of sub-project 1
--- subsub-project 2 of sub-project 1
-- sub-project 2
--- subsubproject 1 of sub-project 2
I want to compile sub-project 1 only. So I changed to the sub-project1
directory and called "mvn compile".
But maven tries to download the pom of the base-project and this fails, as
this pom is in no repository yet.
The build of the base-project or the jar-build of subsub-project1 works
fine.
Did I miss anything to configure?
My pom.xml's look like that:
pom.xml of base-project:
<groupId>testgroup</groupId>
<artifactId>base</artifactId>
<packaging>pom</packaging>
<version>1.99.1</version>
:
<modules>
<module>sub1</module>
<module>sub2</module>
</modules>
pom.xml of sub-project 1 in subfolder sub1:
<groupId>testgroup</groupId>
<artifactId>sub1</artifactId>
<packaging>pom</packaging>
<version>1.99.1</version>
:
<parent>
<groupId>testgroup</groupId>
<artifactId>base</artifactId>
<version>1.99.1</version>
<relativePath>..</relativePath>
</parent>
<modules>
:
I appreciate any suggestions!
Thanks in advance!
Regards,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Roman Kalukiewicz
