This repository has been archived by the owner on Oct 11, 2024. It is now read-only.
Maven 206 - enable correct jdk version guessing in liferay children builds #18
Conversation
This file contains 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 stated in https://issues.liferay.com/browse/MAVEN-206, current build-css target can fail if plugin dependencies imply profile activation by jdk version. In the original bug report, failure is triggered by a apache commons dependency.
Other failure can be triggerred by cxf code generation.
This fix, apart the version change, modify AbstractToolsLiferayMojo.java to cascade system and user properties.