Re: [filevault] Installing users and access control entries in the same package

[Konrad Windszus]

I would suggest to split it up into two packages and make the ACL package 
depend on the user package. You can even put those two packages into a common 
container package. The dependencies will enforce the right installation order.
Konrad

> Am 21.08.2020 um 18:47 schrieb Robert Munteanu :
> 
> Hi,
> 
> I am trying to install a content package that includes:
> 
> - two users under /home/users/slingshot
> - content with ACEs that reference the two users under
> /content/slingshot
> 
> When installing the content packages I see that the /content entry is
> processed first, leading to errors like
> 
>  E  /content/slingshot/users/slingshot1/rep:policy
>  ! org.xml.sax.SAXException:
> javax.jcr.security.AccessControlException: Unknown principal slingshot1
> javax.jcr.security.AccessControlException: Unknown principal slingshot1
> 
> and only later on is the user created
> 
>  -  /home
>  -  /home/users
>  A  /home/users/slingshot
>  A  /home/users/slingshot/slingshot1
> 
> Obviously, reinstalling the content package fixes the problem but I'm
> looking for a more error-safe way of installing the content package.
> 
> How can I install this content package with users and ACEs from without
> errors?
> 
> Thanks,
> Robert
> 

[filevault] Installing users and access control entries in the same package

[Robert Munteanu]

Hi,

I am trying to install a content package that includes:

- two users under /home/users/slingshot
- content with ACEs that reference the two users under
/content/slingshot

When installing the content packages I see that the /content entry is
processed first, leading to errors like

  E  /content/slingshot/users/slingshot1/rep:policy
  ! org.xml.sax.SAXException:
javax.jcr.security.AccessControlException: Unknown principal slingshot1
javax.jcr.security.AccessControlException: Unknown principal slingshot1

and only later on is the user created

  -  /home
  -  /home/users
  A  /home/users/slingshot
  A  /home/users/slingshot/slingshot1

Obviously, reinstalling the content package fixes the problem but I'm
looking for a more error-safe way of installing the content package.

How can I install this content package with users and ACEs from without
errors?

Thanks,
Robert

Re: [filevault-package-maven-plugin] Packaging additional files in META-INF

[Robert Munteanu]

Hi Konrad,

On Fri, 2020-08-21 at 12:05 +0200, Konrad Windszus wrote:
> Hi Robert,
> Currently the filevault-package-maven-plugin creates packages from
> mainly two different source directories:
> 
> https://jackrabbit.apache.org/filevault-package-maven-plugin/package-mojo.html#jcrRootSourceDirectory
>  plugin/package-mojo.html#jcrRootSourceDirectory> -> ends up in the
> installed package
> https://jackrabbit.apache.org/filevault-package-maven-plugin/package-mojo.html#metaInfVaultDirectory
>  plugin/package-mojo.html#metaInfVaultDirectory> -> ends up in META-
> INF/vault
> 
> Probably we need an optional third source to put META-INF somewhere
> outside the vault directory.
> Feel free to raise a JIRA.

Thank you for the reply. I filed

  https://issues.apache.org/jira/browse/JCRVLT-471

Thanks,
Robert

Re: [filevault-package-maven-plugin] Packaging additional files in META-INF

[Konrad Windszus]

Hi Robert,
Currently the filevault-package-maven-plugin creates packages from mainly two 
different source directories:

https://jackrabbit.apache.org/filevault-package-maven-plugin/package-mojo.html#jcrRootSourceDirectory
 

 -> ends up in the installed package
https://jackrabbit.apache.org/filevault-package-maven-plugin/package-mojo.html#metaInfVaultDirectory
 

 -> ends up in META-INF/vault

Probably we need an optional third source to put META-INF somewhere outside the 
vault directory.
Feel free to raise a JIRA.

Thanks,
Konrad


> On 21. Aug 2020, at 11:33, Robert Munteanu  wrote:
> 
> Hi,
> 
> I am trying to use the filevault-package-maven-plugin with a Sling
> project. By default, artifacts are checked to see if they have legal
> files: META-INF/{LICENSE,NOTICE}.
> 
> When building a content package these are not included.  I've
> configured the plug-in with:
> 
> 
>org.apache.jackrabbit
>filevault-package-maven-plugin
>1.1.4
>true
>
>${project.build.outputDirectory} otSourceDirectory>
>
> 
> 
> The legal files from target/classes are understandably skipped since
> they don't match the filter defintions, so that's not a good place for
> them. What I would like is to have then copied over to META-INF in the
> resulting content package, but I did not find an easy way to do this.
> 
> I worked around it with an additional resources plug-in execution:
> 
> 
>maven-resources-plugin
>
>
>copy-legal-files
>prepare-package
>
>copy-resources
>
>
>
> ${project.build.directory}/vault-work/META-INF
>
>
>
> ${project.build.directory}/maven-shared-archive-resources/META-INF/
>
>
>
>
>
> 
> 
> Is there a simpler way to copy files to META-INF/ using the plug-in?
> 
> Thanks,
> Robert
> 

[filevault-package-maven-plugin] Packaging additional files in META-INF

[Robert Munteanu]

Hi,

I am trying to use the filevault-package-maven-plugin with a Sling
project. By default, artifacts are checked to see if they have legal
files: META-INF/{LICENSE,NOTICE}.

When building a content package these are not included.  I've
configured the plug-in with:


org.apache.jackrabbit
filevault-package-maven-plugin
1.1.4
true

${project.build.outputDirectory}



The legal files from target/classes are understandably skipped since
they don't match the filter defintions, so that's not a good place for
them. What I would like is to have then copied over to META-INF in the
resulting content package, but I did not find an easy way to do this.

I worked around it with an additional resources plug-in execution:


maven-resources-plugin


copy-legal-files
prepare-package

copy-resources



${project.build.directory}/vault-work/META-INF



${project.build.directory}/maven-shared-archive-resources/META-INF/







Is there a simpler way to copy files to META-INF/ using the plug-in?

Thanks,
Robert

[Release Plan] Apache Jackrabbit Oak 1.8.23

[Nitin Gupta]

Hi,

I plan on releasing oak 1.8.23 on Monday (24th August).

These are the issues included -
https://issues.apache.org/jira/projects/OAK/versions/12348315 .
Please let me know in case there are any concerns.

Thanks,
Nitin