maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepak Panchal (JIRA)" <j...@codehaus.org>
Subject [jira] (MRESOURCES-144) if filter file does not exist it should optionally ignore it, not just throw an exception
Date Thu, 06 Mar 2014 14:26:00 GMT

    [ https://jira.codehaus.org/browse/MRESOURCES-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342473#comment-342473
] 

Deepak Panchal edited comment on MRESOURCES-144 at 3/6/14 8:25 AM:
-------------------------------------------------------------------

I also want to have such a feature. The use case in my case is I want the developers to optionally
specify their local settings that will override the default which is either specified as default
proeprties in the pom file itself or within another filter proeprties file.
Having an option to ignore missing makes this possible.



was (Author: deepan):
I also want to have such a feature. The use case in my case is I want the developers to optionally
specific their local settings that will override the default which is either specified as
default proeprties in the pom file itself or within another filter proeprties file.
Having an option to ignore missing makes this possible.


> if filter file does not exist it should optionally ignore it, not just throw an exception
> -----------------------------------------------------------------------------------------
>
>                 Key: MRESOURCES-144
>                 URL: https://jira.codehaus.org/browse/MRESOURCES-144
>             Project: Maven Resources Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.4.3
>            Reporter: richard stevenson
>            Assignee: Olivier Lamy
>            Priority: Minor
>         Attachments: maven-filter.patch
>
>
> If you have a list of filter files
> <filters>
>   <filter>a.properties</filter>
>   <filter>b.properties</filter>
>   <filter>${prop.name}.properties</filter>
> </filters>
> It would be nice to tell the resources plugin to optioanlly ignore a file if it does
not exist. Currently get the following stack trace:
> org.apache.maven.lifecycle.LifecycleExecutionException: Error loading property f
> ile 'D:\projects\.../src/main/filters/a.filter.properties'
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:719)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:556)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:535)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:387)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:348)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:180)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>         at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
> 0)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>         at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error loading propert
> y file 'D:\projects\.../src/main/filters/a.filter.properties'
>         at org.apache.maven.plugin.resources.ResourcesMojo.execute(ResourcesMojo
> .java:269)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:490)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:694)
>         ... 17 more
> Caused by: org.apache.maven.shared.filtering.MavenFilteringException: Error load
> ing property file 'D:\projects\.../src/main/filters/a.properties'
>         at org.apache.maven.shared.filtering.DefaultMavenFileFilter.loadProperti
> es(DefaultMavenFileFilter.java:274)
>         at org.apache.maven.shared.filtering.DefaultMavenFileFilter.getDefaultFi
> lterWrappers(DefaultMavenFileFilter.java:199)
>         at org.apache.maven.shared.filtering.DefaultMavenResourcesFiltering.filt
> erResources(DefaultMavenResourcesFiltering.java:162)
>         at org.apache.maven.plugin.resources.ResourcesMojo.execute(ResourcesMojo
> .java:265)
>         ... 19 more
> Caused by: java.io.FileNotFoundException: D:\projects\.../src/main/filters/a.fil
> ter.properties
>         at org.apache.maven.shared.filtering.PropertyUtils.loadPropertyFile(Prop
> ertyUtils.java:65)
>         at org.apache.maven.shared.filtering.DefaultMavenFileFilter.loadProperti
> es(DefaultMavenFileFilter.java:269)
>         ... 22 more



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message