-
Suggestion
-
Resolution: Fixed
-
None
-
Using Tomcat 5.5, JDK 6 on Solaris 10
The core Crowd jar seems to have much more in it than is required to integrate a client. In particular, the hibernate mapping file at the root of the jar (which is unnecessary in making a client) gets picked up by Grails when included in a Grails project and Grails tries to create Hibernate domain objects for the listed mappings. Removing the hibernate mapping file from the jar works, but I think it would be nice to have a seperate, slimmed down Crowd-client.jar which only has what is required to get a client running.
More work, I know, but it would be nice...
Also, requirements for client integration are sparse, but that is addressed elsewhere.
- is related to
-
CWD-767 Crowd's Client libraries should be slimmed down to a single JAR file containing all required classes for a Crowd Client
- Closed
[CWD-453] Crowd core jar breaks in Grails, need a new slimmed-down client jar
Workflow | Original: JAC Suggestion Workflow [ 3389178 ] | New: JAC Suggestion Workflow 3 [ 3630427 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1392719 ] | New: JAC Suggestion Workflow [ 3389178 ] |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Crowd Development Workflow v2 [ 272757 ] | New: Simplified Crowd Development Workflow v2 [ 1392719 ] |
Workflow | Original: Feature Request Workflow [ 173943 ] | New: Crowd Development Workflow v2 [ 272757 ] |
Workflow | Original: jira [ 84848 ] | New: Feature Request Workflow [ 173943 ] |
Fix Version/s | New: 1.3 [ 13422 ] | |
Assignee | Original: Justen Stepka [Atlassian] [ justen.stepka@atlassian.com ] | New: Justin Koke [ justin@atlassian.com ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |