Skip to content

Added deploy to S3 option+repo#316

Merged
chrisbennight merged 1 commit intomasterfrom
GEOWAVE-315
Apr 10, 2015
Merged

Added deploy to S3 option+repo#316
chrisbennight merged 1 commit intomasterfrom
GEOWAVE-315

Conversation

@chrisbennight
Copy link
Copy Markdown
Contributor

@chrisbennight chrisbennight commented Apr 8, 2015

Other files are formatting auto-changes; only real change here is to the pom.xml

Added the following S3 based maven repos for geowave:

    <distributionManagement>
        <repository>
            <id>geowave-maven-releases</id>
            <name>GeoWave AWS Release Repository</name>
            <url>s3://geowave-maven/release</url>
        </repository>
        <snapshotRepository>
            <id>geowave-maven-snapshots</id>
            <name>GeoWave AWS Snapshot Repository</name>
            <url>s3://geowave-release/snapshot</url>
        </snapshotRepository>
    </distributionManagement>

mvn deploy will now push to releases or snapshots (based on if ${project.version} contains "SNAPSHOT" in the string).

The repo is publicly viewable, but in order to publish you need the access keys - you can put them in your ~/.m2/settings.xml - here is the skeleton fragment:

  <servers>
    <server>
      <id>geowave-maven-releases</id>
      <username>ACCESS_KEY_ID</username>
      <password>SECRET_ACCESS_KEY</password>
    </server>
    <server>
      <id>geowave-maven-snapshots</id>
      <username>ACCESS_KEY_ID</username>
      <password>SECRET_ACCESS_KEY</password>
    </server>
  </servers>

@chrisbennight
Copy link
Copy Markdown
Contributor Author

chrisbennight commented Apr 8, 2015

Issue: #315

@coveralls
Copy link
Copy Markdown

coveralls commented Apr 8, 2015

Coverage Status

Coverage decreased (-0.01%) to 32.86% when pulling 34591dc on GEOWAVE-315 into 4548763 on master.

@chrisbennight
Copy link
Copy Markdown
Contributor Author

chrisbennight commented Apr 9, 2015

Removed the fragments from the repositories tag (no point here) - we should add the location to the docs though - it's

        <repository>
            <id>geowave-maven-releases</id>
            <name>GeoWave AWS Release Repository</name>
            <url>http://geowave-maven.s3-website-us-east-1.amazonaws.com/release</url>
            <releases>
                <enabled>true</enabled>
            </releases>
            <snapshots>
                <enabled>false</enabled>
            </snapshots>
        </repository>
        <repository>
            <id>geowave-maven-snapshot</id>
            <name>GeoWave AWS Snapshot Repository</name>
            <url>http://geowave-maven.s3-website-us-east-1.amazonaws.com/snapshot</url>
            <releases>
                <enabled>false</enabled>
            </releases>
            <snapshots>
                <enabled>true</enabled>
            </snapshots>
        </repository>

@coveralls
Copy link
Copy Markdown

coveralls commented Apr 9, 2015

Coverage Status

Coverage decreased (-0.01%) to 32.86% when pulling 2d9cca1 on GEOWAVE-315 into 4548763 on master.

chrisbennight added a commit that referenced this pull request Apr 10, 2015
@chrisbennight
Merge pull request #316 from ngageoint/GEOWAVE-315
4b814ec 
Added deploy to S3 option+repo
@chrisbennight chrisbennight merged commit 4b814ec into master Apr 10, 2015
@chrisbennight chrisbennight deleted the GEOWAVE-315 branch April 10, 2015 01:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@chrisbennight @coveralls