- This topic has 7 replies, 3 voices, and was last updated 10 years ago by
.
-
Posts
-
Four issues:
1) I have a project with a lot of .JS files – When editing a java script file, the content assist often hangs and I end up having to kill MyEclipse to recover. Very frustrating. I had the same problem in 2014 also which is why I tried upgrading to 2015 CI. When it works the javascript content assist in CI is much nicer though.
2) When I create a Tomcat 6 server instance I am never able to deploy to it, because it never shows in the list of servers available for deployment. Also quite frustrating, but the embedded tomcat 7 instance is working so I’m not completly stopped. The conversion did create a migrated tomcat 6 instance, but it never worked.
3) The asterisk marking an changed file takes a very long time to go away after saving. Sometimes making it hard to know whether the file has actually been saved or not. This is annoying, but not a deal breaker.
4) Creating a jar file using a .jardesc file takes much longer in 2015 CI than it did in previous versions. It works, but more slowly. I.e. in 2014 I would click create and it would be basically done instantly. In 2015, I actually have to wait for the jar to finish building.
Any assistance you can provide for problems 1 & 2 will be greatly appreciated.
Hi,
Sorry that you are seeing issues with MyEclipse.
We released MyEclipse 2015CI 7 last week. If you have not yet updated to it, please go to Help > Check for Updates and apply the update. Restart the IDE when it prompts to.
1. Can you please try increasing the memory settings in the myeclipse.ini file and check if it helps?
The myeclipse.ini file can be found in the same folder as your MyEclipse executable. Open it in any text editor and change the values based on the size of your workspace. For instance, the following settings may be preferable to the defaults.
-vmargs -Xmx768m -XX:MaxPermSize=384mYou might have to increase the -Xmx to a higher value based on the size of your workspace.
If the issue persists even after increasing the memory settings, clear the contents of the .log file which is located at <workspace dir>/.metadata/.log, replicate the issue with the JS editing and send us the .log file for further investigation.
2. I could not replicate the issue with Tomcat 6 at my end. Are you working with MyEclipse 2014 workspace in MyEclipse 2015 ?
Can you please switch to a new workspace, configure the Tomcat 6 and check if you can start the server from the Servers view. Create a sample web project and see if you can deploy to server.
3. Increasing the memory might also help in resolving the 3 & 4 issues.
Let us know how it works for you.
@support-swapna wrote:
1. Can you please try increasing the memory settings in the myeclipse.ini file and check if it helps?
Increasing the memory did not help, but upgrading to the latest release seems to have worked for now. I’ll let you know if it comes back.
@support-swapna wrote:
2. I could not replicate the issue with Tomcat 6 at my end. Are you working with MyEclipse 2014 workspace in MyEclipse 2015 ?
Can you please switch to a new workspace, configure the Tomcat 6 and check if you can start the server from the Servers view. Create a sample web project and see if you can deploy to server.
My workspace has been migrated through many different versions of MyEclipse. Prior to 2015 CI, I was using 2014. Even from a new workspace with a sample web project I am unable to see my Tomcat 6 server in the Manage Deployments window.
@support-swapna wrote:
3. Increasing the memory might also help in resolving the 3 & 4 issues.
I’m not seeing the slow save issue currently, but the slow jar process still occurs.
Hi,
Glad that you are no longer seeing issues when editing JS files.
1. When no project is selected, the Manage Deployments window displays the list of servers which already have projects deployed to them. If there is no project deployed to Tomcat 6, the Manage Deployments window will not display the Tomcat 6. If you select a project from the Module dropdown, it will display the list of servers to which the selected project has already been deployed.
If you have selected a project that hasn’t been deployed to any server, the list will be blank and you should click the ‘Add’ button to open up the server selection window. If the project is deployable to an already configured server then you can select the server from the list else you will have to manually define another server.
If you are not seeing Tomcat 6 for your project, then for some reason the project is not deployable to Tomcat 6.You can check with the SimpleJSPExample project from the EOD to rule out issues with Tomcat 6 connector.
Here is the screenshot for your reference :
Alternatively, you can right click on the Tomcat 6 server in the Servers view and select ‘Add/Remove Deployments’. Choose the project from the ‘Available’ list and deploy.
2. I tried to create a jar from a simple .jardesc and I did not see any slowness. Creating a jar file from the .jardesc is an Eclipse feature. I am not sure if the functionality changed in the latest Eclipse (MyEclipse 2015 is based on Eclipse Luna). I recommend using build tools like Maven and ANT instead.
Let us know how it works for you.
@support-swapna wrote:
Hi,
If you are not seeing Tomcat 6 for your project, then for some reason the project is not deployable to Tomcat 6.You can check with the SimpleJSPExample project from the EOD to rule out issues with Tomcat 6 connector.
.Thanks for the response.
The project was previously deployed to Tomcat 6 under ME2014.
I did get a sample project deployed to Tomcat 6 from the blank workspace I created in ME2015CI. You guys added an extra step that was not immediately obvious. Instead of configuring the server in preferences and then being able to deploy to it, we must now configure the server in preferences, and then manually create an instance of the server from the deploy modules window.
However, when I attempt to do that from my actual workspace I am only given the option to create a tomcat 7 or tomcat 8 server. Attempting to download more server adapters does not show the ability to add tomcat 6.
I imported my project from my old workspace to the blank workspace. I still only see tomcat 7 and tomcat 8 options when attempting to create a server. The existing server I deployed my sample project to does not appear.
For anyone with similar problems, attempting to attempting to download the, “SimpleJSPExample” project – the actual project name is ‘Hello World’ Web Application. I was not able to download this example project – it simply failed at the “authenticating using pserver” step with “could not install example project”.
I compared and replaced org.eclipse.wst.common.project.facet.core.xml in my project with the contents of the same file from the sample project. That appears to have solved the Tomcat 6 deployment problem.
katesr,
I just wanted to ad a couple of notes about setting up new servers.
What I think you did was create a new runtime from the Window->Preferences->Servers->Runtime Environments page. When doing this, it’s possible to select an option to automatically create a new local server, at the same time. You can create multiple servers with the same runtime, which is why it is split this way.
You can also create a server definition from the Servers view, using a button near the top of the view, or right-clicking in the view and selecting New->Server. You can also use the File->New menu item. When creating a server, you can select an existing runtime (that is appropriate for the server type) or create a new runtime at the same time.
When deploying to a server, only the servers that can run the selected project are shown (when trying to deploy a specific project) or only the projects that can be deployed to a server are shown (when trying to deploy projects to a specific server). This is generally determined by different levels of JEE technologies. You can see what each server can deploy by trying to create a new server – the types of projects that can be deployed are shown beneath the servers list, when selecting a particular server.
I hope this information helps in the future and sorry for the confusion.
