Re: can't stop tomee with maven plugin

Sorry but what you mean with: Stop is intended for "start" only as in tomcat. ??? >From the page http://tomee.apache.org/tomee-maven-plugin.html Exist the command tomee:stop Sorry for my confusion -- Sent from:

Continuous integration and a PR

Hello everyone, I have a question about PR and continuous integrations. Why we don't have a plugin to run the tests when we open a PR? I'm also helping in another Apache Project such as Apache TinkerPop and Apache Commons

Re: TomEE Maven Plugin: Can conf/system.properties be externalized?

I guess you want to hide user, password, connection, schema etc. You could use variable replacement with ${} and pack the file in the jar and then just set the properties to replace like Romain mentioned. I think it should work, Cheers, Roberto > On 22 Nov 2018, at 05:42, Romain Manni-Bucau

Arquillian TomEE embedded on Java 10

I'm using Java jdk 10 TomEE 7.1(also embedded), johnzon 1.0.0(also tried with 1.0.1) . When running test case which is using Arquillian, f.e. from Intellij I get this error message: Exception in thread "main" java.lang.IllegalAccessError: tried to access field

Re: TomEE Maven Plugin: Can conf/system.properties be externalized?

Brilliant! I knew about setting system properties, but I didn't know ${var} would pull from the unix environment! What we're doing now is tomee-exec->deb package->sftp to ubuntu->freight script adds to apt repo->apt installation on linux system. The deb script creates a user/group after the

Re: can't stop tomee with maven plugin

Stop a TomEE started with start command. means you can use tomee:stop to stop an instance launched with tomee:start. tomee:run blocks in the contextual shell and is stopped typing "exit" in the shell (it is a kind of command line interface) Romain Manni-Bucau @rmannibucau

Re: Continuous integration and a PR

If it helps: Travis is quite bad for big OS projects cause it has a limited queue for OS project which prevent parallelism very quickly so you would just wait days at the end, likely better to ask infra to setup the build on ASF jenkins IMHO. We can have a light flavor of the build, like just a

Re: Continuous integration and a PR

Hi Otavio, Just needs to be asked to infra but the reactivity will be ~3h instead of a few minutes like for small projects so not sure it would help much. Investing in a build.sh can help more (./build.sh --core, ./build.sh --tomee, ./build.sh --tomee --validate etc) - it is an old idea nobody

Re: Arquillian TomEE embedded on Java 10

It is likely missing some --add-opens for unamed module on the command line Le jeu. 22 nov. 2018 17:43, COURTAULT Francois < francois.courta...@gemalto.com> a écrit : > Hello, > > I don't know if it is related but I can't use TomEE using Java 11 or 10. > > See my Jira issues: > -

Re: Continuous integration and a PR

We do have a CI server: https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8 Our build is massive though - it takes between 2 and 5 hours, depending on hardware. 6+ PRs being updated per day would mean it would be potentially running all the time with a growing queue. Commons-lang on the other

RE: Arquillian TomEE embedded on Java 10

Hello, I don't know if it is related but I can't use TomEE using Java 11 or 10. See my Jira issues: - https://issues.apache.org/jira/projects/TOMEE/issues/TOMEE-2263 - https://issues.apache.org/jira/projects/TOMEE/issues/TOMEE-2264 Best Regards. PS: you vote for it. -Original

Re: TomEE Maven Plugin: Can conf/system.properties be externalized?

side note: why tomee:exec and not tomee:build which was intended for that case? Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn

Re: TomEE Maven Plugin: Can conf/system.properties be externalized?

You also have propertiesproviders and configurers for resources: https://github.com/apache/tomee/blob/8547f730b7c9fc085534a8f5d1f68340154d2cfe/container/openejb-core/src/main/java/org/apache/openejb/resource/heroku/HerokuDatabasePropertiesProvider.java and

RE: TomEE Maven Plugin: Can conf/system.properties be externalized?

Hi guys, I'm looking at the same thing but from perspective to run TomEE image in the K8's cluster. The ${} replacement looks promising, especially when I found this thread http://tomee-openejb.979440.n4.nabble.com/how-con-figure-the-datasource-into-tomee-xml-using-docker-td4682533.html where

Re: can't stop tomee with maven plugin

Hi Mauro, The options Romain mentioned worked fine on my side, it can be divided into two groups: If you start from the command line using: mvn tomee:run >From the same terminal you can do the following options to stop it: - exit - quit - crtl + c If you start from the command line

Re: TomEE Maven Plugin: Can conf/system.properties be externalized?

To complete the for example (somehow typed it in my brain instead of the form:) It looks like it will solve some problems by reading directly from the configmap (cdi custom config source would be awesome) instead of relying on some yaml. Cheers, Dmitry From:

RE: TomEE Maven Plugin: Can conf/system.properties be externalized?

Thanks Romain, this is pretty cool functionality I can see the potential (for example ). Just for the sake of completeness ('also' follows after 'yes':), is it still Ok to use env variables in ${}? Cheers, Dmitry -Original Message- From: Romain Manni-Bucau

Re: TomEE Maven Plugin: Can conf/system.properties be externalized?

Placeholders are a real feature so ko worry on them. Not sure what you mean by cdi config source but microprofile is not tomee mainstream (they still breaks api between each versions) and cdi hapoens way too late for the container (tomee and cdi extension) but an app using only injection you can