Hi
Based on a couple of previous e-mails and me doing one of the tasks, I
identified that once I append -V during my fresh build I reliased I was still
using the installed Maven.
>>> mvn -
>>> DdistributionTargetFolder=/Users/rajivpjs/tools/maven-test/apache-maven-3.4.0-SNAPSHOT
>>> clean pack
Am 07/30/16 um 21:12 schrieb Karl Heinz Marbaise:
> Hi,
>
> If I test with this version the build will fail if I don't set the
> modelVersion (empty tag) or remove the entry completely...
This wasn't intended. Will fix it. It should just warn about it. Thanks.
-
Hi,
If I test with this version the build will fail if I don't set the
modelVersion (empty tag) or remove the entry completely...
~/ws-git/javaee (master *)$
~/tools/maven-test/apache-maven-3.4.0-SNAPSHOT/bin/mvn clean package
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems wer
Hi Jason,
On 7/30/16 5:48 PM, Jason van Zyl wrote:
You know there’s code in there for running segments of the lifecycle Igor put
in there about 18 months ago?
I have found something which is called
DefaultLifecycleTaskSegmentCalculator (with a method:
calculateTaskSegments( MavenSession ses
So I think really what you want vis-a-vis artifact resolution is a way to have
a new repository system session with new/altered implementations for fixes or
new behavior. Possibly a new repository system as well. If the default behavior
continues to work, anyone can do whatever radical things th
Also I assume you’re doing this for performance reasons? Ideally if everything
was idempotent and incremental this would not be necessary. Igor wrote the
segment execution code (intentionally make sure it wasn’t generally accessible
to users) because running chunks of the lifecycle to avoid perf
You know there’s code in there for running segments of the lifecycle Igor put
in there about 18 months ago?
> On Jul 30, 2016, at 11:25 AM, Karl Heinz Marbaise wrote:
>
> Hi,
>
> currently I've written a PoC to define a life cycle range on command line
> like this:
>
> mvn generate-sources..
Hi,
currently I've written a PoC to define a life cycle range on command
line like this:
mvn generate-sources..generate-resources
which will run only the life cycle phases from generate-sources (incl.)
to generate-resources (incl.)...
This works so far:
$ mvn pre-integration-test..post-in
