Hello,
are there some good guides about structuring bigger maven projects
(including shared code, easy deployment & versioning, etc.)? There's
much about the basic stuff, default folders, etc. but somehow, I seem to
keep missing the articles (and books) about the "big picture" for bigger
proj
I use maven-compiler-plugin to load /lib/*.jar files, like this in pom.xml:
org.apache.maven.plugins
maven-compiler-plugin
3.0
1.7
1.7
UTF-8
${projec
My experience is precisely the opposite of yours. The most common
practice is for the parent to be the aggregator; it's hard to get the
site plugin, for example, to work right with your preferred structure
where they are different.
I have built many projects with the the one-parent structure, and
A while ago, I started working on an existing project with many developers.
The codebase has a large multi-project Maven build. The top directory is both
an "aggregator" and "parent" POM, as it has a "modules" list, and all of the
child modules have it as their parent POM, for dependencies and
Hi Niranjan,
> We do set this because we have been burned many times where wrong
> classes from older jar files were getting loaded.
...
> This caused all sort of interesting crashes at runtime.
Runtime... of your application? That would be caused by your deployment
mechanism, which is past where
> How to depend on the same jars with different versions in one project?
Maven's whole design is centered around each GA having only one associated
V. Hence, it performs dependency convergence during builds etc. You can do
a structure like Anders described, which will solve it at compile time, but
You would need a multi-module project, with separate modules for the code
that depends on the different versions av det dependency "jar" (artifact).
You would then, typically, have one or more moduoles for the common code
and then one module for each of the version of the dependency with
incompatib
Hello Bernd,
Hello Chas,
thanks for your mails.
@Bernd:
The problem is that we have some old projects which definitely overwrite their
artifacts in the repository.
Unfortunately I can't change that at the moment and also not in the near future
as I don't have enough time for that.
Also I'm awar
