Skip to content

Conversation

@ghost
Copy link

@ghost ghost commented May 9, 2016

No description provided.

@simboss
Copy link
Member

simboss commented May 10, 2016

Can we have some background info for this change?

@ghost
Copy link
Author

ghost commented May 10, 2016

Sure,
I'm trying to use geoserver-manager in a customer project build using wavemaker. The actual version (1.5.11) is incompatible with WaveMaker version (1.7.x). On your side this means only a version upgrade. No code is changed.
The same problem happens with other various libs.

@ccancellieri
Copy link
Contributor

Dear Federico,
Take the time to check out the dependency exclusions provided by maven2-3.
Cheers,
Carlo
Il 10/Mag/2016 13:02, "Federico Guizzardi" notifications@github.com ha
scritto:

Sure,
I'm trying to use geoserver-manager in a customer project build using
wavemaker. The actual version (1.5.11) is incompatible with WaveMaker
version (1.7.x). On your side this means only a version upgrade. No code is
changed.
The same problem happens with other various libs.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#193 (comment)

@simboss
Copy link
Member

simboss commented May 10, 2016

I second what carlo said, although I am not against this update, I don't see it as high priority.

@ghost
Copy link
Author

ghost commented May 11, 2016

As you wish.
Actually, I'm using my fork with this patch for all my projects, so it no urgent. I only want to share what I do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants