why you want
> shared company/team/product/buildenv parents.
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
>
>
>
>
> On Fri, Jan 13, 2017 at 5:51 PM +0100, "Dean Schulze" <
> dean.w.schu...@gmail.com> wrote:
>
>
>
>
>
>
&g
I would like to avoid having to add
1.8
1.8
to every pom.xml. Is there a global setting I can set in mvn to make Java
8 the default so I don't have to add this to every pom.xml?
The FAQ shows the profile below to declare a dependency for tools.jar. This
seems to be a problem waiting to happen now that Oracle is the vendor for the
official JVM. (A recent update to JDK 1.6 caused problems for Eclipse because
Eclipse was expecting a property setting of Sun Microsystems
Hi Wayne,
Here are my suggestions so far:
Descriptions of what the various elements in a pom do (similar to the Ant
documentation).
Sequence diagrams for maven execution (typical cases) to show how POM elements
affect the build.
How do phases and goals relate to POM elements?
Changes from
Wayne,
Thanks for your concise statement. I'm new to maven and have been trying to
figure out how to use maven by reading the documentation. What a quagmire.
Maven documentation authors - please study Wayne's concise statement below.
That is what we need in the Maven documentation. Not the
if needed. Profiles work great for
that, but I can see exactly where the hydra head fits on the beast now and
don't intend on doing anything more with them unless absolutely necessary.
$0.02...
On Jan 13, 2011, at 5:10 PM, Dean Schulze wrote:
I need to modify the maven build
I need to modify the maven build for a large project
to skip certain steps during typical development builds (i.e. don't
build the *-source.jar files). I've searched for conditional
execution for maven, but haven't found anything.
A dev profile sounds like the intuitive way
