Cannot access repository: 400: Invalid request

[msiemens]

It seems like the repository mentioned in the README doesn't work any more. The URL https://raw.githubusercontent.com/TomDemeranville/orcid-java-client/mvn-repo/ results in a HTTP 400 error (Invalid request).

[TomDemeranville]

It look like a github hosting change. Not sure what's going on as the
files are still there.

On Sat, Dec 13, 2014 at 11:51 AM, Markus Siemens [email protected]
wrote:

It seems like the repository mentioned in the README doesn't work any
more. The URL
https://raw.githubusercontent.com/TomDemeranville/orcid-java-client/mvn-repo/
results in a HTTP 400 error (Invalid request).

—
Reply to this email directly or view it on GitHub
#2.

[msiemens]

It looks like GitHub silently disabled directory access via raw.githubusercontent.com.

[TomDemeranville]

Gutted. Not sure how we can fix this.

On Sat, Dec 13, 2014 at 1:04 PM, Markus Siemens [email protected]
wrote:

It looks like GitHub silently disabled directory access via
raw.githubusercontent.com.

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

[rjoberon]

This answer gives a hint: http://stackoverflow.com/a/22210816/1824721

[TomDemeranville]

I've moved jobs and I no longer have the time to maintain the repository.
Perhaps ORCiD would be interested, or you could fork it?

On Tue, Feb 3, 2015 at 1:01 PM, Robert Jäschke [email protected]
wrote:

This answer gives a hint: http://stackoverflow.com/a/22210816/1824721

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

[windmueller]

It would be possible to release the client directly on Maven Central:

http://central.sonatype.org/pages/ossrh-guide.html

However, Tom has to file a request to allow the package "uk.bl.odin". An alternative would be to change the package. Comments?

[TomDemeranville]

Great idea! I think I could get the BL to agree for us to use their domain without much trouble. Or I'm happy for it to change to com.demeranville.orcid (or anything else people suggest)

[windmueller]

Changing the package would break upgrades for people using the client, so in my opinion we should stick with it.

Tom, would you apply for this on the Sonatype page and add me as a contributor?

[TomDemeranville]

Will do, but I'll not be able to do it until later today.

[windmueller]

Tom, is there any news on this?

[windmueller]

I just released 1.12.2, but since we have currently no way to deploy it at Sonatype, it is hard for others to use. Should we stick with the plan of keeping the current package?

[TomDemeranville]

Sorry stephen, I will be able to give this my full attention real soon
now. I think we should keep the odin package name for now and look to more
it to org.orcid in the future.

On Mon, Jun 8, 2015 at 9:55 AM, Stephan Windmüller <[email protected]

wrote:

I just released 1.12.2, but since we have currently no way to deploy it at
Sonatype, it is hard for others to use. Should we stick with the plan of
keeping the current package?

—
Reply to this email directly or view it on GitHub
#2 (comment)
.