Aws-sdk-java: Flow Framework: Release build tools jar to Maven Central

[christophercurrie]

The flow build tools jar is only available by downloading the SDK from the AWS website, which makes it awkward to integrate into Maven-driven AspectJ compilation. Please consider releasing this JAR to Maven central so that end users don't need to install it locally. See stackoverflow for more details of this scenario.

[mirceal]

+1

[flozano]

+1 here

[DuvallK]

Now that Amazon has separated the SDK in Maven into multiple modules, this seems like a logical next step.

[ericdcobb]

:+1:

[vvondra]

+1

[andersonkyle]

@fulghum Any update on this issue & #349 ?

[kristianperkins]

+1

[srmds]

+1

[ajkerr]

+100. We asked about this literally years ago on the support forums, and never received a response as to why this jar is not published. I'm guessing there is a licensing issue at play here, but if so, why not just tell us that?

[srmds]

@ajkerr Amen to you! Would also like to have a clear answer on why there is no correspondence on this issue.

[ajkerr]

To make matters worse, recent versions of the full SDK have misnamed versions of this jar file, e.g. aws-java-sdk-flow-build-tools.jar-1.10.65.jar (note the extra '.jar' before the version number).

[fulghum]

Hey guys, sincere apologies for the lack of response from us on this issue. The Flow library is maintained by another team, separate from the AWS SDK for Java team, and unfortunately this issue fell through the cracks. I'm happy to let you know that we are now actively working on getting the Flow build tools published to Maven. The Flow team is working on this, and if they hit any snags, we're going to jump in and help them out.

@ajkerr – As to the jar naming issue, @manikandanrs just fixed this issue in our build logic and we'll get the fix published in the next SDK release going out next week.

Apologies again that it's taken us longer than we'd like to help out with this problem. As always, thank you for all the feedback; please keep it coming! We'll have an update on this for you by the end of next week.

[varunnvs92]

Hey guys, apologies for not getting back sooner. The AWS SDK for Java team has now released the flow build tools jar to Maven. You can add this as a dependency by:

    <dependency>
       <groupId>com.amazonaws</groupId>
       <artifactId>aws-swf-build-tools</artifactId>
       <version>1.0</version>
    </dependency>

I hope this solves the issue that you were facing. Try it out and give us your feedback.

[umcodemonkey]

@varunnvs92 Thanks, this will help immensely. However, I notice that the POM declares the SCM location to be https://github.com/aws/aws-swf-build-tools.git, which does not appear to be publicly available, despite the declaration of Apache 2.0 licensing.

This issue is tracked separately as #349, I'll follow up there as well.

[manikandanrs]

@umcodemonkey we are working on getting it to a separate Github repository. Stay tuned.

[mirceal]

awesome. thanks @fulghum and @varunnvs92 !

[egglestonbd]

@varunnvs92,
The sdk download page references v. 1.10.71 (http://sdk-for-java.amazonwebservices.com/latest/aws-java-sdk.zip) which includes the build flow tools. And your reference above references 1.0. How do they line up?

[varunnvs92]

@egglestonbd Thanks for bringing it up. Both jars are exactly the same. The build tools jar is owned by a different team, so the maven artifactId is named accordingly. We will be renaming the build flow tools jar in aws-java-sdk.zip to match maven within the next few releases. We are investigating the effect of this and will act accordingly. Please let me know if you have more questions. Thank you.

[ajkerr]

Great news! Happy this is finally done.

[manikandanrs]

Closing this issue as the jar is published to maven.