Issues
- iTunesU trunk does not compile with Sakai 2.10 trunkITU-23Resolved issue: ITU-23Zhen Qian
- Upgrade itunesu-tool contrib Tool to use jsf 1.1_02ITU-22Resolved issue: ITU-22Zhen Qian
- itunesu tool throws exception with Tomcat7ITU-21Resolved issue: ITU-21Zhen Qian
- iTunesU needs profile to deploy under Sakai 2.9ITU-20Resolved issue: ITU-20
- unmappable character for encoding UTF-8 for internationally coded double quote symbols within java filesITU-19Resolved issue: ITU-19Zhen Qian
- add a folder to store itunesu-related scriptsITU-18Resolved issue: ITU-18Zhen Qian
- improve the batch delete process in iTunesU admin toolITU-17Resolved issue: ITU-17Zhen Qian
- ClassCastException error in various RSF based tools when handling alert messagesITU-16Resolved issue: ITU-16Zhen Qian
- provide a iTunesU Admin function to download iTunesU content for batch of site idsITU-15Resolved issue: ITU-15Zhen Qian
- NullPointerException in iTunesU toolITU-14Resolved issue: ITU-14Zhen Qian
- More flexible iTunesU credential/permission mappingITU-13
- Calculated target section mode for iTunesU course page copy jobITU-11
- Just-in-time iTunesU container hierarchy creationITU-10
- Eagerly cache iTunesU Course Page HandlesITU-9
- iTunesU Course Page delete-after-copy (i.e. move)ITU-8
- iTunesU Course Page copyITU-7
- Incorrect result from ITunesUServiceImpl.getITunesUCourseHandle() when matchIdentifier is not setITU-6Resolved issue: ITU-6Zhen Qian
- upgrade service call in iTunesU toolITU-5Resolved issue: ITU-5Zhen Qian
- add the ability to add Feed Group into site iTunes U pageITU-4Resolved issue: ITU-4Zhen Qian
- Fix dependencies of Sakai 2.6-compatible branch of iTunesUITU-3Resolved issue: ITU-3Zhen Qian
- Provide base pom with a <version> = 1.0-SNAPSHOTITU-2Resolved issue: ITU-2Anthony Whyte
- upgrade HttpClient 3.x to HttpClient 4.0ITU-1Resolved issue: ITU-1Zhen Qian
22 of 22
We couldn't connect to that issue
Make sure that this issue actually exists in that project. If it does, try again in a few minutes. If you still can't link to the issue, contact your Jira admin.