On Fri, 16 Jun 2017 04:55:17 +0200, Olivier Lamy wrote:
well not better as it looks not being possible
[ERROR] 'dependencyManagement.dependencies.dependency.classifier' for
org.eclipse.jetty:jetty-bom:pom:bom must be empty, imported POM cannot
have
a classifier. @ line 40, column 21
WHY th
well not better as it looks not being possible
[ERROR] 'dependencyManagement.dependencies.dependency.classifier' for
org.eclipse.jetty:jetty-bom:pom:bom must be empty, imported POM cannot have
a classifier. @ line 40, column 21
WHY this restriction?
On 16 June 2017 at 11:40, Olivier Lamy wrote:
Hi Robert
Sorry for late reply.
Well this doesn't work (see source here [1]) you can attach an artifact
with his own GAV.
And it's neither possible to change GAV of an attached artifact.
Caused by: java.lang.UnsupportedOperationException: Cannot change the
groupId for an attached artifact. It is d
Hi Olivier,
assuming this bom file is not used by the reactor, it should be possible
to possible to generate it in the root pom and attach it with its own
GA[1][2].
The javadoc content says this piece of code is deprecated, probably
because it introduces some magic where it is hard to deter
Hi,
Not sure how to do that in a non hackhish way.
My current goal: generate a bom style pom with all reactor projects in
dptMngt section.
As people are lazy to write dptMngt section in theirs poms they delegate to
others with this pom.
So as I'm lazy too I don't want to write/maintain this pom nei
