[
https://issues.apache.org/jira/browse/SLING-11532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus closed SLING-11532.
---
> Remove old relocation artifact maven-sling-plu
[
https://issues.apache.org/jira/browse/SLING-11532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus reassigned SLING-11532:
---
Assignee: Konrad Windszus
> Remove old relocation artifact maven-sling-plu
/07b629c761a1d7dcc1ee68a8a9c3c013bad5f3da.
> Remove old relocation artifact maven-sling-plugin
> -
>
> Key: SLING-11532
> URL: https://issues.apache.org/jira/browse/SLING-11532
> Project: Sling
>
is not a breaking change, but anyhow
the other changes included in the next release warrant a 3.0 release for me as
well :)
> Remove old relocation artifact maven-sling-plugin
> -
>
> Key: SLING-11532
>
propose to release the next version of sling-maven-plugin with version
3.0.0 to signal this breaking change.
> Remove old relocation artifact maven-sling-plugin
> -
>
> Key: SLING-11532
>
[
https://issues.apache.org/jira/browse/SLING-11532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-11532:
Issue Type: Improvement (was: Bug)
> Remove old relocation artifact maven-sling-plu
, do you have any concerns
with removing the old artifactId traces fully from the repo now?
> Remove old relocation artifact maven-sling-plugin
> -
>
> Key: SLING-11532
> URL: https://issues.apache.
-maven-plugin}} and the old artifactId {{maven-sling-plugin}} just
contains the relocation information.
According to
https://maven.apache.org/guides/mini/guide-relocation.html#releasing-the-next-version
it is not necessary to always release both the relocated and the old
artifactId together. Just
-maven-plugin}} and the old artifactId {{maven-sling-plugin}} just
contains the relocation information.
According to
https://maven.apache.org/guides/mini/guide-relocation.html#releasing-the-next-version
it is not necessary to always release both the relocated and the old
artifactId together. Just
Konrad Windszus created SLING-11532:
---
Summary: Remove old relocation artifact maven-sling-plugin
Key: SLING-11532
URL: https://issues.apache.org/jira/browse/SLING-11532
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-8212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-8212.
--
> Parent: Replace maven-sling-plugin with sling-maven-plugin and ban old
> artif
/apache/sling-maven-plugin
> Rename maven-sling-plugin to sling-maven-plugin
> ---
>
> Key: SLING-8204
> URL: https://issues.apache.org/jira/browse/SLING-8204
> Project: Sling
> Is
>To: dev@sling.apache.org
>Subject: Re: rename sling-maven-sling-plugin git repo?
>
>Hi Stefan,
>
>On Mon, 2019-01-14 at 19:53 +, Stefan Seifert wrote:
>> unfortunately it's not possible to create a new gitbox repo named
>> "sling-sling-maven-plugin" becaus
Hi Stefan,
On Mon, 2019-01-14 at 19:53 +, Stefan Seifert wrote:
> unfortunately it's not possible to create a new gitbox repo named
> "sling-sling-maven-plugin" because the form validation thinks the
> double prefix was not intended.
Initially we only added the 'sling-' prefix if it was
This should be possible via INFRA. Compare e.g. with
https://issues.apache.org/jira/browse/INFRA-16017?filter=-4=project%20%3D%20INFRA%20AND%20text%20~%20%22rename%20git%22%20order%20by%20created%20DESC
> Am 14.01.2019 um 20:53 schrieb Stefan Seifert :
>
> should we rename the github repo as
should we rename the github repo as well to "sling-sling-maven-plugin"?
it would
a) be more consistent and
b) fix auto-generated github links like on the download page [1] which is
currently broken
i'm not sure if renaming a github & gitbox is possible (at least there is no
self-service tool
[
https://issues.apache.org/jira/browse/SLING-8212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert updated SLING-8212:
--
Fix Version/s: Bundle Parent 35
> Parent: Replace maven-sling-plugin with sling-maven-plu
/aa670cb74f9093da351e08942a50fdaca63fb0c2
> Parent: Replace maven-sling-plugin with sling-maven-plugin and ban old
> artifact id
> --
>
> Key: SLING-8212
> URL: https://issues.apache.org/jira
Stefan Seifert created SLING-8212:
-
Summary: Parent: Replace maven-sling-plugin with
sling-maven-plugin and ban old artifact id
Key: SLING-8212
URL: https://issues.apache.org/jira/browse/SLING-8212
[
https://issues.apache.org/jira/browse/SLING-8204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-8204.
-
> Rename maven-sling-plugin to sling-maven-plu
://lists.apache.org/thread.html/d188debfc90ca4c9b6198d04f1b4db6aff68743d6cf51017d0caf613@%3Cdev.sling.apache.org%3E
> Rename maven-sling-plugin to sling-maven-plugin
> ---
>
> Key: SLING-8204
> URL: https://issues.apache.
[
https://issues.apache.org/jira/browse/SLING-8204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-8204.
---
Resolution: Fixed
https://github.com/apache/sling-maven-sling-plugin/commit
+1
--
Jason
On Mon, Jan 7, 2019, at 12:20 PM, Stefan Seifert wrote:
> i've created [1] to make or maven sling plugin name finally conformant
> with the "latest" maven conventions (which are in place for many years
> already).
> to still support the old artifact name i pro
i've created [1] to make or maven sling plugin name finally conformant with the
"latest" maven conventions (which are in place for many years already).
to still support the old artifact name i propose to add a relocate pom using
the old coordinates, which eases the migration.
if no
://github.com/apache/sling-maven-sling-plugin/pull/2
> Rename maven-sling-plugin to sling-maven-plugin
> ---
>
> Key: SLING-8204
> URL: https://issues.apache.org/jira/browse/SLING-8204
>
/thread.html/f058f8e2756cb0855121b21a3f7f6195dae426213d9f57ba4080ffa6@%3Cdev.sling.apache.org%3E
and i'm picking up the proposal [~olli] here, which worked quite well for the
relocation of osgi-mock and sling-mock already.
> Rename maven-sling-plugin to sling-maven-plu
(or in the context of a JIRA
issue) about this and the outcome was not to do it. I don’t remember the
details though.
> Rename maven-sling-plugin to sling-maven-plugin
> ---
>
> Key: SLING-8204
> URL: https://is
Stefan Seifert created SLING-8204:
-
Summary: Rename maven-sling-plugin to sling-maven-plugin
Key: SLING-8204
URL: https://issues.apache.org/jira/browse/SLING-8204
Project: Sling
Issue Type
Hi,
The vote has passed with the following result :
+1 (binding): Robert Munteanu, Carsten Ziegeler, Stefan Seifert, Radu
Cotescu
I will copy this release to the Sling dist directory and promote the
artifacts to the central Maven repository.
Thanks for voting,
Robert
+1
> On 14 Aug 2018, at 18:18, Robert Munteanu wrote:
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] 0 Don't care
> [ ] -1 Don't release, because ...
>
> This majority vote is open for at least 72 hours.
>
> Thanks,
>
> Robert
+1
+1
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
On Tue, 2018-08-14 at 18:18 +0200, Robert Munteanu 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-7645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-7645.
-
> Maven Sling Plugin: Update to latest fsresou
[
https://issues.apache.org/jira/browse/SLING-7644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-7644.
-
> Maven-Sling-Plugin requires Java 8
> --
>
>
Hi,
The vote has passed with the following result :
+1 (binding): Carsten Ziegeler, Stefan Seifert, Radu Cotescu
I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.
stefan
+1
> On 4 May 2018, at 10:05, Stefan Seifert wrote:
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] 0 Don't care
> [ ] -1 Don't release, because ...
>
> This majority vote is open for at least 72 hours.
>
> stefan
+1
Hi,
Apache Sling Context-Aware Configuration Impl 1.4.12 (1 issue)
https://issues.apache.org/jira/browse/SLING/fixforversion/12342552
Apache Maven Sling Plugin 2.3.6 (2 issues)
https://issues.apache.org/jira/browse/SLING/fixforversion/12341759
There are still some outstanding issues:
https
+1
Stefan Seifert wrote
> Hi,
>
> Apache Sling Context-Aware Configuration Impl 1.4.12 (1 issue)
> https://issues.apache.org/jira/browse/SLING/fixforversion/12342552
>
> Apache Maven Sling Plugin 2.3.6 (2 issues)
> https://issues.apache.org/jira/browse/SLING/f
[
https://issues.apache.org/jira/browse/SLING-7645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-7645.
---
Resolution: Fixed
fixed:
https://github.com/apache/sling-maven-sling-plugin/commit
[
https://issues.apache.org/jira/browse/SLING-7644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-7644.
---
Resolution: Fixed
fixed:
https://github.com/apache/sling-maven-sling-plugin/commit
Stefan Seifert created SLING-7645:
-
Summary: Maven Sling Plugin: Update to latest fsresource
Key: SLING-7645
URL: https://issues.apache.org/jira/browse/SLING-7645
Project: Sling
Issue Type
.
> Maven-Sling-Plugin requires Java 8
> --
>
> Key: SLING-7644
> URL: https://issues.apache.org/jira/browse/SLING-7644
> Project: Sling
> Issue Type: Bug
> Components: Mave
impossible to build our
java 7 based modules with Java 7.
So we have two options, either move back to 2.3.2 for our parent pom and
declare that the maven sling plugin requires Java 8
or
fix this Java 8 dependency in 2.3.6 and change our parent pom to 2.3.6
But the way it is atm does not make
/sling-maven-sling-plugin/commit/9579510a3c3efde58319fc25749836c18c4e9644
which references
http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-json_1.1_spec/1.0/geronimo-json_1.1_spec-1.0.pom
http://repo1.maven.org/maven2/org/apache/geronimo/genesis/genesis-java8-flava/2.3/genesis-java8
Hi,
for some time I noticed a problem with our latest parent pom when using
Java 7 to build some modules. It seems that the latest version of the
Sling Plugin requires Java 8 although it does not declare this.
As we're still supporting and using Java 7 in many modules as the base,
we should fix
Carsten Ziegeler created SLING-7644:
---
Summary: Maven-Sling-Plugin requires Java 8
Key: SLING-7644
URL: https://issues.apache.org/jira/browse/SLING-7644
Project: Sling
Issue Type: Bug
On Fri, 2017-10-06 at 11:16 +0200, Karl Pauls wrote:
> On Fri, Oct 6, 2017 at 10:43 AM, Stefan Seifert de> wrote:
> > yes, in think this would be helpful.
> > could be configurable, but by default it should be switched on.
> > if deployment was not succesfull the "install"
s on the setup of your filevault xml project if this ist he
>> case - and often it's not.
>>
>> but if you have a build/resources/resource declaration in your project that
>> copies everything to target/classes (which is not required, but is seen
>> often in proj
have an optional configuration property in the
> maven-sling-plugin to support this use case.
>
> stefan
>
>>-Original Message-
>>From: Julian Sedding [mailto:jsedd...@gmail.com]
>>Sent: Thursday, December 14, 2017 9:35 AM
>>To: Sling Developers List
>>Subject
project that
copies everything to target/classes (which is not required, but is seen often
in project setups), then it should work.
yes, it would make sense to have an optional configuration property in the
maven-sling-plugin to support this use case.
stefan
>-Original Message-
>From:
gt; stefan
>
>
>>-Original Message-
>>From: Julian Sedding [mailto:jsedd...@gmail.com]
>>Sent: Wednesday, December 13, 2017 2:32 PM
>>To: Sling Developers List
>>Subject: Re: Maven Sling Plugin - fsmount
>>
>>Hi Stefan
>>
>>Thanks
fsresource implementation; i'm not
sure if it makes sense to integrate this special usecase also in the logic of
the sling:fsmount goal.
stefan
>-Original Message-
>From: Julian Sedding [mailto:jsedd...@gmail.com]
>Sent: Wednesday, December 13, 2017 2:32 PM
>To: Sling Develo
iled code via .gitignore. is this an option
> for you as well?
>
> stefan
>
>>-Original Message-
>>From: Julian Sedding [mailto:jsedd...@apache.org]
>>Sent: Wednesday, December 13, 2017 11:47 AM
>>To: Sling Developers List
>>Subject: Maven Sling Plu
containing compiled code via .gitignore. is this an option
for you as well?
stefan
>-Original Message-
>From: Julian Sedding [mailto:jsedd...@apache.org]
>Sent: Wednesday, December 13, 2017 11:47 AM
>To: Sling Developers List
>Subject: Maven Sling Plugin - fsmount
>
&g
Hi all and Stefan in particular
I am in the process of setting up a maven build for a joint frontend
(HTML, CSS, JS) and backend team (Sling / AEM).
The goals for the frontend team workflow are:
- use Node.js based tooling / frontend build (integrated using
frontend-maven-plugin - works)
-
[
https://issues.apache.org/jira/browse/SLING-7181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-7181.
-
> Maven Sling Plugin: Add Incremental Build Support for Validation M
Hi,
The vote has passed with the following result :
+1 (binding): Stefan Seifert, Robert Munteanu, Karl Pauls
I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.
stefan
day, October 16, 2017 9:00 AM
>>To: dev@sling.apache.org
>>Subject: RE: [VOTE] Release Apache Sling Maven Sling Plugin 2.3.4
>>
>>one (binding) vote is missing...
>>
>>stefan
>>
>>
>
>
--
Karl Pauls
karlpa...@gmail.com
one (binding) vote is missing... anyone?
stefan
>-Original Message-
>From: Stefan Seifert [mailto:sseif...@pro-vision.de]
>Sent: Monday, October 16, 2017 9:00 AM
>To: dev@sling.apache.org
>Subject: RE: [VOTE] Release Apache Sling Maven Sling Plugin 2.3.4
>
>one (bin
one (binding) vote is missing...
stefan
On Wed, 2017-10-11 at 19:23 +, Stefan Seifert wrote:
> Please vote to approve this release:
+1
Robert
signature.asc
Description: This is a digitally signed message part
+1
Hi,
We solved 1 issues in this release:
https://issues.apache.org/jira/projects/SLING/versions/12341647
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1801/
You can use this UNIX script to download the release and verify the signatures:
[
https://issues.apache.org/jira/browse/SLING-7181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-7181.
---
Resolution: Fixed
Completed: At revision: 1811313
> Maven Sling Plugin: Add Incremen
Stefan Seifert created SLING-7181:
-
Summary: Maven Sling Plugin: Add Incremental Build Support for
Validation Mojo
Key: SLING-7181
URL: https://issues.apache.org/jira/browse/SLING-7181
Project: Sling
error
Yes please!
regards,
Karl
> stefan
>
>>-Original Message-
>>From: Robert Munteanu [mailto:romb...@apache.org]
>>Sent: Friday, October 6, 2017 10:35 AM
>>To: dev@sling.apache.org
>>Subject: Should the maven-sling-plugin check if the bundle deploym
: Friday, October 6, 2017 10:35 AM
>To: dev@sling.apache.org
>Subject: Should the maven-sling-plugin check if the bundle deployment was
>successful?
>
>Hi,
>
>I was just wondering whether deploying a bundle with the Maven plugin
>should also check if the bundle could be star
Hi,
I was just wondering whether deploying a bundle with the Maven plugin
should also check if the bundle could be started. It would definitely
be helpful.
We technically have access to the bundle name and version from the jar
file and can use the the OSGi console REST APIs to poll for the
Hi,
The vote has passed with the following result :
+1 (binding): Stefan Seifert, Robert Munteanu, Daniel Klco, Radu Cotescu
I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.
stefan
+1
On Wed, 20 Sep 2017 at 12:59 Stefan Seifert wrote:
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] 0 Don't care
> [ ] -1 Don't release, because ...
>
> This majority vote is open for at least 72 hours.
>
> stefan
>
>
+1
On Wed, Sep 20, 2017 at 8:57 AM, Robert Munteanu wrote:
> On Wed, 2017-09-20 at 10:59 +, Stefan Seifert wrote:
> > Please vote to approve this release:
>
> +1
>
> Robert
On Wed, 2017-09-20 at 10:59 +, 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-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-2480.
--
> Add config for maven-sling-plugin to m2e configurat
+1
Hi,
We solved 1 issues in this release:
https://issues.apache.org/jira/projects/SLING/versions/12340658
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1788/
You can use this UNIX script to download the release and verify the signatures:
[
https://issues.apache.org/jira/browse/SLING-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-6917.
-
> Maven Sling Plugin: Deploy fsresource bundles on fsmount goal if requi
[
https://issues.apache.org/jira/browse/SLING-6920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-6920.
-
> Maven Sling Plugin: Optional activate json tick parse support for validate
>
Hi,
The vote has passed with the following result :
+1 (binding): Stefan Seifert, Carsten Ziegeler, Robert Munteanu, Karl Pauls
I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.
stefan
+1
regards,
Karl
On Tue, May 30, 2017 at 12:35 PM, Robert Munteanu wrote:
> On Tue, 2017-05-30 at 08:58 +, Stefan Seifert wrote:
>> Please vote to approve this release:
>
> +1
>
> Robert
--
Karl Pauls
karlpa...@gmail.com
On Tue, 2017-05-30 at 08:58 +, 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
)
https://issues.apache.org/jira/browse/SLING/fixforversion/12340621
Apache Sling File System Resource Provider 1.4.4 (1 issue)
https://issues.apache.org/jira/browse/SLING/fixforversion/12340622
Apache Sling Maven Sling Plugin 2.3.0 (2 issues)
https://issues.apache.org/jira/browse/SLING
[
https://issues.apache.org/jira/browse/SLING-6920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-6920.
---
Resolution: Fixed
Completed: At revision: 1796677
> Maven Sling Plugin: Optional activ
Stefan Seifert created SLING-6920:
-
Summary: Maven Sling Plugin: Optional activate json tick parse
support for validate goal
Key: SLING-6920
URL: https://issues.apache.org/jira/browse/SLING-6920
[
https://issues.apache.org/jira/browse/SLING-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-6917.
---
Resolution: Fixed
Completed: At revision: 1796657
> Maven Sling Plugin: Deploy fsresou
Stefan Seifert created SLING-6917:
-
Summary: Maven Sling Plugin: Deploy fsresource bundles on fsmount
goal if required
Key: SLING-6917
URL: https://issues.apache.org/jira/browse/SLING-6917
Project
[
https://issues.apache.org/jira/browse/SLING-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-6875.
-
> maven-sling-plugin: Support tick as well as double quote when validating JSON
>
Hi,
The vote has passed with the following result :
+1 (binding): Stefan Seifert, Carsten Ziegeler, Karl Pauls
I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.
stefan
+1
regards,
Karl
On Wed, May 24, 2017 at 11:50 AM, Carsten Ziegeler wrote:
> +1
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
--
Karl Pauls
karlpa...@gmail.com
+1
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
+1
Provider 1.4.2 (3 issues)
https://issues.apache.org/jira/browse/SLING/fixforversion/12340511
Apache Sling Maven Sling Plugin 2.2.2 (1 issue)
https://issues.apache.org/jira/browse/SLING/fixforversion/12340254
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling
[
https://issues.apache.org/jira/browse/SLING-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-6875.
---
Resolution: Fixed
Completed: At revision: 1795976
> maven-sling-plugin: Support t
Stefan Seifert created SLING-6875:
-
Summary: maven-sling-plugin: Support tick as well as double quote
when validating JSON files
Key: SLING-6875
URL: https://issues.apache.org/jira/browse/SLING-6875
[
https://issues.apache.org/jira/browse/SLING-6622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-6622.
-
> maven-sling-plugin: Add "fsmount" and &quo
[
https://issues.apache.org/jira/browse/SLING-6619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-6619.
-
> maven-sling-plugin: Switch to javax.json + John
[
https://issues.apache.org/jira/browse/SLING-6630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-6630.
-
> maven-sling-plugin: Support Mount FileVault XML for File System Resource
> Pr
1 - 100 of 243 matches
Mail list logo