April 2013 - jbosstools-issues - Jboss List Archives

[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: -------------------------------------- Ahoj Petře, this should be assigned to somebody else as I do not have enough insight into these JBDS internals. Snježa is perhaps a good candidate. > 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: Peter Palaga > Fix For: 4.1.x > > > 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

1
0
0 / 0

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

by Petr Suchý (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13905?page=com.atlassian.jira.plugi... ] Petr Suchý updated JBIDE-13905: ------------------------------- Steps to Reproduce: Prereq: JPP 6.0.0.GA 1. Open New Dynamic Web Project wizard 2. Go into Project Facelets window and select JBoss Core Portlet 3. Go to JBoss Portlet Capabilities page 4. _Portlet Target Runtime Provider_ is not present was: Prereq: JPP 6.0.0.GA 1. Open New Dynamic Web Project wizard 2. Go into Project Facelets window and select JBoss Core Portlet 3. On JBoss Portlet Capabilities window is not present _Portlet Target Runtime Provider_ as Type of Portlet Implementation Library > 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: Peter Palaga > Fix For: 4.1.x > > > 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

1
0
0 / 0

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

by Petr Suchý (JIRA)

Petr Suchý created JBIDE-13905: ---------------------------------- Summary: 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.1.0.Alpha1, 4.0.1.Final Reporter: Petr Suchý Assignee: Peter Palaga Fix For: 4.1.x 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13839) Adding runtimes through runtime-detection does not work properly

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13839?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13839: ------------------------------------- merged > Adding runtimes through runtime-detection does not work properly > ---------------------------------------------------------------- > > Key: JBIDE-13839 > URL: https://issues.jboss.org/browse/JBIDE-13839 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.1.0.Alpha1 > Reporter: Petr Suchý > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > > When I add runtime (i.e. SOA-P 5.2) through runtime-detection, then I remove it from Servers view and then I add different runtime but with the same name (i.e. SOA-P 5.3, again through runtime-detection), this new runtime is not added. -- 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
0
0 / 0

[JBoss JIRA] (JBIDE-13831) Add 'Edit' to possible actions in 'configure maven repositories'

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13831?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-13831 at 4/3/13 4:16 AM: ------------------------------------------------------------- PR applied in master. As I commented on the PR : {quote} I noticed these 2 minor annoyances : The repo viewer should have a horizontal scroller, since adding the (inactive) suffix can make a pretty long label the repo order changes after an edit. {quote} See JBIDE-13904 was (Author: fbricon): PR applied in master. As I commented on the PR : {quote} I noticed these 2 minor annoyances : The repo viewer should have a horizontal scroller, since adding the (inactive) suffix can make a pretty long label the repo order changes after an edit. {quote} > Add 'Edit' to possible actions in 'configure maven repositories' > ---------------------------------------------------------------- > > Key: JBIDE-13831 > URL: https://issues.jboss.org/browse/JBIDE-13831 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.0.0.Final > Reporter: Michelle Murray > Assignee: Snjezana Peco > Labels: new_and_noteworthy > Fix For: 4.1.0.Alpha2 > > > In Windows > Preferences > JBoss Tools > JBoss Maven Integration, there is configure maven repositories. > This has options to 'remove', 'remove all', and 'add repository'. Is it possible to add an 'edit' option? > For example, I have jboss eap 6.0.0 and I want to update it to 6.0.1. Or what if I use the 'add repository' option and make a small mistake - I would have to remove the repo and start again. I realize there are workarounds for both of these examples but 'Edit' would be useful from a user perspective. -- 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
0
0 / 0

[JBoss JIRA] (JBIDE-13904) Minor UI issues in "Configure Repositories" wizard

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-13904: ----------------------------------- Summary: Minor UI issues in "Configure Repositories" wizard Key: JBIDE-13904 URL: https://issues.jboss.org/browse/JBIDE-13904 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 4.1.0.Alpha2 Reporter: Fred Bricon Assignee: Snjezana Peco Priority: Minor Fix For: 4.1.0.Beta1 In the Window > Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories... * The repo viewer should have a horizontal scroller, since adding the (inactive) suffix can make a pretty long label and you have to resize the whole dialog to be able to read the labels * Edit a repo, switching the profile activation status : it reorders the repositories/profiles in settings.xml. -- 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
0
0 / 0

