Should we have https://repository.apache.org/content/repositories/staging/org/apache/toree/ exist before publishing to staging? I don't know if that gets created the first time we publish to staging, or if that is something we need to get made through infrastructure or some other means.
On Wed, Dec 7, 2016 at 9:52 AM Chip Senkbeil <[email protected]> wrote: > Yep, verified that the signatures are generated each jar, its sources jar, > its pom, and its javadoc jar. All credentials are in place, gpg passphrase > is being used correctly to sign the jars, and I'm still getting forbidden > errors such as the following: > > (toree-sql-interpreter/*:publishSigned) java.io.IOException: Access to URL > https://repository.apache.org/content/repositories/staging/org/apache/toree/kernel/toree-sql-interpreter_2.10/0.1.0-incubating/toree-sql-interpreter_2.10-0.1.0-incubating-sources.jar > was refused by the server: Forbidden > > > On Wed, Dec 7, 2016 at 7:27 AM Chip Senkbeil <[email protected]> > wrote: > > I believe they are. We're using an sbt plugin that I've also used to > publish signed jars to maven central. I'll try to inspect later today to > make sure. > > Is there no way to upload signed jars by hand just to test my permissions? > > On Tue, Dec 6, 2016, 9:25 PM Hitesh Shah <[email protected]> wrote: > > Are the jars being signed with your gpg key? For releases, unsigned jars > are not allowed so that might be something to check too. > > -- Hitesh > > > > On Tue, Dec 6, 2016 at 7:01 PM, Chip Senkbeil <[email protected]> > wrote: > > > I've got my credentials configured, although we're using sbt instead of > > Maven to publish our artifacts. Before I had my credentials added, I was > > getting another error about not having credentials; so, I'm pretty sure > > they're being applied when publishing the jars. Is there a way to > manually > > add jars to staging through the Nexus UI just to see if my account has > > permission? > > > > On Tue, Dec 6, 2016 at 6:44 PM Luciano Resende <[email protected]> > > wrote: > > > > > Looks like the staging profile is set for toree... have you configured > to > > > pass your credentials when trying to deploy ? In maven I just configure > > the > > > settings.xml with credentials and it works... see some details on > > > http://maven.apache.org/developers/committer-settings.html > > > > > > On Tue, Dec 6, 2016 at 10:25 AM, Chip Senkbeil < > [email protected]> > > > wrote: > > > > > > > Moved to dev. > > > > > > > > On Tue, Dec 6, 2016 at 12:23 PM Hitesh Shah <[email protected]> > wrote: > > > > > > > > > Lets move this conversation to dev@. > > > > > > > > > > thanks > > > > > -- Hitesh > > > > > > > > > > On Tue, Dec 6, 2016 at 8:52 AM, Chip Senkbeil < > > [email protected] > > > > > > > > > wrote: > > > > > > > > > > Both Gino and I have gotten forbidden errors when trying to publish > > > Toree > > > > > jars to staging. I'm able to login to nexus via > > > > > https://repository.apache.org with my apache credentials just > fine. > > > Gino > > > > > was able to publish to snapshot okay. > > > > > > > > > > I checked out an example of an Apache Spark release vote sent to > > IPMC, > > > > and > > > > > their staging has an interesting name associated with it: > > > > > > > > > https://repository.apache.org/content/repositories/orgapachespark-1006/ > > > > > (from > > > > > https://lists.apache.org/api/source.lua/ > > d1e547d49a43f837c0ad13364ac82a > > > > 4b84801b755c4a364b8ab42c6d@1390809763@% > 3Cgeneral.incubator.apache.org > > %3E > > > > > ) > > > > > > > > > > How do we get staging working? Do we need to go to infrastructure > > > again? > > > > > Is it necessary if we have the content under snapshots? > > > > > > > > > > I wanted to close the Toree dev vote thread and start the vote > thread > > > on > > > > > IPMC. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Luciano Resende > > > http://twitter.com/lresende1975 > > > http://lresende.blogspot.com/ > > > > > > >
