January 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8208) Improve how annotation processors are setup/detected via maven/m2eclipse

by Max Rydahl Andersen (JIRA)

Improve how annotation processors are setup/detected via maven/m2eclipse ------------------------------------------------------------------------ Key: JBIDE-8208 URL: https://issues.jboss.org/browse/JBIDE-8208 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Max Rydahl Andersen Fix For: 3.2.1 Any way m2eclipse can setup and detect annotation processors ? Why isn't annotation processor not enabled by default when generating the .settings files for it ? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

9
26
0 / 0

[JBoss JIRA] (JBIDE-10702) Editor for JCR Compact Node Definition (CND) files

by Randall Hauch (JIRA)

Randall Hauch created JBIDE-10702: ------------------------------------- Summary: Editor for JCR Compact Node Definition (CND) files Key: JBIDE-10702 URL: https://issues.jboss.org/browse/JBIDE-10702 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: modeshape Reporter: Randall Hauch Assignee: Dan Florian JSR-283 (aka, JCR 2.0) includes a standard format called 'Compact Node Definition' that is used to declare node types, property definitions, and child node definitions. *Resources* The official grammar of the CND format is defined in [Section 25.2|http://www.day.com/specs/jcr/2.0/25_Appendix.html#25.2%20Compact%20N...] of the JCR 2.0 specification. The ModeShape project has in its documentation a [tutorial|https://docs.jboss.org/author/display/MODE/Defining+custom+node+...] for working with CND files. The ModeShape project also has code to parse a CND file, and it's probably better to simply copy this code and simplify/customize it to the editor's needs rather than have the editor depend on the ModeShape project for just these classes (which probably aren't perfectly usable as is for the editor). There are also example CNDs in the ModeShape codebase. *Requirements* # Edit any .cnd file in the workspace _(Priority 1)_ # View the file source, with support for select/copy _(Priority 1)_ # Edit the file source, with support for paste _(Priority 3)_ # Syntax highlighting (color keywords, quoted strings, comments) of file source would be a nice-to-have _(Priority 2)_ # Problem markers (in file source, Problems view) would be a nice-to-have _(Priority 3)_ # Form-based editor: ## view/edit/add/remove namespace declarations _(Priority 1)_ ## view/edit/add/remove node type and its attributes and supertypes _(Priority 1)_ ## view/edit/add/remove property definition (and its attributes) for a selected node type _(Priority 1)_ ## view/edit/add/remove child node definition (and its attributes) for a selected node type _(Priority 1)_ # Preferences for ## using long, medium, or short forms of attributes (e.g., "abstract" vs "abs" vs "a") _(Priority 2, start out w/ long)_ *Other ideas* # It would be nice if the user doesn't have to scroll in the form editor when working on a node type. # Is it possible to optionally see the both inherited and explicit property definitions and child node definitions? Perhaps the inherited definitions might be grey-ed out and non-editable. One issue might be how to know which node type it came from (without cluttering up the UI). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

5
31
0 / 0

[JBoss JIRA] (JBIDE-10666) Delete OpenShift domain with JBoss tooling

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-10666: -------------------------------------- Summary: Delete OpenShift domain with JBoss tooling Key: JBIDE-10666 URL: https://issues.jboss.org/browse/JBIDE-10666 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Reporter: Stefan Bunciak Assignee: Andre Dietisheim Priority: Critical OpenShift wizard should provide a way how to remove domain, as the CLI client supports it: rhc-ctl-domain -l [-p ] (-a [-k ] | -r | -u [-k ]) -l|--rhlogin rhlogin Red Hat login (RHN or OpenShift login with OpenShift Express access) (required) -p|--password password RHLogin password (optional, will prompt) -n|--namespace namespace Namespace for your application(s) (alphanumeric - max 16 chars) (required for destroying domain) -a|--add-ssh-key key-name Add SSH key to the user account (key-name is the user-specified identifier for the key) -r|--remove-ssh-key key-name Remove SSH key from the user account -u|--update-ssh-key key-name Update SSH key for the user account --destroy Destroys the domain and any added ssh keys -k|--ssh key-filepath SSH public key filepath --config path Path of alternate config file -d|--debug Print Debug info -h|--help Show Usage info -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

5
25
0 / 0

[JBoss JIRA] (JBDS-1954) license text not aligned in JBDS features

by Max Rydahl Andersen (Created) (JIRA)

license text not aligned in JBDS features ----------------------------------------- Key: JBDS-1954 URL: https://issues.jboss.org/browse/JBDS-1954 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: updatesite Reporter: Max Rydahl Andersen Priority: Minor Fix For: 5.0.0.Beta1 noticed that licensetext are not same for JBDS features. see screenshot from p2 update manager. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

5
8
0 / 0

[JBoss JIRA] (JBDS-1988) When a SOA-P runtime is defined - why not define the corresponding (embedded) ESB runtime

by Len DiMaggio (Created) (JIRA)

