Am 2016-01-01 um 05:12 schrieb Dan Tran:
Strange, I even went this far in my pluginManagement
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-project-info-reports-plugin</artifactId>
<version>${project-info-report.plugin.version}</version>
<dependencies>
<dependency>
<groupId>org.apache.maven.shared</groupId>
<artifactId>maven-shared-jar</artifactId>
<version>1.1</version>
<exclusions>
<exclusion>
<groupId>org.apache.bcel</groupId>
<artifactId>bcel</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>com.google.code.findbugs</groupId>
<artifactId>bcel-findbugs</artifactId>
<version>6.0</version>
</dependency>
</dependencies>
</plugin>
And the debug log still shows the old bcel, looks like my <dependencies>
settings just disappear
Could you hookup the report plugin ( 2.8.2-SNAPSHOT) with the snapshot of
maven-shared-jar-1.2?. I can give it a try
I cannot confirm this problem. Just updated from your change and adapted
the IT full-pom to include maven-artifact 3.3.9 (Java 7) and dropwizard
9.x (Java 8) and the dependencies report looks good now. Have a look
here: http://home.apache.org/~michaelo/full-pom/dependencies.html
Michael
On Thu, Dec 31, 2015 at 6:42 PM, Michael Osipov <micha...@apache.org> wrote:
Am 2016-01-01 um 01:47 schrieb Dan Tran:
I add this jar to my project-info-report-plugin
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-project-info-reports-plugin</artifactId>
<version>${project-info-report.plugin.version}</version>
<dependencies>
<dependency>
<groupId>org.apache.maven.shared</groupId>
<artifactId>maven-shared-jar</artifactId>
<version>${shared.jar.version}</version>
</dependency>
</dependencies>
</plugin>
and still see the bcel's java8 issue. may be we should ask wide audience
at maven list to verify this
I have replaced Commons BCEL 5.2 with a interim version 6.0 published by
Findbugs because the original one has not been released yet.
Can you run with -X and provide the classpath tree of the plugin?
We should see whether the correct dependency is included or not. You have
to exclude 5.2 explicitly because gid and aid do not match.
Michael
On Thu, Dec 31, 2015 at 12:30 PM, Michael Osipov <micha...@apache.org>
wrote:
Hi,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12334441
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=component%20%3D%20maven-shared-jar%20AND%20project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC
Staging repo:
https://repository.apache.org/content/repositories/maven-1242/
https://repository.apache.org/content/repositories/maven-1242/org/apache/maven/shared/maven-shared-jar/1.2/maven-shared-jar-1.2-source-release.zip
Source release checksum(s):
maven-shared-jar-1.2-source-release.zip sha1:
0fce6592e9ffc2d31b3ad9e59d6a488af31f78ac
Staging site:
https://maven.apache.org/shared-archives/maven-shared-jar-LATEST/
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Vote open for 72 hours.
[ ] +1
[ ] +0
[ ] -1
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
