it does'nt work. it's before. i can't provide server.xml with vars. tomee:exec fail. Le 10 août 2015 19:11, "Romain Manni-Bucau" <[email protected]> a écrit :
> Hi Yann, > > you should be able to use "-DadditionalSystemProperties=-Dhttp.port=1080 > -Dhttps.port=1443" > > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <http://rmannibucau.wordpress.com> | Github < > https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > <http://www.tomitribe.com> > > 2015-08-10 10:08 GMT-07:00 Yann Blazart <[email protected]>: > > > Hello, currently I'm trying to make packing to deliver TomEE and Apps in > > production as One Jar to run with tomee:exec. > > The only way I found to permit to the production team to configure > > resources is to make them write a tomee.xml and provide its path by using > > the -DadditionalSystemProperties=-Dopenejb.conf.file=... > > > > Well done, but to configure the http listening port, I followed a blog > post > > from Romain. > > > > in the blog article 50 shades of tomee, Romain has written that we could > > use tomee:exec to generate the big jar and pass some vars to the next > java > > command, to launch tomee, to override some values. In his example he say > > that he can override the http.port in server.xml. Great ! > > > > But in fact, while I'm providing a server.xml with the ${http.port} in > the > > connector for the tomcat, the tomee:exec fail because of an > > NumberFormatException. > > > > The plugin tomee try to get the value from the provided server.xml, with > > pain of course in this case. > > > > Is it possible to fix it ? I can't clearly see the impacts on the other > > goals of the mojo if I change the code. > > > > Does anybody have an idea ? > > > > Thanks a lot. > > >
