Henry, I've got the access to upload artifacts to https://repository.apache.org/service/local/staging/deploy/maven2/, and based on the result of latest execution, all .jar, .asc, etc. of eagle 0.4.0-incubating are uploaded to the url successfully. However, I still cannot find them via web-browser from https://repository.apache.org/content/repositories/releases/org/apache/. I went through all documents I had read about the uploading process, but didn't find any instruction for how to verify the visibility of the uploaded jars. Do you have any idea with it, please?
BTW, is there any additional operation/request I have to make, or is there any sync process that I have to wait for? Thanks. Michael On Thu, Aug 11, 2016 at 11:21 AM, Michael Wu <[email protected]> wrote: > Tickets created: > https://issues.apache.org/jira/browse/INFRA-12409 > https://issues.apache.org/jira/browse/INFRA-12410 > > On Thu, Aug 11, 2016 at 10:07 AM, Michael Wu <[email protected]> wrote: > >> Henry, >> >> Thank you very much for guiding me with those details! I'll do it right >> now. >> >> Michael >> >> On Tue, Aug 9, 2016 at 2:39 AM, Henry Saputra <[email protected]> >> wrote: >> >>> So, we need to file 2 infra tickets: >>> 1. One is to add target in Maven repository for Eagle. You can see sample >>> from here: https://issues.apache.org/jira/browse/INFRA-8026 or >>> https://issues.apache.org/jira/browse/INFRA-7246 >>> 2. Create ticket for you to be granted karma to access Apache Nexus repo. >>> >>> - Henry >>> >>> On Mon, Aug 8, 2016 at 12:56 AM, Michael Wu <[email protected]> wrote: >>> >>> > Hi Henry, >>> > >>> > No, eagle never pushed artifacts to ASF Nexus repository. How can we >>> get >>> > the access, please? >>> > >>> > Michael >>> > >>> > On Mon, Aug 8, 2016 at 2:21 PM, Henry Saputra <[email protected] >>> > >>> > wrote: >>> > >>> > > I found Eagle in ASF release dist folder but do not see it in the >>> Nexus >>> > > Maven repo (https://repository.apache.org) >>> > > >>> > > Has Eagle pushed artifacts to ASF Nexus repository for prev releases? >>> > > >>> > > - Henry >>> > > >>> > > On Wed, Aug 3, 2016 at 8:04 PM, Michael Wu <[email protected]> >>> wrote: >>> > > >>> > > > Hi mentors, >>> > > > >>> > > > I was trying to use >>> > > > >>> > > > $> mvn -Papache-release -DskipTests -Dgpg.passphrase=${GPG_ >>> > > PASSPHRASE} >>> > > > deploy >>> > > > >>> > > > to upload eagle's jars to >>> > > > https://repository.apache.org/service/local/staging/deploy/maven2, >>> but >>> > > it >>> > > > always return 400 error, as below fragment: >>> > > > ******************** >>> > > > [ERROR] Failed to execute goal >>> > > > org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy >>> > > (default-deploy) >>> > > > on project eagle-parent: Failed to deploy artifacts: Could not >>> transfer >>> > > > artifact org.apache.eagle:eagle-parent:pom:0.4.0-incubating >>> from/to >>> > > > apache.releases.https ( >>> > > > https://repository.apache.org/service/local/staging/deploy/maven2 >>> ): >>> > > Failed >>> > > > to transfer file: >>> > > > https://repository.apache.org/service/local/staging/deploy/ >>> > > > maven2/org/apache/eagle/eagle-parent/0.4.0-incubating/eagle- >>> > > > parent-0.4.0-incubating.pom. >>> > > > Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1] >>> > > > ******************** >>> > > > >>> > > > Could you instruct me, whether it's caused by the lack of access >>> to the >>> > > > repository and which mailing list I should get connected with to >>> solve >>> > > this >>> > > > issue, please? Thanks. >>> > > > >>> > > > Michael >>> > > > >>> > > >>> > >>> >> >> >
