- This topic has 4 replies, 2 voices, and was last updated 9 years, 3 months ago by jhugohr.
-
AuthorPosts
-
piougyParticipantHello,
We have an error when installing JBoss tools 4.2.3 on Eclipse 4.4.2 Standard
Unable to resolve Package
–Software to be resolved has different definitions for the same ID + version pair; this breaks the deterministic nature of provisioning and resolution can not proceed. Problematic IUs: [org.eclipse.jpt.jpa.feature.feature.group_3.4.1.v201410241959]
–Encountered problems while resolving DsiApplisThanks
jhugohrMemberHello,
can you pls provide some more info:
– Are you importing the update site as a third party library on the admin console?
– or, are you trying via Update Site or Marketplace?
– What features are you selecting while importing the library?
– or are you selecting the ‘Import all’?
– Does your package has any other software installed ?We had tried several JBoss features and they installed ok, that’s why we would like you to provide more details, but so far we have not been able to reproduce the issue.
Thanks in advance and will look forward your response.
Regards Hugo Herrera,
SDC Support Team
piougyParticipantHello,
I have this probleme using update site url (Third-Party Librairies) :
http://download.jboss.org/jbosstools/updates/stable/luna/
or with archive download at http://sourceforge.net/projects/jboss/files/JBossTools/jbosstools4.2.x/jbosstools-4.2.3.Final_2015-03-26_22-41-56-B370-updatesite-core.zip
First time i check import all (don’t work)
I chek only one feature (jboss common) don’t work
with same errorThanks a lot
jhugohrMemberHello,
thank you for your response, could you also please share with us the logs of your Delivery Hub and the Admin Console? you can find them under:
Delivery Hub:
<$install-dir>/Data Files/logsAdmin Console:
<$install-dir>/Admin Console/logsThe Delivery Hub logs can also be downloaded from inside the Admin Console, look for an action “Download all server logs” at the “Monitoring” tab inside ‘Administration -> System’ section
Regards Hugo Herrera
SDC Support.
jhugohrMemberHello,
We’ve been through the steps along with the screenshots you provided and the ‘Verify’ worked in our side. Could you please import the update site into a new Third Party Library again, it could be the case that the update site had changed from the time you’ve imported it.
Otherwise there is a workaround, but, please try re-importing first.
To try the workaround, you can try editing the ‘package.xml’ file for the package that is failing and add a package property.
The problem you are facing is that for some reason there are two versions of
org.eclipse.jpt.jpa.feature.feature.group 3.4.1.v201410241959
with different JPA requirements. The package property will make the Verify phase skip this extra level of checking.ATTENTION: org.eclipse.jpt.jpa.feature.feature.group 3.4.1.v201410241959 has differing requirements across sites: [javax.persistence 0.0.0, javax.persistence [2.1.0.v201304241213]]
Try by following these steps:
1) Stop the Admin Console
2) To find package ‘package.xml’ file, get into the following directory:<$installation-dir>/Admin Console/local-storage/metavc/packages
on it you will find existing packages guid. You need to enter on each one and look for the ‘package.xml’ file. Open the file and look into the branding tag for your package title.
3) Add the following tags at the bottom of the file, before ‘</package>’ tag.
<properties>
<property key=”skip.misconfigured.ius” value=”true”></property></properties>
4) Restart the Admin Console
5) Try ‘Verify’ againHope this will help you to move forward.
If you have any comment, please let us know.
Regards Hugo Herrera,
SDC Support Team -
AuthorPosts