March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13709) integration-tests should use JBTIS target platform to resolve SOA-related requirements like Zest

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13709: ---------------------------------- Summary: integration-tests should use JBTIS target platform to resolve SOA-related requirements like Zest Key: JBIDE-13709 URL: https://issues.jboss.org/browse/JBIDE-13709 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: esb, testing-tools Affects Versions: 4.0.0.Alpha1-SOA Reporter: Nick Boldt Assignee: Martin Malina >From JBIDE-13594, but for integration-tests instead of esb project. https://github.com/jbosstools/jbosstools-integration-tests/blob/master/si... requires ESB, which requires Zest. So, you need to ensure you're building your integration stack tests (which incidentally should be separated from the Core tests) using [~leacu]'s target platform for JBTIS. Here's how you patch your root pom (in the 4.0.x branch) to use the JBTIS TP (for Juno-based requirements): https://github.com/jbosstools/jbosstools-esb/pull/24/files I'm not sure what you'll have to do for the Kepler-based tests - either need a Kepler-based TP for JBTIS, or to disable those tests. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13709) integration-tests should use JBTIS target platform to resolve SOA-related requirements like Zest

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13709?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13709: ------------------------------- Description: >From JBIDE-13594, but for integration-tests instead of esb project. [~mmalina] said: {quote} I can still see the same error in a build from 03/01 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... {code} [ERROR] Missing requirement: org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 requires 'bundle org.eclipse.zest.core 0.0.0' but it could not be found {code} {quote} https://github.com/jbosstools/jbosstools-integration-tests/blob/master/si... requires ESB, which requires Zest. So, you need to ensure you're building your integration stack tests (which incidentally should be separated from the Core tests) using [~leacu]'s target platform for JBTIS. Here's how you patch your root pom (in the 4.0.x branch) to use the JBTIS TP (for Juno-based requirements): https://github.com/jbosstools/jbosstools-esb/pull/24/files I'm not sure what you'll have to do for the Kepler-based tests - either need a Kepler-based TP for JBTIS, or to disable those tests. was: >From JBIDE-13594, but for integration-tests instead of esb project. https://github.com/jbosstools/jbosstools-integration-tests/blob/master/si... requires ESB, which requires Zest. So, you need to ensure you're building your integration stack tests (which incidentally should be separated from the Core tests) using [~leacu]'s target platform for JBTIS. Here's how you patch your root pom (in the 4.0.x branch) to use the JBTIS TP (for Juno-based requirements): https://github.com/jbosstools/jbosstools-esb/pull/24/files I'm not sure what you'll have to do for the Kepler-based tests - either need a Kepler-based TP for JBTIS, or to disable those tests. > integration-tests should use JBTIS target platform to resolve SOA-related requirements like Zest > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-13709 > URL: https://issues.jboss.org/browse/JBIDE-13709 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: esb, testing-tools > Affects Versions: 4.0.0.Alpha1-SOA > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.1.0.Alpha2 > > > From JBIDE-13594, but for integration-tests instead of esb project. > [~mmalina] said: > {quote} > I can still see the same error in a build from 03/01 > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... > {code} > [ERROR] Missing requirement: org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 requires 'bundle org.eclipse.zest.core 0.0.0' but it could not be found > {code} > {quote} > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/si... requires ESB, which requires Zest. > So, you need to ensure you're building your integration stack tests (which incidentally should be separated from the Core tests) using [~leacu]'s target platform for JBTIS. > Here's how you patch your root pom (in the 4.0.x branch) to use the JBTIS TP (for Juno-based requirements): > https://github.com/jbosstools/jbosstools-esb/pull/24/files > I'm not sure what you'll have to do for the Kepler-based tests - either need a Kepler-based TP for JBTIS, or to disable those tests. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13702) ForgeCorePlugin could use an installed Forge 2 Runtime

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13702?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-13702: ----------------------------------------- AFAIK, this unzip happens when Eclipse loads the bundle for the first time (eg. starts the bundle), since it's called in the start(BundleContext) method. Also Forge 2 is initialized by default (When Eclipse starts), so I think that the option of having an exploded format is a better option, thus avoiding this unnecessary IO in the startup. > ForgeCorePlugin could use an installed Forge 2 Runtime > ------------------------------------------------------ > > Key: JBIDE-13702 > URL: https://issues.jboss.org/browse/JBIDE-13702 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Reporter: George Gastaldi > Assignee: Koen Aers > > In Forge 1, it is possible to configure external Forge runtimes. In Forge 2 it would be nice to allow configuration of that, but also avoid the need to unzip the files in the startup. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13702) ForgeCorePlugin could use an installed Forge 2 Runtime

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13702?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13702: --------------------------------------------- First off - its always a super big codesmell if we need to create custom urlclassloaders but I know Forge2 just can't work without it :( secondly, yes exploded format would probably avoid this issue of constant unzipping but run the risk of code actually writing to this destination. But as long as you dont do then using exploded bundles are an option yes. But that will make the default install of jbt/jbds slower since it will need to unzip these things *always*, not only when forge needs it. are you sure it will create a new temp unzip even if the bundle has not changed? i.e. isn't this only happening because you are always updating the bundle ? > ForgeCorePlugin could use an installed Forge 2 Runtime > ------------------------------------------------------ > > Key: JBIDE-13702 > URL: https://issues.jboss.org/browse/JBIDE-13702 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Reporter: George Gastaldi > Assignee: Koen Aers > > In Forge 1, it is possible to configure external Forge runtimes. In Forge 2 it would be nice to allow configuration of that, but also avoid the need to unzip the files in the startup. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-23) Add support/infrastructure for a p2 installer

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-23: ------------------------------- Summary: Add support/infrastructure for a p2 installer Key: JBTIS-23 URL: https://issues.jboss.org/browse/JBTIS-23 Project: JBoss Tools Integration Stack Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0.0 Reporter: Paul Leacu Assignee: Paul Leacu Fix For: 4.0.0 Add infrastructure for multiple p2 categories. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13703) Team - Verify the workflow

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13703?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13703: --------------------------------------------- I agree this sucks but the problem is the CVS tooling was created before something like Maven got into eclipse. The workflow you follow is just not what the eclipse CVS tooling was expecting. It expects the checkout to have a working eclipse project. We can try and get this fixed in eclipse by allowing for some kind of "detect what kind of project importer should be run based on files in the checkout" but this will not make it into eclipse anytime soon. What we can do is add our own "Import existing project" kind of wizard which could work with the various team providers but it would be our own custom UI and will add to the already existing set of crowded wizards. But at least we would have something we could point users to from Central etc. About CVS not being enabled automatically then this is a general problem for team connections like svn and git too. They tend to not get automatically enabled (you have to use Team > Share Project...). I think this is mainly not done since enabling it on large projects can slow the IDE down considerably (i.e. if you have annotation or labels enabled you will have things be slow). Again, I think we here could consider having an "Check things on import" for projects that checks what kind of cvs, svn, git etc. files are available and offer to enable it. Note: In the PDF you say you are looking for a simple Compile and Build button in the IDE but that is just not how Eclipse works - the user is not supposed to need to call these since eclipse will incrementally compile and build actions are specific to what kind of project you are importing using. But the Build button is under the Project menu if you need it. Problem is probably that you expect Eclipse to use Maven or Ant or Gradle to do its build - but it simply aren't; it uses its own build and via m2e-wtp we use what is in the pom.xml to tell eclipse what to do. Thus if your pom file is "normal" everything should be fine, but if you got special things, then yes you need the custom maven invocations like mvn install/mvn package - but not really any good place to put these in the IDE. > Team - Verify the workflow > -------------------------- > > Key: JBIDE-13703 > URL: https://issues.jboss.org/browse/JBIDE-13703 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Reporter: Burr Sutter > Assignee: Burr Sutter > Attachments: JBDS-usability.pdf > > > The average end-user would like to: > 1) check out (clone) a project from CVS, SVN or Git > -- add repo, navigate repo, check out a project > -- project may or may not have .classpath, .project or .settings files > -- project may be Maven-based > and see if the following work > 2) Are the appropriate facets enabled? > 3) Does it build immediately? > 4) Can I immediately hit the run button to launch it on my app server? > 5) Can I immediately hit the debug button to debug it on my app server? > -- how do I step if there are no break points? > 6) Make a change to a file, re-run/debug again > 7) Run JUnit tests > 8) Check the change back into the repo with comments -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2369) [JBDS Getting started guide] Typos

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBDS-2369?page=com.atlassian.jira.plugin.... ] Vlado Pakan reopened JBDS-2369: ------------------------------- https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/6.0... *[9.2,P1,L1] This section covers all the points how to create, edit and then preview JSP page. > This section outlines how to create, edit and preview a JSP page. Word 'then' was not omitted. > [JBDS Getting started guide] Typos > ---------------------------------- > > Key: JBDS-2369 > URL: https://issues.jboss.org/browse/JBDS-2369 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Doc - RHDS GSG > Affects Versions: 5.0.1.GA > Reporter: Michelle Murray > Assignee: Isaac Rooskov > Priority: Minor > Fix For: 6.0.0.CR1 > > > Typos: > *[Table1.1,R2,C2] ofthe > of the > *[3.2.1,B1,L3] insure > ensure > *[3.3,Current limitations,B2] shoortcuts > shortcuts > *[5,P1,L1] greated with > greeted by > *[5.1,P1,L1] you will see, and is > you will see. It is > *[5.1,P1,L1] setup > set up > *[7.1,B6] you yo > you to > *[7.2,After Fig 7.6] right next its > right next to its > *[9.2,P1,L1] This section covers all the points how to create, edit and then preview JSP page. > This section outlines how to create, edit and preview a JSP page. > *[9.2.1,After Fig9.4] After changes made your > After this line has been added your ... > *[9.2.3,P1,L1] Writing ant > Writing any > *[9.2.3.2,P1,L1] JBoss Server as it is > JBoss Server it is -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13695) Rename Method Participant does not work correctly if project is out of synch

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13695?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-13695: ---------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-javaee/pull/57, https://github.com/jbosstools/jbosstools-jst/pull/65 (was: https://github.com/jbosstools/jbosstools-javaee/pull/57) > Rename Method Participant does not work correctly if project is out of synch > ---------------------------------------------------------------------------- > > Key: JBIDE-13695 > URL: https://issues.jboss.org/browse/JBIDE-13695 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: CDI, common/jst/core, JSF > Affects Versions: 4.1.0.Alpha1 > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Priority: Critical > Fix For: 4.1.0.Alpha2 > > > See: https://community.jboss.org/message/800166#800166 > What to do: > 1. Do not block UI (put error in the log instead producing fatal error) > 2. Make error message more clear > 3. Try to refresh the project -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13695) Rename Method Participant does not work correctly if project is out of synch

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13695?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-13695: ---------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-javaee/pull/57, https://github.com/jbosstools/jbosstools-jst/pull/65, https://github.com/jbosstools/jbosstools-base/pull/58 (was: https://github.com/jbosstools/jbosstools-javaee/pull/57, https://github.com/jbosstools/jbosstools-jst/pull/65) > Rename Method Participant does not work correctly if project is out of synch > ---------------------------------------------------------------------------- > > Key: JBIDE-13695 > URL: https://issues.jboss.org/browse/JBIDE-13695 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: CDI, common/jst/core, JSF > Affects Versions: 4.1.0.Alpha1 > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Priority: Critical > Fix For: 4.1.0.Alpha2 > > > See: https://community.jboss.org/message/800166#800166 > What to do: > 1. Do not block UI (put error in the log instead producing fatal error) > 2. Make error message more clear > 3. Try to refresh the project -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13695) Rename Method Participant does not work correctly if project is out of synch

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13695?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-13695: ---------------------------------- Summary: Rename Method Participant does not work correctly if project is out of synch (was: git) > Rename Method Participant does not work correctly if project is out of synch > ---------------------------------------------------------------------------- > > Key: JBIDE-13695 > URL: https://issues.jboss.org/browse/JBIDE-13695 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: CDI, common/jst/core, JSF > Affects Versions: 4.1.0.Alpha1 > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Priority: Critical > Fix For: 4.1.0.Alpha2 > > > See: https://community.jboss.org/message/800166#800166 > What to do: > 1. Do not block UI (put error in the log instead producing fatal error) > 2. Make error message more clear > 3. Try to refresh the project -- 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, 1 month

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 March 2013