When a SOA-P runtime is defined - why not define the corresponding (embedded) ESB runtime ------------------------------------------------------------------------------------------ Key: JBDS-1988 URL: https://issues.jboss.org/browse/JBDS-1988 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: SOA Platform Affects Versions: 5.0.0.M5 Environment: Version: 5.0.0.M5 Build id: v20111215-0954-H60-M5 Build date: 20111215-0954 Reporter: Len DiMaggio Assignee: Brian Fitzpatrick Fix For: 5.0.0.Beta1 The ESB runtime detector is able to correctly locate the embedded ESB runtime in a SOA-P server installation. Why not automatically define an ESB runtime when the user defines a SOA-P server runtime? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

5
8
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-189) modify ws user guide documents

by Feng Qian (JIRA)

modify ws user guide documents ------------------------------ Key: TOOLSDOC-189 URL: https://issues.jboss.org/browse/TOOLSDOC-189 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Feng Qian Assignee: Isaac Rooskov After fix the issue: JBIDE-8490,need to modify the ws docs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
14
0 / 0

[JBoss JIRA] (JBIDE-10415) build problems in Beta1

by Nick Boldt (Created) (JIRA)

build problems in Beta1 ----------------------- Key: JBIDE-10415 URL: https://issues.jboss.org/browse/JBIDE-10415 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, updatesite Affects Versions: 3.3.0.M5 Reporter: Nick Boldt Assignee: Nick Boldt Priority: Blocker Fix For: 3.3.0.M5 Container issue for build problems w/ M5. Check subtasks for component-specific issues. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
5
0 / 0

[JBoss JIRA] (JBDS-1956) get m2eclipse logging under control in JBDS

by Max Rydahl Andersen (Created) (JIRA)

get m2eclipse logging under control in JBDS -------------------------------------------- Key: JBDS-1956 URL: https://issues.jboss.org/browse/JBDS-1956 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: maven Reporter: Max Rydahl Andersen Assignee: Fred Bricon Priority: Critical Fix For: 5.0.0.Beta1 When starting default JBDS installation the console gets *spewed* over with debug info. We should get that under control. What are our options? log to a file ? disable/reduce default log level? missing a plugin to control it or ? something ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
2
0 / 0

[JBoss JIRA] (JBIDE-10232) exploded deploy does not work on windows because of use of File#renameTo

by Jim Sellers (Created) (JIRA)

exploded deploy does not work on windows because of use of File#renameTo ------------------------------------------------------------------------ Key: JBIDE-10232 URL: https://issues.jboss.org/browse/JBIDE-10232 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Environment: JBossAS Tools: Version: 2.3.0.v20111104-1515-H45-M4 Java version: 1.5.0_22, vendor: Sun Microsystems Inc. Java home: C:\devtools\java\jdk1.5.0_22\jre Default locale: en_CA, platform encoding: Cp1252 OS name: "windows xp", version: "5.1", arch: "x86", family: "windows" Reporter: Jim Sellers Assignee: Rob Stryker Setup: in a project on windows with an ear / war / jar in an exploded format and having started the server in debug mode. If you make any changes to a file in the jar, the jar will be rebuilt and try to be deployed. This seems to work but it pops up an error dialog box *every time*. The error message looks like the following: {code} Error renaming C:\devtools\jboss\jboss-4.2.3.GA\server\default\tmp\jbosstoolsTemp\tmp2587902707203199490.jar to C:\devtools\jboss\jboss-4.2.3.GA\server\default\deploy\MyExampleEAR.ear\MyExampleWAR.war\WEB-INF\lib\MyDependantJar-2.3-SNAPSHOT.jar. This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination. You may adjust these settings in the server editor. {code} For the method org.jboss.ide.eclipse.as.core.server.xpl.PublishCopyUtil#safeRename(File,File,int) it calls File#renameTo(File) for moving the file from the temp directory to WEB-INF/lib. From the javadocs for renameTo it says that this might not work if the file in the destination already exists. Possible fixes: # before calling the rename, try to delete on the destination file ( to.delete() ) # org.apache.commons.io.FileUtils#moveFile(File,File) tries to call the renameTo and if that fails it falls back to coping the file to the destination. {code:JAVA|title=Sample Unit test} /* This test needs to be run on windows. */ @Test public void testCopyForWindows() throws IOException { File from = File.createTempFile("source", ".txt"); File to = File.createTempFile("target", ".txt"); File[] files = {from, to}; for (File file : files) { // set for cleanup file.deleteOnExit(); assertTrue("file should exist" + file.getAbsolutePath(), file.exists()); assertTrue("file should be writable" + file.getAbsolutePath(), file.canWrite()); } // if safeRename was not private! assertTrue("should have been able to rename the file", safeRename(from, to, 10)); } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

6
5
0 / 0

[JBoss JIRA] (JBIDE-10218) Run button in toolbar needs to run the newly generated project

by Burr Sutter (Created) (JIRA)

Run button in toolbar needs to run the newly generated project -------------------------------------------------------------- Key: JBIDE-10218 URL: https://issues.jboss.org/browse/JBIDE-10218 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Burr Sutter The Run icon in the Eclipse toolbar is where a new developer (new to JBoss Tools) expects to go directly after he has generated a new project from either File-New or JBoss Central by using one of the archetypes or project examples/quickstarts. This means the generated project needs to be highlighted in the Project Explorer and the Run button should "just work". There is also an issue with Run vs Debug - if the server is in "debug mode" then Run should just assume that is OK and not prompt the user. Run on Server should be the default so the user can use a single click on OK -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

10
19
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 January 2012