[clean-plugin] Delete files with non-ASCII names created on Windows using clean on *nix
I have a resource file named "Mise à jour.pptx" under test/resources/pptx. The file was created on Windows, checked into CVS and checked out onto a Linux server. The filename on Linux now contains \o340 (which is the ISO-8859-1 / Win-1252 encoded value for the à). When running mvn -e clean on the project, I get (under maven-clean 2.5): [ERROR] Failed to execute goal org.apache.maven.plugins:maven-clean-plugin:2.5:clean (default-clean) on project [project-name]: Failed to clean project: Failed to delete /homes/[path-to-project]/[project-name]/target/checkout/src/test/resources/pptx -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-clean-plugin:2.5:clean (default-clean) on project [project-name]: Failed to clean project: Failed to delete /homes/[path-to-project]/[project-name]/target/checkout/src/test/resources/pptx 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:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:318) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) 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:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:414) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:357) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to clean project: Failed to delete /homes/[path-to-project]/[project-name]/target/checkout/src/test/resources/pptx at org.apache.maven.plugin.clean.CleanMojo.execute(CleanMojo.java:215) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) ... 19 more Caused by: java.io.IOException: Failed to delete /homes/[path-to-project]/[project-name]/target/checkout/src/test/resources/pptx at org.apache.maven.plugin.clean.Cleaner.delete(Cleaner.java:249) at org.apache.maven.plugin.clean.Cleaner.delete(Cleaner.java:191) at org.apache.maven.plugin.clean.Cleaner.delete(Cleaner.java:158) at org.apache.maven.plugin.clean.Cleaner.delete(Cleaner.java:158) at org.apache.maven.plugin.clean.Cleaner.delete(Cleaner.java:158) at org.apache.maven.plugin.clean.Cleaner.delete(Cleaner.java:158) at org.apache.maven.plugin.clean.Cleaner.delete(Cleaner.java:158) at org.apache.maven.plugin.clean.Cleaner.delete(Cleaner.java:158) at org.apache.maven.plugin.clean.Cleaner.delete(Cleaner.java:117) at org.apache.maven.plugin.clean.CleanMojo.execute(CleanMojo.java:193) ... 21 more On the previous version (2.4.1), the error message would specify the file name, but same basic message. I've changed the filename to replace the "à" with a plain "a" and it works (to verify that nothing about file contents, other parts of name, permissions, etc. were causing issues. and this is the work around that I will use). This seems to be a known Java limitation when not using the NIO.2 (JSR-203) classes: http://bugs.sun.com/view_bug.do?bug_id=6522199 http://bugs.sun.com/view_bug.do?bug_id=4899439 Am I understanding this correctly? If so, are there other workarounds (i.e. besides renaming files)? Thanks... jz - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: PDF Plugin custom properties do not appear
Hi Nikola,
Sorry it took me so long, but you wrote just when my vacation started...
I think this is a feature that was never implemented, as the docs [1]
only mention "... System properties, Maven project properties and some
date properties." that can be filtered, ie no custom properties.
However, given that this works fine with the site plugin I would call it
a bug really, consider filing an issue in jira:
http://jira.codehaus.org/browse/MPDF
cheers,
-Lukas
[1] http://maven.apache.org/plugins/maven-pdf-plugin/examples/filtering.html
Am 05.08.2013 11:29, schrieb Nikola Mishev:
Hi all,
I am trying to generate a PDF, but I face the following issue.
Although I do have properties defined in my pom.xml they are not properly
filtered in any type of content I use.
e.g. I have the property defined in pom.xml
My other value
If I use this property in pdf.xml it appears in the generated PDF, but if I
set it in an .apt.vm file as ${myProperty} it doesn't.
The apt file is also with .vm extension as documented on the site.
On the other hand properties as ${project.name} work fine.
Do you have an idea what am I missing?
Thanks,
Nikola
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Any way to generically specify a release version in a child POM when using the Maven release plugin?
@Bret, as you've figured out already, it works for non-jars. In case of a
war, you just add artifacts type (war). :-)
@Baptiste, yes, for the release itself. I find it even more practical to
have configuration for maven-release-plugin
true in project's pom.
Regards,
Ziga Gregoric
On Tue, Aug 20, 2013 at 10:44 PM, Baptiste Mathus wrote:
> Would need to check but maybe try adding -DautoVersionSubmodules=true so
> that all modules get released with that version.
>
> My 2 cents.
> Le 20 août 2013 19:54, "laredotornado-3" a
> écrit :
>
> > Hi,
> >
> > I'm using Maven 3.0.3. I have a multi-module project and want to use the
> > Maven release plugin (through Jenkins). When running release:prepare,
> the
> > process dies with the error
> >
> > Executing Maven: -B -f
> > /scratch/jenkins/workspace/subco/parent/pom.xml
> > -amd -pl org.mainco.subco:childModuleA
> -DdevelopmentVersion=38.0.1-SNAPSHOT
> > -DreleaseVersion=38.0.0 -Dusername=myuser -Dpassword=* -P prod -P
> > cloudbees -DskipTests -Dresume=false -DdryRun=true release:prepare
> > …
> > message : Failed to execute goal
> > org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli)
> on
> > project childModuleA: Can't release project due to non released
> > dependencies
> > :
> > org.mainco.subco:childModuleB:jar:38.0.0-SNAPSHOT:compile
> > org.mainco.subco:parent:pom:38.0.0-SNAPSHOT
> >
> >
> > Is there another way I can write the child dependency so that a release
> > version will be used? I could hard code things but then I would have to
> go
> > and update all my child poms every time I want to use the Maven release
> > plugin, which seems to defeat the purpose.
> >
> > The problematic child module (similar to others) is setup like so …
> >
> > childModuleA
> > jar
> > ...
> >
> > parent
> > org.mainco.subco
> > 38.0.0-SNAPSHOT
> >
> > ...
> >
> > ...
> >
> > org.mainco.subco
> > childModuleB
> > ${project.version}
> >
> >
> >
> >
> > Thanks, - Dave
> >
> >
> >
> > --
> > View this message in context:
> >
> http://maven.40175.n5.nabble.com/Any-way-to-generically-specify-a-release-version-in-a-child-POM-when-using-the-Maven-release-plugin-tp5768328.html
> > Sent from the Maven - Users mailing list archive at Nabble.com.
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>
