RE: [M2] Just need the open source eyes on this

2006-12-04 Thread Peter . Pilgrim
 -Original Message-
 From: Pilgrim, Peter 
 Sent: 04 December 2006 16:10
 To: 'Maven Users List'
 Subject: [M2] Just need the open source eyes on this 
 
 Hi
 
 Maven says it cant download the file from the internal repository.
 
 Anything out of the ordinary of this maven-metadata.xml file.
 

Ignore I think firewall proxy issues are preventing the routing
access direct to internal repository from the machine.



BTW: Any one got a good guide to the metadata format and explanation?
Most of it I did was guess work.

 
 ?xml version=1.0?
 metadata
   groupIdorg.easymock/groupId
   artifactIdeasymock/artifactId
   version2.2/version
   versioning
 latest2.2/latest
 release2.2/release
 
 versions
   version1.2/version
   version2.2/version
 /versions
 lastUpdated20061120170542/lastUpdated
   /versioning
 /metadata
 !--*PP* Mon Nov 20 17:05:42 GMT 2006 --
 
 Error
 
 [INFO] Error building POM (may not be this project's POM).
 
 
 Project ID: org.easymock:easymock
 
 Reason: Error getting POM for 'org.easymock:easymock' from 
 the repository: Error  transferring file
   org.easymock:easymock:pom:1.2
 
 from the specified remote repositories:
   central (http://repo1.maven.org/maven2),
   ptsp-repository 
 (file://V:\pilgripe_PTSP1_2\LDN_PTS/build/repository),
   ptsp-internal 
 (http://sldn0868dap.ldn.swissbank.com:9091/internal/maven-reposi
 tory)
 
--
Peter Pilgrim
UBS Investment Bank, 
PTS Portal / IT FIRC OPS LDN,
100 Liverpool Street, London EC2M 2RH, United Kingdom
+44 (0) 20 75 75692
:: Java EE / E-Commerce / Enterprise Integration / Development ::
 

Visit our website at http://www.ubs.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [M2] Just need the open source eyes on this

2006-12-04 Thread Wayne Fay

Do you have the corresponding sha1 and md5 files next to the pom file
named ie blah-1.0.pom, blah-1.0.pom.sha1, blah-1.0.pom.md5? You will
need this for all files in the repository.

This can cause those error messages, IIRC.

Wayne

On 12/4/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

 -Original Message-
 From: Pilgrim, Peter
 Sent: 04 December 2006 16:10
 To: 'Maven Users List'
 Subject: [M2] Just need the open source eyes on this

 Hi

 Maven says it cant download the file from the internal repository.

 Anything out of the ordinary of this maven-metadata.xml file.


Ignore I think firewall proxy issues are preventing the routing
access direct to internal repository from the machine.



BTW: Any one got a good guide to the metadata format and explanation?
Most of it I did was guess work.


 ?xml version=1.0?
 metadata
   groupIdorg.easymock/groupId
   artifactIdeasymock/artifactId
   version2.2/version
   versioning
 latest2.2/latest
 release2.2/release

 versions
   version1.2/version
   version2.2/version
 /versions
 lastUpdated20061120170542/lastUpdated
   /versioning
 /metadata
 !--*PP* Mon Nov 20 17:05:42 GMT 2006 --

 Error

 [INFO] Error building POM (may not be this project's POM).


 Project ID: org.easymock:easymock

 Reason: Error getting POM for 'org.easymock:easymock' from
 the repository: Error  transferring file
   org.easymock:easymock:pom:1.2

 from the specified remote repositories:
   central (http://repo1.maven.org/maven2),
   ptsp-repository
 (file://V:\pilgripe_PTSP1_2\LDN_PTS/build/repository),
   ptsp-internal
 (http://sldn0868dap.ldn.swissbank.com:9091/internal/maven-reposi
 tory)

--
Peter Pilgrim
UBS Investment Bank,
PTS Portal / IT FIRC OPS LDN,
100 Liverpool Street, London EC2M 2RH, United Kingdom
+44 (0) 20 75 75692
:: Java EE / E-Commerce / Enterprise Integration / Development ::


Visit our website at http://www.ubs.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [M2] Just need the open source eyes on this

2006-12-04 Thread Wendy Smoak

On 12/4/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:


Ignore I think firewall proxy issues are preventing the routing
access direct to internal repository from the machine.


Based on other problems you've reported, that sounds likely.  FWIW, I
think releases are discovered directly, by constructing the path to
the artifact, not by reading the metadata.


BTW: Any one got a good guide to the metadata format and explanation?
Most of it I did was guess work.


No, but feel free to add a page to the wiki.  'Guide to Maven
Repository Metadata' sounds like a useful thing to have. :)

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [M2] Just need the open source eyes on this

2006-12-04 Thread Peter . Pilgrim


 -Original Message-
 From: Wendy Smoak [mailto:[EMAIL PROTECTED] 
 Sent: 04 December 2006 16:50
 To: Maven Users List
 Subject: Re: [M2] Just need the open source eyes on this
 
 On 12/4/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 
  Ignore I think firewall proxy issues are preventing the 
 routing access 
  direct to internal repository from the machine.
 
 Based on other problems you've reported, that sounds likely.  
 FWIW, I think releases are discovered directly, by 
 constructing the path to the artifact, not by reading the metadata.


That's very interesting, Wendy.
In my experience you do need a maven-metadata.xml file with 
information that points to the versions of the artifact. 
 
  BTW: Any one got a good guide to the metadata format and 
 explanation?
  Most of it I did was guess work.
 
 No, but feel free to add a page to the wiki.  'Guide to Maven 
 Repository Metadata' sounds like a useful thing to have. :)
 

--
Peter Pilgrim
UBS Investment Bank, 
PTS Portal / IT FIRC OPS LDN,
100 Liverpool Street, London EC2M 2RH, United Kingdom
+44 (0) 20 75 75692
:: Java EE / E-Commerce / Enterprise Integration / Development ::
 

Visit our website at http://www.ubs.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [M2] Just need the open source eyes on this

2006-12-04 Thread Peter . Pilgrim

Hi

 -Original Message-
 From: Wayne Fay [mailto:[EMAIL PROTECTED] 
 Sent: 04 December 2006 16:48
 To: Maven Users List
 Subject: Re: [M2] Just need the open source eyes on this
 
 Do you have the corresponding sha1 and md5 files next to the 
 pom file named ie blah-1.0.pom, blah-1.0.pom.sha1, 
 blah-1.0.pom.md5? You will need this for all files in the 
 repository.
 
 This can cause those error messages, IIRC.
 
Thanks Wayne

I wrote a Java tool that regenerates the MD5 and SHA-1 files based on
Brett's DigestUtils.
The only thing I did was append a '\n' to the end of the files. Just so
I could 
execute `cat *.md5' and get a newline character on the command line. I
don't think 
that cause Maven fail though.

BTW: Your schema worked out quite well in the end. It is just so hard
find out when
Maven cant transfer a file down or work out what possible else has gone
wrong.

 
 On 12/4/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
   -Original Message-
   From: Pilgrim, Peter
   Sent: 04 December 2006 16:10
   To: 'Maven Users List'
   Subject: [M2] Just need the open source eyes on this
  
   Hi
  
   Maven says it cant download the file from the internal repository.
  
   Anything out of the ordinary of this maven-metadata.xml file.
  
 
  Ignore I think firewall proxy issues are preventing the 
 routing access 
  direct to internal repository from the machine.
 
 
 
  BTW: Any one got a good guide to the metadata format and 
 explanation?
  Most of it I did was guess work.
 
  
   ?xml version=1.0?
   metadata
 groupIdorg.easymock/groupId
 artifactIdeasymock/artifactId
 version2.2/version
 versioning
   latest2.2/latest
   release2.2/release
  
   versions
 version1.2/version
 version2.2/version
   /versions
   lastUpdated20061120170542/lastUpdated
 /versioning
   /metadata
   !--*PP* Mon Nov 20 17:05:42 GMT 2006 --
  
   Error
  
   [INFO] Error building POM (may not be this project's POM).
  
  
   Project ID: org.easymock:easymock
  
   Reason: Error getting POM for 'org.easymock:easymock' from the 
   repository: Error  transferring file
 org.easymock:easymock:pom:1.2
  
   from the specified remote repositories:
 central (http://repo1.maven.org/maven2),
 ptsp-repository
   (file://V:\pilgripe_PTSP1_2\LDN_PTS/build/repository),
 ptsp-internal
   (http://sldn0868dap.ldn.swissbank.com:9091/internal/maven-reposi
   tory)
  
====
--
Peter Pilgrim
UBS Investment Bank, 
PTS Portal / IT FIRC OPS LDN,
100 Liverpool Street, London EC2M 2RH, United Kingdom
+44 (0) 20 75 75692
:: Java EE / E-Commerce / Enterprise Integration / Development ::

Visit our website at http://www.ubs.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [M2] Just need the open source eyes on this

2006-12-04 Thread Wendy Smoak

On 12/4/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:


That's very interesting, Wendy.
In my experience you do need a maven-metadata.xml file with
information that points to the versions of the artifact.


If that were true across the board, no one would be able to use MyFaces 1.1.4.
  http://repo1.maven.org/maven2/org/apache/myfaces/core/myfaces-impl/
(The metadata only mentions the 1.1.2 version.)

Archiva may be more sensitive to incorrect metadata, however.

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [M2] Just need the open source eyes on this

2006-12-04 Thread Peter . Pilgrim


--
Peter Pilgrim
UBS Investment Bank, 
PTS Portal / IT FIRC OPS LDN,
100 Liverpool Street, London EC2M 2RH, United Kingdom
+44 (0) 20 75 75692
:: Java EE / E-Commerce / Enterprise Integration / Development ::
 

 -Original Message-
 From: Wendy Smoak [mailto:[EMAIL PROTECTED] 
 Sent: 04 December 2006 17:13
 To: Maven Users List
 Subject: Re: [M2] Just need the open source eyes on this
 
 On 12/4/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 
  That's very interesting, Wendy.
  In my experience you do need a maven-metadata.xml file with 
  information that points to the versions of the artifact.
 

I wonder if the problem is that the easymock 1.2 does not exist at the
moment
on central 

http://repo1.maven.org/maven2/org/easymock/easymock/


Hence Maven complains when over here we try to overrule the repository.
From the BBWM book in terms of precedure the local-most profiles wins
out. 
(Page 70)

I ran maven so that it activates a profile that points to the internal
repo. Is there a setting for a repository definiton inside a ``local
profile''
that overrules completely? 


 If that were true across the board, no one would be able to 
 use MyFaces 1.1.4.
http://repo1.maven.org/maven2/org/apache/myfaces/core/myfaces-impl/
 (The metadata only mentions the 1.1.2 version.)
 
 Archiva may be more sensitive to incorrect metadata, however.
 
I am not using Archiva because I could get Maven to download from the
Tomcat Server. I am just using a Tomcat with the DefaultServlet that
serves files from a directory instead.

 --
 Wendy
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

Visit our website at http://www.ubs.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [M2] Just need the open source eyes on this

2006-12-04 Thread Tom Huybrechts

For dependencies, the path in a local or remote repository can be
constructed using groupId, artifactId, version, classifier and type
since all of these are always known from the POM (or parent POMs).

For plugins the version is not always known. If no version is
specified for a given plugin, the resolver will use the metadata
(which are version independent) to retrieve the latest or release
version from the artifact metadata in local or remote repository.
e.g. 
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-ejb-plugin/maven-metadata.xml

In case you specify a short version for a plugin goal (like
eclipse:eclipse), then the resolver can map this on artifactIds using
group metadata for the registered plugin groups.
e.g. http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-metadata.xml

Tom

On 12/4/06, Wendy Smoak [EMAIL PROTECTED] wrote:

On 12/4/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

 That's very interesting, Wendy.
 In my experience you do need a maven-metadata.xml file with
 information that points to the versions of the artifact.

If that were true across the board, no one would be able to use MyFaces 1.1.4.
   http://repo1.maven.org/maven2/org/apache/myfaces/core/myfaces-impl/
(The metadata only mentions the 1.1.2 version.)

Archiva may be more sensitive to incorrect metadata, however.

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]