syntax for specifying maven group + artifact ids
See original GitHub issue@FroMage has introduced an artifact
annotation for specifying Maven group and artifact ids. I’m not happy with that since our import
statements already have a welldefined syntax for specifying these. I will introduce the following syntax:
module org.hibernate.core org.hibernate:"hibernate-core" "2.1.1" { ... }
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Guide to Naming Conventions - Apache Maven
Guide to naming conventions on groupId, artifactId, and version. groupId uniquely identifies your project across all projects. A group ID should follow ...
Read more >Maven artifact and groupId naming - Stack Overflow
Guide to naming conventions on groupId, artifactId and version · As a work for hire should I use com.my.company.project as groupId or com.client....
Read more >How to Define Maven GroupId with Examples? - eduCBA
Maven groupid is nothing but the id of the project group. Generally, the group id is unique among all the projects. Group id...
Read more >Apache Maven Tutorial - Baeldung
The groupId is a parameter indicating the group or individual that created a project, which is often a reversed company domain name. The ......
Read more >What is the Difference Between groupId and artifactId in Maven
The groupId is an XML element in the POM.XML file of a Maven project that specifies the id of the project group. In...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It doesn’t yet, but it will.
Is that coming before the next release?