Publish to maven

[nikita-sheremet-clearscale]

Could you please make version 1.0 and publish this into maven repo?

[ZoharShayHFY]

+1

[lbodor]

+1

[jlarroque]

+1

[geekidentity]

+1

[Nick-Anderssohn]

+1

[vettukal]

+1

[ryl]

+1

[mazherChoudhury]

+1

[rimal]

+1

[tdstein]

+1

[leandro-rouberte]

+1

[grelland]

+1

[DidierLamond]

+1

[technologycoder]

+1

[workmanw]

+1

[AndreLouisCaron]

+1

[ghost]

+1

[Sathishruw]

+1

[masonkirchner]

For everyone wanting this to be published to Maven, you can use JitPack to resolve the dependency.

Gradle:

1. Add it in your root build.gradle at the end of repositories:

	allprojects {
		repositories {
			...
			maven { url 'https://jitpack.io' }
		}
	}

2. Add the dependency:

	dependencies {
	        implementation 'com.github.awslabs:aws-request-signing-apache-interceptor:b3772780da'
	}

Maven:

1. Add the JitPack repository to your build file:

	<repositories>
		<repository>
		    <id>jitpack.io</id>
		    <url>https://jitpack.io</url>
		</repository>
	</repositories>

2. Add the dependency:

	<dependency>
	    <groupId>com.github.awslabs</groupId>
	    <artifactId>aws-request-signing-apache-interceptor</artifactId>
	    <version>b3772780da</version>
	</dependency>

SBT:

1. Add it in your build.sbt at the end of resolvers:

    resolvers += "jitpack" at "https://jitpack.io"

2. Add the dependency

	libraryDependencies += "com.github.awslabs" % "aws-request-signing-apache-interceptor" % "b3772780da"	

[bowbahdoe]

Update on this would be greatly appreciated

[danielpsf]

Although #2 (comment) is a potential workaround, it would be much appreciated if someone just added it to TravisCI and made it available on Maven Central.

I could Open a PR to do that, but I'd really think that it would be better to have AWS to publish it, not to cause confusion on the community having an AWS lib been published under danielpsf name. 😜

[outcomes-keyan-hardman]

+1

[erlemantos]

+1

[jleskovar-tyro]

+1

[nagarajatantry]

AWS Team, Could you please provide an update on this?

[saharathkleips]

+1 Our team would love if this artifact became available on Maven Central

[elrob]

+1

[FedorRomanov]

+1

[segalziv]

+1

[sschwell]

+1

[nvts8a]

+1

[Ryulth]

+1

[paulmdavies]

+1

[MohammedSehweil]

+1

[ameer-harri]

+1

[swyp-de]

seems to be very complicated to put this up.

[sschwell]

fwiw this one worked for me and is available from maven central:

    <dependency>
        <groupId>vc.inreach.aws</groupId>
        <artifactId>aws-signing-request-interceptor</artifactId>
        <version>0.0.22</version>
    </dependency>

[acm19]

Given nobody seems to maintain this repository and I really needed this feature released I created a fork and refactor it to have version 2. AWS guys please let me know if you are interested on implementing and releasing it and I can create a PR. In the meanwhile the repository is: https://github.com/acm19/aws-request-signing-apache-interceptor and released on github packages: https://github.com/acm19/aws-request-signing-apache-interceptor/packages/209282 in case it's useful to anyone else.

[aetter]

Hi all, thanks for all the helpful comments and code samples. I'm working to find a team to own and maintain this repository, given that it's so useful and hasn't seen much activity in a long time. Goals for that team will be to examine acm19's awesome work with version 2 of the SDK and see about publishing to Maven. In the meantime, we've merged an important bug fix for an issue that could cause operations like flush and force merge to fail with a signature mismatch error.

Edit 1/22/2021: I haven't been able to get any traction here. I share everyone's frustrations around the state of the library and will keep trying to find a team to own maintenance, but don't have any good news to share at this time. 👎