Good day to you, Raghu ,
Possible explanations to why that is happening:
1. hibernate-3.0 was already there when you ran your maven command ( do a
mvn clean first to be sure )
2. The binaries hibernate-3.0 and hibernate-3.0.5 does not have the same
groupId and artifactId.
3. It was added there by some other means like via dependency plugin, antrun
plugin etc.
Possible way to fix this:
1. Do mvn clean install
2. Check if both hibernate-3.0 and hibernate-3.0.5 are still in your target
* If they are, then we've ruled out possibility #1 ( end here )
3. Do a mvn project-info-reports:dependencies ( or if that's too hard to
memorize, you can use mvn site:site instead ).
4. Browse through the generated dependencies report (
target\site\dependencies.html )
5. Check if you have a two binaries with the artifactId hibernate but with
different groupId
* If true, then that explains why those two are there.
* To see whether what dependencies you're using, do a mvn
dependency:analyze
* Fix your list of dependencies in your pom.xml ( end here )
6. Check your build again and see if there is any goals that copies
hibernate-3.0 to your target.
Cheers,
Franz
raghurajan.x.gurunathan wrote:
>
> Hi All
>
> I use maven-2.0.4 and having this, problem i have defined my pom.xml as
>
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate</artifactId>
> <version>3.0.5</version>
> </dependency>
>
> but when i run the mvn deploy its also including hibernate-3.0, eventhough
> its getting the proper version 3.0.5,
>
> I know i saw some threads regarding this some time, but i forgot, what it
> is, can anyone help me here, ??
>
>
> Thanks,
> Raghu |
>
>
> -----------------------------------------
> This communication is for informational purposes only. It is not
> intended as an offer or solicitation for the purchase or sale of
> any financial instrument or as an official confirmation of any
> transaction. All market prices, data and other information are not
> warranted as to completeness or accuracy and are subject to change
> without notice. Any comments or statements made herein do not
> necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
> and affiliates.
>
> This transmission may contain information that is privileged,
> confidential, legally privileged, and/or exempt from disclosure
> under applicable law. If you are not the intended recipient, you
> are hereby notified that any disclosure, copying, distribution, or
> use of the information contained herein (including any reliance
> thereon) is STRICTLY PROHIBITED. Although this transmission and any
> attachments are believed to be free of any virus or other defect
> that might affect any computer system into which it is received and
> opened, it is the responsibility of the recipient to ensure that it
> is virus free and no responsibility is accepted by JPMorgan Chase &
> Co., its subsidiaries and affiliates, as applicable, for any loss
> or damage arising in any way from its use. If you received this
> transmission in error, please immediately contact the sender and
> destroy the material in its entirety, whether in electronic or hard
> copy format. Thank you.
>
> Please refer to http://www.jpmorgan.com/pages/disclosures for
> disclosures relating to UK legal entities.
>
>
--
View this message in context:
http://www.nabble.com/Dependency-problem-tf3517261s177.html#a9820993
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
