Skip to content

Commit

Permalink
Log skipped TargetEnvironments only in debug
Browse files Browse the repository at this point in the history
This info is not helpful in majority of cases as setting a platform
filter in the manifest is an explicit action which the developer does so
there is no need to be reminded of that at the very beginning of the
build where Maven usually gives warnings like missing plugin versions
and etc. that makes it quite often considered as potential problem.
Log in debug mode instead.
  • Loading branch information
akurtakov committed Jan 12, 2024
1 parent 178782d commit bf634db
Showing 1 changed file with 8 additions and 8 deletions.
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
/*******************************************************************************
* Copyright (c) 2008, 2022 Sonatype Inc. and others.
* Copyright (c) 2008, 2024 Sonatype Inc. and others.
* This program and the accompanying materials
* are made available under the terms of the Eclipse Public License 2.0
* which accompanies this distribution, and is available at
Expand Down Expand Up @@ -333,10 +333,10 @@ private void setBREEHeaderSelectionPolicy(TargetPlatformConfiguration result, Xp

/**
* Take the constraints of the configured execution environment into account when resolving
* dependencies or target definitions. These constraints include the list of system packages and
* the <tt>Bundle-RequiredExecutionEnvironment</tt> header. When set to <code>true</code>, the
* dependency resolution verifies that the bundle and all required bundles can be used in an
* OSGi container with the configured execution environment.
* dependencies or target definitions. These constraints include the list of system packages and the
* <tt>Bundle-RequiredExecutionEnvironment</tt> header. When set to <code>true</code>, the
* dependency resolution verifies that the bundle and all required bundles can be used in an OSGi
* container with the configured execution environment.
*/
private void setResolveWithEEContraints(TargetPlatformConfiguration result, Xpp3Dom resolverDom) {
String value = getStringValue(resolverDom.getChild(RESOLVE_WITH_EXECUTION_ENVIRONMENT_CONSTRAINTS));
Expand Down Expand Up @@ -384,7 +384,7 @@ private void addTargetEnvironments(TargetPlatformConfiguration result, MavenProj
}
}
if (!skipped.isEmpty()) {
logger.info(MessageFormat.format(
logger.debug(MessageFormat.format(
"Declared TargetEnvironment(s) {0} are skipped for {1} as they do not match the project filter {2}.",
skipped.stream().map(TargetEnvironment::toFilterProperties).map(String::valueOf)
.collect(Collectors.joining(", ")),
Expand Down Expand Up @@ -594,9 +594,9 @@ private static String getStringValue(Xpp3Dom element) {
*
* @param project
* @param targetFile
* the target file to check
* the target file to check
* @param otherTargetFiles
* other target files to take into account
* other target files to take into account
* @return <code>true</code> if the target file is the primary artifact, <code>false</code>
* otherwise
*/
Expand Down

0 comments on commit bf634db

Please sign in to comment.