Hi,
The vote has passed with the following result :
+1 (binding): Stefan Seifert, Carsten Ziegeler, Justin Edelson
I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.
stefan
+1
On Tue, Mar 21, 2017 at 7:14 AM Stefan Seifert
wrote:
> (sending again as last mail >3 hours ago did not make it to the list)
>
> Hi,
>
> We solved 3 issues in this release:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12339178
>
> Staging repository:
>
+1
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
(sending again as last mail >3 hours ago did not make it to the list)
Hi,
We solved 3 issues in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12339178
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1676/
You can use this UNIX
+1
-sling-plugin/
> maven-sling-plugin: Add "fsmount" and "fsunmount" goals
> ---
>
> Key: SLING-6622
> URL: https://issues.apache.org/jira/browse/SLING-6622
> Project: Sl
Stefan Seifert created SLING-6630:
-
Summary: maven-sling-plugin: Support Mount FileVault XML for File
System Resource Provider
Key: SLING-6630
URL: https://issues.apache.org/jira/browse/SLING-6630
[
https://issues.apache.org/jira/browse/SLING-6630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-6630.
---
Resolution: Fixed
Completed: At revision: 1786207
> maven-sling-plugin: Support Mo
the generated plugin docs
in the same way as it is currently done for maven-bundle-plugin
http://felix.apache.org/documentation/development/release-management-nexus.html#publish-generated-documentation
> maven-sling-plugin: Add "fsmount" and &quo
for the maven-sling-plugin yet,
could you add some documentation to
https://sling.apache.org/documentation/development/sling.html?
> maven-sling-plugin: Add "fsmount" and "fsunmount" goals
> ---
>
> Key:
[
https://issues.apache.org/jira/browse/SLING-6622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-6622.
---
Resolution: Fixed
Completed: At revision: 1785998
> maven-sling-plugin: Add "
Stefan Seifert created SLING-6622:
-
Summary: maven-sling-plugin: Add "fsmount" and "fsunmount" goals
Key: SLING-6622
URL: https://issues.apache.org/jira/browse/SLING-6622
[
https://issues.apache.org/jira/browse/SLING-6619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-6619.
---
Resolution: Fixed
Completed: At revision: 1785906
> maven-sling-plugin: Swi
Stefan Seifert created SLING-6619:
-
Summary: maven-sling-plugin: Switch to javax.json + Johnzon
Key: SLING-6619
URL: https://issues.apache.org/jira/browse/SLING-6619
Project: Sling
Issue
Hi,
The vote has passed with the following result :
+1 (binding): Stefan Seifert, Carsten Ziegeler, Robert Munteanu, Oliver Lietz
I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.
stefan
On Friday 20 January 2017 14:16:10 Stefan Seifert wrote:
> >Shouldn't we rename to sling-maven-plugin to follow Maven's naming policy
> >(see warning during build)?
>
> this would mean a major compatibility break because the artifact id in all
> poms that use it would need to change, and no
>Shouldn't we rename to sling-maven-plugin to follow Maven's naming policy
>(see warning during build)?
this would mean a major compatibility break because the artifact id in all poms
that use it would need to change, and no update check (e.g. versions plugin)
would detect the new version
On Thursday 19 January 2017 22:09:07 Stefan Seifert wrote:
> Hi,
>
> Apache Sling File System Resource Provider 1.2.2*) (4 issues)
> https://issues.apache.org/jira/browse/SLING/fixforversion/12328647
> *) version 1.2.0 was skipped due to an issue found after release
>
> Apa
On Thu, 2017-01-19 at 22:09 +, Stefan Seifert wrote:
> Please vote to approve this release:
+1
Robert
signature.asc
Description: This is a digitally signed message part
+1
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
+1
Hi,
Apache Sling File System Resource Provider 1.2.2*) (4 issues)
https://issues.apache.org/jira/browse/SLING/fixforversion/12328647
*) version 1.2.0 was skipped due to an issue found after release
Apache Sling Maven Sling Plugin 2.1.10 (1 issue)
https://issues.apache.org/jira/browse/SLING
all OSGi subsystem through the maven-sling-plugin
> -
>
> Key: SLING-5309
> URL: https://issues.apache.org/jira/browse/SLING-5309
> Project: Sling
> Issue Type: Improvement
>
/console should be
enough.
> maven-sling-plugin: HTTP Status is not checked correctly when WebConsole
> install method used
>
>
> Key: SLING-5627
>
-sling-plugin has not been changed recently in the regard of how
status codes are handled for POSTs towards the Felix WebConsole
(https://github.com/apache/sling/blame/74d2764d4a092dfd02e2b173564e0105f696c607/tooling/maven/maven-sling-plugin/src/main/java/org/apache/sling/maven/bundlesupport
.
> maven-sling-plugin: HTTP Status is not checked correctly when WebConsole
> install method used
>
>
> Key: SLING-5627
> URL: https://issues.apache.org/jira
://localhost:4502/system/console/bundles}} helped.
> maven-sling-plugin: HTTP Status is not checked correctly when WebConsole
> install method used
>
>
> Key: SLING-5627
>
[
https://issues.apache.org/jira/browse/SLING-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-5628.
Resolution: Fixed
> maven-sling-plugin: Clarify documentation of sling.url and adj
].
> maven-sling-plugin: Clarify documentation of sling.url and adjust the default
> value to the current state
>
>
> Key: SLING-5628
> URL: https:/
at
{{/console/bundles}}.)
> maven-sling-plugin: Clarify documentation of sling.url and adjust the default
> value to the current state
>
>
>
[
https://issues.apache.org/jira/browse/SLING-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-5628:
---
Summary: maven-sling-plugin: Clarify documentation of sling.url and adjust
the default value
[
https://issues.apache.org/jira/browse/SLING-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-5628:
---
Summary: maven-sling-plugin: Clarify documentation of sling.url and fix the
default value
}} description in the
documentation
(https://sling.apache.org/documentation/development/sling.html#the-install-goal)
and also to give that a more reasonable default value (which will not work
with AEM though).
> maven-sling-plugin: HTTP Status is not checked correctly when WebConsole
> install
on your side:
The Felix WebConsole BundlesServlet will never return a 201 for a POST request
(https://github.com/apache/felix/blob/trunk/webconsole/src/main/java/org/apache/felix/webconsole/internal/core/BundlesServlet.java#L322).
And the maven-sling-plugin has not been changed recently
Peter Melnikov created SLING-5627:
-
Summary: maven-sling-plugin: HTTP Status is not checked correctly
when WebConsole install method used
Key: SLING-5627
URL: https://issues.apache.org/jira/browse/SLING-5627
Hi,
The vote has passed with the following result :
+1 (binding): Robert Munteanu, Carsten Ziegeler, Stefan Seifert
I will promote the artifacts to the central Maven repository.
Could some PMC member please move the artifacts to dist?
Thanks for voting,
Konrad
Konrad Windszus created SLING-5615:
--
Summary: Upgrade pluginMgmt to maven-sling-plugin 2.1.8
Key: SLING-5615
URL: https://issues.apache.org/jira/browse/SLING-5615
Project: Sling
Issue Type
Konrad Windszus wrote
> Hi,
>
> The vote has passed with the following result :
>
> +1 (binding): Robert Munteanu, Carsten Ziegeler, Stefan Seifert
>
> I will promote the artifacts to the central Maven repository.
> Could some PMC member please move the artifacts to dist?
Done
Thanks
Carsten
://svn.apache.org/r1735283].
> Upgrade pluginMgmt to maven-sling-plugin 2.1.8
> --
>
> Key: SLING-5615
> URL: https://issues.apache.org/jira/browse/SLING-5615
> Project: Sling
> Is
[
https://issues.apache.org/jira/browse/SLING-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus closed SLING-5335.
--
> maven-sling-plugin: Allow installing bundles through SlingPostServlet
> mech
+1
Actually that will not reveal what needs to be fixed in the pom.xml until
another release was done.
> On 14 Mar 2016, at 08:48, Carsten Ziegeler wrote:
>
> Bertrand Delacretaz wrote
>> On Sun, Mar 13, 2016 at 10:41 AM, Carsten Ziegeler
>> wrote:
Bertrand Delacretaz wrote
> On Sun, Mar 13, 2016 at 10:41 AM, Carsten Ziegeler
> wrote:
>> ...The really annoying part is that we don't have tooling for this and
>> updating the snapshot dependencies for releases is a manual task...
>
> Doing a full build, removing the
On Sun, Mar 13, 2016 at 10:41 AM, Carsten Ziegeler wrote:
> ...The really annoying part is that we don't have tooling for this and
> updating the snapshot dependencies for releases is a manual task...
Doing a full build, removing the org.apache.sling.* folders from you
On Sun, 2016-03-13 at 09:47 +0100, Konrad Windszus wrote:
> Please vote to approve this release:
+1.
A minor note - since we have new features it would be nice IMO to bump
the version to 2.2.0 . But IMO it's not important enough to consider
restarting the vote.
Robert
signature.asc
+1
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
Konrad Windszus wrote
> Sorry, indeed I didn't read carefully enough.
> Still I would have expected, that in case the release is not yet available
> from Maven Central the dependency would be rolled back to the previous
> SNAPSHOT version (which would have been 2.1.5-SNAPSHOT), because that one
rad Windszus [mailto:konra...@gmx.de]
>> Sent: Saturday, March 12, 2016 8:40 PM
>> To: dev@sling.apache.org
>> Subject: Blocked release of maven-sling-plugin
>>
>> Hi,
>> I intend to release maven-sling-plugin 2.1.8
>> (https://issues.apache.org/jir
Hi,
We solved 2 issues in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12334142
The documentation at
http://sling.apache.org/documentation/development/sling.html has already been
updated accordingly.
Staging repository:
16 8:40 PM
>To: dev@sling.apache.org
>Subject: Blocked release of maven-sling-plugin
>
>Hi,
>I intend to release maven-sling-plugin 2.1.8
>(https://issues.apache.org/jira/browse/SLING/fixforversion/12334142).
>Unfortunately currently the POM contains a dependency towards a SNAPSHOT
&
Hi,
I intend to release maven-sling-plugin 2.1.8
(https://issues.apache.org/jira/browse/SLING/fixforversion/12334142).
Unfortunately currently the POM contains a dependency towards a SNAPSHOT
version of org.apache.sling.commons.json.
The according commit, which changed that version is
http
[
https://issues.apache.org/jira/browse/SLING-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-5335.
Resolution: Fixed
> maven-sling-plugin: Allow installing bundles through SlingPostServ
://svn.apache.org/r1732310].
> maven-sling-plugin: Allow installing bundles through SlingPostServlet
> mechanisms
>
>
> Key: SLING-5335
> URL: https://issues.apache.org/jira
://svn.apache.org/r1732304]. Now Maven 3 is required since the
parameter deploymentMethod is an enum type which is only supported since Maven
3 (https://issues.apache.org/jira/browse/MNG-4292).
> maven-sling-plugin: Allow installing bundles through SlingPostServlet
> mech
://github.com/apache/sling/pull/115
> maven-sling-plugin: Allow installing bundles through SlingPostServlet
> mechanisms
>
>
> Key: SLING-5335
> URL: https://issu
Github user asfgit closed the pull request at:
https://github.com/apache/sling/pull/115
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Hi Steven,
I will take care of the PR soon, looks good at first glance.
For improving the WebDAV support I have created
https://issues.apache.org/jira/browse/SLING-5559
Thanks for your comments,
Konrad
> On 25 Feb 2016, at 02:14, Steven Walters wrote:
>
> On Wed, Feb 24,
[
https://issues.apache.org/jira/browse/SLING-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus reassigned SLING-5335:
--
Assignee: Konrad Windszus
> maven-sling-plugin: Allow installing bundles thro
On Wed, Feb 24, 2016 at 4:27 PM, Carsten Ziegeler
wrote:
> Thanks for bringing up this old topic :)
>
> I'm fine with either solution. It seems that nowadays webdav is used and
> as Robert mentions it's more likely that the POST servlet is available.
> But we can go with
at 15:33 +0100, Konrad Windszus wrote:
>>> Hi,
>>> in the context of [0] the handling of usePut=true was extended to
>>> also create intermediate nodes through the Sling POST servlet.
>>> Currently the maven-sling-plugin behaves like this:
>>>
>&g
>> also create intermediate nodes through the Sling POST servlet.
>> Currently the maven-sling-plugin behaves like this:
>>
>> If you use usePut=true then you must point the targetUrl towards a
>> WebDAV implementation (which handles the PUT request). If the PUT
&g
Hi Konrad,
On Wed, 2016-02-24 at 15:33 +0100, Konrad Windszus wrote:
> Hi,
> in the context of [0] the handling of usePut=true was extended to
> also create intermediate nodes through the Sling POST servlet.
> Currently the maven-sling-plugin behaves like this:
>
> If y
Hi,
in the context of [0] the handling of usePut=true was extended to also create
intermediate nodes through the Sling POST servlet. Currently the
maven-sling-plugin behaves like this:
If you use usePut=true then you must point the targetUrl towards a WebDAV
implementation (which handles
/rfc4918.html#put-resources.
b) the Sling POST servlet which is used to create the intermediate paths
listening at {{sling.url}} as well. WebDAV cannot be used for that as that does
not standardize how a POST on resources should be implemented.
> maven-sling-plugin with usePut = true d
Steven Walters created SLING-5335:
-
Summary: maven-sling-plugin: Allow installing bundles through
SlingPostServlet mechanisms
Key: SLING-5335
URL: https://issues.apache.org/jira/browse/SLING-5335
GitHub user kemuri-9 opened a pull request:
https://github.com/apache/sling/pull/115
SLING-5335: maven-sling-plugin support for SlingPostServlet usage.
* Allow usage of SlingPostServlet for install and uninstall operations.
You can merge this pull request into a Git repository
://github.com/apache/sling/pull/115
SLING-5335: maven-sling-plugin support for SlingPostServlet usage.
* Allow usage of SlingPostServlet for install and uninstall operations.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kemuri-9/sling
one binding vote still missing...
stefan
>-Original Message-
>From: Stefan Seifert [mailto:sseif...@pro-vision.de]
>Sent: Monday, November 09, 2015 1:31 PM
>To: dev@sling.apache.org
>Subject: [VOTE] Release Apache Sling Commons Testing 2.0.22, Commons JSON
>2.0.16,
[
https://issues.apache.org/jira/browse/SLING-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli closed SLING-3121.
--
> Deployment of java bundles fails if the maven-sling-plugin is not declared in
> t
On Mon, 2015-11-09 at 12:31 +, Stefan Seifert wrote:
> Please vote to approve this release:
+1
Robert
signature.asc
Description: This is a digitally signed message part
[
https://issues.apache.org/jira/browse/SLING-5271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-5271.
-
> maven-sling-plugin: Update commons.json dependency for latest JSON Validator
> improv
[
https://issues.apache.org/jira/browse/SLING-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-5272.
-
> maven-sling-plugin: Potential resource leak in JAR file handl
Hi,
The vote has passed with the following result :
+1 (binding): Stefan Seifert, Stefan Egli, Robert Munteanu
I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.
stefan
Apache Sling Commons JSON 2.0.16 - 4 Issues (skipped one version due to
>canceled vote)
>https://issues.apache.org/jira/browse/SLING/fixforversion/12333769
>
>Apache Sling Maven Sling Plugin 2.1.6 - 2 Issues (skipped one version
>due to canceled vote)
>https://issues.apache.
/SLING/fixforversion/12333769
Apache Sling Maven Sling Plugin 2.1.6 - 2 Issues (skipped one version due to
canceled vote)
https://issues.apache.org/jira/browse/SLING/fixforversion/12334045
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1366/
You can use
+1
+1
Hi,
Apache Sling Commons Testing 2.0.20 - 4 Issues
https://issues.apache.org/jira/browse/SLING/fixforversion/12331987
Apache Sling Commons JSON 2.0.14 - 4 Issues
https://issues.apache.org/jira/browse/SLING/fixforversion/12333769
Apache Sling Maven Sling Plugin 2.1.4 - 2 Issues
https
ion/12331987
>
>Apache Sling Commons JSON 2.0.14 - 4 Issues
>https://issues.apache.org/jira/browse/SLING/fixforversion/12333769
>
>Apache Sling Maven Sling Plugin 2.1.4 - 2 Issues
>https://issues.apache.org/jira/browse/SLING/fixforversion/12334045
>
>Staging repository:
es
>https://issues.apache.org/jira/browse/SLING/fixforversion/12333769
>
>Apache Sling Maven Sling Plugin 2.1.4 - 2 Issues
>https://issues.apache.org/jira/browse/SLING/fixforversion/12334045
>
>Staging repository:
>https://repository.apache.org/content/repositories/orgapache
On Fri, 2015-11-06 at 13:50 +0100, Robert Munteanu wrote:
> Filed INFRA-10729 [3] asking for help finding out the root cause.
Infra fixed it, plugin is now available at
http://search.maven.org/#artifactdetails|org.apache.sling|maven-sling
-plugin|2.1.2|maven-plugin
Robert
] Release Apache Sling Commons Testing 2.0.20, Commons JSON
2.0.14, Maven Sling Plugin 2.1.4
Hi,
Apache Sling Commons Testing 2.0.20 - 4 Issues
https://issues.apache.org/jira/browse/SLING/fixforversion/12331987
Apache Sling Commons JSON 2.0.14 - 3 Issues
https://issues.apache.org/jira/browse/SLING
s
> > https://issues.apache.org/jira/browse/SLING/fixforversion/12331987
> >
> > Apache Sling Commons JSON 2.0.14 - 4 Issues
> > https://issues.apache.org/jira/browse/SLING/fixforversion/12333769
> >
> > Apache Sling Maven Sling Plugin 2.1.4 - 2 Issues
> >
forgot policy about not reusing version numbers - makes sense of course.
will do again...
stefan
LING/fixforversion/12333769
-1 SLING-5276
> Apache Sling Maven Sling Plugin 2.1.4 - 2 Issues
> https://issues.apache.org/jira/browse/SLING/fixforversion/12334045
-1 subsequent
O.
Stefan Seifert created SLING-5272:
-
Summary: maven-sling-plugin: Potential resource leak in JAR file
handling
Key: SLING-5272
URL: https://issues.apache.org/jira/browse/SLING-5272
Project: Sling
Hi,
On Fri, Nov 6, 2015 at 12:25 PM, Stefan Seifert <sseif...@pro-vision.de> wrote:
> in the svn logs a release of maven-sling-plugin 2.1.2 was done on oct 12th,
> 2015 [1]...
The vote thread is here AFAICS:
http://mail-archives.apache.org/mod_mbox/sling-dev/201510.mbox/%3c144466
[
https://issues.apache.org/jira/browse/SLING-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-5272.
---
Resolution: Fixed
Completed: At revision: 1712958
> maven-sling-plugin: Potent
Stefan Seifert created SLING-5271:
-
Summary: maven-sling-plugin: Update commons.json dependency for
latest JSON Validator improvements
Key: SLING-5271
URL: https://issues.apache.org/jira/browse/SLING-5271
in the svn logs a release of maven-sling-plugin 2.1.2 was done on oct 12th,
2015 [1].
what happened to this release?
it's not on maven central [2], i did not found a vote for it on the mailing
list, i did not found an unpublished staging repo on the apache nexus either.
should i start a re
On Fri, Nov 6, 2015 at 12:38 PM, Bertrand Delacretaz
wrote:
> I didn't find the VOTE RESULT message but that vote did get 3 PMC members +1s.
The result is at [1] , I guess it's easy to overlook since I used the
project named as defined in the pom.xml file.
> So maybe
is released.
> maven-sling-plugin: Update commons.json dependency for latest JSON Validator
> improvements
> -
>
> Key: SLING-5271
> URL: https://issues.apac
[
https://issues.apache.org/jira/browse/SLING-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-3540.
-
> maven-sling-plugin with usePut = true does not create intermediary fold
Hi,
Apache Sling Commons Testing 2.0.20 - 4 Issues
https://issues.apache.org/jira/browse/SLING/fixforversion/12331987
Apache Sling Commons JSON 2.0.14 - 3 Issues
https://issues.apache.org/jira/browse/SLING/fixforversion/12333769
Apache Sling Maven Sling Plugin 2.1.4 - 2 Issues
https
[
https://issues.apache.org/jira/browse/SLING-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-3540:
---
Summary: maven-sling-plugin with usePut = true does not create intermediary
folders
[
https://issues.apache.org/jira/browse/SLING-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-3540.
Resolution: Fixed
> maven-sling-plugin with usePut = true does not create intermedi
using -Dsling.deploy.intermediatePathPrimaryType.
> maven-sling-plugin with usePut = true does not create intermediary folders
> --
>
> Key: SLING-3540
> URL: https://issues.
[
https://issues.apache.org/jira/browse/SLING-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu reassigned SLING-3540:
--
Assignee: Robert Munteanu
> maven-sling-plugin with usePut = true does not cre
[
https://issues.apache.org/jira/browse/SLING-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-3540:
---
Fix Version/s: Maven Sling Plugin 2.1.2
> maven-sling-plugin with usePut = true d
Sling Plugin 2.1.0
> maven-sling-plugin with usePut = true does not create intermediary folders
> --
>
> Key: SLING-3540
> URL: https://issues.apache.org/jira/br
101 - 200 of 243 matches
Mail list logo