Unlikely.  I really think we should be pushing snapshots through more
frequently anyway.  The codebase changes pretty quickly, but the snapshots
have languished for a couple months.

It'd be nice to tie this in with the CI server.  Does anyone know if Brett
made any progress on that?

-- 
Kevin


On 10/8/07 3:50 PM, "Andrus Adamchik" <[EMAIL PROTECTED]> wrote:

> I guess nothing bad would happen if I push the current trunk snapshot
> over to the Maven snapshot repo?
> 
> I'll try to do it tomorrow morning.
> 
> Andrus
> 
> 
> Begin forwarded message:
>> From: "Edward Mostrom (JIRA)" <[email protected]>
>> Date: October 8, 2007 10:42:50 PM GMT+03:00
>> To: [EMAIL PROTECTED]
>> Subject: [JIRA] Commented: (CAY-873) maven-cayenne-plugin requires
>> transitive deps declared
>> 
>> 
>>     [ https://issues.apache.org/cayenne/browse/CAY-873?
>> page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
>> tabpanel#action_12516 ]
>> 
>> Edward Mostrom commented on CAY-873:
>> ------------------------------------
>> 
>> I just switched over to 3.0.  Can we get a new cayenne-server
>> snapshot out there with the dependencies in the pom?
>> 
>>> maven-cayenne-plugin requires transitive deps declared
>>> ------------------------------------------------------
>>> 
>>>                 Key: CAY-873
>>>                 URL: https://issues.apache.org/cayenne/browse/CAY-873
>>>             Project: Cayenne
>>>          Issue Type: Bug
>>>          Components: Cayenne Core Library
>>>    Affects Versions: 3.0
>>>         Environment: Maven 2.0.6, Cayenne 3.0M1
>>>            Reporter: Andrus Adamchik
>>>            Assignee: Andrus Adamchik
>>>             Fix For: 3.0
>>> 
>>> 
>>> maven-cayenne-plugin "cgen" goal failed because of commons-
>>> collections and commons-logging missing. I thought those were
>>> transitive, but looks like they are not and need to be added to
>>> the plugin pom.
>> 
>> -- 
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>> 
>> 
> 

-- 


Reply via email to