[jira] [Commented] (JCRVLT-248) Support install hook bundles

[Tobias Bocanegra (JIRA)]

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

Tobias Bocanegra commented on JCRVLT-248:
-

[~kwin] [~cziegeler] [~reschke] do you see any problem with the filevault 
bundle having a runtime dependency to OSGi core? so far it didn't. i could try 
to make it optional.

> Support install hook bundles
> 
>
> Key: JCRVLT-248
> URL: https://issues.apache.org/jira/browse/JCRVLT-248
> Project: Jackrabbit FileVault
>  Issue Type: Improvement
>  Components: Packaging
>Affects Versions: 3.1.42
>Reporter: Tobias Bocanegra
>
> it would be helpful if the package installer could handle install hook 
> bundles OR if it could register install "hook" components in the felix admin 
> for execution. this would simplify the implementation of hooks that require 
> other osgi services for execution.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Jackrabbit-trunk - Build # 2546 - Still Failing

[Apache Jenkins Server]

The Apache Jenkins build system has built Jackrabbit-trunk (build #2546)

Status: Still Failing

Check console output at https://builds.apache.org/job/Jackrabbit-trunk/2546/ to 
view the results.

[jira] [Commented] (JCRVLT-230) Allow to give an explicit directory as source for META-INF/vault

[Tobias Bocanegra (JIRA)]

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

Tobias Bocanegra commented on JCRVLT-230:
-

ok. added some more tests and javadoc:
https://github.com/apache/jackrabbit-filevault-package-maven-plugin/pull/8

> Allow to give an explicit directory as source for META-INF/vault
> 
>
> Key: JCRVLT-230
> URL: https://issues.apache.org/jira/browse/JCRVLT-230
> Project: Jackrabbit FileVault
>  Issue Type: Improvement
>  Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.0
>Reporter: Konrad Windszus
>Assignee: Tobias Bocanegra
> Fix For: package-maven-plugin-1.0.1
>
>
> Currently the {{META-INF/vault}} structure within the packages is built from 
> {{/META-INF/vault}}.
> This directory is used for two purposes
> # It receives the generated filter.xml, the merged properties.xml, the 
> config.xml and the settings.xml
> # It acts as a source for the resulting package's META-INF/vault
> Not all meta files below META-INF/vault are being generated through the 
> plugin itself. Some need to be written manually to {{workDirectory}} with the 
> help of the {{maven-resource-plugin}}.
> It would be good to allow to give an explicit source directory for the 
> META-INF/vault directory (similar to {{jcrSourceDirectory}}) separated from 
> {{workDirectory}}. This would allow to e.g. specify the packages thumbnail 
> image, without being forced to copy it over to from src to target.
> In addition this parameter should clearly define which meta files are always 
> generated by the filevault-package-maven-plugin and are therefore never 
> considered, even if they are located in the given META-INF/vault source 
> directory.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JCR-4231) Upgrade aws-java-sdk-s3 dependency to 1.11.241

[Julian Reschke (JIRA)]

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

Julian Reschke commented on JCR-4231:
-

trunk: [r1817213|http://svn.apache.org/r1817213]


> Upgrade aws-java-sdk-s3 dependency to 1.11.241
> --
>
> Key: JCR-4231
> URL: https://issues.apache.org/jira/browse/JCR-4231
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: jackrabbit-aws-ext
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_jcr_2_16
> Fix For: 2.18, 2.17.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JCRVLT-230) Allow to give an explicit directory as source for META-INF/vault

[Tobias Bocanegra (JIRA)]

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

Tobias Bocanegra commented on JCRVLT-230:
-

here's the PR
https://github.com/apache/jackrabbit-filevault-package-maven-plugin/pull/8



> Allow to give an explicit directory as source for META-INF/vault
> 
>
> Key: JCRVLT-230
> URL: https://issues.apache.org/jira/browse/JCRVLT-230
> Project: Jackrabbit FileVault
>  Issue Type: Improvement
>  Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.0
>Reporter: Konrad Windszus
>Assignee: Tobias Bocanegra
> Fix For: package-maven-plugin-1.0.1
>
>
> Currently the {{META-INF/vault}} structure within the packages is built from 
> {{/META-INF/vault}}.
> This directory is used for two purposes
> # It receives the generated filter.xml, the merged properties.xml, the 
> config.xml and the settings.xml
> # It acts as a source for the resulting package's META-INF/vault
> Not all meta files below META-INF/vault are being generated through the 
> plugin itself. Some need to be written manually to {{workDirectory}} with the 
> help of the {{maven-resource-plugin}}.
> It would be good to allow to give an explicit source directory for the 
> META-INF/vault directory (similar to {{jcrSourceDirectory}}) separated from 
> {{workDirectory}}. This would allow to e.g. specify the packages thumbnail 
> image, without being forced to copy it over to from src to target.
> In addition this parameter should clearly define which meta files are always 
> generated by the filevault-package-maven-plugin and are therefore never 
> considered, even if they are located in the given META-INF/vault source 
> directory.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (JCR-4231) Upgrade aws-java-sdk-s3 dependency to 1.11.241

[Julian Reschke (JIRA)]

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

Julian Reschke resolved JCR-4231.
-
   Resolution: Fixed
Fix Version/s: 2.17.0

> Upgrade aws-java-sdk-s3 dependency to 1.11.241
> --
>
> Key: JCR-4231
> URL: https://issues.apache.org/jira/browse/JCR-4231
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: jackrabbit-aws-ext
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_jcr_2_16
> Fix For: 2.18, 2.17.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (JCR-4231) Upgrade aws-java-sdk-s3 dependency to 1.11.241

[Julian Reschke (JIRA)]

Julian Reschke created JCR-4231:
---

 Summary: Upgrade aws-java-sdk-s3 dependency to 1.11.241
 Key: JCR-4231
 URL: https://issues.apache.org/jira/browse/JCR-4231
 Project: Jackrabbit Content Repository
  Issue Type: Task
  Components: jackrabbit-aws-ext
Reporter: Julian Reschke
Assignee: Julian Reschke
Priority: Minor
 Fix For: 2.18






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4231) Upgrade aws-java-sdk-s3 dependency to 1.11.241

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4231:

Labels: candidate_jcr_2_16  (was: )

> Upgrade aws-java-sdk-s3 dependency to 1.11.241
> --
>
> Key: JCR-4231
> URL: https://issues.apache.org/jira/browse/JCR-4231
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: jackrabbit-aws-ext
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_jcr_2_16
> Fix For: 2.18
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JCRVLT-230) Allow to give an explicit directory as source for META-INF/vault

[Konrad Windszus (JIRA)]

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

Konrad Windszus commented on JCRVLT-230:


As already mentioned in the initial comment, I think it is crucial to note down 
in the javadoc of this parameter which files are getting overwritten by some 
other parameters.

