You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by Gerhard Petracek <gp...@apache.org> on 2017/07/02 20:56:15 UTC
[discuss] meecrowave dev/prod setup
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
Re: [discuss] meecrowave dev/prod setup
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Last time i hit it i kind of thought it was a maven issue - gradle doesnt
have it for instance. Maybe we should fwd it to mvn list?
On meecrowave side we can doc how to use jar plugin exclusions but it is
pretty much impossible to automate more and right in a useful manner, no?
Le 3 juil. 2017 00:05, "Gerhard Petracek" <gp...@apache.org> a écrit :
> hi romain,
>
> yes - keeping the starter-class in the test-source directory used to be my
> workaround for tomee (which works for meecrowave as well).
> however, i'm trying to get rid of that workaround. (sorry for skipping that
> part in my initial message).
>
> regards,
> gerhard
>
>
>
> 2017-07-02 23:19 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:
>
> > 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" <gp...@apache.org> 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
> > >
> >
>
Re: [discuss] meecrowave dev/prod setup
Posted by Gerhard Petracek <gp...@apache.org>.
hi romain,
yes - keeping the starter-class in the test-source directory used to be my
workaround for tomee (which works for meecrowave as well).
however, i'm trying to get rid of that workaround. (sorry for skipping that
part in my initial message).
regards,
gerhard
2017-07-02 23:19 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:
> 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" <gp...@apache.org> 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
> >
>
Re: [discuss] meecrowave dev/prod setup
Posted by Romain Manni-Bucau <rm...@gmail.com>.
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" <gp...@apache.org> 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
>