[
https://issues.apache.org/jira/browse/SLING-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer updated SLING-8640:
Fix Version/s: (was: Sling Pax Exam Utilities 1.0.6)
[
https://issues.apache.org/jira/browse/SLING-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908693#comment-16908693
]
Andreas Schaefer commented on SLING-8640:
-
Created a PR for this:
schaefa opened a new pull request #35: Created a Feature Launcher Mojo
(launch-features)
URL: https://github.com/apache/sling-slingfeature-maven-plugin/pull/35
The Feature Launcher Mojo accepts all the current parameter of the Feature
Launcher even though the documentary of the parameters
Andreas Schaefer created SLING-8640:
---
Summary: Add a Feature Launcher Mojo to Sling Feature Maven Plugin
Key: SLING-8640
URL: https://issues.apache.org/jira/browse/SLING-8640
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer reassigned SLING-8640:
---
Assignee: Andreas Schaefer
> Add a Feature Launcher Mojo to Sling Feature Maven
Could it be that the issue is with the ‘cloud launcher’ as the ‘jcrinstall’
works.
Here is a test project that will showcase the issue:
https://github.com/schaefa/cpconverter-ssue-fm-starter/tree/issue/cp-not-launching
Hi
When I convert and Launch the Peregrine CMS then I see that all converted
Content Packages remain in ‘Untransformed Resources’ state when I look at the
/system/console/osgi-installer page.
Is there a way to figure out why they remain in that state?
I set the launcher to verbose but I do
Timothee Maret created SLING-8639:
-
Summary: VltUtils does not escape path in when creating filter
patterns
Key: SLING-8639
URL: https://issues.apache.org/jira/browse/SLING-8639
Project: Sling
+1
Hi,
Context-Aware Configuration API 1.2.0 (2 issues)
https://issues.apache.org/jira/browse/SLING/fixforversion/12344000
Context-Aware Configuration Impl 1.5.0 (3 issues)
https://issues.apache.org/jira/browse/SLING/fixforversion/12345451
Staging repository:
[
https://issues.apache.org/jira/browse/SLING-8638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-8638.
---
Resolution: Fixed
[
https://issues.apache.org/jira/browse/SLING-8272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert updated SLING-8272:
--
Issue Type: New Feature (was: Improvement)
> ConfigurationBuilder: Add method to check for
[
https://issues.apache.org/jira/browse/SLING-7954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert updated SLING-7954:
--
Fix Version/s: (was: Context-Aware Configuration Impl 1.4.18)
Description:
The
Stefan Seifert created SLING-8638:
-
Summary: caconfig-impl: Switch from legacy commons collections 3
to commons collections 4
Key: SLING-8638
URL: https://issues.apache.org/jira/browse/SLING-8638
[
https://issues.apache.org/jira/browse/SLING-8630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908363#comment-16908363
]
Andreas Schaefer commented on SLING-8630:
-
Created PR for the change in the CP Converter:
[
https://issues.apache.org/jira/browse/SLING-8637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-8637.
---
Resolution: Fixed
Stefan Seifert created SLING-8637:
-
Summary: caconfig-impl: Lower loglevel vor warning in
DefaultConfigurationResourceResolvingStrategy
Key: SLING-8637
URL: https://issues.apache.org/jira/browse/SLING-8637
Hi Robert
I merged the branch into master and so it should show there.
I will do some more testing today but as soon as the git repo is created I will
move the code over.
Thanks - Andy
> On Aug 15, 2019, at 2:25 AM, Robert Munteanu wrote:
>
> Hi Andy,
>
> On Wed, 2019-08-14 at 18:47 -0700,
[
https://issues.apache.org/jira/browse/SLING-8636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bosschaert resolved SLING-8636.
-
Resolution: Fixed
#1 merged.
> Set webconsole.security.provider.id property on the
[
https://issues.apache.org/jira/browse/SLING-8636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bosschaert updated SLING-8636:
Fix Version/s: Web Console Security Provider 1.2.4
> Set webconsole.security.provider.id
schaefa merged pull request #48: Feature/sling feature converter maven plugin
URL: https://github.com/apache/sling-whiteboard/pull/48
This is an automated message from the Apache Git Service.
To respond to the message,
+1 (non-binding)
- Andy
> On Aug 15, 2019, at 5:29 AM, Karl Pauls wrote:
>
> I would like to call a vote on the following releases:
>
> Apache Sling Feature Modelconverter 1.0.8
>
> We solved 1 issue in this release:
>
> https://issues.apache.org/jira/projects/SLING/versions/12345975
>
>
[
https://issues.apache.org/jira/browse/SLING-8636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bosschaert reassigned SLING-8636:
---
Assignee: David Bosschaert
> Set webconsole.security.provider.id property on the
David Bosschaert created SLING-8636:
---
Summary: Set webconsole.security.provider.id property on the Sling
Web Console Security Provider
Key: SLING-8636
URL: https://issues.apache.org/jira/browse/SLING-8636
]
[INFO] [jenkins-event-spy] Generated
/home/jenkins/jenkins-slave/workspace/e-sling-launchpad-testing_master@tmp/withMaven1a7bdcc2/maven-spy-20190815-145241-90815768641578105131927.log
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven
Please see
https://builds.apache.org/job/Sling/job/sling-org-apache-sling-launchpad-testing/job/master/273/
for details.
No further emails will be sent until the status of the build is changed.
+1
David
On Thu, 15 Aug 2019 at 13:29, Karl Pauls wrote:
> I would like to call a vote on the following releases:
>
> Apache Sling Feature Modelconverter 1.0.8
>
> We solved 1 issue in this release:
>
> https://issues.apache.org/jira/projects/SLING/versions/12345975
>
> Apache Sling SlingStart
On Thu, Aug 15, 2019 at 11:38 AM Carsten Ziegeler wrote:
>
> Am 15.08.2019 um 11:21 schrieb Robert Munteanu:
> > On Thu, 2019-08-15 at 11:12 +0200, Carsten Ziegeler wrote:
> >> Hi Roy,
> >>
> >> I guess my mail is a little bit misleading :)
> >>
> >> It's totally fine to use SLF4J directly and we
[
https://issues.apache.org/jira/browse/SLING-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-8635.
-
Resolution: Fixed
Added in rev 24e8b04
> Close resource resolver at the end of each
Carsten Ziegeler created SLING-8635:
---
Summary: Close resource resolver at the end of each request
Key: SLING-8635
URL: https://issues.apache.org/jira/browse/SLING-8635
Project: Sling
Issue
+1 (only checked signatures)
> On 15 Aug 2019, at 14:29, Karl Pauls wrote:
>
> Please vote to approve these release:
>
> [ ] +1 Approve the releases
> [ ] 0 Don't care
> [ ] -1 Don't release, because ...
+1
Carsten
Am 15.08.2019 um 14:29 schrieb Karl Pauls:
I would like to call a vote on the following releases:
Apache Sling Feature Modelconverter 1.0.8
We solved 1 issue in this release:
https://issues.apache.org/jira/projects/SLING/versions/12345975
Apache Sling SlingStart Maven Plugin
I would like to call a vote on the following releases:
Apache Sling Feature Modelconverter 1.0.8
We solved 1 issue in this release:
https://issues.apache.org/jira/projects/SLING/versions/12345975
Apache Sling SlingStart Maven Plugin 1.8.8
We solved 1 issue in this release:
[
https://issues.apache.org/jira/browse/SLING-8634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls resolved SLING-8634.
---
Resolution: Fixed
> Update Sling Start Maven Plugin to latest Feature Model Converter
>
Karl Pauls created SLING-8634:
-
Summary: Update Sling Start Maven Plugin to latest Feature Model
Converter
Key: SLING-8634
URL: https://issues.apache.org/jira/browse/SLING-8634
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-8633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls resolved SLING-8633.
---
Resolution: Fixed
> Use start-order instead of start-level
> --
karlpauls merged pull request #4: SLING-8633: Use start-order instead of
start-level
URL:
https://github.com/apache/sling-org-apache-sling-feature-modelconverter/pull/4
This is an automated message from the Apache Git
bosschaert commented on issue #4: SLING-8633: Use start-order instead of
start-level
URL:
https://github.com/apache/sling-org-apache-sling-feature-modelconverter/pull/4#issuecomment-521588806
LGTM
This is an automated
karlpauls opened a new pull request #4: SLING-8633: Use start-order instead of
start-level
URL:
https://github.com/apache/sling-org-apache-sling-feature-modelconverter/pull/4
This is an automated message from the Apache
[
https://issues.apache.org/jira/browse/SLING-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-8632.
-
Resolution: Fixed
Added new methods to get/set a JSON structure from an extension and
[
https://issues.apache.org/jira/browse/SLING-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-8632:
Component/s: (was: Feature Flags)
Feature Model
> Add a method to get
[
https://issues.apache.org/jira/browse/SLING-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-8632:
Fix Version/s: Feature Model IO 1.1.0
> Add a method to get a JSON object from an
Am 15.08.2019 um 11:21 schrieb Robert Munteanu:
On Thu, 2019-08-15 at 11:12 +0200, Carsten Ziegeler wrote:
Hi Roy,
I guess my mail is a little bit misleading :)
It's totally fine to use SLF4J directly and we should keep doing
this.
Under the covers, everything you log to slf4j is routed
Hi Andy,
On Wed, 2019-08-14 at 18:47 -0700, Andreas Schaefer wrote:
> Hi
>
> I am aware that this is a long shot but this Maven Plugin can make
> life easier for User that want to convert Sling into a Feature as
> well as launching Sling FM with their Content Packages.
If you think this is
On Thu, 2019-08-15 at 00:10 +0200, Georg Henzler wrote:
> > Replying to myself here - the /content/startup/index.html file is
> > different from the /content/starter/index.html one, so no change is
> > required here.
>
> Sorry for the late reply - so fixed perfectly via SLING-8615. The
> file
>
Karl Pauls created SLING-8633:
-
Summary: Use start-order instead of start-level
Key: SLING-8633
URL: https://issues.apache.org/jira/browse/SLING-8633
Project: Sling
Issue Type: Bug
On Thu, 2019-08-15 at 11:12 +0200, Carsten Ziegeler wrote:
> Hi Roy,
>
> I guess my mail is a little bit misleading :)
>
> It's totally fine to use SLF4J directly and we should keep doing
> this.
> Under the covers, everything you log to slf4j is routed through the
> LogService so other
Hi Roy,
I guess my mail is a little bit misleading :)
It's totally fine to use SLF4J directly and we should keep doing this.
Under the covers, everything you log to slf4j is routed through the
LogService so other components in the system can listen to log entries etc.
So this is about
[
https://issues.apache.org/jira/browse/SLING-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-8631.
-
Resolution: Fixed
Added the new state, deprecated old methods and adjusted reader/writer
Hey Carsten,
What is the benefit of using this log service instead of just keep using SLF4J
which seems to have almost the exact same interface / way of using?
Greets,
Roy
> On 14 Aug 2019, at 08:17, Carsten Ziegeler wrote:
>
> Hi,
>
> the OSGi R7 specification has an update to the Log
[
https://issues.apache.org/jira/browse/SLING-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-8631:
Fix Version/s: Feature Model IO 1.0.8
> Introduce state for extensions
>
51 matches
Mail list logo
