+1
i also think we can omit D) for the first step.
i'm also fine with C) that it always include sample data - we can always add a
switch later to remove it.
for B) we might consider putting all bundle projects below a bundles/ folder
and all content package projects below a /content-packages
With respect to C:
The Sling Project Archetype has two versions of each module in it:
- plain (no code)
- sample code
The archetype can do the following:
- merge samples into module aka having only one module
- delete samples
- keep them separate. Only the plain code module is active in the
On Thu, 2019-09-12 at 16:03 +, Apache Jenkins Server wrote:
> Scripts not permitted to use new java.lang.RuntimeException
> java.lang.String. Administrators can decide whether to approve or
> reject this signature.
This cryptic failure should be fixed with
[
https://issues.apache.org/jira/browse/SLING-8704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928690#comment-16928690
]
Konrad Windszus edited comment on SLING-8704 at 9/12/19 4:07 PM:
-
I
> On 5. Sep 2019, at 16:28, Stefan Seifert wrote:
>
> - Challenge: Building non-committer PRs with Jenkins is no longer allowed
> - problem described in SLING-7245 - Validate pull requests using Jenkins
> Resolved
>- reason are security issues, see also INFRA-18973
>- we assume it
[
https://issues.apache.org/jira/browse/SLING-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu reassigned SLING-8694:
---
Assignee: Radu Cotescu
> Allow selectively downloading artifacts from a staged Nexus
[
https://issues.apache.org/jira/browse/SLING-8704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928690#comment-16928690
]
Konrad Windszus commented on SLING-8704:
I opened https://app.codeship.com/apache-sling for PoC
[
https://issues.apache.org/jira/browse/SLING-8704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-8704:
---
Description:
As outlined in
-slave/workspace/e-sling-launchpad-testing_master@tmp/withMaven7b421c6f/maven-spy-20190912-155816-5704242202946773223082.log
[Pipeline] }
[withMaven] Publishers: Pipeline Graph Publisher: 27 ms, JGiven Publisher: 1 ms
[Pipeline] // withMaven
[Pipeline] }
[Pipeline] // stage
Scripts not permitted to use
[
https://issues.apache.org/jira/browse/SLING-7245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928687#comment-16928687
]
Konrad Windszus commented on SLING-7245:
The broken PR build is now tracked in SLING-8704.
>
Konrad Windszus created SLING-8704:
--
Summary: Build PRs from non-committers
Key: SLING-8704
URL: https://issues.apache.org/jira/browse/SLING-8704
Project: Sling
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/SLING-6756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-6756.
Resolution: Not A Problem
Verified that there are no more jvm.config files in Sling repos,
Definitely +1 on having only one archetype. In case D is too much effort, we
could even leave it out.
A maintained archetype is better than what we currently have.
And it should be pretty easy for every developer to just copy over from a
blueprint project created from the archetype only the
On Thu, 2019-09-05 at 14:28 +, Stefan Seifert wrote:
> - Challenge: Building non-committer PRs with Jenkins is no longer
> allowed
> - problem described in SLING-7245 - Validate pull requests using
> Jenkins Resolved
> - reason are security issues, see also INFRA-18973
> - we assume
[
https://issues.apache.org/jira/browse/SLING-6756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928677#comment-16928677
]
Konrad Windszus commented on SLING-6756:
I think we no longer have any .mvn folder in any of our
Robert Munteanu created SLING-8703:
--
Summary: Run Sling Starter ITs for modules part of the Sling
Starter
Key: SLING-8703
URL: https://issues.apache.org/jira/browse/SLING-8703
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-2760.
Resolution: Won't Fix
Project is in the attic, resolving WONTFIX
>
[
https://issues.apache.org/jira/browse/SLING-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-2760.
--
> org.apache.sling.auth.openid bundle has dependencies not available on Maven
> central
>
[
https://issues.apache.org/jira/browse/SLING-6756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928670#comment-16928670
]
Robert Munteanu commented on SLING-6756:
[~kwin] - I think this is no longer applicable, right?
[
https://issues.apache.org/jira/browse/SLING-8702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-8702:
---
Summary: Investigate automatically onboarding Sling projects to SonarCloud
(was:
Robert Munteanu created SLING-8702:
--
Summary: Investigate automatically onoboarding Sling projects to
SonarCloud
Key: SLING-8702
URL: https://issues.apache.org/jira/browse/SLING-8702
Project: Sling
Robert Munteanu created SLING-8701:
--
Summary: Investigate custom set of SonarCloud rules
Key: SLING-8701
URL: https://issues.apache.org/jira/browse/SLING-8701
Project: Sling
Issue Type:
Please see
https://builds.apache.org/job/Sling/job/sling-org-apache-sling-launchpad-testing/job/master/309/
for details.
No further emails will be sent until the status of the build is changed.
Reminder, if there's something that you feel is significant to Sling. Add it to
the website news.
Currently the last news item on our front page is from last year.
- Jason
On Thu, 2019-09-05 at 14:43 +, Stefan Seifert wrote:
> - currently there are lots of sling maven archetypes, and most of
> them not well maintained
> - we would favor to have only one single "project" archetypes,
> probably the new "project" archetype contributed by andy
> - add parameters to
On Mon, 2019-09-09 at 09:04 -0700, Andreas Schaefer wrote:
> Hi
>
> I am not sure about this but my question was the other way around.
>
> Do we want in the future that Content Package are writing in a
> Feature Model way (Content ZIP file separate from Bundles connected
> though a FM
[
https://issues.apache.org/jira/browse/SLING-8700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928546#comment-16928546
]
Robert Munteanu edited comment on SLING-8700 at 9/12/19 1:52 PM:
-
This
[
https://issues.apache.org/jira/browse/SLING-8700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928546#comment-16928546
]
Robert Munteanu edited comment on SLING-8700 at 9/12/19 1:52 PM:
-
This
[
https://issues.apache.org/jira/browse/SLING-8700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928546#comment-16928546
]
Robert Munteanu commented on SLING-8700:
This I've tried and did not work:
- disabling the Maven
[
https://issues.apache.org/jira/browse/SLING-8700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-8700:
---
Attachment: compiler-errors-screenshot.png
> Unexpected compiler errors in Eclipse during
+1
David
On Wed, 11 Sep 2019 at 12:52, Oliver Lietz wrote:
> Hi,
>
> We solved 1 issue in this release:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12344864
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-2128
>
> You can use this
rombert commented on issue #9: SLING-3629 - Provide an XML formatter for
content.xml files
URL: https://github.com/apache/sling-ide-tooling/pull/9#issuecomment-530806403
One of the builds failed because someone/something interrupted the build
```
[INFO] Running
rombert merged pull request #9: SLING-3629 - Provide an XML formatter for
content.xml files
URL: https://github.com/apache/sling-ide-tooling/pull/9
This is an automated message from the Apache Git Service.
To respond to the
+1 great summary.
On Tue, Sep 10, 2019 at 12:37 PM Stefan Seifert
wrote:
> i try to write a first summary:
>
> - we have good use cases for a rewriter in general, but are unhappy with
> the current implementation and it's way of configuration. the whole thing
> is a bit "alien" to the other
@Stefan: thanks for the summary. +1 IMHO that captures the main points
of the discussion well.
Regards
Julian
On Tue, Sep 10, 2019 at 6:37 PM Stefan Seifert wrote:
>
> i try to write a first summary:
>
> - we have good use cases for a rewriter in general, but are unhappy with the
> current
@Konrad: I guess it boils down to rich-text processing again. So you
could argue that each component should explicitly process all its
rich-text properties explicitly and dump into a data-structure held in
a request attribute. It would be possible, but it would be much more
invasive than
... for urls, not for markup in general.
On Tue, Sep 10, 2019 at 10:35 AM Konrad Windszus wrote:
> The new url rewriter SPI will be perfectly supporting AOP.
> Konrad
>
> > Am 10.09.2019 um 16:09 schrieb Justin Edelson >:
> >
> > I see that the same assumptions are being made here that were
Robert Munteanu created SLING-8700:
--
Summary: Unexpected compiler errors in Eclipse during development
Key: SLING-8700
URL: https://issues.apache.org/jira/browse/SLING-8700
Project: Sling
rombert opened a new pull request #9: SLING-3629 - Provide an XML formatter for
content.xml files
URL: https://github.com/apache/sling-ide-tooling/pull/9
Update following review comments from @kwin
This is an automated
[
https://issues.apache.org/jira/browse/SLING-8699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-8699:
---
Issue Type: New Feature (was: Task)
> Create sub-command to moving artifacts to
Filed https://issues.apache.org/jira/browse/SLING-8699 for tracking.
Thanks,
Robert
On Wed, 2019-09-11 at 04:19 +0200, Carsten Ziegeler wrote:
> Sounds good to me, with the addition that it does not upload the md5
> files to SVN and only creates the sha256 (or sha512?) if the check
> of
> the
[
https://issues.apache.org/jira/browse/SLING-8572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-8572.
Resolution: Fixed
Fixed with [sling-tooling-jenkins commit
[
https://issues.apache.org/jira/browse/SLING-8572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928409#comment-16928409
]
Robert Munteanu commented on SLING-8572:
I've expanded the status check to use
[
https://issues.apache.org/jira/browse/SLING-8572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928398#comment-16928398
]
Robert Munteanu commented on SLING-8572:
It seems that the current result is not recognised for
[
https://issues.apache.org/jira/browse/SLING-8572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu reassigned SLING-8572:
--
Assignee: Robert Munteanu
> sling-ide-tooling is reported as broken but is actually
[
https://issues.apache.org/jira/browse/SLING-8594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Tripodi resolved SLING-8594.
---
Resolution: Won't Fix
Existing Analyzer Tasks provide the same check already
> Create an
Robert Munteanu created SLING-8699:
--
Summary: Create sub-command to moving artifacts to dist.apache.org
Key: SLING-8699
URL: https://issues.apache.org/jira/browse/SLING-8699
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-8698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928309#comment-16928309
]
Robert Munteanu edited comment on SLING-8698 at 9/12/19 7:29 AM:
-
It's
[
https://issues.apache.org/jira/browse/SLING-8698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928309#comment-16928309
]
Robert Munteanu commented on SLING-8698:
It's still [~bellingard] that needs to add you to the
[
https://issues.apache.org/jira/browse/SLING-8683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928290#comment-16928290
]
Carsten Ziegeler edited comment on SLING-8683 at 9/12/19 7:00 AM:
--
[
https://issues.apache.org/jira/browse/SLING-8683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928290#comment-16928290
]
Carsten Ziegeler commented on SLING-8683:
-
Renamed the mojo to include artifact and adjusted the
51 matches
Mail list logo
