April 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-5720) EAR Libraries in Dynamic Web Project

by Burr Sutter (JIRA)

EAR Libraries in Dynamic Web Project ------------------------------------ Key: JBIDE-5720 URL: https://jira.jboss.org/jira/browse/JBIDE-5720 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: core Environment: jbdevstudio-win32-3.0.0.v201001060655N-H50-CR1 Reporter: Burr Sutter Attachments: EAR_Libraries.jpg Creation of a New Dynamic Web Project adds "EAR Libraries" - that does not make sense because I (the user) am building a WAR and I do not want anything to do with an EAR in this case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-1354) Runtimes should be configurable with respect to what jars to return for certain runtimes

by Max Andersen (JIRA)

Runtimes should be configurable with respect to what jars to return for certain runtimes ---------------------------------------------------------------------------------------- Key: JBIDE-1354 URL: http://jira.jboss.com/jira/browse/JBIDE-1354 Project: JBoss Tools Issue Type: Feature Request Components: JBossAS Reporter: Max Andersen Fix For: 2.1 deploy only runtime could have preferences to control which jars they would actually return for various facets etc. optimally these would actually work on on any of our runtimes and just use variables/clever-defaults depending and allow users to override them if necessary. The user should be able to point to jars in a project, workspace, filesystem, classpath library, maven/ivy dependency even ...etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

6
26
0 / 0

[JBoss JIRA] Created: (JBIDE-4127) "Add JSF-Capabilities" adds jsf-facelets.jar which is older than the one in .classpath

by Leiv Hellebo (JIRA)

"Add JSF-Capabilities" adds jsf-facelets.jar which is older than the one in .classpath -------------------------------------------------------------------------------------- Key: JBIDE-4127 URL: https://jira.jboss.org/jira/browse/JBIDE-4127 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.0.0.GA Environment: JBDS 2.0.GA Seam 2.1.X Reporter: Leiv Hellebo The Add JSF-Capabilities dialog makes it possible to shoot oneself in the foot: It will happily add jsf-facelets.jar with Implementation-Version: 1.1.11, even if the one mentioned in .classpath has Implementation-Version: 1.1.15.B1 AFAICS, when performing a redirect within a long-running conversation, this makes "DEBUG [org.jboss.seam.contexts.ServletLifecycle] >>> Begin re-initialization" disappear from server.log, and needed context vars are not initialized. I'd file this as an "Improvement", not a "Bug" if it was possible. You may want to say "PEBKAC" to this... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-1050) Add Capabilities to Struts 1.3 at struts Tools

by Hermes Waldemarin (JIRA)

Add Capabilities to Struts 1.3 at struts Tools ---------------------------------------------- Key: JBIDE-1050 URL: http://jira.jboss.com/jira/browse/JBIDE-1050 Project: JBoss Tools Issue Type: Bug Components: JBoss Tools Core Affects Versions: 2.0.0.Beta3 Environment: Eclipse 3.3 Europa, Windows XP Reporter: Hermes Waldemarin I`m use struts 1.3.x in my aplication. I need to use chains policies in struts config, but this implementation is in 1.3.x version. Can you add Struts 1.3.x capabilities for struts plugin? Thanks... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8355) Automatic detection of server ports cannot handle changing configuration from default

by Magnus Mogren (JIRA)

Automatic detection of server ports cannot handle changing configuration from default ------------------------------------------------------------------------------------- Key: JBIDE-8355 URL: https://issues.jboss.org/browse/JBIDE-8355 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.CR1 Reporter: Magnus Mogren Assignee: Rob Stryker I create a new server for JBoss AS 6.0. I select the "default" configuration in the "New server" dialog. JNDI port is detected as 1099 as it should be. Now i open the "Edit server runtime environment" dialog and change from "default" to "all" configuration. I have edited the conf/bindingservice.beans\META-INF\bindings-jboss-beans.xml file to use JNDI port 11099 instead of 1099 for the "all" configuration. Now the autodetected JNDI port is still 1099? If i click the "Configure..." next to the auto detect checkbox and then "Edit XPath" i see that the root directory is still pointing to the default configuration. If i click the browse button and try to change the root directory it does not take the change. It still points to the default directory the next time i open the "Edit XPath" dialog. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

