Is there any way (using plugins, whatever) to get a stable reference to the
root project version? Here is what I’m trying to do. I have a reactor project:
pom.xml
module1/pom.xml
module2/pom.xml
The wrinkle is that the root pom.xml has a parent (for example foo:bar:1.2).
foo.bar
Hi,
On 9/16/15 1:50 AM, Jordan Zimmerman wrote:
Is there any way (using plugins, whatever) to get a stable reference to the
root project version? Here is what I’m trying to do. I have a reactor project:
pom.xml
module1/pom.xml
module2/pom.xml
The wrinkle is that the root pom
Dear All,
I am using maven 3.2.5
i want to use difference property files to build war for diff environments
and deploy it on local, test and prod accordingly based on maven command -
mvn -Plocal clean install
/resources/local/env.properties
/resources/test/env.properties
/resources/prod/env.pro
Why not make three new separate projects that produce the required war
files.
Only put the minimum configuration in the new projects and let them
depend on jars that contain the shared code and resources.
Maven prefers to produce 1 artifact per project.
On 16/09/2015 2:29 AM, Neeraj Malik wro
I spoke with Jason and it turns out what I want to do requires a
change to core. Therefore:
https://issues.apache.org/jira/browse/MNG-5890
On Wed, Sep 16, 2015 at 9:01 AM, Ron Wheeler
wrote:
> Why not make three new separate projects that produce the required war
> files.
> Only put the minimum c
Or a core extension but this change is likely not that hard and meshes with
what we’ve done with the .mvn directory which is to signify the root of the
reactor.
> On Sep 16, 2015, at 12:20 PM, Jordan Zimmerman
> wrote:
>
> I spoke with Jason and it turns out what I want to do requires a
> cha
the only difference I see, and which makes a huge difference, is that the value
has to be calculated also when effective model is built from repository
(instead of project direct build, with its reactor)
I fear it is not so trivial in the context of repository calculation, since
there is no mor
