You can subscribe to this list here.
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2012 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Andrew M. <mi...@gm...> - 2012-03-20 21:10:41
|
Hi Chris, Firstly, thanks for getting back to me. I know this is probably not one of your top development priorities at Amazon so I really appreciate it. I use the SDK as jar files right now, and have been doing workarounds in an ad-hoc manner, but I would be happy to use the source instead and make modifications as I find bugs and send you patches for it. It would be much easier for me to use the source as a Maven project, because I think using Ant + maven in eclipse with a whole pile of jar files lying around would be a huge mess. I think it would be hard to convert the project to Maven for you in a patch though - what if instead you let me do it in a branch in your repository and then examined the results? I think Maven is the natural way to go since pretty much all of your dependencies use Maven, and it's really easy to add libraries to projects when you don't have to worry about 30 jar files. It will also help to keep track of some of the jar files you aren't really using (especially if they are referenced just one or two times) and keep the dependencies up-to-date. (Also, the AWS SDK uses Maven - I'm not sure if you work on that, but it's pretty well supported.) Is allowing me a branch in your sourceforge repository something you're willing to do? Thanks, Andrew On 03/20/12 15:24, Chris Mounce wrote: > The Java SDK is still being maintained, and we intend on keeping it > up-to-date with new API features. The 1.5.0 release was the first > release in a long time, but it's not going to be our last. > > We do accept community contributions, and if you want to contribute, > that would be fantastic! If you send us patches, we'll look them over, > and they'll probably end up in the next version of the SDK. > > Maven is something we'd like to use to manage our dependencies, but > switching to Maven hasn't been a really high priority. If this is > something that you'd like to do, we'd gladly incorporate your work. > > We're aware of the ClientConfig issue, and we're planning on doing a > bugfix release sometime soon. It sounded like you encountered multiple > bugs -- do you have any other bugfixes that could go out with the release? > > Thanks for your help, > Chris Mounce > > > On 3/15/12 9:42 PM, Andrew Mao wrote: >> Hi, >> >> I was wondering if there is still active development on this SDK, and >> whether or not I could contribute to it. I have been rolling my own API >> for a while and decided to switch to this one when I saw the new 1.5.0 >> release, but I see some problems in the code when trying to integrate it >> into my application (for example, the url constants in ClientConfig >> still don't use https, and that is causing errors.) Also, it seems like >> the project can benefit from using maven to compile with the sheer >> amount of dependencies (indeed, the AWS SDK uses maven.) >> >> I'd love to help with this SDK instead of just working on my own >> separately, since I use MTurk from Java on a regular basis and it would >> be great to join the effort. Hope this message gets to someone! >> >> Thanks, >> >> Andrew >> >> ------------------------------------------------------------------------------ >> >> This SF email is sponsosred by: >> Try Windows Azure free for 90 days Click Here >> http://p.sf.net/sfu/sfd2d-msazure >> _______________________________________________ >> Mturksdk-java-develop mailing list >> Mtu...@li... >> https://lists.sourceforge.net/lists/listinfo/mturksdk-java-develop > |
From: Chris M. <mo...@am...> - 2012-03-20 19:58:46
|
The Java SDK is still being maintained, and we intend on keeping it up-to-date with new API features. The 1.5.0 release was the first release in a long time, but it's not going to be our last. We do accept community contributions, and if you want to contribute, that would be fantastic! If you send us patches, we'll look them over, and they'll probably end up in the next version of the SDK. Maven is something we'd like to use to manage our dependencies, but switching to Maven hasn't been a really high priority. If this is something that you'd like to do, we'd gladly incorporate your work. We're aware of the ClientConfig issue, and we're planning on doing a bugfix release sometime soon. It sounded like you encountered multiple bugs -- do you have any other bugfixes that could go out with the release? Thanks for your help, Chris Mounce On 3/15/12 9:42 PM, Andrew Mao wrote: > Hi, > > I was wondering if there is still active development on this SDK, and > whether or not I could contribute to it. I have been rolling my own API > for a while and decided to switch to this one when I saw the new 1.5.0 > release, but I see some problems in the code when trying to integrate it > into my application (for example, the url constants in ClientConfig > still don't use https, and that is causing errors.) Also, it seems like > the project can benefit from using maven to compile with the sheer > amount of dependencies (indeed, the AWS SDK uses maven.) > > I'd love to help with this SDK instead of just working on my own > separately, since I use MTurk from Java on a regular basis and it would > be great to join the effort. Hope this message gets to someone! > > Thanks, > > Andrew > > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ > Mturksdk-java-develop mailing list > Mtu...@li... > https://lists.sourceforge.net/lists/listinfo/mturksdk-java-develop |
From: Andrew M. <mi...@gm...> - 2012-03-16 04:42:33
|
Hi, I was wondering if there is still active development on this SDK, and whether or not I could contribute to it. I have been rolling my own API for a while and decided to switch to this one when I saw the new 1.5.0 release, but I see some problems in the code when trying to integrate it into my application (for example, the url constants in ClientConfig still don't use https, and that is causing errors.) Also, it seems like the project can benefit from using maven to compile with the sheer amount of dependencies (indeed, the AWS SDK uses maven.) I'd love to help with this SDK instead of just working on my own separately, since I use MTurk from Java on a regular basis and it would be great to join the effort. Hope this message gets to someone! Thanks, Andrew |
From: Mark C. <mar...@gm...> - 2007-10-05 18:04:12
|