You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Alex Huang <Al...@citrix.com> on 2013/03/06 01:55:21 UTC
Setting up a better eclipse environment....
Hi All,
I've heard this from a couple of developers on eclipse and cloudstack. Thought I share this tip.
When you open hit Shift-Ctrl-R on eclipse, it opens up the Open Resource dialogue. A lot of people do this as a quick way to get to a file. With CloudStack, many people see a bunch of .class files and three or four different .java files of the same name.
Here's how to get rid of all of that.
1. Quit Eclipse
2. Make sure your workspace is not stored in the cloudstack directory. (This may be only my problem because I used to like to do that.) If your workspace is stored in the directory, you want to delete all eclipse metadata and create the workspace somewhere else.
3. Remove the eclipse generated bin directory from all of the directories. The reason is because CloudStack projects used to use bin as the directory for all the eclipse generated .class files but now with maven based projects, eclipse uses target/classes to store them. So now eclipse sees the .class files in the bin directories as resources that you own. That's why there's .class files in the Open Resource directory.
4. Remove all of the .project files. This is again because we used to checkin .project files and some of your .project files were not created from maven pom.xml. If you did this before, then you can skip steps 5-8.
5. Start Eclipse.
6. If you deleted your workspace in step 2, then you should create a new workspace.
7. Remove all of the projects.
8. Import all maven projects again.
9. Hit Shift-Ctrl-R to open resource dialogue
10. Click on the down arrow in the upper right of the dialogue box
11. Click on the Edit Active Working Set from the drop down menu
12. Create a working set called cloudstack
13. Add all of the projects to it and then remove the parent projects. The reason you want to remove them is because they're parent projects and when you open resource, the open resource dialogue gets the .java file from both the actual project and the parent projects so the same .java file appears more than once.
o Cloudstack-framework
o Cloud-engine
o Cloudstack
o Cloudstack-plugins
o Cloud-services
14. Click on finish
15. Click on the top right drop down button again
16. Make sure "Show derived resources" is not checked
Another easier way to do this may be to push all your commits and changes and then delete the source directory and reclone the repo. Then follow just steps 6-16.
After doing that, when you hit Ctrl-Shift-R, make sure the CloudStack working set is selected. Now only the java file you want will show up. There's no .class files and no multiple copies of the same java files.
--Alex
Re: Setting up a better eclipse environment....
Posted by Sheng Yang <sh...@yasker.org>.
Need to save to wiki...
--Sheng
On Tue, Mar 5, 2013 at 5:06 PM, Alex Huang <Al...@citrix.com> wrote:
> Another tip I have is to create one source repo and workspace for one major branch. We've been changing our environment a lot and it really messes with the whole git checkout <branch> and then have eclipse reconfigure automatically. It has the added benefit of working on multiple branches at the same time simply by opening multiple eclipses.
>
> Just don't create workspaces in the directory you store your source. This used to be okay for me back in the ant days but since the switch to maven, eclipse has had really weird problems with that. Once I stored the workspace outside of the source directory, everything works beautifully.
>
> --Alex
>
>> -----Original Message-----
>> From: Alex Huang [mailto:Alex.Huang@citrix.com]
>> Sent: Tuesday, March 5, 2013 4:55 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Setting up a better eclipse environment....
>>
>> Hi All,
>>
>> I've heard this from a couple of developers on eclipse and cloudstack.
>> Thought I share this tip.
>>
>> When you open hit Shift-Ctrl-R on eclipse, it opens up the Open Resource
>> dialogue. A lot of people do this as a quick way to get to a file. With
>> CloudStack, many people see a bunch of .class files and three or four
>> different .java files of the same name.
>>
>> Here's how to get rid of all of that.
>>
>>
>> 1. Quit Eclipse
>>
>> 2. Make sure your workspace is not stored in the cloudstack directory.
>> (This may be only my problem because I used to like to do that.) If your
>> workspace is stored in the directory, you want to delete all eclipse metadata
>> and create the workspace somewhere else.
>>
>> 3. Remove the eclipse generated bin directory from all of the directories.
>> The reason is because CloudStack projects used to use bin as the directory
>> for all the eclipse generated .class files but now with maven based projects,
>> eclipse uses target/classes to store them. So now eclipse sees the .class files
>> in the bin directories as resources that you own. That's why there's .class
>> files in the Open Resource directory.
>>
>> 4. Remove all of the .project files. This is again because we used to
>> checkin .project files and some of your .project files were not created from
>> maven pom.xml. If you did this before, then you can skip steps 5-8.
>>
>> 5. Start Eclipse.
>>
>> 6. If you deleted your workspace in step 2, then you should create a new
>> workspace.
>>
>> 7. Remove all of the projects.
>>
>> 8. Import all maven projects again.
>>
>> 9. Hit Shift-Ctrl-R to open resource dialogue
>>
>> 10. Click on the down arrow in the upper right of the dialogue box
>>
>> 11. Click on the Edit Active Working Set from the drop down menu
>>
>> 12. Create a working set called cloudstack
>>
>> 13. Add all of the projects to it and then remove the parent projects. The
>> reason you want to remove them is because they're parent projects and
>> when you open resource, the open resource dialogue gets the .java file from
>> both the actual project and the parent projects so the same .java file appears
>> more than once.
>>
>> o Cloudstack-framework
>>
>> o Cloud-engine
>>
>> o Cloudstack
>>
>> o Cloudstack-plugins
>>
>> o Cloud-services
>>
>> 14. Click on finish
>>
>> 15. Click on the top right drop down button again
>>
>> 16. Make sure "Show derived resources" is not checked
>>
>> Another easier way to do this may be to push all your commits and changes
>> and then delete the source directory and reclone the repo. Then follow just
>> steps 6-16.
>>
>> After doing that, when you hit Ctrl-Shift-R, make sure the CloudStack
>> working set is selected. Now only the java file you want will show up.
>> There's no .class files and no multiple copies of the same java files.
>>
>> --Alex
>
Re: Setting up a better eclipse environment....
Posted by Kelven Yang <ke...@citrix.com>.
If you run directly through Eclipse, you don't need
-Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n
You may put your memory settings to the debug profile under JRE tab for
JVM settings
Kelven
On 3/6/13 10:16 AM, "Mike Tutkowski" <mi...@solidfire.com> wrote:
>Thanks
>
>I dropped that value down.
>
>For some reason I get this exception in Eclipse, but not my normal
>console:
>
>Caused by: org.springframework.beans.BeanInstantiationException: Could not
>instantiate bean class [com.cloud.vm.dao.DomainRouterDaoImpl]: Constructor
>threw exception; nested exception is java.lang.OutOfMemoryError: Java heap
>space
>
>at
>org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:162)
>
>at
>org.springframework.beans.factory.support.SimpleInstantiationStrategy.inst
>antiate(
>SimpleInstantiationStrategy.java:76)
>
>at
>org.springframework.beans.factory.support.AbstractAutowireCapableBeanFacto
>ry.instantiateBean(
>AbstractAutowireCapableBeanFactory.java:990)
>
>... 327 more
>
>Caused by: java.lang.OutOfMemoryError: Java heap space
>
>
>On Wed, Mar 6, 2013 at 11:10 AM, Kelven Yang <ke...@citrix.com>
>wrote:
>
>> Mike,
>> you are giving too much to MaxPermSize, with latest master/ASF 4.1
>>branch,
>> -XX:MaxPermSize=128m would be enough
>>
>> Kelven
>>
>> On 3/5/13 11:04 PM, "Mike Tutkowski" <mi...@solidfire.com>
>>wrote:
>>
>> >-XX:MaxPermSize=1024m -Xmx2048m
>>
>>
>
>
>--
>*Mike Tutkowski*
>*Senior CloudStack Developer, SolidFire Inc.*
>e: mike.tutkowski@solidfire.com
>o: 303.746.7302
>Advancing the way the world uses the
>cloud<http://solidfire.com/solution/overview/?video=play>
>**
Re: Setting up a better eclipse environment....
Posted by Mike Tutkowski <mi...@solidfire.com>.
Thanks
I dropped that value down.
For some reason I get this exception in Eclipse, but not my normal console:
Caused by: org.springframework.beans.BeanInstantiationException: Could not
instantiate bean class [com.cloud.vm.dao.DomainRouterDaoImpl]: Constructor
threw exception; nested exception is java.lang.OutOfMemoryError: Java heap
space
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:162)
at
org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(
SimpleInstantiationStrategy.java:76)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(
AbstractAutowireCapableBeanFactory.java:990)
... 327 more
Caused by: java.lang.OutOfMemoryError: Java heap space
On Wed, Mar 6, 2013 at 11:10 AM, Kelven Yang <ke...@citrix.com> wrote:
> Mike,
> you are giving too much to MaxPermSize, with latest master/ASF 4.1 branch,
> -XX:MaxPermSize=128m would be enough
>
> Kelven
>
> On 3/5/13 11:04 PM, "Mike Tutkowski" <mi...@solidfire.com> wrote:
>
> >-XX:MaxPermSize=1024m -Xmx2048m
>
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*
Re: Setting up a better eclipse environment....
Posted by Mike Tutkowski <mi...@solidfire.com>.
This is the exception I see in my Eclipse console (but not my regular
console):
Caused by: java.lang.OutOfMemoryError: Java heap space
... 329 more
2013-03-06 10:50:09.764:WARN::Failed startup of context
org.mortbay.jetty.plugin.Jetty6PluginWebAppContext@557ce3bb
{/client,/Users/mtutkowski/Documents/CloudStack/src/incubator-cloudstack/client/target/cloud-client-ui-4.2.0-SNAPSHOT}
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'virtualMachineEntityImpl': Injection of autowired
dependencies failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: private
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManager
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.manager;
nested exception is org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'VMEntityManagerImpl': Injection of autowired
dependencies failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: protected com.cloud.vm.VirtualMachineManager
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl._itMgr;
nested exception is org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'clusteredVirtualMachineManagerImpl':
Injection of autowired dependencies failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: protected com.cloud.storage.StorageManager
com.cloud.vm.VirtualMachineManagerImpl._storageMgr; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'storageManagerImpl': Injection of autowired dependencies
failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: protected com.cloud.vm.UserVmManager
com.cloud.storage.StorageManagerImpl._userVmMgr; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'userVmManagerImpl': Injection of autowired dependencies
failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: protected com.cloud.network.NetworkModel
com.cloud.vm.UserVmManagerImpl._networkModel; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'networkModelImpl': Injection of autowired dependencies
failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: com.cloud.configuration.ConfigurationManager
com.cloud.network.NetworkModelImpl._configMgr; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'configurationManagerImpl': Injection of autowired
dependencies failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: com.cloud.user.AccountManager
com.cloud.configuration.ConfigurationManagerImpl._accountMgr; nested
exception is org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'accountManagerImpl': Injection of autowired
dependencies failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: private com.cloud.network.security.SecurityGroupManager
com.cloud.user.AccountManagerImpl._networkGroupMgr; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'securityGroupManagerImpl2': Injection of autowired
dependencies failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: com.cloud.agent.AgentManager
com.cloud.network.security.SecurityGroupManagerImpl._agentMgr; nested
exception is org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'clusteredAgentManagerImpl': Injection of autowired
dependencies failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: protected com.cloud.ha.HighAvailabilityManager
com.cloud.agent.manager.AgentManagerImpl._haMgr; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'highAvailabilityManagerExtImpl': Injection of autowired
dependencies failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: java.util.List
com.cloud.ha.HighAvailabilityManagerImpl._investigators; nested exception
is org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'XenServerInvestigator': Injection of autowired dependencies
failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: com.cloud.resource.ResourceManager
com.cloud.ha.XenServerInvestigator._resourceMgr; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'resourceManagerImpl': Injection of autowired dependencies
failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: protected com.cloud.storage.secondary.SecondaryStorageVmManager
com.cloud.resource.ResourceManagerImpl._secondaryStorageMgr; nested
exception is org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'premiumSecondaryStorageManagerImpl': Injection of
autowired dependencies failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: protected com.cloud.network.NetworkManager
com.cloud.storage.secondary.SecondaryStorageManagerImpl._networkMgr; nested
exception is org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'networkManagerImpl': Injection of autowired
dependencies failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: com.cloud.network.rules.RulesManager
com.cloud.network.NetworkManagerImpl._rulesMgr; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'rulesManagerImpl': Injection of autowired dependencies
failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: com.cloud.network.rules.FirewallManager
com.cloud.network.rules.RulesManagerImpl._firewallMgr; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'firewallManagerImpl': Injection of autowired dependencies
failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: com.cloud.network.vpc.VpcManager
com.cloud.network.firewall.FirewallManagerImpl._vpcMgr; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'vpcManagerImpl': Injection of autowired dependencies
failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: com.cloud.network.NetworkService
com.cloud.network.vpc.VpcManagerImpl._ntwkSvc; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'networkServiceImpl': Injection of autowired dependencies
failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: java.util.List com.cloud.network.NetworkServiceImpl._networkGurus;
nested exception is org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'ovsGuestNetworkGuru': Injection of autowired
dependencies failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: com.cloud.network.ovs.OvsTunnelManager
com.cloud.network.guru.OvsGuestNetworkGuru._ovsTunnelMgr; nested exception
is org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'ovsTunnelManagerImpl': Injection of autowired dependencies
failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: com.cloud.vm.dao.DomainRouterDao
com.cloud.network.ovs.OvsTunnelManagerImpl._routerDao; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'domainRouterDaoImpl' defined in URL
[jar:file:/Users/mtutkowski/Documents/CloudStack/src/incubator-cloudstack/client/target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/lib/cloud-server-4.2.0-SNAPSHOT.jar!/com/cloud/vm/dao/DomainRouterDaoImpl.class]:
Instantiation of bean failed; nested exception is
org.springframework.beans.BeanInstantiationException: Could not instantiate
bean class [com.cloud.vm.dao.DomainRouterDaoImpl]: Constructor threw
exception; nested exception is java.lang.OutOfMemoryError: Java heap space
at
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(
AutowiredAnnotationBeanPostProcessor.java:287)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(
AbstractAutowireCapableBeanFactory.java:1106)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(
AbstractAutowireCapableBeanFactory.java:517)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(
AbstractAutowireCapableBeanFactory.java:456)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(
AbstractBeanFactory.java:294)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(
DefaultSingletonBeanRegistry.java:225)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(
AbstractBeanFactory.java:291)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(
AbstractBeanFactory.java:193)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(
DefaultListableBeanFactory.java:609)
at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(
AbstractApplicationContext.java:918)
at org.springframework.context.support.AbstractApplicationContext.refresh(
AbstractApplicationContext.java:469)
at
org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(
ContextLoader.java:383)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(
ContextLoader.java:283)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(
ContextLoaderListener.java:111)
at org.mortbay.jetty.handler.ContextHandler.startContext(
ContextHandler.java:549)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
at org.mortbay.jetty.webapp.WebAppContext.startContext(
WebAppContext.java:1282)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:518)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:499)
at org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(
Jetty6PluginWebAppContext.java:115)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.handler.HandlerCollection.doStart(
HandlerCollection.java:152)
at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(
ContextHandlerCollection.java:156)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.handler.HandlerCollection.doStart(
HandlerCollection.java:152)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
at org.mortbay.jetty.Server.doStart(Server.java:224)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.plugin.Jetty6PluginServer.start(
Jetty6PluginServer.java:132)
at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(
AbstractJettyMojo.java:454)
at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(
AbstractJettyMojo.java:396)
at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(
AbstractJettyRunMojo.java:210)
at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:184)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(
DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
MojoExecutor.java:209)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(
LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(
LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(
LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(
LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(
Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(
Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(
Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
On Wed, Mar 6, 2013 at 12:04 AM, Mike Tutkowski <
mike.tutkowski@solidfire.com> wrote:
> Here is what I have for MAVEN_OPTS when trying to run Jetty/Management
> Server:
>
> -XX:MaxPermSize=1024m -Xmx2048m -Xdebug
> -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n
>
>
> On Wed, Mar 6, 2013 at 12:02 AM, Mike Tutkowski <
> mike.tutkowski@solidfire.com> wrote:
>
>> Hey guys,
>>
>> I appreciate all this Eclipse info. I've mainly been building and
>> running the system from a command prompt, but would like to work more in
>> Eclipse.
>>
>> I have cleaning, installing, and deploying a new DB working, but running
>> the management server with Jetty leads to an out-of-heap-memory error (all
>> of this from Eclipse...it works fine from the command prompt of the
>> terminal app I'm using in Mac OS X).
>>
>> Any ideas?
>>
>> Thanks!
>>
>>
>> On Tue, Mar 5, 2013 at 6:48 PM, Alex Huang <Al...@citrix.com> wrote:
>>
>>> I tried that but it seems to be overloaded. Like to choose my own
>>> plugins and keep it to a minimum. Maybe just psychological but at least I
>>> think it's faster.
>>>
>>> --Alex
>>>
>>> > -----Original Message-----
>>> > From: Frank Zhang [mailto:Frank.Zhang@citrix.com]
>>> > Sent: Tuesday, March 5, 2013 5:09 PM
>>> > To: cloudstack-dev@incubator.apache.org
>>> > Subject: RE: Setting up a better eclipse environment....
>>> >
>>> > Another tip:
>>> >
>>> > Using Spring Tool Suite that is a forked eclipse with Spring features
>>> saves you
>>> > much time in installing plugins like m2e(maven plugin)
>>> >
>>> > http://www.springsource.org/sts
>>> >
>>> > > -----Original Message-----
>>> > > From: Alex Huang [mailto:Alex.Huang@citrix.com]
>>> > > Sent: Tuesday, March 05, 2013 5:07 PM
>>> > > To: cloudstack-dev@incubator.apache.org
>>> > > Subject: RE: Setting up a better eclipse environment....
>>> > >
>>> > > Another tip I have is to create one source repo and workspace for one
>>> > > major branch. We've been changing our environment a lot and it
>>> really
>>> > > messes with the whole git checkout <branch> and then have eclipse
>>> > > reconfigure automatically. It has the added benefit of working on
>>> > > multiple branches at the same time simply by opening multiple
>>> eclipses.
>>> > >
>>> > > Just don't create workspaces in the directory you store your source.
>>> > > This used to be okay for me back in the ant days but since the switch
>>> > > to maven, eclipse has had really weird problems with that. Once I
>>> > > stored the workspace outside of the source directory, everything
>>> works
>>> > beautifully.
>>> > >
>>> > > --Alex
>>> > >
>>> > > > -----Original Message-----
>>> > > > From: Alex Huang [mailto:Alex.Huang@citrix.com]
>>> > > > Sent: Tuesday, March 5, 2013 4:55 PM
>>> > > > To: cloudstack-dev@incubator.apache.org
>>> > > > Subject: Setting up a better eclipse environment....
>>> > > >
>>> > > > Hi All,
>>> > > >
>>> > > > I've heard this from a couple of developers on eclipse and
>>> cloudstack.
>>> > > > Thought I share this tip.
>>> > > >
>>> > > > When you open hit Shift-Ctrl-R on eclipse, it opens up the Open
>>> > > > Resource dialogue. A lot of people do this as a quick way to get
>>> to
>>> > > > a file. With CloudStack, many people see a bunch of .class files
>>> > > > and three or four different .java files of the same name.
>>> > > >
>>> > > > Here's how to get rid of all of that.
>>> > > >
>>> > > >
>>> > > > 1. Quit Eclipse
>>> > > >
>>> > > > 2. Make sure your workspace is not stored in the cloudstack
>>> directory.
>>> > > > (This may be only my problem because I used to like to do that.)
>>> If
>>> > > > your workspace is stored in the directory, you want to delete all
>>> > > > eclipse metadata and create the workspace somewhere else.
>>> > > >
>>> > > > 3. Remove the eclipse generated bin directory from all of the
>>> > directories.
>>> > > > The reason is because CloudStack projects used to use bin as the
>>> > > > directory for all the eclipse generated .class files but now with
>>> > > > maven based projects, eclipse uses target/classes to store them.
>>> So
>>> > > > now eclipse sees the .class files in the bin directories as
>>> > > > resources that you own. That's why there's .class files in the
>>> Open
>>> > Resource directory.
>>> > > >
>>> > > > 4. Remove all of the .project files. This is again because
>>> we used to
>>> > > > checkin .project files and some of your .project files were not
>>> > > > created from maven pom.xml. If you did this before, then you can
>>> > > > skip
>>> > > steps 5-8.
>>> > > >
>>> > > > 5. Start Eclipse.
>>> > > >
>>> > > > 6. If you deleted your workspace in step 2, then you should
>>> create a
>>> > > new
>>> > > > workspace.
>>> > > >
>>> > > > 7. Remove all of the projects.
>>> > > >
>>> > > > 8. Import all maven projects again.
>>> > > >
>>> > > > 9. Hit Shift-Ctrl-R to open resource dialogue
>>> > > >
>>> > > > 10. Click on the down arrow in the upper right of the dialogue
>>> box
>>> > > >
>>> > > > 11. Click on the Edit Active Working Set from the drop down menu
>>> > > >
>>> > > > 12. Create a working set called cloudstack
>>> > > >
>>> > > > 13. Add all of the projects to it and then remove the parent
>>> projects.
>>> > The
>>> > > > reason you want to remove them is because they're parent projects
>>> > > > and when you open resource, the open resource dialogue gets the
>>> > > > .java file from both the actual project and the parent projects so
>>> > > > the same .java file appears more than once.
>>> > > >
>>> > > > o Cloudstack-framework
>>> > > >
>>> > > > o Cloud-engine
>>> > > >
>>> > > > o Cloudstack
>>> > > >
>>> > > > o Cloudstack-plugins
>>> > > >
>>> > > > o Cloud-services
>>> > > >
>>> > > > 14. Click on finish
>>> > > >
>>> > > > 15. Click on the top right drop down button again
>>> > > >
>>> > > > 16. Make sure "Show derived resources" is not checked
>>> > > >
>>> > > > Another easier way to do this may be to push all your commits and
>>> > > > changes and then delete the source directory and reclone the repo.
>>> > > > Then follow just steps 6-16.
>>> > > >
>>> > > > After doing that, when you hit Ctrl-Shift-R, make sure the
>>> > > > CloudStack working set is selected. Now only the java file you
>>> want will
>>> > show up.
>>> > > > There's no .class files and no multiple copies of the same java
>>> files.
>>> > > >
>>> > > > --Alex
>>>
>>>
>>
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkowski@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play>
>> *™*
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play>
> *™*
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*
Re: Setting up a better eclipse environment....
Posted by Kelven Yang <ke...@citrix.com>.
Mike,
you are giving too much to MaxPermSize, with latest master/ASF 4.1 branch,
-XX:MaxPermSize=128m would be enough
Kelven
On 3/5/13 11:04 PM, "Mike Tutkowski" <mi...@solidfire.com> wrote:
>-XX:MaxPermSize=1024m -Xmx2048m
Re: Setting up a better eclipse environment....
Posted by Mike Tutkowski <mi...@solidfire.com>.
Here is what I have for MAVEN_OPTS when trying to run Jetty/Management
Server:
-XX:MaxPermSize=1024m -Xmx2048m -Xdebug
-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n
On Wed, Mar 6, 2013 at 12:02 AM, Mike Tutkowski <
mike.tutkowski@solidfire.com> wrote:
> Hey guys,
>
> I appreciate all this Eclipse info. I've mainly been building and running
> the system from a command prompt, but would like to work more in Eclipse.
>
> I have cleaning, installing, and deploying a new DB working, but running
> the management server with Jetty leads to an out-of-heap-memory error (all
> of this from Eclipse...it works fine from the command prompt of the
> terminal app I'm using in Mac OS X).
>
> Any ideas?
>
> Thanks!
>
>
> On Tue, Mar 5, 2013 at 6:48 PM, Alex Huang <Al...@citrix.com> wrote:
>
>> I tried that but it seems to be overloaded. Like to choose my own
>> plugins and keep it to a minimum. Maybe just psychological but at least I
>> think it's faster.
>>
>> --Alex
>>
>> > -----Original Message-----
>> > From: Frank Zhang [mailto:Frank.Zhang@citrix.com]
>> > Sent: Tuesday, March 5, 2013 5:09 PM
>> > To: cloudstack-dev@incubator.apache.org
>> > Subject: RE: Setting up a better eclipse environment....
>> >
>> > Another tip:
>> >
>> > Using Spring Tool Suite that is a forked eclipse with Spring features
>> saves you
>> > much time in installing plugins like m2e(maven plugin)
>> >
>> > http://www.springsource.org/sts
>> >
>> > > -----Original Message-----
>> > > From: Alex Huang [mailto:Alex.Huang@citrix.com]
>> > > Sent: Tuesday, March 05, 2013 5:07 PM
>> > > To: cloudstack-dev@incubator.apache.org
>> > > Subject: RE: Setting up a better eclipse environment....
>> > >
>> > > Another tip I have is to create one source repo and workspace for one
>> > > major branch. We've been changing our environment a lot and it really
>> > > messes with the whole git checkout <branch> and then have eclipse
>> > > reconfigure automatically. It has the added benefit of working on
>> > > multiple branches at the same time simply by opening multiple
>> eclipses.
>> > >
>> > > Just don't create workspaces in the directory you store your source.
>> > > This used to be okay for me back in the ant days but since the switch
>> > > to maven, eclipse has had really weird problems with that. Once I
>> > > stored the workspace outside of the source directory, everything works
>> > beautifully.
>> > >
>> > > --Alex
>> > >
>> > > > -----Original Message-----
>> > > > From: Alex Huang [mailto:Alex.Huang@citrix.com]
>> > > > Sent: Tuesday, March 5, 2013 4:55 PM
>> > > > To: cloudstack-dev@incubator.apache.org
>> > > > Subject: Setting up a better eclipse environment....
>> > > >
>> > > > Hi All,
>> > > >
>> > > > I've heard this from a couple of developers on eclipse and
>> cloudstack.
>> > > > Thought I share this tip.
>> > > >
>> > > > When you open hit Shift-Ctrl-R on eclipse, it opens up the Open
>> > > > Resource dialogue. A lot of people do this as a quick way to get to
>> > > > a file. With CloudStack, many people see a bunch of .class files
>> > > > and three or four different .java files of the same name.
>> > > >
>> > > > Here's how to get rid of all of that.
>> > > >
>> > > >
>> > > > 1. Quit Eclipse
>> > > >
>> > > > 2. Make sure your workspace is not stored in the cloudstack
>> directory.
>> > > > (This may be only my problem because I used to like to do that.) If
>> > > > your workspace is stored in the directory, you want to delete all
>> > > > eclipse metadata and create the workspace somewhere else.
>> > > >
>> > > > 3. Remove the eclipse generated bin directory from all of the
>> > directories.
>> > > > The reason is because CloudStack projects used to use bin as the
>> > > > directory for all the eclipse generated .class files but now with
>> > > > maven based projects, eclipse uses target/classes to store them. So
>> > > > now eclipse sees the .class files in the bin directories as
>> > > > resources that you own. That's why there's .class files in the Open
>> > Resource directory.
>> > > >
>> > > > 4. Remove all of the .project files. This is again because
>> we used to
>> > > > checkin .project files and some of your .project files were not
>> > > > created from maven pom.xml. If you did this before, then you can
>> > > > skip
>> > > steps 5-8.
>> > > >
>> > > > 5. Start Eclipse.
>> > > >
>> > > > 6. If you deleted your workspace in step 2, then you should
>> create a
>> > > new
>> > > > workspace.
>> > > >
>> > > > 7. Remove all of the projects.
>> > > >
>> > > > 8. Import all maven projects again.
>> > > >
>> > > > 9. Hit Shift-Ctrl-R to open resource dialogue
>> > > >
>> > > > 10. Click on the down arrow in the upper right of the dialogue box
>> > > >
>> > > > 11. Click on the Edit Active Working Set from the drop down menu
>> > > >
>> > > > 12. Create a working set called cloudstack
>> > > >
>> > > > 13. Add all of the projects to it and then remove the parent
>> projects.
>> > The
>> > > > reason you want to remove them is because they're parent projects
>> > > > and when you open resource, the open resource dialogue gets the
>> > > > .java file from both the actual project and the parent projects so
>> > > > the same .java file appears more than once.
>> > > >
>> > > > o Cloudstack-framework
>> > > >
>> > > > o Cloud-engine
>> > > >
>> > > > o Cloudstack
>> > > >
>> > > > o Cloudstack-plugins
>> > > >
>> > > > o Cloud-services
>> > > >
>> > > > 14. Click on finish
>> > > >
>> > > > 15. Click on the top right drop down button again
>> > > >
>> > > > 16. Make sure "Show derived resources" is not checked
>> > > >
>> > > > Another easier way to do this may be to push all your commits and
>> > > > changes and then delete the source directory and reclone the repo.
>> > > > Then follow just steps 6-16.
>> > > >
>> > > > After doing that, when you hit Ctrl-Shift-R, make sure the
>> > > > CloudStack working set is selected. Now only the java file you
>> want will
>> > show up.
>> > > > There's no .class files and no multiple copies of the same java
>> files.
>> > > >
>> > > > --Alex
>>
>>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play>
> *™*
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*
Re: Setting up a better eclipse environment....
Posted by Mike Tutkowski <mi...@solidfire.com>.
Hey guys,
I appreciate all this Eclipse info. I've mainly been building and running
the system from a command prompt, but would like to work more in Eclipse.
I have cleaning, installing, and deploying a new DB working, but running
the management server with Jetty leads to an out-of-heap-memory error (all
of this from Eclipse...it works fine from the command prompt of the
terminal app I'm using in Mac OS X).
Any ideas?
Thanks!
On Tue, Mar 5, 2013 at 6:48 PM, Alex Huang <Al...@citrix.com> wrote:
> I tried that but it seems to be overloaded. Like to choose my own plugins
> and keep it to a minimum. Maybe just psychological but at least I think
> it's faster.
>
> --Alex
>
> > -----Original Message-----
> > From: Frank Zhang [mailto:Frank.Zhang@citrix.com]
> > Sent: Tuesday, March 5, 2013 5:09 PM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: RE: Setting up a better eclipse environment....
> >
> > Another tip:
> >
> > Using Spring Tool Suite that is a forked eclipse with Spring features
> saves you
> > much time in installing plugins like m2e(maven plugin)
> >
> > http://www.springsource.org/sts
> >
> > > -----Original Message-----
> > > From: Alex Huang [mailto:Alex.Huang@citrix.com]
> > > Sent: Tuesday, March 05, 2013 5:07 PM
> > > To: cloudstack-dev@incubator.apache.org
> > > Subject: RE: Setting up a better eclipse environment....
> > >
> > > Another tip I have is to create one source repo and workspace for one
> > > major branch. We've been changing our environment a lot and it really
> > > messes with the whole git checkout <branch> and then have eclipse
> > > reconfigure automatically. It has the added benefit of working on
> > > multiple branches at the same time simply by opening multiple eclipses.
> > >
> > > Just don't create workspaces in the directory you store your source.
> > > This used to be okay for me back in the ant days but since the switch
> > > to maven, eclipse has had really weird problems with that. Once I
> > > stored the workspace outside of the source directory, everything works
> > beautifully.
> > >
> > > --Alex
> > >
> > > > -----Original Message-----
> > > > From: Alex Huang [mailto:Alex.Huang@citrix.com]
> > > > Sent: Tuesday, March 5, 2013 4:55 PM
> > > > To: cloudstack-dev@incubator.apache.org
> > > > Subject: Setting up a better eclipse environment....
> > > >
> > > > Hi All,
> > > >
> > > > I've heard this from a couple of developers on eclipse and
> cloudstack.
> > > > Thought I share this tip.
> > > >
> > > > When you open hit Shift-Ctrl-R on eclipse, it opens up the Open
> > > > Resource dialogue. A lot of people do this as a quick way to get to
> > > > a file. With CloudStack, many people see a bunch of .class files
> > > > and three or four different .java files of the same name.
> > > >
> > > > Here's how to get rid of all of that.
> > > >
> > > >
> > > > 1. Quit Eclipse
> > > >
> > > > 2. Make sure your workspace is not stored in the cloudstack
> directory.
> > > > (This may be only my problem because I used to like to do that.) If
> > > > your workspace is stored in the directory, you want to delete all
> > > > eclipse metadata and create the workspace somewhere else.
> > > >
> > > > 3. Remove the eclipse generated bin directory from all of the
> > directories.
> > > > The reason is because CloudStack projects used to use bin as the
> > > > directory for all the eclipse generated .class files but now with
> > > > maven based projects, eclipse uses target/classes to store them. So
> > > > now eclipse sees the .class files in the bin directories as
> > > > resources that you own. That's why there's .class files in the Open
> > Resource directory.
> > > >
> > > > 4. Remove all of the .project files. This is again because we
> used to
> > > > checkin .project files and some of your .project files were not
> > > > created from maven pom.xml. If you did this before, then you can
> > > > skip
> > > steps 5-8.
> > > >
> > > > 5. Start Eclipse.
> > > >
> > > > 6. If you deleted your workspace in step 2, then you should
> create a
> > > new
> > > > workspace.
> > > >
> > > > 7. Remove all of the projects.
> > > >
> > > > 8. Import all maven projects again.
> > > >
> > > > 9. Hit Shift-Ctrl-R to open resource dialogue
> > > >
> > > > 10. Click on the down arrow in the upper right of the dialogue box
> > > >
> > > > 11. Click on the Edit Active Working Set from the drop down menu
> > > >
> > > > 12. Create a working set called cloudstack
> > > >
> > > > 13. Add all of the projects to it and then remove the parent
> projects.
> > The
> > > > reason you want to remove them is because they're parent projects
> > > > and when you open resource, the open resource dialogue gets the
> > > > .java file from both the actual project and the parent projects so
> > > > the same .java file appears more than once.
> > > >
> > > > o Cloudstack-framework
> > > >
> > > > o Cloud-engine
> > > >
> > > > o Cloudstack
> > > >
> > > > o Cloudstack-plugins
> > > >
> > > > o Cloud-services
> > > >
> > > > 14. Click on finish
> > > >
> > > > 15. Click on the top right drop down button again
> > > >
> > > > 16. Make sure "Show derived resources" is not checked
> > > >
> > > > Another easier way to do this may be to push all your commits and
> > > > changes and then delete the source directory and reclone the repo.
> > > > Then follow just steps 6-16.
> > > >
> > > > After doing that, when you hit Ctrl-Shift-R, make sure the
> > > > CloudStack working set is selected. Now only the java file you want
> will
> > show up.
> > > > There's no .class files and no multiple copies of the same java
> files.
> > > >
> > > > --Alex
>
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*
RE: Setting up a better eclipse environment....
Posted by Alex Huang <Al...@citrix.com>.
I tried that but it seems to be overloaded. Like to choose my own plugins and keep it to a minimum. Maybe just psychological but at least I think it's faster.
--Alex
> -----Original Message-----
> From: Frank Zhang [mailto:Frank.Zhang@citrix.com]
> Sent: Tuesday, March 5, 2013 5:09 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Setting up a better eclipse environment....
>
> Another tip:
>
> Using Spring Tool Suite that is a forked eclipse with Spring features saves you
> much time in installing plugins like m2e(maven plugin)
>
> http://www.springsource.org/sts
>
> > -----Original Message-----
> > From: Alex Huang [mailto:Alex.Huang@citrix.com]
> > Sent: Tuesday, March 05, 2013 5:07 PM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: RE: Setting up a better eclipse environment....
> >
> > Another tip I have is to create one source repo and workspace for one
> > major branch. We've been changing our environment a lot and it really
> > messes with the whole git checkout <branch> and then have eclipse
> > reconfigure automatically. It has the added benefit of working on
> > multiple branches at the same time simply by opening multiple eclipses.
> >
> > Just don't create workspaces in the directory you store your source.
> > This used to be okay for me back in the ant days but since the switch
> > to maven, eclipse has had really weird problems with that. Once I
> > stored the workspace outside of the source directory, everything works
> beautifully.
> >
> > --Alex
> >
> > > -----Original Message-----
> > > From: Alex Huang [mailto:Alex.Huang@citrix.com]
> > > Sent: Tuesday, March 5, 2013 4:55 PM
> > > To: cloudstack-dev@incubator.apache.org
> > > Subject: Setting up a better eclipse environment....
> > >
> > > Hi All,
> > >
> > > I've heard this from a couple of developers on eclipse and cloudstack.
> > > Thought I share this tip.
> > >
> > > When you open hit Shift-Ctrl-R on eclipse, it opens up the Open
> > > Resource dialogue. A lot of people do this as a quick way to get to
> > > a file. With CloudStack, many people see a bunch of .class files
> > > and three or four different .java files of the same name.
> > >
> > > Here's how to get rid of all of that.
> > >
> > >
> > > 1. Quit Eclipse
> > >
> > > 2. Make sure your workspace is not stored in the cloudstack directory.
> > > (This may be only my problem because I used to like to do that.) If
> > > your workspace is stored in the directory, you want to delete all
> > > eclipse metadata and create the workspace somewhere else.
> > >
> > > 3. Remove the eclipse generated bin directory from all of the
> directories.
> > > The reason is because CloudStack projects used to use bin as the
> > > directory for all the eclipse generated .class files but now with
> > > maven based projects, eclipse uses target/classes to store them. So
> > > now eclipse sees the .class files in the bin directories as
> > > resources that you own. That's why there's .class files in the Open
> Resource directory.
> > >
> > > 4. Remove all of the .project files. This is again because we used to
> > > checkin .project files and some of your .project files were not
> > > created from maven pom.xml. If you did this before, then you can
> > > skip
> > steps 5-8.
> > >
> > > 5. Start Eclipse.
> > >
> > > 6. If you deleted your workspace in step 2, then you should create a
> > new
> > > workspace.
> > >
> > > 7. Remove all of the projects.
> > >
> > > 8. Import all maven projects again.
> > >
> > > 9. Hit Shift-Ctrl-R to open resource dialogue
> > >
> > > 10. Click on the down arrow in the upper right of the dialogue box
> > >
> > > 11. Click on the Edit Active Working Set from the drop down menu
> > >
> > > 12. Create a working set called cloudstack
> > >
> > > 13. Add all of the projects to it and then remove the parent projects.
> The
> > > reason you want to remove them is because they're parent projects
> > > and when you open resource, the open resource dialogue gets the
> > > .java file from both the actual project and the parent projects so
> > > the same .java file appears more than once.
> > >
> > > o Cloudstack-framework
> > >
> > > o Cloud-engine
> > >
> > > o Cloudstack
> > >
> > > o Cloudstack-plugins
> > >
> > > o Cloud-services
> > >
> > > 14. Click on finish
> > >
> > > 15. Click on the top right drop down button again
> > >
> > > 16. Make sure "Show derived resources" is not checked
> > >
> > > Another easier way to do this may be to push all your commits and
> > > changes and then delete the source directory and reclone the repo.
> > > Then follow just steps 6-16.
> > >
> > > After doing that, when you hit Ctrl-Shift-R, make sure the
> > > CloudStack working set is selected. Now only the java file you want will
> show up.
> > > There's no .class files and no multiple copies of the same java files.
> > >
> > > --Alex
RE: Setting up a better eclipse environment....
Posted by Frank Zhang <Fr...@citrix.com>.
Another tip:
Using Spring Tool Suite that is a forked eclipse with Spring features saves you much time in installing plugins like m2e(maven plugin)
http://www.springsource.org/sts
> -----Original Message-----
> From: Alex Huang [mailto:Alex.Huang@citrix.com]
> Sent: Tuesday, March 05, 2013 5:07 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Setting up a better eclipse environment....
>
> Another tip I have is to create one source repo and workspace for one major
> branch. We've been changing our environment a lot and it really messes
> with the whole git checkout <branch> and then have eclipse reconfigure
> automatically. It has the added benefit of working on multiple branches at
> the same time simply by opening multiple eclipses.
>
> Just don't create workspaces in the directory you store your source. This
> used to be okay for me back in the ant days but since the switch to maven,
> eclipse has had really weird problems with that. Once I stored the workspace
> outside of the source directory, everything works beautifully.
>
> --Alex
>
> > -----Original Message-----
> > From: Alex Huang [mailto:Alex.Huang@citrix.com]
> > Sent: Tuesday, March 5, 2013 4:55 PM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: Setting up a better eclipse environment....
> >
> > Hi All,
> >
> > I've heard this from a couple of developers on eclipse and cloudstack.
> > Thought I share this tip.
> >
> > When you open hit Shift-Ctrl-R on eclipse, it opens up the Open
> > Resource dialogue. A lot of people do this as a quick way to get to a
> > file. With CloudStack, many people see a bunch of .class files and
> > three or four different .java files of the same name.
> >
> > Here's how to get rid of all of that.
> >
> >
> > 1. Quit Eclipse
> >
> > 2. Make sure your workspace is not stored in the cloudstack directory.
> > (This may be only my problem because I used to like to do that.) If
> > your workspace is stored in the directory, you want to delete all
> > eclipse metadata and create the workspace somewhere else.
> >
> > 3. Remove the eclipse generated bin directory from all of the directories.
> > The reason is because CloudStack projects used to use bin as the
> > directory for all the eclipse generated .class files but now with
> > maven based projects, eclipse uses target/classes to store them. So
> > now eclipse sees the .class files in the bin directories as resources
> > that you own. That's why there's .class files in the Open Resource directory.
> >
> > 4. Remove all of the .project files. This is again because we used to
> > checkin .project files and some of your .project files were not
> > created from maven pom.xml. If you did this before, then you can skip
> steps 5-8.
> >
> > 5. Start Eclipse.
> >
> > 6. If you deleted your workspace in step 2, then you should create a
> new
> > workspace.
> >
> > 7. Remove all of the projects.
> >
> > 8. Import all maven projects again.
> >
> > 9. Hit Shift-Ctrl-R to open resource dialogue
> >
> > 10. Click on the down arrow in the upper right of the dialogue box
> >
> > 11. Click on the Edit Active Working Set from the drop down menu
> >
> > 12. Create a working set called cloudstack
> >
> > 13. Add all of the projects to it and then remove the parent projects. The
> > reason you want to remove them is because they're parent projects and
> > when you open resource, the open resource dialogue gets the .java file
> > from both the actual project and the parent projects so the same .java
> > file appears more than once.
> >
> > o Cloudstack-framework
> >
> > o Cloud-engine
> >
> > o Cloudstack
> >
> > o Cloudstack-plugins
> >
> > o Cloud-services
> >
> > 14. Click on finish
> >
> > 15. Click on the top right drop down button again
> >
> > 16. Make sure "Show derived resources" is not checked
> >
> > Another easier way to do this may be to push all your commits and
> > changes and then delete the source directory and reclone the repo.
> > Then follow just steps 6-16.
> >
> > After doing that, when you hit Ctrl-Shift-R, make sure the CloudStack
> > working set is selected. Now only the java file you want will show up.
> > There's no .class files and no multiple copies of the same java files.
> >
> > --Alex
RE: Setting up a better eclipse environment....
Posted by Alex Huang <Al...@citrix.com>.
Another tip I have is to create one source repo and workspace for one major branch. We've been changing our environment a lot and it really messes with the whole git checkout <branch> and then have eclipse reconfigure automatically. It has the added benefit of working on multiple branches at the same time simply by opening multiple eclipses.
Just don't create workspaces in the directory you store your source. This used to be okay for me back in the ant days but since the switch to maven, eclipse has had really weird problems with that. Once I stored the workspace outside of the source directory, everything works beautifully.
--Alex
> -----Original Message-----
> From: Alex Huang [mailto:Alex.Huang@citrix.com]
> Sent: Tuesday, March 5, 2013 4:55 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Setting up a better eclipse environment....
>
> Hi All,
>
> I've heard this from a couple of developers on eclipse and cloudstack.
> Thought I share this tip.
>
> When you open hit Shift-Ctrl-R on eclipse, it opens up the Open Resource
> dialogue. A lot of people do this as a quick way to get to a file. With
> CloudStack, many people see a bunch of .class files and three or four
> different .java files of the same name.
>
> Here's how to get rid of all of that.
>
>
> 1. Quit Eclipse
>
> 2. Make sure your workspace is not stored in the cloudstack directory.
> (This may be only my problem because I used to like to do that.) If your
> workspace is stored in the directory, you want to delete all eclipse metadata
> and create the workspace somewhere else.
>
> 3. Remove the eclipse generated bin directory from all of the directories.
> The reason is because CloudStack projects used to use bin as the directory
> for all the eclipse generated .class files but now with maven based projects,
> eclipse uses target/classes to store them. So now eclipse sees the .class files
> in the bin directories as resources that you own. That's why there's .class
> files in the Open Resource directory.
>
> 4. Remove all of the .project files. This is again because we used to
> checkin .project files and some of your .project files were not created from
> maven pom.xml. If you did this before, then you can skip steps 5-8.
>
> 5. Start Eclipse.
>
> 6. If you deleted your workspace in step 2, then you should create a new
> workspace.
>
> 7. Remove all of the projects.
>
> 8. Import all maven projects again.
>
> 9. Hit Shift-Ctrl-R to open resource dialogue
>
> 10. Click on the down arrow in the upper right of the dialogue box
>
> 11. Click on the Edit Active Working Set from the drop down menu
>
> 12. Create a working set called cloudstack
>
> 13. Add all of the projects to it and then remove the parent projects. The
> reason you want to remove them is because they're parent projects and
> when you open resource, the open resource dialogue gets the .java file from
> both the actual project and the parent projects so the same .java file appears
> more than once.
>
> o Cloudstack-framework
>
> o Cloud-engine
>
> o Cloudstack
>
> o Cloudstack-plugins
>
> o Cloud-services
>
> 14. Click on finish
>
> 15. Click on the top right drop down button again
>
> 16. Make sure "Show derived resources" is not checked
>
> Another easier way to do this may be to push all your commits and changes
> and then delete the source directory and reclone the repo. Then follow just
> steps 6-16.
>
> After doing that, when you hit Ctrl-Shift-R, make sure the CloudStack
> working set is selected. Now only the java file you want will show up.
> There's no .class files and no multiple copies of the same java files.
>
> --Alex