April 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-39) Approve update to SwtichYard 0.8.0.Final and BPMN2 modeler 0.2.4

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-39?page=com.atlassian.jira.plugin.s... ] Kris Verlaenen resolved JBTIS-39. --------------------------------- Resolution: Done Sure, sounds fine > Approve update to SwtichYard 0.8.0.Final and BPMN2 modeler 0.2.4 > ---------------------------------------------------------------- > > Key: JBTIS-39 > URL: https://issues.jboss.org/browse/JBTIS-39 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: drools/ jBPM5 > Reporter: Rob Cernich > Assignee: Kris Verlaenen > Fix For: 4.0.0 > > > There were no dependency errors building the site. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13938) Add support for server requirements to integration-tests

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13938?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-13938: ------------------------------- Description: * new annotations for test classes will be introduced * server will be defined in reddeer requirement xml * server adapter will be configured according to the xml configuration was: * new annotations for test classes will be introduced * server is defined in reddeer requirement xml * server adapter is configured according to the xml configuration > Add support for server requirements to integration-tests > --------------------------------------------------------- > > Key: JBIDE-13938 > URL: https://issues.jboss.org/browse/JBIDE-13938 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: QA > Affects Versions: 4.1.0.Alpha1 > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.1.0.Beta1 > > > * new annotations for test classes will be introduced > * server will be defined in reddeer requirement xml > * server adapter will be configured according to the xml configuration -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13938) Add support for server requirements to integration-tests

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-13938: ---------------------------------- Summary: Add support for server requirements to integration-tests Key: JBIDE-13938 URL: https://issues.jboss.org/browse/JBIDE-13938 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: QA Affects Versions: 4.1.0.Alpha1 Reporter: Pavol Srna Assignee: Pavol Srna Fix For: 4.1.0.Beta1 * new annotations for test classes will be introduced * server is defined in reddeer requirement xml * server adapter is configured according to the xml configuration -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13843) SWTBot 2.0.5 depends on org.junit4, which has been removed from Eclipse 4.3M6. Can we use SWTBot 2.1 instead?

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13843?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-13843: --------------------------------------- OK, right now if I use the newer target platform, RedDeer won't compile because there are many dependencies on junit4 in manifests. So once we move to that we will need to update that. But otherwise it should be fine. I don't think we have any objection to this change - we need to adjust to the progress :) For now we will use JBT target platform p2 repo. We will think about creating our own TP. > SWTBot 2.0.5 depends on org.junit4, which has been removed from Eclipse 4.3M6. Can we use SWTBot 2.1 instead? > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13843 > URL: https://issues.jboss.org/browse/JBIDE-13843 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, testing-tools > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 4.1.0.Alpha2 > > > Eclipse 4.3M5a contains: > {code}4.3milestones/S-4.3M5a-201302041400/plugins/org.junit4_4.8.1.v20120705-112236.jar{code} > But in Eclipse 4.3M6, the only JUnit available is: > {code}4.3milestones/S-4.3M6-201303141330/plugins/org.junit_4.11.0.v201303080030.jar{code} > So, we need to see if a newer SWTBot can be used which depends on org.junit instead of org.junit4. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13905) portlet-api library of JPP 6 is not imported

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13905?page=com.atlassian.jira.plugi... ] Peter Palaga commented on JBIDE-13905: -------------------------------------- [~mstruk] says that in JPP 6.1 (which will be based on EAP 6.1), `portlet-api.jar` module should be located at `modules/system/add-ons/gatein/javax/portlet/api/main/` > portlet-api library of JPP 6 is not imported > -------------------------------------------- > > Key: JBIDE-13905 > URL: https://issues.jboss.org/browse/JBIDE-13905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Portal/GateIn > Affects Versions: 4.0.1.Final, 4.1.0.Alpha1 > Reporter: Petr Suchý > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > > When you want to create Dynamic Web Project using JPP 6.0.0.GA, you cannot simply choose Portlet implementation library as a Portlet Target Runtime Provider in a New Dynamic Web Project Wizard. You are forced to add _portlet-api.jar_ manually from here: > {code} > ${JPP6}/modules/javax/portlet/api/main/ > {code} -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13905) portlet-api library of JPP 6 is not imported

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13905?page=com.atlassian.jira.plugi... ] Peter Palaga edited comment on JBIDE-13905 at 4/5/13 6:39 AM: -------------------------------------------------------------- [~mstruk] says that in JPP 6.1 (which will be based on EAP 6.1), {{portlet-api.jar}} module should be located at {{modules/system/add-ons/gatein/javax/portlet/api/main/}} was (Author: ppalaga): [~mstruk] says that in JPP 6.1 (which will be based on EAP 6.1), `portlet-api.jar` module should be located at `modules/system/add-ons/gatein/javax/portlet/api/main/` > portlet-api library of JPP 6 is not imported > -------------------------------------------- > > Key: JBIDE-13905 > URL: https://issues.jboss.org/browse/JBIDE-13905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Portal/GateIn > Affects Versions: 4.0.1.Final, 4.1.0.Alpha1 > Reporter: Petr Suchý > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > > When you want to create Dynamic Web Project using JPP 6.0.0.GA, you cannot simply choose Portlet implementation library as a Portlet Target Runtime Provider in a New Dynamic Web Project Wizard. You are forced to add _portlet-api.jar_ manually from here: > {code} > ${JPP6}/modules/javax/portlet/api/main/ > {code} -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13843) SWTBot 2.0.5 depends on org.junit4, which has been removed from Eclipse 4.3M6. Can we use SWTBot 2.1 instead?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13843?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13843: ---------------------------------------- A good link to a stable repo is http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... Also, I'd encourage to create and use you own target platform since you'll probably won't need all of JBT target-platform/repositories to develop RedDeer. I think it makes sense that you don't use the parent pom: it's very coupled with JBT concerns, so 2/3 of it would be useless in your case. For the remaining third (source features, code-coverage, repository facade...) you can simply copy-paste some bits in your RedDeer parent pom. > SWTBot 2.0.5 depends on org.junit4, which has been removed from Eclipse 4.3M6. Can we use SWTBot 2.1 instead? > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13843 > URL: https://issues.jboss.org/browse/JBIDE-13843 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, testing-tools > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 4.1.0.Alpha2 > > > Eclipse 4.3M5a contains: > {code}4.3milestones/S-4.3M5a-201302041400/plugins/org.junit4_4.8.1.v20120705-112236.jar{code} > But in Eclipse 4.3M6, the only JUnit available is: > {code}4.3milestones/S-4.3M6-201303141330/plugins/org.junit_4.11.0.v201303080030.jar{code} > So, we need to see if a newer SWTBot can be used which depends on org.junit instead of org.junit4. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13737) Provide Restart for Application as the Web-UI does

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13737?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13737: ------------------------------------- Release Notes Text: There are cases where you want to restart your OpenShift application. This is required if you for instance add the enable_jpda marker to allow you to remote debug it. You then have to restart your OpenShift application so that it picks the new marker and enables debugging. JBoss Tools for OpenShift now allows you to restart your application from its context menu in the OpenShift Explorer. > Provide Restart for Application as the Web-UI does > -------------------------------------------------- > > Key: JBIDE-13737 > URL: https://issues.jboss.org/browse/JBIDE-13737 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: new_and_noteworthy > Fix For: 4.1.0.Alpha2 > > Attachments: try-in-a-minute.png > > > We need at least a way to restart an application as the web-UI does: > !application-restart.png! -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13737) Provide Restart for Application as the Web-UI does

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13737?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13737: ------------------------------------- Labels: new_and_noteworthy (was: ) > Provide Restart for Application as the Web-UI does > -------------------------------------------------- > > Key: JBIDE-13737 > URL: https://issues.jboss.org/browse/JBIDE-13737 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: new_and_noteworthy > Fix For: 4.1.0.Alpha2 > > Attachments: try-in-a-minute.png > > > We need at least a way to restart an application as the web-UI does: > !application-restart.png! -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13843) SWTBot 2.0.5 depends on org.junit4, which has been removed from Eclipse 4.3M6. Can we use SWTBot 2.1 instead?

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13843?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-13843: --------------------------------------- [~nickboldt] RedDeer does not use the shared parent pom, so your setting of TARGET_PLATFORM_VERSION in https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... makes no difference. I would like to check if moving to the M6-based TP will break anything in RedDeer. Is there a regular p2 repo of that? Something like http://download.jboss.org/jbosstools/updates/kepler/ . Yes, I could use a target-platform definition but that's unnecessarily complicated if there is a p2 repo. Why don't we use the shared parent pom? Probably because of the idea that RedDeer is meant as an independent project that anybody can use and is not bound to JBT in any way. > SWTBot 2.0.5 depends on org.junit4, which has been removed from Eclipse 4.3M6. Can we use SWTBot 2.1 instead? > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13843 > URL: https://issues.jboss.org/browse/JBIDE-13843 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, testing-tools > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 4.1.0.Alpha2 > > > Eclipse 4.3M5a contains: > {code}4.3milestones/S-4.3M5a-201302041400/plugins/org.junit4_4.8.1.v20120705-112236.jar{code} > But in Eclipse 4.3M6, the only JUnit available is: > {code}4.3milestones/S-4.3M6-201303141330/plugins/org.junit_4.11.0.v201303080030.jar{code} > So, we need to see if a newer SWTBot can be used which depends on org.junit instead of org.junit4. -- 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

13 years, 2 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 April 2013