On 19 May 2012, at 19:15, Franklin, Matthew B. wrote:

> On 5/19/12 2:10 PM, "Scott Wilson" <[email protected]> wrote:
> 
>> On 19 May 2012, at 16:17, Franklin, Matthew B. wrote:
>> 
>>> Moving this to a discuss thread.  Sorry for polluting the VOTE thread.
>>> 
>>>> -----Original Message-----
>>>> From: Franklin, Matthew B. [mailto:[email protected]]
>>>> Sent: Saturday, May 19, 2012 10:54 AM
>>>> To: [email protected]
>>>> Subject: RE: [VOTE] Apache Wookie 0.10.0-incubating Release Candidate
>>>> 
>>>>> -----Original Message-----
>>>>> From: Franklin, Matthew B. [mailto:[email protected]]
>>>>> Sent: Thursday, May 17, 2012 9:59 AM
>>>>> To: [email protected]
>>>>> Subject: RE: [VOTE] Apache Wookie 0.10.0-incubating Release Candidate
>>>>> 
>>>>> I will review this today.  One suggestion, we probably should not use
>>>>> the
>>>> same
>>>>> version string for a canceled vote.  Maybe call it 0.10.1 or
>>>>> something else to
>>>>> ensure that there is no confusion.
>>>> 
>>>> Got a little behind; but, in reviewing the release yesterday I was
>>>> unable to
>>>> build the tag or the source tarball.  Since I can't build 0.9.2 or
>>>> trunk, I assume
>>>> this is something in my environment; but I want to be sure.  I am
>>>> getting the
>>>> error from ivy:
>>>> 
>>>> [ivy:resolve]              ::::::::::::::::::::::::::::::::::::::::::::::
>>>> [ivy:resolve]              ::          UNRESOLVED DEPENDENCIES         ::
>>>> [ivy:resolve]              ::::::::::::::::::::::::::::::::::::::::::::::
>>>> [ivy:resolve]              :: commons-logging#commons-logging;1.1.1:
>>>> configuration not found in commons-logging#commons-logging;1.1.1:
>>>> 'compile'. It was required from org.apache.wookie#wookie-parser;0.10.0-
>>>> incubating-SNAPSHOT runtime
>>>> [ivy:resolve]              ::::::::::::::::::::::::::::::::::::::::::::::
>>>> 
>>>> Anyone seen this before?
>> 
>> I think commons-logging 1.1.1 may not have been synched with maven
>> central as a search there doesn't turn anything up - its in repo1 however:
>> 
>> http://repo1.maven.org/maven2/commons-logging/commons-logging/1.1.1/common
>> s-logging-1.1.1.pom
> 
> I am new to ivy, but with Maven, as you know, you can point to a different
> repo in the POM.  Is there a comparable mechanism for Ivy?  

Yes, its configured in ant/ivysettings.xml

> Also, commons
> logging 1.1.1 is in my local maven repository cache.  Wouldn't ivy just
> use that?

OK, thats odd, yes it should use it.

> Is anyone else having this issue? I will try it on a different machine to
> be sure this isn't just with my machine.
> 
>> 
>>>> 
>>>>> 
>>>>>> -----Original Message-----
>>>>>> From: Scott Wilson [mailto:[email protected]]
>>>>>> Sent: Wednesday, May 16, 2012 7:05 AM
>>>>>> To: wookie-dev
>>>>>> Subject: [VOTE] Apache Wookie 0.10.0-incubating Release Candidate
>>>>>> 
>>>>>> This is the third incubator release for Apache Wookie, with the
>>>>>> artifacts
>>>> being
>>>>>> versioned as 0.10.0-incubating.
>>>>>> 
>>>>>> We are requesting a vote via wookie-dev for the release of the
>>>>>> artifacts in
>>>>> the
>>>>>> first instance found here...
>>>>>> 
>>>>>> http://people.apache.org/builds/incubator/wookie/0.10.0-incubating/
>>>>>> 
>>>>>> ...as the final 0.10.0-incubating release.
>>>>>> 
>>>>>> PGP release keys (signed using 6F30516D):
>>>>>> 
>>>>>> http://www.apache.org/dist/incubator/wookie/KEYS
>>>>>> 
>>>>>> Additionally there are 3 sets of maven artifacts, which we hope will
>>>>>> help
>>>>>> others to integrate WOOKIE into their own applications. These are...
>>>>>> 
>>>>>> 1. Wookie itself as a downloadable WAR
>>>>>> 2. The W3C parser
>>>>>> 3. The Java connector framework
>>>>>> 
>>>>>> These artifacts are now in the staging area found here...
>>>>>> 
>>>>>> https://repository.apache.org/content/repositories/orgapachewookie-
>>>> 094/
>>>>>> 
>>>>>> Please take the time to verify the artifacts before casting your
>>>>>> vote.
>>>>>> 
>>>>>> Vote will be open at least 72 hours but until we receive most of the
>>>>>> committers votes.
>>>>>> 
>>>>>> [ ] +1  approve
>>>>>> [ ] +0  no opinion
>>>>>> [ ] -1  disapprove (and reason why)
>>>>> 
>>>> 
>>> 
>> 
> 

Reply via email to