maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Carpenter (JIRA)" <j...@codehaus.org>
Subject [jira] Created: (MNG-4434) Incorrect spam filter applied by dev@mojo.codehaus.org on my nawkboy@gmail.com account.
Date Tue, 10 Nov 2009 16:30:55 GMT
Incorrect spam filter applied by dev@mojo.codehaus.org on my nawkboy@gmail.com account.
---------------------------------------------------------------------------------------

                 Key: MNG-4434
                 URL: http://jira.codehaus.org/browse/MNG-4434
             Project: Maven 2
          Issue Type: Task
            Reporter: James Carpenter


I sent a post to dev@mojo.codehaus.org via a nawkboy@gmail.com account I use just for mailing
lists.  Shortly after signing onto the mailing list I sent the email below.  Unfortunately,
it appears it was blocked by a spam filter of some sort as it never showed up on the mailing
list.  Can someone please add my email to a whitelist and/or otherwise instruct the spam filter
to let it through?

---------- Forwarded message ----------
From: James Carpenter <nawkboy@gmail.com>
Date: Mon, Nov 2, 2009 at 2:02 PM
Subject: Request to push a new release with MCOBERTURA-114 patch
To: dev@mojo.codehaus.org


Assuming the maintainers are comfortable with the changes, when can I reasonably expect an
official release version of the plugin which contains my changes submitted with MCOBERTURA-114?

Background:
It is occasionally useful to measure the code coverage for manual and/or automated tests which
run against a test environment.

(Not to be confused with measuring code coverage of unit tests executed automatically by the
build system.)  For example, you may have a set of automated regression tests written using
JMeter, Selenium, etc. which for some reason or another are not appropriate to run as part
of the maven build.


To this end I have created a patch which greatly enhances the documentation needed to guide
a user for this use case. I have also extended the instrument goal to support registering
a module's cobertura.ser file as an attached artifact.  This turns out to significantly clean
up the child modules of a multi-module project, which would otherwise be cluttered with build-helper
plugin configuration details.

For more details, I recommend you read the PDF attached to MCOBERTURA-114 which shows the
html rendered version of the enhanced documentation.

I have also included some scans of hand-drawn diagrams I drew to complement the text.  The
documentation text in the patch does not currently link to or otherwise include the hand-drawn
diagrams.  I created the hand-drawn diagrams for use inside my company after I had finished
creating the patch.

Related Link: http://jira.codehaus.org/browse/MCOBERTURA-114

Sincerely,
James Carpenter
email: jcarpenter621@yahoo.pleaseremoveme.com

-- 
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

        

Mime
View raw message