Permalink
Commits on May 23, 2014
  1. Add alternative credential strategies to documentation

    Previously the documentation only described passing credential
    information via the ~/.m2/settings.xml file.  The code however,
    supported additional strategies that were undocumented.  This change
    adds the documentation for those alternative strategies.
    
    [resolves #21]
    nebhale committed May 23, 2014
Commits on Apr 9, 2014
  1. Merge branch 'lalyos-patch-1'

    nebhale committed Apr 9, 2014
  2. Update README to describe public s3 bucket policy

    The automatic setting of a public-read ACL for each artifact is
    removed in: https://github.com/spring-projects/aws-
    maven/commit/2ece0db9b0f381a8800441e9c64b8fcb72d0415e
    
    If somebody needs the old behaviour, needs to set a bucket policy. The
    provided script automates the process. see issues:
    
    * #6
    * #8
    * #19
    
    [resolves #20]
    lalyos committed with nebhale Apr 8, 2014
Commits on Mar 31, 2014
Commits on Mar 30, 2014
Commits on Feb 17, 2014
  1. Credential Provider Chain

    This change adds support for a CredentialProviderChain.  This enables
    a tiered lookup of credential locations.
    
    [Complete #9]
    nebhale committed Feb 17, 2014
  2. Do not set ACL

    Previously, the ACL of each artifact and directory was set explicitly
    without the ability to override it.  This caused problems in certain
    environments and wasn't wanted any longer in the 5.x line.  This
    change removes that explicit configuration in lieu of using bucket
    policies.
    
    [Completes #6][Completes #8]
    nebhale committed Feb 17, 2014
  3. Java 7 minimum

    Since Java 6 does not have the proper CAs to handle S3's SSL
    certificates, there's no longer any need to support Java 6.  This
    change updates the minimum supported Java to Java 7.
    nebhale committed Feb 17, 2014
  4. Merge branch 'jmena-master'

    nebhale committed Feb 17, 2014
  5. Use password instead of passphrase

    Previously, the aws-maven wagon used the username and passphrase
    facilities in the wagon API to contribute credentials.  At some point,
    the implementation of the API changed such that it was no longer
    possible to use that pairing together.  This change updates the wagon
    to use username and password now, which can be used together.
    
    [#14]
    jmena committed with nebhale Oct 19, 2013
  6. Rename test files

    In an attempt to slim down the POM file, I removed some custom
    configuration of the Maven surefire plugin.  This causes the custom-
    named tests to not run.  This change updates the names of the tests to
    be standard.
    nebhale committed Feb 17, 2014
  7. Restart development

    After a period of inactivity, this commit starts active development up
    again.  Most of the changes are centered around working in IDEA,
    copyrights, and formatting.
    nebhale committed Feb 17, 2014
Commits on Jun 17, 2013
  1. Merge branch '4.x'

    nebhale committed Jun 17, 2013
  2. Add link to versions

    Previously, there was no way to determine the latest version of the
    wagon from the main documentation page.  This changes adds a link to
    the complete listing of versions in Maven Central.
    
    [Finishes #11]
    nebhale committed Jun 17, 2013
Commits on May 16, 2013
  1. Merge branch '4.x'

    nebhale committed May 16, 2013
Commits on May 2, 2013
  1. Merge branch '4.x'

    nebhale committed May 2, 2013
  2. Add support for eu-west-1

    Previously the wagon could not be used to access buckets with a
    location constraint of eu-west-1 (issue #7).  However, it was able to
    access buckets with a location constraint of EU.  According to the
    Amazon documentation[1], EU is the 'official' S3 location constraint
    for the Ireland datacenter.  The truth however, is that both eu-west-1
    and EU are valid S3 location constraints for it. For example, when a
    bucket is created with the AWS console[2], the bucket is assigned the
    eu-west-1 location constraint.  However, when the bucket is created
    using some other tools (for example, Transmit[3]), the bucket is
    assigned the EU location constraint.  This is not documented anywhere,
    and notably, the location constraint for the northern Virgina
    datacenter must be US and cannot be us-east-1.
    
    This change adds support for buckets with an eu-west-1 location
    constraint.  It also adds support for buckets with a us-gov-west-1
    location constraint (GovCloud), but does not test that this
    functionality works.  At this time, it is not possible to create a
    test bucket in GovCloud so there are no tests that verify the
    functionality.
    
    [1]: http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region
    [2]: http://console.aws.amazon.com
    [3]: http://panic.com/transmit/
    [4]: http://aws.amazon.com/govcloud-us/
    nebhale committed May 2, 2013
  3. Version updates

    As it is good hygiene to stay up to date with versions, this change
    updates the amazonaws and logback versions.
    nebhale committed May 2, 2013
Commits on Apr 17, 2013
  1. Merge branch '4.x'

    nebhale committed Apr 17, 2013
  2. Merge branch '4.x'

    nebhale committed Apr 17, 2013
  3. Merge branch '4.x'

    nebhale committed Apr 17, 2013
  4. More pom.xml polishing

    nebhale committed Apr 17, 2013
  5. Merge branch '4.x'

    nebhale committed Apr 17, 2013
  6. Version updates

    nebhale committed Apr 17, 2013
Commits on Mar 8, 2013
  1. Merge branch '4.x'

    Conflicts:
    	pom.xml
    nebhale committed Mar 8, 2013
  2. Merge branch '4.x'

    nebhale committed Mar 8, 2013
  3. Merge branch 'sonar' into 4.x

    nebhale committed Mar 8, 2013
  4. Sonar fixes

    Fixes for sonar violations
    nebhale committed Mar 8, 2013