# Publish maven project to JCenter

## Step1. 在Bintray portal上新建空的repo和package

repo name我設成`wisepaas-datahub` packagename根據JCenter上慣例, 規則為groupId:artifactId, 所以我的pkg name為`wisepaas.datahub:cloud-sdk`

## Step2. 根據Portal auto-gen提示去修改project pom.xml和maven setting.xml

在portal建完pkg後, 會順便產生設定讓你複製貼上, 點擊 `Set me up` ![](https://3639912965-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M4wburGGKab7MC2oOVd%2F-M4wbweZ8BSNkeEXgUzh%2F-M4wbzzJw0jON90YTeZz%2Fbintrayhint.PNG?generation=1586933822985272\&alt=media) 接著再點擊`Uploading` > `Deploying with Maven` ![](https://3639912965-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M4wburGGKab7MC2oOVd%2F-M4wbweZ8BSNkeEXgUzh%2F-M4wbzzLMrL83HcptQj8%2Fbintrayhint2.PNG?generation=1586933823267014\&alt=media)

要特別注意, password不是指login pwd, 是一組token, 要從portal產生, 可以看到有兩段cfg,上面那一段是要放在全域maven setting.xml的, 下面那段是要放在專案pom.xml的

pom.xml

```
...
    <distributionManagement>
        <repository>
            <id>bintray-advwacloud-wisepaas-datahub</id>
            <name>advwacloud-wisepaas-datahub</name>
            <url>https://api.bintray.com/maven/advwacloud/wisepaas-datahub/wisepaas.datahub:cloud-sdk/;publish=1</url>
        </repository>
    </distributionManagement>
</project>
```

接著要改setting.xml, 不知道它放哪, 可以下mvn -X, 找到下面兩行, 任選一個來改就行

```
[DEBUG] Reading global settings from xxxx\settings.xml
[DEBUG] Reading user settings from xxxx\settings.xml
```

setting.xml已經有註解掉的範例, 修改它就好

## Step3. mvn deploy推到Bintray上

用VSCODE有按鈕可以直接deploy, 或下指令 `& mvn deploy -f "project-path\pom.xml"`

接著到Bintray portal看到maven info有出現就算成功將project推到Bintray了

![](https://3639912965-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M4wburGGKab7MC2oOVd%2F-M4wbweZ8BSNkeEXgUzh%2F-M4wbzzNOvXf1BVqyT8v%2Fbintrayhint3.PNG?generation=1586933823817678\&alt=media)

## Step4. Bintray上推到JCenter, JCenter才是真正的public repo

![](https://3639912965-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M4wburGGKab7MC2oOVd%2F-M4wbweZ8BSNkeEXgUzh%2F-M4wbzzP35gR3LC3f-IU%2Fbintrayhint4.PNG?generation=1586933824240325\&alt=media) ![](https://3639912965-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M4wburGGKab7MC2oOVd%2F-M4wbweZ8BSNkeEXgUzh%2F-M4wbzzRw_v3FJzIQz7R%2Fbintrayhint5.PNG?generation=1586933823642427\&alt=media)

你很有可能會遇到 `POM project file is not valid.`, 代表你的pom.xml缺少某些欄位

這裡列出幾個常見缺少的, 請檢查一下, 以下範例真的可以填空值

```
  <name>scada</name>
  <description>wisepaas scada sdk</description>
  <inceptionYear></inceptionYear>
  <licenses></licenses>
  <organization></organization>
  <developers></developers>
  <contributors></contributors>
  <scm></scm>
```

送出之後不是馬上上架, 好像還會再審核, 而且我記得它會要你附上source code/doc, 但有一招可以繞過

* 先建一個空資料夾
* 放一個README.md (內容隨意)
* 在相同目錄執行 `jar cvf cloud-sdk-0.0.1-sources.jar *`
* 然後直接用Bintray poratl上傳檔案
* 照上述步驟再做一個 `jar cvf cloud-sdk-0.0.1-javadoc.jar *`

接著回到portal

![](https://3639912965-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M4wburGGKab7MC2oOVd%2F-M4wbweZ8BSNkeEXgUzh%2F-M4wbzzTmYZHsNurRVDZ%2Fbintrayhint6.PNG?generation=1586933824455172\&alt=media) ![](https://3639912965-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M4wburGGKab7MC2oOVd%2F-M4wbweZ8BSNkeEXgUzh%2F-M4wbzzVsMOg367jgkP8%2Fbintrayhint7.PNG?generation=1586933824022324\&alt=media) ![](https://3639912965-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M4wburGGKab7MC2oOVd%2F-M4wbweZ8BSNkeEXgUzh%2F-M4wbzzXVioIZbI18_LW%2Fbintrayhint8.PNG?generation=1586933823470363\&alt=media)

好像只有第一版本需要這樣審核, 後面的版本不用doc跟source也可以


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://advwacloud.gitbook.io/rd-newbie-guide/kai-fa-huan-jing/jcenter-maven-tutorial.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.