Tomcat support improvements
The 10.04 cycle saw a lot of improvements in usability for the tomcat6 package. What can we do now to better support the needs of users developing and deploying Tomcat in production ? Is there even better defaults that we should use ?
Blueprint information
- Status:
- Complete
- Approver:
- Jos Boumans
- Priority:
- Medium
- Drafter:
- Thierry Carrez
- Direction:
- Approved
- Assignee:
- Thierry Carrez
- Definition:
- Approved
- Series goal:
- Accepted for maverick
- Implementation:
- Implemented
- Milestone target:
- maverick-alpha-3
- Started by
- Thierry Carrez
- Completed by
- Thierry Carrez
Whiteboard
Status:
Completed.
Complexity:
maverick-alpha-3: 2
Work items for maverick-alpha-2:
Fix tomcat to respect the user defined in /etc/default/
Fix improper group write permission for /var/lib/
General directory permissions review: DONE
Merge back in Debian the libservlet2.5 transition already done in Ubuntu main: DONE
Work items for maverick-alpha-3:
Add debconf questions about user/group to run under: DONE
Add debconf questions about default JVM options: DONE
Rebase patch on 6.0.28-1, commit to Debian: DONE
Wait for debian upload, sync back to Ubuntu: DONE
Document how to package applications with tomcat6 -- http://
mathiaz review - 20100526:
- looks good to me.
jib review / 20100526:
* Suggested priority: 2
* Suggested Subcycle: Alpha3 - No rush and may be good work for Java head?
* Some work needs to happen in alpha2 (linked to a SRU that the support team asked for), see wi below -- ttx
* Given how intimate I am with the codebase, I prefer to lead this one (I already started working on the urgent items) --ttx
* "Hibernate migration to main" is a perfect spec for Java head, as it allows to see and touch Java packaging on a large number of packages (and bring expertise to cut down deps where needed) --ttx