Re: Resource plugin - LifecycleExecutionException - Input length = 1
Hi, On 12.08.20 21:44, Tobias wrote: Hi, a new version of the maven-resources-plugin (3.2.0) has been released recently. Trying to take advantage of this I added org.apache.maven.plugins maven-resources-plugin 3.2.0 org.apache.maven.shared maven-filtering 3.2.0 org.apache.maven.shared maven-shared-utils 3.3.3 to the pom.xml file (the version of maven-resources-plugin had not been specified before). This is the most important thing you should always define the versions of all your plugins. I don't understand why you have defined maven-shared-utils, and maven-filtering as plugins? Cause they are no plugins. And not needed by usual project... Apart from I recommend to make a directory where the filtered resources can be put into. I use the usual resources directory. A separate directory which contains the files which should not being filtered like `non-filtered-resources` that makes the configuration easier and makes very clear for users what is being done. Kind regards Karl Heinz Marbaise When running maven I see in the output that now version 3.2.0 of the resource plugin is used (before it was 2.x). However, it now results in the following error : Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:testResources (default-testResources) on project XXX: Input length = 1 See [2] below for a more detailed stack trace. Do you know what goes wrong and how this can be fixed? [Help1] says that "The concrete meaning of the exception depends on the plugin so please have a look at its documentation." I took at look at [1] but didn't find "Input length = 1" mentioned somewhere - could you maybe point me to the right direction? Unfortunately, I can't share the the full pom. I hope this information is sufficient. Best regards Tobias [1] https://maven.apache.org/plugins/maven-resources-plugin/index.html [2] 11:46:07,007 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:testResources (default-testResources) on project XXX: Input length = 1 -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:testResources (default-testResources) on project XXX: Input length = 1 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:218) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:151) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:115) at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder.lambda$createBuildCallable$0 (MultiThreadedBuilder.java:191) at java.util.concurrent.FutureTask.run (FutureTask.java:266) at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511) at java.util.concurrent.FutureTask.run (FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624) at java.lang.Thread.run (Thread.java:748) Caused by: org.apache.maven.plugin.MojoExecutionException: Input length = 1 at org.apache.maven.plugins.resources.ResourcesMojo.execute (ResourcesMojo.java:362) at org.apache.maven.plugins.resources.TestResourcesMojo.execute (TestResourcesMojo.java:75) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:136) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:151) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:115) at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder.lambda$createBuildCallable$0 (MultiThreadedBuilder.java:191) at java.util.concurrent.FutureTask.run (FutureTask.java:266) at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511) at java.util.concurrent.FutureTask.run (FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624) at java.lang.Thread.run (Thread.java:748) Caused by: org.apache.maven.shared.filtering.MavenFilteringException: Input length = 1 at org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile (DefaultMavenFileFilter.java:113) at org.apache.maven.shared.filtering.DefaultMavenResourcesFi
Re: Resource plugin - LifecycleExecutionException - Input length = 1
Op wo 12 aug. 2020 om 21:47 schreef Tobias : > > > Failed to execute goal > org.apache.maven.plugins:maven-resources-plugin:3.2.0:testResources > (default-testResources) on project XXX: Input length = 1 > > See [2] below for a more detailed stack trace. > > Do you know what goes wrong and how this can be fixed? > > I ran into this as well, after updating the list of " nonFilteredFileExtensions" this seems to be fixed, see eg. https://github.com/B3Partners/brmo/pull/901/files run "mvn -X process-test-resources" to get the list of filtered files -- Disclaimer; This message is just a reflection of what I thought at the time of sending. The message may contain information that is not intended for you or that you don't understand.
Re: resource plugin and empty directories
There's a feature request for it in JIRA: http://jira.codehaus.org/browse/MRESOURCES-36 AsafM wrote: I couldn't find any option to make this plugin copy empty directories. Any chance the developers solved that? Wayne Fay wrote: Not sure if this is currently possible. Check the source code to see what configuration options are available and perhaps you'll find something. If its not already implemented in the resource plugin, I have to imagine it would be a pretty simple modification (with an added variable copyEmptyDirectories, default to false) to add this functionality and provide a patch back to the project. Wayne On 3/27/06, Kevin Galligan <[EMAIL PROTECTED]> wrote: Is there any way to get the resource plugin to copy empty directories (I assume its the resource plugin when doing a jar packaged build). Long story as to why I'd need this. Thanks, -Kevin -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: resource plugin and empty directories
I couldn't find any option to make this plugin copy empty directories. Any chance the developers solved that? Wayne Fay wrote: > > Not sure if this is currently possible. Check the source code to see > what configuration options are available and perhaps you'll find > something. > > If its not already implemented in the resource plugin, I have to > imagine it would be a pretty simple modification (with an added > variable copyEmptyDirectories, default to false) to add this > functionality and provide a patch back to the project. > > Wayne > > > On 3/27/06, Kevin Galligan <[EMAIL PROTECTED]> wrote: >> Is there any way to get the resource plugin to copy empty directories (I >> assume its the resource plugin when doing a jar packaged build). Long >> story >> as to why I'd need this. >> >> Thanks, >> -Kevin >> >> > > -- View this message in context: http://www.nabble.com/resource-plugin-and-empty-directories-tp3619573p18868167.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Resource plugin copying files which end up not being binary compatible
Found out why - i had property filtering on over the entire directory. Disable for the specific binary file and all works. Is this something the resources plugin should check for? Is there any use case when binary files would be able to be filtered? Cam Cam wrote: Hi, I'm using the maven resources plugin to copy some binary files to the target directory however after copying the target file is not binary compatible with the original. I'm guessing this is because the resources plugin changes the character encoding, unfortunately i can't set the encoding to use because its in an old ibm format which isn't even ASCII. I guess my question is why does the resources plugin even convert files when copying? Does anyone have any workarounds for copying files? What's also funny is that it works on osx but fails on linux... any help is much appreciated, cam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Resource Plugin
Hey,
I wasn't so much knocking the documentation. I ended up finding this info in
the pom model. I found it kind of difficult to find actually.
D-
-Original Message-
From: franz see [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 12, 2006 4:23 AM
To: users@maven.apache.org
Subject: Re: Resource Plugin
Douglas Ferguson wrote:
>
> I can't find any documentation on how to change the default location of
> the
> resources plugin.
>
>
>
> I checked out the code and it declares ${project.resources}.
> But this is a list of resource objects. I'd like to just change the
> directory from ${basedir}/src/main/resources ->
> ${basedir}/${someotherdir}/src/main/resources
>
>
>
>
>
> __
>
>
> Douglas W. Ferguson
>
> EPSIIA - Another Fiserv Connection
>
> Development
>
> Office Phone: 512-329-0081 ext. 3309
>
> Dial Toll Free: 800-415-5946
>
> Mobile Phone: 512-293-7279
>
> Fax: 512-329-0086
>
> [EMAIL PROTECTED]
>
> www.epsiia.com <http://www.epsiia.com/>
>
> __
>
>
>
>
>
Good day to you Douglas,
You can try out [1] for more info regarding maven-resources-plugin. That
documentation is still being reviewed and is still not final, but it's good
enough (i think).
Anyway, to answer your question add the following to your pom:
[...]
[..a resource directory...]
[..another resource directory...]
[...]
Also, if you have some comments regarding the documentation, it would be
greatly appreciated ^_^
Thanks a bunch and goodluck to you
- Franz
Ref:
[1] http://people.apache.org/~aramirez/maven-resources-plugin/
--
View this message in context:
http://www.nabble.com/Resource-Plugin-tf2092205.html#a5774084
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Resource Plugin
Douglas Ferguson wrote:
>
> I can't find any documentation on how to change the default location of
> the
> resources plugin.
>
>
>
> I checked out the code and it declares ${project.resources}.
> But this is a list of resource objects. I'd like to just change the
> directory from ${basedir}/src/main/resources ->
> ${basedir}/${someotherdir}/src/main/resources
>
>
>
>
>
> __
>
>
> Douglas W. Ferguson
>
> EPSIIA - Another Fiserv Connection
>
> Development
>
> Office Phone: 512-329-0081 ext. 3309
>
> Dial Toll Free: 800-415-5946
>
> Mobile Phone: 512-293-7279
>
> Fax: 512-329-0086
>
> [EMAIL PROTECTED]
>
> www.epsiia.com
Re: resource plugin and empty directories
Not sure if this is currently possible. Check the source code to see what configuration options are available and perhaps you'll find something. If its not already implemented in the resource plugin, I have to imagine it would be a pretty simple modification (with an added variable copyEmptyDirectories, default to false) to add this functionality and provide a patch back to the project. Wayne On 3/27/06, Kevin Galligan <[EMAIL PROTECTED]> wrote: > Is there any way to get the resource plugin to copy empty directories (I > assume its the resource plugin when doing a jar packaged build). Long story > as to why I'd need this. > > Thanks, > -Kevin > >
