Has anyone get archiva running on standalone jetty (not maven-jetty-plugin)?

I got it to run, but only by copying src/jetty-env.xml into the
generated WEB-INF directory - which makes me think that I'm either
missing some subtlety in configuring jetty, or that archiva should be
putting the jetty-env.xml into the WEB-INF directory as standard.

Of course, I'm very much a newbie to java webapps, so it could be
something else that I'm missing.


Is it possible to have jetty run archiva without putting the
jetty-env.xml in WEB-INF?

Would there be any disadvantages in the archiva build being changed to
package the jetty-env.xml into the war file? If not, could the archiva
developers consider doing that?


Thanks,

Max.

Reply via email to