Hi Gerhard What is the proposal? I use it for demos with either maven jar exclude or just putting it in test classes instead of main and it work fine. Also maven plugin or a plain maven exec shouldnt require any custom main so not sure which blocker you hit. Can you detail it please?
Le 2 juil. 2017 22:56, "Gerhard Petracek" <[email protected]> a écrit : > hi @ all, > > i'm currently using meecrowave for the upcoming chapter of cdi@work. > i'm quite happy with it, however, imo we should improve one area. > i would like to show a starter similar to [1]. that's a fast alternative to > the maven-plugin (as well as the runner-jar). > > however, using this approach to start the application during development > results in a web-archive (for prod.) which contains meecrowave as a lib. > the current workaround is to use different maven profiles (one defines > meecrowave as a provided dependency and the other one as a compile > dependency). > imo we need something more useful to allow both in parallel (such a > starter-class as well as the maven-plugin or runner-jar) without using > workarounds like different maven profiles. > > regards, > gerhard > > [1] > https://github.com/os890/meecrowave_template_jax-rs_ > cdi_jpa/blob/master/src/dev-starter/java/org/os890/ > meecrowave/dev/DevStarter.java >
