JProfiler integrates fine into IntelliJ IDEA 12.0.4 and Eclipse 4.2.2 but it does not integrate into Scala IDE 3.0.0.
I have fresh installs of Scala IDE 3.0.0 (based on Eclipse Indigo) and JProfiler 7.2.2. and have enabled the "Profile" actions under "Window->Customize Perspective".
The profile buttons are all disabled, and there is no JProfiler entry in the Preferences dialog.
There are no obvious error messages, but ~/.jprofiler7/config.xml does not contain the integration entries for eclipse 3.7. Including the successful IntelliJ and Eclipse 4.2.2 entries the relevant section looks like this:
<integrations>
<netbeansConfig targetDir="" />
<eclipseConfig targetDir="/Applications/eclipse-4.2.2" />
<ideaConfig targetDir="/Users/richard/Library/Application Support/IntelliJIdea12" />
<jdeveloperConfig targetDir="" />
</integrations>
Is Scala IDE 3.0.0 supported?
Edit
The JProfiler integration installs these files under the Eclipse application folder:
/Applications/eclipse/plugins/com.jprofiler.integrations.eclipse
/Applications/eclipse/plugins/com.jprofiler.integrations.eclipse/META-INF
/Applications/eclipse/plugins/com.jprofiler.integrations.eclipse/META-INF/MANIFEST.MF
/Applications/eclipse/plugins/com.jprofiler.integrations.eclipse/eclipse3-jprofiler.jar
/Applications/eclipse/plugins/com.jprofiler.integrations.eclipse/icons
/Applications/eclipse/plugins/com.jprofiler.integrations.eclipse/icons/bundle_obj.gif
/Applications/eclipse/plugins/com.jprofiler.integrations.eclipse/icons/eclipse_launcher.gif
/Applications/eclipse/plugins/com.jprofiler.integrations.eclipse/icons/java_app.gif
/Applications/eclipse/plugins/com.jprofiler.integrations.eclipse/icons/java_applet.gif
/Applications/eclipse/plugins/com.jprofiler.integrations.eclipse/icons/jprofiler.png
/Applications/eclipse/plugins/com.jprofiler.integrations.eclipse/icons/julaunch.gif
/Applications/eclipse/plugins/com.jprofiler.integrations.eclipse/icons/julaunchpgn.gif
/Applications/eclipse/plugins/com.jprofiler.integrations.eclipse/icons/swt_launcher.gif
/Applications/eclipse/plugins/com.jprofiler.integrations.eclipse/jprofiler.properties
/Applications/eclipse/plugins/com.jprofiler.integrations.eclipse/plugin.properties
/Applications/eclipse/plugins/com.jprofiler.integrations.eclipse/plugin.xml
I also noticed that there is no integration zip file in the JProfiler installation for Eclipse 3.7:
/Applications/jprofiler7/integrations/eclipse33-jprofiler.zip
/Applications/jprofiler7/integrations/eclipse34-jprofiler.zip
/Applications/jprofiler7/integrations/eclipse35-jprofiler.zip
/Applications/jprofiler7/integrations/eclipse36-jprofiler.zip
/Applications/jprofiler7/integrations/eclipse42-jprofiler.zip
Edit 2
None of these log files mention profiler:
$ locate log | grep eclipse | grep "\.log$"
/Applications/eclipse/Eclipse 4.2 Classic.app/Contents/Profile/configuration/1365105032164.log
/Applications/eclipse/Eclipse 4.2 Classic.app/Contents/Profile/configuration/1365105063165.log
/Applications/eclipse/Eclipse 4.2 Classic.app/Contents/Profile/configuration/1365185736428.log
/Applications/eclipse/configuration/org.eclipse.update/install.log
/Users/richard/.eclipse/610389151/configuration/1345715718730.log
/Users/richard/coursera/progfun/workspace/.metadata/.plugins/org.eclipse.ui.views.log
/Users/richard/workspaces/eclipse37/.metadata/.log
/Users/richard/workspaces/eclipse42/.metadata/.log
Edit 3
This is the content of the workspace's .metadata.log file"
!SESSION 2013-04-10 09:48:50.570 -----------------------------------------------
eclipse.buildId=3.0.0-vfinal-20130326-1146-Typesafe
java.version=1.6.0_43
java.vendor=Apple Inc.
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
Framework arguments: -keyring /Users/richard/.eclipse_keyring -showlocation
Command-line arguments: -os macosx -ws cocoa -arch x86_64 -keyring /Users/richard/.eclipse_keyring -showlocation
!ENTRY org.eclipse.core.net 1 0 2013-04-10 09:49:10.083
!MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences
Related
I'm trying to run the mono profiler, however, I'm not getting any profiler output or error messages.
If I run mono --profile=log program.exe the program runs as expected and there are no error messages, yet there is no output.mlpd file.
I have the profiler libs installed and visible:-
# ldconfig -p | grep libmono-profiler
libmono-profiler-log.so.0 (libc6,hard-float) => /usr/lib/libmono-profiler-log.so.0
libmono-profiler-coverage.so.0 (libc6,hard-float) => /usr/lib/libmono-profiler-coverage.so.0
libmono-profiler-aot.so.0 (libc6,hard-float) => /usr/lib/libmono-profiler-aot.so.0
I've tried using mono-sgen and just about every example of profiler options I could find, and nothing changes.
Changing the profiler to something invalid, like mono --profile=meh program.exe has the same result (program runs, no error message, no profiler output)
I've tried on two different machines (Yocto Thud and Ubuntu 18.04.2)
Mono JIT compiler version 5.18.0.268 (tarball Fri Jun 28 03:01:54 UTC 2019)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: normal
Notifications: epoll
Architecture: armel,vfp+hard
Disabled: none
Misc: softdebug
Interpreter: yes
LLVM: supported, not enabled.
Suspend: preemptive
GC: sgen (concurrent by default)
Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: altstack
Notifications: epoll
Architecture: amd64
Disabled: none
Misc: softdebug
Interpreter: yes
LLVM: yes(600)
Suspend: hybrid
GC: sgen (concurrent by default)
This used to work in previous versions of mono in these environments, however, it's non-trivial to roll back and test.
UPDATE
I've managed to resolve this on some platforms (Ubuntu) with the installation of the mono-profiler package.
This package provides the following files:-
/.
/usr
/usr/bin
/usr/bin/emveepee
/usr/bin/mprof-decoder
/usr/bin/mprof-heap-viewer
/usr/lib
/usr/lib/mono-tools
/usr/lib/mono-tools/Mono.Profiler.Widgets.dll
/usr/lib/mono-tools/emveepee.exe
/usr/lib/mono-tools/mprof-decoder-library.dll
/usr/lib/mono-tools/mprof-decoder.exe
/usr/lib/mono-tools/mprof-heap-snapshot-explorer.dll
/usr/lib/mono-tools/mprof-heap-viewer.exe
/usr/share
/usr/share/doc
/usr/share/doc/mono-profiler
/usr/share/doc/mono-profiler/changelog.Debian.gz
/usr/share/doc/mono-profiler/copyright
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/mprof-decoder.1.gz
/usr/share/man/man1/mprof-heap-viewer.1.gz
These appear to be just tools for dealing with profile output. It's not clear which of these files "enables" /usr/bin/mono to actually capture profile data, or why mono is not reporting an error that required files(?) are not present.
The /usr/lib/libmono-profiler-*.so files were already on these platforms (prior to installing mono-profiler)
The remaining platform to resolve is Yocto Thud on ARM. With no package available as with Ubuntu, and no error message, it's difficult to tell what's missing that might be causing this issue.
The solution for Ubuntu was to install the mono-profiler package.
The issue on Yocto Thud was that /usr/lib/libmono-profiler-log.so.0 was present, however, mono looks for /usr/lib/libmono-profiler-log.so (determined using strace) which was not symlinked to /usr/lib/libmono-profiler-log.so.0.
The fact that mono doesn't report this as an error appears to be a bug.
I'm stuck. I am unable to figure out what is causing me to receive "Unresolved requirement: Require-Capability" errors for an SWT bundle (and others, if I dig deeper). The requirements stated for it are win32 os and ws, and arch of x86_64, all of which seem like they should be satisfied by my system. I have included details below, and will update with details that anyone requests.
Background and Problem Details
I'm working on an Eclipse plugin project that hasn't been exported in a long time. It was upgraded from Java 7 to 8, and from Juno to Mars, since the last release. Last week, I went to make a new release, by using the 'Eclipse Product export wizard' in the .product file. Previous releases were fine. Launching the project from within Eclipse works fine (using the product file context menu Run As->Eclipse application to create the Launch configuration). Using the Validate Plug-ins functionality, seen in both the .product and launch config, shows no problems.
The log shows the following:
!SESSION 2016-08-05 09:50:28.847 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_101
java.vendor=Oracle Corporation
BootLoader constants: OS=${target.os}, ARCH=${target.arch}, WS=${target.ws}, NL=en_US
Framework arguments: -enableassertions
Command-line arguments: -os ${target.os} -ws ${target.ws} -arch ${target.arch} -clean -consoleLog -enableassertions -console
!ENTRY org.eclipse.osgi 4 0 2016-08-05 09:50:30.975
!MESSAGE An error occurred while automatically activating bundle org.eclipse.ui.workbench (96).
!STACK 0
org.osgi.framework.BundleException: Error starting module.
at org.eclipse.osgi.container.Module.doStart(Module.java:580)
...
Caused by: java.lang.NoClassDefFoundError: org/eclipse/swt/SWTError
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
at java.lang.Class.getConstructor0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at org.eclipse.osgi.internal.framework.BundleContextImpl.loadBundleActivator(BundleContextImpl.java:755)
at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:706)
at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:941)
at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:318)
at org.eclipse.osgi.container.Module.doStart(Module.java:571)
... 42 more
Caused by: java.lang.ClassNotFoundException: org.eclipse.swt.SWTError cannot be found by org.eclipse.ui.workbench_3.107.0.v20150825-2206
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
at java.lang.ClassLoader.loadClass(Unknown Source)
... 51 more
Root exception:
java.lang.NoClassDefFoundError: org/eclipse/swt/SWTError
...
!ENTRY org.eclipse.osgi 4 0 2016-08-05 09:50:30.988
!MESSAGE An error occurred while automatically activating bundle ca.uvic.chisel.atlantis (2).
!STACK 0
org.osgi.framework.BundleException: Error loading bundle activator.
at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:711)
etc etc...
I have access to the osgi console, and gotten some more information:
osgi> ss org.eclipse.swt
"Framework is launched."
id State Bundle
82 RESOLVED org.eclipse.swt_3.104.1.v20150825-0743
113 INSTALLED org.eclipse.swt.win32.win32.x86_64_3.104.1.v20150825-0743
osgi> diag 113
org.eclipse.swt.win32.win32.x86_64 [113]
Unresolved requirement: Require-Capability: eclipse.platform; filter:="(& (osg
i.ws=win32) (osgi.os=win32) (osgi.arch=x86_64))"
```
Some more details on SWT on my system...the exported application has "/plugins/org.eclipse.swt.win32.win32.x86_64_3.104.1.v20150825-0743.jar", which is the same version specified by the org.eclipse.swt.win32.win32.x86_64 entry in the .product file's "Plug-ins and Fragments" config. (There is also org.eclipse.swt_3.104.1.v20150825-0743.jar and matching org.eclipse.swt). The bundle fragment requirements are as noted in the osgi console results, namely "(& (osgi.ws=win32) (osgi.os=win32) (osgi.arch=x86_64))".
In the previous (functioning) release from my archives, I see it has org.eclipse.swt.win32.win32.x86_64_3.100.1.v4234e.jar. I do not know if the bundle fragment requirements were the same or different back then. I do not have access to the osgi console in this release, because I did not include the necessary libraries for it back then.
Looking at other bundles, I saw some that are not RESOLVED status either.
Development Context
I am developing, exporting, and running the project on Windows 7. My JRE System Library for dev is jre1.8.0_101-b13. This is the same version (same file path) as the JRE installed for running Java applications.
C:\Atlantis Export\Atlantis 0.3.0 TEST 3>java -XshowSettings:properties -version
Property settings:
awt.toolkit = sun.awt.windows.WToolkit
file.encoding = Cp1252
file.encoding.pkg = sun.io
file.separator = \
java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
java.awt.printerjob = sun.awt.windows.WPrinterJob
java.class.path = .
java.class.version = 52.0
java.endorsed.dirs = C:\Program Files\Java\jre1.8.0_101\lib\endorsed
java.ext.dirs = C:\Program Files\Java\jre1.8.0_101\lib\ext
C:\Windows\Sun\Java\lib\ext
java.home = C:\Program Files\Java\jre1.8.0_101
java.io.tmpdir = C:\Users\eric\AppData\Local\Temp\
java.library.path = C:\ProgramData\Oracle\Java\javapath
C:\Windows\Sun\Java\bin
C:\Windows\system32
C:\Windows
C:\ProgramData\Oracle\Java\javapath
C:\Windows\system32
C:\Windows
C:\Windows\System32\Wbem
C:\Windows\System32\WindowsPowerShell\v1.0\
C:\Program Files (x86)\pgmodeler
C:\WinPython-64bit-3.4.3.5\python-3.4.3.amd64
%USERPROFILE%\.dnx\bin
C:\Program Files\Microsoft DNX\Dnvm\
C:\Program Files\nodejs\
C:\Program Files (x86)\Skype\Phone\
C:\Windows\System32\WindowsPowerShell\v1.0\
C:\Program Files\010 Editor
C:\Users\eric\AppData\Roaming\npm
.
java.runtime.name = Java(TM) SE Runtime Environment
java.runtime.version = 1.8.0_101-b13
java.specification.name = Java Platform API Specification
java.specification.vendor = Oracle Corporation
java.specification.version = 1.8
java.vendor = Oracle Corporation
java.vendor.url = http://java.oracle.com/
java.vendor.url.bug = http://bugreport.sun.com/bugreport/
java.version = 1.8.0_101
java.vm.info = mixed mode
java.vm.name = Java HotSpot(TM) 64-Bit Server VM
java.vm.specification.name = Java Virtual Machine Specification
java.vm.specification.vendor = Oracle Corporation
java.vm.specification.version = 1.8
java.vm.vendor = Oracle Corporation
java.vm.version = 25.101-b13
line.separator = \r \n
os.arch = amd64
os.name = Windows 7
os.version = 6.1
path.separator = ;
sun.arch.data.model = 64
sun.boot.class.path = C:\Program Files\Java\jre1.8.0_101\lib\resources.jar
C:\Program Files\Java\jre1.8.0_101\lib\rt.jar
C:\Program Files\Java\jre1.8.0_101\lib\sunrsasign.jar
C:\Program Files\Java\jre1.8.0_101\lib\jsse.jar
C:\Program Files\Java\jre1.8.0_101\lib\jce.jar
C:\Program Files\Java\jre1.8.0_101\lib\charsets.jar
C:\Program Files\Java\jre1.8.0_101\lib\jfr.jar
C:\Program Files\Java\jre1.8.0_101\classes
sun.boot.library.path = C:\Program Files\Java\jre1.8.0_101\bin
sun.cpu.endian = little
sun.cpu.isalist = amd64
sun.desktop = windows
sun.io.unicode.encoding = UnicodeLittle
sun.java.launcher = SUN_STANDARD
sun.jnu.encoding = Cp1252
sun.management.compiler = HotSpot 64-Bit Tiered Compilers
sun.os.patch.level = Service Pack 1
sun.stderr.encoding = cp437
sun.stdout.encoding = cp437
user.country = US
user.dir = C:\Atlantis Export\Atlantis 0.3.0 TEST 3
user.home = C:\Users\eric
user.language = en
user.name = eric
user.script =
user.timezone =
user.variant =
java version "1.8.0_101"
Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)
I have tried upgrading again from Mars, to Neon. That didn't resolve anything. Downgrading to Juno to fix something like this smells like the wrong solution.
So...while preparing my answer, I found the solution. I know that if I had someone to bounce this off of before, it might have occurred to me then.
I noticed that the ${target.ws} and ${target.os} occur in the launch config. I am not sure how these were added; perhaps the product file generated these arguments, perhaps I added them when trying to fix another bug many moons ago. In any case, I was googling to see how to inspect these values, and decided to simply remove them and test launch and export without them. both worked fine. I don't need them there, I am not sure if they were even containing values.
To reiterate, my solution was to remove the "-os ${target.os} -ws ${target.ws} -arch ${target.arch}" arguments in the .product file (as well as the launch config derived from it).
I may have added them on the advice of somewhere like this (but I don't know why): Eclipse Validation error - Platform filter did not match:(&(osgi.ws=win32)(osgi.os=win32)(osgi.arch=x86)) . Looking at blame, I see that the arguments were added when I first changed the project from using manually defined launch configurations, to using .product based launch configuration; there were inconsistencies and machine dependent strings when the launch was manually defined. I do not know if they were automatically added, or if I thought I needed them.
Problem:
When I want to run a project from within Anypoint Studio I am encountering a problem. This project was originally setup in Eclipse Juno with the Mule IDE plugin.
From within Eclipse Juno I was able to run the mule-config.xml on a local installation Mule Server.
Now I have upgraded to the latest Anypoint Studio (5.3.1; I have both the standalone and the plug-in with Eclipse Mars). I was successful in importing the project in the Anypoint environment and building it with Maven.
In both (standalone and plug-in) I am not able to run the project. When I try running through ‘Run Configurations’ I get an error where it complains that a resource is not available. But I don’t understand this error, because the resource /XmlProxyValidationFilter it is complaining about is a custom filter within my project in src/main/java which is on my build path (all included, none excluded).
Definition of the custom filter:
<custom-filter name="xmlValidatieRequestFilter" class="nl.xxx.icc.mule.XmlProxyValidationFilter">
<spring:property name="xsdRepositoryBean" ref="iccXsdRepositoryBean" />
</custom-filter>
Calling the custom filter from a flow:
<flow name="xmlproxy.validator">
<!-- some other stuff -->
<filter ref="xmlValidatieRequestFilter" />
</flow>
This flow validates an XML-message that is passing through against its corresponding XSD which is in the xsdRepositoryBean.
What I have tried:
In Run-configurations I have chosen my project in Mule domains/projects (expecting it to be added to the classpath) and Mule Server 3.4.0 CE as Target Server Runtime (same runtime as with successful Maven-build).
In Run-configurations tried to add the missing resource to User Entries on the Classpath tab.
I have found a suggestion to try in this question, but I am not sure how to do this since I use Maven integrated in Eclipse. Therefor I have tried converting my project to a Maven project (I think this is a function specific to the Anypoint plug-in) but this does not solve the problem.
Tried to find similar problems for possible solutions, but only the above came close.
Question:
Any ideas why I am getting an error about a missing resource when I try to run the flow, while this resource is in my project-folder and I can build the project without problems with Maven?
Error-log:
eclipse.buildId=4.5.1.M20150904-0015
java.version=1.8.0_31
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product
org.mule.tooling.core
Error
Wed Oct 21 08:00:33 CEST 2015
Unable to package application ZIP file
java.lang.reflect.InvocationTargetException
at org.mule.tooling.core.packageManager.ExportPackageManager.export(ExportPackageManager.java:87)
at org.mule.tooling.runtime.launch.DefaultDeploymentStrategy.packageZipFile(DefaultDeploymentStrategy.java:55)
at org.mule.tooling.runtime.launch.DefaultDeploymentStrategy.deployToEmbeddedInstance(DefaultDeploymentStrategy.java:26)
at org.mule.tooling.runtime.launch.MuleRuntimeLaunchDelegate.deployProjects(MuleRuntimeLaunchDelegate.java:486)
at org.mule.tooling.runtime.launch.MuleRuntimeLaunchDelegate.performLegacyDeployment(MuleRuntimeLaunchDelegate.java:344)
at org.mule.tooling.runtime.launch.MuleRuntimeLaunchDelegate.launch(MuleRuntimeLaunchDelegate.java:238)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.eclipse.core.internal.resources.ResourceException: Resource '/XmlProxyValidationFilter' does not exist.
at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:334)
at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:208)
at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:140)
at org.eclipse.core.internal.resources.Project.hasNature(Project.java:521)
at org.mule.tooling.core.deployer.MuleApplicationDeployment.copyArtifacts(MuleApplicationDeployment.java:621)
at org.mule.tooling.core.deployer.MuleApplicationDeployment.copyReferencedProjectsArtifactsRecursively(MuleApplicationDeployment.java:615)
at org.mule.tooling.core.deployer.MuleApplicationDeployment.copyReferencedProjectsArtifacts(MuleApplicationDeployment.java:608)
at org.mule.tooling.core.packageManager.MuleApplicationExportDelegate.export(MuleApplicationExportDelegate.java:41)
at org.mule.tooling.core.packageManager.ExportPackageManager.doExport(ExportPackageManager.java:93)
at org.mule.tooling.core.packageManager.ExportPackageManager.export(ExportPackageManager.java:85)
... 10 more
Root exception:
org.eclipse.core.internal.resources.ResourceException: Resource '/XmlProxyValidationFilter' does not exist.
at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:334)
at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:208)
at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:140)
at org.eclipse.core.internal.resources.Project.hasNature(Project.java:521)
at org.mule.tooling.core.deployer.MuleApplicationDeployment.copyArtifacts(MuleApplicationDeployment.java:621)
at org.mule.tooling.core.deployer.MuleApplicationDeployment.copyReferencedProjectsArtifactsRecursively(MuleApplicationDeployment.java:615)
at org.mule.tooling.core.deployer.MuleApplicationDeployment.copyReferencedProjectsArtifacts(MuleApplicationDeployment.java:608)
at org.mule.tooling.core.packageManager.MuleApplicationExportDelegate.export(MuleApplicationExportDelegate.java:41)
at org.mule.tooling.core.packageManager.ExportPackageManager.doExport(ExportPackageManager.java:93)
at org.mule.tooling.core.packageManager.ExportPackageManager.export(ExportPackageManager.java:85)
at org.mule.tooling.runtime.launch.DefaultDeploymentStrategy.packageZipFile(DefaultDeploymentStrategy.java:55)
at org.mule.tooling.runtime.launch.DefaultDeploymentStrategy.deployToEmbeddedInstance(DefaultDeploymentStrategy.java:26)
at org.mule.tooling.runtime.launch.MuleRuntimeLaunchDelegate.deployProjects(MuleRuntimeLaunchDelegate.java:486)
at org.mule.tooling.runtime.launch.MuleRuntimeLaunchDelegate.performLegacyDeployment(MuleRuntimeLaunchDelegate.java:344)
at org.mule.tooling.runtime.launch.MuleRuntimeLaunchDelegate.launch(MuleRuntimeLaunchDelegate.java:238)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
#Jeroen Akershoek ... I have faced same issue. So please put your resource in src/main/resource directory and use class path loader in your filter jar.
I just installed Aptana Studio 3.4.2 on a fresh install of Linux Mint 16 with Oracle java. The program closes unexpectedly. So far I've only used it with the Python perspective active. It seems to happen more often when I'm editing an html file. I used it for 3 hours one day before it crashed; other times only 10 minutes.
The log file has a recurring error that may be related but I can't find any info on it:
!MESSAGE Invalid preference page path: XML Syntax.
Does anyone know what is causing this?
Java Version:
java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
Aptana Diagnostic:
Host OS: Linux
OS Version: 3.11.0-12-generic
OS Arch: x86_64
JRE Version: 1.7.0_45
JRE Vendor: Oracle Corporation
JRE Home: /opt/java/jdk1.7.0_45/jre
Aptana Studio 3 Version: 3.4.2.201308081805
Install Directory: file:/opt/Aptana_Studio_3/
Workspace Directory: file:/home/jeff/workspace/
VM Arguments: -Xms40m
-Xmx512m
-Declipse.p2.unsignedPolicy=allow
-Declipse.log.size.max=10000
-Declipse.log.backup.max=5
-Djava.awt.headless=true
-XX:MaxPermSize=256m
-jar
/opt/Aptana_Studio_3//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
Language: en_US
Node.JS Version: Not installed
NPM Path: Not installed
ENV:
MDMSESSION=default
GNOME_KEYRING_CONTROL=/run/user/1000/keyring-ka4Jsn
SHLVL=1
SSH_AGENT_PID=1662
TEXTDOMAINDIR=/usr/share/locale/
XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt
GDM_XSERVER_LOCATION=local
SESSION_MANAGER=local/jeff-main:#/tmp/.ICE-unix/1585,unix/jeff-main:/tmp/.ICE-unix/1585
GNOME_DESKTOP_SESSION_ID=this-is-deprecated
CLUTTER_DISABLE_XINPUT=1
GDMSESSION=default
XDG_SESSION_COOKIE=812a644561ed637b3aa6135652bf871c-1389232561.233987-1413464634
XDG_DATA_DIRS=/usr/share/default:/usr/share/gnome:/usr/local/share/:/usr/share/:/usr/share/mdm/
MANDATORY_PATH=/usr/share/gconf/default.mandatory.path
PWD=/home/jeff
GIO_LAUNCHED_DESKTOP_FILE=/home/jeff/Desktop/AptanaStudio3.desktop
MDM_XSERVER_LOCATION=local
LOGNAME=jeff
GPG_AGENT_INFO=/run/user/1000/keyring-ka4Jsn/gpg:0:1
GIO_LAUNCHED_DESKTOP_FILE_PID=3387
SSH_AUTH_SOCK=/run/user/1000/keyring-ka4Jsn/ssh
NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat
TEXTDOMAIN=im-config
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-9GHbJcIE3A,guid=4d478335c530a3bf45ec18fb52ce01b1
SHELL=/bin/bash
GNOME_KEYRING_PID=1509
XDG_CURRENT_DESKTOP=GNOME
XDG_CONFIG_DIRS=/etc/xdg/xdg-default:/etc/xdg
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
DESKTOP_SESSION=default
APTANA_VERSION=3.4.2.1368863613
DISPLAY=:0.0
USER=jeff
HOME=/home/jeff
XAUTHORITY=/home/jeff/.Xauthority
XDG_SEAT=seat0
WINDOWPATH=8
XDG_SESSION_ID=c1
DEFAULTS_PATH=/usr/share/gconf/default.default.path
MDM_LANG=en_US.UTF-8
USERNAME=jeff
XDG_VTNR=8
XDG_RUNTIME_DIR=/run/user/1000
LANG=en_US.UTF-8
I Had the same problem with PHP. I found out that the program terminate when I hover my mouse over an object. So far so good after disabling the hover.
To disable: Window -> Preferences -> Content Assist -> Show information on hover: off
Try add
-Dorg.eclipse.swt.browser.DefaultType=mozilla
in AptanaStudio3.ini
Eclipse continue crashing
open AptanaStudio3.ini and append this line to end of file:
-Dorg.eclipse.swt.browser.DefaultType=mozilla
Try install Xterm and open again.
I have successfully installed sonar plug-in for eclipse, however when I try to 'Run Local Analysis' for sonar, eclipse gives an error saying:
An internal error occurred during: "Sonar Analysis".
Unable to create markers
and console for Sonar has following info printed:
Usage: javaw [-options] class [args...]
(to execute a class)
or javaw [-jar] [-options] jarfile [args...]
(to execute a jar file)
where options include:
-cp -classpath
set search path for application classes and resources
-D=
set a system property
-verbose[:class|gc|jni]
enable verbose output
-version print product version
-version:
require the specified version to run
-showversion print product version and continue
-jre-restrict-search | -no-jre-restrict-search
include/exclude user private JREs in the version search
-agentlib:[=]
load native agent library , e.g. -agentlib:hprof
see also, -agentlib:jdwp=help and -agentlib:hprof=help
-agentpath:[=]
load native agent library by full pathname
-javaagent:[=]
load Java programming language agent, see java.lang.instrument
-? -help print this help message
-X print help on non-standard options
-splash: show splash screen with specified image
-ea[:...|:]
-enableassertions[:...|:]
enable assertions
-da[:...|:]
-disableassertions[:...|:]
disable assertions
-esa | -enablesystemassertions
enable system assertions
-dsa | -disablesystemassertions
disable system assertions
Plz help with how to proceed for Local analysis in eclipse.
[Update: Version Details]
Eclipse: Indigo (3.7.1)
Sonar Plug-in: 3.0.0
Sonar(Server): 3.4.1
Sonar Web Service Client: 3.4.0
Java: 1.4.1 ('Java EE IDE' property in Eclipse Features)
Local Java Installation: 1.6