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 (DefaultM
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.
Resource plugin - LifecycleExecutionException - Input length = 1
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). 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.DefaultMavenResourcesFiltering.filterResources (DefaultMavenResourcesFiltering.java:262) at org.apache.maven.plugins.resources.ResourcesMojo.execute (ResourcesMojo.java:356) 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
Problem with the resource-plugin v2.7 and nonFilteredFileExtensions
Hi there, we just tried to update our usage of the maven-resource-plugin to Version 2.7 but afterwards the build failed with the following error message: Failed to execute goal org.apache.maven.plugins:maven-resource-plugin:2.7:resource (default resources) on project XYZ: Mark invalid - [Help 1] While my researches I could not find any changes to the usage of this. So I wonder if there is a bug in the new version or if we did anything wrong. It works fine with Version 2.4. and 2.6. Here the code of our pom file. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId version2.7/version configuration nonFilteredFileExtensions nonFilteredFileExtensionwoff/ nonFilteredFileExtension nonFilteredFileExtensioneot/ nonFilteredFileExtension nonFilteredFileExtensionttf/ nonFilteredFileExtension nonFilteredFileExtensionsvg/ nonFilteredFileExtension /nonFilteredFileExtensions /configuration /plugin Thanks a lot for the help! And best regards Michael Michael Lemler. Software Engineer.
Re: Problem with the resource-plugin v2.7 and nonFilteredFileExtensions
Hi, first thanks for going so fast to a new version and finding this issue...if it really is one... On 10/6/14 12:04 PM, Michael Lemler wrote: Hi there, we just tried to update our usage of the maven-resource-plugin to Version 2.7 but afterwards the build failed with the following error message: Failed to execute goal org.apache.maven.plugins:maven-resource-plugin:2.7:resource (default resources) on project XYZ: Mark invalid - [Help 1] I assume that you are using filtering apart from that I assume you are filtering files which should not being filtered cause this means files are being filtered which have encoding characters which can't correctly copied.. (filtered). I can reproduce the problem if i miss to add an .img extension to my pom file, cause .img is a kind of binary file which is being filtered but should NOT... If i add the appropriate nonFilteredFileExtensionimg/nonFilteredFileExtension It works without any problem... Please check the failing build via mvn -X output and search for the filtering locations in the output...like the following: [DEBUG] ignoreDelta true [INFO] Copying 3 resources [DEBUG] file duke-beerjpg.img has a filtered file extension [DEBUG] filtering /Users/kama/apache-maven/maven-plugins/maven-resources-plugin/target/it/possible-bug/src/main/resources/duke-beerjpg.img to /Users/kama/apache-maven/maven-plugins/maven-resources-plugin/target/it/possible-bug/target/classes/duke-beerjpg.img In this case i have a file duke-beerjpg.img which is filtered but should not being filter which is causing the failure... In this case it means that i have to fix my build and add the appropriate nonFilteredFileExtension...to prevent filtering of such files... While my researches I could not find any changes to the usage of this. So I wonder if there is a bug in the new version or if we did anything wrong. It works fine with Version 2.4. and 2.6. Here the code of our pom file. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId version2.7/version configuration nonFilteredFileExtensions nonFilteredFileExtensionwoff/ nonFilteredFileExtension nonFilteredFileExtensioneot/ nonFilteredFileExtension nonFilteredFileExtensionttf/ nonFilteredFileExtension nonFilteredFileExtensionsvg/ nonFilteredFileExtension /nonFilteredFileExtensions /configuration /plugin Thanks a lot for the help! And best regards Michael Michael Lemler. Software Engineer. Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven resource plugin
You need to move the configuration section into the execution you want it for. The current setup will also affect default lifecycle bindings of the resources plugin. /Anders On Thu, Oct 4, 2012 at 12:44 AM, sudha sudha...@gmail.com wrote: Hi, I'm trying to use maven resource plugin to copy and filter some property files from one directory to another ( not src/main/resources ). The source directory ( in this case configuration directory under basedir) has just one property file. When I do a mvn install, it creates the configuration_filtered directory but also copies a html file present in src/main/java to configuration_filtered. This should not happen. The html file should be copied to WEB-INF. Can someone help?, please. This is my plugin code: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId version2.6/version executions execution idcopy-resources-1/id phasepackage/phase goals goal copy-resources /goal /goals /execution /executions configuration outputDirectory${basedir}/configuration_filtered/outputDirectory resources resource directory${basedir}/configuration/directory includes include **/*.properties /include include **/*.xml /include /includes excludes exclude **/*.html /exclude /excludes filteringtrue/filtering /resource /resources buildFilters buildFilter${basedir}/tokenfile.dev/buildFilter /buildFilters useBuildFilterstrue/useBuildFilters delimiters delimiter${*}/delimiter delimiter@/delimiter /delimiters /configuration /plugin -Thanks -- View this message in context: http://maven.40175.n5.nabble.com/Maven-resource-plugin-tp5724796.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven resource plugin
Thanks. That worked. -- View this message in context: http://maven.40175.n5.nabble.com/Maven-resource-plugin-tp5724796p5724909.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
Maven resource plugin
Hi, I'm trying to use maven resource plugin to copy and filter some property files from one directory to another ( not src/main/resources ). The source directory ( in this case configuration directory under basedir) has just one property file. When I do a mvn install, it creates the configuration_filtered directory but also copies a html file present in src/main/java to configuration_filtered. This should not happen. The html file should be copied to WEB-INF. Can someone help?, please. This is my plugin code: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId version2.6/version executions execution idcopy-resources-1/id phasepackage/phase goals goal copy-resources /goal /goals /execution /executions configuration outputDirectory${basedir}/configuration_filtered/outputDirectory resources resource directory${basedir}/configuration/directory includes include **/*.properties /include include **/*.xml /include /includes excludes exclude **/*.html /exclude /excludes filteringtrue/filtering /resource /resources buildFilters buildFilter${basedir}/tokenfile.dev/buildFilter /buildFilters useBuildFilterstrue/useBuildFilters delimiters delimiter${*}/delimiter delimiter@/delimiter /delimiters /configuration /plugin -Thanks -- View this message in context: http://maven.40175.n5.nabble.com/Maven-resource-plugin-tp5724796.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
Resource-Plugin
Hi all, I was playing around with the resource-plugin to copy several resources around in my project, and found a problem with the plugin. It appears that the parameter 'includeEmptyDirs' is not always (!) being obeyed. From what I can see, it works when I configure several resources and do NOT specify a 'targetPath' on them. The problem is that I don't want all resources in the same location. As a workaround I now define several executions, but I was wondering if this is a known issue and if others may have found another way to accomplish this. If nobody ever noticed, I might create a JIRA and maybe attach a patch for it. Thanks. -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 A-1210 Wien M +43 664 88657566 E roland.asm...@adesso.at W www.adesso.at - business. people. technology. - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[Resource plugin] Copy resource from other module
Hi, I tried to use Resource plugin with copy goal to copy resources from another module to current module : build plugins plugin artifactIdmaven-resources-plugin/artifactId version2.4.3/version executions execution idcopy-resources/id !-- here the phase you need -- phasevalidate/phase goals goalcopy-resources/goal /goals configuration outputDirectory${basedir}/extra-resources/outputDirectory resources resource directory${basedir}/../other-module/src/main/resources/directory filteringtrue/filtering /resource /resources /configuration /execution /executions /plugin /plugins But it seems that we are stuck to the basedir...can anyone confirm this ? Thank you
Re: Strange behaviour on resource plugin
Hi! fond it by myself: The -X helps a lot in between. The properties were specified in a profile which was not active when running from the command line. Sorry for bothering you! On 10/19/2010 04:09 PM, Søren Krum wrote: Hi! I have detected a strange bahaviour of the maven resource plugin, and i am wondering if someone can give me a hint, what is going wrong here. One of my maven projects uses the resource plugin to copy some configuration files with some placeholders in them. When running maven from eclipse, the placeholders are nicely replaced with some values from the pom file, but when starting maven from the console, this replacement does not take place. My eclipse uses a maven 3.0 snapshot, while i tried maven 2.2.1 and 3.0 from the command line, both not eager to do the replacement. To make this behaviour even stranger, i detected this failing replacement after i updated my os from ubuntu 8/04 to 10/04, but i have no idea if that is really connected. I did not touch the maven installations at all, so it is a bit confusing Any idea is highly welcome :-) -- Med vennlig hilsen Søren D. Krum Systemutvikler/system developer UNINETT FAS + 47 73557859 There are 10 different kind of people in the world, those who understand binary and those who don't - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Strange behaviour on resource plugin
Hi! I have detected a strange bahaviour of the maven resource plugin, and i am wondering if someone can give me a hint, what is going wrong here. One of my maven projects uses the resource plugin to copy some configuration files with some placeholders in them. When running maven from eclipse, the placeholders are nicely replaced with some values from the pom file, but when starting maven from the console, this replacement does not take place. My eclipse uses a maven 3.0 snapshot, while i tried maven 2.2.1 and 3.0 from the command line, both not eager to do the replacement. To make this behaviour even stranger, i detected this failing replacement after i updated my os from ubuntu 8/04 to 10/04, but i have no idea if that is really connected. I did not touch the maven installations at all, so it is a bit confusing Any idea is highly welcome :-) -- Med vennlig hilsen Søren D. Krum Systemutvikler/system developer UNINETT FAS + 47 73557859 There are 10 different kind of people in the world, those who understand binary and those who don't - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Strange behaviour on resource plugin
I have detected a strange bahaviour of the maven resource plugin, and i am wondering if someone can give me a hint, what is going wrong here. Did you lock down the version of m-r-p in your pom? If not, you really have no control over what version is being used, and it is possible that you have run into some change in functionality or a bug that is causing this behaviour. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Strange behaviour on resource plugin
Hello, Do you define the version of maven-resources-plugin in your pom ? Are you using profiles? 2010/10/19 Søren Krum soren.k...@uninett.no Hi! I have detected a strange bahaviour of the maven resource plugin, and i am wondering if someone can give me a hint, what is going wrong here. One of my maven projects uses the resource plugin to copy some configuration files with some placeholders in them. When running maven from eclipse, the placeholders are nicely replaced with some values from the pom file, but when starting maven from the console, this replacement does not take place. My eclipse uses a maven 3.0 snapshot, while i tried maven 2.2.1 and 3.0 from the command line, both not eager to do the replacement. To make this behaviour even stranger, i detected this failing replacement after i updated my os from ubuntu 8/04 to 10/04, but i have no idea if that is really connected. I did not touch the maven installations at all, so it is a bit confusing Any idea is highly welcome :-) -- Med vennlig hilsen Søren D. Krum Systemutvikler/system developer UNINETT FAS + 47 73557859 There are 10 different kind of people in the world, those who understand binary and those who don't - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Vincent
Maven Resource plugin help
Hello everyone, In my maven pom, I have profiles defined and I have a environment file which changes a variable according to the profile name. When I build maven within my SpringSource Tool Suite, in my target folder, the variable defined in the environment file doesnt not change according to the profile name. But in my target / project/environment.conf file, I do see the change. When I try to use mvn clean install command from the command prompt, It still does not change. what could I be missing? Thanks and Regards, Meenakshi
Writing a plugin, intercepting resource plugin...
Hello, I am thinking about a plugin, that when present in a maven pom plugins set should automatically adds some special source and target folder to the resources plugin, so that some special resources are copied without having to configure them in the resources plugin itself. How do I do that ? Cheers, Kai - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Writing a plugin, intercepting resource plugin...
I am thinking about a plugin, that when present in a maven pom plugins set should automatically adds some special source and target folder to the resources plugin, so that some special resources are copied without having to configure them in the resources plugin itself. How do I do that ? Perhaps doable via a profile. I'd try that route before going for a plugin. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Remote resource plugin doesn't work in release plugin
use maven plugin like this mvn somePlugin:goal -Dparam=value in cmd the param should be the param of somePlugin supply? And, the ${variable} in the pom file,it should be a variable which maven can know it, it can be a environment variable of OS or a property file configed in the pom hope help you , Please forgive my poor English - - 2009/11/17 Max Grigoriev max.grigor...@webamg.com Hi everybody, I have a project which uses remote-resources (hibernate mapping files). My pom.xml ... plugin artifactIdmaven-remote-resources-plugin/artifactId version1.1/version executions execution goals goalprocess/goal /goals configuration resourceBundles resourceBundlecom.myproj.sws2:sws-mapping:${sws.mapping.version}/resourceBundle /resourceBundles outputDirectory${project.build.directory}/outputDirectory attachedfalse/attached /configuration /execution /executions /plugin ... plugin artifactIdmaven-release-plugin/artifactId version2.0-beta-9/version configuration tagBasehttps://path-to-svn/tags/tagBase /configuration /plugin ... When I make mvn package -Dsws.mapping.version=2.0.0 - everything's ok and resources are resolved and downloaded also they are put to WAR file. But when I try to release this project: mvn release:clean release:prepare -Dsws.mapping.version=2.0.0 -Dusername=svn_user -Dpassword=svn_passwd And I receive error: [INFO] [INFO] [remote-resources:process {execution: default}] [INFO] [WARNING] Unable to get resource 'com.myproj.sws2:sws-mapping:jar:null' from repository myrep ( http://maven.myrepcom:8081): While configuring wagon for 'mavuser': Unable to apply wagon configuration. [INFO] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] [INFO] [INFO] Resources JAR cannot be found. As you can see, resource version is unset - 'com.myproj.sws2:sws-mapping:jar:null'. Why my property (sws.mapping.version) is null not 2.0.0 as I set in command line ? Thanks -- alien.sulin(苏琳冲) SuLinchong Qq387973308 Msn sulinch...@hotmail.com
Remote resource plugin doesn't work in release plugin
Hi everybody, I have a project which uses remote-resources (hibernate mapping files). My pom.xml ... plugin artifactIdmaven-remote-resources-plugin/artifactId version1.1/version executions execution goals goalprocess/goal /goals configuration resourceBundles resourceBundlecom.myproj.sws2:sws-mapping:${sws.mapping.version}/resourceBundle /resourceBundles outputDirectory${project.build.directory}/outputDirectory attachedfalse/attached /configuration /execution /executions /plugin ... plugin artifactIdmaven-release-plugin/artifactId version2.0-beta-9/version configuration tagBasehttps://path-to-svn/tags/tagBase /configuration /plugin ... When I make mvn package -Dsws.mapping.version=2.0.0 - everything's ok and resources are resolved and downloaded also they are put to WAR file. But when I try to release this project: mvn release:clean release:prepare -Dsws.mapping.version=2.0.0 -Dusername=svn_user -Dpassword=svn_passwd And I receive error: [INFO] [INFO] [remote-resources:process {execution: default}] [INFO] [WARNING] Unable to get resource 'com.myproj.sws2:sws-mapping:jar:null' from repository myrep (http://maven.myrepcom:8081): While configuring wagon for 'mavuser': Unable to apply wagon configuration. [INFO] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] [INFO] [INFO] Resources JAR cannot be found. As you can see, resource version is unset - 'com.myproj.sws2:sws-mapping:jar:null'. Why my property (sws.mapping.version) is null not 2.0.0 as I set in command line ? Thanks
Maven Resource Plugin - Filtering: How to configure custom Token to be filtered
Hi, i want to migrate from antmod to maven. I wonder if it is possible to configure additional tokens to replace my property placeholders ( not only @...@ and ${} ). I want to replace $$ ones. I've read http://maven.apache.org/shared/maven-filtering/usage.html but looking at latest trunk or beta3 of the maven shared component the docs mention MavenProjectValueSource which is gone already and does only exist in beta2 anymore (exists only up to revision 806645). So what would be the best way to get my custom token filtered? Is it configurable or have i have to write my own resource mojo (against trunk version or beta3, what must be done as the example is outdated, isn't it?). thx for help Torsten -- Bitte senden Sie mir keine Word- oder PowerPoint-Anhänge. Siehe http://www.gnu.org/philosophy/no-word-attachments.de.html Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect. -- Linus Torvalds smime.p7s Description: S/MIME cryptographic signature
Re: Maven Resource Plugin - Filtering: How to configure custom Token to be filtered
Hi, Have a look at delimiters [1] parameters in the resources mojo HTH, -- Olivier http://maven.apache.org/plugins/maven-resources-plugin/resources-mojo.html#delimiters 2009/9/24 Torsten Krah tk...@fachschaft.imn.htwk-leipzig.de: Hi, i want to migrate from antmod to maven. I wonder if it is possible to configure additional tokens to replace my property placeholders ( not only @...@ and ${} ). I want to replace $$ ones. I've read http://maven.apache.org/shared/maven-filtering/usage.html but looking at latest trunk or beta3 of the maven shared component the docs mention MavenProjectValueSource which is gone already and does only exist in beta2 anymore (exists only up to revision 806645). So what would be the best way to get my custom token filtered? Is it configurable or have i have to write my own resource mojo (against trunk version or beta3, what must be done as the example is outdated, isn't it?). thx for help Torsten -- Bitte senden Sie mir keine Word- oder PowerPoint-Anhänge. Siehe http://www.gnu.org/philosophy/no-word-attachments.de.html Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect. -- Linus Torvalds -- Olivier - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Resource Plugin - Filtering: How to configure custom Token to be filtered
Am Donnerstag, 24. September 2009 13:55:08 schrieb Olivier Lamy: Have a look at delimiters [1] parameters in the resources mojo Hi, thx for this hint. Did have a look there - delimiters does sounds nice (i need to turn off useDefaultDelimiters to get them respected), however its not working as expected (at least expected by me ;-)). plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId version2.4/version configuration useDefaultDelimitersfalse/useDefaultDelimiters delimiters delimiter$/delimiter delimiter@/delimiter delimiter#/delimiter delimiter${*}/delimiter /delimiters encodingUTF-8/encoding /configuration /plugin Using this i get a NullPointerException: java.lang.NullPointerException at org.codehaus.plexus.interpolation.multi.DelimiterSpecification.parse(DelimiterSpecification.java:54) at org.codehaus.plexus.interpolation.multi.MultiDelimiterStringSearchInterpolator.setDelimiterSpecs(MultiDelimiterStringSearchInterpolator.java:394) Removing the ${*} (although the docs does mention it as valid and i would like to use it too) it runs but not working like expected: Some exampled i tried: mvn clean resources:resource -Dtest.value=true As example using this property file: test.value=$test.value$ test.value=#test.value# test.val...@test.value@ test.value=${test.value} Using only: delimiter$/delimiter delimiter@/delimiter i get this result: test.value=true test.value=#test.value# test.value=true test.value=${test.value} Using this one: delimiter$/delimiter delimiter@/delimiter delimiter#/delimiter the result is: test.value=true test.value=#test.value# test.val...@test.value@ test.value=${test.value} Whats wrong here? Did i miss something or is my plugin configuration incorrect? Might this be a bug? Torsten -- Bitte senden Sie mir keine Word- oder PowerPoint-Anhänge. Siehe http://www.gnu.org/philosophy/no-word-attachments.de.html Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect. -- Linus Torvalds smime.p7s Description: S/MIME cryptographic signature
Re: Maven Resource Plugin - Filtering: How to configure custom Token to be filtered
probably a bug. (I have to investigate more) Can you create a issue [1] and attach a simple project to reproduce the issue. Thanks ! -- Olivier [1] http://jira.codehaus.org/browse/MRESOURCES 2009/9/24 Torsten Krah tk...@fachschaft.imn.htwk-leipzig.de: Am Donnerstag, 24. September 2009 13:55:08 schrieb Olivier Lamy: Have a look at delimiters [1] parameters in the resources mojo Hi, thx for this hint. Did have a look there - delimiters does sounds nice (i need to turn off useDefaultDelimiters to get them respected), however its not working as expected (at least expected by me ;-)). plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId version2.4/version configuration useDefaultDelimitersfalse/useDefaultDelimiters delimiters delimiter$/delimiter delimiter@/delimiter delimiter#/delimiter delimiter${*}/delimiter /delimiters encodingUTF-8/encoding /configuration /plugin Using this i get a NullPointerException: java.lang.NullPointerException at org.codehaus.plexus.interpolation.multi.DelimiterSpecification.parse(DelimiterSpecification.java:54) at org.codehaus.plexus.interpolation.multi.MultiDelimiterStringSearchInterpolator.setDelimiterSpecs(MultiDelimiterStringSearchInterpolator.java:394) Removing the ${*} (although the docs does mention it as valid and i would like to use it too) it runs but not working like expected: Some exampled i tried: mvn clean resources:resource -Dtest.value=true As example using this property file: test.value=$test.value$ test.value=#test.value# test.val...@test.value@ test.value=${test.value} Using only: delimiter$/delimiter delimiter@/delimiter i get this result: test.value=true test.value=#test.value# test.value=true test.value=${test.value} Using this one: delimiter$/delimiter delimiter@/delimiter delimiter#/delimiter the result is: test.value=true test.value=#test.value# test.val...@test.value@ test.value=${test.value} Whats wrong here? Did i miss something or is my plugin configuration incorrect? Might this be a bug? Torsten -- Bitte senden Sie mir keine Word- oder PowerPoint-Anhänge. Siehe http://www.gnu.org/philosophy/no-word-attachments.de.html Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect. -- Linus Torvalds -- Olivier - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Custom lifecycle. Changing the default resource plugin confiduration.
Martin, Using an archetype for this is a good workaround. I may actually make an archetype for this kind of projects. I ended up writing a mojo and binding it to the initialize phase. In this mojo I change the output directory. This seems to work fine. Muchas gracias por tu ayuda. Cheers. Erick. On Mon, Jun 15, 2009 at 5:49 PM, Martin Gainty mgai...@hotmail.com wrote: http://maven.apache.org/plugins/maven-archetype-plugin/examples/create-with-property-file.html create the archetype with included properties to create a catalog $ cat archetype.properties archetype.groupId=my.group.id archetype.artifactId=archetype-with-properties archetype.version=2.0 archetype.filteredExtensions=java archetype.languages=groovy an_additional_property=my specific value output-directory=/usr/erick/theme //create archetype $ cd some-project $ mvn archetype:create-from-project -Darchetype.properties=../archetype.properties //install the archetype $ cd target/generated-sources/archetype/ $ mvn install //run it $ mvn archetype:generate -DarchetypeCatalog=local Ayuda? Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 15 Jun 2009 14:42:13 -0400 Subject: Re: Custom lifecycle. Changing the default resource plugin confiduration. From: edov...@gmail.com To: users@maven.apache.org As a last resource solution yes. The thing is I don't want to force the clients of the plugin to have to do this. instead i just want them to declared an specific packaging type and that's it. Unfortunately they will have to still define the my theme plugin in their poms.xml as it needs to have the extensions parameter set to true; but forcing them to also define the resources plugin to change this particular configuration parameter is plain wrong. There most be another way of doing this that does not involve the clients of the plugins doing anything special; that's what I am looking for. Gracias nuevamente. Erick. On Mon, Jun 15, 2009 at 2:15 PM, Martin Gainty mgai...@hotmail.com wrote: de nada can you use a configuration parameter for output-directory? plugin groupIdsample.plugin/groupId artifactIdmaven-erick-plugin/artifactId version1.0/version configuration output-directorytheme/output-directory /configuration /plugin http://maven.apache.org/guides/plugin/guide-java-plugin-development.html Quizas? Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 15 Jun 2009 13:50:32 -0400 Subject: Re: Custom lifecycle. Changing the default resource plugin confiduration. From: edov...@gmail.com To: users@maven.apache.org *Martin, I don't think that will work here as maven it self is the one calling the copy-resources goal on the resources-plugin. What I need is a declarative way to pass the output directory into maven from within my plugin
RE: Custom lifecycle. Changing the default resource plugin confiduration.
glad to hear the custom mojo solution is working for you Saludos Cordiales desde EEUU! Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Tue, 16 Jun 2009 10:12:00 -0400 Subject: Re: Custom lifecycle. Changing the default resource plugin confiduration. From: edov...@gmail.com To: users@maven.apache.org Martin, Using an archetype for this is a good workaround. I may actually make an archetype for this kind of projects. I ended up writing a mojo and binding it to the initialize phase. In this mojo I change the output directory. This seems to work fine. Muchas gracias por tu ayuda. Cheers. Erick. On Mon, Jun 15, 2009 at 5:49 PM, Martin Gainty mgai...@hotmail.com wrote: http://maven.apache.org/plugins/maven-archetype-plugin/examples/create-with-property-file.html create the archetype with included properties to create a catalog $ cat archetype.properties archetype.groupId=my.group.id archetype.artifactId=archetype-with-properties archetype.version=2.0 archetype.filteredExtensions=java archetype.languages=groovy an_additional_property=my specific value output-directory=/usr/erick/theme //create archetype $ cd some-project $ mvn archetype:create-from-project -Darchetype.properties=../archetype.properties //install the archetype $ cd target/generated-sources/archetype/ $ mvn install //run it $ mvn archetype:generate -DarchetypeCatalog=local Ayuda? Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 15 Jun 2009 14:42:13 -0400 Subject: Re: Custom lifecycle. Changing the default resource plugin confiduration. From: edov...@gmail.com To: users@maven.apache.org As a last resource solution yes. The thing is I don't want to force the clients of the plugin to have to do this. instead i just want them to declared an specific packaging type and that's it. Unfortunately they will have to still define the my theme plugin in their poms.xml as it needs to have the extensions parameter set to true; but forcing them to also define the resources plugin to change this particular configuration parameter is plain wrong. There most be another way of doing this that does not involve the clients of the plugins doing anything special; that's what I am looking for. Gracias nuevamente. Erick. On Mon, Jun 15, 2009 at 2:15 PM, Martin Gainty mgai...@hotmail.com wrote: de nada can you use a configuration parameter for output-directory? plugin groupIdsample.plugin/groupId artifactIdmaven-erick-plugin/artifactId version1.0/version configuration output-directorytheme/output-directory /configuration /plugin http://maven.apache.org/guides/plugin/guide-java-plugin-development.html Quizas? Martin __ Verzicht und Vertraulichkeitanmerkung/Note de
Fwd: Custom lifecycle. Changing the default resource plugin confiduration.
Brett, I went through the doc you send me below but could nor find an answer to my question there. I have redefined the lifecycle in my components.xml as follows: component-set components component roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role role-hintcstheme/role-hint implementationorg.apache.maven.lifecycle.mapping.DefaultLifecycleMapping/implementation configuration phases process-resourcesorg.apache.maven.plugins:maven-resources-plugin:resources/process-resources packagecom.syncapse.clearspace:maven-theme-plugin:package/package installorg.apache.maven.plugins:maven-install-plugin:install/install /phases /configuration /component /components /component-set It is all working fine except for the fact that I need to resources plugin to output all the resources into a folder called theme instead of the default classes. This is to ease the creation of a zip file that most have all content inside one single directory at the root of the zip (the theme directory). How can I do this from inside a plugin?? Thanks a lot. Erick. -- Forwarded message -- From: Brett Porter br...@apache.org Date: Fri, Jun 12, 2009 at 11:57 PM Subject: Re: Custom lifecycle. Changing the default resource plugin confiduration. To: Maven Developers List d...@maven.apache.org This is still a more appropriate question for users@maven.apache.org, as this is the list for development on maven and its plugins itself. I'd be happy to follow up on the thread there. To help you along, you don't need to overwrite the default lifecycle - just bind different goals to it. You can't configure goals when you do that - I'm a bit unsure whether you are putting your plugin in there, or the resources plugin, or both. What you are likely looking to do is extend the resources plugin with the new configuration and functionality and bind that by default. An example of declaring a new packaging type is here: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/introduction/introduction-to-the-lifecycle.apt?revision=501590 On 13/06/2009, at 6:37 AM, Erick Dovale wrote: Folks, I am writing a plugin that builds an artifact that needs no compilation or tests whatsever as it is only resources. I am overwriting the default lifecycle to only run the resources phases, the packaging phases and the install phases. I need to change the resource plugin configuration to write the file to a folder other than classes. How can I achieve this from a plugin? Thanks. Erick. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: Custom lifecycle. Changing the default resource plugin confiduration.
Hi Erick could you call resources:copyResources -DoutputDirectory=/theme http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html ? Saludos Cordiales Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 15 Jun 2009 11:49:43 -0400 Subject: Fwd: Custom lifecycle. Changing the default resource plugin confiduration. From: edov...@gmail.com To: users@maven.apache.org Brett, I went through the doc you send me below but could nor find an answer to my question there. I have redefined the lifecycle in my components.xml as follows: component-set components component roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role role-hintcstheme/role-hint implementationorg.apache.maven.lifecycle.mapping.DefaultLifecycleMapping/implementation configuration phases process-resourcesorg.apache.maven.plugins:maven-resources-plugin:resources/process-resources packagecom.syncapse.clearspace:maven-theme-plugin:package/package installorg.apache.maven.plugins:maven-install-plugin:install/install /phases /configuration /component /components /component-set It is all working fine except for the fact that I need to resources plugin to output all the resources into a folder called theme instead of the default classes. This is to ease the creation of a zip file that most have all content inside one single directory at the root of the zip (the theme directory). How can I do this from inside a plugin?? Thanks a lot. Erick. -- Forwarded message -- From: Brett Porter br...@apache.org Date: Fri, Jun 12, 2009 at 11:57 PM Subject: Re: Custom lifecycle. Changing the default resource plugin confiduration. To: Maven Developers List d...@maven.apache.org This is still a more appropriate question for users@maven.apache.org, as this is the list for development on maven and its plugins itself. I'd be happy to follow up on the thread there. To help you along, you don't need to overwrite the default lifecycle - just bind different goals to it. You can't configure goals when you do that - I'm a bit unsure whether you are putting your plugin in there, or the resources plugin, or both. What you are likely looking to do is extend the resources plugin with the new configuration and functionality and bind that by default. An example of declaring a new packaging type is here: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/introduction/introduction-to-the-lifecycle.apt?revision=501590 On 13/06/2009, at 6:37 AM, Erick Dovale wrote: Folks, I am writing a plugin that builds an artifact that needs no compilation or tests whatsever as it is only resources. I am overwriting the default lifecycle to only run the resources phases, the packaging phases and the install phases. I need to change the resource plugin configuration to write the file to a folder other than classes. How can I achieve this from a plugin? Thanks. Erick. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org _ Insert movie times and more without leaving Hotmail®. http://windowslive.com/Tutorial/Hotmail/QuickAdd?ocid=TXT_TAGLM_WL_HM_Tutorial_QuickAdd_062009
Re: Custom lifecycle. Changing the default resource plugin confiduration.
*Martin, I don't think that will work here as maven it self is the one calling the copy-resources goal on the resources-plugin. What I need is a declarative way to pass the output directory into maven from within my plugin. Gracias. Erick * On Mon, Jun 15, 2009 at 1:32 PM, Martin Gainty mgai...@hotmail.com wrote: Hi Erick could you call resources:copyResources -DoutputDirectory=/theme http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html ? Saludos Cordiales Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 15 Jun 2009 11:49:43 -0400 Subject: Fwd: Custom lifecycle. Changing the default resource plugin confiduration. From: edov...@gmail.com To: users@maven.apache.org Brett, I went through the doc you send me below but could nor find an answer to my question there. I have redefined the lifecycle in my components.xml as follows: component-set components component roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role role-hintcstheme/role-hint implementationorg.apache.maven.lifecycle.mapping.DefaultLifecycleMapping/implementation configuration phases process-resourcesorg.apache.maven.plugins:maven-resources-plugin:resources/process-resources packagecom.syncapse.clearspace:maven-theme-plugin:package/package installorg.apache.maven.plugins:maven-install-plugin:install/install /phases /configuration /component /components /component-set It is all working fine except for the fact that I need to resources plugin to output all the resources into a folder called theme instead of the default classes. This is to ease the creation of a zip file that most have all content inside one single directory at the root of the zip (the theme directory). How can I do this from inside a plugin?? Thanks a lot. Erick. -- Forwarded message -- From: Brett Porter br...@apache.org Date: Fri, Jun 12, 2009 at 11:57 PM Subject: Re: Custom lifecycle. Changing the default resource plugin confiduration. To: Maven Developers List d...@maven.apache.org This is still a more appropriate question for users@maven.apache.org, as this is the list for development on maven and its plugins itself. I'd be happy to follow up on the thread there. To help you along, you don't need to overwrite the default lifecycle - just bind different goals to it. You can't configure goals when you do that - I'm a bit unsure whether you are putting your plugin in there, or the resources plugin, or both. What you are likely looking to do is extend the resources plugin with the new configuration and functionality and bind that by default. An example of declaring a new packaging type is here: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/introduction/introduction-to-the-lifecycle.apt?revision=501590 On 13/06/2009, at 6:37 AM, Erick Dovale wrote: Folks, I am writing a plugin that builds an artifact that needs no compilation or tests whatsever as it is only resources. I am overwriting the default lifecycle to only run the resources phases, the packaging phases and the install phases. I need to change the resource plugin configuration to write the file to a folder other than classes. How can I achieve this from a plugin? Thanks. Erick. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org _ Insert movie times and more without leaving Hotmail®. http://windowslive.com/Tutorial/Hotmail/QuickAdd?ocid=TXT_TAGLM_WL_HM_Tutorial_QuickAdd_062009
RE: Custom lifecycle. Changing the default resource plugin confiduration.
de nada can you use a configuration parameter for output-directory? plugin groupIdsample.plugin/groupId artifactIdmaven-erick-plugin/artifactId version1.0/version configuration output-directorytheme/output-directory /configuration /pluginhttp://maven.apache.org/guides/plugin/guide-java-plugin-development.html Quizas? Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 15 Jun 2009 13:50:32 -0400 Subject: Re: Custom lifecycle. Changing the default resource plugin confiduration. From: edov...@gmail.com To: users@maven.apache.org *Martin, I don't think that will work here as maven it self is the one calling the copy-resources goal on the resources-plugin. What I need is a declarative way to pass the output directory into maven from within my plugin. Gracias. Erick * On Mon, Jun 15, 2009 at 1:32 PM, Martin Gainty mgai...@hotmail.com wrote: Hi Erick could you call resources:copyResources -DoutputDirectory=/theme http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html ? Saludos Cordiales Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 15 Jun 2009 11:49:43 -0400 Subject: Fwd: Custom lifecycle. Changing the default resource plugin confiduration. From: edov...@gmail.com To: users@maven.apache.org Brett, I went through the doc you send me below but could nor find an answer to my question there. I have redefined the lifecycle in my components.xml as follows: component-set components component roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role role-hintcstheme/role-hint implementationorg.apache.maven.lifecycle.mapping.DefaultLifecycleMapping/implementation configuration phases process-resourcesorg.apache.maven.plugins:maven-resources-plugin:resources/process-resources packagecom.syncapse.clearspace:maven-theme-plugin:package/package installorg.apache.maven.plugins:maven-install-plugin:install/install /phases /configuration /component /components /component-set It is all working fine except for the fact that I need to resources plugin to output all the resources into a folder called theme instead of the default classes. This is to ease the creation of a zip file that most have all content inside one single directory at the root of the zip (the theme directory). How can I do this from inside a plugin?? Thanks a lot. Erick. -- Forwarded message -- From: Brett Porter br...@apache.org Date: Fri, Jun 12, 2009 at 11:57 PM Subject: Re: Custom lifecycle. Changing the default resource plugin confiduration. To: Maven Developers List d...@maven.apache.org This is still a more appropriate question for users@maven.apache.org, as this is the list
Re: Custom lifecycle. Changing the default resource plugin confiduration.
As a last resource solution yes. The thing is I don't want to force the clients of the plugin to have to do this. instead i just want them to declared an specific packaging type and that's it. Unfortunately they will have to still define the my theme plugin in their poms.xml as it needs to have the extensions parameter set to true; but forcing them to also define the resources plugin to change this particular configuration parameter is plain wrong. There most be another way of doing this that does not involve the clients of the plugins doing anything special; that's what I am looking for. Gracias nuevamente. Erick. On Mon, Jun 15, 2009 at 2:15 PM, Martin Gainty mgai...@hotmail.com wrote: de nada can you use a configuration parameter for output-directory? plugin groupIdsample.plugin/groupId artifactIdmaven-erick-plugin/artifactId version1.0/version configuration output-directorytheme/output-directory /configuration /plugin http://maven.apache.org/guides/plugin/guide-java-plugin-development.html Quizas? Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 15 Jun 2009 13:50:32 -0400 Subject: Re: Custom lifecycle. Changing the default resource plugin confiduration. From: edov...@gmail.com To: users@maven.apache.org *Martin, I don't think that will work here as maven it self is the one calling the copy-resources goal on the resources-plugin. What I need is a declarative way to pass the output directory into maven from within my plugin. Gracias. Erick * On Mon, Jun 15, 2009 at 1:32 PM, Martin Gainty mgai...@hotmail.com wrote: Hi Erick could you call resources:copyResources -DoutputDirectory=/theme http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html ? Saludos Cordiales Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 15 Jun 2009 11:49:43 -0400 Subject: Fwd: Custom lifecycle. Changing the default resource plugin confiduration. From: edov...@gmail.com To: users@maven.apache.org Brett, I went through the doc you send me below but could nor find an answer to my question there. I have redefined the lifecycle in my components.xml as follows: component-set components component roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role role-hintcstheme/role-hint implementationorg.apache.maven.lifecycle.mapping.DefaultLifecycleMapping/implementation configuration phases process-resourcesorg.apache.maven.plugins:maven-resources-plugin:resources/process-resources packagecom.syncapse.clearspace:maven-theme-plugin:package/package installorg.apache.maven.plugins:maven-install-plugin:install/install /phases /configuration /component
RE: Custom lifecycle. Changing the default resource plugin confiduration.
http://maven.apache.org/plugins/maven-archetype-plugin/examples/create-with-property-file.html create the archetype with included properties to create a catalog $ cat archetype.properties archetype.groupId=my.group.id archetype.artifactId=archetype-with-properties archetype.version=2.0 archetype.filteredExtensions=java archetype.languages=groovy an_additional_property=my specific value output-directory=/usr/erick/theme //create archetype $ cd some-project $ mvn archetype:create-from-project -Darchetype.properties=../archetype.properties //install the archetype $ cd target/generated-sources/archetype/ $ mvn install //run it $ mvn archetype:generate -DarchetypeCatalog=local Ayuda? Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 15 Jun 2009 14:42:13 -0400 Subject: Re: Custom lifecycle. Changing the default resource plugin confiduration. From: edov...@gmail.com To: users@maven.apache.org As a last resource solution yes. The thing is I don't want to force the clients of the plugin to have to do this. instead i just want them to declared an specific packaging type and that's it. Unfortunately they will have to still define the my theme plugin in their poms.xml as it needs to have the extensions parameter set to true; but forcing them to also define the resources plugin to change this particular configuration parameter is plain wrong. There most be another way of doing this that does not involve the clients of the plugins doing anything special; that's what I am looking for. Gracias nuevamente. Erick. On Mon, Jun 15, 2009 at 2:15 PM, Martin Gainty mgai...@hotmail.com wrote: de nada can you use a configuration parameter for output-directory? plugin groupIdsample.plugin/groupId artifactIdmaven-erick-plugin/artifactId version1.0/version configuration output-directorytheme/output-directory /configuration /plugin http://maven.apache.org/guides/plugin/guide-java-plugin-development.html Quizas? Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 15 Jun 2009 13:50:32 -0400 Subject: Re: Custom lifecycle. Changing the default resource plugin confiduration. From: edov...@gmail.com To: users@maven.apache.org *Martin, I don't think that will work here as maven it self is the one calling the copy-resources goal on the resources-plugin. What I need is a declarative way to pass the output directory into maven from within my plugin. Gracias. Erick * On Mon, Jun 15, 2009 at 1:32 PM, Martin Gainty mgai...@hotmail.com wrote: Hi Erick could you call resources:copyResources -DoutputDirectory=/theme http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html ? Saludos Cordiales Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Can the resource-plugin copy the resource out of the project path?
for example: my resource file is in /home/admin/key/DAS.key or c:/key/DSA.key.how can I set it?
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 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: Using resource plugin -- why do my resources end up in classes/ ?
Is there any reason why these files shouldn't be considered binaries by the assembly plugin? I'm now running into a problem where my binaries are getting included in the zip file I create, but my resources are not. Do I need to explicitly include the mas files, or is there an option within the moduleSet to include resources? On Tue, May 13, 2008 at 1:33 PM, matthew sporleder [EMAIL PROTECTED] wrote: Thanks, that worked perfectly. On Tue, May 13, 2008 at 1:17 PM, Kalle Korhonen [EMAIL PROTECTED] wrote: I'd separate out those resources from classpath resources by putting them into a different dir. Then use: resource directorysrc/main/data/directory targetPath../targetPath /resource Or, if you bind resources plugin yourself like you did below, use: configuration outputDirectory${basedir}/target/outputDirectory /configuration Kalle On Tue, May 13, 2008 at 9:03 AM, matthew sporleder [EMAIL PROTECTED] wrote: How can I change the outputDirectory for all of my modules which include the following: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId version2.2/version executions execution phasecompile/phase goals goalresources/goal /goals /execution /executions /plugin /plugins /build Currently my resources/* are being copied to target/classes/ and I really just need them in target/ I've tried changing the outputDirectory, but it's not really working how I'd like with modules. (I end up with the copies in the parent's target/ instead of the modules'. Thanks, Matt - 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]
Using resource plugin -- why do my resources end up in classes/ ?
How can I change the outputDirectory for all of my modules which include the following: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId version2.2/version executions execution phasecompile/phase goals goalresources/goal /goals /execution /executions /plugin /plugins /build Currently my resources/* are being copied to target/classes/ and I really just need them in target/ I've tried changing the outputDirectory, but it's not really working how I'd like with modules. (I end up with the copies in the parent's target/ instead of the modules'. Thanks, Matt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using resource plugin -- why do my resources end up in classes/ ?
I'd separate out those resources from classpath resources by putting them into a different dir. Then use: resource directorysrc/main/data/directory targetPath../targetPath /resource Or, if you bind resources plugin yourself like you did below, use: configuration outputDirectory${basedir}/target/outputDirectory /configuration Kalle On Tue, May 13, 2008 at 9:03 AM, matthew sporleder [EMAIL PROTECTED] wrote: How can I change the outputDirectory for all of my modules which include the following: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId version2.2/version executions execution phasecompile/phase goals goalresources/goal /goals /execution /executions /plugin /plugins /build Currently my resources/* are being copied to target/classes/ and I really just need them in target/ I've tried changing the outputDirectory, but it's not really working how I'd like with modules. (I end up with the copies in the parent's target/ instead of the modules'. Thanks, Matt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using resource plugin -- why do my resources end up in classes/ ?
Thanks, that worked perfectly. On Tue, May 13, 2008 at 1:17 PM, Kalle Korhonen [EMAIL PROTECTED] wrote: I'd separate out those resources from classpath resources by putting them into a different dir. Then use: resource directorysrc/main/data/directory targetPath../targetPath /resource Or, if you bind resources plugin yourself like you did below, use: configuration outputDirectory${basedir}/target/outputDirectory /configuration Kalle On Tue, May 13, 2008 at 9:03 AM, matthew sporleder [EMAIL PROTECTED] wrote: How can I change the outputDirectory for all of my modules which include the following: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId version2.2/version executions execution phasecompile/phase goals goalresources/goal /goals /execution /executions /plugin /plugins /build Currently my resources/* are being copied to target/classes/ and I really just need them in target/ I've tried changing the outputDirectory, but it's not really working how I'd like with modules. (I end up with the copies in the parent's target/ instead of the modules'. Thanks, Matt - 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]
resource plugin - does it require a profile?
Hi, I found out that the resource plugin is capable of simply copying files to a directory. I would like to use this to update files in my tomcat webapps project folder (when necessary). However, I am already using the plugin to copy resources to the war file that is generated in the regular build phases (1): build resources resource directory${basedir}/src/configuration/directory includes include*.xml/include /includes ... /resource /resources I tried to additionally add (2): plugin artifactIdmaven-resources-plugin/artifactId configuration outputDirectory${MY_OUTPUT_DIR}/outputDirectory resources resource directory${MYRESOURCES_DIRECTORY}/directory includes include**/*.jsp/include include**/*.js/include include**/*.css/include ... /includes /resource /resources /configuration /plugin However, this (2) didn't work out - Maven still used the settings I had specified under build. Finally I found a temporary solution, using profiles: ... profile idmyspecialfunc/id build resources resource directory${MYRESOURCES_DIRECTORY}/directory includes include**/*.jsp/include include**/*.js/include include**/*.css/include ... /includes /resource /resources /build /profile ... Then, when calling: mvn resources:resources -P myspecialfunc it works as desired. However I don't really like it that way, as the other developers would have to remember this kinda complicated call. Isn't there an easier way to get this done? Thanks in advance, Stefanie -- GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen! Jetzt dabei sein: http://www.shortview.de/[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Cannot configure filters for resource plugin
My first diagnostic was wrong. Here is my config : plugin artifactIdmaven-resources-plugin/artifactId executions execution iddev/id goalsgoalresources/goal/goals configuration outputDirectory${basedir}/src/main/properties/dev/outputDirectory filters filter${basedir}/src/filters/dev.properties/filter /filters /configuration /execution /executions /plugin outputDirectory is set as expected, but not filters. Using debugger, I wen into CollectionConverter.fromExpression( .. ) with configuration = filtersfiltersD:\projets\pnm\pnm/src/filters/dev.properties/filters/filters The configuration.gatValue( null ) is expected (but maybe I'm wrong) to return the configured value... for a strange reason, the configuration.domattribute has its value set to the expression ${ project.build.filters} and does not return the childlist... What's wrong ? Is this related to expression vs default-value ? Nico. 2008/2/14, nicolas de loof [EMAIL PROTECTED]: Hello, I need to generate configuration fils for muliple environments (dev/test/prod) in the same build, to get packaged in my assembly. The templates files are in my resources directory, and I have 3 filters files in src/main/filters I'd like to run the resource plugin 3 times using execution, with configuration changed to use the 3 filters files ... but the filters parameter is set as expression=${ project.build.filters} Is there any way to set configuration to override this expression ? Using project.build.filtersMyFile/ has no effect. Why is expression used for plugin parameters ? Why not use default-value, so that user can override whene needed ? Nico
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]
Resource plugin copying files which end up not being binary compatible
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: project [...] build resources resource[..a resource directory...]/resource resource[..another resource directory...]/resource resources /build [...] /project 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 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: project [...] build resources resource[..a resource directory...]/resource resource[..another resource directory...]/resource resources /build [...] /project 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]
Resource Plugin
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/ __
resource plugin and empty directories
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
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