[JBoss JIRA] Created: (JBIDE-3191) Cannot run tests when building JMX by itself
by Nick Boldt (JIRA)
Cannot run tests when building JMX by itself
--------------------------------------------
Key: JBIDE-3191
URL: https://jira.jboss.org/jira/browse/JBIDE-3191
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng
Affects Versions: 3.0.0.beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.0.0.cr1
Using /devstudio-trunk/releng/org.jboss.ide.eclipse.releng/hudson/build.sh with the following parameters changed, JMX will build on its own:
builders=jmx
nightlyBuildSteps=standalone.product,reports,build-results,update-site
Turning tests back on, however, the build fails:
builders=jmx
nightlyBuildSteps=standalone.product,reports,tests,build-results,update-site
[java] Java Result: 13
[echo]
[echo] The builder <b>tests</b> failed to compile with the following results:<br/><br/>
[echo]
[echo] <pre>
[echo] BUILD FAILED
[echo] /opt/public/jbt-jbds/nightly-with-tests/jbds-build/clean-eclipse/eclipse/plugins/org.eclipse.pde.build_3.4.1.R34x_v20080805/scripts/build.xml:24: The following error occurred while executing this line:
[echo] /opt/public/jbt-jbds/nightly-with-tests/jbds-build/clean-eclipse/eclipse/plugins/org.eclipse.pde.build_3.4.1.R34x_v20080805/scripts/build.xml:64: The following error occurred while executing this line:
[echo] /opt/public/jbt-jbds/nightly-with-tests/org.jboss.ide.eclipse.releng/builders/tests/customTargets.xml:13: The following error occurred while executing this line:
[echo] /opt/public/jbt-jbds/nightly-with-tests/jbds-build/clean-eclipse/eclipse/plugins/org.eclipse.pde.build_3.4.1.R34x_v20080805/scripts/genericTargets.xml:88: Bundle org.jboss.tools.common.kb.test_0.0.0 failed to resolve.:
[echo] Missing required plug-in org.jboss.tools.common_0.0.0.
[echo] Missing required plug-in org.jboss.tools.common.kb_0.0.0.
[echo] Missing required plug-in org.jboss.tools.common.test_0.0.0.
[echo] Missing required plug-in org.jboss.tools.common.projecttemplates_0.0.0.
[echo]
[echo]
[echo] Total time: 3 minutes 2 seconds
[echo] </pre>
[echo] /opt/public/jbt-jbds/nightly-with-tests/jbds-build/3.0.0.CR1/200811132054/tests
BUILD FAILED
/home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/buildNightly.xml:12: The following error occurred while executing this line:
/home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/build.xml:56: The following error occurred while executing this line:
/home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/build.xml:27: The following error occurred while executing this line:
/home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/build.xml:37: The following error occurred while executing this line:
/home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/product/productBuild.xml:76: The following error occurred while executing this line:
/home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/product/productBuild.xml:105: The following error occurred while executing this line:
/home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/product/productBuild.xml:261: Specify at least one source - a file or a resource collection.
Total time: 23 minutes 21 seconds
I suspect this is a result of the tests being coupled together, such that they depend on the whole build (builders=jmx,examples,drools-ide,archives,richfaces,jbpm-convert,freemarker,hibernate-tools,struts,jbpm,as,seam,esb,ws,birt,portlet,smooks) and its output.
Would there be value in incrementally splitting each build's tests out so they can run independently? eg.,
builders=jmx,jmx-tests
nightlyBuildSteps=standalone.product,reports,tests-jmx,build-results,update-site
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBIDE-4971) Deploying BIRT aaplication to JBoss AS 5.x
by Snjezana Peco (JIRA)
Deploying BIRT aaplication to JBoss AS 5.x
------------------------------------------
Key: JBIDE-4971
URL: https://jira.jboss.org/jira/browse/JBIDE-4971
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: birt, JBossAS
Affects Versions: 3.1.0.M3
Reporter: Snjezana Peco
Assignee: Snjezana Peco
Steps to reproduce
- download testbirt.zip project from https://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/seam-examples... (56MB)
- configure Seam 2.2.0 and a JBoss Runtime
- deploy to JBoss AS server
- call the "Test Birt" link
JBoss AS 4.2.3
- works correctly
JBoss AS 5.1.0 GA
- doesn't work due to the problem described on http://www.jboss.org/index.html?module=bb&op=viewtopic&t=156898
JBoss EAP 5.0
You will often get warnings (eap5log1.txt)
When calling the "Test Birt" action, you will get either eap5log2.txt or eap5log3.txt.
The problem isn't always reproducible. Sometimes it doesn't happen, but rarely.
The problem happens due to the way in which JBoss AS 5 initializes the application. BIRT uses org.eclipse.birt.report.listener.ViewerServletContextListener to initialize the BIRT engine (OSGi) when starting the application. If this listener is commented/removed, the problem won't happen. If the BIRT engine hasn't been already initialized, it will be initialized when starting a BIRT servlet so that this listener isn't obliged. Maybe this is even better because the BIRT engine is initialized only when it is called. For now, we can use this as a workaround. However, it seems that there is a problem when the JBoss AS server initializes the application.
Another problem is that JBoss AS aggressively logs a warning about missing classes in BIRT internal jars (WEB-INF/platform/plugins/*.jar) when adding a new *xhtml file to the application. This can be solved by adding a line to <JBOSSAS_HOME/server/default/conf/bootstrap/profile.xml:
...
<bean name="WebVisitorAttributes" class="org.jboss.system.server.profile.basic.IncludeExcludeVisitorAttributes">
<constructor>
<parameter>
<set>
<value>.war</value>
</set>
</parameter>
<parameter>
<set>
<value>WEB-INF/classes</value>
<value>WEB-INF/lib</value>
<value>WEB-INF/platform</value> <!-- BIRT workaround -->
</set>
</parameter>
</constructor>
</bean>
...
The workaround isn't applicable to JBoss AS 5.1.0.GA.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBIDE-910) Servlet Generator for Dynamic Web Project is creating errornous web.xml files
by Steve Davidson (JIRA)
Servlet Generator for Dynamic Web Project is creating errornous web.xml files
-----------------------------------------------------------------------------
Key: JBIDE-910
URL: http://jira.jboss.com/jira/browse/JBIDE-910
Project: JBoss Tools
Issue Type: Bug
Components: JBoss Tools Core
Affects Versions: 2.0.0.Beta3
Environment: Windows XP Professionial SP2
Reporter: Steve Davidson
When creating a Servlet using the New File - Servlet wizard in a Dynamic Web Project in a clean workspace, the web.xml file is not properly created. Specifically, this is what gets generated;
<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<display-name>
DemoFlaw</display-name>
<servlet>
<description>
</description>
<display-name>
DemoServlet</display-name>
<servlet-name>DemoServlet</servlet-name>
<servlet-class>
org.ccccd.webone.DemoServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>DemoServlet</servlet-name>
<url-pattern>/DemoServlet</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>index.html</welcome-file>
<welcome-file>index.htm</welcome-file>
<welcome-file>index.jsp</welcome-file>
<welcome-file>default.html</welcome-file>
<welcome-file>default.htm</welcome-file>
<welcome-file>default.jsp</welcome-file>
</welcome-file-list>
</web-app>
The extra whitespace at the end of the start tag <servlet-class> causes the deployment to fail. This is occuring on 100% of the computers in the Java Web Class that I am teaching.
-Steve
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBIDE-2726) Incorrect behavior of Server properties > Ports Monitoring
by Aliaksey Nis (JIRA)
Incorrect behavior of Server properties > Ports Monitoring
----------------------------------------------------------
Key: JBIDE-2726
URL: https://jira.jboss.org/jira/browse/JBIDE-2726
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.alpha
Environment: WindowsXP SP2
JBoss Tools
Version: 3.0.0.Alpha1
Build id: 200809010011-nightly
Build date: 01 september 2008
JDK 1.5_08
Reporter: Aliaksey Nis
Priority: Optional
EXECUTE: Open Server view.
EXECUTE: Right click on Server > Properties.
EXECUTE: Select Monitoring. Press Add button.
EXECUTE: Add port number in "Monitor port". Try to select something from drop-down menu "Content".
FAILURE: Content menu is empty. But Ok button is enabled. When Ok button pressed - nothing happens (except wizard closing).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months