Maven central repo is missing metadata for Mockito

[GoogleCodeExporter]

What steps will reproduce the problem?
Navigate to http://repo1.maven.org/maven2/org/mockito/mockito-core/

What is the expected output? 
I expect to see a maven-metadata.xml file.

I noticed this issue when versions-maven-plugin said it couldn't find
Mockito.  It is one of the tools that relies on accurate metadata.

An example of a maven-metadata.xml file can be seen in this directory:
http://repo1.maven.org/maven2/junit/junit/

Original issue reported on code.google.com by lukewpat...@gmail.com on 19 Mar 2009 at 2:29

[GoogleCodeExporter]

Usually the "maven-metadata.xml" file is created as part of the Maven deploy 
step, 
correct? How does the current JAR artifact deployment procedure for Mockito 
work?

Original comment by alex.h...@gmail.com on 19 Mar 2009 at 2:45

[GoogleCodeExporter]

Why would you need the maven-metadata.xml ?
Yes, the file is produced when you deploy with maven, which we don't use.

We just layout artifact according to maven repo organization and rsync.

Original comment by iczechowski@gmail.com on 22 Mar 2009 at 8:19

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by iczechowski@gmail.com on 22 Mar 2009 at 8:20

[GoogleCodeExporter]

reply to Comment 2

investigating, connecting the dots here:
http://jira.codehaus.org/browse/MEV-443?focusedCommentId=170575&page=com.atlassi
an.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_170575

Original comment by lukewpat...@gmail.com on 22 Mar 2009 at 8:54

[GoogleCodeExporter]

Would you like to use version ranges for Mockito ?
The issue you mentioned, doesn't list Mockito anywhere. 
Is this some general initiative to fix metadata ?

I'd be glad to see the case where you need maven-metadata.xml, than we may 
consider 
to update it with the next release.

Original comment by iczechowski@gmail.com on 22 Mar 2009 at 9:18

[GoogleCodeExporter]

"Would you like to use version ranges for Mockito ?"
No, I noticed the effects of missing metadata while using the 
versions-maven-plugin
to check for new Mockito versions.  The versions plugin said Mockito couldn't 
be found.
http://mojo.codehaus.org/versions-maven-plugin/

"Is this some general initiative to fix metadata ?"
No, I attached that link because it might answer the bigger questions about 
metadata
publishing responsibilities.  I found that after filing this bug and after 
reading
your questions from comment #2.

Original comment by lukewpat...@gmail.com on 22 Mar 2009 at 9:29

[GoogleCodeExporter]

Thanks for the info. I'm gonna take a look at it.
We have not released metadata as they were not necessary until now :)

Original comment by iczechowski@gmail.com on 22 Mar 2009 at 9:42

[GoogleCodeExporter]

Igor started working on our build file to include maven ant tasks. Next release,
we'll have correct metadata.

Original comment by szcze...@gmail.com on 21 Apr 2009 at 10:20

[GoogleCodeExporter]

Ok, the metadata is now correctly created by ant. (thanks Igor). Once we 
release it
will appear in maven central

Original comment by szcze...@gmail.com on 12 May 2009 at 9:37

[GoogleCodeExporter]

I just looked at the metadata file on Maven Central and it lists only the new 
release
candidate, version 1.8.0-rc1. Ideally, the metadata file should list all the
available versions, so that ranges can be used. For example, if I make a 
library that
is compatible with any version of Mockito after 1.7, I'd like to specify a 
dependency
on Mockito [1.7,) -- but I don't think that will work when 1.7 is not listed in 
the
metadata.

Original comment by at...@chebucto.ns.ca on 11 Jun 2009 at 2:52

[GoogleCodeExporter]

Oh, I see. We've just started generating the metadata therefore previous 
versions are
not included. It should be easy to fix with the full release that will come up 
around
~Monday.

Original comment by szcze...@gmail.com on 11 Jun 2009 at 8:56

[GoogleCodeExporter]

Original comment by szcze...@gmail.com on 11 Jun 2009 at 8:57

• Added labels: Milestone-Release1.8

[GoogleCodeExporter]

Fixed in rc2. It's already in the maven central.

Original comment by szcze...@gmail.com on 18 Jun 2009 at 11:05

• Changed state: Fixed