RE: Maven properties passed to external ant build file

Looks like if I use nested elements inside the call it's working. Which is contrary to the maven-antrun-plugin 'Using Maven properties' section at http://maven.apache.org/plugins/maven-antrun-plugin/usage.html. Will try to reduce and example project and file a bug report. > -Original

Re: options

> On Aug 17, 2017, at 11:59 PM, Tomaz Majerhold > wrote: > > No, because it is on CI system and I can't do it interactively(I know docker > switches ), thx any way. Where the container instance runs shouldn’t matter. If it’s a container as you say, the Maven

Re: How best to use profiles and modules for different build purposes

First of all, if you want to do releases you WILL need a centralized (remote) repo where you can deploy that to. It doesn't make sense for every developer to build their own copy of any release of your internal artifacts. Secondly, you don't need to deploy your artifacts to a remote repo. You can

Re: Transitive dependencies and version management

What you would do is that you specify the version of C in dependencyManagement of A. When you then build A, the specified version of C will be used regardless of what version is specified in B. However, for thsi to work in runtime this requires the specified version of C to be compatible with the

Re: options

No, because it is on CI system and I can't do it interactively(I know docker switches ), thx any way. Regards, Tomaž James Klo je 17.8.2017 ob 16:25 napisal: You can attach and inspect a running Docker container with: docker exec -it bash But the cache should be by default in ~/.m2. So