Currently, the RepoInit grammer does not seem to support creating groups,
which is somewhat problematic if you want to be able to assign both service
user and group ACLs during the RepoInit process.
As mentioned in SLING-5499[1], this was planned and adding support for
groups should be discussed.
[
https://issues.apache.org/jira/browse/SLING-8080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743419#comment-16743419
]
Robert Munteanu commented on SLING-8080:
Stopping progress for now - we will probably switch to
[
https://issues.apache.org/jira/browse/SLING-7936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743418#comment-16743418
]
Robert Munteanu commented on SLING-7936:
Stopping progress since I think any maven plugin
[
https://issues.apache.org/jira/browse/SLING-7245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743417#comment-16743417
]
Robert Munteanu commented on SLING-7245:
Things seem to mostly work, including email
On Tue, 2019-01-15 at 15:45 +0100, Bertrand Delacretaz wrote:
> On Tue, Jan 15, 2019 at 3:31 PM Stefan Seifert <
> sseif...@pro-vision.de> wrote:
> > ...as starting point i've created a wiki page:
> > https://cwiki.apache.org/confluence/x/VIUCBg ...
>
> Thank you! I have tweaked it to make it
On Tue, 2019-01-15 at 14:52 -0600, Daniel Klco wrote:
> Yeah, sorry a sling project specifically.
I don't think we have one yet...
Robert
Yeah, sorry a sling project specifically.
On Tue, Jan 15, 2019, 9:29 AM Robert Munteanu On Tue, 2019-01-15 at 08:28 -0600, Daniel Klco wrote:
> > Badging should be possible, I'm not sure right now we have an example
> > of
> > deprecated projects which are in GitHub. If someone wanted to point
On Tue, 2019-01-15 at 08:28 -0600, Daniel Klco wrote:
> Badging should be possible, I'm not sure right now we have an example
> of
> deprecated projects which are in GitHub. If someone wanted to point
> me to
> one, I could check why it's not badged properly.
This is an archived repository.
On Tue, 2019-01-15 at 14:31 +, Stefan Seifert wrote:
> > I know there are multiple Github-related items that we would to get
> > more tooling on:
> >
> > - archiving repositories
> > - github topics
> > - disabling Jira integration
> >
> > It would be great is someone could create a wiki
On Tue, Jan 15, 2019 at 3:31 PM Stefan Seifert wrote:
>
> ...as starting point i've created a wiki page:
> https://cwiki.apache.org/confluence/x/VIUCBg ...
Thank you! I have tweaked it to make it clearer that we will gladly
accept collaborations from other projects on this.
Once we agree on
Hello Devs!
You're receiving this email because you are subscribed to one or more
Apache developer email lists.
I’m writing to let you know about an exciting event coming to the Chicago
area: The Apache Roadshow Chicago. It will be held May 13th and 14th at
three bars in the Logan Square
>I know there are multiple Github-related items that we would to get
>more tooling on:
>
>- archiving repositories
>- github topics
>- disabling Jira integration
>
>It would be great is someone could create a wiki page which lists all
>our needs so we can take this to infra and see how we can
Badging should be possible, I'm not sure right now we have an example of
deprecated projects which are in GitHub. If someone wanted to point me to
one, I could check why it's not badged properly.
A few additional thoughts/questions:
- As an interim, could we prepend deprecated / obsolete
Robert Munteanu created SLING-8216:
--
Summary: Resolve GitHub API quota issues
Key: SLING-8216
URL: https://issues.apache.org/jira/browse/SLING-8216
Project: Sling
Issue Type: Sub-task
On Tue, 2019-01-15 at 14:00 +0100, Bertrand Delacretaz wrote:
> On Tue, Jan 15, 2019 at 1:32 PM Carsten Ziegeler <
> cziege...@apache.org> wrote:
> > That (archiving) sounds like a good option to me...
>
> I like it as well, but...
>
> > Stefan Seifert wrote
> > > additionally in github there is
On Tue, Jan 15, 2019 at 1:32 PM Carsten Ziegeler wrote:
> That (archiving) sounds like a good option to me...
I like it as well, but...
> Stefan Seifert wrote
> > additionally in github there is an option to "archive" a repository [1]...
> > I suppose this can only be done by infra...
Unless
That (archiving) sounds like a good option to me
Regards
Carsten
Stefan Seifert wrote
i think as well we should not delete the git repository.
adding a badge makes sense.
additionally in github there is an option to "archive" a repository [1] - it's then set
to readonly for everyone and
karlpauls merged pull request #12: SLING-8215 - adding the missing support for
multilevel nesting of sub…
URL:
https://github.com/apache/sling-org-apache-sling-feature-extension-content/pull/12
As this is a foreign pull request (from a fork), the diff has been
sent to your commit
DominikSuess opened a new pull request #12: SLING-8215 - adding the missing
support for multilevel nesting of sub…
URL:
https://github.com/apache/sling-org-apache-sling-feature-extension-content/pull/12
…packages
This is an
i think as well we should not delete the git repository.
adding a badge makes sense.
additionally in github there is an option to "archive" a repository [1] - it's
then set to readonly for everyone and github displays a label "Archived" in the
repository list and a warning message if anything
[
https://issues.apache.org/jira/browse/SLING-8204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742957#comment-16742957
]
Stefan Seifert commented on SLING-8204:
---
the git repository was renamed to
Dominik Süß created SLING-8215:
--
Summary: Content-Extension fails to handle multilayer nesting of
packages
Key: SLING-8215
URL: https://issues.apache.org/jira/browse/SLING-8215
Project: Sling
Hi Carsten,
> On 15 Jan 2019, at 10:49, Carsten Ziegeler wrote:
>
> The thread at [1] seems to suggest batches.
We did suggest badges, but I think we never added them anywhere, or at least I
cannot find them. Instead, we’ve created a Deprecated section at [2].
>
> I personally don't like
See https://builds.apache.org/job/sling-ide-tooling/job/master/73/
[
https://issues.apache.org/jira/browse/SLING-8214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742911#comment-16742911
]
David Bosschaert commented on SLING-8214:
-
The ability to specify additional metadata is already
Hi
with svn we moved deprecated/obsolete modules to the attic
How do we handle this now with git?
The thread at [1] seems to suggest batches.
I personally don't like having git repositories around which should not
be used. On the other hand, removing the git repo has some disadvantages
as
ah, ok - than we can go with sling-maven-plugin.
i've opened a ticket to do the rename [1].
stefan
[1] https://issues.apache.org/jira/browse/INFRA-17653
>-Original Message-
>From: Robert Munteanu [mailto:romb...@apache.org]
>Sent: Tuesday, January 15, 2019 9:27 AM
>To:
Karl Pauls created SLING-8214:
-
Summary: Provide a way to handle bundles with same symbolic name
but different mvn group/artifact ids
Key: SLING-8214
URL: https://issues.apache.org/jira/browse/SLING-8214
[
https://issues.apache.org/jira/browse/SLING-8213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bosschaert updated SLING-8213:
Fix Version/s: slingfeature-maven-plugin 0.8.2
> Not possible to specify wildcard handler
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
30 matches
Mail list logo
