>
> I will not argue about the names as they make totally sense but we should try
> to be more consistent. Back then I was asked to use a more specific project/
> repo: sling-org-apache-sling-bnd-plugin-headers-parameters-remove¹ instead of
> just sling-org-apache-sling-bnd-plugins²
>
> O.
>
On Thursday, 2 June 2022 14:05:22 CEST Konrad Windszus wrote:
> I see, then “sling-maven-enforcer-rules” and "maven-enforcer-rules” make
> more sense. WDYT?
I will not argue about the names as they make totally sense but we should try
to be more consistent. Back then I was asked to use a more
Sounds good to me. You could go with the other one as well, I was just
curious :-)
Thanks,
Robert
On Thu, 2022-06-02 at 14:05 +0200, Konrad Windszus wrote:
> I see, then “sling-maven-enforcer-rules” and "maven-enforcer-rules”
> make more sense.
> WDYT?
> Konrad
>
> > On 2. Jun 2022, at 13:58,
I see, then “sling-maven-enforcer-rules” and "maven-enforcer-rules” make more
sense.
WDYT?
Konrad
> On 2. Jun 2022, at 13:58, Robert Munteanu wrote:
>
> On Thu, 2022-06-02 at 09:56 +, Konrad Windszus wrote:
>> Coming back to this topic after a long time I propose to use the
>> repository
On Thu, 2022-06-02 at 09:56 +, Konrad Windszus wrote:
> Coming back to this topic after a long time I propose to use the
> repository name "sling-org-apache-sling-maven-enforcer-rules" for
> this and give it artifact id "org.apache.sling.maven.enforcer.rules".
>
> If I don't hear any
Coming back to this topic after a long time I propose to use the repository
name "sling-org-apache-sling-maven-enforcer-rules" for this and give it
artifact id "org.apache.sling.maven.enforcer.rules".
If I don't hear any objections I would create the repo at the end of the week.
Konrad
On
Hi,
On Fri, May 28, 2021 at 9:05 AM Konrad Windszus wrote:
> ...I propose to create a dedicated repository in Sling containing Enforcer
> Rules starting with this one rule...
Works for me as long as automated tests make the maintenance of those
rules easy.
-Bertrand
Hi,
I tried to contribute a Enforcer Rule to Apache Maven Enforcer in
https://issues.apache.org/jira/browse/MENFORCER-385 (PR in
https://github.com/apache/maven-enforcer/pull/97)
Unfortunately the Maven committers consider this rule covering too much of an
edge case to be considered for
