hazelcast-wm >= 3.3 OSGI Manifest spring package imports should not be required #6072

Closed
fwassmer opened this Issue Aug 27, 2015 · 3 comments

Projects

None yet

4 participants

@fwassmer
Contributor

Starting with hazelcast-wm 3.3.0 spring packages are imported and required in the Manifest.mf,
so hazlecast-wm can only be started when spring is also installed:

org.springframework.context;version="[3.1,4)",
org.springframework.security.core.session;version="[3.1,4)",
org.springframework.security.web.session;version="[3.1,4)",
org.springframework.web.context;version="[3.1,4)",
org.springframework.web.context.support;versio n="[3.1,4)"

Those dependencies should be set to be optional with resolution:=optional
in the pom ( <Import-Package>... ):
e.g.: org.springframework.context;version="[3.1,4)";resolution:=optional

@bilalyasar
Collaborator

@fwassmer yes your findings seems logical. If you want, you can create PR about this issue..

@bilalyasar bilalyasar added this to the 3.6 milestone Aug 27, 2015
@fwassmer
Contributor

PR created: #6073

@serkan-ozal
Contributor

closed via #6073

@serkan-ozal serkan-ozal closed this Sep 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment