ALFA not recognising Attributes term - eclipse

I downloaded the ALFA plugin for eclipse and followed the instructions in the alfa-install-plugin.pdf that was included in the zip archive. It seemed to install OK.
However, when I pasted the example snippet of ALFA into an example file (test.alfa), as per the instructions, it failed to "compile" successfully. The Attributes.subjectId == “alice” term was underlined in red. This occurs even though the provided standard-attributes.alfa and system.alfa files are both present in the same src directory as test.alfa.
I think the plugin should have found the definition of Attributes.subjectId in standard-attributes.alfa but clearly this did not happen.
Details of my setup:
ubuntu 15.10 64-bit
Eclipse version: eclipse-dsl-kepler-SR2 (64-bit)
ALFA-1.0-update-site.zip (current)
Oracle java version: 1.8.0_66
Note that alfa was tested on eclipse Kepler (64-bit) on Ubuntu 12.10, which is now at end of life.
I tried several possibilities, but all had the same problem: using the Java developer (not the DSL-specific) version, using different alfa snippets, using a Java eclipse project but not a basic eclipse project, renaming standard-attributes.alfa to Attributes.alfa (to match its namespace), ...
I wonder whether other users have encountered this problem, and if so, how they fixed it!
Thank you.

Unfortunately ALFA Eclipse plugin v 1.0 does not work with the Kepler release of Eclipse. Things changed a lot internally in the plugin architecture of Kepler and hence you will need to use v 1.0.2 of the plugin.

Related

Error configuring pipeline debugger in Eclipse

