February 2012 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-8280) Content assist for JSF 2 should not add managed beans annotated with @ManagedBean when faces-config@metadata-complete="true" in WEB-INF/faces-config.xml

by Denis Golovin (JIRA)

Content assist for JSF 2 should not add managed beans annotated with @ManagedBean when faces-config@metadata-complete="true" in WEB-INF/faces-config.xml -------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8280 URL: https://issues.jboss.org/browse/JBIDE-8280 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF Affects Versions: 3.2.0.CR1, 3.3.0.M1 Reporter: Denis Golovin Assignee: Alexey Kazakov Fix For: 3.3.x According faces-config 2.0 scheme: "Attribute : metadata-complete The metadata-complete attribute defines whether this JavaServer Faces application is complete, or whether the class files available to this module and packaged with this application should be examined for annotations that specify configuration information. This attribute is only inspected on the application configuration resource file located at "WEB-INF/faces-config.xml". The presence of this attribute on any application configuration resource other than the one located at "WEB-INF/faces-config.xml", including any files named using the javax.faces.CONFIG_FILES attribute, must be ignored. If metadata-complete is set to "true", the JavaServer Faces runtime must ignore any annotations that specify configuration information, which might be present in the class files of the application. If metadata-complete is not specified or is set to "false", the JavaServer Faces runtime must examine the class files of the application for annotations, as specified by the specification. If "WEB-INF/faces-config.xml" is not present, the JavaServer Faces runtime will assume metadata-complete to be "false". The value of this attribute will have no impact on runtime annotations such as @ResourceDependency or @ListenerFor. Data Type : boolean Enumerated Values : - true - false" -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

5
7
0 / 0

[JBoss JIRA] (JBIDE-10946) <#noescape> without having seen <#escape> is not necessarily an error

by Chris West (JIRA)

Chris West created JBIDE-10946: ---------------------------------- Summary: <#noescape> without having seen <#escape> is not necessarily an error Key: JBIDE-10946 URL: https://issues.jboss.org/browse/JBIDE-10946 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: FreeMarker Environment: FreeMarker IDE 1.1.0.v20111025-0320-H192-Final Eclipse Java EE IDE for Web Developers. Version: Indigo Release Build id: 20110615-0604 Win7 x64 Java 7 Reporter: Chris West Assignee: Max Rydahl Andersen Currently FreeMarker IDE presents an error for each instance of <#noformat> it encounters, unless it's already seen a <#escape x as x?html> in the same file: {code:xml} <#noformat> ${a.b} ${c} </#noformat> {code} {noformat} Error in template: foo.ftl on line 1, column 1 noescape with no matching escape encountered. {noformat} This template may have been included: {code:xml} <#escape x as x?html> <#include "foo.ftl"> </#escape> {code} ... or may have been wrapped in a loader which does effectively the same thing, for example, http://watchitlater.com/blog/2011/10/default-html-escape-using-freemarker/ This results in many spurious error reports. Please allow me to disable these. -- 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

14 years

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6138) create an import wizard for the jBPM3 examples

by Koen Aers (JIRA)

create an import wizard for the jBPM3 examples ---------------------------------------------- Key: JBIDE-6138 URL: https://jira.jboss.org/jira/browse/JBIDE-6138 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jbpm Reporter: Koen Aers Assignee: Koen Aers Fix For: 3.1.1, 3.1.x, 3.2.next -- 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

3
10
0 / 0

[JBoss JIRA] (JBIDE-9939) When you create a new appliaction, it should get selected in the list of applications

by Andre Dietisheim (Created) (JIRA)

When you create a new appliaction, it should get selected in the list of applications ------------------------------------------------------------------------------------- Key: JBIDE-9939 URL: https://issues.jboss.org/browse/JBIDE-9939 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 3.3.0.M4 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M4 Attachments: new-app.png If you create a new application, it should get selected in the list of available applications, as soon as you close the creation dialog. !new-app.png! How to reproduce: 1) ASSERT: have an OpenShift Express account and domain 2) EXECUTE: open up the appliaction wizard 3) EXECUTE: on the "Application selection" page, hit "New", select the appropriate settings and hit "Finish" Result: There's no selection in the appliaction table. Expected result: The freshly create app is selected. -- 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

14 years

5
5
0 / 0

[JBoss JIRA] (JBDS-2017) Investigate usage of Jacoco report file as Usage collector

by Mickael Istria (JIRA)

Mickael Istria created JBDS-2017: ------------------------------------ Summary: Investigate usage of Jacoco report file as Usage collector Key: JBDS-2017 URL: https://issues.jboss.org/browse/JBDS-2017 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build, P2 Enabled Product, Usage Reporting Reporter: Mickael Istria Assignee: Nick Boldt Using the jacoco java.agent is pretty simple to set up and generates a coverage report file without affecting performances. We could think about starting JBDS with this java.agent and consume the Jacoco report files to get "technical" usage report. Same could apply to JBoss tools by using p2 touchpoint to modify eclipse.ini when installing an IU: http://pweclipse.blogspot.com/2012/02/p2-can-update-your-eclipseini.html -- 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

14 years

3
11
0 / 0

[JBoss JIRA] Created: (JBIDE-9264) support openshift express and openshift flex

by Andre Dietisheim (JIRA)

