error in plugin JUCMNav eclipse - eclipse-plugin

I am trying to add jUCMNav to eclipse, and I am getting this error:
Cannot complete the install because one or more required items could not be found.
Software being installed: jUCMNav: URN Editor (UCM and GRL) 6.0.0 (seg.jUCMNav.feature.group 6.0.0)
Missing requirement: jUCMNav 6.0.0 (seg.jUCMNav 6.0.0) requires 'bundle org.eclipse.e4.core.contexts 1.3.1' but it could not be found
Cannot satisfy dependency:
From: jUCMNav: URN Editor (UCM and GRL) 6.0.0 (seg.jUCMNav.feature.group 6.0.0)
To: seg.jUCMNav [6.0.0]
what should I do to complete the installation ? any help is much appreciated
PS: the link that I added for the installation is :
http://jucmnav.softwareengineering.ca/jucmnav/updatesite/

I had the same problem when i was using eclipse Indigo.
I took the latest version of eclipse and it worked fine.

Related

undefined keyword error in pycharm robot framework

i am using pycharm with intellibot and robot framework plugins. one of a sudden, keywords turned undefined like "click element". but other robot framework libraries works well.
com.intellij.diagnostic.PluginException: getComponentAdapterOfType is used to get com.intellij.psi.impl.PsiManagerImpl (requestorClass=com.millennialmedia.intellibot.psi.RobotPsiManager, requestorConstructor=public com.millennialmedia.intellibot.psi.RobotPsiManager(com.intellij.psi.impl.PsiManagerImpl)).
Probably constructor should be marked as NonInjectable. [Plugin: com.millennialmedia.intellibot]
at com.intellij.serviceContainer.ConstructorParameterResolver.findTargetAdapter(ConstructorParameterResolver.kt:111)
at com.intellij.serviceContainer.ConstructorParameterResolver.resolveInstance(ConstructorParameterResolver.kt:59)
at com.intellij.serviceContainer.ConstructorInjectionKt.instantiateUsingPicoContainer(constructorInjection.kt:45)
at com.intellij.serviceContainer.PlatformComponentManagerImpl.instantiateClassWithConstructorInjection(PlatformComponentManagerImpl.kt:505)
at com.intellij.serviceContainer.MyComponentAdapter.doCreateInstance(MyComponentAdapter.kt:35)
at com.intellij.serviceContainer.BaseComponentAdapter.getInstanceUncached(BaseComponentAdapter.kt:110)
at com.intellij.serviceContainer.BaseComponentAdapter.getInstance(BaseComponentAdapter.kt:72)
at com.intellij.serviceContainer.BaseComponentAdapter.getInstance$default(BaseComponentAdapter.kt:65)
at com.intellij.serviceContainer.PlatformComponentManagerImpl.createComponents(PlatformComponentManagerImpl.kt:177)
at com.intellij.openapi.project.impl.ProjectImpl.init(ProjectImpl.java:295)
at com.intellij.openapi.project.impl.ProjectManagerImpl.initProject(ProjectManagerImpl.java:315)
at com.intellij.openapi.project.impl.ProjectManagerImpl.convertAndLoadProject(ProjectManagerImpl.java:624)
at com.intellij.platform.PlatformProjectOpenProcessor.prepareProject(PlatformProjectOpenProcessor.java:315)
at com.intellij.platform.PlatformProjectOpenProcessor.lambda$openExistingProject$0(PlatformProjectOpenProcessor.java:241)
at com.intellij.platform.ProjectUiFrameAllocator$run$1$1.run(ProjectFrameAllocator.kt:77)
at com.intellij.openapi.progress.impl.CoreProgressManager$2.run(CoreProgressManager.java:247)
at com.intellij.openapi.progress.impl.CoreProgressManager$TaskRunnable.run(CoreProgressManager.java:888)
at com.intellij.openapi.progress.impl.CoreProgressManager$5.run(CoreProgressManager.java:441)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:163)
at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:585)
at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:531)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:59)
at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:150)
at com.intellij.openapi.application.impl.ApplicationImpl.lambda$null$4(ApplicationImpl.java:441)
at com.intellij.util.ConcurrencyUtil.runUnderThreadName(ConcurrencyUtil.java:221)
at com.intellij.util.ConcurrencyUtil.lambda$underThreadNameRunnable$3(ConcurrencyUtil.java:209)
at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:238)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
I am facing same issue but it got resolved by the following steps.
Go to https://github.com/lte2000/intellibot/blob/develop/intellibot.jar
Download the jar file
Open PyCharm -> Settings -> Plugins -> Click on Setting Icon (Right side from the Installed tab) -> Select Install plugin from Disk
Import the jar file in PyCharm editor
Click on Restart
Intellibot plugin exception still continue, but I fixed undefined keyword problem by installing "IntelliBot #SeleniumLibrary Patched" plugin.
This answer might be too late, but here we go
I faced the same issue. additionally, pycharm wasn't recognizing some of the keywords.
My plug-in was version IntelliBot 0.10.143.381 (pycharm plugin marketplace)
On Intellibot GitHub the latest version is 0.13.191.8026
So.
I uninstall the old plugin.
Download the release version on Github
https://github.com/lte2000/intellibot/releases/tag/v0.13.191.8026
Install the new version
Now everything is working, no more error notifications and no more problems with the syntax highlight

Strange error when upgrading play-services-auth from 15.0.0 to 16.0.1

For my android project I upgraded play-services-auth library version from 15.0.0 to 16.0.1
Since then I see following error during the build and it also produces
ajcore files
I have removed my .gradle caches and done build and still see this error.
Anybody else seen this before, how do I fix it?
java.lang.IllegalStateException: Expecting .,<, or ;, but found authapi while unpacking Lcom/google/android/gms/common/api/internal/BaseImplementation$ApiMethodImpl;
at org.aspectj.util.GenericSignatureParser.parseClassTypeSignature(GenericSignatureParser.java:204)
at org.aspectj.util.GenericSignatureParser.parseFieldTypeSignature(GenericSignatureParser.java:155)
at org.aspectj.util.GenericSignatureParser.parseTypeArgument(GenericSignatureParser.java:267)
In my case, removing the Hugo logging plugin fixed the issue.
Check in your gradle file if you have it configured.
classpath 'com.jakewharton.hugo:hugo-plugin:1.2.1'
It happens because some plugin (added by you) use libs:
org.aspectj:aspectjtools
or
org.aspectj:aspectjrt for codegeneration

`Error:osgi: [optaplanner-core] Unexpected build error` on building CloudBalancingHelloWorld

I cloned optaplanner's repository.
I imported the top-level pom.xml in IntelliJ IDEA.
Then I tried to run org.optaplanner.examples.cloudbalancing.app.CloudBalancingHelloWorld.
I get the following error: Error:osgi: [optaplanner-core] Unexpected build error
The doc says the maven integration will take care of the rest, so I guess I am missing something.
Question 1: Can I somewhat configure IDEA (or use the CLI) to show more verbose errors, so that I can debug it? Unexpected build error is not enough information for me to figure that problem out.
Question 2: How can I fix this error?
FYI, this box is running Ubuntu 18.04 (edit: exact same issue on Fedora 28). My maven version is as follows.
$ mvn --version
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-25T04:49:05+09:00)
Maven home: /opt/apache-maven-3.5.3
Java version: 1.8.0_181, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.15.0-32-generic", arch: "amd64", family: "unix"
EDIT: IntelliJ version: 2018.2.1
Run configuration:
You should disable the Osmorc plugin in IDEA. After thay the project will normally build
Intellij IDEA's OSGI plugin chould not recongnized properties like parsedVersion.*, which was generate by org.codehaus.mojo:build-helper-maven-plugin added in parent project org.kie:kie-parent.
You should disable the OSGI plugin, or add following code to /pom.xml manually.
<properties>
...
<parsedVersion.majorVersion>7</parsedVersion.majorVersion>
<parsedVersion.minorVersion>28</parsedVersion.minorVersion>
<parsedVersion.incrementalVersion>0</parsedVersion.incrementalVersion>
</properties>
Drools and jbpm has the same issue, because they also use org.kie:kie-parent as parent project. It could be sloved by the same way.
i meet the same problem,and solve it later.
first,remove the osgi module in Project Structure->Facets .
then, change the Run/Debug Configurations as the project README.adoc said.
after all ,i can run it successfully.

Can't find ogg with PkgConfig

