Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Keep Jetty instance alive in daemon mode after maven command completes

It seems that "-D=<some-switch>"  doesn't get passed through to the forked
jetty instance.  

We start jetty in forked mode as such:

mvn clean install *-Denv=local *-Pjetty-deploy

But the logs tell me:

null org.springframework.web.context.ContextLoader main 2012-11-02
09:31:08,015 ERROR Context initialization failed
 org.springframework.beans.factory.BeanInitializationException: Could not
load properties; nested exception is java.io.FileNotFoundException: class
path resource [env/*${env}*/application.properties] cannot be opened because
it does not exist

How do I fix this?



--
View this message in context: http://jetty.4.n6.nabble.com/Keep-Jetty-instance-alive-in-daemon-mode-after-maven-command-completes-tp4959365p4959472.html
Sent from the Jetty User mailing list archive at Nabble.com.


Back to the top