[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-7565) Problems publishing and accessing parent pom + target platforms
by Nick Boldt (JIRA)
Problems publishing and accessing parent pom + target platforms
---------------------------------------------------------------
Key: JBIDE-7565
URL: https://jira.jboss.org/browse/JBIDE-7565
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.2.0.Beta2
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.2.0.CR1
Thought I had this solved, but on further testing, I've found a problem.
This file is 404'd:
http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o...
However, the one I actually published is fine:
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
So, when I try to retrieve the pom from the repo, I get this error:
[DEBUG] Using connector WagonRepositoryConnector with priority 0 for http://repository.jboss.org/nexus/content/groups/public/
Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o...
[DEBUG] Reading resolution tracking file /home/nboldt/.m2/repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.1-SNAPSHOT/resolver-status.properties
[DEBUG] Writing resolution tracking file /home/nboldt/.m2/repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.1-SNAPSHOT/resolver-status.properties
[DEBUG] Could not find metadata org.jboss.tools:org.jboss.tools.target.platform:0.0.1-SNAPSHOT/maven-metadata.xml in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/)
[DEBUG] Using connector WagonRepositoryConnector with priority 0 for http://repository.jboss.org/nexus/content/groups/public/
Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o...
[DEBUG] Reading resolution tracking file /home/nboldt/.m2/repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.1-SNAPSHOT/org.jboss.tools.target.platform-0.0.1-SNAPSHOT-unified.target.lastUpdated
[DEBUG] Writing resolution tracking file /home/nboldt/.m2/repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.1-SNAPSHOT/org.jboss.tools.target.platform-0.0.1-SNAPSHOT-unified.target.lastUpdated
[ERROR] Internal error: java.lang.RuntimeException: Could not resolve target platform specification artifact org.jboss.tools:org.jboss.tools.target.platform:target:unified:0.0.1-SNAPSHOT -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not resolve target platform specification artifact org.jboss.tools:org.jboss.tools.target.platform:target:unified:0.0.1-SNAPSHOT
How can I force the resolution process to look at
https://repository.jboss.org/nexus/content/repositories/snapshots instead of http://repository.jboss.org/nexus/content/groups ?
Or, how can I force the missing/empty file to contain the correct versioning information so that maven can find the artifact?
I also tried to switch from
<uniqueVersion>true</uniqueVersion>
to
<uniqueVersion>false</uniqueVersion>
but the published artifacts still have the uniqueVersion suffixes.
----------
Steps to reproduce:
# remove your existing local .m2 cache
if [[ -d ~/.m2 ]]; then mv ~/.m2 ~/.m2___GOOD; fi
# check out build folder
cd /tmp; svn co http://anonsvn.jboss.org/repos/jbosstools/trunk/build/
# check out tests folder
cd /tmp; svn co http://anonsvn.jboss.org/repos/jbosstools/trunk/tests/
# build tests
cd /tmp/tests; mvn3 clean install -X -e -fae -U -B
Workaround:
However, if the parent pom is built locally, then the tests can be built too, w/o a problem (because the parent pom + target platform artifacts now exist locally in my ~/.m2 folder):
# build parent pom + target platform
cd /tmp/build; mvn3 clean install -f parent/pom.xml
# build tests
cd /tmp/tests; mvn3 clean install -X -e -fae -U -B
----------
Here's how I'm building + publishing the artifacts, fwiw:
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2.0.Beta2.target-platf...
--
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-8058) smooks test fails when run w/ all other tests (incl. emma code coverage), but passes when run solo (no emma)
by Nick Boldt (JIRA)
smooks test fails when run w/ all other tests (incl. emma code coverage), but passes when run solo (no emma)
------------------------------------------------------------------------------------------------------------
Key: JBIDE-8058
URL: https://issues.jboss.org/browse/JBIDE-8058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: smooks
Affects Versions: 3.2.0.CR1
Reporter: Nick Boldt
Assignee: Brian Fitzpatrick
Priority: Optional
Passes: http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.2...
Passing for at least the last 4 builds (Since #8)
> mvn3 clean install -B -U -fae -e -Dmaven.repo.local=${WORKSPACE}/m2-repository -P helios-local-target,jbosstools-nightly-trunk,hudson
---
Fails: http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.2...
Failing for the past 43 builds (Since #216 )
> mvn3 clean install -B -U -fae -e -Dmaven.repo.local=${WORKSPACE}/m2-repo -P helios-local-target,jbosstools-nightly-trunk,hudson,coverage
---
I'm not sure this is a big deal, I'm just curious why this is happening. Ideally, the same test should pass in both scenarios.
Could it be related to emma code coverage?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBIDE-8043) Two different context menus for OnMessage/OnAlarm
by Marek Baluch (JIRA)
Two different context menus for OnMessage/OnAlarm
-------------------------------------------------
Key: JBIDE-8043
URL: https://issues.jboss.org/browse/JBIDE-8043
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel
Affects Versions: 3.2.0.Beta2, 3.2.0.CR1
Environment: JBoss Tools: 3.2_trunk.2010-12-16_04-27-01-H504
Reporter: Marek Baluch
Priority: Minor
It's possible to get 2 context menus for OnMessage and OnAlarm branch. While both are usable only one of them is consistent with other context menus for similar activities. The first (IMO correct one) allows to add activities to the branch in question while the other does not.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBIDE-7551) Instance View: Table Sorting should have 3 states and indicate sorting with arrows
by Andre Dietisheim (JIRA)
Instance View: Table Sorting should have 3 states and indicate sorting with arrows
----------------------------------------------------------------------------------
Key: JBIDE-7551
URL: https://jira.jboss.org/browse/JBIDE-7551
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.2.0.CR1
How to reproduce:
1) make sure you have instance view opened and a few instances listed
2) click on a column
Result:
the column gets sorted, but there's no icon that shows the sort direction. Furthermore there are only 2 states: sorting ascending or descending
Expected result:
The column gets sorted and an icon shows what direction (ascending/descending) is activated. Furthermore you should be able to toggle between ascending/descending/not sorted by clicking consecutively on the same column
--
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