kepler bump to m2e 1.4.0 #3
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
nobody interested to merge this and release an updated version of the connector? Might be also interesting to support m2e 1.5 now. |
|
+1 would be nice to have this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As M2E has been bumped to 1.4.0 with Kepler release I redid the changes of pull request #2 , bumping this time to 1.4.0 versions.
I also manually updated Eclipse 3.6 target to a 4.2 one because of some issues in 1.6.2 slf4j dependency coming from m2e and not found.
Tests fail halfway inside ckpackager plugin, with some error regarding maven-dependency-copy to an existing target folder (which sounds superficially similar to comments in the last pull request).
I hope this is useful or helps :)