December 2011 - jbosstools-issues

[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

4
13
0 / 0

[JBoss JIRA] (JBIDE-10441) Hibernate Configuration launcher file opens Hibernate Console Dialog by default

by Jiri Peterka (Created) (JIRA)

Hibernate Configuration launcher file opens Hibernate Console Dialog by default ------------------------------------------------------------------------------- Key: JBIDE-10441 URL: https://issues.jboss.org/browse/JBIDE-10441 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: hibernate Affects Versions: 3.3.0.M4 Reporter: Jiri Peterka Assignee: Dmitry Geraskov Fix For: 3.3.0.Beta1 Steps: Create Hibernate Console Configuration and store it in as a launcher file in a project. Try to open it. It's opened in a plain text editor. I would like to see opening via Hibernate Configuration dialog (as similar as when I click on Hibernate Configuration item in Hibernate Console Configuration view). It have to be recognized according to it's content because filename/extension is general for all launchers (*.launcher). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

9
12
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, 2 months

5
8
0 / 0

[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

6
12
0 / 0

[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

3
9
0 / 0

[JBoss JIRA] Created: (JBDS-1597) Importing existing BPEL quickstart into JBDS4 generates error message, but the import is successful

by Len DiMaggio (JIRA)

Importing existing BPEL quickstart into JBDS4 generates error message, but the import is successful --------------------------------------------------------------------------------------------------- Key: JBDS-1597 URL: https://issues.jboss.org/browse/JBDS-1597 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Error Reporting Environment: Version: 4.0.0.GA Build id: v20110216-1930-H239-GA Build date: 20110216-1930 SOA-P 5.1 GA JBoss Tools http://download.jboss.org/jbosstools/updates/nightly/trunk/ (BPEL editor) 1.0.0.v20110217-0324-H60-Alpha1 Reporter: Len DiMaggio Attachments: log, Screenshot.png Screen shot and .log for the error are attached - the error was seen importing SOA-P 5.1's bpel_hello_world_header_ode quickstart. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
15
0 / 0

[JBoss JIRA] Created: (JBIDE-9035) IPublishCopyCallbackHandler#deleteResource returns status but no caller is accounting for

by Andre Dietisheim (JIRA)

IPublishCopyCallbackHandler#deleteResource returns status but no caller is accounting for ----------------------------------------------------------------------------------------- Key: JBIDE-9035 URL: https://issues.jboss.org/browse/JBIDE-9035 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M1, 3.2.1.M1 Reporter: Andre Dietisheim Assignee: Rob Stryker Fix For: 3.3.x IPublishCopyCallbackHandler#deleteResource returns status instances for the different filesystem operations involved to it but none of the callers take them in account. They all ignore it and return STATUS_OK. occurrences: * AltMethodZippedJSTPublisher#removeRemoteDeploymentFolder * AbstractServerToolsPublisher#fullPublish * AbstractServerToolsPublisher#unpublish * JBoss7JSTPublisher#removeDeployedMarkerFile * PublishCopyUtil#publishDelta -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (JBDS-1595) Editing Documentation property for WSDL - result is that text written to wsdl shows a one-char lag behind that shown in property field in JBDS

by Len DiMaggio (JIRA)

Editing Documentation property for WSDL - result is that text written to wsdl shows a one-char lag behind that shown in property field in JBDS ----------------------------------------------------------------------------------------------------------------------------------------------- Key: JBDS-1595 URL: https://issues.jboss.org/browse/JBDS-1595 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: visualeditor Environment: Version: 4.0.0.GA Build id: v20110216-1930-H239-GA Build date: 20110216-1930 SOA-P 5.1 GA JBoss Tools http://download.jboss.org/jbosstools/updates/nightly/trunk/ (BPEL editor) 1.0.0.v20110217-0324-H60-Alpha1 Reporter: Len DiMaggio Editing Documentation property for WSDL - result is that text written to wsdl shows a one-char lag behind that shown in property field in JBDS See the attached screen shot for an example of this -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
8
0 / 0

[JBoss JIRA] Created: (JBIDE-8329) Automatic detection of web port does not work for EAP 4.3

by Magnus Mogren (JIRA)

Automatic detection of web port does not work for EAP 4.3 --------------------------------------------------------- Key: JBIDE-8329 URL: https://issues.jboss.org/browse/JBIDE-8329 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.CR1 Reporter: Magnus Mogren Assignee: Rob Stryker The automatic detection of web port does not work for EAP 4.3 servers. The reason is a faulty XPath expession used to detect the port: //Server/Service[@name='jboss.web']/Connector[count(@sslProtocol) = 0 and (count(@protocol) = 0 or @protocol = 'HTTP/1.1')] That expression tries to get the value of the Connector element in the server.xml, not the port attribute of the element. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8045) Unable to select fault variable data type in faultHandler.

by Marek Baluch (JIRA)

Unable to select fault variable data type in faultHandler. ---------------------------------------------------------- Key: JBIDE-8045 URL: https://issues.jboss.org/browse/JBIDE-8045 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.Beta2, 3.2.0.CR1 Reporter: Marek Baluch Attachments: fault_handler.zip User is not able to select the data type for a user defined fault when defining a faultHandler catch branch. It's possible to attempt to select the data type using the browse button but the chosen type is not noticed by the UI. The message structure is missing too. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
10
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 December 2011