This is an automated email from the ASF dual-hosted git repository.
rombert pushed a change to branch issue/SLING-12354
in repository
https://gitbox.apache.org/repos/asf/sling-slingfeature-maven-plugin.git
omit 65988ed SLING-12354 - Set sling.java.version to 11
add 5bf5dc0 SLING-12173 - Configuration errors in Eclipse for projects
using the slingfeature-maven-plugin (#83)
add c06ee30 [maven-release-plugin] prepare release
slingfeature-maven-plugin-1.8.2
add 771d9b4 [maven-release-plugin] prepare for next development iteration
add 218785e SLING-12355 - Use the TemporaryFolder JUnit rule instead of
manually managing temp directories (#86)
add b37311e SLING-12354 - Set sling.java.version to 11
add 14b5187 SLING-12353 - The AnalyserMetadataHandler is executed too
often
add 964dbd8 SLING-12353 - The AnalyserMetadataHandler is executed too
often
add 7fb7717 SLING-12354 - Set sling.java.version to 11
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (65988ed)
\
N -- N -- N refs/heads/issue/SLING-12354 (7fb7717)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
pom.xml | 18 +-
.../feature/maven/mojos/AggregateFeaturesMojo.java | 36 +-
.../maven/mojos/AggregateFeaturesMojoTest.java | 553 +++++++--------------
.../maven/mojos/ExtractExtensionsMojoTest.java | 37 +-
.../maven/mojos/FeatureLauncherMojoTest.java | 15 +-
5 files changed, 240 insertions(+), 419 deletions(-)
