This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

empty SCM error

Hello Forum,

I recently installed OO Studio 10.50 and tried to connect to our SVN-Repository. Turtoise-SVN works, but the OO Studio internal SCM does not work. In the Studio.log there is a line about the imported certificate, but then this appeares:

2016-10-26 09:04:43,419 ERROR ScmMessagesPanel.writeScmCommands:277 SCM message:

And the message is empty. When starting the OO Studio the following erros appear:

Caused by: java.lang.RuntimeException: Unable to execute mojo: Execution null of goal com.hp.oo:oo-bea-legacy-plugin:1.3.0:plugin-metadata failed: Plugin com.hp.oo:oo-bea-legacy-plugin:1.3.0 or one of its dependencies could not be resolved: The following artifacts could not be resolved: weblogic:weblogic:jar:10.3, weblogic:wljmsclient:jar:10.3.0.0, weblogic:wljmxclient:jar:10.3.0.0, weblogic:wlclient:jar:10.3.0.0, weblogic:com.bea.core.utils.wrapper:jar:1.3.0.0, weblogic:com.bea.core.weblogic.socket.api:jar:1.0.0.0, weblogic:com.bea.core.annogen:jar:1.2.0.0, weblogic:com.bea.core.common.security.api:jar:1.0.0.0_5-0-2-0, weblogic:com.bea.core.common.security.providers.env:jar:1.0.0.0_5-0-2-0, weblogic:com.bea.core.datasource:jar:1.4.0.0, weblogic:com.bea.core.descriptor:jar:1.4.0.0, weblogic:com.bea.core.descriptor.j2ee:jar:1.1.0.0, weblogic:com.bea.core.descriptor.j2ee.binding:jar:1.1.0.0, weblogic:com.bea.core.descriptor.wl:jar:1.1.0.0, weblogic:com.bea.core.descriptor.wl.binding:jar:1.1.0.0, weblogic:com.bea.core.diagnostics.core:jar:2.1.0.0, weblogic:com.bea.core.i18n:jar:1.4.0.0, weblogic:com.bea.core.logging:jar:1.4.0.0, weblogic:com.bea.core.management.core:jar:2.3.0.0, weblogic:com.bea.core.messaging.kernel:jar:1.4.0.0, weblogic:com.bea.core.resourcepool:jar:1.4.0.0, weblogic:com.bea.core.store:jar:1.4.0.0, weblogic:com.bea.core.store.gxa:jar:1.4.0.0, weblogic:com.bea.core.transaction:jar:2.5.0.0, weblogic:com.bea.core.utils.classloaders:jar:1.4.0.0, weblogic:com.bea.core.utils.full:jar:1.4.0.0, weblogic:com.bea.core.weblogic.lifecycle:jar:1.1.0.0, weblogic:com.bea.core.weblogic.rmi.client:jar:1.4.0.0, weblogic:com.bea.core.weblogic.saaj:jar:1.3.0.0, weblogic:com.bea.core.weblogic.security:jar:1.0.0.0_5-0-2-0, weblogic:com.bea.core.weblogic.security.auth:jar:1.0.0.0, weblogic:com.bea.core.weblogic.security.digest:jar:1.0.0.0, weblogic:com.bea.core.weblogic.security.identity:jar:1.1.0.0, weblogic:com.bea.core.weblogic.security.logger:jar:1.1.0.0, weblogic:com.bea.core.weblogic.security.wls:jar:1.0.0.0_5-0-2-0, weblogic:com.bea.core.weblogic.stax:jar:1.4.0.0, weblogic:com.bea.core.weblogic.web.api:jar:1.2.0.0, weblogic:com.bea.core.weblogic.workmanager:jar:1.4.0.0, weblogic:com.bea.core.workarea:jar:1.4.0.0, weblogic:com.bea.core.xml.beaxmlbeans:jar:1.0.0.0_2-4-0, weblogic:com.bea.core.xml.stax:jar:1.1.0.0, weblogic:com.bea.core.xml.staxb.buildtime:jar:1.3.0.0, weblogic:com.bea.core.xml.staxb.runtime:jar:1.3.0.0, weblogic:com.bea.core.xml.weblogic.xpath:jar:1.1.0.0, weblogic:com.bea.core.xml.xmlbeans:jar:1.0.0.0_2-4-0: Cannot access (C:\Users\Paul Markwart\.oo\data\maven) in offline mode and the artifact weblogic:weblogic:jar:10.3 has not been downloaded from it before.

Thanks in advance.

  • 0  

    Hi Paul,

    regarding the SCM - I do not see the certificate error but that might be the problem you are facing and need to investigate/fix.

    As for the other errors you see, those are related to 3rd party libraries that are not imported in your system. I suggest you start with this link and make sure you read about this jar before using it.

    https://hpln.hpe.com/contentoffering/oo-third-party-libraries-content 

  • 0 in reply to   

    Hi all,

    We encountered the same issue, solution --> install Microsoft Visual C 2010 SP1 Redistributable package (x86).

  • Suggested Answer

    0 in reply to 

    Huge thanks for your solution, Nick!  I got a great new work laptop yesterday and was puzzling over this issue for way too long.  As per the original poster, I couldn't see how Tortoise was okay, certificates were not an issue, everything was installed properly, etc.  The Studio log suggested a Git Client issue (I use SVN), but I even tried installing the Git Client.  Got rid of the error, but not the problem.  You did that :-)

  • Suggested Answer

    0 in reply to 

    Huge thanks for your solution, Nick!  I got a great new work laptop yesterday and was puzzling over this issue for way too long.  As per the original poster, I couldn't see how Tortoise was okay, certificates were not an issue, everything was installed properly, etc.  The Studio log suggested a Git Client issue (I use SVN), but I even tried installing the Git Client.  It got rid of the error, but not the problem.  You did that :-)

  • 0 in reply to 

    Huge thanks for your solution, Nick!  I got a great new work laptop yesterday and was puzzling over this issue for way too long.  As per the original poster, I couldn't see how Tortoise was okay, certificates were not an issue, everything was installed properly, etc.  The Studio log suggested a Git Client issue (I use SVN), but I even tried installing the Git Client.  It got rid of the error, but not the problem.  You did that :-)

  • 0 in reply to 

    Huge thanks for your solution, Nick!  I got a great new work laptop yesterday and was puzzling over this issue for way too long.  As per the original poster, I couldn't see how Tortoise was okay, certificates were not an issue, everything was installed properly, etc.  The Studio log suggested a Git Client issue (I use SVN), but I even tried installing the Git Client.  It got rid of the error, but not the problem.  You did that :-)