Re: Clover version; release new project POM
On 8 February 2011 20:17, Oleg Kalnichevski wrote: > On Tue, 2011-02-08 at 19:23 +, sebb wrote: > >> > >> > And I know I used 3.0.2 to generate the data as well (the 2.6.3 >> > database is not compatible with 3.0.2). >> >> I've just tried running with 2.6.2, 3.0.1 and 3.0.2 and they all seem >> to work with the 2.6.3 license, for example: >> >> [INFO] Clover Version 3.0.1, built on March 31 2010 (build-787) >> [INFO] Clover: Open Source License registered to Apache. >> > > Hhm. That never worked for me for some reason. I have the following in my settings.xml: clover true D:\eclipseworkspaces\main\clover.license and the clover.license file is the one donated to the ASF. > Oleg > > > > - > 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]
Re: Clover version; release new project POM
On Tue, 2011-02-08 at 19:23 +, sebb wrote: > > > > And I know I used 3.0.2 to generate the data as well (the 2.6.3 > > database is not compatible with 3.0.2). > > I've just tried running with 2.6.2, 3.0.1 and 3.0.2 and they all seem > to work with the 2.6.3 license, for example: > > [INFO] Clover Version 3.0.1, built on March 31 2010 (build-787) > [INFO] Clover: Open Source License registered to Apache. > Hhm. That never worked for me for some reason. Oleg - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Re: Clover version; release new project POM
On 8 February 2011 19:04, sebb wrote: > On 8 February 2011 18:52, sebb wrote: >> On 8 February 2011 17:07, Oleg Kalnichevski wrote: >>> "sebb" wrote: >>> I had some problems generating the site, because the build phase was using clover 2.6.3, whereas the report phase was using the latest Clover which is currently 3.0.2. I've added a property clover.version (3.0.2) to the project POM. It would be nice to be able to add the clover plugin details to the reporting section of the project POM, but AFAIK, that will force clover to be run for all modules, which we don't want. So it looks like all the child POMs that have clover in the reporting section will need the version to be added. I guess this also means that we need to release the project POM - need to do that anyway for the skin updates. I'm happy to RM them both. - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] >>> >>> Sebastian, >>> >>> ASF does not have a license for the latest version of Clover. This is the >>> reason poms used version 2.6.3. >> >> I see, in which case I'll change the version back. >> But in any case, the version needs to be specified in the reporting >> section as well. >> >> But I was able to run version 3.0.2 earlier, and I did not notice a >> problem with the licence. >> I need to investigate further. > > Weird. > > The licence I'm using is definitely the one we were given for 2.6.3, > yet the report I generated says: > > Clover Report generated by Clover Code Coverage v3.0.2 > Tue Feb 8 2011 17:01:53 GMT. Clover: Open Source License > registered to Apache. > > And I know I used 3.0.2 to generate the data as well (the 2.6.3 > database is not compatible with 3.0.2). I've just tried running with 2.6.2, 3.0.1 and 3.0.2 and they all seem to work with the 2.6.3 license, for example: [INFO] Clover Version 3.0.1, built on March 31 2010 (build-787) [INFO] Clover: Open Source License registered to Apache. It's easy enough to override the version (-Dclover.version=3.0.2) if required, so I've left the setting for now. > I've reverted the POM to 2.6.3 for now. > >>> - >>> 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]
Re: Clover version; release new project POM
On 8 February 2011 18:52, sebb wrote: > On 8 February 2011 17:07, Oleg Kalnichevski wrote: >> "sebb" wrote: >> >>>I had some problems generating the site, because the build phase was >>>using clover 2.6.3, whereas the report phase was using the latest >>>Clover which is currently 3.0.2. >>> >>>I've added a property clover.version (3.0.2) to the project POM. >>>It would be nice to be able to add the clover plugin details to the >>>reporting section of the project POM, but AFAIK, that will force >>>clover to be run for all modules, which we don't want. >>> >>>So it looks like all the child POMs that have clover in the reporting >>>section will need the version to be added. >>> >>>I guess this also means that we need to release the project POM - need >>>to do that anyway for the skin updates. >>> >>>I'm happy to RM them both. >>> >>>- >>>To unsubscribe, e-mail: [email protected] >>>For additional commands, e-mail: [email protected] >> >> Sebastian, >> >> ASF does not have a license for the latest version of Clover. This is the >> reason poms used version 2.6.3. > > I see, in which case I'll change the version back. > But in any case, the version needs to be specified in the reporting > section as well. > > But I was able to run version 3.0.2 earlier, and I did not notice a > problem with the licence. > I need to investigate further. Weird. The licence I'm using is definitely the one we were given for 2.6.3, yet the report I generated says: Clover Report generated by Clover Code Coverage v3.0.2 Tue Feb 8 2011 17:01:53 GMT.Clover: Open Source License registered to Apache. And I know I used 3.0.2 to generate the data as well (the 2.6.3 database is not compatible with 3.0.2). I've reverted the POM to 2.6.3 for now. >> - >> 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]
Re: Clover version; release new project POM
On 8 February 2011 17:07, Oleg Kalnichevski wrote: > "sebb" wrote: > >>I had some problems generating the site, because the build phase was >>using clover 2.6.3, whereas the report phase was using the latest >>Clover which is currently 3.0.2. >> >>I've added a property clover.version (3.0.2) to the project POM. >>It would be nice to be able to add the clover plugin details to the >>reporting section of the project POM, but AFAIK, that will force >>clover to be run for all modules, which we don't want. >> >>So it looks like all the child POMs that have clover in the reporting >>section will need the version to be added. >> >>I guess this also means that we need to release the project POM - need >>to do that anyway for the skin updates. >> >>I'm happy to RM them both. >> >>- >>To unsubscribe, e-mail: [email protected] >>For additional commands, e-mail: [email protected] > > Sebastian, > > ASF does not have a license for the latest version of Clover. This is the > reason poms used version 2.6.3. I see, in which case I'll change the version back. But in any case, the version needs to be specified in the reporting section as well. But I was able to run version 3.0.2 earlier, and I did not notice a problem with the licence. I need to investigate further. > - > 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]
Re: Clover version; release new project POM
"sebb" wrote: >I had some problems generating the site, because the build phase was >using clover 2.6.3, whereas the report phase was using the latest >Clover which is currently 3.0.2. > >I've added a property clover.version (3.0.2) to the project POM. >It would be nice to be able to add the clover plugin details to the >reporting section of the project POM, but AFAIK, that will force >clover to be run for all modules, which we don't want. > >So it looks like all the child POMs that have clover in the reporting >section will need the version to be added. > >I guess this also means that we need to release the project POM - need >to do that anyway for the skin updates. > >I'm happy to RM them both. > >- >To unsubscribe, e-mail: [email protected] >For additional commands, e-mail: [email protected] Sebastian, ASF does not have a license for the latest version of Clover. This is the reason poms used version 2.6.3. - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
