You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-dev@jackrabbit.apache.org by Marcel Reutegger <mr...@adobe.com> on 2017/04/26 12:13:16 UTC

[m12n] parent pom reference

Hi,

I noticed that the new modules have a parent pom reference like this:

    <artifactId>jackrabbit-oak</artifactId>
    <groupId>org.apache.jackrabbit</groupId>
    <version>1.8-SNAPSHOT</version>

while existing modules use:

    <groupId>org.apache.jackrabbit</groupId>
    <artifactId>oak-parent</artifactId>
    <version>1.8-SNAPSHOT</version>
    <relativePath>../oak-parent/pom.xml</relativePath>

Is this intentional? One side effect is that new modules are not deployed.
In my view, they should all reference oak-parent.

Regards
 Marcel

Re: [m12n] parent pom reference

Posted by Angela Schreiber <an...@adobe.com>.

thanks a lot!

On 26/04/17 15:01, "Marcel Reutegger" <mr...@adobe.com> wrote:

>On 26/04/17 14:37, Angela Schreiber wrote:
>> for the modules created during the m12n effort that's an oversight
>> can you create an issue?
>
>See OAK-6133. I will change it accordingly.
>
>Regards
>  Marcel

Re: [m12n] parent pom reference

Posted by Marcel Reutegger <mr...@adobe.com>.

On 26/04/17 14:37, Angela Schreiber wrote:
> for the modules created during the m12n effort that's an oversight
> can you create an issue?

See OAK-6133. I will change it accordingly.

Regards
  Marcel

Re: [m12n] parent pom reference

Posted by Angela Schreiber <an...@adobe.com>.

hi marcel

for the modules created during the m12n effort that's an oversight
can you create an issue?

angela

On 26/04/17 14:13, "Marcel Reutegger" <mr...@adobe.com> wrote:

>Hi,
>
>I noticed that the new modules have a parent pom reference like this:
>
>    <artifactId>jackrabbit-oak</artifactId>
>    <groupId>org.apache.jackrabbit</groupId>
>    <version>1.8-SNAPSHOT</version>
>
>while existing modules use:
>
>    <groupId>org.apache.jackrabbit</groupId>
>    <artifactId>oak-parent</artifactId>
>    <version>1.8-SNAPSHOT</version>
>    <relativePath>../oak-parent/pom.xml</relativePath>
>
>Is this intentional? One side effect is that new modules are not deployed.
>In my view, they should all reference oak-parent.
>
>Regards
> Marcel
>