Skip to content

Fix Java Configurator

0a34f9e
Select commit
Loading
Failed to load commit list.
Open

Fix Java Configurator #2114

Fix Java Configurator
0a34f9e
Select commit
Loading
Failed to load commit list.
Jenkins - M2E / Maven succeeded Dec 29, 2025 in 0s

No new issues, 63 total

Total New Outstanding Fixed Trend
63 0 63 1 👍

Reference build: m2e » main #111

Details

Severity distribution of all issues

Error Warning High Warning Normal Warning Low
0 0 63 0

Annotations

Check warning on line 440 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

bnd:bnd-process

NORMAL:
Raw output
<pre><code>/home/jenkins/agent/workspace/m2e_PR-2114/org.eclipse.m2e.maven.runtime/pom.xml [0:0]: Unused Export-Package instructions: [org.apache.maven.wagon.*] /home/jenkins/agent/workspace/m2e_PR-2114/org.eclipse.m2e.maven.runtime/pom.xml [0:0]: Export org.apache.maven.wagon.shared.http, has 9, private references [org.apache.http, org.apache.http.auth, org.apache.http.client, org.apache.http.client.config, org.apache.http.client.methods, org.apache.http.conn.ssl, org.apache.http.impl.client, org.apache.http.impl.conn, org.apache.http.protocol] /home/jenkins/agent/workspace/m2e_PR-2114/org.eclipse.m2e.maven.runtime/pom.xml [0:0]: Export org.codehaus.plexus.component.configurator.converters.special, has 1, private references [org.codehaus.classworlds] /home/jenkins/agent/workspace/m2e_PR-2114/org.eclipse.m2e.maven.runtime/pom.xml [0:0]: Export org.codehaus.plexus.component.factory, has 1, private references [org.codehaus.classworlds] /home/jenkins/agent/workspace/m2e_PR-2114/org.eclipse.m2e.maven.runtime/pom.xml [0:0]: Export org.eclipse.aether.transport.http, has 3, private references [org.apache.http, org.apache.http.client, org.apache.http.client.methods] /home/jenkins/agent/workspace/m2e_PR-2114/org.eclipse.m2e.maven.runtime/pom.xml [0:0]: Export org.eclipse.aether.transport.http.RFC9457, has 1, private references [org.apache.http.client.methods] /home/jenkins/agent/workspace/m2e_PR-2114/org.eclipse.m2e.maven.runtime/pom.xml [0:0]: Export com.google.inject, has 2, private references [com.google.errorprone.annotations, org.aopalliance.intercept] /home/jenkins/agent/workspace/m2e_PR-2114/org.eclipse.m2e.maven.runtime/pom.xml [0:0]: Export com.google.inject.spi, has 1, private references [org.aopalliance.intercept] /home/jenkins/agent/workspace/m2e_PR-2114/org.eclipse.m2e.maven.runtime/pom.xml [0:0]: Export org.eclipse.sisu.inject, has 1, private references [org.sonatype.inject] /home/jenkins/agent/workspace/m2e_PR-2114/ANONYMOUS [0:0]: Invalid package name: &#x27;META-INF.plexus&#x27; in Export-Package /home/jenkins/agent/workspace/m2e_PR-2114/ANONYMOUS [0:0]: Invalid package name: &#x27;META-INF.sisu&#x27; in Export-Package</code></pre>

Check warning on line 467 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-source:feature-source

NORMAL:
Raw output
<pre><code>Goal &#x27;feature-source&#x27; is deprecated: Source features are used for a long time to include sources in development environments but they where always brittle to use and badly integrated. As nowadays Tycho/P2 offers better ways to archive similar, the automatic generation of such features is deprecated and will be removed on the next release. In cases where this is still required, one should replace it with an explicitly maintained source feature in a dedicated module.</code></pre>

Check warning on line 510 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-source:feature-source

NORMAL:
Raw output
<pre><code>Goal &#x27;feature-source&#x27; is deprecated: Source features are used for a long time to include sources in development environments but they where always brittle to use and badly integrated. As nowadays Tycho/P2 offers better ways to archive similar, the automatic generation of such features is deprecated and will be removed on the next release. In cases where this is still required, one should replace it with an explicitly maintained source feature in a dedicated module.</code></pre>

Check warning on line 531 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-source:feature-source

NORMAL:
Raw output
<pre><code>Goal &#x27;feature-source&#x27; is deprecated: Source features are used for a long time to include sources in development environments but they where always brittle to use and badly integrated. As nowadays Tycho/P2 offers better ways to archive similar, the automatic generation of such features is deprecated and will be removed on the next release. In cases where this is still required, one should replace it with an explicitly maintained source feature in a dedicated module.</code></pre>

Check warning on line 561 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-p2-extras:compare-version-with-baselines

NORMAL:
Raw output
<pre><code>org.apache.maven.archetype:archetype-common:3.2.1: Host org.eclipse.m2e.maven.runtime=bundle-version=&quot;[3.8.0,4.0.0)&quot; for this fragment/require bundle cannot be found on the classpath org.apache.maven.archetype:archetype-common:3.2.1: Host com.ibm.icu= for this fragment/require bundle cannot be found on the classpath org.apache.maven.archetype:archetype-common:3.2.1: Unused Import-Package instructions: [org.jdom2*] org.apache.maven.archetype:archetype-common:3.2.1: Unused Export-Package instructions: [org.apache.maven.archetype.*] </code></pre>

Check warning on line 567 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-p2-extras:compare-version-with-baselines

NORMAL:
Raw output
<pre><code>org.apache.maven.archetype:archetype-catalog:3.2.1: Host org.eclipse.m2e.archetype.common=bundle-version=&quot;[3.2.104,4)&quot; for this fragment/require bundle cannot be found on the classpath org.apache.maven.archetype:archetype-catalog:3.2.1: Unused Export-Package instructions: [org.apache.maven.*] </code></pre>

Check warning on line 570 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-p2-extras:compare-version-with-baselines

NORMAL:
Raw output
<pre><code>org.apache.maven.archetype:archetype-descriptor:3.2.1: Host org.eclipse.m2e.archetype.common=bundle-version=&quot;[3.2.104,4)&quot; for this fragment/require bundle cannot be found on the classpath</code></pre>

Check warning on line 574 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-p2-extras:compare-version-with-baselines

NORMAL:
Raw output
<pre><code>org.apache.maven.shared:maven-artifact-transfer:0.13.1: Host org.eclipse.m2e.archetype.common=bundle-version=&quot;[3.2.104,4)&quot; for this fragment/require bundle cannot be found on the classpath org.apache.maven.shared:maven-artifact-transfer:0.13.1: Unused Export-Package instructions: [org.apache.maven.*] </code></pre>

Check warning on line 674 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-source:feature-source

NORMAL:
Raw output
<pre><code>Goal &#x27;feature-source&#x27; is deprecated: Source features are used for a long time to include sources in development environments but they where always brittle to use and badly integrated. As nowadays Tycho/P2 offers better ways to archive similar, the automatic generation of such features is deprecated and will be removed on the next release. In cases where this is still required, one should replace it with an explicitly maintained source feature in a dedicated module.</code></pre>

Check warning on line 1167 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-source:feature-source

NORMAL:
Raw output
<pre><code>Goal &#x27;feature-source&#x27; is deprecated: Source features are used for a long time to include sources in development environments but they where always brittle to use and badly integrated. As nowadays Tycho/P2 offers better ways to archive similar, the automatic generation of such features is deprecated and will be removed on the next release. In cases where this is still required, one should replace it with an explicitly maintained source feature in a dedicated module.</code></pre>

Check warning on line 1542 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-source:feature-source

NORMAL:
Raw output
<pre><code>Goal &#x27;feature-source&#x27; is deprecated: Source features are used for a long time to include sources in development environments but they where always brittle to use and badly integrated. As nowadays Tycho/P2 offers better ways to archive similar, the automatic generation of such features is deprecated and will be removed on the next release. In cases where this is still required, one should replace it with an explicitly maintained source feature in a dedicated module.</code></pre>

Check warning on line 1701 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-source:feature-source

NORMAL:
Raw output
<pre><code>Goal &#x27;feature-source&#x27; is deprecated: Source features are used for a long time to include sources in development environments but they where always brittle to use and badly integrated. As nowadays Tycho/P2 offers better ways to archive similar, the automatic generation of such features is deprecated and will be removed on the next release. In cases where this is still required, one should replace it with an explicitly maintained source feature in a dedicated module.</code></pre>

Check warning on line 1837 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-source:feature-source

NORMAL:
Raw output
<pre><code>Goal &#x27;feature-source&#x27; is deprecated: Source features are used for a long time to include sources in development environments but they where always brittle to use and badly integrated. As nowadays Tycho/P2 offers better ways to archive similar, the automatic generation of such features is deprecated and will be removed on the next release. In cases where this is still required, one should replace it with an explicitly maintained source feature in a dedicated module.</code></pre>

Check warning on line 1973 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-source:feature-source

NORMAL:
Raw output
<pre><code>Goal &#x27;feature-source&#x27; is deprecated: Source features are used for a long time to include sources in development environments but they where always brittle to use and badly integrated. As nowadays Tycho/P2 offers better ways to archive similar, the automatic generation of such features is deprecated and will be removed on the next release. In cases where this is still required, one should replace it with an explicitly maintained source feature in a dedicated module.</code></pre>

Check warning on line 2109 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-source:feature-source

NORMAL:
Raw output
<pre><code>Goal &#x27;feature-source&#x27; is deprecated: Source features are used for a long time to include sources in development environments but they where always brittle to use and badly integrated. As nowadays Tycho/P2 offers better ways to archive similar, the automatic generation of such features is deprecated and will be removed on the next release. In cases where this is still required, one should replace it with an explicitly maintained source feature in a dedicated module.</code></pre>

