Daniel Vimont created HBASE-17598:
-------------------------------------
Summary: new archetypes apparently not deployed to Maven Central
Repository
Key: HBASE-17598
URL: https://issues.apache.org/jira/browse/HBASE-17598
Project: HBase
Issue Type: Bug
Components: Usability
Affects Versions: 1.3.0, 1.3.1
Reporter: Daniel Vimont
On search.maven.org, one sees that most of the artifacts for the 1.3.0 release
have been successfully deployed, but neither of the two new archetypes can
apparently be found there:
{{hbase-client-project-archetype}}
{{hbase-shaded-client-project-archetype}}
We do see the projects used to *build* the archetypes (which actually probably
don't need to be published via Maven), but we do not see the archetypes
themselves.
For a specific example, the following artifacts (POM and JAR) need to have been
deployed for the first archetype listed above:
{{hbase/hbase-archetypes/hbase-client-project/target/build-archetype/target/generated-sources/archetype/pom.xml}}
{{hbase/hbase-archetypes/hbase-client-project/target/build-archetype/target/generated-sources/archetype/target/hbase-client-project-archetype-1.3.0.jar}}
(The awkwardly deep directory structures are what the Maven
archetype-generation tools generate during the build of hbase.)
BTW, the Maven documentation on the deployment of archetypes amounts to a
single sentence:
"Once you are happy with the state of your archetype, you can deploy (or submit
it to Maven Central) it as any other artifact and the archetype will then be
available to any user of Maven."
That sentence is found on this page:
https://maven.apache.org/guides/mini/guide-creating-archetypes.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
