[jira] [Created] (MNG-7603) Build cache XSD is not published
David Phillips created MNG-7603: --- Summary: Build cache XSD is not published Key: MNG-7603 URL: https://issues.apache.org/jira/browse/MNG-7603 Project: Maven Issue Type: Bug Reporter: David Phillips The [build cache XSD|https://maven.apache.org/xsd/build-cache-config-1.0.0.xsd] which is [referenced here|https://maven.apache.org/extensions/maven-build-cache-extension/build-cache-build.html] is not published on the Maven website. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MENFORCER-409) Log at ERROR level when is set
David Phillips created MENFORCER-409:
Summary: Log at ERROR level when is set
Key: MENFORCER-409
URL: https://issues.apache.org/jira/browse/MENFORCER-409
Project: Maven Enforcer Plugin
Issue Type: Bug
Reporter: David Phillips
When {{true}} is set, messages for problems that will fail the
build should be logged at {{ERROR}} level, so that they are easier to find in
the log:
{noformat}
[WARN] Rule 1: org.apache.maven.plugins.enforcer.RequireUpperBoundDeps failed
with message:
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (MCOMPILER-425) Compiler argument with newline treated as multiple arguments in fork mode
David Phillips created MCOMPILER-425:
Summary: Compiler argument with newline treated as multiple
arguments in fork mode
Key: MCOMPILER-425
URL: https://issues.apache.org/jira/browse/MCOMPILER-425
Project: Maven Compiler Plugin
Issue Type: Bug
Affects Versions: 3.8.1
Reporter: David Phillips
In the below example, we want to pass the second argument as a single argument
to the compiler, but we add newlines in the XML for readability. This works
correctly when not forking, but when forking, the argument is treated as
multiple arguments.
{code:xml}
true
-XDcompilePolicy=simple
-Xplugin:ErrorProne
-Xep:ObjectToString:ERROR
com.google.errorprone
error_prone_core
2.4.0
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MSHADE-250) Allow prefixing relocated classes
[
https://issues.apache.org/jira/browse/MSHADE-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Phillips updated MSHADE-250:
--
Description: I would like to prefix all of the relocated classes with a
{{$}}. This prevents them from accidentally being used, imported by IDEs, etc.
For example, {{com.google.common.collect.ImmutableList}} would become
{{guava.collect.$ImmutableList}}. (was: I would like to prefix all of the
relocated classes with a {{$}}. This prevents them from accidentally being
used, imported by IDEs, etc. For example,
{{com.google.common.collect.ImmutableList}} would become
{{com.example.guava.collect.$ImmutableList}}.)
> Allow prefixing relocated classes
> -
>
> Key: MSHADE-250
> URL: https://issues.apache.org/jira/browse/MSHADE-250
> Project: Maven Shade Plugin
> Issue Type: New Feature
>Reporter: David Phillips
>Priority: Major
>
> I would like to prefix all of the relocated classes with a {{$}}. This
> prevents them from accidentally being used, imported by IDEs, etc. For
> example, {{com.google.common.collect.ImmutableList}} would become
> {{guava.collect.$ImmutableList}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MSHADE-250) Allow prefixing relocated classes
David Phillips created MSHADE-250:
-
Summary: Allow prefixing relocated classes
Key: MSHADE-250
URL: https://issues.apache.org/jira/browse/MSHADE-250
Project: Maven Shade Plugin
Issue Type: New Feature
Reporter: David Phillips
I would like to prefix all of the relocated classes with a {{$}}. This prevents
them from accidentally being used, imported by IDEs, etc. For example,
{{com.google.common.collect.ImmutableList}} would become
{{com.example.guava.collect.$ImmutableList}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] (MSHADE-184) Cannot use dollar sign in shadedPattern name
[
https://jira.codehaus.org/browse/MSHADE-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Phillips closed MSHADE-184.
-
Resolution: Not A Bug
> Cannot use dollar sign in shadedPattern name
>
>
> Key: MSHADE-184
> URL: https://jira.codehaus.org/browse/MSHADE-184
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: David Phillips
>
> The following relocation would be useful to prevent IDEs from suggesting the
> relocated classes for import:
> {code:xml}
>
> org.apache.commons com.example.$internal.commons
>
> {code}
> Unfortunately, it fails with an error:
> {code:none}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:2.3:shade (default) on project
> hive-apache: Error creating shaded jar: Illegal group reference -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSHADE-184) Cannot use dollar sign in shadedPattern name
[
https://jira.codehaus.org/browse/MSHADE-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=362042#comment-362042
]
David Phillips commented on MSHADE-184:
---
It looks like escaping the dollar sign works:
{code:xml}
org.apache.commonscom.example.\$internal.commons
{code}
> Cannot use dollar sign in shadedPattern name
>
>
> Key: MSHADE-184
> URL: https://jira.codehaus.org/browse/MSHADE-184
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: David Phillips
>
> The following relocation would be useful to prevent IDEs from suggesting the
> relocated classes for import:
> {code:xml}
>
> org.apache.commons com.example.$internal.commons
>
> {code}
> Unfortunately, it fails with an error:
> {code:none}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:2.3:shade (default) on project
> hive-apache: Error creating shaded jar: Illegal group reference -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSHADE-184) Cannot use dollar sign in shadedPattern name
David Phillips created MSHADE-184:
-
Summary: Cannot use dollar sign in shadedPattern name
Key: MSHADE-184
URL: https://jira.codehaus.org/browse/MSHADE-184
Project: Maven Shade Plugin
Issue Type: Bug
Affects Versions: 2.3
Reporter: David Phillips
The following relocation would be useful to prevent IDEs from suggesting the
relocated classes for import:
{code:xml}
org.apache.commonscom.example.$internal.commons
{code}
Unfortunately, it fails with an error:
{code:none}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-shade-plugin:2.3:shade (default) on project
hive-apache: Error creating shaded jar: Illegal group reference -> [Help 1]
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MDEP-469) analyze-report java.io.FileNotFoundException:
[
https://jira.codehaus.org/browse/MDEP-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361116#comment-361116
]
David Phillips commented on MDEP-469:
-
We see this error all the time, but for the analyze-only goal which we run in
the process-test-classes phase.
> analyze-report java.io.FileNotFoundException:
> -
>
> Key: MDEP-469
> URL: https://jira.codehaus.org/browse/MDEP-469
> Project: Maven Dependency Plugin
> Issue Type: Bug
>Affects Versions: 2.9
>Reporter: jieryn
>
> Apache Maven 3.2.3, multi-module project,
> maven-dependency-plugin:analyze-report:2.9 throws FileNotFoundException
> during site phase (same exact project and configuration but with 2.8 is
> successful):
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project
> dao: Error generating maven-dependency-plugin:2.9:analyze-report: Cannot
> analyze dependencies:
> /var/lib/jenkins/jobs/site_com.acme.proj/workspace/domain/target/classes (Is
> a directory) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
> project dao: Error generating maven-dependency-plugin:2.9:analyze-report:
> Cannot analyze dependencies
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error generating
> maven-dependency-plugin:2.9:analyze-report: Cannot analyze dependencies
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:146)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 more
> Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error
> generating maven-dependency-plugin:2.9:analyze-report: Cannot analyze
> dependencies
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:239)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:311)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:129)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:182)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:141)
> ... 21 more
> Caused by: org.apache.maven.reporting.MavenReportException: Cannot analyze
> dependencies
> at
> org.apache.maven.plugin.dependency.analyze.AnalyzeReportMojo.executeReport(AnalyzeReportMojo.java:145)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:196)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:224)
> ... 25 more
> Caused by:
> org.apache.maven.shared.dependency.analyzer.ProjectDependencyAnalyzerException
[jira] (MNG-5363) Regression for SSLv3
[
https://jira.codehaus.org/browse/MNG-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315972#comment-315972
]
David Phillips commented on MNG-5363:
-
This also occurs with 3.0.3:
{noformat}
Apache Maven 3.0.3 (r1075438; 2011-02-28 09:31:09-0800)
Maven home: /usr/share/maven
Java version: 1.7.0_07, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_07.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.8.2", arch: "x86_64", family: "mac"
{noformat}
> Regression for SSLv3
>
>
> Key: MNG-5363
> URL: https://jira.codehaus.org/browse/MNG-5363
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Errors
>Affects Versions: 3.0.4
> Environment: Operation system independent, but tested on Macbook Pro
> with 10.6 and Red Hat Enterprise Linux 6 on a virtual machine.
>Reporter: James Kionka
>
> When attempting to access a Maven repository which uses SSLv3, you get the
> following error, "javax.net.ssl.SSLException: Received fatal alert:
> bad_record_mac".
> Earlier versions of Maven used java.net.URLConnection which respects the
> https.protocols system property. This allowed us to set it to SSLv3, which is
> what our Maven repository uses. However, HttpClient ignores that property. In
> other situations, we programmatically tell HttpClient to use SSLv3, which we
> cannot do from our end.
> You can find another person in the same situation here:
> http://stackoverflow.com/questions/12787657/received-fatal-alert-bad-record-mac-when-deploying-to-sonatype
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHADE-128) Too many warnings "We have duplicates"
[ https://jira.codehaus.org/browse/MSHADE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311538#comment-311538 ] David Phillips commented on MSHADE-128: --- This isn't a duplicate of MSHADE-126, which is bug that generates false warnings. Rather, this issue is about improving the messages for legitimate warnings. Please re-open and apply the patch. This is a huge improvement! > Too many warnings "We have duplicates" > -- > > Key: MSHADE-128 > URL: https://jira.codehaus.org/browse/MSHADE-128 > Project: Maven 2.x Shade Plugin > Issue Type: Improvement >Affects Versions: 1.7.1 >Reporter: Raffaele >Assignee: Benson Margulies > Attachments: pom.xml, warning-we-have-duplicates.patch > > > When creating an uberjar, sometimes the same class is present in two or more > dependencies' JARs. For each class, maven-shade-plugin issues a WARNING We > have a duplicate in. > This is annoying and can muddle newcomers up (like myself), because it's not > clear how to fix. > I don't know if a programmatic solution to these warnings could exist: maybe > it will always require human interaction. However, it's better to point users > in the right direction and not spit out thousands of useless warnings. > Attached is a pom which triggers thousands of warnings and a patch with a > prettier (and hopefully more useful) output like > [WARNING] bcprov-jdk14-138.jar, bcprov-jdk14-1.38.jar define 1292 > overlappping classes: > [WARNING] - org.bouncycastle.asn1.ocsp.ResponderID > [WARNING] - org.bouncycastle.crypto.params.DSAPublicKeyParameters > [WARNING] - org.bouncycastle.crypto.engines.DESEngine > [WARNING] - org.bouncycastle.jce.provider.JCEElGamalPrivateKey > [WARNING] - org.bouncycastle.jce.provider.JCEStreamCipher$Skipjack_CFB8 > [WARNING] - org.bouncycastle.jce.provider.JCESecretKeyFactory > [WARNING] - org.bouncycastle.i18n.filter.UntrustedInput > [WARNING] - org.bouncycastle.asn1.x9.X962NamedCurves$5 > [WARNING] - org.bouncycastle.jce.X509KeyUsage > [WARNING] maven-shade-plugin has detected that some .class files > [WARNING] are present in two or more JARs. When this happens, only > [WARNING] one single version of the class is copied in the uberjar. > [WARNING] Usually this is not harmful and you can skeep these > [WARNING] warnings, otherwise try to manually exclude artifacts > [WARNING] based on mvn dependency:tree -Ddetail=true and the above > [WARNING] output > [WARNING] See http://docs.codehaus.org/display/MAVENUSER/Shade+Plugin -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
