Which of your dependencies do you need help with? I did the POM for
Commons Logging 1.1.1, so I have a pretty good idea of what's needed.
I had marked all the other dependencies for log4j as optional, because
prior to Maven, that is technically what people had been doing
naturally
Could some explain the difference between the dependency scope
provided versus optional if there actually is any..
We have converted log4j over to Maven recently and accidently forgot
to mark a few dependencies with flags indicating that, while needing
for compile time, should not
On 10/05/2008, at 9:38 AM, Brianefox wrote:
Provided means to include in the compile do but not in the package
(war)
Optional means that it wont be pulled in transitively by users of
your jar
From this, I gather Optional is actually what we want. Would it be
fair to say that Optional
to Archiva.
cheers,
Paul Smith
Core Engineering Manager
Aconex
The easy way to save time and money on your project
696 Bourke Street, Melbourne,
VIC 3000, Australia
Tel: +61 3 9240 0200 Fax: +61 3 9240 0299
Email: [EMAIL PROTECTED] www.aconex.com
This email and any attachments are intended solely
On 01/08/2007, at 4:01 PM, Milos Kleint wrote:
AFAIK that's intentional. To avoid people downloading the whole
repo through wget. rsynch is the preferred method I think.
Then why is curl not rejected? Why is Archiva failing? Why is my
local mvn retrieval also failing?
I'm happy to
It looks like your running a *nix, but can you tell us specifically
what OS, JDK version, Maven version, etc? We've had Windows users run
into similar problems who were having troubles due to overzealous
antivirus software, etc.
maven 2.0.6 running on both OSX and RedHat EL3 (happens across
=
'218016709d90d14b64bfb1de3a86a2247e8873db' - IGNORING
Is there something wacky with the repository? It seems to eventually
go away.
Paul Smith
Core Engineering Manager
Aconex
The easy way to save time and money on your project
696 Bourke Street, Melbourne,
VIC 3000, Australia
Tel: +61 3 9240 0200 Fax: +61 3
I'm not sure whether it's the xmlbeans bit that it's worried about
but then complaining about commons-beanutils, I've specifically
excluded xmlbeans-jsr173 in my pom from the dependency I _think_
it's coming from:
I managed to 'find' a version of xmlbeans-jsr173 and deployed that to
On 24/07/2007, at 5:16 PM, Paul Smith wrote:
I've been (slowly) porting our application to Maven 2.0.x. Run up
against a very weird dependency problem with a project that refuses
to build anymore. See the full mvn -X output, but the snippet that
appears to me to be the problem
I tried the archiva alpha-2 distribution and trunk, but I'm having
trouble do a simple 'mvn deploy' to an Archiva snapshot repo that has
been freshly setup with just the admin user.
I get this output:
[INFO] [deploy:deploy]
altDeploymentRepository = null
[INFO] Retrieving previous
Can you point out where you read that?
Michael is correct. Right now, it should be dav:http:// for
deployment.
Ok, now I'm starting to think I ate some bad cheese and was
hallucinating. the dav:http://... works.I had tried dav://...
and http://; but not dav:http://;. I was
/properties
/profile
/profiles
...
Paul Smith
Core Engineering Manager
Aconex
The easy way to save time and money on your project
696 Bourke Street, Melbourne,
VIC 3000, Australia
Tel: +61 3 9240 0200 Fax: +61 3 9240 0299
Email: [EMAIL PROTECTED] www.aconex.com
This email
and to be clear (sorry), the build still completes ok, but the
resulting filtering is using the one derived from settings.xml, and
not the explicit profile asked for on the command line..
Paul
On 06/06/2007, at 9:56 AM, Paul Smith wrote:
mvn 2.0.4
I'm sure this is plainly my
13 matches
Mail list logo
