Hi Vitalii I think this would be a temporary headache for people to re-setup/update their IDEs' projects.
Is it possible to have this done together with https://issues.apache.org/jira/browse/DRILL-6956 [https://issues.apache.org/jira/browse/DRILL-6956] (Maintain a single entry for Drill Version in the pom file) ? ~ Kunal On 4/22/2019 4:13:27 AM, Vitalii Diravka <[email protected]> wrote: Hi all! I am going to rename project.artifactId (see [1] or DRILL-7169) from ' *drill-root*' [2] to '*apache-drill*' or 'drill'. Some other project examples: Hbase: hbase [3] Calcite: calcite [4] Parquet: parquet artifactId> [5] Hive: hive [6] Avro: avro-toplevel artifactId> [7] Spark: spark-parent_2.12 [8] Renaming to 'apache-drill' artifatId will allow to use this variable in a lot of places to avoid hard-coding '*apache-drill*' string in different paths [1]. A typical artifact produced by Maven would have the form -. (for example, myapp-1.0.jar) [9], [10]. Current Drill final name of different artifacts: apache-drill-${project.version} Therefore looks like '*apache-drill*' is the best name of Drill artifactId, which will allow to keep consistency of all Drill artifacts. For sure it will lead for changing of Drill artifactId in maven central repository: https://mvnrepository.com/artifact/org.apache.drill/drill-root What do you think guys? Can we update it? Are there any risks to do it? [1] https://github.com/apache/drill/pull/1746 [2] https://github.com/apache/drill/blob/master/pom.xml#L32 [3] https://github.com/apache/hbase/blob/master/pom.xml#L40 [4] https://github.com/apache/calcite/blob/master/pom.xml#L28 [5] https://github.com/apache/parquet-mr/blob/master/pom.xml#L11 [6] https://github.com/apache/hive/blob/master/pom.xml#L23 [7] https://github.com/apache/avro/blob/master/pom.xml#L29 [8] https://github.com/apache/spark/blob/master/pom.xml#L28 [9] https://maven.apache.org/guides/mini/guide-naming-conventions.html [10] https://maven.apache.org/guides/getting-started/ Kind regards Vitalii
