Tweaking pom.xml repository entry for abdera to remove stalled maven run issue

A number of people have reported that during Maven builds
the are 
lagging when Maven is trying to check for updates.

The solution for this is to comment out the abdera
repository entry so 
maven will use the pinned version.

The only person this will affect is Brian as he is doing
active work on 
the branch - but he can just remove the comment.

I'll be doing this change immediately.

---
Bear

Build and Release Engineer
Open Source Applications Foundation (OSAF)
bearosafoundation.org
http://www.osafoundation
.org

bearcode-bear.com
http://code-bear.com

PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822
40B3 CD29


_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

On 8/16/07, Mike <bearcode-bear.com> wrote:
> A number of people have reported that during Maven
builds the are
> lagging when Maven is trying to check for updates.
>
> The solution for this is to comment out the abdera
repository entry so
> maven will use the pinned version.
>
> The only person this will affect is Brian as he is
doing active work on
> the branch - but he can just remove the comment.
>
> I'll be doing this change immediately.

actually even the snapshot version should be coming from the
osaf
repository, as i've deployed jars incorporating some local
patches. so
we should be fine leaving the abdera repository commented
out.

now if only we could fix the ical4j problem that keeps maven
from
working in offline mode on the 0.8 branch... 
_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev