For example, the following command would run Eclipse with a heap size of 2048MB: eclipse normal arguments -vmargs -Xmx2048m more VM args The arguments after -vmargs are directly passed to the VM.They explode the memory representation of your binary files by 35-40. The easiest thing to do is download Eclipse IDE for Java EE Developers.In my case ,when running the webapp using jetty I got java.lang.OutOfmemory error PremGen space error : in order to fix that i have increased the eclipse JRE.If you are getting OutOfMemoryError s while running Eclipse, the VM can be told to let the heap grow to a larger amount by passing the -vmargs command to the Eclipse launcher. Eclipse 4.2 Juno (or higher) is the recommended version of Eclipse to use because its support for Maven via the m2e plugin works the best with all of the OpenNMS maven plugins and dependencies. Go to your Eclipse setup folder If you are running Eclipse on Mac OS X then Right click on eclipse.app icon Click on Show Package Contents Open eclipse.ini file Change below parameters -Xms512m-Xmx3000m (Hoping your developer box has >4GB of memory) Add below parameters -XX. Tuning Eclipse Performance and Avoiding OutOfMemory Exceptions.And install the plugins from these update sites:If Eclipse won't let you add the EGit URL, and claims that it's a "duplicate", you should be able to enable that built-in site by clicking on the "Additional Software Sources" or "Available Software Sites" link in the Install New Software dialog, finding it in the (large) list of built-in sites, and checking the box. I know you feel dirty installing applications outside of your favorite package manager.First, you'll want to configure Eclipse to use the OpenNMS code conventions.Go to Help -> Install New Software. Exe built file showed nothing.Do not use the eclipse provided by your distribution (Ubuntu 10.04's Eclipse is broken for instance), it's probably patched and some plugins won't install properly.
Increase Memory For Eclipse Patch Sources FeatureIf you are working on an earlier version of OpenNMS, you should really consider upgrading, and if that's not (yet) possible, see the next section for instructions that work with OpenNMS 1.6 and earlier. Google Eclipse Plugin: Galileo (3.5), Helios (3.6), Indigo (3.7), Juno (4.2)These instructions are for OpenNMS 1.7 and newer. Groovy Eclipse SDK/Groovy-Eclipse Sources Feature Groovy Eclipse SDK/Groovy-Eclipse JDT Patch Sources Feature (not 3.7) Groovy IDE: Galileo (3.5), Helios (3.6), Indigo (3.7), Juno (4.2)![]() Select your ~/rcs/opennms directory as your root, and select all projects. Go to File->Import and select Maven->Existing Maven Projects On Mac OS X, you can edit Eclipse.app/Contents/MacOS/eclipse.ini and adjust the existing "-Xmx" option. On Linux: eclipse -vmargs -Xmx2GFor most developers who only import specific modules that they are working on, a smaller value of 1G should be sufficient. If after completing this step you still have errors about missing configuration classes, you might need to right-click target/generated-sources/castor, and select Build Path -> Use As Source Folder from the context menu for that project. This will catch all of the "generated" sources in the projects, and you should get a clean build Select all projects, right-click, and choose Maven->Update Project Configuration If you are behind a proxy, do not forget to configure it in ~/.m2/settings.xml You may want to deselect "opennms-tools" when importing, since it contains projects that have external (private) dependencies. Siemens opc scout v10 download freeIf you you get the problem "The project '' does not have any GWT SDKs on its build path", then right click on the named project, goto "Build Path/Add Libraries", select "Google Web Toolkit" and click Next, then click "Finish" to use the default SDK. UPDATE: A good fix to pull in sources which are generated in the target directory is to use the build-helper-maven-plugin documented at $/generated-sources/castor Any ideas on how to fix this?) (TODO: For some reason if you Maven->Update Project Configuration for these projects, the build path gets reset and you have to re-add the castoror wsdl2java paths again. For jira-troubleticketer and opennms-integration-otrs you might need to add target/generated-sources/axistools/wsdl2java to the build path. Sometimes you can get "Unknown" validation errors in opennms-webapp. The XML will be re-validated and the Problem removed To clear them without rebuilding or nuking things, double click on the Problem to open the affected file, then right click on the editor and choose "Validate". It seems to be something like an inability to find the referenced XSDs or similar. Sometimes when starting up, some of the XML files will fail to validate and you'll get one or more "Problem"s appear, of type "XML Problem" with some horribly long and unhelpful description. On deleting those directories and files, reopening eclipse, validating and rebuilding the project, the problems went away. Performing an interrupting manual builds seems to have left a "classes" and "lib" directory, and a configuration.properties file, in opennms-webapp/src/main/webapp/WEB-INF/. (Mine said something about the lack of useDefaultDelimiters field/setter on a bean in the Maven plugin, but grep showed nothing so I think it was a side-effect of the real problem). (An example of this is features/remote-poller/pom.xml. Then in the added pluginManagement section change the ignore to execute to that m2eclipse will execute the action as part of an Eclipse workspace full or incremental build. You can use the quick-fix on the problem pom.xml to ignore the plugin error. Some projects might generate a Plugin execution not covered by lifecycle configuration within eclipse when they are added. Next check out the opennms code (for details, see Developing with Git):Git clone git://github.com/OpenNMS/opennms.git If you are developing on a newer version of OpenNMS, please see the previous section, "Current instructions." Speaking of current, do you really want to be developing with an old version of OpenNMS? There are newer stable and unstable branches available and we suggest you use them instead of old, unsupported code. The best way to get rid of these warnings is to place the lifecycle-mapping plugin management section inside a property activated profile.These instructions are for OpenNMS 1.6 and earlier. So you can add lifecycle-mapping for the 3 goals, execute, compile, and testCompile, and the errors in eclipse will go away.) One thing you will notice when you add this quick fix, is that your command line compiles will generate warnings due to these missing maven plugins. And select General->Existing Projects into Workspace and set the root directory to ~/rcs/opennms. (Note: eclipse does not accept the '~' character) Add a classpath variable called M2_REPO and set its value to /.m2/repository. Go to Window->Preferences and select Java->Build Path->Classpath Variables. Open eclipse and create a new workspace ![]()
0 Comments
Leave a Reply. |
AuthorKarlos ArchivesCategories |