[VOTE] Release Fulcrum-Cache, Version 1.1

[Thomas Vandahl-2]

Hi folks,

(This is the first step in a number of component releases I've planned,
so expect some more of these vote calls)

I would like to ask whether the Fulcrum-Cache component should be
released. I have uploaded the artifacts to
http://people.apache.org/~tv/fulcrum/ namely

- Distributions to .
- Jars to jars/
- Poms to poms/
- The site to docs/


Please vote if you want these files to be released as Fulcrum-Cache,
Version 1.1

[ ] +1 Yes, these were due long ago
[ ] 0 I don't care
[ ] -1 No (give reasons)

The Vote ends on Saturday, June 14th 2008 13:00 CEST

Bye, Thomas.

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

[Thomas Vandahl-2]

Thomas Vandahl wrote:
> [X] +1 Yes, these were due long ago

Obviously.

Bye, Thomas.

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

[Siegfried Goeschl]

Hi Thomas,

[X] -1 No (give reasons)

If have issues regarding the M1 build

1) the maven-jcoverage-plugin call in maven.xml breaks my build since I
don't have the plugin installed (it is obsolete)

Some other minor thingies

2) are you using maven-1.1 or maven-1.0.2 - maven-1.1 complains about
the default goal defined in maven.xml
3) there are some minor PMD and JavaDoc issues regarding test sources
but for such a tiny project there shouldn't be any
4) in general I would recommend o use "major.minor.patch", i.e.
fulcrum-cache-1.1.0, to make versioning more consistent

I fixed the following issues

1) removed the plugin invocation
2) moved default goal to project.xml


Cheers,

Siegfried Goeschl

Thomas Vandahl wrote:

> Hi folks,
>
> (This is the first step in a number of component releases I've
> planned, so expect some more of these vote calls)
>
> I would like to ask whether the Fulcrum-Cache component should be
> released. I have uploaded the artifacts to
> http://people.apache.org/~tv/fulcrum/ namely
>
> - Distributions to .
> - Jars to jars/
> - Poms to poms/
> - The site to docs/
>
>
> Please vote if you want these files to be released as Fulcrum-Cache,
> Version 1.1
>
> [ ] +1 Yes, these were due long ago
> [ ] 0 I don't care
> [ ] -1 No (give reasons)
>
> The Vote ends on Saturday, June 14th 2008 13:00 CEST
>
> Bye, Thomas.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>
>

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

[Siegfried Goeschl]

Hi Thomas,

I have a problem understanding the dependencies (snippet from the pom.xml)

    <dependency>
      <groupId>commons-collections</groupId>
      <artifactId>commons-collections</artifactId>
      <version>3.1</version>
    </dependency>
    <dependency>
      <groupId>commons-logging</groupId>
      <artifactId>commons-logging</artifactId>
      <version>1.0.4</version>
    </dependency>
    <dependency>
      <groupId>concurrent</groupId>
      <artifactId>concurrent</artifactId>
      <version>1.3.4</version>
    </dependency>

Are this dependencies belonging to JCS and/or EHCache?

Thanks in advance

Siegfried Goeschl

Siegfried Goeschl wrote:

> Hi Thomas,
>
> [X] -1 No (give reasons)
>
> If have issues regarding the M1 build
>
> 1) the maven-jcoverage-plugin call in maven.xml breaks my build since
> I don't have the plugin installed (it is obsolete)
>
> Some other minor thingies
>
> 2) are you using maven-1.1 or maven-1.0.2 - maven-1.1 complains about
> the default goal defined in maven.xml
> 3) there are some minor PMD and JavaDoc issues regarding test sources
> but for such a tiny project there shouldn't be any
> 4) in general I would recommend o use "major.minor.patch", i.e.
> fulcrum-cache-1.1.0, to make versioning more consistent
>
> I fixed the following issues
>
> 1) removed the plugin invocation
> 2) moved default goal to project.xml
>
>
> Cheers,
>
> Siegfried Goeschl
>
> Thomas Vandahl wrote:
>> Hi folks,
>>
>> (This is the first step in a number of component releases I've
>> planned, so expect some more of these vote calls)
>>
>> I would like to ask whether the Fulcrum-Cache component should be
>> released. I have uploaded the artifacts to
>> http://people.apache.org/~tv/fulcrum/ namely
>>
>> - Distributions to .
>> - Jars to jars/
>> - Poms to poms/
>> - The site to docs/
>>
>>
>> Please vote if you want these files to be released as Fulcrum-Cache,
>> Version 1.1
>>
>> [ ] +1 Yes, these were due long ago
>> [ ] 0 I don't care
>> [ ] -1 No (give reasons)
>>
>> The Vote ends on Saturday, June 14th 2008 13:00 CEST
>>
>> Bye, Thomas.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>
>

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

