2023-05-03 11:06:20 +02:00
== Why is this an issue?
2021-04-28 16:49:39 +02:00
Shared naming conventions allow teams to collaborate effectively. This rule raises an issue when the a pom's ``++groupId++`` does not match the provided regular expression.
2021-04-28 18:08:03 +02:00
2023-05-03 11:06:20 +02:00
=== Noncompliant code example
2021-04-28 16:49:39 +02:00
With the default regular expression: ``++(com|org)(\.[a-z][a-z-0-9]*)+++``
2022-02-04 17:28:24 +01:00
[source,xml]
2021-04-28 16:49:39 +02:00
----
<project ...>
<groupId>myCo</groupId> <!-- Noncompliant -->
<!-- ... -->
</project>
----
2021-04-28 18:08:03 +02:00
2023-05-03 11:06:20 +02:00
=== Compliant solution
2021-04-28 16:49:39 +02:00
2022-02-04 17:28:24 +01:00
[source,xml]
2021-04-28 16:49:39 +02:00
----
<project ...>
<groupId>com.myco</groupId>
<!-- ... -->
</project>
----
2021-04-28 18:08:03 +02:00
2021-06-02 20:44:38 +02:00
2021-06-03 09:05:38 +02:00
ifdef::env-github,rspecator-view[]
2021-09-20 15:38:42 +02:00
'''
== Implementation Specification
(visible only on this page)
2023-05-25 14:18:12 +02:00
=== Message
2021-09-20 15:38:42 +02:00
2023-05-25 14:18:12 +02:00
Update this "groupId" to match the provided regular expression: xxx.
=== Parameters
.regex
****
----
(com|org)(\.[a-z][a-z-0-9]*)+
----
The regular expression the "groupId" should match
****
=== Highlighting
groupId value
2021-09-20 15:38:42 +02:00
2021-06-08 15:52:13 +02:00
'''
2021-06-02 20:44:38 +02:00
== Comments And Links
(visible only on this page)
2023-05-25 14:18:12 +02:00
=== on 30 Nov 2015, 14:06:29 Michael Gumowski wrote:
LGTM [~ann.campbell.2]!
Note that I'm not sure about your regex. You can have more that one group, separated by dots, after the first ``++com++``/``++org++``.
=== on 30 Nov 2015, 16:00:30 Ann Campbell wrote:
Uhm... yeah [~michael.gumowski]. That's what I intended.
2021-06-03 09:05:38 +02:00
endif::env-github,rspecator-view[]