Maybe adding this to your subproject's pom helps? It resolved the problem of
being able to build a subproject on a clean server without running the main
build first.
<parent>
...
<relativePath>../../pom.xml</relativePath>
</parent>
Assuming that your aggregator pom is two levels below your subproject's poms:
pom.xml
|- modules
| |- subproject1
| | |- pom.xml
| |- subproject2
| | |- pom.xml
Tobias
On 13.10.2010, at 03:49, LongkerDandy wrote:
> I have the same situation.
> Always using mvn install.
>
> On Fri, Sep 10, 2010 at 8:50 PM, Bruno Harbulot <
> [email protected]> wrote:
>
>> Hello,
>>
>> I'm trying to use the "bundle" packaging and the maven-bundle-plugin in a
>> multi-module project.
>>
>> The following is declared in the parent POM and in the sub-module POMs
>> (although it might not be necessary):
>>
>> <plugin>
>> <groupId>org.apache.felix</groupId>
>> <artifactId>maven-bundle-plugin</artifactId>
>> <extensions>true</extensions>
>> <version>2.1.0</version>
>> <configuration>
>> <instructions>
>>
>> <Bundle-SymbolicName>${project.artifactId}</Bundle-SymbolicName>
>> </instructions>
>> </configuration>
>> </plugin>
>>
>>
>> When we were using the 'jar' packaging, "mvn package" was able to find
>> dependencies between sub-modules. However, after switching to 'bundle',
>> these modules can no longer be found using "mvn package". "mvn install"
>> works (and once this has been done once, "mvn package" works after, of
>> course).
>> The problem is that it prevents "mvn package" to be done on clean
>> installations (for continuous integration, for example).
>> Has anyone experienced similar problems? Is there a workaround for this?
>> (I'm using Maven 2.2.1, if it's relevant.)
>>
>> Best wishes,
>>
>> Bruno
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
