and about the hibernate problems. this works for me:
adding this bit:
                    <dependency>
                        <groupId>cobertura</groupId>
                        <artifactId>cobertura</artifactId>
                        <version>1.8</version>
                    </dependency>

to this part in the pom file:

            <plugin>
                <groupId>org.codehaus.mojo</groupId>
                <artifactId>hibernate3-maven-plugin</artifactId>
                <version>2.0-alpha-1</version>
                <configuration>
                    <components>
                        <component>
                            <name>hbm2ddl</name>
                            <implementation>
                                annotationconfiguration</implementation>
                           
                            <!-- Use 'jpaconfiguration' if your going
the -Ddao.framework=jpa-hibernate route. -->
                           
                           
<!--<implementation>jpaconfiguration</implementation>-->
                        </component>
                    </components>
                    <componentProperties>
                        <drop>true</drop>
                        <jdk5>true</jdk5>
                        <propertyfile>
                            target/classes/jdbc.properties</propertyfile>
                        <skip>${maven.test.skip}</skip>
                    </componentProperties>
                </configuration>
                <executions>
                    <execution>
                        <phase>process-test-resources</phase>
                        <goals>
                            <goal>hbm2ddl</goal>
                        </goals>
                    </execution>
                </executions>
                <dependencies>
                    <dependency>
                        <groupId>${jdbc.groupId}</groupId>
                        <artifactId>${jdbc.artifactId}</artifactId>
                        <version>${jdbc.version}</version>
                    </dependency>
                    <dependency>
                        <groupId>cobertura</groupId>
                        <artifactId>cobertura</artifactId>
                        <version>1.8</version>
                    </dependency>
                </dependencies>
            </plugin>

matt can this be added to the pom file??

tibi



Matt Raible wrote:
> Removing the aspectj-maven-plugin from your pom.xml should solve this problem.
>
> http://issues.appfuse.org/browse/APF-914
>
> Matt
>
> On 9/24/07, Matt Raible <[EMAIL PROTECTED]> wrote:
>   
>> I've opened a thread on this on Maven's user list:
>>
>> http://www.nabble.com/Code-Coverage-Plugins-with-Maven-2-tf4510331s177.html
>>
>> Matt
>>
>> On 9/24/07, Matt Raible <[EMAIL PROTECTED]> wrote:
>>     
>>> You might try adding the following to the <plugins> section of your pom.xml.
>>>
>>>             <plugin>
>>>                 <groupId>org.codehaus.mojo</groupId>
>>>                 <artifactId>cobertura-maven-plugin</artifactId>
>>>                 <executions>
>>>                     <execution>
>>>                         <goals>
>>>                             <goal>clean</goal>
>>>                         </goals>
>>>                     </execution>
>>>                 </executions>
>>>             </plugin>
>>>
>>> If that helps, let me know.  I'll see if I can reproduce the 0%
>>> problem using struts2-basic after running appfuse:full-source.
>>>
>>> Matt
>>>
>>> On 9/24/07, tibi <[EMAIL PROTECTED]> wrote:
>>>       
>>>> yes cobertura is great when it works... but i can't get it working any 
>>>> more.
>>>> i have version 2.0
>>>> when i run it it complains about my files in the hibernate.cfg.xml.
>>>> i used to comment all my model objects out so cobertura would run. but
>>>> now my test are not running any more :(
>>>>
>>>>
>>>> is there someone who can make these cool reports??
>>>>
>>>>
>>>> tibi
>>>>
>>>>
>>>> Richard Brewster wrote:
>>>>         
>>>>> Thanks, but I get ZERO test coverage, using either 2.0 or 2.1 of the
>>>>> cobertura-maven-plugin.  So something else is wrong.
>>>>>
>>>>> I did verify that cobertura-maven-plugin 2.1 is depending on cobertura 
>>>>> 1.8.
>>>>> But cobertura 1.9 has been out since June, 2007.  Time to update the 
>>>>> plugin.
>>>>>
>>>>> Richard
>>>>>
>>>>>
>>>>> mraible wrote:
>>>>>
>>>>>           
>>>>>> The Corbertura plugin for Maven has been notoriously buggy. Make sure
>>>>>> you have <version>2.0</version> specified for it to work properly.
>>>>>>
>>>>>> With some googling, I found this - maybe it will help:
>>>>>>
>>>>>> http://tinyurl.com/2n2mrz
>>>>>>
>>>>>> Matt
>>>>>>
>>>>>> On 9/21/07, Richard Brewster <[EMAIL PROTECTED]> wrote:
>>>>>>
>>>>>>             
>>>>>>> Using AppFuse 2.0-RC1 modular struts 2 archetype.  But this problem
>>>>>>> occurs in
>>>>>>> previous archetypes too, for me.  In the core module the command:
>>>>>>>
>>>>>>> mvn clean site
>>>>>>>
>>>>>>> succeeds and the following is logged:
>>>>>>>
>>>>>>> Tests run: 45, Failures: 0, Errors: 0, Skipped: 0
>>>>>>>
>>>>>>> [INFO] Preparing surefire-report:report-only
>>>>>>> [INFO] No goals needed for project - skipping
>>>>>>> [INFO] Preparing cobertura:cobertura
>>>>>>> [INFO] [aspectj:compile {execution: default}]
>>>>>>> [INFO] [resources:resources]
>>>>>>> [INFO] Using default encoding to copy filtered resources.
>>>>>>> [INFO] [compiler:compile]
>>>>>>> [INFO] Nothing to compile - all classes are up to date
>>>>>>> [INFO] [cobertura:instrument]
>>>>>>> [INFO] Cobertura 1.7 - GNU GPL License (NO WARRANTY) - See COPYRIGHT 
>>>>>>> file
>>>>>>> Instrumenting 40 classes to
>>>>>>> C:\dev\af-modular\core\target\generated-classes\cobertura
>>>>>>> Cobertura: Saved information on 38 classes.
>>>>>>> Instrument time: 203ms
>>>>>>>
>>>>>>> [INFO] Instrumentation was successful.
>>>>>>>
>>>>>>> ... all tests run again, successfully again.  Finally you see:
>>>>>>>
>>>>>>> [INFO] Cobertura 1.7 - GNU GPL License (NO WARRANTY) - See COPYRIGHT 
>>>>>>> file
>>>>>>> Cobertura: Loaded information on 38 classes.
>>>>>>> Report time: 719ms
>>>>>>>
>>>>>>> [INFO] Cobertura Report generation was successful.
>>>>>>>
>>>>>>> When you look at the report, it is all RED.  Zero coverage.  It seems to
>>>>>>> me
>>>>>>> that the generated classes are not put into the test classpath ahead of
>>>>>>> the
>>>>>>> normal classes, as required.  You would expect Cobertura to log that it
>>>>>>> has
>>>>>>> loaded information on the classes under test, too, and I see no logs of
>>>>>>> that
>>>>>>> kind.  Must be a classpath problem.  What should I do?
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Richard Brewster
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> View this message in context:
>>>>>>> http://www.nabble.com/Cobertura-reporting-0--coverage-tf4496724s2369.html#a12823394
>>>>>>> Sent from the AppFuse - User mailing list archive at Nabble.com.
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>>>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>               
>>>>>> --
>>>>>> http://raibledesigns.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]
>>>>
>>>>
>>>>         
>>> --
>>> http://raibledesigns.com
>>>
>>>       
>> --
>> http://raibledesigns.com
>>
>>     
>
>
>   

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

Reply via email to