[jira] [Commented] (JCRVLT-262) Implement workaround for JCRVLT-177 when creating subpackages

[Konrad Windszus (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCRVLT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330167#comment-16330167
 ] 

Konrad Windszus commented on JCRVLT-262:


There are several issues with upgrading:
# all releases since 3.1.38 suffered from pretty serious regressions, namely 
https://issues.apache.org/jira/browse/JCRVLT-186 in 3.1.40 and 
https://issues.apache.org/jira/browse/JCRVLT-258 in both 3.1.40 and 3.1.42
# Adobe does not provide an official hotfix in its commercial product AEM 
containing a newer version

Apart from that the workaround does not do any harm (even in newer instances). 
It just switches from "Simple File Aggregates" for sub packages to "Extended 
File Aggregates" (http://jackrabbit.apache.org/filevault/vaultfs.html)

> Implement workaround for JCRVLT-177 when creating subpackages
> -
>
> Key: JCRVLT-262
> URL: https://issues.apache.org/jira/browse/JCRVLT-262
> Project: Jackrabbit FileVault
>  Issue Type: Bug
>  Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.1
>Reporter: Konrad Windszus
>Priority: Major
>
> Due to bug JCRVLT-177 all package metadata (like filters or dependencies) of 
> subpackages are not correctly overwritten (when updating a SNAPSHOT version 
> package with Jackrabbit Filevault < 3.1.40).
> The workaround to create subpackages not only as one Simple File (the .zip) 
> but also creating an according .content.xml works around this limitation and 
> leads to correctly updating the meta data. The Maven plugin should allow to 
> optionally create the .content.xml along with the subpackage automatically.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: 1.0.40 broken because of missing package exports

[Julian Reschke]

On 2018-01-17 12:44, Julian Reschke wrote:

See

   https://issues.apache.org/jira/browse/OAK-7167

So it seems we need to fix this, and start a new release cycle?

Feedback appreciated.


So I believe this is fixed now - should we attempt a new release?

Best regards, Julian

[jira] [Commented] (JCRVLT-262) Implement workaround for JCRVLT-177 when creating subpackages

[Tobias Bocanegra (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCRVLT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16329990#comment-16329990
 ] 

Tobias Bocanegra commented on JCRVLT-262:
-

I would rather not add such workarounds and rather ensure that systems upgrade 
to a recent filevault.

> Implement workaround for JCRVLT-177 when creating subpackages
> -
>
> Key: JCRVLT-262
> URL: https://issues.apache.org/jira/browse/JCRVLT-262
> Project: Jackrabbit FileVault
>  Issue Type: Bug
>  Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.1
>Reporter: Konrad Windszus
>Priority: Major
>
> Due to bug JCRVLT-177 all package metadata (like filters or dependencies) of 
> subpackages are not correctly overwritten (when updating a SNAPSHOT version 
> package with Jackrabbit Filevault < 3.1.40).
> The workaround to create subpackages not only as one Simple File (the .zip) 
> but also creating an according .content.xml works around this limitation and 
> leads to correctly updating the meta data. The Maven plugin should allow to 
> optionally create the .content.xml along with the subpackage automatically.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (JCRSITE-51) Long command line options doesn't work in jackrabbit-standalone backup demo

[Marcel Reutegger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCRSITE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcel Reutegger resolved JCRSITE-51.
-
Resolution: Fixed

Fixed: http://svn.apache.org/r1821380

Thanks for reporting.

> Long command line options doesn't work in jackrabbit-standalone backup demo
> ---
>
> Key: JCRSITE-51
> URL: https://issues.apache.org/jira/browse/JCRSITE-51
> Project: Jackrabbit Site
>  Issue Type: Bug
>Reporter: Woonsan Ko
>Assignee: Marcel Reutegger
>Priority: Minor
>
> Long command line options with equal sign, e.g, 
> {{--backup-repo=jackrabbit-backupN}}, doesn't work in jackrabbit-standalone 
> backup demo example.
> It works with {{--backup-repo jackrabbit-backupN}} (without equal sign) 
> though.
>   
> Here's the detail:
> The example script in [1] doesn't seem to work (any more?):
> {code:java}
> $ java -jar jackrabbit-standalone-2.14.4.jar --backup \
>        --repo=jackrabbit \
>        --conf=jackrabbit/repository.xml \
>        --backup-repo=jackrabbit-backupN \
>        --backup-conf=jackrabbit-backupN/repository.xml
> {code}
> throwing:
> {noformat}
> Exception in thread "main"
> org.apache.commons.cli.UnrecognizedOptionException: Unrecognized
> option: --repo=jackrabbit
>     at org.apache.commons.cli.Parser.processOption(Parser.java:379)
>     at org.apache.commons.cli.Parser.parse(Parser.java:193)
>     at org.apache.commons.cli.Parser.parse(Parser.java:71)
>     at org.apache.jackrabbit.standalone.Main.(Main.java:99)
>     at org.apache.jackrabbit.standalone.Main.main(Main.java:60)
> {noformat}
> The following instead seems working (at least in command line option parsing):
> {code:java}
> $ java -jar jackrabbit-standalone-2.14.4.jar --backup \
>        --repo jackrabbit \
>        --conf jackrabbit/repository.xml \
>        --backup-repo jackrabbit-backupN \
>        --backup-conf jackrabbit-backupN/repository.xml
> {code}
> [1] 
> [http://jackrabbit.apache.org/jcr/standalone-server.html#Backup_and_migration]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (JCRSITE-51) Long command line options doesn't work in jackrabbit-standalone backup demo

[Marcel Reutegger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCRSITE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcel Reutegger reassigned JCRSITE-51:
---

Assignee: Marcel Reutegger

> Long command line options doesn't work in jackrabbit-standalone backup demo
> ---
>
> Key: JCRSITE-51
> URL: https://issues.apache.org/jira/browse/JCRSITE-51
> Project: Jackrabbit Site
>  Issue Type: Bug
>Reporter: Woonsan Ko
>Assignee: Marcel Reutegger
>Priority: Minor
>
> Long command line options with equal sign, e.g, 
> {{--backup-repo=jackrabbit-backupN}}, doesn't work in jackrabbit-standalone 
> backup demo example.
> It works with {{--backup-repo jackrabbit-backupN}} (without equal sign) 
> though.
>   
> Here's the detail:
> The example script in [1] doesn't seem to work (any more?):
> {code:java}
> $ java -jar jackrabbit-standalone-2.14.4.jar --backup \
>        --repo=jackrabbit \
>        --conf=jackrabbit/repository.xml \
>        --backup-repo=jackrabbit-backupN \
>        --backup-conf=jackrabbit-backupN/repository.xml
> {code}
> throwing:
> {noformat}
> Exception in thread "main"
> org.apache.commons.cli.UnrecognizedOptionException: Unrecognized
> option: --repo=jackrabbit
>     at org.apache.commons.cli.Parser.processOption(Parser.java:379)
>     at org.apache.commons.cli.Parser.parse(Parser.java:193)
>     at org.apache.commons.cli.Parser.parse(Parser.java:71)
>     at org.apache.jackrabbit.standalone.Main.(Main.java:99)
>     at org.apache.jackrabbit.standalone.Main.main(Main.java:60)
> {noformat}
> The following instead seems working (at least in command line option parsing):
> {code:java}
> $ java -jar jackrabbit-standalone-2.14.4.jar --backup \
>        --repo jackrabbit \
>        --conf jackrabbit/repository.xml \
>        --backup-repo jackrabbit-backupN \
>        --backup-conf jackrabbit-backupN/repository.xml
> {code}
> [1] 
> [http://jackrabbit.apache.org/jcr/standalone-server.html#Backup_and_migration]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Intent to backport OAK-{7168,7169,7171} to 1.8

[Andrei Dulceanu]

+1

Andrei

2018-01-17 16:56 GMT+02:00 Francesco Mari :

> I intend to backport OAK-{7168,7169,7171} to the 1.8 branch. The three
> issues fix the behaviour of the debug, datastorecheck, and history
> command when it comes to error handling. The fix make these commands
> return with a non-zero exit code in case of error and print error
> message to standard error instead of standard output.
>

Intent to backport OAK-{7168,7169,7171} to 1.8

[Francesco Mari]

I intend to backport OAK-{7168,7169,7171} to the 1.8 branch. The three
issues fix the behaviour of the debug, datastorecheck, and history
command when it comes to error handling. The fix make these commands
return with a non-zero exit code in case of error and print error
message to standard error instead of standard output.

Re: Minor documentation error in jackrabbit-standalone 2.14+ backup command line example

[Woonsan Ko]

On Mon, Jan 15, 2018 at 6:14 AM, Marcel Reutegger  wrote:
> Hi,
>
> Thanks for reporting. Can you please create a JIRA issue for this?

Done:
- https://issues.apache.org/jira/browse/JCRSITE-51

Thanks,

Woonsan

>
> Regards
>  Marcel
>
>
> On 11/01/18 22:11, Woonsan Ko wrote:
>>
>> Hi,
>>
>> I just wanted to report a minor documentation error. The example
>> script in [1] doesn't seem to work (any more?):
>>
>> $ java -jar jackrabbit-standalone-2.14.4.jar --backup \
>> --repo=jackrabbit \
>> --conf=jackrabbit/repository.xml \
>> --backup-repo=jackrabbit-backupN \
>> --backup-conf=jackrabbit-backupN/repository.xml
>>
>> throwing:
>>
>> Exception in thread "main"
>> org.apache.commons.cli.UnrecognizedOptionException: Unrecognized
>> option: --repo=jackrabbit
>>  at org.apache.commons.cli.Parser.processOption(Parser.java:379)
>>  at org.apache.commons.cli.Parser.parse(Parser.java:193)
>>  at org.apache.commons.cli.Parser.parse(Parser.java:71)
>>  at org.apache.jackrabbit.standalone.Main.(Main.java:99)
>>  at org.apache.jackrabbit.standalone.Main.main(Main.java:60)
>>
>> The following instead seems working (at least in command line option
>> parsing):
>>
>> $ java -jar jackrabbit-standalone-2.14.4.jar --backup \
>> --repo jackrabbit \
>> --conf jackrabbit/repository.xml \
>> --backup-repo jackrabbit-backupN \
>> --backup-conf jackrabbit-backupN/repository.xml
>>
>> Regards,
>>
>> Woonsan
>>
>> [1]
>> http://jackrabbit.apache.org/jcr/standalone-server.html#Backup_and_migration
>>
>

[jira] [Updated] (JCRSITE-51) Long command line options doesn't work in jackrabbit-standalone backup demo

[Woonsan Ko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCRSITE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Woonsan Ko updated JCRSITE-51:
--
Description: 
Long command line options with equal sign, e.g, 
{{--backup-repo=jackrabbit-backupN}}, doesn't work in jackrabbit-standalone 
backup demo example.
It works with {{--backup-repo jackrabbit-backupN}} (without equal sign) though.
  
Here's the detail:

The example script in [1] doesn't seem to work (any more?):

{code:java}
$ java -jar jackrabbit-standalone-2.14.4.jar --backup \
       --repo=jackrabbit \
       --conf=jackrabbit/repository.xml \
       --backup-repo=jackrabbit-backupN \
       --backup-conf=jackrabbit-backupN/repository.xml
{code}

throwing:

{noformat}
Exception in thread "main"
org.apache.commons.cli.UnrecognizedOptionException: Unrecognized
option: --repo=jackrabbit
    at org.apache.commons.cli.Parser.processOption(Parser.java:379)
    at org.apache.commons.cli.Parser.parse(Parser.java:193)
    at org.apache.commons.cli.Parser.parse(Parser.java:71)
    at org.apache.jackrabbit.standalone.Main.(Main.java:99)
    at org.apache.jackrabbit.standalone.Main.main(Main.java:60)
{noformat}

The following instead seems working (at least in command line option parsing):

{code:java}
$ java -jar jackrabbit-standalone-2.14.4.jar --backup \
       --repo jackrabbit \
       --conf jackrabbit/repository.xml \
       --backup-repo jackrabbit-backupN \
       --backup-conf jackrabbit-backupN/repository.xml
{code}

[1] 
[http://jackrabbit.apache.org/jcr/standalone-server.html#Backup_and_migration]

> Long command line options doesn't work in jackrabbit-standalone backup demo
> ---
>
> Key: JCRSITE-51
> URL: https://issues.apache.org/jira/browse/JCRSITE-51
> Project: Jackrabbit Site
>  Issue Type: Bug
>Reporter: Woonsan Ko
>Priority: Minor
>
> Long command line options with equal sign, e.g, 
> {{--backup-repo=jackrabbit-backupN}}, doesn't work in jackrabbit-standalone 
> backup demo example.
> It works with {{--backup-repo jackrabbit-backupN}} (without equal sign) 
> though.
>   
> Here's the detail:
> The example script in [1] doesn't seem to work (any more?):
> {code:java}
> $ java -jar jackrabbit-standalone-2.14.4.jar --backup \
>        --repo=jackrabbit \
>        --conf=jackrabbit/repository.xml \
>        --backup-repo=jackrabbit-backupN \
>        --backup-conf=jackrabbit-backupN/repository.xml
> {code}
> throwing:
> {noformat}
> Exception in thread "main"
> org.apache.commons.cli.UnrecognizedOptionException: Unrecognized
> option: --repo=jackrabbit
>     at org.apache.commons.cli.Parser.processOption(Parser.java:379)
>     at org.apache.commons.cli.Parser.parse(Parser.java:193)
>     at org.apache.commons.cli.Parser.parse(Parser.java:71)
>     at org.apache.jackrabbit.standalone.Main.(Main.java:99)
>     at org.apache.jackrabbit.standalone.Main.main(Main.java:60)
> {noformat}
> The following instead seems working (at least in command line option parsing):
> {code:java}
> $ java -jar jackrabbit-standalone-2.14.4.jar --backup \
>        --repo jackrabbit \
>        --conf jackrabbit/repository.xml \
>        --backup-repo jackrabbit-backupN \
>        --backup-conf jackrabbit-backupN/repository.xml
> {code}
> [1] 
> [http://jackrabbit.apache.org/jcr/standalone-server.html#Backup_and_migration]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (JCRSITE-51) Long command line options doesn't work in jackrabbit-standalone backup demo

[Woonsan Ko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCRSITE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Woonsan Ko updated JCRSITE-51:
--
Environment: (was: Long command line options with equal sign, e.g, 
{{--backup-repo=jackrabbit-backupN}}, doesn't work in jackrabbit-standalone 
backup demo example.
 It works with {{--backup-repo jackrabbit-backupN}} (without equal sign) though.
  
 Here's the detail:

The example script in [1] doesn't seem to work (any more?):
{code:java}
$ java -jar jackrabbit-standalone-2.14.4.jar --backup \
       --repo=jackrabbit \
       --conf=jackrabbit/repository.xml \
       --backup-repo=jackrabbit-backupN \
       --backup-conf=jackrabbit-backupN/repository.xml
{code}
throwing:
{noformat}
Exception in thread "main"
org.apache.commons.cli.UnrecognizedOptionException: Unrecognized
option: --repo=jackrabbit
    at org.apache.commons.cli.Parser.processOption(Parser.java:379)
    at org.apache.commons.cli.Parser.parse(Parser.java:193)
    at org.apache.commons.cli.Parser.parse(Parser.java:71)
    at org.apache.jackrabbit.standalone.Main.(Main.java:99)
    at org.apache.jackrabbit.standalone.Main.main(Main.java:60)
{noformat}
The following instead seems working (at least in command line option parsing):
{code:java}
$ java -jar jackrabbit-standalone-2.14.4.jar --backup \
       --repo jackrabbit \
       --conf jackrabbit/repository.xml \
       --backup-repo jackrabbit-backupN \
       --backup-conf jackrabbit-backupN/repository.xml
{code}
[1] 
[http://jackrabbit.apache.org/jcr/standalone-server.html#Backup_and_migration])

> Long command line options doesn't work in jackrabbit-standalone backup demo
> ---
>
> Key: JCRSITE-51
> URL: https://issues.apache.org/jira/browse/JCRSITE-51
> Project: Jackrabbit Site
>  Issue Type: Bug
>Reporter: Woonsan Ko
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (JCRSITE-51) Long command line options doesn't work in jackrabbit-standalone backup demo

[Woonsan Ko (JIRA)]

Woonsan Ko created JCRSITE-51:
-

 Summary: Long command line options doesn't work in 
jackrabbit-standalone backup demo
 Key: JCRSITE-51
 URL: https://issues.apache.org/jira/browse/JCRSITE-51
 Project: Jackrabbit Site
  Issue Type: Bug
 Environment: Long command line options with equal sign, e.g, 
{{--backup-repo=jackrabbit-backupN}}, doesn't work in jackrabbit-standalone 
backup demo example.
 It works with {{--backup-repo jackrabbit-backupN}} (without equal sign) though.
  
 Here's the detail:

The example script in [1] doesn't seem to work (any more?):
{code:java}
$ java -jar jackrabbit-standalone-2.14.4.jar --backup \
       --repo=jackrabbit \
       --conf=jackrabbit/repository.xml \
       --backup-repo=jackrabbit-backupN \
       --backup-conf=jackrabbit-backupN/repository.xml
{code}
throwing:
{noformat}
Exception in thread "main"
org.apache.commons.cli.UnrecognizedOptionException: Unrecognized
option: --repo=jackrabbit
    at org.apache.commons.cli.Parser.processOption(Parser.java:379)
    at org.apache.commons.cli.Parser.parse(Parser.java:193)
    at org.apache.commons.cli.Parser.parse(Parser.java:71)
    at org.apache.jackrabbit.standalone.Main.(Main.java:99)
    at org.apache.jackrabbit.standalone.Main.main(Main.java:60)
{noformat}
The following instead seems working (at least in command line option parsing):
{code:java}
$ java -jar jackrabbit-standalone-2.14.4.jar --backup \
       --repo jackrabbit \
       --conf jackrabbit/repository.xml \
       --backup-repo jackrabbit-backupN \
       --backup-conf jackrabbit-backupN/repository.xml
{code}
[1] 
[http://jackrabbit.apache.org/jcr/standalone-server.html#Backup_and_migration]
Reporter: Woonsan Ko






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Intent to backport OAK-7157 to 1.8

[Andrei Dulceanu]

+1

Andrei

2018-01-16 17:50 GMT+02:00 Michael Dürig :

>
> +1. This is also relevant for OAK-7132 in the broader scope.
>
> Michael
>
>
> On 16.01.18 16:45, Francesco Mari wrote:
>
>> I intend to backport OAK-7157 to the 1.8 branch. The fix implements an
>> optimisation for cold standby instances. With the fix in place,
>> standby instances only retained the latest generation, instead of the
>> last two generations. This allows a cold standby instance to remove
>> old segments more aggressively and save space on disk.
>>
>>

Re: Intent to backport OAK-7131 (xpath to sql2 conversion drops order by clause for some cases)

[Vikas Saurabh]

+1

--Vikas
(sent from mobile)

On 17-Jan-2018 18:37, "Thomas Mueller"  wrote:

> I want to backport OAK-7152 to all maintenance branches. The fix is simple
> and low risk.
>
> Regards,
> Thomas
>
>
>

Intent to backport OAK-7131 (xpath to sql2 conversion drops order by clause for some cases)

[Thomas Mueller]

I want to backport OAK-7152 to all maintenance branches. The fix is simple and 
low risk.

Regards,
Thomas

Re: Intent to backport OAK-7152

[Thomas Mueller]

+1

On 15.01.18, 09:47, "Marcel Reutegger"  wrote:

Hi,

I will backport OAK-7152 to all maintenance branches. The fix is trivial 
and very low risk because the method currently simply does not return.

Regards
 Marcel

[jira] [Comment Edited] (JCRVLT-262) Implement workaround for JCRVLT-177 when creating subpackages

[Konrad Windszus (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCRVLT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328691#comment-16328691
 ] 

Konrad Windszus edited comment on JCRVLT-262 at 1/17/18 12:46 PM:
--

The proposed workaround would place a {{.content.xml}} in a sibling folder to 
the subpackage's zip named {{}} having the following 
content

{code}


http://www.jcp.org/jcr/1.0;
jcr:primaryType="nt:file">


{code}


was (Author: kwin):
The proposed workaround would place a {{.content.xml}} in a sibling folder to 
the ZIP named {{}} having the following content

{code}


http://www.jcp.org/jcr/1.0;
jcr:primaryType="nt:file">


{code}

> Implement workaround for JCRVLT-177 when creating subpackages
> -
>
> Key: JCRVLT-262
> URL: https://issues.apache.org/jira/browse/JCRVLT-262
> Project: Jackrabbit FileVault
>  Issue Type: Bug
>  Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.1
>Reporter: Konrad Windszus
>Priority: Major
>
> Due to bug JCRVLT-177 all package metadata (like filters or dependencies) of 
> subpackages are not correctly overwritten (when updating a SNAPSHOT version 
> package with Jackrabbit Filevault < 3.1.40).
> The workaround to create subpackages not only as one Simple File (the .zip) 
> but also creating an according .content.xml works around this limitation and 
> leads to correctly updating the meta data. The Maven plugin should allow to 
> optionally create the .content.xml along with the subpackage automatically.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (JCRVLT-262) Implement workaround for JCRVLT-177 when creating subpackages

[Konrad Windszus (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCRVLT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328691#comment-16328691
 ] 

Konrad Windszus edited comment on JCRVLT-262 at 1/17/18 12:46 PM:
--

The proposed workaround would place a {{.content.xml}} in a sibling folder to 
the ZIP named {{}} having the following content

{code}


http://www.jcp.org/jcr/1.0;
jcr:primaryType="nt:file">


{code}


was (Author: kwin):
The proposed workaround would place a {{.content.xml}} in a sibling folder to 
the ZIP named {{}} having the following content

{code}


http://www.day.com/jcr/vault/1.0; 
xmlns:jcr="http://www.jcp.org/jcr/1.0; xmlns:nt="http://www.jcp.org/jcr/nt/1.0;
jcr:primaryType="nt:file">


{code}

> Implement workaround for JCRVLT-177 when creating subpackages
> -
>
> Key: JCRVLT-262
> URL: https://issues.apache.org/jira/browse/JCRVLT-262
> Project: Jackrabbit FileVault
>  Issue Type: Bug
>  Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.1
>Reporter: Konrad Windszus
>Priority: Major
>
> Due to bug JCRVLT-177 all package metadata (like filters or dependencies) of 
> subpackages are not correctly overwritten (when updating a SNAPSHOT version 
> package with Jackrabbit Filevault < 3.1.40).
> The workaround to create subpackages not only as one Simple File (the .zip) 
> but also creating an according .content.xml works around this limitation and 
> leads to correctly updating the meta data. The Maven plugin should allow to 
> optionally create the .content.xml along with the subpackage automatically.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (JCRVLT-262) Implement workaround for JCRVLT-177 when creating subpackages

[Konrad Windszus (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCRVLT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328691#comment-16328691
 ] 

Konrad Windszus commented on JCRVLT-262:


The proposed workaround would place a {{.content.xml}} in a sibling folder to 
the ZIP named {{}} having the following content

{code}


http://www.day.com/jcr/vault/1.0; 
xmlns:jcr="http://www.jcp.org/jcr/1.0; xmlns:nt="http://www.jcp.org/jcr/nt/1.0;
jcr:primaryType="nt:file">


{code}

> Implement workaround for JCRVLT-177 when creating subpackages
> -
>
> Key: JCRVLT-262
> URL: https://issues.apache.org/jira/browse/JCRVLT-262
> Project: Jackrabbit FileVault
>  Issue Type: Bug
>  Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.1
>Reporter: Konrad Windszus
>Priority: Major
>
> Due to bug JCRVLT-177 all package metadata (like filters or dependencies) of 
> subpackages are not correctly overwritten (when updating a SNAPSHOT version 
> package with Jackrabbit Filevault < 3.1.40).
> The workaround to create subpackages not only as one Simple File (the .zip) 
> but also creating an according .content.xml works around this limitation and 
> leads to correctly updating the meta data. The Maven plugin should allow to 
> optionally create the .content.xml along with the subpackage automatically.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (JCRVLT-262) Implement workaround for JCRVLT-177 when creating subpackages

[Konrad Windszus (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCRVLT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus updated JCRVLT-262:
---
Description: 
Due to bug JCRVLT-177 all package metadata (like filters or dependencies) of 
subpackages are not correctly overwritten (when updating a SNAPSHOT version 
package with Jackrabbit Filevault < 3.1.40).
The workaround to create subpackages not only as one Simple File (the .zip) but 
also creating an according .content.xml works around this limitation and leads 
to correctly updating the meta data. The Maven plugin should allow to 
optionally create the .content.xml along with the subpackage automatically.

  was:
Due to bug JCRVLT-177 all package metadata (like filters or dependencies) of 
subpackages are not correctly overwritten (when updating a SNAPSHOT version 
package with Jackrabbit Filevault < ).
The workaround to create subpackages not only as one Simple File (the .zip) but 
also creating an according .content.xml works around this limitation and leads 
to correctly updating the meta data. The Maven plugin should allow to 
optionally create the .content.xml along with the subpackage automatically.


> Implement workaround for JCRVLT-177 when creating subpackages
> -
>
> Key: JCRVLT-262
> URL: https://issues.apache.org/jira/browse/JCRVLT-262
> Project: Jackrabbit FileVault
>  Issue Type: Bug
>  Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.1
>Reporter: Konrad Windszus
>Priority: Major
>
> Due to bug JCRVLT-177 all package metadata (like filters or dependencies) of 
> subpackages are not correctly overwritten (when updating a SNAPSHOT version 
> package with Jackrabbit Filevault < 3.1.40).
> The workaround to create subpackages not only as one Simple File (the .zip) 
> but also creating an according .content.xml works around this limitation and 
> leads to correctly updating the meta data. The Maven plugin should allow to 
> optionally create the .content.xml along with the subpackage automatically.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (JCRVLT-262) Implement workaround for JCRVLT-177 when creating subpackages

[Konrad Windszus (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCRVLT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus updated JCRVLT-262:
---
Description: 
Due to bug JCRVLT-177 all package metadata (like filters or dependencies) of 
subpackages are not correctly overwritten (when updating a SNAPSHOT version 
package with Jackrabbit Filevault < ).
The workaround to create subpackages not only as one Simple File (the .zip) but 
also creating an according .content.xml works around this limitation and leads 
to correctly updating the meta data. The Maven plugin should allow to 
optionally create the .content.xml along with the subpackage automatically.

  was:
Due to bug JCRVLT-177 all package metadata (like filters or dependencies) of 
subpackages are not correctly overwritten (when updating a SNAPSHOT version 
package).
The workaround to create subpackages not only as one Simple File (the .zip) but 
also creating an according .content.xml works around this limitation and leads 
to correctly updating the meta data. The Maven plugin should allow to 
optionally create the .content.xml along with the subpackage automatically.


> Implement workaround for JCRVLT-177 when creating subpackages
> -
>
> Key: JCRVLT-262
> URL: https://issues.apache.org/jira/browse/JCRVLT-262
> Project: Jackrabbit FileVault
>  Issue Type: Bug
>  Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.1
>Reporter: Konrad Windszus
>Priority: Major
>
> Due to bug JCRVLT-177 all package metadata (like filters or dependencies) of 
> subpackages are not correctly overwritten (when updating a SNAPSHOT version 
> package with Jackrabbit Filevault < ).
> The workaround to create subpackages not only as one Simple File (the .zip) 
> but also creating an according .content.xml works around this limitation and 
> leads to correctly updating the meta data. The Maven plugin should allow to 
> optionally create the .content.xml along with the subpackage automatically.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (JCRVLT-262) Implement workaround for JCRVLT-177 when creating subpackages

[Konrad Windszus (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCRVLT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus updated JCRVLT-262:
---
Description: 
Due to bug JCRVLT-177 all package metadata (like filters or dependencies) of 
subpackages are not correctly overwritten (when updating a SNAPSHOT version 
package).
The workaround to create subpackages not only as one Simple File (the .zip) but 
also creating an according .content.xml works around this limitation and leads 
to correctly updating the meta data. The Maven plugin should allow to 
optionally create the .content.xml along with the subpackage automatically.

  was:
Due to bug JCRVLT-177 all package metadata (like filters or dependencies) of 
subpackages are not correctly overwritten (when updating a SNAPSHOT version 
package).
The workaround to create subpackages not only as one Simple File (the .zip) but 
also creating an according .content.xml works around this limitation and leads 
to correctly updating the meta data.


> Implement workaround for JCRVLT-177 when creating subpackages
> -
>
> Key: JCRVLT-262
> URL: https://issues.apache.org/jira/browse/JCRVLT-262
> Project: Jackrabbit FileVault
>  Issue Type: Bug
>  Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.1
>Reporter: Konrad Windszus
>Priority: Major
>
> Due to bug JCRVLT-177 all package metadata (like filters or dependencies) of 
> subpackages are not correctly overwritten (when updating a SNAPSHOT version 
> package).
> The workaround to create subpackages not only as one Simple File (the .zip) 
> but also creating an according .content.xml works around this limitation and 
> leads to correctly updating the meta data. The Maven plugin should allow to 
> optionally create the .content.xml along with the subpackage automatically.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (JCRVLT-262) Implement workaround for JCRVLT-177 when creating subpackages

[Konrad Windszus (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCRVLT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus updated JCRVLT-262:
---
Environment: (was: Due to bug JCRVLT-177 all package metadata (like 
filters or dependencies) of subpackages are not correctly overwritten (when 
updating a SNAPSHOT version package).
The workaround to create subpackages not only as one Simple File (the .zip) but 
also creating an according .content.xml works around this limitation and leads 
to correctly updating the meta data.)

> Implement workaround for JCRVLT-177 when creating subpackages
> -
>
> Key: JCRVLT-262
> URL: https://issues.apache.org/jira/browse/JCRVLT-262
> Project: Jackrabbit FileVault
>  Issue Type: Bug
>  Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.1
>Reporter: Konrad Windszus
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (JCRVLT-262) Implement workaround for JCRVLT-177 when creating subpackages

[Konrad Windszus (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCRVLT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus updated JCRVLT-262:
---
Description: 
Due to bug JCRVLT-177 all package metadata (like filters or dependencies) of 
subpackages are not correctly overwritten (when updating a SNAPSHOT version 
package).
The workaround to create subpackages not only as one Simple File (the .zip) but 
also creating an according .content.xml works around this limitation and leads 
to correctly updating the meta data.

> Implement workaround for JCRVLT-177 when creating subpackages
> -
>
> Key: JCRVLT-262
> URL: https://issues.apache.org/jira/browse/JCRVLT-262
> Project: Jackrabbit FileVault
>  Issue Type: Bug
>  Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.1
>Reporter: Konrad Windszus
>Priority: Major
>
> Due to bug JCRVLT-177 all package metadata (like filters or dependencies) of 
> subpackages are not correctly overwritten (when updating a SNAPSHOT version 
> package).
> The workaround to create subpackages not only as one Simple File (the .zip) 
> but also creating an according .content.xml works around this limitation and 
> leads to correctly updating the meta data.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (JCRVLT-262) Implement workaround for JCRVLT-177 when creating subpackages

[Konrad Windszus (JIRA)]

Konrad Windszus created JCRVLT-262:
--

 Summary: Implement workaround for JCRVLT-177 when creating 
subpackages
 Key: JCRVLT-262
 URL: https://issues.apache.org/jira/browse/JCRVLT-262
 Project: Jackrabbit FileVault
  Issue Type: Bug
  Components: package maven plugin
Affects Versions: package-maven-plugin-1.0.1
 Environment: Due to bug JCRVLT-177 all package metadata (like filters 
or dependencies) of subpackages are not correctly overwritten (when updating a 
SNAPSHOT version package).
The workaround to create subpackages not only as one Simple File (the .zip) but 
also creating an according .content.xml works around this limitation and leads 
to correctly updating the meta data.
Reporter: Konrad Windszus






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (JCR-4074) jackrabbit-jcr2dav: add system property to disable davex support for testing

[Julian Reschke (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCR-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085553#comment-16085553
 ] 

Julian Reschke edited comment on JCR-4074 at 1/17/18 11:28 AM:
---

trunk: [r1772343|http://svn.apache.org/r1772343]
2.12: [r1801829|http://svn.apache.org/r1801829]
2.10: [r1811717|http://svn.apache.org/r1811717]
2.8: [r1821353|http://svn.apache.org/r1821353] 
[r1818284|http://svn.apache.org/r1818284]
2.6: [r1821354|http://svn.apache.org/r1821354]



was (Author: reschke):
trunk: [r1772343|http://svn.apache.org/r1772343]
2.12: [r1801829|http://svn.apache.org/r1801829]
2.10: [r1811717|http://svn.apache.org/r1811717]
2.8: [r1821353|http://svn.apache.org/r1821353] 
[r1818284|http://svn.apache.org/r1818284]


> jackrabbit-jcr2dav: add system property to disable davex support for testing
> 
>
> Key: JCR-4074
> URL: https://issues.apache.org/jira/browse/JCR-4074
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: jackrabbit-webdav, test
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 2.13.5, 2.14, 2.12.8, 2.10.7, 2.6.10, 2.8.8
>
>
> We currently only test with davex support disabled (and we know that the set 
> of expected test failures will be different for dav, due to certain 
> operations leading to UnsupportedOperationsExceptions).
> For now just add a system property to enable non-davex testing for those who 
> care.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (JCR-4074) jackrabbit-jcr2dav: add system property to disable davex support for testing

[Julian Reschke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCR-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated JCR-4074:

Fix Version/s: 2.6.10

> jackrabbit-jcr2dav: add system property to disable davex support for testing
> 
>
> Key: JCR-4074
> URL: https://issues.apache.org/jira/browse/JCR-4074
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: jackrabbit-webdav, test
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 2.13.5, 2.14, 2.12.8, 2.10.7, 2.6.10, 2.8.8
>
>
> We currently only test with davex support disabled (and we know that the set 
> of expected test failures will be different for dav, due to certain 
> operations leading to UnsupportedOperationsExceptions).
> For now just add a system property to enable non-davex testing for those who 
> care.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (JCR-4074) jackrabbit-jcr2dav: add system property to disable davex support for testing

[Julian Reschke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCR-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated JCR-4074:

Labels:   (was: candidate_jcr_2_6)

> jackrabbit-jcr2dav: add system property to disable davex support for testing
> 
>
> Key: JCR-4074
> URL: https://issues.apache.org/jira/browse/JCR-4074
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: jackrabbit-webdav, test
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 2.13.5, 2.14, 2.12.8, 2.10.7, 2.6.10, 2.8.8
>
>
> We currently only test with davex support disabled (and we know that the set 
> of expected test failures will be different for dav, due to certain 
> operations leading to UnsupportedOperationsExceptions).
> For now just add a system property to enable non-davex testing for those who 
> care.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (JCR-4074) jackrabbit-jcr2dav: add system property to disable davex support for testing

[Julian Reschke (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCR-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085553#comment-16085553
 ] 

Julian Reschke edited comment on JCR-4074 at 1/17/18 10:53 AM:
---

trunk: [r1772343|http://svn.apache.org/r1772343]
2.12: [r1801829|http://svn.apache.org/r1801829]
2.10: [r1811717|http://svn.apache.org/r1811717]
2.8: [r1821353|http://svn.apache.org/r1821353] 
[r1818284|http://svn.apache.org/r1818284]



was (Author: reschke):
trunk: [r1772343|http://svn.apache.org/r1772343]
2.12: [r1801829|http://svn.apache.org/r1801829]
2.10: [r1811717|http://svn.apache.org/r1811717]
2.8: [r1818284|http://svn.apache.org/r1818284]


> jackrabbit-jcr2dav: add system property to disable davex support for testing
> 
>
> Key: JCR-4074
> URL: https://issues.apache.org/jira/browse/JCR-4074
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: jackrabbit-webdav, test
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_jcr_2_6
> Fix For: 2.13.5, 2.14, 2.12.8, 2.10.7, 2.8.8
>
>
> We currently only test with davex support disabled (and we know that the set 
> of expected test failures will be different for dav, due to certain 
> operations leading to UnsupportedOperationsExceptions).
> For now just add a system property to enable non-davex testing for those who 
> care.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (JCR-4074) jackrabbit-jcr2dav: add system property to disable davex support for testing

[Julian Reschke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCR-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated JCR-4074:

Fix Version/s: (was: 2.8.7)
   2.8.8

> jackrabbit-jcr2dav: add system property to disable davex support for testing
> 
>
> Key: JCR-4074
> URL: https://issues.apache.org/jira/browse/JCR-4074
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: jackrabbit-webdav, test
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_jcr_2_6
> Fix For: 2.13.5, 2.14, 2.12.8, 2.10.7, 2.8.8
>
>
> We currently only test with davex support disabled (and we know that the set 
> of expected test failures will be different for dav, due to certain 
> operations leading to UnsupportedOperationsExceptions).
> For now just add a system property to enable non-davex testing for those who 
> care.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [Fwd: Jenkins build is still unstable: Jackrabbit-Oak-Windows #110]

[Andrei Dulceanu]

Hi Robert,

I worked mostly in the standby area, so I'll have a look at the tests in
org.apache.jackrabbit.oak.segment.standby.*.

Thanks,
Andrei

2018-01-17 10:27 GMT+02:00 Robert Munteanu :

> Hi,
>
> We have gathered some failures on Windows ( 11 tests failing now ).
>
> org.apache.jackrabbit.oak.run.osgi.DocumentNodeStoreConfigTest.
> testRDBDocumentStoreRestart
> org.apache.jackrabbit.oak.run.osgi.RepositoryShutdownTest.
> multipleShutdownAndWait
> org.apache.jackrabbit.oak.run.osgi.DocumentNodeStoreConfigTest.
> testRDBDocumentStoreLateDataSource
> org.apache.jackrabbit.oak.run.osgi.DocumentNodeStoreConfigTest.
> testRDBDocumentStoreLateDataSource
> org.apache.jackrabbit.oak.segment.standby.BrokenNetworkIT.
> testProxySSLSkippedBytes
> org.apache.jackrabbit.oak.segment.standby.BrokenNetworkIT.
> testProxyFlippedStartByte
> org.apache.jackrabbit.oak.segment.standby.BrokenNetworkIT.
> testProxySSLSkippedBytesIntermediateChange
> org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT.
> testResilientSync
> org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT.
> testSyncUpdatedBinaryProperty
> org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT.
> testSync
> org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT.
> testSyncBigBlob
>
> Would be great to have them reviewed by those that touched those areas of
> code recently.
>
> Thanks,
>
> Robert
>
> -- Mesaj redirecționat --
> From: Apache Jenkins Server 
> To: 
> Cc:
> Bcc:
> Date: Wed, 17 Jan 2018 06:12:03 +
> Subject: Jenkins build is still unstable: Jackrabbit-Oak-Windows #110
> See  110/display/redirect?page=changes>
>
>
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.2.28

[Davide Giannella]

[X] +1 Release this package as Apache Jackrabbit Oak 1.2.28

D.

potential Oak call topic: baseline comparison version changes

[Julian Reschke]

1. Decide what to set it to on trunk
2. Decide what to set it to on stable releases
3. Document the above in the release procedure
4. Check past releases and Jackrabbit for consistency

[Fwd: Jenkins build is still unstable: Jackrabbit-Oak-Windows #110]

[Robert Munteanu]

Hi,

We have gathered some failures on Windows ( 11 tests failing now ). 


org.apache.jackrabbit.oak.run.osgi.DocumentNodeStoreConfigTest.testRDBDocumentStoreRestart

org.apache.jackrabbit.oak.run.osgi.RepositoryShutdownTest.multipleShutdownAndWait

org.apache.jackrabbit.oak.run.osgi.DocumentNodeStoreConfigTest.testRDBDocumentStoreLateDataSource

org.apache.jackrabbit.oak.run.osgi.DocumentNodeStoreConfigTest.testRDBDocumentStoreLateDataSource

org.apache.jackrabbit.oak.segment.standby.BrokenNetworkIT.testProxySSLSkippedBytes

org.apache.jackrabbit.oak.segment.standby.BrokenNetworkIT.testProxyFlippedStartByte

org.apache.jackrabbit.oak.segment.standby.BrokenNetworkIT.testProxySSLSkippedBytesIntermediateChange

org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT.testResilientSync

org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT.testSyncUpdatedBinaryProperty
org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT.testSync

org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT.testSyncBigBlob

Would be great to have them reviewed by those that touched those areas of code 
recently.

Thanks,

Robert--- Begin Message ---
See 


--- End Message ---