[Thomas Vandahl-2]

Hi Siegfried,

Siegfried Goeschl wrote:
> 2) are you using maven-1.1 or maven-1.0.2 - maven-1.1 complains about
> the default goal defined in maven.xml

A bit picky, are we? :-)

> 3) there are some minor PMD and JavaDoc issues regarding test sources
> but for such a tiny project there shouldn't be any

I don't see any PMD issues in the PMD report at
http://people.apache.org/~tv/fulcrum/docs/pmd-report.html If you used
another PMD tool, what settings did you use?

Bye, Thomas.


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

[Thomas Vandahl-2]

Siegfried Goeschl wrote:

> Hi Thomas,
>
> I have a problem understanding the dependencies (snippet from the pom.xml)
>
>    <dependency>
>      <groupId>commons-collections</groupId>
>      <artifactId>commons-collections</artifactId>
>      <version>3.1</version>
>    </dependency>
>    <dependency>
>      <groupId>commons-logging</groupId>
>      <artifactId>commons-logging</artifactId>
>      <version>1.0.4</version>
>    </dependency>

These belong to EHCache. The references at
http://ehcache.sourceforge.net/dependencies.html are somewhat different
but apply to later versions (which are not in the Apache Maven Repo)

>    <dependency>
>      <groupId>concurrent</groupId>
>      <artifactId>concurrent</artifactId>
>      <version>1.3.4</version>
>    </dependency>
JCS. According to http://jakarta.apache.org/jcs/dependencies.html there
are more but they will only be needed if certain plugins are configured.

Bye, Thomas

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

[Siegfried Goeschl]

Hi Thomas,

sorry if I sound like a complete a**hole but I *hate* build scripts
printing warnings and deprecation. The warning is the bug you chase next
week and the deprecation is the broken build in two months time ... :-(

Since today is my Open Source Day I' will have a look at the PMD issue
you don't have ...

Siegfried Goeschl

Thomas Vandahl wrote:

> Hi Siegfried,
>
> Siegfried Goeschl wrote:
>> 2) are you using maven-1.1 or maven-1.0.2 - maven-1.1 complains about
>> the default goal defined in maven.xml
>
> A bit picky, are we? :-)
>
>> 3) there are some minor PMD and JavaDoc issues regarding test sources
>> but for such a tiny project there shouldn't be any
>
> I don't see any PMD issues in the PMD report at
> http://people.apache.org/~tv/fulcrum/docs/pmd-report.html If you used
> another PMD tool, what settings did you use?
>
> Bye, Thomas.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>
>

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

[Thomas Vandahl-2]

Siegfried Goeschl wrote:
> Hi Thomas,
>
> sorry if I sound like a complete a**hole but I *hate* build scripts
> printing warnings and deprecation. The warning is the bug you chase next
> week and the deprecation is the broken build in two months time ... :-(

Yes, I have to admit that parts of my spinal chord were thinking in that
direction... Anyway, we are talking about a maven-plugin that has been
around for years and will not stop to be around just because it may be
obsolete. After all, it's not the plugin we vote about but the artifact.

> Since today is my Open Source Day I' will have a look at the PMD issue
> you don't have ...

Just a side comment: I would not spent too much effort removing *all*
PMD warnings. Some of them are plain silly. Once more: I see no warnings
in the PMD report at the site. Does your PMD-plugin do different things
than mine?

>> Siegfried Goeschl wrote:
>>> 2) are you using maven-1.1 or maven-1.0.2 - maven-1.1 complains about
>>> the default goal defined in maven.xml

The build was done using maven 1.0.2. This version needs the default
goal in maven.xml. So you are telling me that I should break my build to
remove a warning in yours?

Bye, Thomas.

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

[Thomas Vandahl-2]

Thomas Vandahl wrote:

