[mojo-dev] [jira] Closed: (MOJO-658) Use system cl for verification when running in a 1.4 vm
[ http://jira.codehaus.org/browse/MOJO-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed MOJO-658. - Resolution: Fixed > Use system cl for verification when running in a 1.4 vm > --- > > Key: MOJO-658 > URL: http://jira.codehaus.org/browse/MOJO-658 > Project: Mojo > Issue Type: Improvement > Components: retrotranslator >Reporter: Jason Dillon > Assigned To: Jason Dillon >Priority: Minor > > When running on JRE 1.4, > Retrotranslator.setClassLoader(ClassLoader.getSystemClassLoader()) may be > used for the verification classpath instead of adding system jars from JRE > 1.4. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] Created: (MOJO-661) Update RAT plugin to work with RAT-0.5-SNAPSHOT
Update RAT plugin to work with RAT-0.5-SNAPSHOT --- Key: MOJO-661 URL: http://jira.codehaus.org/browse/MOJO-661 Project: Mojo Issue Type: Improvement Reporter: Lars Trieloff Attachments: rat-0.5-snapshot.patch The rat-lib has undergone a massive API change from version 0.4.1 to 0.5-SNAPSHOT. The attached patch updates the rat-maven-plugin to the latest version of the API. A snapshot of rat-lib-0.5-SNAPSHOT is deployed at http://snapshots.mindquarry.org/com/google/code/p/arat/rat-lib/0.5-SNAPSHOT/ The test cases have been updated to the new plugin configuration accordingly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] Updated: (MOJO-657) Plugin fails in multiproject modules
[
http://jira.codehaus.org/browse/MOJO-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Trieloff updated MOJO-657:
---
Attachment: docbook-maven-plugin-multiproject.patch
This patch extends my previous patches by adding multiproject support (one
piece that had been missing so far) and adds the missing MojoURLResolver that
is able to resolve resources from jar dependencies.
> Plugin fails in multiproject modules
>
>
> Key: MOJO-657
> URL: http://jira.codehaus.org/browse/MOJO-657
> Project: Mojo
> Issue Type: Bug
>Reporter: Luke Taylor
> Attachments: docbook-maven-plugin-multiproject.patch
>
>
> I've been using the plugin with the patch from MOJO-617 (with some help from
> the patch author) and I get the following error:
> [INFO] [docbook:transform]
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] basedir
> /Users/luke/Work/OpenSrc/acegitrunk/acegisecurity/core/src/docbook does not
> exist
> [INFO]
>
> [INFO] Trace
> java.lang.IllegalStateException: basedir
> /Users/luke/Work/OpenSrc/acegitrunk/acegisecurity/core/src/docbook does not
> exist
> at
> org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:542)
> at
> org.codehaus.plexus.compiler.util.scan.AbstractSourceInclusionScanner.scanForSources(AbstractSourceInclusionScanner.java:78)
> at
> org.codehaus.plexus.compiler.util.scan.StaleSourceScanner.getIncludedSources(StaleSourceScanner.java:84)
> at
> org.codehaus.mojo.docbook.OLinkDBUpdater.update(OLinkDBUpdater.java:97)
> at
> org.codehaus.mojo.docbook.TransformMojo.execute(TransformMojo.java:180)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
> Adding the following code to the start of the execute() method in
> TranformMojo seems to get rid of the problem:
> if (!this.sourceDirectory.exists())
> {
> log.debug("No docbook source directory " + this.sourceDirectory);
> return;
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] Commented: (MOJO-644) Do not generate cobertura dashboard
[
http://jira.codehaus.org/browse/MOJO-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88761
]
David Vicente commented on MOJO-644:
yes, it will be customized because i must keep the compatibility between :
- cobertura-maven-plugin in version 2.0 which has the cobertura.ser located in
${basedir}/ directory
- cobertura-maven-plugin in version 2.1 which has the cobertura.ser located in
${project.build.directory}/cobertura/ directory
> Do not generate cobertura dashboard
> ---
>
> Key: MOJO-644
> URL: http://jira.codehaus.org/browse/MOJO-644
> Project: Mojo
> Issue Type: Bug
> Components: dashboard
> Environment: cobertura-maven-plugin version 2.1
>Reporter: Brice Ruzand
> Assigned To: David Vicente
> Attachments: dashboard.txt
>
>
> with cobertura-maven-plugin version 2.1, cobertura.ser file is located in
> ${project.build.directory}/cobertura/cobertura.ser and not in
> ${basedir}/cobertura.ser
> Patch file attached
> Maybe this property can be cutomized.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] Commented: (MOJO-644) Do not generate cobertura dashboard
[
http://jira.codehaus.org/browse/MOJO-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88764
]
Brice Ruzand commented on MOJO-644:
---
Yes, I'am agree
> Do not generate cobertura dashboard
> ---
>
> Key: MOJO-644
> URL: http://jira.codehaus.org/browse/MOJO-644
> Project: Mojo
> Issue Type: Bug
> Components: dashboard
> Environment: cobertura-maven-plugin version 2.1
>Reporter: Brice Ruzand
> Assigned To: David Vicente
> Attachments: dashboard.txt
>
>
> with cobertura-maven-plugin version 2.1, cobertura.ser file is located in
> ${project.build.directory}/cobertura/cobertura.ser and not in
> ${basedir}/cobertura.ser
> Patch file attached
> Maybe this property can be cutomized.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] Updated: (MOJO-662) Line Cover Rate invalid calcul
[
http://jira.codehaus.org/browse/MOJO-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brice Ruzand updated MOJO-662:
--
Attachment: CoberturaReportBean.java
Corrected classes
> Line Cover Rate invalid calcul
> ---
>
> Key: MOJO-662
> URL: http://jira.codehaus.org/browse/MOJO-662
> Project: Mojo
> Issue Type: Bug
> Components: dashboard
>Reporter: Brice Ruzand
> Attachments: CoberturaReportBean.java
>
>
> in this classe :
> org.codehaus.mojo.dashboard.report.plugin.beans.CoberturaReportBean
> in method merge : calculation of lineCoverRate is missing
> methode with correction
> /**
> *
> * @param dashboardReport
> */
> public void merge( CoberturaReportBean dashboardReport )
> {
> if ( dashboardReport != null )
> {
> this.nbClasses = this.nbClasses + dashboardReport.getNbClasses();
> this.numberOfCoveredBranches = this.numberOfCoveredBranches +
> dashboardReport.getNumberOfCoveredBranches();
> this.numberOfCoveredLines = this.numberOfCoveredLines +
> dashboardReport.getNumberOfCoveredLines();
> this.numberOfValidBranches = this.numberOfValidBranches +
> dashboardReport.getNumberOfValidBranches();
> this.numberOfValidLines = this.numberOfValidLines +
> dashboardReport.getNumberOfValidLines();
> if ( numberOfValidBranches == 0 )
> {
> // no branches, therefore 100% branch coverage.
> branchCoverRate = 1d;
> }
> else
> {
> branchCoverRate = (double) numberOfCoveredBranches /
> numberOfValidBranches;
> }
> if ( numberOfValidLines == 0 )
> {
> // no branches, therefore 100% branch coverage.
> lineCoverRate = 1d;
> }
> else
> {
>lineCoverRate = (double) numberOfCoveredLines /
> numberOfValidLines;
> }
> }
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] Created: (MOJO-662) Line Cover Rate invalid calcul
Line Cover Rate invalid calcul
---
Key: MOJO-662
URL: http://jira.codehaus.org/browse/MOJO-662
Project: Mojo
Issue Type: Bug
Components: dashboard
Reporter: Brice Ruzand
Attachments: CoberturaReportBean.java
in this classe :
org.codehaus.mojo.dashboard.report.plugin.beans.CoberturaReportBean
in method merge : calculation of lineCoverRate is missing
methode with correction
/**
*
* @param dashboardReport
*/
public void merge( CoberturaReportBean dashboardReport )
{
if ( dashboardReport != null )
{
this.nbClasses = this.nbClasses + dashboardReport.getNbClasses();
this.numberOfCoveredBranches = this.numberOfCoveredBranches +
dashboardReport.getNumberOfCoveredBranches();
this.numberOfCoveredLines = this.numberOfCoveredLines +
dashboardReport.getNumberOfCoveredLines();
this.numberOfValidBranches = this.numberOfValidBranches +
dashboardReport.getNumberOfValidBranches();
this.numberOfValidLines = this.numberOfValidLines +
dashboardReport.getNumberOfValidLines();
if ( numberOfValidBranches == 0 )
{
// no branches, therefore 100% branch coverage.
branchCoverRate = 1d;
}
else
{
branchCoverRate = (double) numberOfCoveredBranches /
numberOfValidBranches;
}
if ( numberOfValidLines == 0 )
{
// no branches, therefore 100% branch coverage.
lineCoverRate = 1d;
}
else
{
lineCoverRate = (double) numberOfCoveredLines /
numberOfValidLines;
}
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] Assigned: (MOJO-662) Line Cover Rate invalid calcul
[
http://jira.codehaus.org/browse/MOJO-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Vicente reassigned MOJO-662:
--
Assignee: David Vicente
> Line Cover Rate invalid calcul
> ---
>
> Key: MOJO-662
> URL: http://jira.codehaus.org/browse/MOJO-662
> Project: Mojo
> Issue Type: Bug
> Components: dashboard
>Reporter: Brice Ruzand
> Assigned To: David Vicente
> Attachments: CoberturaReportBean.java
>
>
> in this classe :
> org.codehaus.mojo.dashboard.report.plugin.beans.CoberturaReportBean
> in method merge : calculation of lineCoverRate is missing
> methode with correction
> /**
> *
> * @param dashboardReport
> */
> public void merge( CoberturaReportBean dashboardReport )
> {
> if ( dashboardReport != null )
> {
> this.nbClasses = this.nbClasses + dashboardReport.getNbClasses();
> this.numberOfCoveredBranches = this.numberOfCoveredBranches +
> dashboardReport.getNumberOfCoveredBranches();
> this.numberOfCoveredLines = this.numberOfCoveredLines +
> dashboardReport.getNumberOfCoveredLines();
> this.numberOfValidBranches = this.numberOfValidBranches +
> dashboardReport.getNumberOfValidBranches();
> this.numberOfValidLines = this.numberOfValidLines +
> dashboardReport.getNumberOfValidLines();
> if ( numberOfValidBranches == 0 )
> {
> // no branches, therefore 100% branch coverage.
> branchCoverRate = 1d;
> }
> else
> {
> branchCoverRate = (double) numberOfCoveredBranches /
> numberOfValidBranches;
> }
> if ( numberOfValidLines == 0 )
> {
> // no branches, therefore 100% branch coverage.
> lineCoverRate = 1d;
> }
> else
> {
>lineCoverRate = (double) numberOfCoveredLines /
> numberOfValidLines;
> }
> }
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] Commented: (MOJO-662) Line Cover Rate invalid calcul
[
http://jira.codehaus.org/browse/MOJO-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88790
]
David Vicente commented on MOJO-662:
yes, it's true.
i don't know how i have missed this error.
thxs
> Line Cover Rate invalid calcul
> ---
>
> Key: MOJO-662
> URL: http://jira.codehaus.org/browse/MOJO-662
> Project: Mojo
> Issue Type: Bug
> Components: dashboard
>Reporter: Brice Ruzand
> Assigned To: David Vicente
> Attachments: CoberturaReportBean.java
>
>
> in this classe :
> org.codehaus.mojo.dashboard.report.plugin.beans.CoberturaReportBean
> in method merge : calculation of lineCoverRate is missing
> methode with correction
> /**
> *
> * @param dashboardReport
> */
> public void merge( CoberturaReportBean dashboardReport )
> {
> if ( dashboardReport != null )
> {
> this.nbClasses = this.nbClasses + dashboardReport.getNbClasses();
> this.numberOfCoveredBranches = this.numberOfCoveredBranches +
> dashboardReport.getNumberOfCoveredBranches();
> this.numberOfCoveredLines = this.numberOfCoveredLines +
> dashboardReport.getNumberOfCoveredLines();
> this.numberOfValidBranches = this.numberOfValidBranches +
> dashboardReport.getNumberOfValidBranches();
> this.numberOfValidLines = this.numberOfValidLines +
> dashboardReport.getNumberOfValidLines();
> if ( numberOfValidBranches == 0 )
> {
> // no branches, therefore 100% branch coverage.
> branchCoverRate = 1d;
> }
> else
> {
> branchCoverRate = (double) numberOfCoveredBranches /
> numberOfValidBranches;
> }
> if ( numberOfValidLines == 0 )
> {
> // no branches, therefore 100% branch coverage.
> lineCoverRate = 1d;
> }
> else
> {
>lineCoverRate = (double) numberOfCoveredLines /
> numberOfValidLines;
> }
> }
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] Created: (MOJO-663) Update documentation to new docck standards
Update documentation to new docck standards --- Key: MOJO-663 URL: http://jira.codehaus.org/browse/MOJO-663 Project: Mojo Issue Type: Improvement Components: tomcat Reporter: Mark Hobson Need to overhaul documentation to move it in line with other plugins. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [vote] Release tomcat-maven-plugin 1.0-alpha-1
Hi there, I've had requests to move the Tomcat Maven plugin out of the sandbox and make a 1.0-alpha-1 release. There are a number of outstanding issues [1], but these will be addressed in future releases. +1 from me. Cheers, Mark [1] http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=11062&sorter/order=DESC&sorter/field=priority&resolution=-1&component=12116 - To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
Re: [mojo-dev] [vote] Release tomcat-maven-plugin 1.0-alpha-1
+1 On 2/28/07, Mark Hobson <[EMAIL PROTECTED]> wrote: Hi there, I've had requests to move the Tomcat Maven plugin out of the sandbox and make a 1.0-alpha-1 release. There are a number of outstanding issues [1], but these will be addressed in future releases. +1 from me. Cheers, Mark [1] http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=11062&sorter/order=DESC&sorter/field=priority&resolution=-1&component=12116 - To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
Re: [mojo-dev] [vote] Release tomcat-maven-plugin 1.0-alpha-1
+0 Raphaël 2007/2/28, Dan Tran <[EMAIL PROTECTED]>: +1 On 2/28/07, Mark Hobson <[EMAIL PROTECTED]> wrote: > > Hi there, > > I've had requests to move the Tomcat Maven plugin out of the sandbox > and make a 1.0-alpha-1 release. There are a number of outstanding > issues [1], but these will be addressed in future releases. > > +1 from me. > > Cheers, > > Mark > > [1] > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=11062&sorter/order=DESC&sorter/field=priority&resolution=-1&component=12116 > > - > To unsubscribe from this list please visit: > >http://xircles.codehaus.org/manage_email > >
[mojo-dev] [jira] Created: (MOJO-664) upgrade to AspectJ 1.5.3
upgrade to AspectJ 1.5.3 Key: MOJO-664 URL: http://jira.codehaus.org/browse/MOJO-664 Project: Mojo Issue Type: Improvement Components: aspectj Reporter: Ken Geis AspectJ 1.5.3 includes many fixes, including a much better memory profile. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
Re: [mojo-dev] [vote] Release tomcat-maven-plugin 1.0-alpha-1
+0 Is this the latest site content? http://mojo.codehaus.org/tomcat-maven-plugin/ --jason On Feb 28, 2007, at 10:35 AM, Mark Hobson wrote: Hi there, I've had requests to move the Tomcat Maven plugin out of the sandbox and make a 1.0-alpha-1 release. There are a number of outstanding issues [1], but these will be addressed in future releases. +1 from me. Cheers, Mark [1] http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=true&mode=hide&pid=11062&sorter/order=DESC&sorter/ field=priority&resolution=-1&component=12116 - To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email - To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
Re: [mojo-dev] [vote] Release tomcat-maven-plugin 1.0-alpha-1
+1 Kris On Wed, 2007-02-28 at 20:41 +0100, Raphaël Piéroni wrote: > +0 > > Raphaël > > 2007/2/28, Dan Tran <[EMAIL PROTECTED]>: > +1 > > > > On 2/28/07, Mark Hobson <[EMAIL PROTECTED]> wrote: > Hi there, > > I've had requests to move the Tomcat Maven plugin out > of the sandbox > and make a 1.0-alpha-1 release. There are a number of > outstanding > issues [1], but these will be addressed in future > releases. > > +1 from me. > > Cheers, > > Mark > > [1] > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=11062&sorter/order=DESC&sorter/field=priority&resolution=-1&component=12116 > > > - > To unsubscribe from this list please visit: > >http://xircles.codehaus.org/manage_email > > > > signature.asc Description: This is a digitally signed message part
[mojo-dev] is there a reverse engineering support in hibernate3 plugin.
i would like to use hibernate tools reverse engineering using this plugin. is the functionality already existing? Kathir. - To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] Closed: (CBUILDS-14) SCM-based C builds lifecycle
[ http://jira.codehaus.org/browse/CBUILDS-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed CBUILDS-14. - Assignee: John Casey Resolution: Fixed fixed and tested. > SCM-based C builds lifecycle > > > Key: CBUILDS-14 > URL: http://jira.codehaus.org/browse/CBUILDS-14 > Project: Mojo C Builds > Issue Type: New Feature > Components: Automake/Autoconfig Orchestration >Reporter: Roger Hoover > Assigned To: John Casey > Fix For: 1.0-alpha-4 > > > If you're building an autotools project from SCM, you'll need to run > autoreconf if you change any automake or autoconf files. Also, during the > release process, "make dist" needs to be run in order to generate the source > tarball artifact. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] Closed: (MCOBERTURA-62) 0% coverage being reported even though tests have run.
[ http://jira.codehaus.org/browse/MCOBERTURA-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Derek Clarkson closed MCOBERTURA-62. Resolution: Won't Fix Ok, not your issue. After some research I found that Cobertura only writes the files after the JVM closes down. I was running the tests within the same JVM so no data had been written to the file and therefore nothing was reported. I'm currently re-writing the plugin to fork a jvm so that the results can be written. There is documentation on the Cobertura site about how it writes data. > 0% coverage being reported even though tests have run. > -- > > Key: MCOBERTURA-62 > URL: http://jira.codehaus.org/browse/MCOBERTURA-62 > Project: Maven 2.x Cobertura Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: Both 2.1 and 2.0 releases. >Reporter: Derek Clarkson > > The plugin correctly instruments the code and puts the .ser file location > into the system properties. I then fire a custom plugin which runs JUnit4 > tests. It uses the instrumented classes in it's class path and runs all tests > correctly, producing output in it's report directory. The cobertura plugin > then generates it's reports which find 0% coverage. > Looking at the system the instrumentation, system property and reporting > phases all make reference to the /target/cobertura/cobertura.ser > file. Looking at the file it would appear that no data in being appended to > it when the test are being run. Apart from looking at the URLs passed to the > classloader running the test code I cannot see any way to confirm it is > running the instrumented code. BTW the urls are > /target/generated-classes and also > \.m2\repository\cobertura\cobertura\1.8\cobertura-1.8.jar > I've tried this same project with the 2.0 (cobertura 1.7) plugin and got the > same results. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] Closed: (MOJO-163) jalopy tests fail when project built from the mojo level
[ http://jira.codehaus.org/browse/MOJO-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johnny R. Ruiz III closed MOJO-163. --- Resolution: Fixed Cannot reproduce this issue > jalopy tests fail when project built from the mojo level > > > Key: MOJO-163 > URL: http://jira.codehaus.org/browse/MOJO-163 > Project: Mojo > Issue Type: Bug > Components: jalopy >Reporter: Matt Brozowski > Assigned To: Johnny R. Ruiz III > > When trying to build from the mojo level the jalopy tests fail > Here's the top of the exception that is thrown: > --- > T E S T S > --- > java.io.FileNotFoundException: > /Users/brozow/svn/mojo/jalopy-maven-plugin/src/test/resources/input/test/Circle.java > (No such file or directory) > at java.io.FileInputStream.open(Native Method) > at java.io.FileInputStream.(FileInputStream.java:106) > at > org.codehaus.mojo.jalopy.JalopyMojoTest.getTextContents(JalopyMojoTest.java:232) > at > org.codehaus.mojo.jalopy.JalopyMojoTest.compareTextFiles(JalopyMojoTest.java:205) > at > org.codehaus.mojo.jalopy.JalopyMojoTest.testExecute(JalopyMojoTest.java:108) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
