[jbosstools-dev] Some questions about migrating to Java 8 and Mars

Brian Fitzpatrick bfitzpat at redhat.com
Fri Jul 24 09:13:44 EDT 2015


Thanks Nick!! The earlyaccess stuff is from Paul for JBTIS, so we'll have to chat with him about some of those changes. :)

Test failures I can deal with. :)

_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, Tooling
JBoss by Red Hat

----- Original Message -----
From: "Nick Boldt" <nboldt at redhat.com>
To: "Brian Fitzpatrick" <bfitzpat at redhat.com>, "Max Rydahl Andersen" <manderse at redhat.com>
Cc: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>
Sent: Thursday, July 23, 2015 6:28:03 PM
Subject: Re: [jbosstools-dev] Some questions about migrating to Java 8 and Mars

Build is yellow in Jenkins. Welcome to Mars!

You had it set to use RHEL5, Maven 3.1.1, JDK 1.7 and a tiny amount of 
memory (-Xmx256m). You're now using RHEL 6 or 7, Maven 3.2.5, JDK 1.8, 
and the usual memory settings (-Xms512m -Xmx1024m -XX:PermSize=128m 
-XX:MaxPermSize=256m).

Managed to get a few successful builds (but there are test failures, 
which is why it's yellow).

--

I've scrubbed the workspace to verify that we don't need to RESOLVE the 
target platform (that is, use -Pmultiple2repo to create a local TP 
site). All we should need is to build it and publish the .target into 
the local ~/.m2 repo. Even that step MIGHT be unnecessary but I like the 
idea of validating your TP as part of your build, at least until you 
adopt the JBTIS TP entirely and no longer need your own fork.

Here's a PR to move you from the ancient publish.sh to the new 
deploy-to-jboss.org profile / mojo.

https://github.com/jboss-switchyard/tools/pull/520

As a result you'll have all your CI builds pushed into a new location:

http://download.jboss.org/jbosstools/mars/snapshots/builds/switchyard-tools/

You'll also have a "latest update site" here:

http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-stack/switchyard-tools/

I also updated the job config to actually pass in valid values of the 
BUILD_TYPE variable into the mojo so that if you decide you want to 
build a development or stable build, you can set a different value and 
it'll push an update site into a folder other than /snapshots/updates/ 
-- rather you'll get /development/ or /stable/.

Not sure if you'd ever use the "earlyaccess" value -- that seems suspect 
to me. Maybe we should just remove that from the job and the site/pom.xml ?

Cheers,

Nick

On 07/23/2015 04:25 PM, Brian Fitzpatrick wrote:
> To add to the bizarreness, I just got an out of memory error even on Jenkins...
>
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/JBTIS/job/SwitchYard-Tools/570/console
>
> http://fpaste.org/247560/37683084/
>
> Paul or Nick, have you guys seen that before?
>
> _______________________________
> Brian Fitzpatrick (aka "Fitz")
> Senior Software Engineer, Tooling
> JBoss by Red Hat
>
> ----- Original Message -----
> From: "Brian Fitzpatrick" <bfitzpat at redhat.com>
> To: "Max Rydahl Andersen" <manderse at redhat.com>
> Cc: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>
> Sent: Thursday, July 23, 2015 7:41:49 AM
> Subject: Re: [jbosstools-dev] Some questions about migrating to Java 8 and Mars
>
> I just closed the tools, eclipse, and switchyard-tools-eclipse-plugins projects and now I'm not getting the out of memory errors.
>
> Is there something going on with "general" projects and the maven build in m2e I wonder?
>
> --Fitz
> _______________________________
> Brian Fitzpatrick (aka "Fitz")
> Senior Software Engineer, Tooling
> JBoss by Red Hat
>
> ----- Original Message -----
> From: "Brian Fitzpatrick" <bfitzpat at redhat.com>
> To: "Max Rydahl Andersen" <manderse at redhat.com>
> Cc: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>
> Sent: Thursday, July 23, 2015 7:30:10 AM
> Subject: Re: [jbosstools-dev] Some questions about migrating to Java 8 and Mars
>
> Sure Max, let me offer a few more details.
>
> Keep in mind this is on Windows. The 18 projects are the plugins projects (https://github.com/jboss-switchyard/tools/tree/master/eclipse) from SwitchYard along with the parent eclipse and top-level directories as general projects.
>
> Nothing I haven't done a hundred times before with Luna and Java 7.
>
> The projects are:
>
> tools
> eclipse
> org.switchyard.tools
> org.switchyard.tools.core
> org.switchyard.tools.cxf
> org.switchyard.tools.m2e
> org.switchyard.tools.models.sca.core
> org.switchyard.tools.models.sca.core.edit
> org.switchyard.tools.models.sca1_1
> org.switchyard.tools.models.sca1_1.edit
> org.switchyard.tools.models.switchyard1_0
> org.switchyard.tools.ui
> org.switchyard.tools.ui.bpel
> org.switchyard.tools.ui.bpmn2
> org.switchyard.tools.ui.debug
> org.switchyard.tools.ui.editor
> org.switchyard.tools.xsd
> switchyard-tools-eclipse-plugins
>
> I have created a PR with my Mars updates here - https://github.com/jboss-switchyard/tools/pull/518
>
> It consistently crashes in Eclipse Mars with m2e and this memory issue. But I have it building at the command line (without tests - mvn -U clean install -DskipTests) up to the point where it tries to assemble the site:
>
> [ERROR] Plugin org.jboss.tools.tycho-plugins:repository-utils:0.23.1 or one of its dependencies could not be resolved: Failure to find org.jboss.tools.tycho-plugins:repository-utils:jar:0.23.1 in http://maven.repository.redhat.com/techpreview/all/ was cached in the local repository, resolution will not be reattempted until the update interval of redhat-techpreview-all-repository has elapsed or updates are forced -> [Help 1]
>
> Nick - Is there a particular maven repo I need in my list to get tycho 0.23.1 to be happy?
>
> Hope this helps a little. Thanks for the help folks!
>
> --Fitz
> _______________________________
>
> Brian Fitzpatrick (aka "Fitz")
> Senior Software Engineer, Tooling
> JBoss by Red Hat
>
> ----- Original Message -----
> From: "Max Rydahl Andersen" <manderse at redhat.com>
> To: "Brian Fitzpatrick" <bfitzpat at redhat.com>
> Cc: "Fred Bricon" <fbricon at redhat.com>, "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>
> Sent: Thursday, July 23, 2015 3:40:34 AM
> Subject: Re: [jbosstools-dev] Some questions about migrating to Java 8 and Mars
>
> Brian,
>
> What does one need to do to reproduce this ?
>
> Which 18 projects are talking about here ?
> Maybe those 18 projects have some "magic" combination of custom maven
> plugins or
> some cyclic dependency that for some reason causes a regression in m2e ?
>
> I'm surprised since m2e actually seem to in general use much less memory
> in Mars for me.
>
> So lets get it reproduced on others to dig deeper.
>
> /max
>
>
>> I had the settings at the end after -vmargs, but had -Xms512m and
>> -XX:MaxMetaspaceSize=512m, which apparently it didn't like.
>>
>> This worked better:
>>
>> -Xms256m
>> -Xmx2048m
>> -XX:MaxMetaspaceSize=256m
>>
>> Now that I got that working I was able to re-import my projects (only
>> 18 projects in all in the entire workspace) and now I'm back to this:
>>
>> eclipse.buildId=4.5.0.I20150603-2000
>> java.version=1.8.0_45
>> java.vendor=Oracle Corporation
>> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
>> Framework arguments:  -product org.eclipse.epp.package.jee.product
>> Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product
>> org.eclipse.epp.package.jee.product
>>
>> org.eclipse.core.jobs
>> Error
>> Wed Jul 22 17:06:59 MDT 2015
>> An internal error occurred during: "Building workspace".
>>
>> java.lang.OutOfMemoryError: GC overhead limit exceeded
>> 	at java.util.HashMap.newNode(HashMap.java:1734)
>> 	at java.util.HashMap.putVal(HashMap.java:630)
>> 	at java.util.HashMap.put(HashMap.java:611)
>> 	at java.util.HashSet.add(HashSet.java:219)
>> 	at
>> org.apache.maven.model.io.xpp3.MavenXpp3ReaderEx.checkFieldWithDuplicate(MavenXpp3ReaderEx.java:114)
>> 	at
>> org.apache.maven.model.io.xpp3.MavenXpp3ReaderEx.parsePlugin(MavenXpp3ReaderEx.java:3039)
>> 	at
>> org.apache.maven.model.io.xpp3.MavenXpp3ReaderEx.parsePluginManagement(MavenXpp3ReaderEx.java:3362)
>> 	at
>> org.apache.maven.model.io.xpp3.MavenXpp3ReaderEx.parseBuild(MavenXpp3ReaderEx.java:977)
>> 	at
>> org.apache.maven.model.io.xpp3.MavenXpp3ReaderEx.parseModel(MavenXpp3ReaderEx.java:2512)
>> 	at
>> org.apache.maven.model.io.xpp3.MavenXpp3ReaderEx.read(MavenXpp3ReaderEx.java:4350)
>> 	at
>> org.apache.maven.model.io.xpp3.MavenXpp3ReaderEx.read(MavenXpp3ReaderEx.java:560)
>> 	at
>> org.apache.maven.model.io.DefaultModelReader.read(DefaultModelReader.java:121)
>> 	at
>> org.apache.maven.model.io.DefaultModelReader.read(DefaultModelReader.java:94)
>> 	at
>> org.apache.maven.model.building.DefaultModelProcessor.read(DefaultModelProcessor.java:81)
>> 	at
>> org.apache.maven.model.building.DefaultModelBuilder.readModel(DefaultModelBuilder.java:529)
>> 	at
>> org.apache.maven.model.building.DefaultModelBuilder.readParentExternally(DefaultModelBuilder.java:1023)
>> 	at
>> org.apache.maven.model.building.DefaultModelBuilder.readParent(DefaultModelBuilder.java:796)
>> 	at
>> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:325)
>> 	at
>> org.apache.maven.model.building.DefaultModelBuilder.importDependencyManagement(DefaultModelBuilder.java:1201)
>> 	at
>> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:451)
>> 	at
>> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:417)
>> 	at
>> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:407)
>> 	at
>> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:161)
>> 	at
>> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:119)
>> 	at
>> org.apache.maven.project.DefaultProjectBuilder.initProject(DefaultProjectBuilder.java:679)
>> 	at
>> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:176)
>> 	at
>> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:119)
>> 	at
>> org.apache.maven.project.DefaultProjectBuilder.initProject(DefaultProjectBuilder.java:679)
>> 	at
>> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:176)
>> 	at
>> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:119)
>> 	at
>> org.eclipse.m2e.core.internal.embedder.MavenImpl.readMavenProject(MavenImpl.java:636)
>> 	at
>> org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager$4.call(ProjectRegistryManager.java:704)
>>
>>
>> _______________________________
>> Brian Fitzpatrick (aka "Fitz")
>> Senior Software Engineer, Tooling
>> JBoss by Red Hat
>>
>> ----- Original Message -----
>> From: "Fred Bricon" <fbricon at redhat.com>
>> To: "Brian Fitzpatrick" <bfitzpat at redhat.com>
>> Cc: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>
>> Sent: Wednesday, July 22, 2015 5:03:49 PM
>> Subject: Re: [jbosstools-dev] Some questions about migrating to Java 8
>> and Mars
>>
>> check you put the vm settings after -vmargs
>> https://wiki.eclipse.org/FAQ_How_do_I_increase_the_heap_size_available_to_Eclipse%3F
>>
>>> Le 22 juil. 2015 à 19:00, Brian Fitzpatrick <bfitzpat at redhat.com> a
>>> écrit :
>>>
>>> Even better - I get "Error: Could not create the Java Virtual
>>> Machine. Error: A fatal exception has occurred. Program will exit."
>>>
>>> I think my settings are screwed up.
>>>
>>> _______________________________
>>> Brian Fitzpatrick (aka "Fitz")
>>> Senior Software Engineer, Tooling
>>> JBoss by Red Hat
>>>
>>> ----- Original Message -----
>>> From: "Fred Bricon" <fbricon at redhat.com>
>>> To: "Brian Fitzpatrick" <bfitzpat at redhat.com>
>>> Cc: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>
>>> Sent: Wednesday, July 22, 2015 4:59:16 PM
>>> Subject: Re: [jbosstools-dev] Some questions about migrating to Java
>>> 8 and Mars
>>>
>>> workspace corrupted by previous failure?
>>>
>>>> Le 22 juil. 2015 à 18:57, Brian Fitzpatrick <bfitzpat at redhat.com> a
>>>> écrit :
>>>>
>>>> Very interesting.
>>>>
>>>> Updating the ini file led to this:
>>>>
>>>> eclipse.buildId=4.5.0.I20150603-2000
>>>> java.version=1.8.0_45
>>>> java.vendor=Oracle Corporation
>>>> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
>>>> Framework arguments:  -product org.eclipse.epp.package.jee.product
>>>> Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product
>>>> org.eclipse.epp.package.jee.product
>>>>
>>>> org.eclipse.core.resources
>>>> Error
>>>> Wed Jul 22 16:50:53 MDT 2015
>>>> Could not read metadata for
>>>> 'C:/marsm5/workspace/.metadata/.plugins/org.eclipse.core.resources/.root/.markers'.
>>>>
>>>> java.io.IOException: Incompatible file format. Workspace was saved
>>>> with an incompatible version: 0.
>>>> 	at
>>>> org.eclipse.core.internal.resources.MarkerReader.getReader(MarkerReader.java:43)
>>>> 	at
>>>> org.eclipse.core.internal.resources.MarkerReader.read(MarkerReader.java:49)
>>>> 	at
>>>> org.eclipse.core.internal.resources.MarkerManager.restoreFromSave(MarkerManager.java:544)
>>>> 	at
>>>> org.eclipse.core.internal.resources.MarkerManager.restore(MarkerManager.java:529)
>>>> 	at
>>>> org.eclipse.core.internal.resources.SaveManager.restoreMarkers(SaveManager.java:826)
>>>> 	at
>>>> org.eclipse.core.internal.resources.SaveManager.restore(SaveManager.java:723)
>>>> 	at
>>>> org.eclipse.core.internal.resources.SaveManager.startup(SaveManager.java:1588)
>>>> 	at
>>>> org.eclipse.core.internal.resources.Workspace.startup(Workspace.java:2386)
>>>> 	at
>>>> org.eclipse.core.internal.resources.Workspace.open(Workspace.java:2157)
>>>> 	at
>>>> org.eclipse.core.resources.ResourcesPlugin.start(ResourcesPlugin.java:463)
>>>> 	at
>>>> org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:771)
>>>> 	at
>>>> org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
>>>> 	at java.security.AccessController.doPrivileged(Native Method)
>>>> 	at
>>>> org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:764)
>>>> 	at
>>>> org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:721)
>>>> 	at
>>>> org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:941)
>>>> 	at
>>>> org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:318)
>>>> 	at org.eclipse.osgi.container.Module.doStart(Module.java:571)
>>>> 	at org.eclipse.osgi.container.Module.start(Module.java:439)
>>>> 	at
>>>> org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:454)
>>>> 	at
>>>> org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
>>>> 	at
>>>> org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:531)
>>>> 	at
>>>> org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:324)
>>>> 	at
>>>> org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:327)
>>>> 	at
>>>> org.eclipse.osgi.internal.loader.sources.SingleSourcePackage.loadClass(SingleSourcePackage.java:36)
>>>> 	at
>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:398)
>>>> 	at
>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
>>>> 	at
>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
>>>> 	at
>>>> org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
>>>> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>>>> 	at
>>>> org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:140)
>>>> 	at
>>>> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
>>>> 	at
>>>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
>>>> 	at
>>>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
>>>> 	at
>>>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
>>>> 	at
>>>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
>>>> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> 	at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>>> 	at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>> 	at java.lang.reflect.Method.invoke(Method.java:497)
>>>> 	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
>>>> 	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
>>>> 	at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
>>>>
>>>> And this:
>>>>
>>>> eclipse.buildId=4.5.0.I20150603-2000
>>>> java.version=1.8.0_45
>>>> java.vendor=Oracle Corporation
>>>> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
>>>> Framework arguments:  -product org.eclipse.epp.package.jee.product
>>>> Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product
>>>> org.eclipse.epp.package.jee.product
>>>>
>>>> org.eclipse.e4.ui.workbench
>>>> Error
>>>> Wed Jul 22 16:50:54 MDT 2015
>>>> Unable to load resource
>>>> file:/C:/marsm5/workspace/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi
>>>>
>>>> org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException:
>>>> org.xml.sax.SAXParseExceptionpublicId:
>>>> file:/C:/marsm5/workspace/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi;
>>>> systemId:
>>>> file:/C:/marsm5/workspace/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi;
>>>> lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.
>>>> 	at
>>>> org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.handleDemandLoadException(ResourceSetImpl.java:319)
>>>> 	at
>>>> org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:278)
>>>> 	at
>>>> org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource(ResourceSetImpl.java:406)
>>>> 	at
>>>> org.eclipse.e4.ui.internal.workbench.ResourceHandler.getResource(ResourceHandler.java:351)
>>>> 	at
>>>> org.eclipse.e4.ui.internal.workbench.ResourceHandler.loadResource(ResourceHandler.java:327)
>>>> 	at
>>>> org.eclipse.e4.ui.internal.workbench.ResourceHandler.loadMostRecentModel(ResourceHandler.java:231)
>>>> 	at
>>>> org.eclipse.e4.ui.internal.workbench.swt.E4Application.loadApplicationModel(E4Application.java:397)
>>>> 	at
>>>> org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:254)
>>>> 	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:620)
>>>> 	at
>>>> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
>>>> 	at
>>>> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
>>>> 	at
>>>> org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
>>>> 	at
>>>> org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
>>>> 	at
>>>> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
>>>> 	at
>>>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
>>>> 	at
>>>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
>>>> 	at
>>>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
>>>> 	at
>>>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
>>>> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> 	at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>>> 	at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>> 	at java.lang.reflect.Method.invoke(Method.java:497)
>>>> 	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
>>>> 	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
>>>> 	at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
>>>> Caused by: org.xml.sax.SAXParseExceptionpublicId:
>>>> file:/C:/marsm5/workspace/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi;
>>>> systemId:
>>>> file:/C:/marsm5/workspace/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi;
>>>> lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.
>>>> 	at
>>>> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
>>>> 	at
>>>> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)
>>>> 	at
>>>> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:441)
>>>> 	at
>>>> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:368)
>>>> 	at
>>>> com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1436)
>>>> 	at
>>>> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:999)
>>>> 	at
>>>> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
>>>> 	at
>>>> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:117)
>>>> 	at
>>>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
>>>> 	at
>>>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)
>>>> 	at
>>>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
>>>> 	at
>>>> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
>>>> 	at
>>>> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
>>>> 	at
>>>> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:649)
>>>> 	at
>>>> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:333)
>>>> 	at
>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:175)
>>>> 	at
>>>> org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourceImpl.java:261)
>>>> 	at
>>>> org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1518)
>>>> 	at
>>>> org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1297)
>>>> 	at
>>>> org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoad(ResourceSetImpl.java:259)
>>>> 	at
>>>> org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:274)
>>>> 	... 23 more
>>>>
>>>> And ultimately this:
>>>>
>>>> eclipse.buildId=4.5.0.I20150603-2000
>>>> java.version=1.8.0_45
>>>> java.vendor=Oracle Corporation
>>>> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
>>>> Framework arguments:  -product org.eclipse.epp.package.jee.product
>>>> Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product
>>>> org.eclipse.epp.package.jee.product
>>>>
>>>> org.eclipse.e4.ui.workbench
>>>> Error
>>>> Wed Jul 22 16:50:54 MDT 2015
>>>> The persisted workbench has no top-level windows, so reinitializing
>>>> with defaults.
>>>>
>>>> java.lang.Exception
>>>> 	at
>>>> org.eclipse.e4.ui.internal.workbench.ResourceHandler.loadMostRecentModel(ResourceHandler.java:236)
>>>> 	at
>>>> org.eclipse.e4.ui.internal.workbench.swt.E4Application.loadApplicationModel(E4Application.java:397)
>>>> 	at
>>>> org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:254)
>>>> 	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:620)
>>>> 	at
>>>> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
>>>> 	at
>>>> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
>>>> 	at
>>>> org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
>>>> 	at
>>>> org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
>>>> 	at
>>>> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
>>>> 	at
>>>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
>>>> 	at
>>>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
>>>> 	at
>>>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
>>>> 	at
>>>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
>>>> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> 	at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>>> 	at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>> 	at java.lang.reflect.Method.invoke(Method.java:497)
>>>> 	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
>>>> 	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
>>>> 	at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
>>>>
>>>>
>>>> Guess I'll be re-importing my projects...
>>>>
>>>> _______________________________
>>>> Brian Fitzpatrick (aka "Fitz")
>>>> Senior Software Engineer, Tooling
>>>> JBoss by Red Hat
>>>>
>>>> ----- Original Message -----
>>>> From: "Fred Bricon" <fbricon at redhat.com>
>>>> To: "Brian Fitzpatrick" <bfitzpat at redhat.com>
>>>> Cc: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>
>>>> Sent: Wednesday, July 22, 2015 4:45:17 PM
>>>> Subject: Re: [jbosstools-dev] Some questions about migrating to Java
>>>> 8 and Mars
>>>>
>>>> How many projects open in your workspace?
>>>> have you tried -Xmx2048m in eclipse.ini?
>>>>
>>>>> Le 22 juil. 2015 à 18:30, Brian Fitzpatrick <bfitzpat at redhat.com>
>>>>> a écrit :
>>>>>
>>>>> Hey folks,
>>>>>
>>>>> I'm starting to move the SwitchYard editor to Java 8 and Eclipse
>>>>> Mars. The biggest thing is I'm hitting some issues when building in
>>>>> Eclipse using the m2e code (Maven->Update Project). Specifically,
>>>>> I'm seeing "An internal error occurred during: "Updating Maven
>>>>> Project".
>>>>> GC overhead limit exceeded"
>>>>>
>>>>> I've tried updating the -XX:MaxPermSize=256m to
>>>>> -XX:MaxMetaspaceSize=256m per the suggestions here
>>>>> (https://dzone.com/articles/java-8-permgen-metaspace) but it hasn't
>>>>> made any difference.
>>>>>
>>>>> Nick suggested updating the build to use Tycho 0.23.1, but that
>>>>> hasn't made a difference.
>>>>>
>>>>> Anybody have any suggestions on what to try?
>>>>>
>>>>> Thanks
>>>>> --Fitz
>>>>>
>>>>> _______________________________
>>>>> Brian Fitzpatrick (aka "Fitz")
>>>>> Senior Software Engineer, Tooling
>>>>> JBoss by Red Hat
>>>>>
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>>
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /max
> http://about.me/maxandersen
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com



More information about the jbosstools-dev mailing list