Actually turns out that it was part of the funkiness and a file that was auto-generated by Archiva. The files that I was uploading to our "internal" repository had the file name of SNAPSHOT in them (even though the repo allowed snapshots). I have since split it up appropriately so that anything with SNAPSHOT is in the snapshot repo and anything release is in the "internal" repo.
Again, more funkiness from upgrading from 1.3.6 to 2.0.1. I have it all sorted out now and everything is working correctly (as far as I can tell). On Tue, Apr 22, 2014 at 5:11 PM, Olivier Lamy <[email protected]> wrote: > Is resolver.properties part of the files you want to upload? > > > On 23 April 2014 02:37, Jared Griffith <[email protected]> wrote: > > I'm getting exception errors when trying to upload artifacts about > > resolver.properties file not being named correctly. When trying to check > > the artifacts tab on the artifact that I uploaded, I get an error "An > error > > has happened you must contact the administrator to check the logs. " and > in > > the logs is this: http://pastebin.com/RWkBKTZ0 > > > > Any help would be great. > > > > > > > > -- > > > > Jared Griffith > > Linux Administrator, PICS Auditing, LLC > > P: (949) 936-4574 > > C: (909) 653-7814 > > > > <http://www.picsauditing.com> > > > > 17701 Cowan #140 | Irvine, CA | 92614 > > > > Join PICS on LinkedIn and Twitter! > > > > <https://twitter.com/PICSAuditingLLC> > > > > -- > Olivier Lamy > Ecetera: http://ecetera.com.au > http://twitter.com/olamy | http://linkedin.com/in/olamy > -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 <http://www.picsauditing.com> 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! <https://twitter.com/PICSAuditingLLC>
