+1 to blow away the snapshots area. I don't see any reason to keep around old snapshots of versions that were released and if they are not going to be released they should not be there.
On Mon, Jan 18, 2016 at 10:53 AM, Timothy Bish <tabish...@gmail.com> wrote: > We seem to have a bit of a mess in our snapshots area with lots of old > snapshots for ancient releases like 5.3, 5.4, etc along with snapshots > for an ActiveMQ 6.0.0 release that has caused some confusion recently. > > Some examples of old snapshots or snapshot to things that were never > released. > > > https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/ > > https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/ > > https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/ > > https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/ > > https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/ > > We can request that infra wipe out the snapshots area and let the > jenkins runs repopulate with only the current builds for active project > work. Alternatively we can go through every folder and audit them but > given they are snapshots it's simpler just to blow them all away. > > Thoughts? > > -- > Tim Bish > twitter: @tabish121 > blog: http://timbish.blogspot.com/ > > >
