On Thu, Dec 3, 2009 at 8:07 AM, Edwin Shin <[email protected]> wrote:
> Can we safely remove
>  - org/fedoracommons

Akubra 0.2 was released last week, with a new groupId.  This
previously housed the Akubra 0.1 release, but it should be ok to get
rid of....along with org/apache in thirdparty (that held a version of
derby only used by Akubra 0.1).  I'm ok with getting rid of these
since now since 0.2 is now released, and I've also just made backups
of these directories in the release-archive.  Lets get them out of the
maven repo.

>  - org/fedorarepo

Asger's fcrepo-579 branch is the only active one that's still using
the old groupId... I figured we could wait on deleting the old copy of
the libs from the m2 repo till that branch gets merged (so it's still
buildable on a machine with an empty .m2/repository) ..but if Asger
says it's ok, I'm fine with it.

- Chris

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing. 
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Fedora-commons-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers

Reply via email to