You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by eBay Customer Support <no...@ebay.com> on 2005/03/08 23:59:53 UTC

RE: [VOTE] Releasing CruiseControl plugin v1.7? (KMM158504026V22743L0KM)

Hello,

Thank you for writing to eBay. My name is Fenton. 

I have now received seven emails regarding this 'CruiseControl' issue. I
would like to inform you that you are writing to eBay's Trust & Safety 
department. If you have an issue with an eBay transaction, I ask that 
you clearly state your issue, otherwise I would ask that you remove us 
from your mailing list regarding this software development. 

This is for both your security and privacy for the software, as well as 
my time that has been spent reading your communication. 

Thanks again for writing, and thank you for being part of the eBay 
community.

Kind Regards

Fenton
Fraud Prevention Group
_____________________________________________________________





Original Message Follows:
-------------------------

My previous email about CC and CVSROOT went out today, I wrote it a
couple days ago, not sure why it didn't send.  At any rate, I just
committed my fix, based on someone else finding the same issue, and I'll
work on the failing plugin tests tonight.
Eric
-----Original Message-----
From: Eric Pugh [mailto:epugh@upstate.com] 
Sent: Tuesday, March 08, 2005 3:06 PM
To: 'Maven Developers List'
Subject: RE: [VOTE] Releasing CruiseControl plugin v1.7?
-1
Plugin tests are failing!  I know we don't run them much, but I noticed
that Brett commented out the cruisecontrol plugin:test from being run as
part of the main Maven build, and that feels like a real "mark of
shame".  
Would it be possible to hold on till the end of this week?  I just fixed
a bug with setting up CVSROOT's and would like a day or two to test it
on my production systems.  I am also working on a small tweak to make
creating your own cruisecontrol.jsl a bit easier.  Right now I jump
through odd hoops to get my own cruisecontrol.jsl to load, and would
like to simplify and document it a bit more.
If you really need the 1.7 release this week, then my tweak can wait for
1.8, if you can just review my bugfix for the CVSROOT and ${url}
property, and we agree that plugin:test doesn't have to pass, then I'll
change my -1 to a -0.  Otherwise, I hope to get done in the next two
days fixing the plugin tests.
ERic
-----Original Message-----
From: Arnaud HERITIER [mailto:aheritier@gmail.com] 
Sent: Sunday, March 06, 2005 5:10 PM
To: 'Maven Developers List'
Subject: RE: [VOTE] Releasing CruiseControl plugin v1.7?
+1
Arnaud
> -----Message d'origine-----
> De : Vincent Massol [mailto:vmassol@pivolis.com]
> Envoy� : dimanche 6 mars 2005 22:02
> � : 'Maven Developers List'
> Objet : [VOTE] Releasing CruiseControl plugin v1.7?
> 
> Hi,
> 
> I'd like to release the CC plugin v1.7. Here are the changes brought 
> since
> v1.6:
> 
>       <action dev="vmassol" type="update">
>         Removed all dependencies on the SCM module and instead replace
> all
>         occurrences with <code>${pom.artifactId}</code>.
>       </action>
>       <action dev="vmassol" type="add">
>         Added new <code>cruisecontrol:configure-war</code>
> goal that generates
>         a configured CruiseControl webapp WAR.
>       </action>
>       <action dev="vmassol" type="update">
>         Use the same default value for the 
>         <code>maven.cruisecontrol.mail.buildresultsurl</code> property
>         than the one for 
> <code>maven.cruisecontrol.buildresults.url</code>.
>       </action>
>       <action dev="vmassol" type="update">
>         Modified default value of
> <code>maven.cruisecontrol.logs.mergedirectory</code>
>         so that CC can aggregate JUnit test reports both for 
> single project and
>         multiproject setups.
>       </action>
>       <action dev="vmassol" type="update">
>         Compute automatically the merge directory automatically (the 
>         value of <code>maven.cruisecontrol.logs.mergedirectory</code>
>         if not specified by the user. The computation uses the
>         <code>maven.build.dir</code> property to guess the output
>         directory for JUnit test results.
>       </action>
>       <action dev="vmassol" type="add">
>         Added a new 
> <code>maven.cruisecontrol.logs.pattern</code> property
>         to specify the report files that will be merged by 
> CC. Defaults to
>         <code>*.xml</code>.
>       </action>
>       <action dev="vmassol" type="add">
>         Added a new <code>cruisecontrol:install-local</code> goal
>         to install the generated CC config to a target location on 
>         the same machine (it uses a file copy). In the future we could
>         provide other installation mechanisms like ssh, scp, etc.
>       </action>
>       <action dev="vmassol" type="update">
>         Changed the default build status file name to be 
>         <code>status.txt</code> which is the default value
>         expected by the CC Webapp.
>       </action>
>       <action dev="vmassol" type="update">
>         New <code>maven.cruisecontrol.work.dir</code> 
> property that specifies
>         what CC work directory to use for the project. 
> Default values of
>         <code>maven.cruisecontrol.checkout.dir</code> and 
>         <code>maven.cruisecontrol.logs.dir</code> have been 
> modified to be
>         relative to it.
>       </action>
>       <action dev="vmassol" type="fix">
>         Fixed default property values for 
> <code>maven.cruisecontrol.mail.xlsdir</code>
>         and <code>maven.cruisecontrol.mail.css</code> so that 
> the plugin works by default
>         with the latest CC version (2.2.1).
>       </action>
>       <action dev="vmassol" type="fix" issue="MPCRUISECONTROL-19">
>         Fix order in which the CruiseControl's 
> <code>&lt;project&gt;</code>
>         elements are generated. They must be in the order of the less
>         dependent project first.        
>       </action>
> 
> Here's my +1
> 
> Thanks
> -Vincent
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For 
> additional commands, e-mail: dev-help@maven.apache.org
> 
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org