[jira] [Created] (MNG-6904) VLT-RCP allow to pass a filter.xml for more finegrained control
Konrad Windszus created MNG-6904:
Summary: VLT-RCP allow to pass a filter.xml for more finegrained
control
Key: MNG-6904
URL: https://issues.apache.org/jira/browse/MNG-6904
Project: Maven
Issue Type: Improvement
Reporter: Konrad Windszus
Although the {{ResourceCopier}} allows to set a source filter
(https://github.com/apache/jackrabbit-filevault/blob/e257001ec22ea06bcc987cbf79f0cc9b15c4e186/vault-core/src/main/java/org/apache/jackrabbit/vault/util/RepositoryCopier.java#L119)
this cannot be leveraged through RCP tasks yet. There should be add an
additional optional parameter for RcpTask
(https://github.com/apache/jackrabbit-filevault/blob/f44ac494bc49e1153df5b23769e799b5ebdecb1b/vault-rcp/src/main/java/org/apache/jackrabbit/vault/rcp/impl/RcpTask.java#L85)
which allows to set that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-6904) VLT-RCP allow to pass a filter.xml for more finegrained control
[
https://issues.apache.org/jira/browse/MNG-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105285#comment-17105285
]
Konrad Windszus commented on MNG-6904:
--
Created in wrong project, as moving is not possible just closing here. The
correct issue is at https://issues.apache.org/jira/browse/JCRVLT-437.
> VLT-RCP allow to pass a filter.xml for more finegrained control
> ---
>
> Key: MNG-6904
> URL: https://issues.apache.org/jira/browse/MNG-6904
> Project: Maven
> Issue Type: Improvement
>Reporter: Konrad Windszus
>Priority: Major
>
> Although the {{ResourceCopier}} allows to set a source filter
> (https://github.com/apache/jackrabbit-filevault/blob/e257001ec22ea06bcc987cbf79f0cc9b15c4e186/vault-core/src/main/java/org/apache/jackrabbit/vault/util/RepositoryCopier.java#L119)
> this cannot be leveraged through RCP tasks yet. There should be add an
> additional optional parameter for RcpTask
> (https://github.com/apache/jackrabbit-filevault/blob/f44ac494bc49e1153df5b23769e799b5ebdecb1b/vault-rcp/src/main/java/org/apache/jackrabbit/vault/rcp/impl/RcpTask.java#L85)
> which allows to set that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MSHADE-364) Don't log as duplicate resource handled by a transformer
Romain Manni-Bucau created MSHADE-364: - Summary: Don't log as duplicate resource handled by a transformer Key: MSHADE-364 URL: https://issues.apache.org/jira/browse/MSHADE-364 Project: Maven Shade Plugin Issue Type: Task Affects Versions: 3.2.3 Reporter: Romain Manni-Bucau Follow up of MSHADE-306, when a transformer handles a resource, no need to log it as duplicated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MASSEMBLY-936) Fix line length
Elliotte Rusty Harold created MASSEMBLY-936:
---
Summary: Fix line length
Key: MASSEMBLY-936
URL: https://issues.apache.org/jira/browse/MASSEMBLY-936
Project: Maven Assembly Plugin
Issue Type: Improvement
Reporter: Elliotte Rusty Harold
The code is full of sections like this where the 120 character line length is
violated and yet someone turned off checkstyle instead of fixing the line
length. This code is a pain to work with on a 13" laptop. Fix it.
{color:#808080}// CHECKSTYLE_OFF: LineLength
{color}{color:#80}return {color}FixedStringSearchInterpolator.create(
{color:#80}new {color}PrefixedPropertiesValueSource(
InterpolationConstants.{color:#660e7a}PROJECT_PROPERTIES_PREFIXES{color},
project.getProperties(), {color:#80}true {color}),
{color:#80}new {color}PrefixedObjectValueSource(
InterpolationConstants.{color:#660e7a}PROJECT_PREFIXES{color},
project, {color:#80}true {color}) );
{color:#808080}// CHECKSTYLE_ON: LineLength{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (SUREFIRE-1788) Unhandled native logs in SurefireForkChannel
[ https://issues.apache.org/jira/browse/SUREFIRE-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1788. -- Resolution: Fixed https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=5a1c7430967710b2fe50c19cb6742f4d7dcdb9b7 > Unhandled native logs in SurefireForkChannel > > > Key: SUREFIRE-1788 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1788 > Project: Maven Surefire > Issue Type: Task > Components: Maven Failsafe Plugin, Maven Surefire Plugin, process > forking >Reporter: Tibor Digana >Assignee: Tibor Digana >Priority: Major > Fix For: 3.0.0-M5 > > > This is related only to the internal change of the version 3.0.0-M5 itself. > The > [stdOut|https://github.com/apache/maven-surefire/blob/master/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/extensions/SurefireForkChannel.java#L153] > should be printed to INFO on the console. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (MDEP-480) There should be an option to prevent files overwrite for unpack-dependencies and unpack
[ https://issues.apache.org/jira/browse/MDEP-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105720#comment-17105720 ] Robert Scholte edited comment on MDEP-480 at 5/12/20, 8:34 PM: --- The description contains an interesting word: scope for artifact or file. Right now overwriteRelease, overwriteSnapshot, overwriteIfNewer are all booleans, but I think it makes sense to allow the scope here too. So valid values would be: - true - false - artifact: (similar to true) - file This will keep the number of parameters small. was (Author: rfscholte): The description contains an interesting word: scope for artifact or file. Right now overwriteRelease, overwriteSnapshot, overwriteIfNewer are all booleans, but I think it makes sense to allow the scope here too. So valid values would be: - true - false - artifact: (similar to true) - file This will keep the number of parameters small. > There should be an option to prevent files overwrite for unpack-dependencies > and unpack > --- > > Key: MDEP-480 > URL: https://issues.apache.org/jira/browse/MDEP-480 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: unpack, unpack-dependencies >Reporter: duongdeptrai >Assignee: Benson Margulies >Priority: Major > Attachments: patch-maven-dependency-2.9-overwriteFiles.patch > > > There should be an option to prevent file overwrite when extracting files. > This option is very helpful when unpack or unpack-dependencies happens after > process-resouce phase. > Currently, there is overwriteRelease, overwriteSnapshot, overwriteIfNewer. > But they all work on the artifact scope (that means decide if a whole > artifact should overwrite), not files scope (if a file should overwrite an > existing file). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MDEP-480) There should be an option to prevent files overwrite for unpack-dependencies and unpack
[ https://issues.apache.org/jira/browse/MDEP-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105720#comment-17105720 ] Robert Scholte commented on MDEP-480: - The description contains an interesting word: scope for artifact or file. Right now overwriteRelease, overwriteSnapshot, overwriteIfNewer are all booleans, but I think it makes sense to allow the scope here too. So valid values would be: - true - false - artifact: (similar to true) - file This will keep the number of parameters small. > There should be an option to prevent files overwrite for unpack-dependencies > and unpack > --- > > Key: MDEP-480 > URL: https://issues.apache.org/jira/browse/MDEP-480 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: unpack, unpack-dependencies >Reporter: duongdeptrai >Assignee: Benson Margulies >Priority: Major > Attachments: patch-maven-dependency-2.9-overwriteFiles.patch > > > There should be an option to prevent file overwrite when extracting files. > This option is very helpful when unpack or unpack-dependencies happens after > process-resouce phase. > Currently, there is overwriteRelease, overwriteSnapshot, overwriteIfNewer. > But they all work on the artifact scope (that means decide if a whole > artifact should overwrite), not files scope (if a file should overwrite an > existing file). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (SUREFIRE-1570) Maven-fail-safe doesn't put testing JPMS module on module path
[
https://issues.apache.org/jira/browse/SUREFIRE-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana reassigned SUREFIRE-1570:
--
Assignee: Tibor Digana
> Maven-fail-safe doesn't put testing JPMS module on module path
> --
>
> Key: SUREFIRE-1570
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1570
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
>Affects Versions: 2.22.0
>Reporter: Pavel_K
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M5
>
> Attachments: mavenproject20.zip
>
>
> I uploaded project - mavenproject20. Run `mvn verify`. You will see the
> following:
> {code:java}
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building mavenproject20 0.1.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> mavenproject20 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @
> mavenproject20 ---
> [WARNING]
>
> [WARNING] * Required filename-based automodules detected. Please don't
> publish this project to a public artifact repository! *
> [WARNING]
>
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 3 source files to
> /home/Jim/NetBeansProjects/mavenproject20/target/classes
> [WARNING]
> /home/Jim/NetBeansProjects/mavenproject20/src/main/java/module-info.java:[1,8]
> module name component Mavenproject20 should avoid terminal digits
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
> mavenproject20 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory
> /home/Jim/NetBeansProjects/mavenproject20/src/test/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.8.0:testCompile (default-testCompile) @
> mavenproject20 ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 1 source file to
> /home/Jim/NetBeansProjects/mavenproject20/target/test-classes
> [INFO]
> [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ mavenproject20
> ---
> [INFO]
> [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ mavenproject20 ---
> [INFO] Building jar:
> /home/Jim/NetBeansProjects/mavenproject20/target/mavenproject20-0.1.0-SNAPSHOT.jar
> [INFO]
> [INFO] --- maven-failsafe-plugin:2.22.0:integration-test (integration-tests)
> @ mavenproject20 ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running me.pavel.mavenproject20.ServiceIT
> JDKModulePath:null
> ModuleName:null
> module jdk.unsupported
> module jdk.sctp
> module java.naming
> module java.jnlp
> module jdk.httpserver
> module java.xml
> module javafx.controls
> module java.datatransfer
> module jdk.javadoc
> module jdk.jconsole
> module java.instrument
> module jdk.packager
> module jdk.deploy
> module jdk.jfr
> module jdk.management
> module jdk.charsets
> module oracle.net
> module jdk.jdeps
> module java.sql.rowset
> module jdk.net
> module jdk.accessibility
> module jdk.attach
> module jdk.internal.le
> module jdk.snmp
> module java.base
> module jdk.plugin
> module jdk.dynalink
> module jdk.naming.rmi
> module jdk.internal.opt
> module java.management.rmi
> module jdk.management.jfr
> module javafx.swing
> module jdk.editpad
> module jdk.crypto.ec
> module jdk.javaws
> module jdk.jstatd
> module jdk.management.agent
> module javafx.graphics
> module javafx.media
> module java.rmi
> module java.prefs
> module jdk.security.jgss
> module javafx.fxml
> module java.smartcardio
> module jdk.xml.dom
> module java.xml.crypto
> module jdk.jsobject
> module jdk.jdi
> module jdk.compiler
> module java.management
> module jdk.management.cmm
> module jdk.packager.services
> module jdk.jartool
> module jdk.scripting.nashorn
> module java.security.jgss
> module jdk.localedata
> module java.desktop
> module jdk.zipfs
> module jdk.jshell
> module oracle.desktop
> module jdk.internal.ed
> module java.security.sasl
> module jdk.jdwp.agent
> module java.compiler
> module jdk.plugin.dom
> module javafx.web
> module jdk.naming.dns
> module jdk.crypto.cryptoki
> mod
[jira] [Updated] (SUREFIRE-1570) Maven-fail-safe doesn't put testing JPMS module on module path
[
https://issues.apache.org/jira/browse/SUREFIRE-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1570:
---
External issue URL: https://github.com/apache/maven-surefire/pull/297
> Maven-fail-safe doesn't put testing JPMS module on module path
> --
>
> Key: SUREFIRE-1570
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1570
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
>Affects Versions: 2.22.0
>Reporter: Pavel_K
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M5
>
> Attachments: mavenproject20.zip
>
>
> I uploaded project - mavenproject20. Run `mvn verify`. You will see the
> following:
> {code:java}
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building mavenproject20 0.1.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> mavenproject20 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @
> mavenproject20 ---
> [WARNING]
>
> [WARNING] * Required filename-based automodules detected. Please don't
> publish this project to a public artifact repository! *
> [WARNING]
>
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 3 source files to
> /home/Jim/NetBeansProjects/mavenproject20/target/classes
> [WARNING]
> /home/Jim/NetBeansProjects/mavenproject20/src/main/java/module-info.java:[1,8]
> module name component Mavenproject20 should avoid terminal digits
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
> mavenproject20 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory
> /home/Jim/NetBeansProjects/mavenproject20/src/test/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.8.0:testCompile (default-testCompile) @
> mavenproject20 ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 1 source file to
> /home/Jim/NetBeansProjects/mavenproject20/target/test-classes
> [INFO]
> [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ mavenproject20
> ---
> [INFO]
> [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ mavenproject20 ---
> [INFO] Building jar:
> /home/Jim/NetBeansProjects/mavenproject20/target/mavenproject20-0.1.0-SNAPSHOT.jar
> [INFO]
> [INFO] --- maven-failsafe-plugin:2.22.0:integration-test (integration-tests)
> @ mavenproject20 ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running me.pavel.mavenproject20.ServiceIT
> JDKModulePath:null
> ModuleName:null
> module jdk.unsupported
> module jdk.sctp
> module java.naming
> module java.jnlp
> module jdk.httpserver
> module java.xml
> module javafx.controls
> module java.datatransfer
> module jdk.javadoc
> module jdk.jconsole
> module java.instrument
> module jdk.packager
> module jdk.deploy
> module jdk.jfr
> module jdk.management
> module jdk.charsets
> module oracle.net
> module jdk.jdeps
> module java.sql.rowset
> module jdk.net
> module jdk.accessibility
> module jdk.attach
> module jdk.internal.le
> module jdk.snmp
> module java.base
> module jdk.plugin
> module jdk.dynalink
> module jdk.naming.rmi
> module jdk.internal.opt
> module java.management.rmi
> module jdk.management.jfr
> module javafx.swing
> module jdk.editpad
> module jdk.crypto.ec
> module jdk.javaws
> module jdk.jstatd
> module jdk.management.agent
> module javafx.graphics
> module javafx.media
> module java.rmi
> module java.prefs
> module jdk.security.jgss
> module javafx.fxml
> module java.smartcardio
> module jdk.xml.dom
> module java.xml.crypto
> module jdk.jsobject
> module jdk.jdi
> module jdk.compiler
> module java.management
> module jdk.management.cmm
> module jdk.packager.services
> module jdk.jartool
> module jdk.scripting.nashorn
> module java.security.jgss
> module jdk.localedata
> module java.desktop
> module jdk.zipfs
> module jdk.jshell
> module oracle.desktop
> module jdk.internal.ed
> module java.security.sasl
> module jdk.jdwp.agent
> module java.compiler
> module jdk.plugin.dom
> module javafx.web
> module jdk.namin
[jira] [Assigned] (SUREFIRE-1733) Surefire and Failsafe JPMS additions for JUnit 5.x execution
[
https://issues.apache.org/jira/browse/SUREFIRE-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana reassigned SUREFIRE-1733:
--
Assignee: Tibor Digana
> Surefire and Failsafe JPMS additions for JUnit 5.x execution
>
>
> Key: SUREFIRE-1733
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1733
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Affects Versions: 2.22.2, 3.0.0-M4
>Reporter: John Patrick
>Assignee: Tibor Digana
>Priority: Minor
> Fix For: 3.0.0-M5
>
> Attachments: surefire-v2.22.2_junit-v5.5.2.txt,
> surefire-v2.22.2_junit-v5.6.0-M1.txt, surefire-v3.0.0-M4_junit-v5.5.2.txt,
> surefire-v3.0.0-M4_junit-v5.6.0-M1.txt
>
>
> Following on from SUREFIRE-1731 it was highlighted that some projects need
> extra '--add-open' options for JUnit to execute correctly, lots have already
> been handled or added or supported in previous releases but I'm needing to
> add these for a project to run correctly.
> I'm happy to start looking at a patch, but need help with where repo or class
> to start looking at.
> This is what extra arguments I'm needing to pass to surefire/failsafe.
> {code}
> --add-opens
> ${project.Automatic-Module-Name}/${project.Automatic-Module-Name}=ALL-UNNAMED
> --add-opens
> ${project.Automatic-Module-Name}/${project.Automatic-Module-Name}=org.junit.platform.commons
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED
> {code}
> Luckly my module names and package names are all on the same standard and
> I've got a maven property for each sub module defining what
> 'project.Automatic-Module-Name' is.
> The 2nd two are probably easy and will work for everyone, the 1st two might
> require some discussion and maybe define two variables that surefire and
> failsafe can use, one for the module name and one for the package name if
> they can dynamically scan the source code and work it out.
> This is the stacktrace I'm seeing;
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on
> project PROJECT: There are test failures.
> [ERROR]
> [ERROR] Please refer to PATH/target/surefire-reports for the individual test
> results.
> [ERROR] Please refer to dump files (if any exist) [date].dump,
> [date]-jvmRun[N].dump and [date].dumpstream.
> [ERROR] There was an error in the forked process
> [ERROR] java.lang.IllegalAccessError: class
> org.junit.platform.launcher.core.LauncherFactory (in unnamed module
> @0x6eceb130) cannot access class
> org.junit.platform.commons.util.Preconditions (in module
> org.junit.platform.commons) because module org.junit.platform.commons does
> not export org.junit.platform.commons.util to unnamed module @0x6eceb130
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There
> was an error in the forked process
> [ERROR] java.lang.IllegalAccessError: class
> org.junit.platform.launcher.core.LauncherFactory (in unnamed module
> @0x6eceb130) cannot access class
> org.junit.platform.commons.util.Preconditions (in module
> org.junit.platform.commons) because module org.junit.platform.commons does
> not export org.junit.platform.commons.util to unnamed module @0x6eceb130
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:656)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:282)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1183)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1011)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:857)
> [ERROR] at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.jav
[jira] [Updated] (MSHADE-363) Breaking change to ResourceTransformer's API
[ https://issues.apache.org/jira/browse/MSHADE-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSHADE-363: - Fix Version/s: 3.2.4 > Breaking change to ResourceTransformer's API > > > Key: MSHADE-363 > URL: https://issues.apache.org/jira/browse/MSHADE-363 > Project: Maven Shade Plugin > Issue Type: Bug >Affects Versions: 3.2.3 >Reporter: Andy Wilkinson >Priority: Major > Fix For: 3.2.4 > > > A Spring Boot user has [made us > aware|https://github.com/spring-projects/spring-boot/issues/21128] of a > [breaking change to the API of > ResourceTransformer|https://github.com/apache/maven-shade-plugin/commit/0d7bfb53a5fd83eede7edfd5552db5fa561d6286#diff-f09094e2212bb4d1173a4e183635b958] > in 3.2.3. > Ideally, we don't want to require a specific version of the Shade plugin. > While I think we may be able to support the new and old both variants of the > method, it would be preferable if future 3.2.x releases are backwards > compatible with 3.2.2. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSHADE-360) ServicesResourceTransformer.modifyOutputStream swallows IOExceptions
[ https://issues.apache.org/jira/browse/MSHADE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSHADE-360: - Affects Version/s: 3.2.3 > ServicesResourceTransformer.modifyOutputStream swallows IOExceptions > > > Key: MSHADE-360 > URL: https://issues.apache.org/jira/browse/MSHADE-360 > Project: Maven Shade Plugin > Issue Type: Bug >Affects Versions: 3.2.3 >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > Because it uses PrintWriter and doesn't check error conditions -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSHADE-360) ServicesResourceTransformer.modifyOutputStream swallows IOExceptions
[ https://issues.apache.org/jira/browse/MSHADE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSHADE-360: - Fix Version/s: 3.2.4 > ServicesResourceTransformer.modifyOutputStream swallows IOExceptions > > > Key: MSHADE-360 > URL: https://issues.apache.org/jira/browse/MSHADE-360 > Project: Maven Shade Plugin > Issue Type: Bug >Affects Versions: 3.2.3 >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > Fix For: 3.2.4 > > Time Spent: 20m > Remaining Estimate: 0h > > Because it uses PrintWriter and doesn't check error conditions -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSHADE-359) Remove dependency on Guava
[ https://issues.apache.org/jira/browse/MSHADE-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSHADE-359: - Affects Version/s: 3.2.3 > Remove dependency on Guava > -- > > Key: MSHADE-359 > URL: https://issues.apache.org/jira/browse/MSHADE-359 > Project: Maven Shade Plugin > Issue Type: Improvement >Affects Versions: 3.2.3 >Reporter: Elliotte Rusty Harold >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > There's some trivial usages that can be replaced by standard JDK classes and > apache commons collections -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSHADE-359) Remove dependency on Guava
[ https://issues.apache.org/jira/browse/MSHADE-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSHADE-359: - Fix Version/s: 3.2.4 > Remove dependency on Guava > -- > > Key: MSHADE-359 > URL: https://issues.apache.org/jira/browse/MSHADE-359 > Project: Maven Shade Plugin > Issue Type: Improvement >Affects Versions: 3.2.3 >Reporter: Elliotte Rusty Harold >Priority: Minor > Fix For: 3.2.4 > > Time Spent: 10m > Remaining Estimate: 0h > > There's some trivial usages that can be replaced by standard JDK classes and > apache commons collections -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSHADE-364) Don't log as duplicate resource handled by a transformer
[ https://issues.apache.org/jira/browse/MSHADE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSHADE-364: - Fix Version/s: 3.2.4 > Don't log as duplicate resource handled by a transformer > > > Key: MSHADE-364 > URL: https://issues.apache.org/jira/browse/MSHADE-364 > Project: Maven Shade Plugin > Issue Type: Task >Affects Versions: 3.2.3 >Reporter: Romain Manni-Bucau >Priority: Major > Fix For: 3.2.4 > > > Follow up of MSHADE-306, when a transformer handles a resource, no need to > log it as duplicated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MSHADE-365) document Properties transformers available since 3.2.2 in separate table
Herve Boutemy created MSHADE-365: Summary: document Properties transformers available since 3.2.2 in separate table Key: MSHADE-365 URL: https://issues.apache.org/jira/browse/MSHADE-365 Project: Maven Shade Plugin Issue Type: Task Affects Versions: 3.2.2 Reporter: Herve Boutemy Assignee: Herve Boutemy Fix For: 3.2.4 see https://maven.apache.org/plugins/maven-shade-plugin/examples/resource-transformers.html they were added in 3.2.2 MSHADE-322, they are in a different package from others: having a separate table will be more accurate and more usable (they will be more visible) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MSHADE-365) document Properties transformers available since 3.2.2 in separate table
[ https://issues.apache.org/jira/browse/MSHADE-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105877#comment-17105877 ] Hudson commented on MSHADE-365: --- Build failed in Jenkins: Maven TLP » maven-shade-plugin » master #89 See https://builds.apache.org/job/maven-box/job/maven-shade-plugin/job/master/89/ > document Properties transformers available since 3.2.2 in separate table > > > Key: MSHADE-365 > URL: https://issues.apache.org/jira/browse/MSHADE-365 > Project: Maven Shade Plugin > Issue Type: Task >Affects Versions: 3.2.2 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.2.4 > > > see > https://maven.apache.org/plugins/maven-shade-plugin/examples/resource-transformers.html > they were added in 3.2.2 MSHADE-322, they are in a different package from > others: having a separate table will be more accurate and more usable (they > will be more visible) -- This message was sent by Atlassian Jira (v8.3.4#803005)
