Dan reported issues with the Swing client which look like regressions from the Axis-to-CXF migration. He's documenting some of the specifics in a Jira ticket right now.
Some of the basic stuff works fine: - login, search, ingest by single file, ingest by directory, purge object However, ingesting a duplicate object locks up the Swing client completely. The big question is does anyone feel this should delay the 3.6 release? Before answering, some points to consider: 1) The web (flash) client appears unaffected 2) We've marked the Swing client deprecated for years now 3) Even if we were to hold up the release, I don't have the sense that anyone is particularly interested in or capable of maintaining the Swing client Committers, please vote on whether you think the release should be delayed to address the Swing client issues. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Fedora-commons-developers mailing list Fedora-commons-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
