Manfred,

Ok thanks, I will look into doing that with the simple example. Unfortunately I 
cannot get rid of the proxy server as I am behind a firewall here and that is 
the only route out. However the two maven repository servers could be a better 
way to handle the proxy and the repositories. I have inherited the older 
file:// proxy from previous developers. 

However, I  still don't understand how come this project builds with no issues 
under maven 2?

Cheers,
Martin

-----Original Message-----
From: Manfred Moser [mailto:[email protected]] 
Sent: 24 November 2011 18:24
To: [email protected]
Subject: Re: maven 2 mirgration to maven 3

Most likely your problem is related to the proxy in settings.xml or the file:// 
repository in the pom.

I would remove your pom.xml and try to build a simple project like the simple 
example from the maven book

https://github.com/sonatype/simple-example

Ideally without the proxy.

In either case I would suggest to look at using a repository server like Nexus 
or Artifactory or Archiva to simplify these issues.

Using a file:// repository is definitely a bad idea.

manfred


On 11-11-24 10:12 AM, Martin Sweeney wrote:
> Manfred,
>
> Thanks for the reply and the tip about pastebin - never heard of it.
>
> I have created two pastes in the pastebin
>
> My pom.xml  http://pastebin.com/dRtyGVGz My settings.xml  
> http://pastebin.com/NHK60YBG
>
> All the documentation that I have seen so far has suggested exactly as you 
> say that maven 3 and maven 2 are compatible.  If you would like the error 
> output from the maven 3 build I can supply that as well.
>
> I can remove my entire local maven repository and get maven to download 
> everything again to see if this helps?
>
> Cheers,
> Martin
>
> -----Original Message-----
> From: Manfred Moser [mailto:[email protected]]
> Sent: 24 November 2011 18:02
> To: [email protected]
> Subject: Re: maven 2 mirgration to maven 3
>
> Maven 3 should be a drop in replacement. You might have to show us your 
> settings file.
>
> Also I would get rid of the manually installed artifacts since they most like 
> dont have the pom file (unless you added it as well) and will cause you 
> issues.
>
> In terms of file you will have to use pastebin or a gist since no attachments 
> are allowed on this list.
>
> manfred
> http://simpligility.com
>
> On 11-11-24 09:45 AM, Martin Sweeney wrote:
>> Hi,
>>
>> I am just getting up to speed with maven and I have a couple of projects 
>> that use maven. I have been fighting with maven / dependencies / mirrors and 
>> repositories for the better part of a week now with my projects always 
>> ending up with being unable to resolve dependencies. Usually on a bunch of 
>> the same jar files (commons-lang, commons-discovery - to name a couple).
>>
>> I am using maven 3.0.3 with jdk150_12.
>>
>> What I have found out is that I can manually install these jar files into my 
>> (what I assume to be local repository) using mvn install:install-file 
>> command. I get the correct successfully updated response to this command and 
>> re-run my mvn clean install command. Only to find that the result is exactly 
>> the same "build failure" with the same jar files being not found.
>>
>> If I look into my local repository and follow the artifact/group/version 
>> path I see my jar file is happily sitting there, but for some reason is not 
>> recognised or found.
>>
>> I dont understand how come it appears to me that maven 3.0.3 is not looking 
>> at my local repository for my files?
>> Also how come everytime I run the command mvn install maven 3.0.3 goes off 
>> into the internet and tries to download all the files again?
>>
>> I did some further investigation into the problem and actually went and got 
>> the binaries for maven 2.0.11. I updated my path variables and then re-ran 
>> my build on the project under maven 2.0.11 using mvn clean install. This 
>> time after an age of downloading and updating files the project successfully 
>> built. I have not changed any source code in the project or altered the pom 
>> file (which maybe the issue) in any way.
>>
>> I understood that maven 3 is backwards compatible with maven 2 projects?
>>
>> Is there any tutorials / migration paths / updates that I need to apply to 
>> my pom file to build the application under maven 3.0.3?
>>
>> I attached the pom and settings files and I can provide the environment 
>> paths etc required and I also have a list of missing jar files that are 
>> causing the issue that I can supply as well.
>>
>> I would like to build the project under maven 3 or at least understand why 
>> the project is not or cannot be built under maven 3.
>>
>> Any help on this would be greatly appreciated.
>>
>> Thanks,
>> Martin Sweeney
>> [email protected]<mailto:[email protected]>
>>
>>
>>
>>
>>
>>
>>
>> This is a PRIVATE message. If you are not the intended recipient please 
>> delete without copying and kindly advise us by e-mail of the mistake in 
>> delivery. NOTE: Regardless of content, this e-mail shall not operate to bind 
>> Payzone to any order or other contract unless pursuant to explicit written 
>> agreement or government initiative expressly permitting the use of e-mail 
>> for such purpose.
>> Thank you for your co-operation.
>>
>> Payzone Ireland  and Payzone Group are subsidiaries of Payzone Ventures Ltd.
>> Directors:  Robert Scott, David Gagie, Julian Gibbins, Arun Kaul, Iain 
>> Kennedy, Charlie Troup, Mike Maloney, Nigel Bell, Julian Rothwell.
>> Registered in UK;  Number: 7112083. Registered Office: Davidson House, 
>> Gadbrook Park, Northwich CW9 7TW.
>>
>> All e-mails are scanned for viruses. You should in addition carry out your 
>> own virus checks. Payzone cannot accept any liability for damage as a result 
>> of software viruses.
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
>
>
> This is a PRIVATE message. If you are not the intended recipient please 
> delete without copying and kindly advise us by e-mail of the mistake in 
> delivery. NOTE: Regardless of content, this e-mail shall not operate to bind 
> Payzone to any order or other contract unless pursuant to explicit written 
> agreement or government initiative expressly permitting the use of e-mail for 
> such purpose.
> Thank you for your co-operation.
>
> Payzone Ireland  and Payzone Group are subsidiaries of Payzone Ventures Ltd.
> Directors:  Robert Scott, David Gagie, Julian Gibbins, Arun Kaul, Iain 
> Kennedy, Charlie Troup, Mike Maloney, Nigel Bell, Julian Rothwell.
> Registered in UK;  Number: 7112083. Registered Office: Davidson House, 
> Gadbrook Park, Northwich CW9 7TW.
>
> All e-mails are scanned for viruses. You should in addition carry out your 
> own virus checks. Payzone cannot accept any liability for damage as a result 
> of software viruses.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>




This is a PRIVATE message. If you are not the intended recipient please delete 
without copying and kindly advise us by e-mail of the mistake in delivery. 
NOTE: Regardless of content, this e-mail shall not operate to bind Payzone to 
any order or other contract unless pursuant to explicit written agreement or 
government initiative expressly permitting the use of e-mail for such purpose.
Thank you for your co-operation.

Payzone Ireland  and Payzone Group are subsidiaries of Payzone Ventures Ltd.
Directors:  Robert Scott, David Gagie, Julian Gibbins, Arun Kaul, Iain Kennedy, 
Charlie Troup, Mike Maloney, Nigel Bell, Julian Rothwell.
Registered in UK;  Number: 7112083. Registered Office: Davidson House, Gadbrook 
Park, Northwich CW9 7TW.

All e-mails are scanned for viruses. You should in addition carry out your own 
virus checks. Payzone cannot accept any liability for damage as a result of 
software viruses.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to