Hi,
Does anyone know of an updated list of maven dependencies best and bad
practices?
for example:
- when to inherit dependencies from parent and when not
- when to use dependencyManagement
- when and when not to use use transitive dependencies
and any other important practices you can
Yaron is right: you may find problems in your build by NOT moving the
.m2/repository folder. You may discover that specific files were available
only in your local repo and not anywhere else (Maven Central or your local
proxy such as Archiva/Artifactory/Nexus). And this is a good time to
discover b
Hi,
I have the same "problem" here which is not really a problem: I deploy the
parent pom (and the parent's parent and so on) and voila. As parent are only
pom, no real package or jars, this not really a problem.
But I think the Flatten Maven Plugin
https://www.mojohaus.org/flatten-maven-plugin/ m
Hello Apache Supporters and Enthusiasts
This is a reminder that our Apache EU Roadshow in Berlin is less than
two weeks away and we need your help to spread the word. Please let your
work colleagues, friends and anyone interested in any attending know
about our Apache EU Roadshow event.
We h
Thanks Francois, I thought It would be cumbersome and probably confusing
users to publish poms and ended up using the flatten-maven-plugin and it
works fine now. Thanks, Naveen
On Thu, May 31, 2018 at 12:36 PM, Francois MAROT
wrote:
> Hi,
>
> I have the same "problem" here which is not really a
My project structure looks like:
ParentA
--Child 1(packagin pom)
|-- subchild1(packaging: war)
|-- subchild2(packaging: war)
|-- subchild3(packaging: war)
|-- subchild1(packaging: war)
--Child 2(packaging pom)
|-- subchild1(packaging: jar)
|--
