Thank you Brian,
I am now using Nexus Repository Manager, and it does save me from a lot of
hassle. It was easier than I thought. I just resisted at first, because
switching from Ant to Maven was more work than I thought it would be, so I
didn't want to get deeper into trouble with repository ma
I've encountered a similar problem when one of the sub-modules is a maven
plugin that is used by another sub-module. I discovered this only when I
cleaned-up my local repository. Then "mvn clean install" didn't work. Even
"mvn clean" and "mvn validate" failed because the plugin was missing.
My
This reminds me of this "best practice" that uses a single maven profile to
run an ant task:
http://ionixx.wordpress.com/2008/03/10/running-specified-ant-tasks-within-maven2-outside-the-lifecycle/
Basically, you can run an ant target from maven like this: mvn -Pant
-Dtarget=my-target.
This is b
Thanks. This sheds some light to my darkness, and may explain why my
home-made maven mirror wasn't working properly.
Alex
On Sat, Nov 29, 2008 at 4:33 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On Sat, Nov 29, 2008 at 5:16 AM, Alex Athanasopoulos
> <[EMAIL PROTECTED]>
This touches on my pet peeve about maven.
I wish that I could download a zip file containing the subset of central
containing maven's core plugins and their dependencies. I would then gladly
use it as my central mirror and work productively on my projects without
having to worry about central.
I
Why not put the jars in a repository? A repository is perfect for
containing 3rd party jars, and one of maven's major benefits. Once you do
that, you don't need to refer to the jars through a hardcoded path, but
simply by a portable artifact identifier. You don't need any special tools
or reposi
