hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Vimont (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17598) new archetypes apparently not deployed to Maven Central Repository
Date Wed, 29 Mar 2017 01:30:42 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946363#comment-15946363

Daniel Vimont commented on HBASE-17598:

[~mantonov]: I hope you don't mind that I added you as a "Watcher" of this issue. Since you're
the steward of all things 1.3.x, I thought this should be brought to your attention. If my
observations above are correct, then apparently some kind of modification needs to be made
to whatever script (or other mechanism) is behind final deployment of artifacts to the Maven
central repository. I don't think I (as only a contributor) have access to that, but please
let me know if you need my assistance resolving this to get {{hbase-client-project-archetype}}
and {{hbase-shaded-client-project-archetype}} available to the end-user community.


> 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

View raw message