April 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13913) Wrong page is opened in a browser when you run project on JPP 6

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13913?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-13913: --------------------------------------- I have added a test using a mockup server. Please let me know if you want me to add a real JPP 6 server. > Wrong page is opened in a browser when you run project on JPP 6 > --------------------------------------------------------------- > > Key: JBIDE-13913 > URL: https://issues.jboss.org/browse/JBIDE-13913 > 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.x > > Attachments: jpp_wrong-page.jpg > > > When you run Web dynamic project on JPP 6.0.0.GA, wrong page is opened in a browser. See a 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2490) migrate JBT and JBDS discovery plugins to new github repo, jbosstools-discovery

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2490?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2490 at 4/6/13 7:54 PM: ---------------------------------------------------------- Unless we plan to build more 3.3.x (5.0.x) or 4.0.x (6.0.x) releases, then 3.3.x (5.0.x) and 4.0.x (6.0.x) are (for now) done maintenance. That may change and prompt the need to potentially backport this later. But I'm not going to do it proactively *_just in case_* we decide to do a release later, since there's an existing (if imperfect) workflow in place already for manually rebuilding discovery plugins for 3.3.x (5.0.x) and 4.0.x (6.0.x) releases. Therefore, here are the sources for the various maintenance/development streams: In 3.3.x, 2 SVN repos: https://svn.jboss.org/repos/jbosstools/branches/jbosstools-3.3.x/central/... http://svn.jboss.org/repos/devstudio/branches/devstudio-5.0.x/product/plu... In 4.0.x, 1 github repo + 1 SVN repo: https://github.com/jbosstools/jbosstools-central/tree/jbosstools-4.0.x/ce... http://svn.jboss.org/repos/devstudio/branches/devstudio-6.0.x/product/plu... In 4.1.x, 1 github repo: https://github.com/jbosstools/jbosstools-discovery [~maxandersen] Does that work? was (Author: nickboldt): Unless we plan to build more 3.3.x (5.0.x) or 4.0.x (6.0.x) releases, then 3.3.x (5.0.x) and 4.0.x (6.0.x) are (for now) done maintenance. That may change and prompt the need to potentially backport this later. But I'm not going to do it proactive just in case we decide to do a release later, since there's an existing (if imperfect) workflow in place already for manually rebuilding discovery plugins for 3.3.x (5.0.x) and 4.0.x (6.0.x) releases. Therefore, here are the sources for the various maintenance/development streams: In 3.3.x, 2 SVN repos: https://svn.jboss.org/repos/jbosstools/branches/jbosstools-3.3.x/central/... http://svn.jboss.org/repos/devstudio/branches/devstudio-5.0.x/product/plu... In 4.0.x, 1 github repo + 1 SVN repo: https://github.com/jbosstools/jbosstools-central/tree/jbosstools-4.0.x/ce... http://svn.jboss.org/repos/devstudio/branches/devstudio-6.0.x/product/plu... In 4.1.x, 1 github repo: https://github.com/jbosstools/jbosstools-discovery [~maxandersen] Does that work? > migrate JBT and JBDS discovery plugins to new github repo, jbosstools-discovery > ------------------------------------------------------------------------------- > > Key: JBDS-2490 > URL: https://issues.jboss.org/browse/JBDS-2490 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 7.0.0.Alpha2 > > > Migrate 2 -3- branches of git sources (including history): > https://github.com/jbosstools/jbosstools-central/tree/master/central/plug... > https://github.com/jbosstools/jbosstools-central/tree/jbosstools-4.1.0.Al... > OMIT: https://github.com/jbosstools/jbosstools-central/tree/jbosstools-4.0.x/ce... > and 2 -3- branches of svn sources (including history): > http://svn.jboss.org/repos/devstudio/trunk/product/plugins/com.jboss.jbds... > http://svn.jboss.org/repos/devstudio/branches/devstudio-7.0.0.Alpha1/prod... > OMIT: http://svn.jboss.org/repos/devstudio/branches/devstudio-6.0.x/product/plu... > to a new Github project called "jbosstools-discovery" under which there would be: > * jbdevstudio/com.jboss.jbds.central.discovery/ > * jbosstools/org.jboss.tools.central.discovery/ -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2490) migrate JBT and JBDS discovery plugins to new github repo, jbosstools-discovery

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2490?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-2490: -------------------------------- Assignee: Max Rydahl Andersen (was: Nick Boldt) > migrate JBT and JBDS discovery plugins to new github repo, jbosstools-discovery > ------------------------------------------------------------------------------- > > Key: JBDS-2490 > URL: https://issues.jboss.org/browse/JBDS-2490 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 7.0.0.Alpha2 > > > Migrate 2 -3- branches of git sources (including history): > https://github.com/jbosstools/jbosstools-central/tree/master/central/plug... > https://github.com/jbosstools/jbosstools-central/tree/jbosstools-4.1.0.Al... > OMIT: https://github.com/jbosstools/jbosstools-central/tree/jbosstools-4.0.x/ce... > and 2 -3- branches of svn sources (including history): > http://svn.jboss.org/repos/devstudio/trunk/product/plugins/com.jboss.jbds... > http://svn.jboss.org/repos/devstudio/branches/devstudio-7.0.0.Alpha1/prod... > OMIT: http://svn.jboss.org/repos/devstudio/branches/devstudio-6.0.x/product/plu... > to a new Github project called "jbosstools-discovery" under which there would be: > * jbdevstudio/com.jboss.jbds.central.discovery/ > * jbosstools/org.jboss.tools.central.discovery/ -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2490) migrate JBT and JBDS discovery plugins to new github repo, jbosstools-discovery

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2490?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2490: ---------------------------------- Unless we plan to build more 3.3.x (5.0.x) or 4.0.x (6.0.x) releases, then 3.3.x (5.0.x) and 4.0.x (6.0.x) are (for now) done maintenance. That may change and prompt the need to potentially backport this later. But I'm not going to do it proactive just in case we decide to do a release later, since there's an existing (if imperfect) workflow in place already for manually rebuilding discovery plugins for 3.3.x (5.0.x) and 4.0.x (6.0.x) releases. Therefore, here are the sources for the various maintenance/development streams: In 3.3.x, 2 SVN repos: https://svn.jboss.org/repos/jbosstools/branches/jbosstools-3.3.x/central/... http://svn.jboss.org/repos/devstudio/branches/devstudio-5.0.x/product/plu... In 4.0.x, 1 github repo + 1 SVN repo: https://github.com/jbosstools/jbosstools-central/tree/jbosstools-4.0.x/ce... http://svn.jboss.org/repos/devstudio/branches/devstudio-6.0.x/product/plu... In 4.1.x, 1 github repo: https://github.com/jbosstools/jbosstools-discovery [~maxandersen] Does that work? > migrate JBT and JBDS discovery plugins to new github repo, jbosstools-discovery > ------------------------------------------------------------------------------- > > Key: JBDS-2490 > URL: https://issues.jboss.org/browse/JBDS-2490 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 7.0.0.Alpha2 > > > Migrate 2 -3- branches of git sources (including history): > https://github.com/jbosstools/jbosstools-central/tree/master/central/plug... > https://github.com/jbosstools/jbosstools-central/tree/jbosstools-4.1.0.Al... > OMIT: https://github.com/jbosstools/jbosstools-central/tree/jbosstools-4.0.x/ce... > and 2 -3- branches of svn sources (including history): > http://svn.jboss.org/repos/devstudio/trunk/product/plugins/com.jboss.jbds... > http://svn.jboss.org/repos/devstudio/branches/devstudio-7.0.0.Alpha1/prod... > OMIT: http://svn.jboss.org/repos/devstudio/branches/devstudio-6.0.x/product/plu... > to a new Github project called "jbosstools-discovery" under which there would be: > * jbdevstudio/com.jboss.jbds.central.discovery/ > * jbosstools/org.jboss.tools.central.discovery/ -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13913) Wrong page is opened in a browser when you run project on JPP 6

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13913?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-13913: --------------------------------------- I will add a test, but would also have to add JPP6 as a requirement. If you think, it would be better to use a mockup server, I will do it, but the test will be less reliable. > Wrong page is opened in a browser when you run project on JPP 6 > --------------------------------------------------------------- > > Key: JBIDE-13913 > URL: https://issues.jboss.org/browse/JBIDE-13913 > 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.x > > Attachments: jpp_wrong-page.jpg > > > When you run Web dynamic project on JPP 6.0.0.GA, wrong page is opened in a browser. See a 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2490) migrate JBT and JBDS discovery plugins to new github repo, jbosstools-discovery

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2490?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen reopened JBDS-2490: --------------------------------------- reopen for clarification: I thought the whole point was to avoid having to update across multiple repositories ? But if this wont be adjusted for 4.0.x stream doesn't this mean they still exist across multiple repos ? (note, i'm fine keeping it as is; just want to be sure that is what you meant). > migrate JBT and JBDS discovery plugins to new github repo, jbosstools-discovery > ------------------------------------------------------------------------------- > > Key: JBDS-2490 > URL: https://issues.jboss.org/browse/JBDS-2490 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 7.0.0.Alpha2 > > > Migrate 2 -3- branches of git sources (including history): > https://github.com/jbosstools/jbosstools-central/tree/master/central/plug... > https://github.com/jbosstools/jbosstools-central/tree/jbosstools-4.1.0.Al... > OMIT: https://github.com/jbosstools/jbosstools-central/tree/jbosstools-4.0.x/ce... > and 2 -3- branches of svn sources (including history): > http://svn.jboss.org/repos/devstudio/trunk/product/plugins/com.jboss.jbds... > http://svn.jboss.org/repos/devstudio/branches/devstudio-7.0.0.Alpha1/prod... > OMIT: http://svn.jboss.org/repos/devstudio/branches/devstudio-6.0.x/product/plu... > to a new Github project called "jbosstools-discovery" under which there would be: > * jbdevstudio/com.jboss.jbds.central.discovery/ > * jbosstools/org.jboss.tools.central.discovery/ -- 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, 3 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13905?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13905: --------------------------------------------- that location won't be correct if the user have applied patches - its fine for a first cut, but just be aware these locations are not reliable. > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13913) Wrong page is opened in a browser when you run project on JPP 6

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13913?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13913: --------------------------------------------- Looks like [~rob.stryker] applied this PR but did not resolve the jira - which actually is good since the PR has no tests. Can't we add some for this show in browser logic so we don't just keep adding on top custom logic without any test to catch if we change/break logic ? > Wrong page is opened in a browser when you run project on JPP 6 > --------------------------------------------------------------- > > Key: JBIDE-13913 > URL: https://issues.jboss.org/browse/JBIDE-13913 > 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.x > > Attachments: jpp_wrong-page.jpg > > > When you run Web dynamic project on JPP 6.0.0.GA, wrong page is opened in a browser. See a 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13848) Issue caused by changing editor ID for ClassFileEditor in Juno

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13848?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-13848: ---------------------------------- Summary: Issue caused by changing editor ID for ClassFileEditor in Juno (was: Issue caused by changing editor ID for ClassFileEdtor in Juno) > Issue caused by changing editor ID for ClassFileEditor in Juno > -------------------------------------------------------------- > > Key: JBIDE-13848 > URL: https://issues.jboss.org/browse/JBIDE-13848 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13939) Usage tests freeze on Kepler M6

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13939?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13939: ------------------------------------------ This test is not testing UI, it's not involving the UI. The usage dialog, that pops up is the one that's included in the Eclipse under test/TP. The problem is that GlobalUsageSettingsTest is enabling usage in the system properties. Latter tests then apparently run new Eclipse instances which then trigger the usage dialog. > Usage tests freeze on Kepler M6 > ------------------------------- > > Key: JBIDE-13939 > URL: https://issues.jboss.org/browse/JBIDE-13939 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Affects Versions: 4.1.0.Alpha1, 4.1.0.Alpha2 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > > The usage tests freezes because they are executed before calling the UsageReportEnablementDialog dialog. > They set the "usage_reporting_enabled" property to true which enables opening the UsageReportEnablementDialog dialog. > The fix is to set usage_reporting_enabled=false after the latest test (UsageIntegrationTest). > The issue happens on Kepler M6. I suppose it is caused by some changes related to the handling UI messagess/jobs. -- 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, 3 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