[ https://issues.apache.org/jira/browse/NPANDAY-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter resolved NPANDAY-413. ---------------------------------- Resolution: Fixed no longer seeing this - please reopen if it is still there for you. I can successfully build without a settings file, as long as I have the right path > Missing npanday-settings.xml file gives exception during build and does not > auto-generate > ----------------------------------------------------------------------------------------- > > Key: NPANDAY-413 > URL: https://issues.apache.org/jira/browse/NPANDAY-413 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins > Affects Versions: 1.4-incubating > Environment: $ mvn -v > Apache Maven 2.2.1 (rdebian-4) > Java version: 1.6.0_24 > Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux" version: "2.6.35-28-generic" arch: "amd64" Family: "unix" > Reporter: John R. Fallows > Fix For: 1.4.1-incubating > > > When npanday-settings.xml is missing from the user's .m2 directory on Linux, > the file is not auto-generated (as it appears to be on Windows systems), and > instead the following exception is displayed in the build console. > {code} > [INFO] [compile:compile {execution: default-compile}] > java.io.FileNotFoundException: /home/jfallows/.m2/npanday-settings.xml (No > such file or directory) > at java.io.FileInputStream.open(Native Method) > at java.io.FileInputStream.<init>(FileInputStream.java:106) > at > npanday.plugin.compile.AbstractCompilerMojo.getNPandaySettingsPath(AbstractCompilerMojo.java:1259) > at > npanday.plugin.compile.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:1086) > at > npanday.plugin.compile.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:725) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.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:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.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) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira