June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17698) Server view could show all deployed modules, obtained from the server

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17698?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-17698: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Server view could show all deployed modules, obtained from the server > --------------------------------------------------------------------- > > Key: JBIDE-17698 > URL: https://issues.jboss.org/browse/JBIDE-17698 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Optional > Fix For: 4.5.x > > > Pavol Srna pointed out to me that when he deletes a project in workspace while it's deployed on a running AS7, it disappears from the server view and he can't undeploy it from Eclipse. > I understand that this is somewhat expected, but we have a suggestion: Could the server view get its deployed modules from the server via the management api and use that to show the modules? Similar to what the web console of AS7/WildFly/EAP6 shows. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16144) Editing files outside the workspace and served by Live Reload fails in Windows

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16144?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-16144: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Editing files outside the workspace and served by Live Reload fails in Windows > ------------------------------------------------------------------------------ > > Key: JBIDE-16144 > URL: https://issues.jboss.org/browse/JBIDE-16144 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.1.CR1 > Environment: Windows 7 - 64b, JDK 1.7.0_45 x86 > Reporter: Fred Bricon > Fix For: 4.5.x > > > * In workspace preferences > General > Workspace > enable "Refresh using native hooks or polling" > * Import https://github.com/jbosstools/jbosstools-documentation/tree/master/whatsnew as a project > * Right-click on an html file, open with > Web Browser via Live Reload > * Open the text file in a text editor (sublime text for me),change something, save -> browser reloads eventually > * Make a second change : file can't be saved "Access denied" > * Wait 1 minute, try again, it works. > * repeat, fail ... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16638) Improve UI of Deployment Scanner settings

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16638?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-16638: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Improve UI of Deployment Scanner settings > ----------------------------------------- > > Key: JBIDE-16638 > URL: https://issues.jboss.org/browse/JBIDE-16638 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Alpha2 > Environment: JBDS 8.0.0.Alpha2b B71 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.x > > Attachments: scanner-options-mockup.png, scanner-options.png > > > Looking at the new options introduced in JBIDE-15287, I don't quite like to look of it. > Let me know if you disagree, but using "(default)" in a field that's supposed to take numbers is not very nice. > !scanner-options.png! > Instead, I propose adding a checkbox in front of the options: > !scanner-options-mockup.png! > Excuse the ugly picture, but the idea is that if the checkbox is not checked, the field is greyed out (and empty). If it is checked, a value is expected. WDYT? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-4920) New Hibernate Console Configuration File (cfg.xml) file doesn't save state for Classpath tab in New Hibernate Console Configuration Step after '<Back' is pressed

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-4920?page=com.atlassian.jira.plugin... ] Jeff MAURY updated JBIDE-4920: ------------------------------ Fix Version/s: 4.5.x (was: 4.5.0.AM1) > New Hibernate Console Configuration File (cfg.xml) file doesn't save state for Classpath tab in New Hibernate Console Configuration Step after '<Back' is pressed > ----------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-4920 > URL: https://issues.jboss.org/browse/JBIDE-4920 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 3.1.0.M4 > Reporter: Denis Golovin > Assignee: Koen Aers > Priority: Trivial > Fix For: 4.5.x > > > 1. EXECUTE: Create Java Project > 2. EXECUTE: Select Java Project from step 1 and invoke New Hibernate Configuration file Wizard > 3. EXECUTE: Go through all steps to New Hibernate Console Configuration step > 4. EXECUTE: Select 'Classpath' tab, remove 'default classpath' entry > 5. EXECUTE: Press '<Back' > 6. EXECUTE: Press 'Next>' and select 'Classpath' tab > 7. ASSERT: State is the same as it was after step 4 above executed > Now it restores default values -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20838) Misleading dialog displayed to user when installing example and dependent packages

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20838?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20838: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Misleading dialog displayed to user when installing example and dependent packages > ---------------------------------------------------------------------------------- > > Key: JBIDE-20838 > URL: https://issues.jboss.org/browse/JBIDE-20838 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.CR2 > Reporter: Len DiMaggio > Priority: Minor > Fix For: 4.5.x > > Attachments: Screenshot.png > > > Steps to recreate: > * After a clean install, from Central install create a project such as a Java EE project > * Observe the dialog in the attached screenshot - after the required packages are installed the user is returned to Central - as a user I would have expected to have had the project created automatically after the required packages were installed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18352) Include a working JAX-WS configurator in the m2e catalog

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18352?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18352: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Include a working JAX-WS configurator in the m2e catalog > -------------------------------------------------------- > > Key: JBIDE-18352 > URL: https://issues.jboss.org/browse/JBIDE-18352 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Fred Bricon > Fix For: 4.5.x > > > there are compilation/build errors when importing projects using the jaxws maven plugin (see javaee7-samples case on JBDS-2847), because the project is not properly configured during the import. Generated code from the project's WSDL would be missing. > The known work-around is to invoke maven from command-line to have the code generated. > Having a fine-tuned, working m2e configurator (ie, tuned for incremental builds and not triggering a full interface generation when some unrelated file is edited) would fix the problem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14503) LiveReload server information in the Servers View

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14503?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-14503: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > LiveReload server information in the Servers View > ------------------------------------------------- > > Key: JBIDE-14503 > URL: https://issues.jboss.org/browse/JBIDE-14503 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: livereload > Affects Versions: 4.1.0.Beta1 > Reporter: Xavier Coulon > Fix For: 4.5.x > > > The LiveReload server should display information in the Server Views, such as: > - number of connected browsers > - proxy enabled > - remote connections enabled > - script injection enabled > - the IP address the Proxy is listening on -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18096) could not complete update project configuration - illegalargumentexception

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18096?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18096: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > could not complete update project configuration - illegalargumentexception > -------------------------------------------------------------------------- > > Key: JBIDE-18096 > URL: https://issues.jboss.org/browse/JBIDE-18096 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Labels: f2f2014 > Fix For: 4.5.x > > > while trying to fix import of javaee-samples I bumped into this happening when running update project configuration. > java.lang.IllegalArgumentException > at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.removeProjectFacet(FacetedProjectWorkingCopy.java:876) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:309) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339) > at org.eclipse.m2e.wtp.WebProjectConfiguratorDelegate.configure(WebProjectConfiguratorDelegate.java:150) > at org.eclipse.m2e.wtp.AbstractProjectConfiguratorDelegate.configureProject(AbstractProjectConfiguratorDelegate.java:93) > at org.eclipse.m2e.wtp.WTPProjectConfigurator.configure(WTPProjectConfigurator.java:70) > at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:477) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:470) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration0(ProjectConfigurationManager.java:408) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:321) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:1) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96) > at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1344) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:318) > at org.eclipse.m2e.core.ui.internal.UpdateMavenProjectJob.runInWorkspace(UpdateMavenProjectJob.java:77) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > It happened on ~100 projects so was quite invasive ;/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13799) Source Lookup enhancements

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13799?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-13799: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Source Lookup enhancements > -------------------------- > > Key: JBIDE-13799 > URL: https://issues.jboss.org/browse/JBIDE-13799 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Fred Bricon > Fix For: 4.5.x > > > The PR includes the following enhancements: > - AS 7.2/EAP 6.1 are now recognized correctly > - the fix for the issue caused by changing the editor ID for ClassFileEdtor in 3.8/4.2 > - the fix for the ConcurrentModificationException exception > - included libraries can be filtered - jsf 1.2 and hibernate 3 will be excluded by default for JBoss AS Container > - JBoss Runtimes now can be included in the Java Search (this feature has been implemented in a similar way to adding PDE plugins to the Java Search) > - JBoss Java Project Source Container > See http://screencast.com/t/39LHqYx5m > Screenshot shows debugging the WeldBootstrap class in JBoss AS 7.1 and JBoss AS 7.2. > Note: > You have to have some deployment on the servers in order the WeldBootstrap class to be created. > You can add more JBoss servers to the Java Search, but it is the best to use only one at a time because of the performance reason. > The "Automatically add the JBoss Maven source container to all JBoss AS launch configurations" and "Include the following JBoss Servers in the Java Search" checkboxes aren't related. The first checkbox adds the source container that enables finding a Java source file when debugging, the second enables finding a Java source file using the Java Search (using the "Open type" command, for instance). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15174) Improved work with datatools connection profiles for various projects using hibernate/jpa

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15174?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-15174: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Improved work with datatools connection profiles for various projects using hibernate/jpa > ----------------------------------------------------------------------------------------- > > Key: JBIDE-15174 > URL: https://issues.jboss.org/browse/JBIDE-15174 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 4.1.0.Beta2 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.5.x > > > When working with JPA projects or examples from Central it's necessary to create JPA connection profile. I assume I already have some kind of configuration - either hibernate configuration, or connection directly defined in persistence.xml or defined data source. Still hibernate tooling and eclipse.datatools is complaining that it needs to define connection profile. You have to create a connection configuration again for connection profile to have working tooling. It leads to multiple configurations or you have to reconfigure a project to use eclipse.datatools connection profiles. > What I would like to see is some mechanism howto easily create connection profiles: > * the seamless way would be some support for our examples to generate connection profiles when they are imported (or at least to help with that) > * and some support for hibernate configuration, persistence.xml and ds when creating connection profiles. > Both features might need some eclipse.datatools contributions. But currently these two worlds (hibernate/jpa tooling and datatools are not very well integrated each other). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

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 June 2017