Hi,
I was wondering if there is a way by which we can skip the install phase for a
particular artifact. My use case is that I am using maven-assembly-plugin with
two assembly descriptors in it. The output of first assembly descriptor is
being used as input of the second assembly descriptor.
Am 11/03/16 um 22:55 schrieb Dave Syer:
>> Without having to update/change any poms?
>
> Yes. Remember the Spring Cloud AWS BOM already had the exclusion in it (it
> just didn't do anything without using a patched version of Maven).
>
So you'd say that your patched 3.4.0-SNAPSHOT (model
> Without having to update/change any poms?
Yes. Remember the Spring Cloud AWS BOM already had the exclusion in it (it
just didn't do anything without using a patched version of Maven).
--
View this message in context:
Am 11/03/16 um 18:54 schrieb Dave Syer:
>> Could you build a 3.4.0-SNAPSHOT locally for testing not requiring a
>> model version bump? It's easy. You just need to change method
>> 'isGreaterOrEqual' of class 'ModelVersions' to always return 'true'.
>
> Yes that works - the Wiremock version is
> Could you build a 3.4.0-SNAPSHOT locally for testing not requiring a
> model version bump? It's easy. You just need to change method
> 'isGreaterOrEqual' of class 'ModelVersions' to always return 'true'.
Yes that works - the Wiremock version is not flagged as a warning.
--
View this
Hello,
I’m trying to use the maven-dependency plugin (2.10) with the build-classpath
goal.
I want to strip the classifier but it’s not work:
mvn dependency:build-classpath -Dmdep.stripClassifier=true
I also add the option -Dmdep.prefix="foo" (needed regarding the documentation)
but it’s not
Am 11/03/16 um 17:14 schrieb Dave Syer:
>> Using current 3.4.0-SNAPSHOT master you can set the model version to
>> 4.1.0 and then you can use excludes in the dependency management import.
>> Would that solve the issue for you? Could you give that a quick test?
>
> It's not "a quick test",
> Using current 3.4.0-SNAPSHOT master you can set the model version to
> 4.1.0 and then you can use excludes in the dependency management import.
> Would that solve the issue for you? Could you give that a quick test?
It's not "a quick test", otherwise I'd be happy to oblige. Or am I missing
Am 11/03/16 um 15:57 schrieb Dave Syer:
> I would like to be able to write a BOM and tell Maven that for some
> dependencies, I am aware of a conflict in the dependency management, but the
> conflict arises in a library I don't control, and I know with high
> confidence that my users either a)
I would like to be able to write a BOM and tell Maven that for some
dependencies, I am aware of a conflict in the dependency management, but the
conflict arises in a library I don't control, and I know with high
confidence that my users either a) don't care, or b) would be happy with my
>From my understanding you would simply have to get rid of the
>tags and copy the 'configuration' part into the main plugin configuration,
>like so:
org.apache.maven.plugins
maven-javadoc-plugin
2.10.4
-Xdoclint:none
protected
11 matches
Mail list logo