I'm trying to build secondlife viewer but fail on:
Building 'Second Life Test' Version 3.8.5.34241
-- Found PkgConfig: /usr/bin/x86_64-pc-linux-gnu-pkg-config (found version "0.29")
-- checking for module 'ogg'
-- package 'ogg' not found
I've libogg installed: https://bpaste.net/show/c6d60173da44
full build log: https://bpaste.net/show/9b3ecbd254c4
pkg_check_modules soruce: https://bitbucket.org/lindenlab/viewer-release/src/dfd2e1723b72b62e8b6c3746fd5f7fbb1132f389/indra/cmake/Audio.cmake?at=default&fileviewer=file-view-default
full build log shows that I'm using USESYSTEMLIBS flag, that means that pkg_check_modules(OGG REQUIRED ogg) just doesn't find /usr/lib64/pkgconfig/ogg.pc with some reason...
What could cause such mysterious bug?
(here is CMakeOut log : https://bpaste.net/show/a2fc804afc73)
pkg-config --exists ogg --print-errors returns nothing
seems like just CMake doesn't work right -__-' https://github.com/Techwolf/techwolf-overlay/issues/2#issuecomment-144851500
This bug is in cmake 3.3.x, downgrade to 3.2.3-r1 will fix it
everything works with 3.2.3
-- checking for module 'ogg'
-- found ogg, version 1.3.2

How to build apache HCatalog 0.5.0?

Its been almost 3 hours and I'm not able to build this. Please can anybody provide the steps. All the documents suggest to use hcatalog-src-0.5.0-incuvating.tar.gz but this is not available anywhere on internet (ad far as I've searched). Then I downloaded the branch 0.5.0 but as per the documentation
http://docs.hortonworks.com/HDPDocuments/HDP1/HDP-1.2.0/ds_HCatalog/install.pdf
of version 0.5.0 you have to build l=using command
ant_home/bin/ant -Dhcatalog.version=0.5.0 -Dforrest.home=forrest_home tar
Now the problem is that the build.xml do not have a target named 'tar'. So I just browsed the build.xml and tried the same command using target as 'package'
ant_home/bin/ant -Dhcatalog.version=0.5.0 -Dforrest.home=forrest_home package
but then its showing me error.
BUILD FAILED
C:\Users\admnilesh\Desktop\hcatalog-branch-0.5\build.xml:71: The following error
occurred while executing this line:
C:\Users\nilesh\Desktop\hcatalog-branch-0.5\build-support\ant\deploy.xml:67:
Unable to resolve artifact: Unable to get dependency information: Unable to read
the metadata file for artifact 'com.sun.jersey:jersey-core:jar': Cannot find pa
rent: net.java:jvnet-parent for project: com.sun.jersey:jersey-project:pom:1.9.1
for project com.sun.jersey:jersey-project:pom:1.9.1
com.sun.jersey:jersey-core:jar:1.9.1
from the specified remote repositories:
apache.snapshots (http://repository.apache.org/snapshots),
central (http://repo1.maven.org/maven2),
glassfish-repository (http://maven.glassfish.org/content/groups/glassfish),
datanucleus (http://www.datanucleus.org/downloads/maven2)
Path to dependency:
1) org.apache.hcatalog:webhcat:jar:0.5.0-SNAPSHOT
Please help me out.
We've been having the same trouble and discussing it over at the hcatalog-user mailing list for the last couple of days. You can have a look at https://issues.apache.org/jira/browse/HCATALOG-601 to see what's being done about this problem.
Quick summary though : Jersey 1.9 depended on a glassfish maven repo, which no longer exists. Bump your jersey dep version from 1.9 to 1.14 and you should be able to build.
Edit : One more thing - we're still going through the release process to release the 0.5.0 incubating candidate, the latest candidates are being put up currently on http://people.apache.org/~travis/ . We should see a public release in a couple of days. In the meanwhile, I suggest poking over at our hcatalog-user mailing list : http://incubator.apache.org/hcatalog/mailing_lists.html
I got the same error while giving target "tar". On specifying the target as "package", the build proceeds ahead but fails with following error:
satish#dev1$ /usr/bin/ant -Dhcatalog.version=0.5.0 -Dforrest.home=/home/satish/work/forrest/apache-forrest-0.9 package
[artifact:dependencies] Unable to resolve artifact: Missing:
[artifact:dependencies] ----------
[artifact:dependencies] 1) org.apache.hcatalog:hcatalog-core:jar:0.5.0
[artifact:dependencies]
[artifact:dependencies]
[artifact:dependencies] Path to dependency:
[artifact:dependencies] 1) org.apache.hcatalog:hcatalog-pig-adapter:jar:0.5.0- incubating
[artifact:dependencies] 2) org.apache.hcatalog:hcatalog-core:jar:0.5.0
[artifact:dependencies] ----------
This issue got resolved by specifying project.version as "0.5.0-incubating" instead of "0.5.0" in build command line. The reason for error is that build installs hcatalog-core artifact as hcatalog-core-0.5.0-incubating.jar. However because of wrong project.version, the dependent projects were instead searching for hcatalog-core-0.5.0.jar.
Build succeeded with:
satish#dev1$ /usr/bin/ant -Dhcatalog.version=0.5.0-incubating -Dforrest.home=/home/satish/work/forrest/apache-forrest-0.9 package