[JBoss JIRA] (JBIDE-16137) webservices component build slow during tests
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16137?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick updated JBIDE-16137:
--------------------------------------
Summary: webservices component build slow during tests (was: webservices component build slow during tests on Luna TP)
> webservices component build slow during tests
> ---------------------------------------------
>
> Key: JBIDE-16137
> URL: https://issues.jboss.org/browse/JBIDE-16137
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, webservices
> Affects Versions: 4.2.0.Alpha1
> Environment: Luna 4.4 M3 TP
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Attachments: jstack-43357.txt
>
>
> when reaching the tests on org.jboss.tools.ws.creation.core.tests, a workbench window appears but nothing is drawn and the build is *very* slow
> {code}
> [INFO] Command line:
> /bin/sh -c cd /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test && /Library/Java/JavaVirtualMachines/jdk1.7.0_12.jdk/Contents/Home/jre/bin/java -Dosgi.noShutdown=false -Dosgi.os=macosx -Dosgi.ws=cocoa -Dosgi.arch=x86_64 '-javaagent:/Users/xcoulon/.m2/repository/org/jacoco/org.jacoco.agent/0.6.1.201212231917/org.jacoco.agent-0.6.1.201212231917-runtime.jar=destfile=/Users/xcoulon/code/jbosstools/jbosstools-webservices/target/jacoco.exec,append=true,includes=org.jboss.tools.ws.creation.core*' -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=256m -XstartOnFirstThread '-Djbosstools.test.jre.6=${jbosstools.test.jre.6}' '-Djbosstools.test.jre.5=${jbosstools.test.jre.5}' -Djbosstools.test.jboss.home.4.2=/Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/requirements/jboss-4.2.3.GA -Dusage_reporting_enabled=false -Dorg.jboss.tools.tests.skipPrivateRequirements=true -Dorg.eclipse.ui.testsDisableWorkbenchAutoSave=true -Dosgi.clean=true -jar /Users/xcoulon/.m2/repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.3.0.v20130327-1440/org.eclipse.equinox.launcher-1.3.0.v20130327-1440.jar -data /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/data -install /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work -configuration /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/configuration -application org.eclipse.tycho.surefire.osgibooter.uitest -testproperties /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/surefire.properties
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16137) webservices component build slow during tests
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16137?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-16137:
-------------------------------------------
Obviously not just OSX...
> webservices component build slow during tests
> ---------------------------------------------
>
> Key: JBIDE-16137
> URL: https://issues.jboss.org/browse/JBIDE-16137
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, webservices
> Affects Versions: 4.2.0.Alpha1
> Environment: Luna 4.4 M3 TP
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Attachments: jstack-43357.txt
>
>
> when reaching the tests on org.jboss.tools.ws.creation.core.tests, a workbench window appears but nothing is drawn and the build is *very* slow
> {code}
> [INFO] Command line:
> /bin/sh -c cd /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test && /Library/Java/JavaVirtualMachines/jdk1.7.0_12.jdk/Contents/Home/jre/bin/java -Dosgi.noShutdown=false -Dosgi.os=macosx -Dosgi.ws=cocoa -Dosgi.arch=x86_64 '-javaagent:/Users/xcoulon/.m2/repository/org/jacoco/org.jacoco.agent/0.6.1.201212231917/org.jacoco.agent-0.6.1.201212231917-runtime.jar=destfile=/Users/xcoulon/code/jbosstools/jbosstools-webservices/target/jacoco.exec,append=true,includes=org.jboss.tools.ws.creation.core*' -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=256m -XstartOnFirstThread '-Djbosstools.test.jre.6=${jbosstools.test.jre.6}' '-Djbosstools.test.jre.5=${jbosstools.test.jre.5}' -Djbosstools.test.jboss.home.4.2=/Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/requirements/jboss-4.2.3.GA -Dusage_reporting_enabled=false -Dorg.jboss.tools.tests.skipPrivateRequirements=true -Dorg.eclipse.ui.testsDisableWorkbenchAutoSave=true -Dosgi.clean=true -jar /Users/xcoulon/.m2/repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.3.0.v20130327-1440/org.eclipse.equinox.launcher-1.3.0.v20130327-1440.jar -data /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/data -install /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work -configuration /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/configuration -application org.eclipse.tycho.surefire.osgibooter.uitest -testproperties /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/surefire.properties
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-15250) Explode utility jars in EAR/WAR deployments
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15250?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-15250:
--------------------------------
Assignee: Rob Stryker
Fix Version/s: 4.2.0.Alpha2
(was: 4.2.0.Alpha1)
> Explode utility jars in EAR/WAR deployments
> -------------------------------------------
>
> Key: JBIDE-15250
> URL: https://issues.jboss.org/browse/JBIDE-15250
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.0.1.Final
> Reporter: Kevin Formsma
> Assignee: Rob Stryker
> Fix For: 4.2.0.Alpha2
>
>
> For larger projects that utilize utility jars within the EAR, it would be nice to have these deployed exploded as well. This would allow hot code replacement for those utility projects.
> A current work around is to make the utility projects modules so that the tooling treats them as a EJB module and deploys them exploded.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-15671) WildFly / EAP domain mode management UI
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15671?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-15671:
--------------------------------
Fix Version/s: 4.2.0.Alpha2
(was: 4.2.0.Alpha1)
> WildFly / EAP domain mode management UI
> ---------------------------------------
>
> Key: JBIDE-15671
> URL: https://issues.jboss.org/browse/JBIDE-15671
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Reporter: Ondrej Zizka
> Assignee: Rob Stryker
> Fix For: 4.2.0.Alpha2
>
> Attachments: domainmodeinitialmockup.bmml, domainmodeinitialmockup.png
>
>
> Max brought the topic of Domain mode management UI.
> The domain mode needs a special treatment.
> Logically it's a matrix, and calls for a matrix-like UI instead of a tree.
> The structure would be similar to the pictures of domain mode in tutorials (TBD: link).
> An inspiration may be taken from AS web console.
> As a preliminary solution, a tree may be used, in which case it may omit host controllers which do not play much role in domain mode management, from the admin PoV.
> The nodes would represent server groups, and their leaves would represent particular servers (JVMs).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-15635) Null Pointer when code assumes runtime type cannot be null
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15635?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-15635:
--------------------------------
Fix Version/s: 4.2.0.Alpha2
(was: 4.2.0.Alpha1)
> Null Pointer when code assumes runtime type cannot be null
> ----------------------------------------------------------
>
> Key: JBIDE-15635
> URL: https://issues.jboss.org/browse/JBIDE-15635
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Environment: Mac OSX 10.8.5
> Oracle JDK 1.7.0_40
> JBoss Developer Studio
> Version: 7.0.1.GA
> Build id: GA-v20130930-2238-B7
> Build date: 20130930-2238
> Reporter: Cojan van Ballegooijen
> Assignee: Rob Stryker
> Fix For: 4.2.0.Alpha2
>
> Attachments: jbosstools-diagnostics-20131008232745.zip, Screen Shot 2013-10-08 at 2.22.05 PM.png
>
>
> - Installed JBoss Developer 7.0.0GA using
> - Upgraded to 7.0.1GA
> - Starting JBoss Developer Studio shows the following error window
> An internal error occurred during: "Refreshing JBoss Tutorials...".
> java.lang.NullPointerException
> - The error mentioned before also occurs when doing a refresh inside JBoss Central in the Start from a sample "portlet"
> - Starting a new Java EE Web project results in the following error
> An error has occurred. See error log for more details.
> java.lang.NullPointerException
> No error log is created in ~/workspace, tried to find *.log file in JBoss Developer Studio installation directory, no log files.
> Found .log in ~/workspace/.metadata
> !SESSION 2013-10-08 16:14:47.792 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.7.0_40
> java.vendor=Oracle Corporation
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
> Framework arguments: -product com.jboss.jbds.product.product -keyring /Users/cballego/.eclipse_keyring -showlocation
> Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.jbds.product.product -keyring /Users/cballego/.eclipse_keyring -consoleLog -showlocation
> !ENTRY org.eclipse.core.net 1 0 2013-10-08 16:14:52.252
> !MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences
> !ENTRY org.eclipse.jface 2 0 2013-10-08 16:14:52.626
> !MESSAGE Keybinding conflicts occurred. They may interfere with normal accelerator operation.
> !SUBENTRY 1 org.eclipse.jface 2 0 2013-10-08 16:14:52.626
> !MESSAGE A conflict occurred for ALT+COMMAND+Z:
> Binding(ALT+COMMAND+Z,
> ParameterizedCommand(Command(org.jboss.tools.cdi.ui.open.namedBean,Open CDI Named Bean,
> Open CDI Named Bean,
> Category(org.eclipse.ui.category.navigate,Navigate,null,true),
> org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@54158353,
> ,,true),null),
> org.eclipse.ui.defaultAcceleratorConfiguration,
> org.eclipse.ui.contexts.window,,,system)
> Binding(ALT+COMMAND+Z,
> ParameterizedCommand(Command(org.eclipse.jdt.ui.edit.text.java.surround.with.quickMenu,Surround With Quick Menu,
> Shows the Surround With quick menu,
> Category(org.eclipse.jdt.ui.category.source,Source,Java Source Actions,true),
> org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@5060e945,
> ,,true),null),
> org.eclipse.ui.defaultAcceleratorConfiguration,
> org.eclipse.ui.contexts.window,,cocoa,system)
> !SUBENTRY 1 org.eclipse.jface 2 0 2013-10-08 16:14:52.626
> !MESSAGE A conflict occurred for COMMAND+SHIFT+F10:
> Binding(COMMAND+SHIFT+F10,
> ParameterizedCommand(Command(org.jboss.tools.common.ui.RegisterAsService,Register As Service,
> Adds class name to META-INF/services/%serviceType% file after service type is selected in the dialog from types extended and implemented by the class.,
> Category(org.eclipse.ui.category.file,File,null,true),
> org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@a72da3d,
> ,,true),null),
> org.eclipse.ui.defaultAcceleratorConfiguration,
> org.eclipse.ui.contexts.window,,,system)
> Binding(COMMAND+SHIFT+F10,
> ParameterizedCommand(Command(org.eclipse.ui.window.showSystemMenu,Show System Menu,
> Show the system menu,
> Category(org.eclipse.ui.category.window,Window,null,true),
> org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@7a55e026,
> ,,true),null),
> org.eclipse.ui.defaultAcceleratorConfiguration,
> org.eclipse.ui.contexts.window,,cocoa,system)
> !ENTRY org.eclipse.core.jobs 4 2 2013-10-08 16:15:04.413
> !MESSAGE An internal error occurred during: "Refreshing JBoss Tutorials...".
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:158)
> at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:151)
> at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getRuntimesFromPattern(WTPRuntimeFix.java:102)
> at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getBestRuntime(WTPRuntimeFix.java:248)
> at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.canFix(WTPRuntimeFix.java:130)
> at org.jboss.tools.project.examples.ProjectExamplesActivator.canFix(ProjectExamplesActivator.java:796)
> at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:68)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16231) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Server]
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16231?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-16231:
--------------------------------
Fix Version/s: 4.2.0.Alpha2
(was: 4.2.0.Alpha1)
> For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Server]
> -----------------------------------------------------
>
> Key: JBIDE-16231
> URL: https://issues.jboss.org/browse/JBIDE-16231
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Alpha2
>
>
> For JBIDE 4.2.0.Alpha1 [Server]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.2.0.Alpha1x
> git push origin jbosstools-4.2.0.Alpha1x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months