<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
<version>1.1</version>
<executions>
<execution>
<id>add-source</id>
<phase>generate-sources</phase>
<goals>
<goal>add-source</goal>
</goals>
<configuration>
<sources>
<source>[YOUR SOURCE DIRECTORY 2]</source>
<source>[YOUR SOURCE DIRECTORY 3]</source>
</sources>
</configuration>
</execution>
</executions>
</plugin>
http://docs.codehaus.org/display/SONAR/Collect+data#Collectdata-NonMavenprojects%28sonarlightmode%29
best regards
Christian
2009/10/5 Barrie Treloar <[email protected]>:
> On Sun, Oct 4, 2009 at 4:15 PM, ifsNabble <[email protected]>
> wrote:
>>
>> Of course! Here´s the solution we found for our problem:
>>
>> As described we have the structure
>>
>> /trunk/projectA/pom.xml
>> /trunk/projectAB/pom.xml
>> /trunk/project.../pom.xml
>> /trunk/projectZ/pom.xml
>>
>> That makes us able to put a pom.xml in the highest hierarchy folder
>> (/trunk/pom.xml).
>> This pom.xml uses the maven-build-helper-plugin where you can specify
>> additional source folders.
>> And due to the fact that we´re on top of folder hierarchy we can use the
>> subfolders ("/project.../src/main/java") and create in that way a virtual
>> project with many many source folders.
>
> Could you paste the snippet of pom.xml that includes
> maven-build-helper-plugin.
>
> Concrete examples help people with problems trouble shoot there own :)
>
> ---------------------------------------------------------------------
> 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]