> Hi folks,
>
> (This is the first step in a number of component releases I've planned,
> so expect some more of these vote calls)
>
> I would like to ask whether the Fulcrum-Cache component should be
> released. I have uploaded the artifacts to
> http://people.apache.org/~tv/fulcrum/ namely
>
> - Distributions to .
> - Jars to jars/
> - Poms to poms/
> - The site to docs/

Ok, this attempt went south. The vote results are:

+1:
Thomas Vandahl (PMC)

0:
none

-1:
Siegfried Goeschl (PMC)

So the artifact will *not* be released. Thanks to all the voters.

Bye, Thomas.


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

[Siegfried Goeschl]

Hi Thomas,

I'm revoking my comments and my "-1"  ... :-(

+) the maven-jcoverage-plugin is in my repo and is used suddenly used by
maven-1.1
+) maven-1.0.2 seems to ignore the default target defined in the
project.xml but maven-1.1 issues a deprecation warning
+) I'm also not able to reproduce the PMD issues either

As a side note - I accidentally setup maven-1.0.2 and maven-1.1 to use
the same local repository and it seems that causes me some problems
(e.g. unable to generate a valid idea project file on the one box but
not on the other). I will need to cleanly separate those instances
before making statements such as "the build is broken"  - AFAIK there is
no way to nail down the plugin dependencies so the build can fail on a
box unexpectedly. One more reason to push M2 ...


PS: Having said that I'm pretty sure that a maven-1.1 user with a clean
repository is unable to build the site so I would recommed not to use
the maven-jcoverage-plugin


Thomas Vandahl wrote:

> Siegfried Goeschl wrote:
>> Hi Thomas,
>>
>> sorry if I sound like a complete a**hole but I *hate* build scripts
>> printing warnings and deprecation. The warning is the bug you chase
>> next week and the deprecation is the broken build in two months time
>> ... :-(
>
> Yes, I have to admit that parts of my spinal chord were thinking in
> that direction... Anyway, we are talking about a maven-plugin that has
> been around for years and will not stop to be around just because it
> may be obsolete. After all, it's not the plugin we vote about but the
> artifact.
>
>> Since today is my Open Source Day I' will have a look at the PMD
>> issue you don't have ...
>
> Just a side comment: I would not spent too much effort removing *all*
> PMD warnings. Some of them are plain silly. Once more: I see no
> warnings in the PMD report at the site. Does your PMD-plugin do
> different things than mine?
>
>>> Siegfried Goeschl wrote:
>>>> 2) are you using maven-1.1 or maven-1.0.2 - maven-1.1 complains
>>>> about the default goal defined in maven.xml
>
> The build was done using maven 1.0.2. This version needs the default
> goal in maven.xml. So you are telling me that I should break my build
> to remove a warning in yours?
>
> Bye, Thomas.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>
>

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

[Siegfried Goeschl]

Hi Thomas,

verified the "maven-joverage-plugin" bit - a site build using maven-1.1
does not work

cache> maven clean site
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.1

DEPRECATED: the default goal should be specified in the <build> section
of project.xml instead of maven.xml
build:start:

clean:clean:
xdoc:clean:

-------------------------------------------------------------------------------
 >> Unable to obtain goal [site]
 >> No goal [maven-jcoverage-plugin:deregister]
-------------------------------------------------------------------------------
BUILD FAILED
-------------------------------------------------------------------------------
Total time   : 1 seconds
Finished at  : Monday, June 16, 2008 1:20:38 PM CEST
Final Memory : 3M/6M
-----------------------------


Siegfried Goeschl wrote:

