Re: Error Publishing OSX package to Maven
Qing helped test by excluding the bundle/source. It still creates 2 repos in Staging. I am not sure if Maven Version or some other maven-plugin difference is causing this issue, there was no issue publishing to Linux-CPU and Linux-GPU from the same code. For now, I have manually uploaded the artifacts(generated through maven release prepare/perform) to the Staging repo so we can make it available for OSX users. This issue needs to be investigated independently. -Naveen On Tue, Sep 11, 2018 at 2:03 PM, Naveen Swamy wrote: > that seems reasonable. I also asked this question on d...@maven.apache.org > to see if there is anything obvious that we missed. > > https://lists.apache.org/thread.html/def6e5c6c47ab2f39592a1fe060b6c > fd0008d303a2b5c814545d231b@%3Cdev.maven.apache.org%3E > > On Tue, Sep 11, 2018 at 11:25 AM, Carin Meier > wrote: > >> I would suggest trying >> >> * Remove bundle/source jar from 1.3.0 and attempt publishing OSX package. >> and seeing if that solves the problem and allows publishing to staging. >> >> If it does work then it helps to identity the cause. >> If the effort does not take to long. I would recommend timeboxing the >> effort and if it is going to take more effort to investigate, we can go >> with announcing later for OSX. >> >> >> - Carin >> >> On Tue, Sep 11, 2018 at 2:10 PM Naveen Swamy wrote: >> >> > hey all, >> > >> > I am working on publishing the 1.3.0 Scala package to Maven and >> > encountering a error when I am about to Close the Repo on Nexus. When I >> > publish the OSX package to Staging, the artifacts gets split into 2 >> > repositories and when I close[1] the repo(to make it available for use) >> it >> > fails since the signature files are in a different repo. This is how the >> > artifacts are getting split >> > >> > Repo1: orgapachemxnet-1018 >> > === >> > mxnet-full_2.11-osx-x86_64-cpu-bundle.jar.md5 >> > mxnet-full_2.11-osx-x86_64-cpu-bundle.jar.sha1 >> > mxnet-full_2.11-osx-x86_64-cpu-sources.jar.asc >> > mxnet-full_2.11-osx-x86_64-cpu-sources.jar.md5 >> > mxnet-full_2.11-osx-x86_64-cpu-src.jar.md5 >> > mxnet-full_2.11-osx-x86_64-cpu-src.jar.sha1 >> > mxnet-full_2.11-osx-x86_64-cpu.jar >> > mxnet-full_2.11-osx-x86_64-cpu.jar.asc >> > mxnet-full_2.11-osx-x86_64-cpu.pom.md5 >> > mxnet-full_2.11-osx-x86_64-cpu.pom.sha1 >> > >> > >> > Repo2: orgapachemxnet-1019 >> > === >> > mxnet-full_2.11-osx-x86_64-cpu-bundle.jar >> > mxnet-full_2.11-osx-x86_64-cpu-bundle.jar.asc >> > mxnet-full_2.11-osx-x86_64-cpu-sources.jar >> > mxnet-full_2.11-osx-x86_64-cpu-sources.jar.sha1 >> > mxnet-full_2.11-osx-x86_64-cpu-src.jar >> > mxnet-full_2.11-osx-x86_64-cpu-src.jar.asc >> > mxnet-full_2.11-osx-x86_64-cpu-jar.md5 >> > mxnet-full_2.11-osx-x86_64-cpu.jar.sha1 >> > mxnet-full_2.11-osx-x86_64-cpu.pom >> > mxnet-full_2.11-osx-x86_64-cpu.pom.asc >> > >> > This was not an issue with Linux-CPU and Linux-GPU versions for 1.3.0 >> and >> > suspicion is the new Source and documentation jar files being added as a >> > part of 1.3.0 for OSX. >> > >> > There are 2 options >> > * Continue to investigate the issue and announce later for OSX (after >> the >> > general announcement) >> > * Remove bundle/source jar from 1.3.0 and attempt publishing OSX >> package. >> > >> > What do you guys suggest? >> > >> > >> > 1) Closing Staged Repo - >> > >> > https://central.sonatype.org/pages/releasing-the-deployment. >> html#locate-and-examine-your-staging-repository >> > 2) Scala Release Process: >> > >> > https://cwiki.apache.org/confluence/display/MXNET/MXNet- >> Scala+Release+Process >> > >> > >
Re: Error Publishing OSX package to Maven
that seems reasonable. I also asked this question on d...@maven.apache.org to see if there is anything obvious that we missed. https://lists.apache.org/thread.html/def6e5c6c47ab2f39592a1fe060b6cfd0008d303a2b5c814545d231b@%3Cdev.maven.apache.org%3E On Tue, Sep 11, 2018 at 11:25 AM, Carin Meier wrote: > I would suggest trying > > * Remove bundle/source jar from 1.3.0 and attempt publishing OSX package. > and seeing if that solves the problem and allows publishing to staging. > > If it does work then it helps to identity the cause. > If the effort does not take to long. I would recommend timeboxing the > effort and if it is going to take more effort to investigate, we can go > with announcing later for OSX. > > > - Carin > > On Tue, Sep 11, 2018 at 2:10 PM Naveen Swamy wrote: > > > hey all, > > > > I am working on publishing the 1.3.0 Scala package to Maven and > > encountering a error when I am about to Close the Repo on Nexus. When I > > publish the OSX package to Staging, the artifacts gets split into 2 > > repositories and when I close[1] the repo(to make it available for use) > it > > fails since the signature files are in a different repo. This is how the > > artifacts are getting split > > > > Repo1: orgapachemxnet-1018 > > === > > mxnet-full_2.11-osx-x86_64-cpu-bundle.jar.md5 > > mxnet-full_2.11-osx-x86_64-cpu-bundle.jar.sha1 > > mxnet-full_2.11-osx-x86_64-cpu-sources.jar.asc > > mxnet-full_2.11-osx-x86_64-cpu-sources.jar.md5 > > mxnet-full_2.11-osx-x86_64-cpu-src.jar.md5 > > mxnet-full_2.11-osx-x86_64-cpu-src.jar.sha1 > > mxnet-full_2.11-osx-x86_64-cpu.jar > > mxnet-full_2.11-osx-x86_64-cpu.jar.asc > > mxnet-full_2.11-osx-x86_64-cpu.pom.md5 > > mxnet-full_2.11-osx-x86_64-cpu.pom.sha1 > > > > > > Repo2: orgapachemxnet-1019 > > === > > mxnet-full_2.11-osx-x86_64-cpu-bundle.jar > > mxnet-full_2.11-osx-x86_64-cpu-bundle.jar.asc > > mxnet-full_2.11-osx-x86_64-cpu-sources.jar > > mxnet-full_2.11-osx-x86_64-cpu-sources.jar.sha1 > > mxnet-full_2.11-osx-x86_64-cpu-src.jar > > mxnet-full_2.11-osx-x86_64-cpu-src.jar.asc > > mxnet-full_2.11-osx-x86_64-cpu-jar.md5 > > mxnet-full_2.11-osx-x86_64-cpu.jar.sha1 > > mxnet-full_2.11-osx-x86_64-cpu.pom > > mxnet-full_2.11-osx-x86_64-cpu.pom.asc > > > > This was not an issue with Linux-CPU and Linux-GPU versions for 1.3.0 and > > suspicion is the new Source and documentation jar files being added as a > > part of 1.3.0 for OSX. > > > > There are 2 options > > * Continue to investigate the issue and announce later for OSX (after the > > general announcement) > > * Remove bundle/source jar from 1.3.0 and attempt publishing OSX package. > > > > What do you guys suggest? > > > > > > 1) Closing Staged Repo - > > > > https://central.sonatype.org/pages/releasing-the- > deployment.html#locate-and-examine-your-staging-repository > > 2) Scala Release Process: > > > > https://cwiki.apache.org/confluence/display/MXNET/ > MXNet-Scala+Release+Process > > >
Re: Error Publishing OSX package to Maven
I would suggest trying * Remove bundle/source jar from 1.3.0 and attempt publishing OSX package. and seeing if that solves the problem and allows publishing to staging. If it does work then it helps to identity the cause. If the effort does not take to long. I would recommend timeboxing the effort and if it is going to take more effort to investigate, we can go with announcing later for OSX. - Carin On Tue, Sep 11, 2018 at 2:10 PM Naveen Swamy wrote: > hey all, > > I am working on publishing the 1.3.0 Scala package to Maven and > encountering a error when I am about to Close the Repo on Nexus. When I > publish the OSX package to Staging, the artifacts gets split into 2 > repositories and when I close[1] the repo(to make it available for use) it > fails since the signature files are in a different repo. This is how the > artifacts are getting split > > Repo1: orgapachemxnet-1018 > === > mxnet-full_2.11-osx-x86_64-cpu-bundle.jar.md5 > mxnet-full_2.11-osx-x86_64-cpu-bundle.jar.sha1 > mxnet-full_2.11-osx-x86_64-cpu-sources.jar.asc > mxnet-full_2.11-osx-x86_64-cpu-sources.jar.md5 > mxnet-full_2.11-osx-x86_64-cpu-src.jar.md5 > mxnet-full_2.11-osx-x86_64-cpu-src.jar.sha1 > mxnet-full_2.11-osx-x86_64-cpu.jar > mxnet-full_2.11-osx-x86_64-cpu.jar.asc > mxnet-full_2.11-osx-x86_64-cpu.pom.md5 > mxnet-full_2.11-osx-x86_64-cpu.pom.sha1 > > > Repo2: orgapachemxnet-1019 > === > mxnet-full_2.11-osx-x86_64-cpu-bundle.jar > mxnet-full_2.11-osx-x86_64-cpu-bundle.jar.asc > mxnet-full_2.11-osx-x86_64-cpu-sources.jar > mxnet-full_2.11-osx-x86_64-cpu-sources.jar.sha1 > mxnet-full_2.11-osx-x86_64-cpu-src.jar > mxnet-full_2.11-osx-x86_64-cpu-src.jar.asc > mxnet-full_2.11-osx-x86_64-cpu-jar.md5 > mxnet-full_2.11-osx-x86_64-cpu.jar.sha1 > mxnet-full_2.11-osx-x86_64-cpu.pom > mxnet-full_2.11-osx-x86_64-cpu.pom.asc > > This was not an issue with Linux-CPU and Linux-GPU versions for 1.3.0 and > suspicion is the new Source and documentation jar files being added as a > part of 1.3.0 for OSX. > > There are 2 options > * Continue to investigate the issue and announce later for OSX (after the > general announcement) > * Remove bundle/source jar from 1.3.0 and attempt publishing OSX package. > > What do you guys suggest? > > > 1) Closing Staged Repo - > > https://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository > 2) Scala Release Process: > > https://cwiki.apache.org/confluence/display/MXNET/MXNet-Scala+Release+Process >
Error Publishing OSX package to Maven
hey all, I am working on publishing the 1.3.0 Scala package to Maven and encountering a error when I am about to Close the Repo on Nexus. When I publish the OSX package to Staging, the artifacts gets split into 2 repositories and when I close[1] the repo(to make it available for use) it fails since the signature files are in a different repo. This is how the artifacts are getting split Repo1: orgapachemxnet-1018 === mxnet-full_2.11-osx-x86_64-cpu-bundle.jar.md5 mxnet-full_2.11-osx-x86_64-cpu-bundle.jar.sha1 mxnet-full_2.11-osx-x86_64-cpu-sources.jar.asc mxnet-full_2.11-osx-x86_64-cpu-sources.jar.md5 mxnet-full_2.11-osx-x86_64-cpu-src.jar.md5 mxnet-full_2.11-osx-x86_64-cpu-src.jar.sha1 mxnet-full_2.11-osx-x86_64-cpu.jar mxnet-full_2.11-osx-x86_64-cpu.jar.asc mxnet-full_2.11-osx-x86_64-cpu.pom.md5 mxnet-full_2.11-osx-x86_64-cpu.pom.sha1 Repo2: orgapachemxnet-1019 === mxnet-full_2.11-osx-x86_64-cpu-bundle.jar mxnet-full_2.11-osx-x86_64-cpu-bundle.jar.asc mxnet-full_2.11-osx-x86_64-cpu-sources.jar mxnet-full_2.11-osx-x86_64-cpu-sources.jar.sha1 mxnet-full_2.11-osx-x86_64-cpu-src.jar mxnet-full_2.11-osx-x86_64-cpu-src.jar.asc mxnet-full_2.11-osx-x86_64-cpu-jar.md5 mxnet-full_2.11-osx-x86_64-cpu.jar.sha1 mxnet-full_2.11-osx-x86_64-cpu.pom mxnet-full_2.11-osx-x86_64-cpu.pom.asc This was not an issue with Linux-CPU and Linux-GPU versions for 1.3.0 and suspicion is the new Source and documentation jar files being added as a part of 1.3.0 for OSX. There are 2 options * Continue to investigate the issue and announce later for OSX (after the general announcement) * Remove bundle/source jar from 1.3.0 and attempt publishing OSX package. What do you guys suggest? 1) Closing Staged Repo - https://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository 2) Scala Release Process: https://cwiki.apache.org/confluence/display/MXNET/MXNet-Scala+Release+Process