October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23370) Update RedDeer in TP for JBT 4.4.2.AM3

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23370?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23370: --------------------------------------- [~rawagner], can you confirm that you can see the latest RedDeer in the current TP when you run tests? I ran a test and it would fail before because of the confirmation of deployment removal, but now it didn't happen, so that seems to prove that the new RedDeer is there now. > Update RedDeer in TP for JBT 4.4.2.AM3 > -------------------------------------- > > Key: JBIDE-23370 > URL: https://issues.jboss.org/browse/JBIDE-23370 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.4.2.AM3 > > > Due to some changes/fixes in RedDeer that we'd like to use in tests, we'd like to update the RedDeer bits in our TP. > This was requested by [~rawagner] and we understand that it's just past code freeze for AM2, so this will probably have to wait until after AM2 is released. > We will want to update RedDeer in the TP to include the latest from > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > I will simply create a snapshot with the rsync script and then give you the url. But it's a bit premature to do it now since it may be a week or two before you actually update the TP. > So please let me know when you're ready for this task and then I can create the update site immediately. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23420) Update RedDeer in TP for JBT 4.4.2.Final

by Martin Malina (JIRA)

Martin Malina created JBIDE-23420: ------------------------------------- Summary: Update RedDeer in TP for JBT 4.4.2.Final Key: JBIDE-23420 URL: https://issues.jboss.org/browse/JBIDE-23420 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: target-platform Affects Versions: 4.4.2.AM2 Reporter: Martin Malina Assignee: Martin Malina Fix For: 4.4.2.AM3 Due to some changes/fixes in RedDeer that we'd like to use in tests, we'd like to update the RedDeer bits in our TP. This was requested by [~rawagner] and we understand that it's just past code freeze for AM2, so this will probably have to wait until after AM2 is released. We will want to update RedDeer in the TP to include the latest from https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... I will simply create a snapshot with the rsync script and then give you the url. But it's a bit premature to do it now since it may be a week or two before you actually update the TP. So please let me know when you're ready for this task and then I can create the update site immediately. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-965) Update ComplexBusinessRuleTaskTest to use insertion of facts

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-965?page=com.atlassian.jira.plugin.... ] Jozef Marko updated JBTIS-965: ------------------------------ Affects Version/s: 4.4.0.Final (was: 4.4.0.CR1-TP) > Update ComplexBusinessRuleTaskTest to use insertion of facts > ------------------------------------------------------------ > > Key: JBTIS-965 > URL: https://issues.jboss.org/browse/JBTIS-965 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2, QE > Affects Versions: 4.4.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Fix For: 4.4.0.Final > > > Update the given test to insert a fact (Person) into the session to get the rule fired. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-964) Confusing versions of BPMN2 features

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-964?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-964: ---------------------------------- Letting you field this one [~bbrodt] > Confusing versions of BPMN2 features > ------------------------------------ > > Key: JBTIS-964 > URL: https://issues.jboss.org/browse/JBTIS-964 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2, distribution > Affects Versions: 10.0.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > > Devstudio IS 10.0.0.CR1 contains the following BPMN2 bundles > - org.eclipse.bpmn2.feature_1.3.1.Final-v20160927-2047-B56.jar > - org.eclipse.bpmn2.modeler.examples_1.3.2.Final-v20161020-1541-B59.jar > - org.eclipse.bpmn2.modeler.runtime.jboss_1.3.2.Final-v20161020-1541-B59.jar > - org.eclipse.bpmn2.modeler_1.3.2.Final-v20161020-1541-B59.jar > As you can see there are two versions which is very confusing. For example, DevstudioIS 10.0.0.Alpha1 contains BPMN2 versions 1.3.0.Final-v20160119-1832 and 1.3.1.Final-v20160831-1132-B55, so how can customer specify correct version in case of reporting an issue? > I don't think there are two standalone projects of BPMN2, so there is no reason to use 2 versions. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-964) Confusing versions of BPMN2 features

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-964?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-964: -------------------------------- Assignee: Robert (Bob) Brodt > Confusing versions of BPMN2 features > ------------------------------------ > > Key: JBTIS-964 > URL: https://issues.jboss.org/browse/JBTIS-964 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2, distribution > Affects Versions: 10.0.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > > Devstudio IS 10.0.0.CR1 contains the following BPMN2 bundles > - org.eclipse.bpmn2.feature_1.3.1.Final-v20160927-2047-B56.jar > - org.eclipse.bpmn2.modeler.examples_1.3.2.Final-v20161020-1541-B59.jar > - org.eclipse.bpmn2.modeler.runtime.jboss_1.3.2.Final-v20161020-1541-B59.jar > - org.eclipse.bpmn2.modeler_1.3.2.Final-v20161020-1541-B59.jar > As you can see there are two versions which is very confusing. For example, DevstudioIS 10.0.0.Alpha1 contains BPMN2 versions 1.3.0.Final-v20160119-1832 and 1.3.1.Final-v20160831-1132-B55, so how can customer specify correct version in case of reporting an issue? > I don't think there are two standalone projects of BPMN2, so there is no reason to use 2 versions. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4143) RPM requires eclipse-m2e-* -> not installable

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4143?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4143: ----------------------------- Sprint: devex #122 October 2016 > RPM requires eclipse-m2e-* -> not installable > --------------------------------------------- > > Key: JBDS-4143 > URL: https://issues.jboss.org/browse/JBDS-4143 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Reporter: Václav Kadlčík > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.2.0.AM3 > > > Follow-up to JBDS-4141. lucene3 is OK now but five others appeared: > # yum localinstall rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64.rpm > ... > --> Finished Dependency Resolution > Error: Package: rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64 (/rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64) > Requires: eclipse-m2e-buildhelper > Error: Package: rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64 (/rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64) > Requires: eclipse-m2e-workspace > Error: Package: rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64 (/rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64) > Requires: eclipse-m2e-egit > Error: Package: rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64 (/rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64) > Requires: eclipse-m2e-core > Error: Package: rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64 (/rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64) > Requires: eclipse-m2e-mavenarchiver > I don't think there's anything in RHEL which can satisfy eclipse-m2e-core, or whatever starting with "eclipse". That is, unless Mat is brewing something really different from his previous builds of rh-eclipse46... > Maybe there's some systematic error how the RPM Requires get created? -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-739) Fuse: Add test for space and special characters in the path

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-739?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-739. ----------------------------------- pushed to master (neon) and jbtis-4.3.x (mars) > Fuse: Add test for space and special characters in the path > ----------------------------------------------------------- > > Key: JBTIS-739 > URL: https://issues.jboss.org/browse/JBTIS-739 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Critical > Fix For: 4.4.0.Final > > Original Estimate: 1 hour > Time Spent: 30 minutes > Remaining Estimate: 30 minutes > > https://issues.jboss.org/browse/FUSETOOLS-1647 > https://issues.jboss.org/browse/FUSETOOLS-1668 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-814) Fuse - Extend the scope of projects used for testing deployment/undeployment

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-814?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-814. ----------------------------------- pushed to master > Fuse - Extend the scope of projects used for testing deployment/undeployment > ---------------------------------------------------------------------------- > > Key: JBTIS-814 > URL: https://issues.jboss.org/browse/JBTIS-814 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.1.Final > Reporter: Andrej Podhradsky > Assignee: Tomáš Sedmík > Priority: Critical > Fix For: 4.4.0.Final > > Original Estimate: 2 hours > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Extend the scope of projects used for testing deployment/undeployment. It seems that projects which were imported a an existing maven project cannot be successfully deployed/undeployed. Please see FUSETOOLS-1997 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4143) RPM requires eclipse-m2e-* -> not installable

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4143?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-4143. ------------------------------ Resolution: Done Fixed with https://github.com/jbdevstudio/jbdevstudio-product/commit/3639dc81a8030af... The systemic problem to which you refer is that I test this on Fedora, so I've got access to more rpms than a RHEL7 use. I've removed all the packages I previously added EXCEPT the rh-* ones and java-1.8.0-openjdk-devel. If you see any other *Requires:* lines in the rpm spec file that point to things not available in RHEL 7, please feel free to point me at them directly (a PR would be great!). > RPM requires eclipse-m2e-* -> not installable > --------------------------------------------- > > Key: JBDS-4143 > URL: https://issues.jboss.org/browse/JBDS-4143 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Reporter: Václav Kadlčík > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.2.0.AM3 > > > Follow-up to JBDS-4141. lucene3 is OK now but five others appeared: > # yum localinstall rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64.rpm > ... > --> Finished Dependency Resolution > Error: Package: rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64 (/rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64) > Requires: eclipse-m2e-buildhelper > Error: Package: rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64 (/rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64) > Requires: eclipse-m2e-workspace > Error: Package: rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64 (/rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64) > Requires: eclipse-m2e-egit > Error: Package: rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64 (/rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64) > Requires: eclipse-m2e-core > Error: Package: rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64 (/rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64) > Requires: eclipse-m2e-mavenarchiver > I don't think there's anything in RHEL which can satisfy eclipse-m2e-core, or whatever starting with "eclipse". That is, unless Mat is brewing something really different from his previous builds of rh-eclipse46... > Maybe there's some systematic error how the RPM Requires get created? -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4143) RPM requires eclipse-m2e-* -> not installable

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4143?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-4143: --------------------------------- Fix Version/s: 10.2.0.AM3 > RPM requires eclipse-m2e-* -> not installable > --------------------------------------------- > > Key: JBDS-4143 > URL: https://issues.jboss.org/browse/JBDS-4143 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Reporter: Václav Kadlčík > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.2.0.AM3 > > > Follow-up to JBDS-4141. lucene3 is OK now but five others appeared: > # yum localinstall rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64.rpm > ... > --> Finished Dependency Resolution > Error: Package: rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64 (/rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64) > Requires: eclipse-m2e-buildhelper > Error: Package: rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64 (/rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64) > Requires: eclipse-m2e-workspace > Error: Package: rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64 (/rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64) > Requires: eclipse-m2e-egit > Error: Package: rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64 (/rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64) > Requires: eclipse-m2e-core > Error: Package: rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64 (/rh-eclipse46-devstudio-10.2-0.20161027.0913.el7.x86_64) > Requires: eclipse-m2e-mavenarchiver > I don't think there's anything in RHEL which can satisfy eclipse-m2e-core, or whatever starting with "eclipse". That is, unless Mat is brewing something really different from his previous builds of rh-eclipse46... > Maybe there's some systematic error how the RPM Requires get created? -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 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 October 2016