Free advice:
1) Before you get too deep into Maven, set up your own Maven Repo. We
use the community version of Nexus but there are others available.
It makes maven much easier to use and much easier to understand.
2) Walk before you run. Try to get your builds running smoothly before
optimizing. A lot of people seem to get hung up trying to optimize
before they are really experienced with the easy things.
3) Scan a couple of the maven books just to get a feel for what is
there. You don't have to read them line by line.
4) Remember that no matter what you are building as an app, hundreds of
people have done it before with maven. You should not run into any
situations where you have to invent the wheel.
5) Profiles are inherently evil. Search the archives if you want to see
some of the problems they can get people into. There are legitimate uses
for profiles but not many.
6) Decouple run-time from compile-time. Programmers produce artifacts.
System administrator configure run-times. If you are both, just remember
which hat you are wearing.
Code that runs on multiple platforms should know the least about the
platform and use run-time tools to configure themselves (JNDI for
example). One maven project => one artifact. Use multiple projects and
assembly projects(no code just configuration files) to build run-time
specific artifacts if you need to.
Most important: Do things the Maven way. If you try to fight Maven, you
will face a determined foe that will ultimately win. People spend tons
of electronic ink in this forum trying to treat Maven like Ant. Maven
knows how to build artifacts and will not cooperate with those who have
other philosophies in mind.
Resistance is Futile!
Maven really is a great help once you get into the right pattern.
Ron
On 21/12/2012 9:00 AM, Kammer, John wrote:
SOLUTION:
OK, turns out the problem was that for whatever reason the first time Maven
downloaded the archives
some of the jar files came in corrupted. The Apache Commons Collections was one
of these and generally the
first one encountered when trying to run any Maven build. The error messages
from the command line
were not terribly enlightening and not until attempting to run the build from
Eclipse did I see that about five
of the jar files were corrupted.
I deleted the corrupted files and re-ran Maven, this time finding one
corrupted file so I deleted it again
and the third time was the charm.
Thanks to those who offered assistance, I am now officially started with
Maven.
----------------
== Hello, and thanks in advance for any help.
== I am completely new to Maven and trying (without success) to get the most
basic of Maven functionality
== to work.
== Have tried multiple versions of Maven and Java all with the same results
(see below).
== It seems the Apache Commons Collections jar is missing, and for some reason
not being downloaded.
== Any ideas why or what I can do about it?
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
