[JBoss JIRA] (JBIDE-13906) JBoss EAP developer studio - Issue while adding custom capability
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13906?page=com.atlassian.jira.plugi... ]
Vlado Pakan reassigned JBIDE-13906:
-----------------------------------
Assignee: Vlado Pakan
> JBoss EAP developer studio - Issue while adding custom capability
> -----------------------------------------------------------------
>
> Key: JBIDE-13906
> URL: https://issues.jboss.org/browse/JBIDE-13906
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JSF
> Affects Versions: 4.0.0.Final
> Reporter: Vlado Pakan
> Assignee: Vlado Pakan
> Fix For: 4.1.0.Alpha2
>
>
> From the linked bugzilla:
> {quote}
> Description of problem:
> I am evaluating JBoss EAP and developer studio. Created an enterprise application and wanted to add richface capability to the web app.
> Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid".
> This happened to me twice and I had to create a new workspace and reconfigure everything from scratch.
> Version-Release number of selected component (if applicable):6.0.0
> How reproducible:
> Create an enterprise application and wanted to add richface capability to the web app.
> Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid".
> Steps to Reproduce:
> Created an enterprise application and wanted to add richface capability to the web app.
> Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid".
>
> Actual results:
> There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid".
> {quote}
--
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
13 years
[JBoss JIRA] (JBIDE-13906) JBoss EAP developer studio - Issue while adding custom capability
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13906?page=com.atlassian.jira.plugi... ]
Vlado Pakan updated JBIDE-13906:
--------------------------------
Fix Version/s: (was: 4.0.1.Final)
> JBoss EAP developer studio - Issue while adding custom capability
> -----------------------------------------------------------------
>
> Key: JBIDE-13906
> URL: https://issues.jboss.org/browse/JBIDE-13906
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JSF
> Affects Versions: 4.0.0.Final
> Reporter: Vlado Pakan
> Fix For: 4.1.0.Alpha2
>
>
> From the linked bugzilla:
> {quote}
> Description of problem:
> I am evaluating JBoss EAP and developer studio. Created an enterprise application and wanted to add richface capability to the web app.
> Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid".
> This happened to me twice and I had to create a new workspace and reconfigure everything from scratch.
> Version-Release number of selected component (if applicable):6.0.0
> How reproducible:
> Create an enterprise application and wanted to add richface capability to the web app.
> Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid".
> Steps to Reproduce:
> Created an enterprise application and wanted to add richface capability to the web app.
> Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid".
>
> Actual results:
> There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid".
> {quote}
--
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
13 years
[JBoss JIRA] (JBDS-2503) JBoss EAP developer studio - Issue while adding custom capability
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBDS-2503?page=com.atlassian.jira.plugin.... ]
Vlado Pakan closed JBDS-2503.
-----------------------------
Verified with JBDS 6.0.1.GA-v20130327-2052-B361
> JBoss EAP developer studio - Issue while adding custom capability
> -----------------------------------------------------------------
>
> Key: JBDS-2503
> URL: https://issues.jboss.org/browse/JBDS-2503
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jsf
> Affects Versions: 6.0.0.GA
> Environment: Windows
> Reporter: Chandrashekhar Tupe
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 6.0.1.GA, 7.0.0.Alpha2
>
> Attachments: logfile.txt
>
>
> I am evaluating JBoss EAP and developer studio. Created an enterprise application and wanted to add richface capability to the web app.
> Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid".
> This happened to me twice and I had to create a new workspace and reconfigure everything from scratch.
--
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
13 years
[JBoss JIRA] (JBIDE-13903) EAP 6.1 cannot start
by John Graham (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13903?page=com.atlassian.jira.plugi... ]
John Graham commented on JBIDE-13903:
-------------------------------------
I downloaded EAP 6.1 alpha separately from JBT. Configured JBT to point at that folder, and it seemed OK.
> EAP 6.1 cannot start
> --------------------
>
> Key: JBIDE-13903
> URL: https://issues.jboss.org/browse/JBIDE-13903
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.1.0.Alpha1
> Environment: F18, EAP 6.1 alpha
> Reporter: John Graham
> Assignee: Rob Stryker
> Priority: Critical
> Attachments: .log
>
>
> Create a EAP 6.1 server definition. Select "start" in the server view. The server view reports that EAP has started, when it hasn't. Log attached.
--
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
13 years
[JBoss JIRA] (JBIDE-13854) intermittent install-grinder test failures caused by SIGSEGV
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13854?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-13854:
----------------------------------------
We usually run jobs on slaves prefixed with dev* or vmg* (RHEL 5 or 6, x86 or x86_64) without any problem. I know that this prefix has a real meaning (dev is a real machine, vmg is a VM...). Most likely "dsp" machines have something different that cause this issue.
I'll ask Vojtech on this topic.
> intermittent install-grinder test failures caused by SIGSEGV
> ------------------------------------------------------------
>
> Key: JBIDE-13854
> URL: https://issues.jboss.org/browse/JBIDE-13854
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Mickael Istria
>
> When run on https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dsp06-rhel5-x86..., this build failed:
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.install-tests.matrix/INSTALL_PLAN=http%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fupdates%2Fdevelopment%2F6.0.1.CR1a.core%3Bhttp%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fupdates%2Fdevelopment%2F6.0.1.CR1a.core%2Fdevstudio-directory.xml,eclipseBundleVersion=juno.R,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/92/console}
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -application org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplication -testApplication org.eclipse.ui.ide.workbench -product org.eclipse.epp.package.jee.product formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,TEST-install-2013032310-1006.xml formatter=org.apache.tools.ant.taskdefs.optional.junit.PlainJUnitResultFormatter -testPluginName org.jboss.tools.tests.installation -className org.jboss.tools.tests.installation.InstallFromCentralTest
> Command-line arguments: -application org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplication -testApplication org.eclipse.ui.ide.workbench -product org.eclipse.epp.package.jee.product -data workspace formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,TEST-install-2013032310-1006.xml formatter=org.apache.tools.ant.taskdefs.optional.junit.PlainJUnitResultFormatter -testPluginName org.jboss.tools.tests.installation -className org.jboss.tools.tests.installation.InstallFromCentralTest -consoleLog -debug
> !ENTRY org.eclipse.osgi 2 1 2013-03-23 10:07:15.646
> !MESSAGE NLS missing message: JBossRuntimeStartup_JBoss_EAP_Server_6_1 in: org.jboss.ide.eclipse.as.core.Messages
> Testsuite: org.jboss.tools.tests.installation.InstallFromCentralTest
> Application Started: 24573
> log4j:WARN No appenders could be found for logger (org.eclipse.swtbot.swt.finder.matchers.AbstractMatcher).
> log4j:WARN Please initialize the log4j system properly.
> !ENTRY org.eclipse.ui.browser 2 0 2013-03-23 10:07:23.217
> !MESSAGE Internal browser is not available: XPCOM error 0x80004003
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x0000003420c08b9b, pid=17450, tid=1076410688
> #
> # JRE version: 6.0_43-b01
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.14-b01 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C [ld-linux-x86-64.so.2+0x8b9b]
> #
> # An error report file with more information is saved as:
> # /qa/local/hudson_workspace/workspace/jbosstools-4.0_stable_branch.install-tests.matrix/cdf6d04c/eclipse/hs_err_pid17450.log
> #
> # If you would like to submit a bug report, please visit:
> # http://java.sun.com/webapps/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> {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
13 years
[JBoss JIRA] (JBDS-2505) JBDS 6.0.1 is based on Juno SR0 instead of SR2
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBDS-2505?page=com.atlassian.jira.plugin.... ]
Jiri Peterka closed JBDS-2505.
------------------------------
Verified in JBDS 6.0.1.CR1b, L64, Note: eclipse platform feature is in version 4.2.1, plugin 4.2.2
> JBDS 6.0.1 is based on Juno SR0 instead of SR2
> ----------------------------------------------
>
> Key: JBDS-2505
> URL: https://issues.jboss.org/browse/JBDS-2505
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build
> Affects Versions: 6.0.1.GA
> Environment: JBDS 6.0.1.CR1a B354
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: respin-b
> Fix For: 6.0.1.GA
>
>
> JBDS 6.0.1.CR1a B354 is based on Eclipse Juno SR0, but should be Juno SR2.
> I know about the recent issue where TP wasn't updated to 4.22.2, so I would expect something 4.22.1 (still Juno SR2). But in fact it is SR0.
> My assumption is that while JBDS BYOE can be installed on the minimal version of Eclipse, the JBDS installer should contain the maximum TP. I hope I'm not wrong here.
> Now I also checked the previous build - JBDS 6.0.1.CR1 B338 and that is based on Eclipse Juno 4.2.1.
--
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
13 years
[JBoss JIRA] (JBIDE-13899) Update Server tests to support latest EAP 6.0.x and 6.1.0.x
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13899?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-13899.
---------------------------------
Fix Version/s: 4.1.0.Alpha2
Resolution: Done
Pushed to master.
> Update Server tests to support latest EAP 6.0.x and 6.1.0.x
> -----------------------------------------------------------
>
> Key: JBIDE-13899
> URL: https://issues.jboss.org/browse/JBIDE-13899
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, JBossAS/Servers
> Affects Versions: 4.0.2.Final, 4.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.1.0.Alpha2
>
>
> Found test classes which refer to JBEAP 6.0 and/or 6.1. They should be updated to refer to the latest 6.0.x AND new 6.1.0.x bits, so both are available for testing.
> {code:title=contains ref to only 6.0. Should it contain 6.1 too?}
> jbosstools-integration-tests/tests/org.jboss.ide.eclipse.as.ui.bot.test/pom.xml
> jbosstools-integration-tests/tests/org.jboss.tools.central.test.ui.bot/pom.xml{code}
> {code:title=contains refs to both 6.0 and 6.1}
> jbosstools-server/as/tests/org.jboss.tools.as.test.core/pom.xml{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
13 years
[JBoss JIRA] (JBIDE-13905) portlet-api library of JPP 6 is not imported
by Petr Suchý (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13905?page=com.atlassian.jira.plugi... ]
Petr Suchý reassigned JBIDE-13905:
----------------------------------
Assignee: Snjezana Peco (was: Peter Palaga)
> portlet-api library of JPP 6 is not imported
> --------------------------------------------
>
> Key: JBIDE-13905
> URL: https://issues.jboss.org/browse/JBIDE-13905
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Portal/GateIn
> Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
> Reporter: Petr Suchý
> Assignee: Snjezana Peco
> Fix For: 4.1.x
>
>
> When you want to create Dynamic Web Project using JPP 6.0.0.GA, you cannot simply choose Portlet implementation library as a Portlet Target Runtime Provider in a New Dynamic Web Project Wizard. You are forced to add _portlet-api.jar_ manually from here:
> {code}
> ${JPP6}/modules/javax/portlet/api/main/
> {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
13 years