5
13
0 / 0

[JBoss JIRA] Created: (JBIDE-5914) M2eclipse is registering bad menu or Seam component view has bad menu id

by Max Rydahl Andersen (JIRA)

M2eclipse is registering bad menu or Seam component view has bad menu id ------------------------------------------------------------------------ Key: JBIDE-5914 URL: https://jira.jboss.org/jira/browse/JBIDE-5914 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven, Seam Affects Versions: 3.1.0.CR2 Reporter: Max Rydahl Andersen Fix For: 3.1.1 What steps will reproduce the problem? 1. Open Seam components view 2. Right Click on project 3. Error log shows up with "Plug-in 'org.maven.ide.eclipse.refactoring' contributed an invalid Menu Extension (Path: 'org.eclipse.jdt.ui.refactoring.menu' is invalid): org.maven.ide.eclipse.editor.RenameProjectAction" Which is rather annoying. I assume either is m2eclipse registreing their menu wrongly or our seam component view (common navigator) is doing something wrong since it works in Project Explorer. -- Error Details -- Date: Tue Feb 23 19:00:35 CET 2010 Message: Plug-in 'org.maven.ide.eclipse.refactoring' contributed an invalid Menu Extension (Path: 'org.eclipse.jdt.ui.refactoring.menu' is invalid): org.maven.ide.eclipse.editor.RenameProjectAction Severity: Error Product: Eclipse 1.2.1.20090812-1036 (org.eclipse.epp.package.jee.product) Plugin: org.eclipse.ui Session Data: eclipse.buildId=M20090917-0800 java.version=1.6.0_14 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=da_DK Framework arguments: -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product -data C:\Users\max\workspace-testy -product org.eclipse.epp.package.jee.product -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-6985) Add NOT_DROPINS + readme or similar into our updatesite zips

by Max Andersen (JIRA)

Add NOT_DROPINS + readme or similar into our updatesite zips ------------------------------------------------------------ Key: JBIDE-6985 URL: https://jira.jboss.org/browse/JBIDE-6985 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Affects Versions: 3.2.x Reporter: Max Andersen Assignee: Nick Boldt Fix For: 3.2.x Just an idea that occurred to that since updatesite zips and our old dropin compatible zips has same layout users keep trying to put them into dropins folder. Could would add a "NOT_FOR_DROPINS" with text explaining this an updatesite and (or at least) a readme or instructions file outlining: "This file is an Eclipse update zip to be used from within an Eclipse installations update manager. Do *not* unzip this zip into Eclipse directly nor into its dropins folder - it will *not* work. Use the Eclipse P2 Update Manager UI to perform the installation." Just a thought after seeing multiple users asking why their installation does not work anymore. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

5
11
0 / 0

[JBoss JIRA] Created: (JBIDE-8783) Upgrade FreeMarker to 2.3.16

by Fernando Ribeiro (JIRA)

Upgrade FreeMarker to 2.3.16 ---------------------------- Key: JBIDE-8783 URL: https://issues.jboss.org/browse/JBIDE-8783 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: FreeMarker Affects Versions: 3.2.0.Final Environment: All JBoss Tools environments. Reporter: Fernando Ribeiro Assignee: Max Rydahl Andersen Priority: Minor Fix For: 3.3.0.M1 The plugin should be upgraded to the latest version of FreeMarker, available at http://sourceforge.net/projects/freemarker/files/freemarker/2.3.16/. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

5
13
0 / 0

[JBoss JIRA] Created: (JBIDE-8174) After opening jBPM process Delete key doesn't work in Project Explorer

by Jiri Peterka (JIRA)

After opening jBPM process Delete key doesn't work in Project Explorer ---------------------------------------------------------------------- Key: JBIDE-8174 URL: https://issues.jboss.org/browse/JBIDE-8174 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.2.0.CR1 Environment: JBDS 4.0.0.CR1 H84, Linux 64 Reporter: Jiri Peterka After double click on process definition, Delete key doesn't work in Project Explorer. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
13
0 / 0

[JBoss JIRA] Created: (JBIDE-8734) Update Site containing JBT Bot Tests

by Jiri Peterka (JIRA)

14 years, 6 months

4
29
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 2011