April 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-9688) Add JBoss public repository to list of default repositories in Eclipse

by Rob Cernich (JIRA)

Add JBoss public repository to list of default repositories in Eclipse ---------------------------------------------------------------------- Key: JBIDE-9688 URL: https://issues.jboss.org/browse/JBIDE-9688 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: maven Reporter: Rob Cernich Assignee: Fred Bricon Priority: Minor M2e exposes an extension point, which allows plugins to contribute repositories to be indexed. Automatically registering the JBoss repository seems like a sensible thing for JBoss Tools. This would allow the user to access the JBoss public repository from the tooling (e.g. add dependency) without requiring them to add the JBoss public repository to their settings.xml file. Of course, the user would still need to ensure that the repository was correctly configured within their pom so the project will build correctly. The following is all that is required (in plugin.xml): <extension point="org.eclipse.m2e.core.indexes"> <index indexId="JBOSS_NEXUS" isShort="true" repositoryUrl="http://repository.jboss.org/nexus/content/groups/public"> </index> </extension> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

7
12
0 / 0

[JBoss JIRA] (JBDS-2030) Disabled modal usage dialogs from extras plugins by default

by Jiri Peterka (JIRA)

Jiri Peterka created JBDS-2030: ---------------------------------- Summary: Disabled modal usage dialogs from extras plugins by default Key: JBDS-2030 URL: https://issues.jboss.org/browse/JBDS-2030 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build, updatesite Affects Versions: 5.0.0.M5 Environment: JBDS 5.0.0.M5 Reporter: Jiri Peterka Assignee: Nick Boldt Fix For: 5.0.0.Beta1 Usage analysis modal dialogs from extras plugins are quire annoying. Mainly in situations when there is more then one and the one with focus is hidden behind the other. It would be nice if appearing of these dialogs could be disabled by default in JBDS. Namely these: * subclipse usage * atlasian connector -- 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, 11 months

5
18
0 / 0

[JBoss JIRA] (JBIDE-11468) Set up Jenkins unstable/yellow builds

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-11468: -------------------------------------- Summary: Set up Jenkins unstable/yellow builds Key: JBIDE-11468 URL: https://issues.jboss.org/browse/JBIDE-11468 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Build/Releng Reporter: Mickael Istria Assignee: Mickael Istria Fix For: 3.3.0.Beta3 In order to have a better readability of build status, we should do the necessary stuff to introduce "unstable/yellow" builds. This build status shows that the only issue in build is failing tests. -- 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, 11 months

2
5
0 / 0

