I believe the problem is the stuff in the parent pom. The dataid
present here seem to take precedence over the dataid's in the child pom.
I do not have acces to the code right now, but why do You want to
mention it in the root pom at all?
If You send me Your pom's, I can take a look at them tomorrow.
/Kent
Den 09/11/2009 kl. 15.08 skrev Andy Bell:
Hi Kent
I'm afraid it makes no difference. What seems to be adding
complexity to this is that the report's pom.xml is picking up the
overall project's pom.xml from the maven repository and configuring
this seems to be part of the problem. What we are looking to achieve
is to run all our tests (which is happening), produce all the
history reports (again this is fine) and then produce the individual
tests - but this bit fails because I cannot find a way to get
chronos to generate them all.
In the main project's pom.xml there is this bit:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>chronos-maven-plugin</artifactId>
<version>1.0-SNAPSHOT</version>
<configuration>
<historydir>${history.home}</historydir>
<dataid>broker-import-service-volume-report</
dataid>
</configuration>
If I exclude the <dataid> tag, then the report fails as it doesn't
know what to build but if i include the <dataid> then only that
single report gets built. What I need is a way for chronos to
determine (or me to tell it) which reports to build... If you want I
can email both these pom.xml file to you...
Andy
2009/11/9 Kent Sølvsten <[email protected]>
Hi Andy
This part looks weird, what happens, if you delete that?
Den 09/11/2009 kl. 12.29 skrev Andy Bell:
<reportSet>
<reports>
<report>report</report>
</reports>
</reportSet>
/Kent
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Andy