support openshift express and openshift flex -------------------------------------------- Key: JBIDE-9264 URL: https://issues.jboss.org/browse/JBIDE-9264 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Affects Versions: 3.3.0.M3 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] (JBIDE-9936) rename jboss 6.0 runtime to 6.x

by Rastislav Wagner (Created) (JIRA)

rename jboss 6.0 runtime to 6.x ------------------------------- Key: JBIDE-9936 URL: https://issues.jboss.org/browse/JBIDE-9936 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime detection Affects Versions: 3.2.x Reporter: Rastislav Wagner Assignee: Snjezana Peco Adding new server runtime enviroment has Jboss 6.0 choice, not 6.x -- 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

14 years

5
5
0 / 0

[JBoss JIRA] (JBIDE-9917) Deadlock in JarAccessFactory.getJarAccess()

by Viacheslav Kabanovich (Created) (JIRA)

Deadlock in JarAccessFactory.getJarAccess() ------------------------------------------- Key: JBIDE-9917 URL: https://issues.jboss.org/browse/JBIDE-9917 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 3.3.0.M3 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M4 HashMap should never be invoked without synchronization if there is a chance that it may be accessed by different threads. Thread [Worker-0] (Suspended) HashMap<K,V>.get(Object) line: 320 JarAccessFactory.getJarAccess(String, JarSystemImpl) line: 11 JarSystemImpl.getJarAccess() line: 32 JarSystemImpl.getChildByPathPart(String) line: 74 JarSystemImpl(XModelObjectImpl).getChildByPath(String) line: 334 TaglibMapping.findTldsInJar(XModelObject) line: 225 TaglibMapping.findTldsInJars() line: 209 TaglibMapping.revalidate(XModelObject) line: 85 JSFWatcherContributor.updateProject() line: 49 Watcher.updateAll() line: 106 Watcher.access$0(Watcher) line: 89 Watcher$WatcherRunnable.run() line: 47 XJob.runInWorkspace(IProgressMonitor) line: 178 XJob(InternalWorkspaceJob).run(IProgressMonitor) line: 38 Worker.run() line: 54 Thread [Worker-7] (Suspended) HashMap<K,V>.get(Object) line: 320 JarAccessFactory.getJarAccess(String, JarSystemImpl) line: 11 JarSystemImpl.getJarAccess() line: 32 JarSystemImpl.getChildByPathPart(String) line: 74 JarSystemImpl(XModelObjectImpl).getChildByPath(String) line: 334 ClassPathMonitor.process() line: 68 JSF2ProjectBuilder.build(int, Map<String,String>, IProgressMonitor) line: 101 KbBuilder.buildExtensionModels(int, Map, IProgressMonitor) line: 191 KbBuilder.build(int, Map<String,String>, IProgressMonitor) line: 136 BuildManager$2.run() line: 728 SafeRunner.run(ISafeRunnable) line: 42 BuildManager.basicBuild(int, IncrementalProjectBuilder, Map<String,String>, MultiStatus, IProgressMonitor) line: 199 BuildManager.basicBuild(IBuildConfiguration, int, IBuildContext, ICommand[], MultiStatus, IProgressMonitor) line: 239 BuildManager$1.run() line: 292 SafeRunner.run(ISafeRunnable) line: 42 BuildManager.basicBuild(IBuildConfiguration, int, IBuildContext, MultiStatus, IProgressMonitor) line: 295 BuildManager.basicBuildLoop(IBuildConfiguration[], IBuildConfiguration[], int, MultiStatus, IProgressMonitor) line: 351 BuildManager.build(IBuildConfiguration[], IBuildConfiguration[], int, IProgressMonitor) line: 374 AutoBuildJob.doBuild(IProgressMonitor) line: 143 AutoBuildJob.run(IProgressMonitor) line: 241 Worker.run() line: 54 -- 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

14 years

4
5
0 / 0

[JBoss JIRA] (JBIDE-10338) org.jboss.tools.common.mylyn depends on atlassian jira connector but does not force it to be installed automatically?

by Nick Boldt (Created) (JIRA)

org.jboss.tools.common.mylyn depends on atlassian jira connector but does not force it to be installed automatically? --------------------------------------------------------------------------------------------------------------------- Key: JBIDE-10338 URL: https://issues.jboss.org/browse/JBIDE-10338 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: common/jst/core, updatesite, UpStream Affects Versions: 3.3.0.M5 Reporter: Nick Boldt Assignee: Alexey Kazakov Fix For: 3.3.0.M5 See parent jira JBIDE-10336 for steps to reproduce. Full log is here: https://issues.jboss.org/secure/attachment/12349551/eclipse.log.Sun_Dec4_... !ENTRY org.eclipse.mylyn.tasks.ui 4 0 2011-12-04 10:29:56.596 !MESSAGE Could not load repository template extension contributed by org.jboss.tools.common.mylyn with connectorKind jira -- 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

14 years

5
12
0 / 0

[JBoss JIRA] (JBIDE-10796) remove org.eclipse.pde.api.tools.ee.fragments from target platforms

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-10796: ---------------------------------- Summary: remove org.eclipse.pde.api.tools.ee.fragments from target platforms Key: JBIDE-10796 URL: https://issues.jboss.org/browse/JBIDE-10796 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, target-platform, updatesite Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.Beta1 Due to https://bugs.eclipse.org/bugs/show_bug.cgi?id=370643, we must remove the org.eclipse.pde.api.tools.ee.fragments feature from the JBT target platform. -- 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

14 years

1
6
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 February 2012