> Allow to give an explicit directory as source for META-INF/vault
> 
>
> Key: JCRVLT-230
> URL: https://issues.apache.org/jira/browse/JCRVLT-230
> Project: Jackrabbit FileVault
>  Issue Type: Improvement
>  Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.0
>Reporter: Konrad Windszus
>Assignee: Tobias Bocanegra
> Fix For: package-maven-plugin-1.0.1
>
>
> Currently the {{META-INF/vault}} structure within the packages is built from 
> {{/META-INF/vault}}.
> This directory is used for two purposes
> # It receives the generated filter.xml, the merged properties.xml, the 
> config.xml and the settings.xml
> # It acts as a source for the resulting package's META-INF/vault
> Not all meta files below META-INF/vault are being generated through the 
> plugin itself. Some need to be written manually to {{workDirectory}} with the 
> help of the {{maven-resource-plugin}}.
> It would be good to allow to give an explicit source directory for the 
> META-INF/vault directory (similar to {{jcrSourceDirectory}}) separated from 
> {{workDirectory}}. This would allow to e.g. specify the packages thumbnail 
> image, without being forced to copy it over to from src to target.
> In addition this parameter should clearly define which meta files are always 
> generated by the filevault-package-maven-plugin and are therefore never 
> considered, even if they are located in the given META-INF/vault source 
> directory.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JCRVLT-230) Allow to give an explicit directory as source for META-INF/vault

[Tobias Bocanegra (JIRA)]

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

Tobias Bocanegra commented on JCRVLT-230:
-

suggested changed:
https://github.com/tripodsan/jackrabbit-filevault-package-maven-plugin/compare/trunk...tripodsan:JCRVLT-230

> Allow to give an explicit directory as source for META-INF/vault
> 
>
> Key: JCRVLT-230
> URL: https://issues.apache.org/jira/browse/JCRVLT-230
> Project: Jackrabbit FileVault
>  Issue Type: Improvement
>  Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.0
>Reporter: Konrad Windszus
>Assignee: Tobias Bocanegra
> Fix For: package-maven-plugin-1.0.1
>
>
> Currently the {{META-INF/vault}} structure within the packages is built from 
> {{/META-INF/vault}}.
> This directory is used for two purposes
> # It receives the generated filter.xml, the merged properties.xml, the 
> config.xml and the settings.xml
> # It acts as a source for the resulting package's META-INF/vault
> Not all meta files below META-INF/vault are being generated through the 
> plugin itself. Some need to be written manually to {{workDirectory}} with the 
> help of the {{maven-resource-plugin}}.
> It would be good to allow to give an explicit source directory for the 
> META-INF/vault directory (similar to {{jcrSourceDirectory}}) separated from 
> {{workDirectory}}. This would allow to e.g. specify the packages thumbnail 
> image, without being forced to copy it over to from src to target.
> In addition this parameter should clearly define which meta files are always 
> generated by the filevault-package-maven-plugin and are therefore never 
> considered, even if they are located in the given META-INF/vault source 
> directory.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (JCR-4223) Upgrade commons-fileupload dependency to 1.3.3

[Julian Reschke (JIRA)]

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

Julian Reschke edited comment on JCR-4223 at 12/5/17 3:12 PM:
--

