Hi Mark-

Thank you for your attention to this matter.

I do not rebase SD Geode on Apache Geode 1.2.0 build snapshots (
1.2.0-SNAPSHOT) until I release SD Geode 1.1.0.RELEASE based on Apache
Geode 1.1.0 (release).

2 things...

1. Because Apache infra deletes (build) snapshots after a release (which I
would say is a questionable practice, actually), the *Spring* team has
created a geode-snapshot (cache)
<https://repo.spring.io/webapp/#/artifacts/browse/tree/General/geode-snapshot>
[1]
in the *Spring* Artifactory (repo) server.

Currently the SD Geode Nightly build is not picking up these "cached" geode
snapshots from [1] because the SD Geode POM is incorrect and pointed at the
wrong *Spring* repo currently
<https://github.com/spring-projects/spring-data-gemfire/blob/apache-geode/pom.xml#L34-L37>
[2]
(i.e. libs-milestone and not libs-snapshot as it should); my mistake.

2. Regardless of #1, I have already based SD Geode on Apache Geode 1.1.0
(release).  I have just not checked in yet as I am currently in the middle
of wrapping up *Lucene Index/Search* support in SD Geode.

I am hoping to have this finished EOD today.

Thanks,
John


[1]
https://repo.spring.io/webapp/#/artifacts/browse/tree/General/geode-snapshot
[2]
https://github.com/spring-projects/spring-data-gemfire/blob/apache-geode/pom.xml#L34-L37


On Thu, Feb 23, 2017 at 12:13 PM, Mark Bretl <mbr...@apache.org> wrote:

> John,
>
> It looks like this is failing because it can't find the
> geode-*-1.1.0-SNAPSHOT.jars. As 1.1.0 has been released, we have removed
> these jars. Next version is currently 1.2.0(-SNAPSHOT).
>
> Would you or someone else be able to update this job?
>
> Thanks,
>
> --Mark
>
>
> On Thu, Feb 23, 2017 at 11:51 AM, Spring CI <c...@spring.io> wrote:
>
>>
>> -----------------------------------------------------------------------
>> Spring Data GemFire > Nightly-ApacheGeode > #481 failed.
>> -----------------------------------------------------------------------
>> This was manually triggered by Trevor Marshall.
>> No failed tests found, a possible compilation error.
>>
>> https://build.spring.io/browse/SGF-NAG-481/
>>
>> ---------------------
>> Currently Responsible
>> ---------------------
>>
>> No one is responsible for fixing this build.
>>
>>
>>
>> --------------
>> Failing Jobs
>> --------------
>>   - Default Job (Default Stage): No tests found.
>>
>>
>>
>>
>> --
>> This message is automatically generated by Atlassian Bamboo
>
>
>


-- 
-John
john.blum10101 (skype)

Reply via email to