Hm... the following should work (as a test at least) but does not:
Index: pom.xml
===================================================================
--- pom.xml (revision 1631900)
+++ pom.xml (working copy)
@@ -26,7 +26,8 @@
<version>34</version>
</parent>
- <artifactId>commons-jcs</artifactId>
+ <groupId>org.apache.commons</groupId>
+ <artifactId>commons-jcs-parent</artifactId>
<packaging>pom</packaging>
<version>2.0-SNAPSHOT</version>
Index: commons-jcs-core/pom.xml
===================================================================
--- commons-jcs-core/pom.xml (revision 1631899)
+++ commons-jcs-core/pom.xml (working copy)
@@ -23,12 +23,13 @@
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.apache.commons</groupId>
- <artifactId>commons-jcs</artifactId>
+ <artifactId>commons-jcs-parent</artifactId>
<version>2.0-SNAPSHOT</version>
<relativePath>../pom.xml</relativePath>
</parent>
- <artifactId>commons-jcs-core</artifactId>
+ <groupId>org.apache.jcs</groupId>
+ <artifactId>jcs</artifactId>
<packaging>jar</packaging>
<name>Apache Commons JCS :: Core</name>
Index: commons-jcs-jcache/pom.xml
===================================================================
--- commons-jcs-jcache/pom.xml (revision 1631899)
+++ commons-jcs-jcache/pom.xml (working copy)
@@ -24,7 +24,7 @@
<parent>
<groupId>org.apache.commons</groupId>
- <artifactId>commons-jcs</artifactId>
+ <artifactId>commons-jcs-parent</artifactId>
<version>2.0-SNAPSHOT</version>
<relativePath>../pom.xml</relativePath>
</parent>
Index: commons-jcs-jcache-extras/pom.xml
===================================================================
--- commons-jcs-jcache-extras/pom.xml (revision 1631899)
+++ commons-jcs-jcache-extras/pom.xml (working copy)
@@ -21,8 +21,8 @@
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
<parent>
- <artifactId>commons-jcs</artifactId>
<groupId>org.apache.commons</groupId>
+ <artifactId>commons-jcs-parent</artifactId>
<version>2.0-SNAPSHOT</version>
</parent>
<modelVersion>4.0.0</modelVersion>
Index: commons-jcs-jcache-openjpa/pom.xml
===================================================================
--- commons-jcs-jcache-openjpa/pom.xml (revision 1631899)
+++ commons-jcs-jcache-openjpa/pom.xml (working copy)
@@ -21,8 +21,8 @@
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
<parent>
- <artifactId>commons-jcs</artifactId>
<groupId>org.apache.commons</groupId>
+ <artifactId>commons-jcs-parent</artifactId>
<version>2.0-SNAPSHOT</version>
</parent>
<modelVersion>4.0.0</modelVersion>
Index: commons-jcs-tck-tests/pom.xml
===================================================================
--- commons-jcs-tck-tests/pom.xml (revision 1631899)
+++ commons-jcs-tck-tests/pom.xml (working copy)
@@ -24,7 +24,7 @@
<parent>
<groupId>org.apache.commons</groupId>
- <artifactId>commons-jcs</artifactId>
+ <artifactId>commons-jcs-parent</artifactId>
<version>2.0-SNAPSHOT</version>
<relativePath>../pom.xml</relativePath>
</parent>
Index: sandbox/pom.xml
===================================================================
--- sandbox/pom.xml (revision 1631899)
+++ sandbox/pom.xml (working copy)
@@ -23,7 +23,7 @@
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.apache.commons</groupId>
- <artifactId>commons-jcs</artifactId>
+ <artifactId>commons-jcs-parent</artifactId>
<version>2.0-SNAPSHOT</version>
</parent>
Gary
On Tue, Oct 14, 2014 at 7:39 PM, Gary Gregory <[email protected]>
wrote:
> If I change to POMs to use org.apache.jcs|jcs for the parent POM and
> org.apache.jcs|jcs as the parent of the modules, I get no reports from "mvn
> clirr:check" of course since org.apache.jcs|jcs is now a POM POM (!) in JCS
> 2.0 as opposed to a Jar POM in 1.3.
>
> Gary
>
> On Tue, Oct 14, 2014 at 7:29 PM, Gary Gregory <[email protected]>
> wrote:
>
>> [Sebb: I added you to this discussion as I am not sure how to get JCS 2.0
>> to have the same Maven coors as 1.3 since it is now a multi-module project].
>>
>> So it sounds like we should change the Maven coords to what they were for
>> 1.3.
>>
>> But 1.3 was one jar and one POM (
>> http://search.maven.org/#artifactdetails|org.apache.jcs|jcs|1.3|pom)
>>
>> What does that mean in 2.0 since we have 4 main modules? They cannot all
>> be called org.apache.jcs|jcs.
>>
>> Is calling the JCS parent POM org.apache.jcs|jcs enough to do the trick?
>>
>> Gary
>>
>> On Tue, Oct 14, 2014 at 6:58 PM, Romain Manni-Bucau <
>> [email protected]> wrote:
>>
>>> about api: public api shouldn't be broken (well the one which is
>>> broken shouldn't be used in code but only in config/properties files).
>>>
>>> about logging: we stated we'll not switch now but that we'll tackle it
>>> for 2.0.0. If we want log4j2 as default I'll fight to get a facade
>>> since jcs is already integrated in tomee (with the snapshot) and tomee
>>> will not bring log4j2 by default (to let apps do what they want as
>>> much as possible without any side effects on config or classloading).
>>> As you guess it will be a "nice" thread so surely not the moment to
>>> start it again ;).
>>>
>>>
>>> Romain Manni-Bucau
>>> @rmannibucau
>>> http://www.tomitribe.com
>>> http://rmannibucau.wordpress.com
>>> https://github.com/rmannibucau
>>>
>>>
>>> 2014-10-15 0:14 GMT+02:00 Gary Gregory <[email protected]>:
>>> > Now that Log4j 2 (2.0.2) is out and can be considered to deprecate
>>> Commons
>>> > Logging since it provides a nice API module, should we switch to it?
>>> >
>>> > Gary
>>> >
>>> > On Tue, Oct 14, 2014 at 4:23 PM, Romain Manni-Bucau <
>>> [email protected]>
>>> > wrote:
>>> >
>>> >> Hello guys,
>>> >>
>>> >> seems we are good regarding dependencies now
>>> >>
>>> >> do we try a release this week? 2.0-alpha-1? Anything blocking?
>>> >>
>>> >>
>>> >> Romain Manni-Bucau
>>> >> @rmannibucau
>>> >> http://www.tomitribe.com
>>> >> http://rmannibucau.wordpress.com
>>> >> https://github.com/rmannibucau
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: [email protected]
>>> >> For additional commands, e-mail: [email protected]
>>> >>
>>> >>
>>> >
>>> >
>>> > --
>>> > E-Mail: [email protected] | [email protected]
>>> > Java Persistence with Hibernate, Second Edition
>>> > <http://www.manning.com/bauer3/>
>>> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>>> > Spring Batch in Action <http://www.manning.com/templier/>
>>> > Blog: http://garygregory.wordpress.com
>>> > Home: http://garygregory.com/
>>> > Tweet! http://twitter.com/GaryGregory
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>>
>>
>>
>> --
>> E-Mail: [email protected] | [email protected]
>> Java Persistence with Hibernate, Second Edition
>> <http://www.manning.com/bauer3/>
>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>> Spring Batch in Action <http://www.manning.com/templier/>
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>>
>
>
>
> --
> E-Mail: [email protected] | [email protected]
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>
--
E-Mail: [email protected] | [email protected]
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
