July 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6569) Make git repo available for JBoss Tools

by Max Rydahl Andersen (JIRA)

Make git repo available for JBoss Tools --------------------------------------- Key: JBIDE-6569 URL: https://jira.jboss.org/browse/JBIDE-6569 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Max Rydahl Andersen Fix For: LATER I think it would be useful to explore how to make a git-svn repo available for jboss tools trunk. Opening this issue for keeping track of what have been attempted so far. -- 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

3
7
0 / 0

[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

1
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8981) Support Hibernate4 in hibernate tools core

by Dmitry Geraskov (JIRA)

Support Hibernate4 in hibernate tools core ------------------------------------------ Key: JBIDE-8981 URL: https://issues.jboss.org/browse/JBIDE-8981 Project: Tools (JBoss Tools) Issue Type: Task Components: Hibernate Affects Versions: 3.3.0.M1 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Priority: Critical Fix For: 3.3.0.M2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBDS-1648) JBoss Dev Studio 4.0 crash

by Matt V (JIRA)

JBoss Dev Studio 4.0 crash -------------------------- Key: JBDS-1648 URL: https://issues.jboss.org/browse/JBDS-1648 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: visualeditor Affects Versions: 4.0.0.GA Environment: Win 7 x64 Pro SP1 Reporter: Matt V I had installed the 4.0GA version of Jboss Dev Studio, created a sample project. Later I restarted the Studio after attempting to install a few plugins (I believe Subclipse). Every time afterwards, it would launch the studio , the UI would launch with code windows, and then the studio would crash to desktop in less than a second afterwards. I do have dump eclipse files that can be attached to this issues. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

20
74
0 / 0

[JBoss JIRA] Created: (JBIDE-8452) JBoss Maven Git integration

by Snjezana Peco (JIRA)

JBoss Maven Git integration --------------------------- Key: JBIDE-8452 URL: https://issues.jboss.org/browse/JBIDE-8452 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Affects Versions: 3.2.0.Final Reporter: Snjezana Peco Assignee: Snjezana Peco It will enable us to import a maven project from a git repository and create project examples using examples from a git repository directly. As to the seam examples, it will be enough to add an entry to the project examples xml file. This feature will require EGit - http://www.eclipse.org/egit -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

5
13
0 / 0

[JBoss JIRA] Created: (JBIDE-8651) Revert workaround for wrong implementation of WTP's ElementImpl.getAttribute(String)

by Yahor Radtsevich (JIRA)

Revert workaround for wrong implementation of WTP's ElementImpl.getAttribute(String) ------------------------------------------------------------------------------------ Key: JBIDE-8651 URL: https://issues.jboss.org/browse/JBIDE-8651 Project: Tools (JBoss Tools) Issue Type: Task Components: Visual Page Editor core Affects Versions: 3.3.0.M1 Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 3.3.x Workaround for JBIDE-8649 (https://bugs.eclipse.org/272378 ) should be reverted when this propblen is fixed on WTP. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-3574) JBoss Tools wizards have black borders around SWT controls

by Denis Golovin (JIRA)

JBoss Tools wizards have black borders around SWT controls ---------------------------------------------------------- Key: JBIDE-3574 URL: https://jira.jboss.org/jira/browse/JBIDE-3574 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.CR2 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.0.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, 3 months

3
21
0 / 0

[JBoss JIRA] Created: (JBIDE-7942) Add an image viewer (reusable via the QuickImage plugin)

by Juergen Zimmermann (JIRA)

Add an image viewer (reusable via the QuickImage plugin) -------------------------------------------------------- Key: JBIDE-7942 URL: https://issues.jboss.org/browse/JBIDE-7942 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Juergen Zimmermann QuickImage is an image viewer which is available as an Eclipse plugin. The homepage is http://psnet.nu/eclipse/index.html . It can be obtained via the Eclipse marketplace and seems to have the EPL license. Such a viewer is nice when you quickly want to inspect some images, icons, buttons etc. inside a web project. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

7
8
0 / 0

[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, 3 months

4
13
0 / 0

[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, 3 months

5
8
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2011