-
Suggestion
-
Resolution: Fixed
-
None
The idea is to modularise Crowd much further than it currently is and remove the poor dependency on crowd-core for our clients.
The end result should be an 'uber jar' that contains all maven modules that have to do with client integration, eg:
- crowd-intregration-osuser
- crowd-intregration-atlassian-user
- crowd-intregration-seraph
- crowd-intregration-fisheye
- crowd-intregration-acegi
- crowd-intregration-jive
And be combined into a single jar file: crowd-integration-client-1.3.jar
- relates to
-
CWD-453 Crowd core jar breaks in Grails, need a new slimmed-down client jar
- Closed
[CWD-767] Crowd's Client libraries should be slimmed down to a single JAR file containing all required classes for a Crowd Client
Workflow | Original: JAC Suggestion Workflow [ 3389189 ] | New: JAC Suggestion Workflow 3 [ 3629610 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1391741 ] | New: JAC Suggestion Workflow [ 3389189 ] |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Crowd Development Workflow v2 [ 272015 ] | New: Simplified Crowd Development Workflow v2 [ 1391741 ] |
Workflow | Original: Feature Request Workflow [ 173383 ] | New: Crowd Development Workflow v2 [ 272015 ] |
Workflow | Original: jira [ 121618 ] | New: Feature Request Workflow [ 173383 ] |
Component/s | Original: Distribution [ 11547 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
W00t! .... this has now been done. We can now do Java 5 in crowd-core
And our users only need one Crowd JAR file, happy days!