Check warning on line 2233 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-source:feature-source

NORMAL:
Raw output
<pre><code>Goal &#x27;feature-source&#x27; is deprecated: Source features are used for a long time to include sources in development environments but they where always brittle to use and badly integrated. As nowadays Tycho/P2 offers better ways to archive similar, the automatic generation of such features is deprecated and will be removed on the next release. In cases where this is still required, one should replace it with an explicitly maintained source feature in a dedicated module.</code></pre>

Check warning on line 2501 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-source:feature-source

NORMAL:
Raw output
<pre><code>Goal &#x27;feature-source&#x27; is deprecated: Source features are used for a long time to include sources in development environments but they where always brittle to use and badly integrated. As nowadays Tycho/P2 offers better ways to archive similar, the automatic generation of such features is deprecated and will be removed on the next release. In cases where this is still required, one should replace it with an explicitly maintained source feature in a dedicated module.</code></pre>

Check warning on line 2649 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-source:feature-source

NORMAL:
Raw output
<pre><code>Goal &#x27;feature-source&#x27; is deprecated: Source features are used for a long time to include sources in development environments but they where always brittle to use and badly integrated. As nowadays Tycho/P2 offers better ways to archive similar, the automatic generation of such features is deprecated and will be removed on the next release. In cases where this is still required, one should replace it with an explicitly maintained source feature in a dedicated module.</code></pre>

Check warning on line 2752 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-source:feature-source

NORMAL:
Raw output
<pre><code>Goal &#x27;feature-source&#x27; is deprecated: Source features are used for a long time to include sources in development environments but they where always brittle to use and badly integrated. As nowadays Tycho/P2 offers better ways to archive similar, the automatic generation of such features is deprecated and will be removed on the next release. In cases where this is still required, one should replace it with an explicitly maintained source feature in a dedicated module.</code></pre>

Check warning on line 2856 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-source:feature-source

NORMAL:
Raw output
<pre><code>Goal &#x27;feature-source&#x27; is deprecated: Source features are used for a long time to include sources in development environments but they where always brittle to use and badly integrated. As nowadays Tycho/P2 offers better ways to archive similar, the automatic generation of such features is deprecated and will be removed on the next release. In cases where this is still required, one should replace it with an explicitly maintained source feature in a dedicated module.</code></pre>

Check warning on line 2960 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-source:feature-source

NORMAL:
Raw output
<pre><code>Goal &#x27;feature-source&#x27; is deprecated: Source features are used for a long time to include sources in development environments but they where always brittle to use and badly integrated. As nowadays Tycho/P2 offers better ways to archive similar, the automatic generation of such features is deprecated and will be removed on the next release. In cases where this is still required, one should replace it with an explicitly maintained source feature in a dedicated module.</code></pre>

Check warning on line 3056 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-source:feature-source

NORMAL:
Raw output
<pre><code>Goal &#x27;feature-source&#x27; is deprecated: Source features are used for a long time to include sources in development environments but they where always brittle to use and badly integrated. As nowadays Tycho/P2 offers better ways to archive similar, the automatic generation of such features is deprecated and will be removed on the next release. In cases where this is still required, one should replace it with an explicitly maintained source feature in a dedicated module.</code></pre>

Check warning on line 3143 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-source:feature-source

NORMAL:
Raw output
<pre><code>Goal &#x27;feature-source&#x27; is deprecated: Source features are used for a long time to include sources in development environments but they where always brittle to use and badly integrated. As nowadays Tycho/P2 offers better ways to archive similar, the automatic generation of such features is deprecated and will be removed on the next release. In cases where this is still required, one should replace it with an explicitly maintained source feature in a dedicated module.</code></pre>

Check warning on line 3230 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-source:feature-source

NORMAL:
Raw output
<pre><code>Goal &#x27;feature-source&#x27; is deprecated: Source features are used for a long time to include sources in development environments but they where always brittle to use and badly integrated. As nowadays Tycho/P2 offers better ways to archive similar, the automatic generation of such features is deprecated and will be removed on the next release. In cases where this is still required, one should replace it with an explicitly maintained source feature in a dedicated module.</code></pre>

Check warning on line 3320 in jenkins-console.log

See this annotation in the file changed.

@jenkins-m2e jenkins-m2e / Maven

tycho-source:feature-source

NORMAL:
Raw output
<pre><code>Goal &#x27;feature-source&#x27; is deprecated: Source features are used for a long time to include sources in development environments but they where always brittle to use and badly integrated. As nowadays Tycho/P2 offers better ways to archive similar, the automatic generation of such features is deprecated and will be removed on the next release. In cases where this is still required, one should replace it with an explicitly maintained source feature in a dedicated module.</code></pre>