Hi Seb,
I have the feeling something is going wrong on Gump, running classes
still import org.apache.commons.collections.FastHashMap that in /trunk
is not more used.
I suspect some update didn't work :(
You can see this because tests fail, like [1] and [2].
Can you help me please? Many thanks in advance,
Simo

[1] 
http://vmgump.apache.org/gump/public/apache-commons/commons-digester/gump_file/TEST-org.apache.commons.digester.BeanPropertySetterRuleTestCase.xml.html
[2] 
http://vmgump.apache.org/gump/public/apache-commons/commons-digester/gump_file/TEST-org.apache.commons.digester.plugins.TestLocalRules.xml.html

http://people.apache.org/~simonetripodi/
http://www.99soft.org/



On Sat, Sep 11, 2010 at 4:19 PM, sebb <seb...@gmail.com> wrote:
> On 11 September 2010 15:04, Simone Tripodi <simone.trip...@gmail.com> wrote:
>> thanks a lot, very appreciated!!! Gump just notified a failure, it
>> will be much more easier understanding why it failed!
>
> Unfortunately that run was started after I made the change, so you
> will have to wait for the next run.
>
>> thanks again, have a nice day,
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Sat, Sep 11, 2010 at 3:54 PM, sebb <seb...@gmail.com> wrote:
>>> On 11 September 2010 08:49, Simone Tripodi <simone.trip...@gmail.com> wrote:
>>>> Hi Phil,
>>>> very very appreciated, believe me that problem didn't let me sleep!!! :)
>>>> Since tag and install steps have been done, I'll try to continue with
>>>> scp using the approach you just suggested...
>>>>
>>>> BTW in the meanwhile, even if I didn't change any single line of code
>>>> on /trunk, Gump nicely reported tests error, so I think I've to fix
>>>> the build first before calling an RC1
>>>
>>> I've added a <report> tag to the digester Gump build which hopefully
>>> will give access to the Surefire reports after the next Gump run.
>>>
>>>> Thanks a lot, have a nice day,
>>>> Simo
>>>>
>>>> http://people.apache.org/~simonetripodi/
>>>> http://www.99soft.org/
>>>>
>>>>
>>>>
>>>> On Sat, Sep 11, 2010 at 3:15 AM, Phil Steitz <phil.ste...@gmail.com> wrote:
>>>>> On 9/10/10 6:27 PM, Simone Tripodi wrote:
>>>>>>
>>>>>> Hi all guys,
>>>>>> the RC1 is driving me crazy... once resolved the gpg issues, following
>>>>>> the wiki guide[1] Rahul ans Seb suggested, once launched "mvn -Prc
>>>>>> release:perform" when going to deploy artifacts, the build was
>>>>>> blocked:
>>>>>>
>>>>>> [INFO] [INFO] [deploy:deploy {execution: default-deploy}]
>>>>>> [INFO]
>>>>>> [INFO]
>>>>>> [INFO] Note that too many successive login failures will result in 
>>>>>> further
>>>>>> [INFO] logins from your IP address being blocked. If this happens, 
>>>>>> contact
>>>>>> [INFO]<infrastruct...@apache.org>, mentioning your IP address so that it
>>>>>> can
>>>>>> [INFO] be unblocked.
>>>>>> [INFO]
>>>>>> [INFO]
>>>>>>
>>>>>> Even if I try to insert my apache password, nothing happens, the
>>>>>> process seems to be suspended... any idea/hints on it?
>>>>>> Many thanks in advance,
>>>>>> Simo
>>>>>>
>>>>>> [1] http://wiki.apache.org/commons/CreatingReleases
>>>>>>
>>>>>> http://people.apache.org/~simonetripodi/
>>>>>> http://www.99soft.org/
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>>>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>>>>
>>>>>
>>>>> If you don't mind a slightly lower-tech approach, the process documented 
>>>>> on
>>>>> the web page [1] works.  I just used it for the [pool] release.  There is 
>>>>> a
>>>>> bash script that automates most of the steps in pool trunk [2], though the
>>>>> steps are pretty simple.  Personally, I think the lack of control and
>>>>> generally flaky behavior of maven release automation is not worth the
>>>>> trouble.  I just use
>>>>>  mvn -Prc -DcreateChecksum=true install
>>>>> to create the artifacts and then deploy them using scp (which you end up
>>>>> having to do in the end to /dist even with the release plugin approach).
>>>>>  The advantages of this approach are 1) it is clear what is happening at
>>>>> each stage 2) tags don't change 3) what we vote on is what gets deployed 
>>>>> 4)
>>>>> it works reliably.
>>>>>
>>>>> [1] http://commons.apache.org/releases/index.html
>>>>> [2] http://svn.apache.org/repos/asf/commons/proper/pool/trunk/pool-RC.sh
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to