[JBoss JIRA] Created: (JBIDE-6953) Disable Usage Reporting in Tests
by Andre Dietisheim (JIRA)
Disable Usage Reporting in Tests
--------------------------------
Key: JBIDE-6953
URL: https://jira.jboss.org/browse/JBIDE-6953
Project: Tools (JBoss Tools)
Issue Type: Release
Environment: CI, Tests
Reporter: Andre Dietisheim
Assignee: Denis Golovin
Priority: Blocker
Fix For: 3.2.0.M2
the UI tests we run should not trigger hits in our usage tracking. The plugin has a preferences setting that disables reporting.
It looks like we disable reporting for our UI test by having a custom config.ini for our UI tests.
The preference settings is:
"allowUsageReportPreference"
It is in the Configuration Scope (common to all workbenches of a particular eclipse instance).
For further lookup @see IUsageReportPreferenceConstants#USAGEREPORT_ENABLED_ID
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[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