Hi Butlers, sorry, my mistake. In fact, watching better the error screenshot you posted, it is failing to find equinox-registry, which as you properly explained is in your local repository, and not equinox-common, which I thought about seeing that you posted that dependency.
Are you sure the version element in the equinox-registry POM file in your local repository has the right gpoupid-artifactid-version in it? Seems like Maven is not seeing it, and going to the remote repository to find it. Can you post the pom file that should be on you hard disk in c:\Documents and settings\yourusername\.m2\repository\org\eclipse\equinox\registry\3.4.0-v20080516-0950\....pom? Also, have you used maven to install it in your local repository? Or just copied the file over there by hand? Simone buters wrote: > Thank you, Simone, very much. :-) > > I think that the analyse is very helpful, but I guess that I have an another > case. :-( > > I've looked at http://repo1.maven.org/maven2/org/eclipse/equinox/registry/ > There are two artefact versions there: 3.2.1-R32x_v20060814 and > 3.3.0-v20070522. I.e. exactly those ones that is displayed in the error. But > the correct version of org.eclipse.equinox.registry, 3.4.0-v20080516-0950, > exists only in my local repository and it's conform with the range > [3.4.0,4.0.0). > > Also Maven is looking for in the remote repository and ignoring the version > of the local one. > > Why? 8-O 8-O 8-O > > > Simone Gianni-2 wrote: > >> Hi Buters, >> seems like it is not searching for equinox-common-3.2.* but for >> equinox-common-3.4.x, and fails to find a 3.4 or higher version, cause >> only 3.2.1 and 3.3.0 are present, both under the 3.4-4.0 range. >> >> Probably some other dependency is raising the minimum version range, and >> Maven will always try to fetch a recent version (3.4.x in this case) to >> avoid errors. >> >> You could try using mvn dependency:analyze goal to perform an analysis >> of all dependencies and see who is requiring equinox-common version 3.4 >> or better. See http://maven.apache.org/plugins/maven-dependency-plugin/ >> for more deails on how dependency plugin works. >> >> Also, running maven with the -X switch will give you detailed >> informations (debug stuff) where you can find why it decides to search >> for 3.4 instead of 3.2. >> >> Hope this helps, >> Simone >> >> >> buters wrote: >> >>> Hi all, >>> >>> http://www.nabble.com/file/p19825141/rcp_err.png >>> >>> There is org.eclipse.equinox.registry-3.4.0-v20080516-0950.jar In my >>> local >>> repository. >>> There is one dependency in its pom.xml: >>> <dependencies> >>> <dependency> >>> <groupId>org.eclipse.equinox</groupId> >>> <artifactId>common</artifactId> >>> <version>[3.2.0,4.0.0)</version> >>> </dependency> >>> </dependencies> >>> >>> The question: where should I search for [3.2.1-R32x_v20060814, >>> 3.3.0-v20070522] and [3.4.0,4.0.0)??? >>> :confused::confused::confused: >>> >>> Thanks beforehand, >>> regards, buters >>> >>> >> -- >> Simone Gianni CEO Semeru s.r.l. Apache Committer >> MALE human being programming a computer http://www.simonegianni.it/ >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> > > -- Simone Gianni CEO Semeru s.r.l. Apache Committer MALE human being programming a computer http://www.simonegianni.it/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