enter image description hereI have been trying really hard to configure a pipeline debugger in eclipse. After using my digital server account in server configuration when i select my site and click 'Debug' button it gives me an error
Could not initialize class com.thoughtworks.xstream.converters.collections.TreeMapConverter
I couldn't find much help online. I even tried changing the JRE version to an older version 14.0.2 but it doesn't seem to help.
[![Image attached of error][2]][2]
enter image description here
That library seems to be a core component of the Pipeline editor. I would suggest that you ensure that your Eclipse version is compatible with the plugin if you haven't done so already.
Currently, according to the documentation it only supports:
Mars - Eclipse 4.5
Neon - Eclipse 4.6
Furthermore, you must install the correct version of the plugin for your version of Eclipse. (Though in the past I've found that older plugin versions may sometimes work in newer Eclipse builds.)
This error relates to discounted class from JRE.
So my recipe for solving the issue:
used OpenJDK v11
installed latest eclipce version
SFCC plugin v4.6
Some found issues:
with new eclipce version brakepoints are not set from JS editor only via ScriptEditor
Thank you,
Aleksandr
I had issues with running debugger, but after I installed eclipse version 2020-12 and installed UX studio plugin it started to work. maybe new versions are not compatible with plugin

Haskell Plugin on Eclipse is not visible

I'm learning Haskell and I need to install Haskell plugin on Eclipse.
I have first installed Eclipse Kepler and then installed the Haskell plugin from http://eclipsefp.sf.net/updates. The plugin installation went ok but the Haskell perspective is not visible at Window > Open Perspective > Other. It's visible at Help > Installation Details, though.
I've come across similar problem at this post:
Plugins installed on Eclipse not visible
I've applied all suggestions: I've started Eclipse as root, I've changed the installation path from /Applications to ~/, I've given write access to plugins folder, no luck.
I've erased Eclipse Kepler and installed Luna, still no luck.
I've updated the JRE to Java SE 7 [1.7.0_71] and edited the Java JRE section at Eclipse preferences, still no luck.
Any help is appreciated, thanks.
My OS X Lion 10.7.4 64bit
I've solved it. The problem seems to stem from multiple java versions installed on Lion.
I've come across this post salesforce Eclipse plugin and there I noticed that multiple Java versions on one system might cause trouble on plugins and in case of saleforce, that was causing trouble on Eclipse plugin or perspective.
Then I've taken a second look at Haskell's Eclipse plugin page Haskell Eclipse plugin and there I saw the java version 7 was emphasized.
So I reckoned that some java version mismatch might be causing Eclipse not to display the Haskell plugin. Btw, my installing the latest (1.7.0_72) version of java didn't change any possibel version mismatch on my Mac OS X, because though I successfully installed 1.7.0_72 version (using the file jdk-7u72-macosx-x64.dmg which I downloaded from oracle.com), the $ javac -version still returned 1.6.0_29.
Then I've found this post multiple java installations on mac os x and added the following line to eclipse.ini
-vm
/Library/Java/JavaVirtualMachines/jdk1.7.0_72.jdk/Contents/Home/bin/java
before -vmargs, and that finally solved the problem. Now the Haskell plugin and perspective comes up. That's fine.

spring development - with or without eclipse + checking eclipse version

Several tutorials mention that you can download spring in a tarball
and install it on your computer but when I go to the springsource
site all I can see is that you can download Spring Tool Suite
which is an eclipse plugin. So my questions are:
What if I wanted to work from the command line or an IDE other than eclipse?
The packages are available for Juno 3.8.2 or Juno 3.4.2, but how can I find
out my eclipse version? I've downloaded the most frequently downloaded version
of eclipse which is the one for Java EE developers but when I click on the Help
-> About entry I get:
Version: Juno Service Release 2
Build id: 20130225-0426
which does not match the eclipse versions on the springsource site 3.8.2 or 3.4.2,
so how do I know which plugin I need?
Thanks.
You can find out your Eclipse version by going to Help -> About Eclipse...
In the dialog that pops up, you will see something like:
Version 4.2.2
or
Version 3.8.2
If you downloaded the most commonly downloaded version, then you most likely have 4.2.2. The "Juno" release actually has distributions built for both 3.8.x and 4.2.x (a little complicated and confusing, I know). So, you should be able to install the Juno version of STS and be fine no matter what which version of Juno Eclipse you have.
EDIT
Your question is not very clear. I thought you were asking about how to install STS, but maybe you are asking about whether or not Eclipse is necessary at all. The answer is that of course, Eclipse is not necessary for Spring development, but it really is the easiest way to develop your spring apps (disclaimer, I am on the STS dev team).
There is no single way to just "downlaod the SpringFramework" because the framework is really just a very large set of jar files and their dependencies. Any single project typically only requires a subset of them as well as requiring other third party dependencies. For this reason, most people prefer working with a build tool like gradle or maven.
Probably the easiest way to get started w/o STS is to clone one of the sample projects from github. A list of the templates are available here: http://dist.springsource.com/release/STS/help/descriptors-3.0.xml which is obvioulsy meant to be consumed from inside of STS. But, you can use the file to grab links to the various github projects.
The Springsource Tool Suite (STS) is not required for developing with Spring. If the question is how you would install the STS, that's actually very easy. In Eclipse 3.7 (Indigo) or 3.8, 4.2 (Juno), click on the Help menu and select Eclipse Marketplace. If its not in the inital screen, use the find box type spring and click go which should bring up the the STS with the version of eclipse it is for in the title. Click install and the correct version and its dependencies will be installed for you. Try to use the eclipse marketplace for all the plugins you install, if possible. It makes things much simpler

Failure creating clojure project in Netbeans

I decided to take a look at Clojure and thought the best and easiest method for me would be to use Netbeans with the Enclojure plugin as I didn't want to have to learn Emacs at the same time. I installed Netbeans 6.9.1 together with the latest JDK using the bundled install (on Windows 7). All went smoothly. I then followed the instructions at http://www.enclojure.org/gettingstarted for installing the enclojure plugin.
When creating a new Clojure application I get the following and see no project files :
java.io.IOException: Could not connect to URL nbresloc:/org/enclojure/ide/templates/project/ClojureProjectTemplate-1.1-distribution.zip. No such resource was found.
Maven is working using mvn --version
I have installed on both Windows 7 and Ubuntu 10.04 (same result).
I have looked on the Enclojure forum and there is a recent open thread for this issue, but it is not solved by anybody presently.
I have Java SE enabled in Netbeans
I have tried enabling the different platform versions of Clojure, 1.0.0, 1.1.0, etc..
The REPL seems to be working happily in Netbeans : (printf "hello") hellonill
I did try ClojureBox on Windows 7, but again that's Emacs, but emacs failed to start the server and hung there and became totally unresponsive.
I come from a .Net background (not Java) so my knowledge of the Java environment is somewhat lacking. My reason for looking at Clojure and not Java.
I am new to Netbeans
If you're interested in a working Maven pom, here is one I've used with Enclojure successfully:
http://puredanger.com/techfiles/100624/pom.xml
There are some project settings you'll need to change and a few dependencies to remove but it might be a good start. In general, I usually create the pom first and then just import the project into NetBeans rather than using the NetBeans options to create projects.
By the way, the REPL work in Enclojure has been split and is coming soon to the Eclipse plugin Counterclockwise.
I had written a small post on it on my blog.
Anyways here is the procedure:
On searching realized that this is a common problem for installing it on > Netbeans 7.. But with some manual tweeks managed to install it. Here are the instructions to install on Netbeans 7. plus:
Install Netbeans 7. You need only the Java SE version.
First Run of Netbeans after installation. Activate feature Java SE
Activate features is on the Start page or from Tools,->Plugins>Installed, click ‘Activate next to the Java SE support
Install Maven: It is HIGHLY recommended that you install maven: http://maven.apache.org/download.html
Go to the Netbeans->Preferences, click on the Miscellaneous tab and make sure the External Maven Home path is pointed to your maven install
Download the EnClojure 1.5 version from here. If you want to manually build, you can do that by following the instructions from here.
After downloading the file, In Netbeans: Goto:- Tools ->Plugins->Downloaded->Add Plugins->Downloaded
Then browse to the downloaded file. Later install by clicking at the “install : button.
Restart and you are on the go.
Visit here to build and run hello world project.Basically building the EnClojure 1.5 manually is the tough job. I hope above was useful.

Eclipse randomly exits after installation of Blackberry plugin/SDK

Since adding the Blackberry Java classes from their website into eclipse, I've had it where eclipse will randomly close, with no discernible pattern, rhyme, error or reason. Here is the environment/software packages that I am using:
Windows XP SP2
Eclipse v3.5.1
Blackberry Java Plugin v1.1.1.200911111641-15
Blackberry Java SDK 4.5.0.21
I've tried the usual steps of complete uninstall and reinstallation of Eclipse and the accompanying plugins on multiple systems with the same configuration, including one that had a fresh install of Windows XP SP2. Upgrading to Eclipse 3.6 didn't work (the plugin wont' install as it's the wrong version), nor the downgrade to 3.4 for the same reason. I also increased the heap size to 512 (system has two gigs of memory) as some research into Eclipse doing this type of thing with Groovy was resolved that way, but again, no dice. Eclipse works great when the blackberry plugins are not installed, and no entries of errors or issues in the event log are helping to show what the issue with these plug-ins might be.
So if anyone has ran into this issue, and even better, has a solution, I'd love to hear about it. Thanks in advance.
EDIT: An additional to my issue, autoComplete with the Blackberry SDK seems to make this extremely unstable, like almost a guaranteed crash. Is this fixable at all?
For anyone that loads this question up trying to find a solution, I've never found a fix. It seems to be a bug with this version of the IDE. If there is a fix, please post.
Did you try to downgrade Eclipse to 3.4 (Ganymede)? I experienced similar issues when I tried upgrading Eclipse to something greater than 3.4.2.
I think the problem is with the plugin, not the IDE. Eclipse has always been stable for me until I installed the BB plugin. Since then it crashes all the time. Since I've installed the release (non-beta) version of the plugin that was recently released I can't even get my project to build.
This could be a manifestation of this bug in Eclipse. Check your C:\eclipse directory for files like hs_err_pidxxxx.log. The file goes on to explain this error:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x753ba053, pid=3144, tid=5820
#
# JRE version: 6.0_20-b02
# Java VM: Java HotSpot(TM) Client VM (16.3-b01 mixed mode, sharing windows-x86 )
# Problematic frame:
# C [USP10.dll+0x1a053]
I've been experiencing this as well. It's completely debilitating. It causes Eclipse to just up and crash out of nowhere (and programming in a language as verbose as Java without Content-Assist is insane).
The bug has been fixed in Eclipse 3.6M7, but unfortunately I can't get the JDE Plug-in to install in the latest release candidate.
This is a known issue with Eclipse 3.5.X and has been fixed for 3.6.0
Bug Ticket link on Eclipse Bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=283503
Looks like we are stuck with this until the next update to the BB Eclipse plugin.