> Hi Thomas,
>
> I'm revoking my comments and my "-1"  ... :-(
>
> +) the maven-jcoverage-plugin is in my repo and is used suddenly used
> by maven-1.1
> +) maven-1.0.2 seems to ignore the default target defined in the
> project.xml but maven-1.1 issues a deprecation warning
> +) I'm also not able to reproduce the PMD issues either
>
> As a side note - I accidentally setup maven-1.0.2 and maven-1.1 to use
> the same local repository and it seems that causes me some problems
> (e.g. unable to generate a valid idea project file on the one box but
> not on the other). I will need to cleanly separate those instances
> before making statements such as "the build is broken"  - AFAIK there
> is no way to nail down the plugin dependencies so the build can fail
> on a box unexpectedly. One more reason to push M2 ...
>
>
> PS: Having said that I'm pretty sure that a maven-1.1 user with a
> clean repository is unable to build the site so I would recommed not
> to use the maven-jcoverage-plugin
>
>
> Thomas Vandahl wrote:
>> Siegfried Goeschl wrote:
>>> Hi Thomas,
>>>
>>> sorry if I sound like a complete a**hole but I *hate* build scripts
>>> printing warnings and deprecation. The warning is the bug you chase
>>> next week and the deprecation is the broken build in two months time
>>> ... :-(
>>
>> Yes, I have to admit that parts of my spinal chord were thinking in
>> that direction... Anyway, we are talking about a maven-plugin that
>> has been around for years and will not stop to be around just because
>> it may be obsolete. After all, it's not the plugin we vote about but
>> the artifact.
>>
>>> Since today is my Open Source Day I' will have a look at the PMD
>>> issue you don't have ...
>>
>> Just a side comment: I would not spent too much effort removing *all*
>> PMD warnings. Some of them are plain silly. Once more: I see no
>> warnings in the PMD report at the site. Does your PMD-plugin do
>> different things than mine?
>>
>>>> Siegfried Goeschl wrote:
>>>>> 2) are you using maven-1.1 or maven-1.0.2 - maven-1.1 complains
>>>>> about the default goal defined in maven.xml
>>
>> The build was done using maven 1.0.2. This version needs the default
>> goal in maven.xml. So you are telling me that I should break my build
>> to remove a warning in yours?
>>
>> Bye, Thomas.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>
>

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

[Thomas Vandahl]

Siegfried Goeschl wrote:
> I'm revoking my comments and my "-1"  ... :-(

Thanks. But even this wouldn't help because we need 3 positive votes...

Bye, Thomas.


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

[seade]

A third vote isn't too far away...  I will try and take a look in the
next few days.

Scott

Thomas Vandahl wrote:

> Siegfried Goeschl wrote:
>> I'm revoking my comments and my "-1"  ... :-(
>
> Thanks. But even this wouldn't help because we need 3 positive votes...
>
> Bye, Thomas.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

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

[seade]

I have finally got around to looking at fulcrum-cache.  I have made a
couple of minor tweaks to the pom to help the m2 builds along.

You will also see that I switched to net.sf.ehcache:ehcache-1.2.4 - this
is a little more recent than the 1.2beta4 release that was previously in
use and is available in both the m1 and m2 repositories.  If we scrap
the m1 builds we can run with the much more current 1.4.1 release.

Scott

Scott Eade wrote:

> A third vote isn't too far away...  I will try and take a look in the
> next few days.
>
> Scott
>
> Thomas Vandahl wrote:
>> Siegfried Goeschl wrote:
>>> I'm revoking my comments and my "-1"  ... :-(
>>
>> Thanks. But even this wouldn't help because we need 3 positive votes...
>>
>> Bye, Thomas.
>>
>

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

[Thomas Vandahl-2]

Scott Eade wrote:
> You will also see that I switched to net.sf.ehcache:ehcache-1.2.4 - this
> is a little more recent than the 1.2beta4 release that was previously in
> use and is available in both the m1 and m2 repositories.  If we scrap
> the m1 builds we can run with the much more current 1.4.1 release.

The last time I checked (just before calling the vote), the latest
version available int the Apache-M1-Repo was 1.2beta4. Where did you get
that from?

Bye, Thomas.


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

[seade]

Thomas Vandahl wrote:

> Scott Eade wrote:
>> You will also see that I switched to net.sf.ehcache:ehcache-1.2.4 -
>> this is a little more recent than the 1.2beta4 release that was
>> previously in use and is available in both the m1 and m2
>> repositories.  If we scrap the m1 builds we can run with the much
>> more current 1.4.1 release.
>
> The last time I checked (just before calling the vote), the latest
> version available int the Apache-M1-Repo was 1.2beta4. Where did you
> get that from?

I appears they changed their groupId:
>      <dependency>
> -      <groupId>ehcache</groupId>
> +      <groupId>net.sf.ehcache</groupId>
>        <artifactId>ehcache</artifactId>
> -      <version>1.2beta4</version>
> +      <version>1.2.4</version>
>      </dependency>
>  
Scott

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