[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, 11 months

9
26
0 / 0

[JBoss JIRA] (JBIDE-11376) --tests has a dependency on jbpm.detector whereas they are no part of the same stream, and dependency is in the other direction

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-11376: -------------------------------------- Summary: --tests has a dependency on jbpm.detector whereas they are no part of the same stream, and dependency is in the other direction Key: JBIDE-11376 URL: https://issues.jboss.org/browse/JBIDE-11376 Project: Tools (JBoss Tools) Issue Type: Bug Components: testing Reporter: Mickael Istria Assignee: Max Rydahl Andersen Priority: Critical Since SOA runtime detector where move to a runtime-soa component, and that dependency was reversed, it is not possible to have tests/ dependending on jbpm.detector -- 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, 11 months

4
5
0 / 0

[JBoss JIRA] (JBDS-2083) izpack installer fails to compile in build-universal-installer step

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2083: -------------------------------- Summary: izpack installer fails to compile in build-universal-installer step Key: JBDS-2083 URL: https://issues.jboss.org/browse/JBDS-2083 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 5.0.0.Beta3 Reporter: Nick Boldt Assignee: Denis Golovin Priority: Blocker Fix For: 5.0.0.Beta3 {code} build-universal-installer: [echo] Building installer for ${platform} platform... [echo] path to ${archive-config} platform zip /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta3/201204011814/jbds-all-package/jbdevstudio-5.0.0.v201204011814N-H1098-Beta3-${archive-config}.zip init-properties: buildcustompanels: [echo] Building panels ... [echo] Build properties written to /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta3/201204011814/installer/build/../../jbds-echoproperties.txt [mkdir] Created dir: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta3/201204011814/installer/build/classes [mkdir] Created dir: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta3/201204011814/installer/build/izpack-panels [unjar] Expanding: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/IzPack-4.3.4/lib/standalone-compiler.jar into /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta3/201204011814/installer/build/izpack-panels [javac] Compiling 26 source files to /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta3/201204011814/installer/build/classes [javac] /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta3/201204011814/installer/src/panels/com/izforge/izpack/installer/Unpacker.java:28: cannot find symbol [javac] symbol : class ConsoleCommandException [javac] location: package com.jboss.jbds.installer [javac] import com.jboss.jbds.installer.ConsoleCommandException; [javac] ^ [javac] /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta3/201204011814/installer/src/panels/com/jboss/jbds/installer/P2DirectorStarterListener.java:75: cannot find symbol [javac] symbol : class ConsoleCommandException [javac] location: interface com.jboss.jbds.installer.P2DirectorStarterListener.ConsoleCommand [javac] void execute() throws ConsoleCommandException; [javac] ^ [javac] /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta3/201204011814/installer/src/panels/com/jboss/jbds/installer/P2DirectorStarterListener.java:76: cannot find symbol [javac] symbol : class ConsoleCommandException [javac] location: interface com.jboss.jbds.installer.P2DirectorStarterListener.ConsoleCommand [javac] void execute(ResponseListener listener) throws ConsoleCommandException; [javac] ^ [javac] /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta3/201204011814/installer/src/panels/com/jboss/jbds/installer/P2DirectorStarterListener.java:87: cannot find symbol [javac] symbol : class ConsoleCommandException [javac] location: class com.jboss.jbds.installer.P2DirectorStarterListener.BaseConsoleCommand [javac] public void execute() throws ConsoleCommandException { [javac] ^ [javac] /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta3/201204011814/installer/src/panels/com/jboss/jbds/installer/P2DirectorStarterListener.java:91: cannot find symbol [javac] symbol : class ConsoleCommandException [javac] location: class com.jboss.jbds.installer.P2DirectorStarterListener.BaseConsoleCommand [javac] public void execute(ResponseListener listener) throws ConsoleCommandException { [javac] ^ [javac] /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta3/201204011814/installer/src/panels/com/jboss/jbds/installer/P2DirectorStarterListener.java:97: cannot find symbol [javac] symbol : class ConsoleCommandException [javac] location: class com.jboss.jbds.installer.P2DirectorStarterListener.BaseConsoleCommand [javac] throw new ConsoleCommandException(rt.getErrCode(),result); [javac] ^ [javac] /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta3/201204011814/installer/src/panels/com/izforge/izpack/installer/Unpacker.java:194: cannot find symbol [javac] symbol : class ConsoleCommandException [javac] location: class com.izforge.izpack.installer.Unpacker [javac] } catch (ConsoleCommandException ex) { [javac] ^ [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 7 errors {code} https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo... -- 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, 11 months

3
2
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, 11 months

5
31
0 / 0

[JBoss JIRA] (JBIDE-11684) EAP 5.0. ER6 Maven artefacts are not compatible with JBT Java EE Web Project

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-11684: ------------------------------------ Summary: EAP 5.0. ER6 Maven artefacts are not compatible with JBT Java EE Web Project Key: JBIDE-11684 URL: https://issues.jboss.org/browse/JBIDE-11684 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.3.0.Beta3 Environment: JBT 3.3.0.beta3-trunk, L64, EAP 6.0.ER6 (as and mvn repo) Reporter: Jiri Peterka Fix For: 3.3.0.Beta3 -- 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, 11 months

8
28
0 / 0

[JBoss JIRA] (JBIDE-11207) Error logged from Forge Plugin:

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-11207: ----------------------------------- Summary: Error logged from Forge Plugin: Key: JBIDE-11207 URL: https://issues.jboss.org/browse/JBIDE-11207 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Burr Sutter I pasted in the following chunk into the Forge window: entity --named Customer --package ~.domain; field string --named firstName; field string --named lastName; field temporal --type DATE --named birthDate; and the result was Java Model Exception: Java Model Status [DATE birthDate [in Customer [in [Working copy] Customer.java [in com.burrsutter.testforge1.domain [in src/main/java [in testforge1]]]]] does not exist] at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:495) at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:529) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:255) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:241) at org.eclipse.jdt.internal.core.SourceRefElement.getSourceRange(SourceRefElement.java:218) at org.jboss.tools.forge.ui.console.FieldPostProcessor.postProcess(FieldPostProcessor.java:36) at org.jboss.tools.forge.ui.console.ForgeCommandProcessor$1.run(ForgeCommandProcessor.java:55) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) -- 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, 11 months

4
6
0 / 0

[JBoss JIRA] (JBIDE-11244) Auto-discover all the modules and add them to the configuration on GWT project import

by Jonathan Fuerth (JIRA)

Jonathan Fuerth created JBIDE-11244: --------------------------------------- Summary: Auto-discover all the modules and add them to the configuration on GWT project import Key: JBIDE-11244 URL: https://issues.jboss.org/browse/JBIDE-11244 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Jonathan Fuerth You can see why this would be desirable at 2:45 of the screencast at http://www.screencast.com/t/sFmXVlaBUvW Note that Errai Maven builds are configured to auto-discover modules too, so this would match existing users' expectations. -- 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, 11 months

6
25
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 2012