September 2013 - jbosstools-issues

[JBoss JIRA] (JBTIS-163) Failed to resolve target definition

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTIS-163?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTIS-163: ----------------------------------------------- Marek Baluch <mbaluch(a)redhat.com> changed the Status of [bug 1005683|https://bugzilla.redhat.com/show_bug.cgi?id=1005683] from NEW to MODIFIED > Failed to resolve target definition > ----------------------------------- > > Key: JBTIS-163 > URL: https://issues.jboss.org/browse/JBTIS-163 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.1.2, 4.1.3, 4.1.4-TP > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > Fix For: 4.1.5.Alpha1-TP > > > During building with target platform 4.1.2-SNAPSHOT / 4.1.2.Final (the same for 4.1.3) I'm getting the following error: > [ERROR] Internal error: java.lang.RuntimeException: Failed to resolve target definition /home/apodhrad/.m2/repository/org/jboss/tools/integration-stack/target-platform/4.1.2-SNAPSHOT/target-platform-4.1.2-SNAPSHOT-base.target: Could not find "org.jboss.tools.locus.jcip.annotations/1.0.0.Final-v20130729-2113-B39" in the repositories of the current location -> [Help 1] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-163) Failed to resolve target definition

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTIS-163?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTIS-163: ----------------------------------------------- Marek Baluch <mbaluch(a)redhat.com> changed the Status of [bug 1005683|https://bugzilla.redhat.com/show_bug.cgi?id=1005683] from MODIFIED to ON_QA > Failed to resolve target definition > ----------------------------------- > > Key: JBTIS-163 > URL: https://issues.jboss.org/browse/JBTIS-163 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.1.2, 4.1.3, 4.1.4-TP > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > Fix For: 4.1.5.Alpha1-TP > > > During building with target platform 4.1.2-SNAPSHOT / 4.1.2.Final (the same for 4.1.3) I'm getting the following error: > [ERROR] Internal error: java.lang.RuntimeException: Failed to resolve target definition /home/apodhrad/.m2/repository/org/jboss/tools/integration-stack/target-platform/4.1.2-SNAPSHOT/target-platform-4.1.2-SNAPSHOT-base.target: Could not find "org.jboss.tools.locus.jcip.annotations/1.0.0.Final-v20130729-2113-B39" in the repositories of the current location -> [Help 1] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-165) Regression - Cannot add a file to the attachments

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBTIS-165?page=com.atlassian.jira.plugin.... ] Viacheslav Kabanovich commented on JBTIS-165: --------------------------------------------- Yes, this is a bug, but it is not a regression, it just happens in the configuration of this project. File /test/.settings/org.eclipse.wst.common.component declares two web roots as follows {code} <wb-resource deploy-path="/" source-path="/esbcontent"/> <wb-resource deploy-path="/" source-path="/src"/> {code} I am not sure now why, but for the case of multiple roots I coded to take the second one as ESB content folder. Java sources are added to the search tree always, be they declared as web roots or not. That is why the dialog window in the screenshot contains two 'src' folders. Possible workaround is to change order of roots: {code} <wb-resource deploy-path="/" source-path="/src"/> <wb-resource deploy-path="/" source-path="/esbcontent"/> {code} To fix the issue I need to know - Is it really necessary to add source folders to <wb-resource> list? - When <wb-resource> contains several items, are they all contributing equally to ESB content? > Regression - Cannot add a file to the attachments > ------------------------------------------------- > > Key: JBTIS-165 > URL: https://issues.jboss.org/browse/JBTIS-165 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.1.2 > Environment: JBoss ESB Tools 1.5.300.Final-v20130815-1755-B1189 > Reporter: Andrej Podhradsky > Assignee: Viacheslav Kabanovich > Priority: Blocker > Attachments: esb_attachment_bug.png, test.zip > > > Cannot add a file to the attachments from esbcontent folder. It's also impossible to add .txt file from the root but .zip file is possible to add. See the screenshot -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-163) Failed to resolve target definition

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-163?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-163. ------------------------------ Fix Version/s: 4.1.5.Alpha1-TP (was: 4.1.4-TP) Resolution: Done resolved again - please use 4.1.5.Alpha1: https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.1.5.Al... > Failed to resolve target definition > ----------------------------------- > > Key: JBTIS-163 > URL: https://issues.jboss.org/browse/JBTIS-163 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.1.2, 4.1.3, 4.1.4-TP > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > Fix For: 4.1.5.Alpha1-TP > > > During building with target platform 4.1.2-SNAPSHOT / 4.1.2.Final (the same for 4.1.3) I'm getting the following error: > [ERROR] Internal error: java.lang.RuntimeException: Failed to resolve target definition /home/apodhrad/.m2/repository/org/jboss/tools/integration-stack/target-platform/4.1.2-SNAPSHOT/target-platform-4.1.2-SNAPSHOT-base.target: Could not find "org.jboss.tools.locus.jcip.annotations/1.0.0.Final-v20130729-2113-B39" in the repositories of the current location -> [Help 1] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-167) remove coretests from the JBTIS TP

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-167?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-167. ------------------------------ Fix Version/s: 4.1.5.Alpha1-TP Resolution: Done https://github.com/jbosstools/jbosstools-integration-stack/pull/119 > remove coretests from the JBTIS TP > ---------------------------------- > > Key: JBTIS-167 > URL: https://issues.jboss.org/browse/JBTIS-167 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.1.4-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.1.5.Alpha1-TP > > > remove: > <unit id="org.jboss.tools.tests" version="3.5.0.Final-v20130717-0450-B102"/> > <repository location="http://download.jboss.org/jbosstools/updates/nightly/coretests/4.1.kepler/"/> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14764) Update VJET in Central

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14764?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-14764: ----------------------------------------- +1 to include this build. The build promise the following issues to be fixed: [Bug 412815 - Date set* Methods should return Number not void|https://bugs.eclipse.org/bugs/show_bug.cgi?id=412815] [Bug 412818 - Unknown Methods for inferred types give warning not error by default Some other minor issues is fixed on validation.|https://bugs.eclipse.org/bugs/show_bug.cgi?id=412818] > Update VJET in Central > ---------------------- > > Key: JBIDE-14764 > URL: https://issues.jboss.org/browse/JBIDE-14764 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Beta1 > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Fix For: 4.1.1.Final > > Attachments: JBIDE14764.png > > > As VJET fixes issues in their 0.10 release (see JBIDE-14122), we should pull a newer version for Beta2 or CR1. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14764) Update VJET in Central

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14764?page=com.atlassian.jira.plugi... ] Victor Rubezhny edited comment on JBIDE-14764 at 9/9/13 4:10 PM: ----------------------------------------------------------------- +1 to include this build. The build promise the following issues to be fixed: [Bug 412815 - Date set* Methods should return Number not void|https://bugs.eclipse.org/bugs/show_bug.cgi?id=412815] [Bug 412818 - Unknown Methods for inferred types give warning not error by default|https://bugs.eclipse.org/bugs/show_bug.cgi?id=412818] Some other minor issues is fixed on validation. was (Author: vrubezhny): +1 to include this build. The build promise the following issues to be fixed: [Bug 412815 - Date set* Methods should return Number not void|https://bugs.eclipse.org/bugs/show_bug.cgi?id=412815] [Bug 412818 - Unknown Methods for inferred types give warning not error by default Some other minor issues is fixed on validation.|https://bugs.eclipse.org/bugs/show_bug.cgi?id=412818] > Update VJET in Central > ---------------------- > > Key: JBIDE-14764 > URL: https://issues.jboss.org/browse/JBIDE-14764 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Beta1 > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Fix For: 4.1.1.Final > > Attachments: JBIDE14764.png > > > As VJET fixes issues in their 0.10 release (see JBIDE-14122), we should pull a newer version for Beta2 or CR1. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-7799) Could not parse process /src/main/rules/ruleflow.rf

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7799?page=com.atlassian.jira.plugin... ] Brian Fitzpatrick resolved JBIDE-7799. -------------------------------------- Fix Version/s: (was: LATER) Resolution: Out of Date This bug is way out of date. > Could not parse process /src/main/rules/ruleflow.rf > --------------------------------------------------- > > Key: JBIDE-7799 > URL: https://issues.jboss.org/browse/JBIDE-7799 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: drools > Affects Versions: 3.2.0.Beta2 > Environment: soa-p 4.3 > Reporter: Libor Zoubek > Assignee: Brian Fitzpatrick > Priority: Blocker > Attachments: .log > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-165) Regression - Cannot add a file to the attachments

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-165?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick reassigned JBTIS-165: --------------------------------------- Assignee: Viacheslav Kabanovich (was: Brian Fitzpatrick) Slava, do you have any time to look into this? > Regression - Cannot add a file to the attachments > ------------------------------------------------- > > Key: JBTIS-165 > URL: https://issues.jboss.org/browse/JBTIS-165 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.1.2 > Environment: JBoss ESB Tools 1.5.300.Final-v20130815-1755-B1189 > Reporter: Andrej Podhradsky > Assignee: Viacheslav Kabanovich > Priority: Blocker > Attachments: esb_attachment_bug.png, test.zip > > > Cannot add a file to the attachments from esbcontent folder. It's also impossible to add .txt file from the root but .zip file is possible to add. See the screenshot -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-1645) JBDS 4 - jBPM upload URL is: "/jbpm-console/upload" but it should be "/gpd-deployer/upload"

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBDS-1645?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBDS-1645: ----------------------------------------------- Brian Fitzpatrick <bfitzpat(a)redhat.com> made a comment on [bug 780614|https://bugzilla.redhat.com/show_bug.cgi?id=780614] Can we close this? > JBDS 4 - jBPM upload URL is: "/jbpm-console/upload" but it should be "/gpd-deployer/upload" > ---------------------------------------------------------------------------------------------- > > Key: JBDS-1645 > URL: https://issues.jboss.org/browse/JBDS-1645 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbpm > Environment: Version: 4.0.0.GA > Build id: v20110216-1930-H239-GA > Build date: 20110216-1930 > Reporter: Len DiMaggio > Assignee: Koen Aers > Priority: Critical > Fix For: 4.1.0.CR1 > > > Related to https://issues.jboss.org/browse/SOA-2937 > The enterprise is using "/gpd-deployer/upload" and the community is using "/jbpm-console/upload". > For JBDS, we should have the default value be "/gpd-deployer/upload" - as this is what the SOA Platform requires. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
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 September 2013