trunk: [r1817097|http://svn.apache.org/r1817097]
2.16: [r1817178|http://svn.apache.org/r1817178]
2.14: [r1817179|http://svn.apache.org/r1817179]
2.12: [r1817181|http://svn.apache.org/r1817181]
2.10: [r1817191|http://svn.apache.org/r1817191]
2.8: [r1817208|http://svn.apache.org/r1817208]
2.6: [r1817211|http://svn.apache.org/r1817211]



was (Author: reschke):
trunk: [r1817097|http://svn.apache.org/r1817097]
2.16: [r1817178|http://svn.apache.org/r1817178]
2.14: [r1817179|http://svn.apache.org/r1817179]
2.12: [r1817181|http://svn.apache.org/r1817181]
2.10: [r1817191|http://svn.apache.org/r1817191]
2.8: [r1817208|http://svn.apache.org/r1817208]


> Upgrade commons-fileupload dependency to 1.3.3
> --
>
> Key: JCR-4223
> URL: https://issues.apache.org/jira/browse/JCR-4223
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Fix For: 2.10.7, 2.6.10, 2.8.7, 2.18, 2.12.9, 2.14.5, 2.17.0, 
> 2.16.1
>
>
> See CVE-2017-12617



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4223) Upgrade commons-fileupload dependency to 1.3.3

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4223:

Labels:   (was: candidate_jcr_2_6)

> Upgrade commons-fileupload dependency to 1.3.3
> --
>
> Key: JCR-4223
> URL: https://issues.apache.org/jira/browse/JCR-4223
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Fix For: 2.10.7, 2.6.10, 2.8.7, 2.18, 2.12.9, 2.14.5, 2.17.0, 
> 2.16.1
>
>
> See CVE-2017-12617



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4223) Upgrade commons-fileupload dependency to 1.3.3

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4223:

Fix Version/s: 2.6.10

> Upgrade commons-fileupload dependency to 1.3.3
> --
>
> Key: JCR-4223
> URL: https://issues.apache.org/jira/browse/JCR-4223
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Fix For: 2.10.7, 2.6.10, 2.8.7, 2.18, 2.12.9, 2.14.5, 2.17.0, 
> 2.16.1
>
>
> See CVE-2017-12617



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (JCR-4223) Upgrade commons-fileupload dependency to 1.3.3

[Julian Reschke (JIRA)]

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

Julian Reschke edited comment on JCR-4223 at 12/5/17 2:53 PM:
--

trunk: [r1817097|http://svn.apache.org/r1817097]
2.16: [r1817178|http://svn.apache.org/r1817178]
2.14: [r1817179|http://svn.apache.org/r1817179]
2.12: [r1817181|http://svn.apache.org/r1817181]
2.10: [r1817191|http://svn.apache.org/r1817191]
2.8: [r1817208|http://svn.apache.org/r1817208]



was (Author: reschke):
trunk: [r1817097|http://svn.apache.org/r1817097]
2.16: [r1817178|http://svn.apache.org/r1817178]
2.14: [r1817179|http://svn.apache.org/r1817179]
2.12: [r1817181|http://svn.apache.org/r1817181]
2.10: [r1817191|http://svn.apache.org/r1817191]


> Upgrade commons-fileupload dependency to 1.3.3
> --
>
> Key: JCR-4223
> URL: https://issues.apache.org/jira/browse/JCR-4223
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_6
> Fix For: 2.10.7, 2.8.7, 2.18, 2.12.9, 2.14.5, 2.17.0, 2.16.1
>
>
> See CVE-2017-12617



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4223) Upgrade commons-fileupload dependency to 1.3.3

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4223:

Labels: candidate_jcr_2_6  (was: candidate_jcr_2_6 candidate_jcr_2_8)

> Upgrade commons-fileupload dependency to 1.3.3
> --
>
> Key: JCR-4223
> URL: https://issues.apache.org/jira/browse/JCR-4223
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_6
> Fix For: 2.10.7, 2.8.7, 2.18, 2.12.9, 2.14.5, 2.17.0, 2.16.1
>
>
> See CVE-2017-12617



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4223) Upgrade commons-fileupload dependency to 1.3.3

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4223:

Fix Version/s: 2.8.7

> Upgrade commons-fileupload dependency to 1.3.3
> --
>
> Key: JCR-4223
> URL: https://issues.apache.org/jira/browse/JCR-4223
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.10.7, 2.8.7, 2.18, 2.12.9, 2.14.5, 2.17.0, 2.16.1
>
>
> See CVE-2017-12617



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Jackrabbit-trunk - Build # 2545 - Still Failing

[Apache Jenkins Server]

The Apache Jenkins build system has built Jackrabbit-trunk (build #2545)

Status: Still Failing

Check console output at https://builds.apache.org/job/Jackrabbit-trunk/2545/ to 
view the results.

[jira] [Comment Edited] (JCR-4139) Update commons-fileupload dependency to 1.3.2

[Julian Reschke (JIRA)]

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

Julian Reschke edited comment on JCR-4139 at 12/5/17 2:31 PM:
--

trunk: [r1797209|http://svn.apache.org/r1797209]
2.16: [r1797209|http://svn.apache.org/r1797209]
2.14: [r1807266|http://svn.apache.org/r1807266]
2.12: [r1809953|http://svn.apache.org/r1809953]
2.10: [r1811736|http://svn.apache.org/r1811736]
2.8: [r1817200|http://svn.apache.org/r1817200]
2.6: [r1817204|http://svn.apache.org/r1817204]


was (Author: reschke):
trunk: [r1797209|http://svn.apache.org/r1797209]
2.16: [r1797209|http://svn.apache.org/r1797209]
2.14: [r1807266|http://svn.apache.org/r1807266]
2.12: [r1809953|http://svn.apache.org/r1809953]
2.10: [r1811736|http://svn.apache.org/r1811736]
2.8: [r1817200|http://svn.apache.org/r1817200]


> Update commons-fileupload dependency to 1.3.2
> -
>
> Key: JCR-4139
> URL: https://issues.apache.org/jira/browse/JCR-4139
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Trivial
> Fix For: 2.16, 2.12.8, 2.15.3, 2.10.7, 2.14.3, 2.6.10, 2.8.7
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4139) Update commons-fileupload dependency to 1.3.2

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4139:

Fix Version/s: 2.6.10

> Update commons-fileupload dependency to 1.3.2
> -
>
> Key: JCR-4139
> URL: https://issues.apache.org/jira/browse/JCR-4139
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Trivial
> Fix For: 2.16, 2.12.8, 2.15.3, 2.10.7, 2.14.3, 2.6.10, 2.8.7
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4139) Update commons-fileupload dependency to 1.3.2

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4139:

Labels:   (was: candidate_jcr_2_6)

> Update commons-fileupload dependency to 1.3.2
> -
>
> Key: JCR-4139
> URL: https://issues.apache.org/jira/browse/JCR-4139
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Trivial
> Fix For: 2.16, 2.12.8, 2.15.3, 2.10.7, 2.14.3, 2.6.10, 2.8.7
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCRVLT-230) Allow to give an explicit directory as source for META-INF/vault

[Tobias Bocanegra (JIRA)]

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

Tobias Bocanegra updated JCRVLT-230:

Fix Version/s: package-maven-plugin-1.0.1

> Allow to give an explicit directory as source for META-INF/vault
> 
>
> Key: JCRVLT-230
> URL: https://issues.apache.org/jira/browse/JCRVLT-230
> Project: Jackrabbit FileVault
>  Issue Type: Improvement
>  Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.0
>Reporter: Konrad Windszus
>Assignee: Tobias Bocanegra
> Fix For: package-maven-plugin-1.0.1
>
>
> Currently the {{META-INF/vault}} structure within the packages is built from 
> {{/META-INF/vault}}.
> This directory is used for two purposes
> # It receives the generated filter.xml, the merged properties.xml, the 
> config.xml and the settings.xml
> # It acts as a source for the resulting package's META-INF/vault
> Not all meta files below META-INF/vault are being generated through the 
> plugin itself. Some need to be written manually to {{workDirectory}} with the 
> help of the {{maven-resource-plugin}}.
> It would be good to allow to give an explicit source directory for the 
> META-INF/vault directory (similar to {{jcrSourceDirectory}}) separated from 
> {{workDirectory}}. This would allow to e.g. specify the packages thumbnail 
> image, without being forced to copy it over to from src to target.
> In addition this parameter should clearly define which meta files are always 
> generated by the filevault-package-maven-plugin and are therefore never 
> considered, even if they are located in the given META-INF/vault source 
> directory.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (JCRVLT-230) Allow to give an explicit directory as source for META-INF/vault

[Tobias Bocanegra (JIRA)]

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

Tobias Bocanegra reassigned JCRVLT-230:
---

Assignee: Tobias Bocanegra

> Allow to give an explicit directory as source for META-INF/vault
> 
>
> Key: JCRVLT-230
> URL: https://issues.apache.org/jira/browse/JCRVLT-230
> Project: Jackrabbit FileVault
>  Issue Type: Improvement
>  Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.0
>Reporter: Konrad Windszus
>Assignee: Tobias Bocanegra
> Fix For: package-maven-plugin-1.0.1
>
>
> Currently the {{META-INF/vault}} structure within the packages is built from 
> {{/META-INF/vault}}.
> This directory is used for two purposes
> # It receives the generated filter.xml, the merged properties.xml, the 
> config.xml and the settings.xml
> # It acts as a source for the resulting package's META-INF/vault
> Not all meta files below META-INF/vault are being generated through the 
> plugin itself. Some need to be written manually to {{workDirectory}} with the 
> help of the {{maven-resource-plugin}}.
> It would be good to allow to give an explicit source directory for the 
> META-INF/vault directory (similar to {{jcrSourceDirectory}}) separated from 
> {{workDirectory}}. This would allow to e.g. specify the packages thumbnail 
> image, without being forced to copy it over to from src to target.
> In addition this parameter should clearly define which meta files are always 
> generated by the filevault-package-maven-plugin and are therefore never 
> considered, even if they are located in the given META-INF/vault source 
> directory.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCRVLT-249) Allow to include a hook jar via a dedicated parameter

[Konrad Windszus (JIRA)]

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

Konrad Windszus updated JCRVLT-249:
---
Affects Version/s: package-maven-plugin-1.0.0
  Component/s: package maven plugin
   Issue Type: Improvement  (was: Bug)

> Allow to include a hook jar via a dedicated parameter
> -
>
> Key: JCRVLT-249
> URL: https://issues.apache.org/jira/browse/JCRVLT-249
> Project: Jackrabbit FileVault
>  Issue Type: Improvement
>  Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.0
>Reporter: Konrad Windszus
>
> Similar to the package thumbnails (JCRVLT-240) there should be a dedicated 
> parameter for including a local hook JAR (either regular JAR or bundle, once 
> JCRVLT-248 is resolved) within a package. This parameter should act similar 
> to {{subPackages}} or {{embeds}}, i.e. look in the project dependencies for 
> an artifact with the given artifactId/groupId/version and if found embed that 
> in {{META-INF/vault/hooks}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (JCRVLT-249) Allow to include a hook jar via a dedicated parameter

[Konrad Windszus (JIRA)]

Konrad Windszus created JCRVLT-249:
--

 Summary: Allow to include a hook jar via a dedicated parameter
 Key: JCRVLT-249
 URL: https://issues.apache.org/jira/browse/JCRVLT-249
 Project: Jackrabbit FileVault
  Issue Type: Bug
Reporter: Konrad Windszus


Similar to the package thumbnails (JCRVLT-240) there should be a dedicated 
parameter for including a local hook JAR (either regular JAR or bundle, once 
JCRVLT-248 is resolved) within a package. This parameter should act similar to 
{{subPackages}} or {{embeds}}, i.e. look in the project dependencies for an 
artifact with the given artifactId/groupId/version and if found embed that in 
{{META-INF/vault/hooks}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JCR-4228) Update Oak dependency to latest 1.0 stable release

[Julian Reschke (JIRA)]

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

Julian Reschke commented on JCR-4228:
-

trunk: [r1817201|http://svn.apache.org/r1817201]


> Update Oak dependency to latest 1.0 stable release
> --
>
> Key: JCR-4228
> URL: https://issues.apache.org/jira/browse/JCR-4228
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: jackrabbit-webapp
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_16, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.18, 2.17.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (JCR-4228) Update Oak dependency to latest 1.0 stable release

[Julian Reschke (JIRA)]

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

Julian Reschke resolved JCR-4228.
-
   Resolution: Fixed
Fix Version/s: 2.17.0

> Update Oak dependency to latest 1.0 stable release
> --
>
> Key: JCR-4228
> URL: https://issues.apache.org/jira/browse/JCR-4228
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: jackrabbit-webapp
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_16, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.18, 2.17.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4228) Update Oak dependency to latest 1.0 stable release

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4228:

Fix Version/s: 2.18

> Update Oak dependency to latest 1.0 stable release
> --
>
> Key: JCR-4228
> URL: https://issues.apache.org/jira/browse/JCR-4228
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: jackrabbit-webapp
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_16, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.18
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4228) Update Oak dependency to latest 1.0 stable release

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4228:

Labels: candidate_jcr_2_10 candidate_jcr_2_12 candidate_jcr_2_14 
candidate_jcr_2_16 candidate_jcr_2_6 candidate_jcr_2_8  (was: )

> Update Oak dependency to latest 1.0 stable release
> --
>
> Key: JCR-4228
> URL: https://issues.apache.org/jira/browse/JCR-4228
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: jackrabbit-webapp
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_16, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.18
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (JCR-4139) Update commons-fileupload dependency to 1.3.2

[Julian Reschke (JIRA)]

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

Julian Reschke edited comment on JCR-4139 at 12/5/17 1:49 PM:
--

trunk: [r1797209|http://svn.apache.org/r1797209]
2.16: [r1797209|http://svn.apache.org/r1797209]
2.14: [r1807266|http://svn.apache.org/r1807266]
2.12: [r1809953|http://svn.apache.org/r1809953]
2.10: [r1811736|http://svn.apache.org/r1811736]
2.8: [r1817200|http://svn.apache.org/r1817200]



was (Author: reschke):
trunk: [r1797209|http://svn.apache.org/r1797209]
2.14: [r1807266|http://svn.apache.org/r1807266]
2.12: [r1809953|http://svn.apache.org/r1809953]
2.10: [r1811736|http://svn.apache.org/r1811736]



> Update commons-fileupload dependency to 1.3.2
> -
>
> Key: JCR-4139
> URL: https://issues.apache.org/jira/browse/JCR-4139
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Trivial
>  Labels: candidate_jcr_2_6
> Fix For: 2.16, 2.12.8, 2.15.3, 2.10.7, 2.14.3, 2.8.7
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4139) Update commons-fileupload dependency to 1.3.2

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4139:

Labels: candidate_jcr_2_6  (was: candidate_jcr_2_6 candidate_jcr_2_8)

> Update commons-fileupload dependency to 1.3.2
> -
>
> Key: JCR-4139
> URL: https://issues.apache.org/jira/browse/JCR-4139
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Trivial
>  Labels: candidate_jcr_2_6
> Fix For: 2.16, 2.12.8, 2.15.3, 2.10.7, 2.14.3, 2.8.7
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4139) Update commons-fileupload dependency to 1.3.2

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4139:

Fix Version/s: 2.8.7

> Update commons-fileupload dependency to 1.3.2
> -
>
> Key: JCR-4139
> URL: https://issues.apache.org/jira/browse/JCR-4139
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Trivial
>  Labels: candidate_jcr_2_6
> Fix For: 2.16, 2.12.8, 2.15.3, 2.10.7, 2.14.3, 2.8.7
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4139) Update commons-fileupload dependency to 1.3.2

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4139:

Labels: candidate_jcr_2_6 candidate_jcr_2_8  (was: candidate_jcr_2_8)

> Update commons-fileupload dependency to 1.3.2
> -
>
> Key: JCR-4139
> URL: https://issues.apache.org/jira/browse/JCR-4139
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Trivial
>  Labels: candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.16, 2.12.8, 2.15.3, 2.10.7, 2.14.3
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: new release of Filevault Package Maven Plugin?

[Tobias Bocanegra]

Ok, I fixed the site:


Version: 1.0.0
http://jackrabbit.apache.org/filevault-package-maven-plugin/

Version: 1.0.1-SNAPSHOT:
http://jackrabbit.apache.org/filevault-package-maven-plugin-archives/1.0.1-SNAPSHOT/

Regards, Toby

[jira] [Comment Edited] (JCR-4223) Upgrade commons-fileupload dependency to 1.3.3

[Julian Reschke (JIRA)]

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

Julian Reschke edited comment on JCR-4223 at 12/5/17 1:14 PM:
--

trunk: [r1817097|http://svn.apache.org/r1817097]
2.16: [r1817178|http://svn.apache.org/r1817178]
2.14: [r1817179|http://svn.apache.org/r1817179]
2.12: [r1817181|http://svn.apache.org/r1817181]
2.10: [r1817191|http://svn.apache.org/r1817191]



was (Author: reschke):
trunk: [r1817097|http://svn.apache.org/r1817097]
2.16: [r1817178|http://svn.apache.org/r1817178]
2.14: [r1817179|http://svn.apache.org/r1817179]
2.12: [r1817181|http://svn.apache.org/r1817181]


> Upgrade commons-fileupload dependency to 1.3.3
> --
>
> Key: JCR-4223
> URL: https://issues.apache.org/jira/browse/JCR-4223
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.10.7, 2.18, 2.12.9, 2.14.5, 2.17.0, 2.16.1
>
>
> See CVE-2017-12617



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4223) Upgrade commons-fileupload dependency to 1.3.3

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4223:

Labels: candidate_jcr_2_6 candidate_jcr_2_8  (was: candidate_jcr_2_10 
candidate_jcr_2_6 candidate_jcr_2_8)

> Upgrade commons-fileupload dependency to 1.3.3
> --
>
> Key: JCR-4223
> URL: https://issues.apache.org/jira/browse/JCR-4223
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.10.7, 2.18, 2.12.9, 2.14.5, 2.17.0, 2.16.1
>
>
> See CVE-2017-12617



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4223) Upgrade commons-fileupload dependency to 1.3.3

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4223:

Fix Version/s: 2.10.7

> Upgrade commons-fileupload dependency to 1.3.3
> --
>
> Key: JCR-4223
> URL: https://issues.apache.org/jira/browse/JCR-4223
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.10.7, 2.18, 2.12.9, 2.14.5, 2.17.0, 2.16.1
>
>
> See CVE-2017-12617



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (JCR-4230) Move -webapp and -standalone to examples

[Julian Reschke (JIRA)]

Julian Reschke created JCR-4230:
---

 Summary: Move -webapp and -standalone to examples
 Key: JCR-4230
 URL: https://issues.apache.org/jira/browse/JCR-4230
 Project: Jackrabbit Content Repository
  Issue Type: Task
  Components: jackrabbit-standalone, jackrabbit-webapp
Reporter: Julian Reschke
Assignee: Julian Reschke






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4228) Update Oak dependency to latest 1.0 stable release

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4228:

Priority: Minor  (was: Major)

> Update Oak dependency to latest 1.0 stable release
> --
>
> Key: JCR-4228
> URL: https://issues.apache.org/jira/browse/JCR-4228
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: jackrabbit-webapp
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (JCR-4229) Remove Oak dependency in webapp

[Julian Reschke (JIRA)]

Julian Reschke created JCR-4229:
---

 Summary: Remove Oak dependency in webapp
 Key: JCR-4229
 URL: https://issues.apache.org/jira/browse/JCR-4229
 Project: Jackrabbit Content Repository
  Issue Type: Task
  Components: jackrabbit-webapp
Reporter: Julian Reschke
Assignee: Julian Reschke
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (JCR-4228) Update Oak dependency to latest 1.0 stable release

[Julian Reschke (JIRA)]

Julian Reschke created JCR-4228:
---

 Summary: Update Oak dependency to latest 1.0 stable release
 Key: JCR-4228
 URL: https://issues.apache.org/jira/browse/JCR-4228
 Project: Jackrabbit Content Repository
  Issue Type: Task
  Components: jackrabbit-webapp
Reporter: Julian Reschke
Assignee: Julian Reschke






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCRVLT-230) Allow to give an explicit directory as source for META-INF/vault

[Konrad Windszus (JIRA)]

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

Konrad Windszus updated JCRVLT-230:
---
Description: 
Currently the {{META-INF/vault}} structure within the packages is built from 
{{/META-INF/vault}}.

This directory is used for two purposes
# It receives the generated filter.xml, the merged properties.xml, the 
config.xml and the settings.xml
# It acts as a source for the resulting package's META-INF/vault

Not all meta files below META-INF/vault are being generated through the plugin 
itself. Some need to be written manually to {{workDirectory}} with the help of 
the {{maven-resource-plugin}}.

It would be good to allow to give an explicit source directory for the 
META-INF/vault directory (similar to {{jcrSourceDirectory}}) separated from 
{{workDirectory}}. This would allow to e.g. specify the packages thumbnail 
image, without being forced to copy it over to from src to target.
In addition this parameter should clearly define which meta files are always 
generated by the filevault-package-maven-plugin and are therefore never 
considered, even if they are located in the given META-INF/vault source 
directory.

  was:
Currently the {{META-INF/vault}} structure within the packages is built from 
{{/META-INF/vault}}.

This directory is used for two purposes
# It receives the generated filter.xml, the merged properties.xml, the 
config.xml and the settings.xml
# It acts as a source for the resulting package's META-INF/vault

Not all meta files below META-INF/vault are being generated through the plugin 
itself. Some need to be written manually to {{workDirectory}} with the help of 
the {{maven-resource-plugin}}.

It would be good to allow to give an explicit source directory for the 
META-INF/vault directory (similar to {{jcrSourceDirectory}}) separated from 
{{workDirectory}}. This would allow to e.g. specify the packages thumbnail 
image, without being forced to copy it over to from src to target.
In addition this parameter should clearly define which meta files are generated 
by the filevault-package-maven-plugin and are therefore never considered, even 
if they are located in the given META-INF/vault source directory.


> Allow to give an explicit directory as source for META-INF/vault
> 
>
> Key: JCRVLT-230
> URL: https://issues.apache.org/jira/browse/JCRVLT-230
> Project: Jackrabbit FileVault
>  Issue Type: Improvement
>  Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.0
>Reporter: Konrad Windszus
>
> Currently the {{META-INF/vault}} structure within the packages is built from 
> {{/META-INF/vault}}.
> This directory is used for two purposes
> # It receives the generated filter.xml, the merged properties.xml, the 
> config.xml and the settings.xml
> # It acts as a source for the resulting package's META-INF/vault
> Not all meta files below META-INF/vault are being generated through the 
> plugin itself. Some need to be written manually to {{workDirectory}} with the 
> help of the {{maven-resource-plugin}}.
> It would be good to allow to give an explicit source directory for the 
> META-INF/vault directory (similar to {{jcrSourceDirectory}}) separated from 
> {{workDirectory}}. This would allow to e.g. specify the packages thumbnail 
> image, without being forced to copy it over to from src to target.
> In addition this parameter should clearly define which meta files are always 
> generated by the filevault-package-maven-plugin and are therefore never 
> considered, even if they are located in the given META-INF/vault source 
> directory.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JCRVLT-230) Allow to give an explicit directory as source for META-INF/vault

[Stefan Seifert (JIRA)]

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

Stefan Seifert commented on JCRVLT-230:
---

in wcm.io content package plugin we used a folder 
{{src/main/package-definition}} as default folder for things like filter.xml 
and thumbnail.png.

> Allow to give an explicit directory as source for META-INF/vault
> 
>
> Key: JCRVLT-230
> URL: https://issues.apache.org/jira/browse/JCRVLT-230
> Project: Jackrabbit FileVault
>  Issue Type: Improvement
>  Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.0
>Reporter: Konrad Windszus
>
> Currently the {{META-INF/vault}} structure within the packages is built from 
> {{/META-INF/vault}}.
> This directory is used for two purposes
> # It receives the generated filter.xml, the merged properties.xml, the 
> config.xml and the settings.xml
> # It acts as a source for the resulting package's META-INF/vault
> Not all meta files below META-INF/vault are being generated through the 
> plugin itself. Some need to be written manually to {{workDirectory}} with the 
> help of the {{maven-resource-plugin}}.
> It would be good to allow to give an explicit source directory for the 
> META-INF/vault directory (similar to {{jcrSourceDirectory}}) separated from 
> {{workDirectory}}. This would allow to e.g. specify the packages thumbnail 
> image, without being forced to copy it over to from src to target.
> In addition this parameter should clearly define which meta files are 
> generated by the filevault-package-maven-plugin and are therefore never 
> considered, even if they are located in the given META-INF/vault source 
> directory.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Oak in Jackrabbit components

[Marcel Reutegger]

On 05/12/17 13:27, Julian Reschke wrote:

How about starting with:

- in trunk, remove the oak dependency
- in trunk, move -webapp and -standalone into ./examples
- in maintenance branches, update to latest OAK 1.0.*


+1

Regards
 Marcel

Re: new release of Filevault Package Maven Plugin?

[Tobias Bocanegra]

Hi,

On 5 Dec 2017, at 13:38, Konrad Windszus 
> wrote:

Right now the published website is at version 1.0.1-SNAPSHOT(!!!) so not the 
latest release version. But it would definitely be appreciated to still be able 
to link to an arbitrary released version of the site.

oops...right :-)

I try to clean this up. Good idea with the multiple versions...
Regards, Toby

Re: new release of Filevault Package Maven Plugin?

[Konrad Windszus]

> sure, but I would have like to finish
> 
> https://issues.apache.org/jira/browse/JCRVLT-230
> 
Yes, that would be greatly appreciated.

[jira] [Comment Edited] (JCR-4223) Upgrade commons-fileupload dependency to 1.3.3

[Julian Reschke (JIRA)]

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

Julian Reschke edited comment on JCR-4223 at 12/5/17 12:38 PM:
---

trunk: [r1817097|http://svn.apache.org/r1817097]
2.16: [r1817178|http://svn.apache.org/r1817178]
2.14: [r1817179|http://svn.apache.org/r1817179]
2.12: [r1817181|http://svn.apache.org/r1817181]



was (Author: reschke):
trunk: [r1817097|http://svn.apache.org/r1817097]
2.16: [r1817178|http://svn.apache.org/r1817178]
2.14: [r1817179|http://svn.apache.org/r1817179]


> Upgrade commons-fileupload dependency to 1.3.3
> --
>
> Key: JCR-4223
> URL: https://issues.apache.org/jira/browse/JCR-4223
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.18, 2.12.9, 2.14.5, 2.17.0, 2.16.1
>
>
> See CVE-2017-12617



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: new release of Filevault Package Maven Plugin?

[Konrad Windszus]

Right now the published website is at version 1.0.1-SNAPSHOT(!!!) so not the 
latest release version. But it would definitely be appreciated to still be able 
to link to an arbitrary released version of the site.
Please check out the concept of maven sites at Apache Sling: 
http://sling.apache.org/documentation/development/release-management.html#appendix-b-deploy-maven-plugin-documentation-if-applicable-
 

There multiple versions are properly supported.

> On 5. Dec 2017, at 13:35, Tobias Bocanegra  wrote:
> 
> Hi,
> 
>> On 5 Dec 2017, at 11:12, Konrad Windszus  wrote:
>> 
>> It would be nice to quickly push an updated Maven site of the latest 
>> Snapshot to http://jackrabbit.apache.org/filevault-package-maven-plugin.html 
>> to be able to verify all the changes related to Mojo parameter documentation.
> 
> I think we should keep the published website aligned with the released 
> version.
> You can build the site yourself by executing: `mvn site` and open 
> traget/site/index.html in your browser.
> 
>> 
>>> On 5. Dec 2017, at 11:09, Stefan Seifert  wrote:
>>> 
>>> thanks to toby we have a lot of new features in the filevault package maven 
>>> plugin.
>>> is it possible to releases it any time soon?
>>> no open issues on the release currently [1]
>>> 
>>> stefan
>>> 
>>> [1] https://issues.apache.org/jira/projects/JCRVLT/versions/12342080
> 
> sure, but I would have like to finish
> 
> https://issues.apache.org/jira/browse/JCRVLT-230
> 
> before releasing. WDYT?
> Regards, Toby

[jira] [Updated] (JCR-4223) Upgrade commons-fileupload dependency to 1.3.3

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4223:

Fix Version/s: 2.12.9

> Upgrade commons-fileupload dependency to 1.3.3
> --
>
> Key: JCR-4223
> URL: https://issues.apache.org/jira/browse/JCR-4223
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.18, 2.12.9, 2.14.5, 2.17.0, 2.16.1
>
>
> See CVE-2017-12617



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: new release of Filevault Package Maven Plugin?

[Tobias Bocanegra]

Hi,

> On 5 Dec 2017, at 11:12, Konrad Windszus  wrote:
> 
> It would be nice to quickly push an updated Maven site of the latest Snapshot 
> to http://jackrabbit.apache.org/filevault-package-maven-plugin.html to be 
> able to verify all the changes related to Mojo parameter documentation.

I think we should keep the published website aligned with the released version.
You can build the site yourself by executing: `mvn site` and open 
traget/site/index.html in your browser.

> 
>> On 5. Dec 2017, at 11:09, Stefan Seifert  wrote:
>> 
>> thanks to toby we have a lot of new features in the filevault package maven 
>> plugin.
>> is it possible to releases it any time soon?
>> no open issues on the release currently [1]
>> 
>> stefan
>> 
>> [1] https://issues.apache.org/jira/projects/JCRVLT/versions/12342080

sure, but I would have like to finish

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

before releasing. WDYT?
Regards, Toby

Re: Oak in Jackrabbit components

[Julian Reschke]

On 2017-12-05 13:03, Marcel Reutegger wrote:

Hi,

On 05/12/17 12:50, Julian Reschke wrote:

- Keep the duplicate modules, but remove the Oak dependency in
Jackrabbit


That would be my preference, for simplicity.


OK, then let's do it this way.


Of course then the next question would be: just in trunk, or
everywhere?


I don't have a strong preference, but I would probably only do it in 
trunk and only there move the two modules under examples. The Jackrabbit 
releases on the maintenance branch would still have the two modules. It 
may be a bit strange to suddenly remove them in patch releases. But then 
I'm also not really opposed to removing them, since I consider them 
examples.


How about starting with:

- in trunk, remove the oak dependency
- in trunk, move -webapp and -standalone into ./examples
- in maintenance branches, update to latest OAK 1.0.*

Best regards, Julian

[jira] [Comment Edited] (JCR-4223) Upgrade commons-fileupload dependency to 1.3.3

[Julian Reschke (JIRA)]

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

Julian Reschke edited comment on JCR-4223 at 12/5/17 12:13 PM:
---

trunk: [r1817097|http://svn.apache.org/r1817097]
2.16: [r1817178|http://svn.apache.org/r1817178]
2.14: [r1817179|http://svn.apache.org/r1817179]



was (Author: reschke):
trunk: [r1817097|http://svn.apache.org/r1817097]
2.16: [r1817178|http://svn.apache.org/r1817178]


> Upgrade commons-fileupload dependency to 1.3.3
> --
>
> Key: JCR-4223
> URL: https://issues.apache.org/jira/browse/JCR-4223
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.18, 2.14.5, 2.17.0, 2.16.1
>
>
> See CVE-2017-12617



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4223) Upgrade commons-fileupload dependency to 1.3.3

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4223:

Labels: candidate_jcr_2_10 candidate_jcr_2_12 candidate_jcr_2_6 
candidate_jcr_2_8  (was: candidate_jcr_2_10 candidate_jcr_2_12 
candidate_jcr_2_14 candidate_jcr_2_6 candidate_jcr_2_8)

> Upgrade commons-fileupload dependency to 1.3.3
> --
>
> Key: JCR-4223
> URL: https://issues.apache.org/jira/browse/JCR-4223
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.18, 2.14.5, 2.17.0, 2.16.1
>
>
> See CVE-2017-12617



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4223) Upgrade commons-fileupload dependency to 1.3.3

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4223:

Fix Version/s: 2.14.5

> Upgrade commons-fileupload dependency to 1.3.3
> --
>
> Key: JCR-4223
> URL: https://issues.apache.org/jira/browse/JCR-4223
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.18, 2.14.5, 2.17.0, 2.16.1
>
>
> See CVE-2017-12617



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Oak in Jackrabbit components

[Marcel Reutegger]

Hi,

On 05/12/17 12:50, Julian Reschke wrote:

- Keep the duplicate modules, but remove the Oak dependency in
Jackrabbit


That would be my preference, for simplicity.


OK, then let's do it this way.


Of course then the next question would be: just in trunk, or
everywhere?


I don't have a strong preference, but I would probably only do it in 
trunk and only there move the two modules under examples. The Jackrabbit 
releases on the maintenance branch would still have the two modules. It 
may be a bit strange to suddenly remove them in patch releases. But then 
I'm also not really opposed to removing them, since I consider them 
examples.


Regards
 Marcel

[jira] [Comment Edited] (JCR-4223) Upgrade commons-fileupload dependency to 1.3.3

[Julian Reschke (JIRA)]

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

Julian Reschke edited comment on JCR-4223 at 12/5/17 11:51 AM:
---

trunk: [r1817097|http://svn.apache.org/r1817097]
2.16: [r1817178|http://svn.apache.org/r1817178]



was (Author: reschke):
trunk: [r1817097|http://svn.apache.org/r1817097]


> Upgrade commons-fileupload dependency to 1.3.3
> --
>
> Key: JCR-4223
> URL: https://issues.apache.org/jira/browse/JCR-4223
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.18, 2.17.0, 2.16.1
>
>
> See CVE-2017-12617



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Oak in Jackrabbit components

[Julian Reschke]

On 2017-12-05 12:45, Marcel Reutegger wrote:

Hi,

On 05/12/17 11:47, Julian Reschke wrote:
Btw, there is no oak-standalone. Do you mean oak-run? This one is 
different because it contains various tools that can indeed be used 
as is.


oak-examples/standalone


Oh, right. I was only looking at the top level modules. Thanks for the 
pointer. So, it looks like in Oak standalone and webapp are already 
considered examples.


I guess this is yet another reason for moving also the Jackrabbit 
equivalents to examples and not release them anymore.


But that doesn't answer your question why those modules are duplicated 
and what we should do with the dependencies from Jackrabbit to Oak.


I see two options:

- Keep the duplicate modules, but remove the Oak dependency in Jackrabbit


That would be my preference, for simplicity. Of course then the next 
question would be: just in trunk, or everywhere?


- Remove the modules in Jackrabbit and change the Oak variants to also 
work with Jackrabbit



Best regards, Julian

[jira] [Updated] (JCR-4223) Upgrade commons-fileupload dependency to 1.3.3

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4223:

Labels: candidate_jcr_2_10 candidate_jcr_2_12 candidate_jcr_2_14 
candidate_jcr_2_6 candidate_jcr_2_8  (was: candidate_jcr_2_10 
candidate_jcr_2_12 candidate_jcr_2_14 candidate_jcr_2_16 candidate_jcr_2_6 
candidate_jcr_2_8)

> Upgrade commons-fileupload dependency to 1.3.3
> --
>
> Key: JCR-4223
> URL: https://issues.apache.org/jira/browse/JCR-4223
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.18, 2.17.0, 2.16.1
>
>
> See CVE-2017-12617



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4223) Upgrade commons-fileupload dependency to 1.3.3

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4223:

Fix Version/s: 2.16.1

> Upgrade commons-fileupload dependency to 1.3.3
> --
>
> Key: JCR-4223
> URL: https://issues.apache.org/jira/browse/JCR-4223
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.18, 2.17.0, 2.16.1
>
>
> See CVE-2017-12617



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Oak in Jackrabbit components

[Marcel Reutegger]

Hi,

On 05/12/17 11:47, Julian Reschke wrote:
Btw, there is no oak-standalone. Do you mean oak-run? This one is 
different because it contains various tools that can indeed be used as 
is.


oak-examples/standalone


Oh, right. I was only looking at the top level modules. Thanks for the 
pointer. So, it looks like in Oak standalone and webapp are already 
considered examples.


I guess this is yet another reason for moving also the Jackrabbit 
equivalents to examples and not release them anymore.


But that doesn't answer your question why those modules are duplicated 
and what we should do with the dependencies from Jackrabbit to Oak.


I see two options:

- Keep the duplicate modules, but remove the Oak dependency in Jackrabbit
- Remove the modules in Jackrabbit and change the Oak variants to also 
work with Jackrabbit


Regards
 Marcel

Re: [VOTE] Release Apache Jackrabbit Oak 1.7.12

[Andrei Dulceanu]

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

[INFO] Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-03T22:39:06+03:00)
[INFO] OS name: "mac os x", version: "10.12.6", arch: "x86_64", family:
"mac"
[INFO] Java version: 1.8.0_65, vendor: Oracle Corporation

Regards,
Andrei

2017-12-04 22:25 GMT+02:00 Davide Giannella :

>
> A candidate for the Jackrabbit Oak 1.7.12 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.7.12/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/
> jackrabbit-oak-1.7.12/
>
> The SHA1 checksum of the archive is
> eca45d4c8d357654253eb488526c4ef2b421ed06.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> $ sh check-release.sh oak 1.7.12
> eca45d4c8d357654253eb488526c4ef2b421ed06
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.7.12.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.7.12
> [ ] -1 Do not release this package because...
>
> D.
>

Re: Oak in Jackrabbit components

[Julian Reschke]

On 2017-12-05 11:35, Marcel Reutegger wrote:

Hi,

On 05/12/17 09:51, Julian Reschke wrote:
This seems to originate from 
 - "Oak in 
Jackrabbit deployment packages" - which is still open today.


Can we either remove this, or clarify what Oak version should be 
used here?


I would rather not remove this, but update to the most recent stable 
version.


Per branch, or globally? So would Jackrabbit 2.12 use Oak 1.6.*, or 
something from the "matching" Oak branch?


I don't think we can do this globally. If these components are in use, 
even though I doubt it, user may be forced to upgrade the repository 
between patch releases. I would keep the branches on the 1.0.x releases 
and update the dependency to the most recent stable 1.0.x. For trunk, I 
would update to the most recent 1.6.x.


OK. FWIW, I just tried an upgrade to 1.6 and it fails due to changes in 
the oak-upgrade API (which is in use for some IT tests).


I'm still in favor of this replacement, but it probably means 
Jackrabbit components that bundle other components would have to go 
on their own release schedule.


Understood, but that's additional work, too.

FWIW, we already do have oak-standalone etc, right? Why duplicate this?


Good question. The more I think about those components, the more I 
consider them samples and not components the Jackrabbit project should 
deliver/release as binaries.


I don't think you would ever deploy jackrabbit-webapp as is. In my view, 
this is a sample and should be released with sources only (if at all). 
The same applies to jackrabbit-standalone, which bundles the 
jackrabbit-webapp.


+1

Btw, there is no oak-standalone. Do you mean oak-run? This one is 
different because it contains various tools that can indeed be used as is.


oak-examples/standalone

Best regards, Julian

Re: Oak in Jackrabbit components

[Marcel Reutegger]

Hi,

On 05/12/17 09:51, Julian Reschke wrote:
This seems to originate from 
 - "Oak in Jackrabbit 
deployment packages" - which is still open today.


Can we either remove this, or clarify what Oak version should be used 
here?


I would rather not remove this, but update to the most recent stable 
version.


Per branch, or globally? So would Jackrabbit 2.12 use Oak 1.6.*, or 
something from the "matching" Oak branch?


I don't think we can do this globally. If these components are in use, 
even though I doubt it, user may be forced to upgrade the repository 
between patch releases. I would keep the branches on the 1.0.x releases 
and update the dependency to the most recent stable 1.0.x. For trunk, I 
would update to the most recent 1.6.x.


I'm still in favor of this replacement, but it probably means 
Jackrabbit components that bundle other components would have to go on 
their own release schedule.


Understood, but that's additional work, too.

FWIW, we already do have oak-standalone etc, right? Why duplicate this?


Good question. The more I think about those components, the more I 
consider them samples and not components the Jackrabbit project should 
deliver/release as binaries.


I don't think you would ever deploy jackrabbit-webapp as is. In my view, 
this is a sample and should be released with sources only (if at all). 
The same applies to jackrabbit-standalone, which bundles the 
jackrabbit-webapp.


Btw, there is no oak-standalone. Do you mean oak-run? This one is 
different because it contains various tools that can indeed be used as is.


Regards
 Marcel

Re: new release of Filevault Package Maven Plugin?

[Konrad Windszus]

It would be nice to quickly push an updated Maven site of the latest Snapshot 
to http://jackrabbit.apache.org/filevault-package-maven-plugin.html 
 to be able 
to verify all the changes related to Mojo parameter documentation.

> On 5. Dec 2017, at 11:09, Stefan Seifert  wrote:
> 
> thanks to toby we have a lot of new features in the filevault package maven 
> plugin.
> is it possible to releases it any time soon?
> no open issues on the release currently [1]
> 
> stefan
> 
> [1] https://issues.apache.org/jira/projects/JCRVLT/versions/12342080
> 
> 

new release of Filevault Package Maven Plugin?

[Stefan Seifert]

thanks to toby we have a lot of new features in the filevault package maven 
plugin.
is it possible to releases it any time soon?
no open issues on the release currently [1]

stefan

[1] https://issues.apache.org/jira/projects/JCRVLT/versions/12342080

[jira] [Commented] (JCRVLT-248) Support install hook bundles

[Tobias Bocanegra (JIRA)]

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

Tobias Bocanegra commented on JCRVLT-248:
-

bq. I think it would be good to support both locals as well as hooks registered 
through any other bundle

yes. this might be an option for a further improvement. right now, there isn't 
really a use case for this, IMO and should be discouraged to depend the 
installation of package on services that are already present in the system. 
this makes the installation more fragile.

> Support install hook bundles
> 
>
> Key: JCRVLT-248
> URL: https://issues.apache.org/jira/browse/JCRVLT-248
> Project: Jackrabbit FileVault
>  Issue Type: Improvement
>  Components: Packaging
>Affects Versions: 3.1.42
>Reporter: Tobias Bocanegra
>
> it would be helpful if the package installer could handle install hook 
> bundles OR if it could register install "hook" components in the felix admin 
> for execution. this would simplify the implementation of hooks that require 
> other osgi services for execution.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Oak in Jackrabbit components

[Julian Reschke]

On 2017-12-05 08:57, Marcel Reutegger wrote:

Hi,

On 04/12/17 20:29, Julian Reschke wrote:
I just noticed that jackrabbit-webdav (and other component) have a 
dependency on OAK 1.0.12.


you probably mean jackrabbit-webapp. AFAICS the webdav component does 
not have a dependency on Oak.


Right. The other one is -standalone (transitive).

This seems to originate from 
 - "Oak in Jackrabbit 
deployment packages" - which is still open today.


Can we either remove this, or clarify what Oak version should be used 
here?


I would rather not remove this, but update to the most recent stable 
version.


Per branch, or globally? So would Jackrabbit 2.12 use Oak 1.6.*, or 
something from the "matching" Oak branch?


Active development on the repository implementation happens primarily in 
Oak, while the 'classic' Jackrabbit implementation is pretty much in 
maintenance mode. I think the original idea was to replace the classic 
implementation with Oak at some point, but the effort stopped half way.


Right.

I'm still in favor of this replacement, but it probably means Jackrabbit 
components that bundle other components would have to go on their own 
release schedule.


Understood, but that's additional work, too.

FWIW, we already do have oak-standalone etc, right? Why duplicate this?

Best regards, Julian