I used top be able to integrate a StarTeam plugin with MyEclipse using this update site URL: http://altd.borland.com/update/eclipse3.6/site.xml
But using newer versions of MyEclipse, this plugin no longer can install, I get this error:
Cannot complete the install because one or more required items could not be found.
Software being installed: StarTeam 2009 R2 Eclipse 3.6 Client 11.0.0.97v20111028-1643 (com.borland.starteam_3.6.feature.group 11.0.0.97v20111028-1643)
Missing requirement: StarTeam 2009 R2 Eclipse 3.6 Client 11.0.0.97v20111028-1643 (com.borland.starteam_3.6.feature.group 11.0.0.97v20111028-1643) requires 'org.eclipse.platform.feature.group [3.6.0,4.0.0)' but it could not be found
Does anyone have the same problem and found a workaround? I am willing to consider any option... so far my best option seems to be to downgrade Eclipse to an older version where the plugin still works. But I want to see if there's a better alternative out there
Found out the answer by a support rep from the group responsible for the plugin.
Firstly, they no longer offer the plugin via that site URL. You download their plugins from their ftp: ftp://ftp.microfocus.com/download/
and Secondly, they do not yet have a plugin that supports the latest verison of Eclipse, they are still working on it...
I would strongly discourage trying to use StarTeam with Eclipse. Ever since StarTeam 5.3, Borland has been trying to play catch-up with Eclipse. In my experience their clients have never worked well with Eclipse even when they did work. Moves in particular were handled very poorly, and resulted in duplicate files in StarTeam. Even worse was trying to use IBM WebSphere/RAD with Eclipse and StarTeam/Eclipse plugin, because IBM and Borland always required different versions of Eclipse and were ultimately incompatible. For a short time there was a time where RAD 6 and StarTeam 2009 (I believe) were both working on the same Eclipse, but the Synchronization was problematic from Eclipse to StarTeam as mentioned. There was a time when Borland had planned on replatforming the StarTeam Client on top of Eclipse, but not sure what ever happened to that plan.
Related
I am attempting to begin building an automation sequence for a client however they are only able to use Blueprism version 6.2 right now. Does anyone know of installing, coding, scheduling, or running issues with this version? Can you also link where the issue has been discussed/resolved?
Ensure they are using the latest patch level for 6.2 (which is 6.2.2) in order to ensure they do not experience issues around scheduling. Details will be available in the Release Notes for 6.2.2 on the Blue Prism portal.
I am a huge fan of Jetbrains "AppCode". But due to the variety of projects I have some depending on older XCode versions and others can be the latest and greatest. It's great that we can have multiple XCode installations side-by-side. But is this also possible with AppCode? I remember that back a couple of years, the EAP version could be installed side-by-side with the stable release. This would also already help, but I cant even find a separate EAP download anymore.
Anybody any tips for me?
You can use JetBrains Toolbox to install as many product versions as you like side by side with the automatic update (optional) and rollback support.
In Toolbox you can set certain product versions to stick to the specific installed version and do not offer the updates.
Major IDE versions do not share the configuration and can be even run at the same time. Minor version can be also configured to use different folders for config/plugins/caches if needed.
As mentioned in the Bluemix guide, I tried installing the Bluemix tool plugin on eclipse(Mars) with Java 7 installed on my Ubuntu machine.
1). Through the eclipse market place where Bluemix tool is present and the same fails with the following error when installation is nearly over:
Cannot complete the install because one or more required items could not be found.
Software currently installed: IBM Bluemix Tools 1.0.5.v20150801_1001
(com.ibm.cftools.feature.feature.group 1.0.5.v20150801_1001)
Missing requirement: Bluemix Tools 1.0.6.v20150801_1001
(com.ibm.cftools.branding 1.0.6.v20150801_1001)
requires 'bundle org.eclipse.jst.server.core 0.0.0' but it could not be found
Cannot satisfy dependency:
From: Cloud Tools Branding UI Plugin 1.0.2.v20150801_1001
(com.ibm.cftools.branding.ui 1.0.2.v20150801_1001)
To: package com.ibm.cftools.branding.internal 0.0.0
Cannot satisfy dependency:
From: IBM Bluemix Tools 1.0.5.v20150801_1001
(com.ibm.cftools.feature.feature.group 1.0.5.v20150801_1001)
To: com.ibm.cftools.branding.ui [1.0.2.v20150801_1001]
I checked this exception and found a description about it in the eclipse web page. However, the remedy is missing for this particular problem.
2). Besides I tried to install the same via WASdev, but I ended up with the following error:
No repository found at http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/updates/cloud/V1.0
However, the same page is accessible from any web browser. Also, I have checked my proxies and they are fine.
Please let me know if there is any solution or what I am doing wrong here. Thanks.
Are you using Eclipse for Java EE Developers edition? It is required that edition to satisfy some bundle requirements.
A few pointers:
An Eclipse update site needs to have a site.xml - check if the location actually has one.
Your install error points to a missing jst component. That's Eclipse "core" stuff. So it seems your access to the original Eclipse update site needs to be checked
Check your Eclipse install, do you have rights to all the files?
Hope this helps
As mentioned, the error message you are receiving (not able to resolve "org.eclipse.jst.server.core") is due to the installation process not being able to locate this package. This package is provided by the same Eclipse marketplace entry or DHE update site from which you are installing (and so you should not see this error when installing from our marketplace or update site). I have confirmed that the provided update site URL is correct and installation works as expected on my own Ubuntu installation.
A few other suggestions, or for users that see the same problem:
This may be a hiccup with DHE or with your connection to the update site. I would suggest trying the installation again.
Try a fresh install of Eclipse to ensure that no other dependencies are interfering with your installation. The Java EE package 'Eclipse IDE for Java EE Developers' available for download from Eclipse.org will include the required package that is mentioned in your error message (though as previously mentioned, this should not be necessary as this package is bundled with our update site/marketplace entry).
Ensure you are NOT using the default version of Eclipse available from the Eclipse Software Center, which is often several versions behind.
If this doesn't help, feel free to provide more information about your current installation (version details, method of installation, any other details) to help us reproduce.
Whenever there is a new update of the worklight studio available in the eclipse market place I install it to get the latest fixes. When I restart eclipse after installing an update, Worklight triggers some kind of process to update my project to the new version. During this process worklight does some black voodoo and updates some files.
I suppose that once I commit these files, the entire team should download and install the new update from the eclipse market place? Because it can't be a good idea to work with an old version of Worklight Studio on a project that was already updated to work with a newer version.
Are there any best practices on this topic?
Is it a good idea to update your worklight studio on a regular base? I'm not talking about minor or major versions, just a new patch which is available in the eclipse marketplace. Take for example an update from platformVersion="6.2.0.00.20140701-1500" to platformVersion="6.2.0.00.20140724-2139"
If you choose to stick with one specific version, how do you distribute this to new members in your development team? Should you keep a copy somewhere? And what happends then if you need a fix?
I suppose that once I commit these files, the entire team should
download and install the new update from the eclipse market place?
Because it can't be a good idea to work with an old version of
Worklight Studio on a project that was already updated to work with a
newer version.
If you do not work alone, and you upgrade your Worklight Studio version (which then does "black voodoo" and updates the project's files) and you then deliver your changes to your SCM, then yes - your team members must upgrade their Worklight Studio plug-in as well.
Are there any best practices on this topic?
As a Worklight development team member, my advise is: if we publish a fix to Eclipse Marketplace / IBM Fix Central - yes, install it.
That said, you can also review the list of fixed bugs ("APARs") in IBM Fix Central and decide whether you'd like to upgrade your installation.
Before doing so, you can opt to first install this fix in a new Eclipse and workspace and make sure your project is not getting broken. If you feel all is OK, upgrade your main development environment and instruct your team members to do the same, then, migrate the project using the new Worklight Studio version and deliver your changes to the SCM.
If you choose to stick with one specific version, how do you
distribute this to new members in your development team? Should you
keep a copy somewhere? And what happends then if you need a fix?
Branch your code in the SCM based on the version? But why create headache...
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I've been on a frustrating quest to find an IDE which provides reasonable support for Grails 1.1 development. My minimum requirements are:
Supports running tests within the IDE
Supports debugging within the IDE while running either the tests or the app itself
Provides code-completion, including dynamic finders added to domain classes
Here's a rundown of my experience so far
Eclipse 3.4.2 (Ganymede)
Using the latest plugins available from the update site, Eclipse's support for Groovy/Grails is truly pathetic. It provides little more than code completion and spurious errors
NetBeans 6.7 Beta
As soon as I imported the project, NetBeans began scanning it. The Navigator view was waiting for the scanning to finish before showing it's contents. About 20 minutes later, both the Navigator view and I were still waiting. Also, support for code completion on dynamic finders is poor, and for some reason it copied all the plugins into $PROJECT_ROOT/web-app/plugins.
IntelliJ 8.1.2
Although the general consensus is that IntelliJ is the best IDE for Groovy/Grails, it does not work well with Grails 1.1.X. The root cause of the problem appears to be the change in the location of the plugins folder. IntelliJ is unable to build the app because it can't find classes I'm importing from plugins, even though those plugins are listed in application.properties
So my question (finally) is whether anyone has found an IDE (not TextMate or Vim) that works with Grails 1.1.X when the plugin folder is in it's default location, i.e. under $HOME/.grails/1.1.X/plugins?
If so, I'd be really grateful for information about:
Which IDE to use (including version number)
Which plugins (if any) need to be installed
How to import an existing project into the IDE
How to run the app, the tests, and debug from within the IDE (if it's not obvious)
Thanks,
Don
NetBeans 6.7 now with Grail 1.1 support
I'm unclear on which version of IntelliJ IDEA the author of that blog post tested, tha didn't work with Grails 1.1.1.
Idea 8.1.2 works very well for me on OSX with Grails 1.1 and 1.1.1. Grails is installed under /Developer/grails-1.1.1 (with a symlink at /Developer/grails ), and the plugins are in the ~/.grails/1.1.1/plugins directory.
I didn't have to install any extra Idea plugins. What I did have to do was tell it where the plugins were, and install the missing ones once I had upgraded to 1.1.1. IDEA's grails integration can even recognize the plugins from the Grails repository and install them from the IDE.
NetBeans 6.7 RC3 works much better with Grails 1.1.1 than the versions before. Debugging only works in attached mode, i.e. you start your application from the command line (grails-debug run-app) and then attach the Netbeans Debugger (port 5005). My experience is that the watches do not show the correct values of the running process. Automatic code formatting is horrible.
IntelliJ 8.1.3 worked good for me with Grails 1.1. Debugging was working correctly (most of the time, from time to time, the status of the debugger does not match the actual process' status) and code formatting is quite good. After I switched to Grails 1.1.1 IntelliJ refuses to start my app ("error running MyApp: Grails are not configured") although grails is installed and GRAILS_HOME is set correctly. The trick is to change the facet in the module settings of your project. There you have to configure the location of your grails 1.1.1 installation. Then IntelliJ crashed while starting your app and you have to do the configuration again . With a little bit of luck it works then and everything is fine.
I've spend a lot of time with these issues in the last days and I am quite angry about that. Therefore I'd like to recommend to go away from grails and to use ruby on rails with NetBeans 6.7 instead. Then you can start to focus on your business, not on configuration and installation issues. If you really need to stick with grails, use IntelliJ and pay for it. It's worth it. Do not even think about using Eclipse, if you do not want to go crazy.
I've been playing around with the version 9 milestone 1 release of IntelliJ and so far have not had any problems working with grails apps.
One thing i did notice was that the project explorer doesn't always refresh properly when files are added via an automated process. sometimes i have to close and re-open the project to see the new files, but that could just be a beta issue in general and not related to the grails support.
They've added a lot of Groovy and Grails support to the latest version of the Spring Source Tool Suite. It doesn't ship with these plugins by default, but there are options to install them as extensions from the dashboard page.
Some of the nice features include the ability to run grails commands in the IDE and support for editing GSPs. The Groovy language support has gotten much better too with the latest release of the plugin. You can read more about that here.
The Spring Tools Suite is also an excellent choice for grails/groovy development. I use it and do not have any cause for regret.
I've been using Netbeans 6.7 for some time and it's very slow, the code completion rarely works. Basically I'm using it as an editor and to format my code.
I used the EAP version of IDEA 8.1 and it was really nice - very easy to setup and develop in compared to the other IDEs. Sorry I don't remember exactly how to import an existing project but it was fairly straight forward.
If cost is not an issue, then IDEA would probably be the best choice.
I use STS (SpringSource Toolkit), I like it better than Intellij or Netbeans. I am using 2.3.3.M2