[JBoss JIRA] (JBIDE-2625) add an "application stop/application start" option to jboss server view

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2625?page=com.atlassian.jira.plugin... ] Rob Stryker updated JBIDE-2625: ------------------------------- Release Notes Text: Previously, right-clicking a module for AS7 and selecting 'stop' execute an undeploy, either by a filesystem marker (.undeploy) or by unpublishing the entire module. Similarly, a 'start' would either add a .deploy or republish the entire deployment. Both of these solutions had problems. Republishing an unchanged deployment was wasteful and took extra time. Using the deployment marker files also required waiting for the deployment scanners to run. For AS >= 7, this has changed, and now 'start' and 'stop' closely match the 'enable' / 'disable' options from the web administration console. The deployments are started or stopped via the management api, without removing or re-adding the archive. This makes start, stop, and restart, much faster than previously. It also solves the user complaint as posted here. Fix Version/s: 4.1.0.Alpha2 (was: 4.0.x) Affects: Release Notes > add an "application stop/application start" option to jboss server view > ----------------------------------------------------------------------- > > Key: JBIDE-2625 > URL: https://issues.jboss.org/browse/JBIDE-2625 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: JBossAS/Servers > Affects Versions: 2.1.2 > Reporter: Francisco Jose Peredo Noguez > Assignee: Rob Stryker > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.1.0.Alpha2 > > Attachments: web-gui.png > > > Sometimes, and application just enters an infinte loop (because of a programming error, because it can not find a class, etc) in those cases one has to stop all the application server but sometimes, the problem can be solved simply by stopping that particular application, fixing the problem, and starting it again, and, since one didn't have to restart Jboss, it takes a lot less time. I would like to be able to do that in an easy way from inside eclipse. -- 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
0
0 / 0

[JBoss JIRA] (JBIDE-2625) add an "application stop/application start" option to jboss server view

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2625?page=com.atlassian.jira.plugin... ] Rob Stryker updated JBIDE-2625: ------------------------------- Labels: new_and_noteworthy (was: ) > add an "application stop/application start" option to jboss server view > ----------------------------------------------------------------------- > > Key: JBIDE-2625 > URL: https://issues.jboss.org/browse/JBIDE-2625 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: JBossAS/Servers > Affects Versions: 2.1.2 > Reporter: Francisco Jose Peredo Noguez > Assignee: Rob Stryker > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.0.x > > Attachments: web-gui.png > > > Sometimes, and application just enters an infinte loop (because of a programming error, because it can not find a class, etc) in those cases one has to stop all the application server but sometimes, the problem can be solved simply by stopping that particular application, fixing the problem, and starting it again, and, since one didn't have to restart Jboss, it takes a lot less time. I would like to be able to do that in an easy way from inside eclipse. -- 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
0
0 / 0

[JBoss JIRA] (JBDS-1914) Move files in developer workspaces in SVN to examples folder in trunk for automated publishing to download.jboss.org/jbosstools/examples/

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-1914?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-1914: ------------------------------ Fix Version/s: 7.0.0.Beta1 (was: 7.0.0.Alpha2) > Move files in developer workspaces in SVN to examples folder in trunk for automated publishing to download.jboss.org/jbosstools/examples/ > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-1914 > URL: https://issues.jboss.org/browse/JBDS-1914 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 5.0.0.M3 > Reporter: Nick Boldt > Assignee: Fred Bricon > Labels: f2f2012 > Fix For: 7.0.0.Beta1 > > > Instead of referencing files in dev workspaces, commit your files into this path in SVN [1] and they'll appear automatically [2] after the next rsync here [3]. Then you can point at a path that's served via a download server (file tracking, better throughput, backups) instead of our anonsvn web UI (slow, untracked). > [1] https://svn.jboss.org/repos/jbosstools/trunk/download.jboss.org/jbosstool... > [2] http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_All/job/j... > [3] http://download.jboss.org/jbosstools/examples/ > These files (line numbers shown) need fixing: > {code} > ./project-examples-jbds40.xml > 851: http://anonsvn.jboss.org/repos/jbosstools/workspace/dflorian/teiid-design... > 877: http://anonsvn.jboss.org/repos/jbosstools/workspace/dflorian/teiid-design... > 894: http://anonsvn.jboss.org/repos/jbosstools/workspace/jdoyle/teiid-designer... > ./project-examples-3.2.xml > 17: http://anonsvn.jboss.org/repos/jbosstools/workspace/dflorian/teiid-design... > 43: http://anonsvn.jboss.org/repos/jbosstools/workspace/dflorian/teiid-design... > 60: http://anonsvn.jboss.org/repos/jbosstools/workspace/jdoyle/teiid-designer... > {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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13686) Compatible runtime constraints should be declared in Stack.yaml

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13686?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-13686: -------------------------------- Fix Version/s: 4.1.0.Beta1 (was: 4.1.0.Alpha2) > Compatible runtime constraints should be declared in Stack.yaml > --------------------------------------------------------------- > > Key: JBIDE-13686 > URL: https://issues.jboss.org/browse/JBIDE-13686 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven, project-examples > Affects Versions: 4.1.0.Alpha1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.1.0.Beta1 > > > Runtime constraints are currently read from project descriptor xmls. > This causes JBIDE-13656. > That info should be read from the stacks instead. The wtp server id should be added as a label for each runtime in stacks.yaml. -- 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
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