The latest from the main geomesa github repo (just pulled from the 
master branch) builds with 1.0.0-rc.2-SNAPSHOT as the version tag, 
though, not 1.0.0-rc.2?
Here's my local maven repo contents (empty for -rc.2, builds for 
rc.2-SNAPSHOT)
*➜  ~  ls 
~/.m2/repository/org/locationtech/geomesa/geomesa-core-accumulo1.5*
1.0.0-rc.2  1.0.0-rc.2-SNAPSHOT  1.0.0-SNAPSHOT  maven-metadata-local.xml
*➜  ~  ls 
~/.m2/repository/org/locationtech/geomesa/geomesa-core-accumulo1.5/1.0.0-rc.2*
geomesa-core-accumulo1.5-1.0.0-rc.2.pom.lastUpdated
*➜  ~  ls 
~/.m2/repository/org/locationtech/geomesa/geomesa-core-accumulo1.5/1.0.0-rc.2-SNAPSHOT*
geomesa-core-accumulo1.5-1.0.0-rc.2-SNAPSHOT.jar 
 geomesa-core-accumulo1.5-1.0.0-rc.2-SNAPSHOT-tests.jar 
 _maven.repositories
geomesa-core-accumulo1.5-1.0.0-rc.2-SNAPSHOT.pom 
 maven-metadata-local.xml  resolver-status.properties
On Thu, Jan 15, 2015 at 3:36 PM, Hunter Provyn <fhp@xxxxxxxx 
<mailto:fhp@xxxxxxxx>> wrote:
    Mike,
    You are welcome.
    The geomesa URL is right but it shouldn't be looking for geotools
    on repo.locationtech.org <http://repo.locationtech.org>.
    Our local artifactory resolves these dependencies for us based on
    the artifact name.
    Maybe there is a configuration problem with your artifactory?
    Hunter
    On 01/15/2015 02:41 PM, Mike Atlas wrote:
        Thanks for the update Hunter. It seems maven doesn't like the
        locationtech repo? I can run wget on all the .pom URIs in the
        output below, so my machine can definitely reach these files
        over the network just fine.
        [INFO] Scanning for projects...
        [INFO]
        [INFO]
        ------------------------------------------------------------------------
        [INFO] Building GeoMesa GDELT 1.0-SNAPSHOT
        [INFO]
        ------------------------------------------------------------------------
        Downloading:
        https://repo.locationtech.org/content/repositories/releases/org/locationtech/geomesa/geomesa-core-accumulo1.5/1.0.0-rc.2/geomesa-core-accumulo1.5-1.0.0-rc.2.pom
        Jan 15, 2015 7:35:46 PM
        org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultHttpClient
        tryExecute
        INFO: I/O exception
        (org.apache.maven.wagon.providers.http.httpclient.NoHttpResponseException)
        caught when processing request: The target server failed to
        respond
        Jan 15, 2015 7:35:46 PM
        org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultHttpClient
        tryExecute
        INFO: Retrying request
        Downloading:
        https://repo.locationtech.org/content/repositories/releases/org/geotools/gt-opengis/11.2/gt-opengis-11.2.pom
        Jan 15, 2015 7:35:49 PM
        org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultHttpClient
        tryExecute
        INFO: I/O exception
        (org.apache.maven.wagon.providers.http.httpclient.NoHttpResponseException)
        caught when processing request: The target server failed to
        respond
        Jan 15, 2015 7:35:49 PM
        org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultHttpClient
        tryExecute
        Thanks in advance,
        Mike
        On Thu, Jan 15, 2015 at 1:30 PM, Hunter Provyn <fhp@xxxxxxxx
        <mailto:fhp@xxxxxxxx> <mailto:fhp@xxxxxxxx
        <mailto:fhp@xxxxxxxx>>> wrote:
            Hi Mike,
            Thanks for bringing this to our attention!
            I have updated GeoMesa-gdelt and the project builds for me
        now.
            Please let us know if you have further problems.
            Hunter
                -------- Forwarded Message --------
                Subject:        [geomesa-users] getting dependencies
        right for
                geomesa-gdelt sample
                Date:   Thu, 15 Jan 2015 11:24:17 -0500
                From:   Mike Atlas <mike@xxxxxxx <mailto:mike@xxxxxxx>
        <mailto:mike@xxxxxxx <mailto:mike@xxxxxxx>>>
                Reply-To:       Geomesa User discussions
                <geomesa-users@xxxxxxxxxxxxxxxx
        <mailto:geomesa-users@xxxxxxxxxxxxxxxx>
                <mailto:geomesa-users@xxxxxxxxxxxxxxxx
        <mailto:geomesa-users@xxxxxxxxxxxxxxxx>>>
                To: geomesa-users@xxxxxxxxxxxxxxxx
        <mailto:geomesa-users@xxxxxxxxxxxxxxxx>
                <mailto:geomesa-users@xxxxxxxxxxxxxxxx
        <mailto:geomesa-users@xxxxxxxxxxxxxxxx>>
                Hi all,
                Has anyone successfully built the geomesa-gdelt
               
        <http://www.geomesa.org/2014/04/17/geomesa-gdelt-analysis/>
                sample project? I'm having trouble with the dependencies
                <https://github.com/geomesa/geomesa-gdelt/issues/2>Â
        not being
                found at all, and even when forcing them by editing
        pom.xml,
                things still don't quite work. One assumption is that
        GeoTools
                is available (in the class path?) but not specified in the
                project, for example. Other issues seem to be around
        whether
                the version name contains the "RC-2/3" string within it.
                I'm able to build geomesa itself using maven just
        fine, however.
                I also tried to build both projects in Eclipse (Luna, with
                Maven and Scala plugins installed) but without much
        luck and
                far more errors as well... Â errors such as "can't expand
                macros compiled by previous versions of
                ScalaGeoHashTest.scala/geomesa-utils
        accumulo1.5/src/test/scala/org/locationtech/geomesa/utils/geohash).
                Besides decomposing the original pom.xml and attempting to
                rebuild this project from scratch, does anyone have
        any tips
                they might have to get this built? I have to confess
        that I'm
                not from the Java/Scala world, so I may be missing some
                foundational concepts about where dependencies should
        live or
                be referenced when using maven/pom.xml filesÂ
                Thanks,
                Mike