July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17816) Default values for Project name, Archetype ID etc. are not filled for archetype project wizards

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-17816: ---------------------------------- Summary: Default values for Project name, Archetype ID etc. are not filled for archetype project wizards Key: JBIDE-17816 URL: https://issues.jboss.org/browse/JBIDE-17816 Project: Tools (JBoss Tools) Issue Type: Bug Components: central, project-examples Affects Versions: 4.2.0.Beta3 Reporter: Radim Hopp In JBT 4.2.0.Beta2 and earlier version New project example wizard for archetypes (HTML5 project, Richfaces project, ...) fileld lot of fields automatically. Now almost all fields are left blank (Project Name, Package, Group Id, Artifact Id) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17300) NPE when starting a remote server with no launch or shutdown command

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17300?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17300: ------------------------------------- This is intentional. You cannot have a blank startup command. If you wish to not have any startup command, you should mark your servers as externally managed... not have a blank startup command. When a blank or whitespace-only startup or shutdown command is present, the default will be used instead. > NPE when starting a remote server with no launch or shutdown command > -------------------------------------------------------------------- > > Key: JBIDE-17300 > URL: https://issues.jboss.org/browse/JBIDE-17300 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Environment: Eclipse Luna M6 > JBT nightly 4.2.0-SNAPSHOT (Beta2-v20140519-0530-B8820) > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta3 > > > When you try to start a remote AS7, you get a NPE popup window with no details. > This is in the workspace log: > {code} > !ENTRY org.jboss.ide.eclipse.as.rse.core 4 0 2014-05-19 13:55:19.968 > !MESSAGE > !STACK 0 > java.lang.NullPointerException > at java.util.regex.Matcher.getTextLength(Matcher.java:1283) > at java.util.regex.Matcher.reset(Matcher.java:309) > at java.util.regex.Matcher.<init>(Matcher.java:229) > at java.util.regex.Pattern.matcher(Pattern.java:1093) > at org.eclipse.rse.internal.services.shells.TerminalServiceHostShell.writeToShell(TerminalServiceHostShell.java:158) > at org.jboss.ide.eclipse.as.rse.core.RSEHostShellModel$ServerShellModel.createStartupShell(RSEHostShellModel.java:106) > at org.jboss.ide.eclipse.as.rse.core.StandardRSEStartLaunchDelegate.executeRemoteCommand(StandardRSEStartLaunchDelegate.java:126) > at org.jboss.ide.eclipse.as.rse.core.StandardRSEJBossStartLaunchDelegate.actualLaunch(StandardRSEJBossStartLaunchDelegate.java:39) > at org.jboss.ide.eclipse.as.rse.core.StandardRSEStartLaunchDelegate.launch(StandardRSEStartLaunchDelegate.java:59) > at org.jboss.ide.eclipse.as.rse.core.subsystems.RSECommandLineLaunchController.launch(RSECommandLineLaunchController.java:73) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} > One other symptom is that when I open the Launch config from Server editor, both the fields for Startup and Shutdown scripts are empty - shouldn't they show the calculated script? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3056) Provide JBDS Central Early Access zip for offline install?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3056?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3056: ------------------------------------------- no - early access is *NOT* the same as central discovery. It is content that can be adding AND updating things in JBDS plugins. It will change over time and no, we dont have obligations to provide offline install of this for every conceivable version at this time. Thus in complete agreement that this should be rejected. > Provide JBDS Central Early Access zip for offline install? > ---------------------------------------------------------- > > Key: JBDS-3056 > URL: https://issues.jboss.org/browse/JBDS-3056 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build, central, updatesite > Affects Versions: 8.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.0.0.Beta2 > > > Do we want to provide an offline zip of the Central Early Access content? We already build it... but do we want to provide it? > [~burrsutter] [~maxandersen] [~mmurray] [~mmusaji] What do you think? This is like providing the JBDS (Core) Central Zip, except that this is Early Access content, and is therefore NOT supported. > Link to zip (if we want it) would go here: > http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_ma... > and here once published, would be on this page: > http://www.jboss.org/products/devstudio/download/ > Documentation on the new EA content is here: > https://devstudio.jboss.com/updates/8.0-staging/central/ > (If you have copy changes for the above page, please open a new JBDS Task JIRA.) > Please +1 or -1 the idea of publishing a *jboss-devstudio-8.0.0.x-updatesite-central-earlyaccess.zip*. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3088) BrowserSim crashes when accessing deployed Ticket Monster example

by Emil Cervenan (JIRA)

Emil Cervenan created JBDS-3088: ----------------------------------- Summary: BrowserSim crashes when accessing deployed Ticket Monster example Key: JBDS-3088 URL: https://issues.jboss.org/browse/JBDS-3088 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: browsersim Affects Versions: 8.0.0.Beta2 Reporter: Emil Cervenan When accessing deployed Ticket Monster example in JBDS Browsersim it will crash. 1. clone TiMo (https://github.com/jboss-developer/ticket-monster) 2. import into JBDS 3. Start EAP 4. Deploy TiMo 5. Show In > BrowserSim Console: <terminated> BrowserSim [Java Application] /usr/lib/jvm/java-1.7.0-openjdk-.../bin/java java version "1.7.0_55" OpenJDK Runtime Environment (fedora-2.4.7.4.fc20-x86_64 u55-b13) OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17300) NPE when starting a remote server with no launch or shutdown command

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17300?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-17300: ---------------------------------- Labels: respin-a (was: ) > NPE when starting a remote server with no launch or shutdown command > -------------------------------------------------------------------- > > Key: JBIDE-17300 > URL: https://issues.jboss.org/browse/JBIDE-17300 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Environment: Eclipse Luna M6 > JBT nightly 4.2.0-SNAPSHOT (Beta2-v20140519-0530-B8820) > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta3 > > > When you try to start a remote AS7, you get a NPE popup window with no details. > This is in the workspace log: > {code} > !ENTRY org.jboss.ide.eclipse.as.rse.core 4 0 2014-05-19 13:55:19.968 > !MESSAGE > !STACK 0 > java.lang.NullPointerException > at java.util.regex.Matcher.getTextLength(Matcher.java:1283) > at java.util.regex.Matcher.reset(Matcher.java:309) > at java.util.regex.Matcher.<init>(Matcher.java:229) > at java.util.regex.Pattern.matcher(Pattern.java:1093) > at org.eclipse.rse.internal.services.shells.TerminalServiceHostShell.writeToShell(TerminalServiceHostShell.java:158) > at org.jboss.ide.eclipse.as.rse.core.RSEHostShellModel$ServerShellModel.createStartupShell(RSEHostShellModel.java:106) > at org.jboss.ide.eclipse.as.rse.core.StandardRSEStartLaunchDelegate.executeRemoteCommand(StandardRSEStartLaunchDelegate.java:126) > at org.jboss.ide.eclipse.as.rse.core.StandardRSEJBossStartLaunchDelegate.actualLaunch(StandardRSEJBossStartLaunchDelegate.java:39) > at org.jboss.ide.eclipse.as.rse.core.StandardRSEStartLaunchDelegate.launch(StandardRSEStartLaunchDelegate.java:59) > at org.jboss.ide.eclipse.as.rse.core.subsystems.RSECommandLineLaunchController.launch(RSECommandLineLaunchController.java:73) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} > One other symptom is that when I open the Launch config from Server editor, both the fields for Startup and Shutdown scripts are empty - shouldn't they show the calculated script? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17465) Should org.jboss.tools.as.test.core test EAP 6.2 and 6.3?

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17465?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17465: ------------------------------------- The only tests (as far as I can see) that require actual installations are the management tests. I believe if possible these should be moved to a component-specific integration location, such as jbosstools-server/as/tests/itest or something like this, which are only run once a week or manually. Discussion on this can follow on list. > Should org.jboss.tools.as.test.core test EAP 6.2 and 6.3? > --------------------------------------------------------- > > Key: JBIDE-17465 > URL: https://issues.jboss.org/browse/JBIDE-17465 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 4.2.0.Beta3 > > > Looking in org.jboss.tools.as.test.core/pom.xml I see you test for & with EAP 6.1 but not 6.2 or 6.3. > https://github.com/jbosstools/jbosstools-server/blob/master/as/tests/org.... > Should that be updated to include 6.2 (now available) and 6.3 (in a month or so when it's released) ? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17396) Unable to discover version of WF 8.1.0 patched build

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17396?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17396. --------------------------------- Verified in JBDS 8.0.0.Beta3 B172 > Unable to discover version of WF 8.1.0 patched build > ----------------------------------------------------- > > Key: JBIDE-17396 > URL: https://issues.jboss.org/browse/JBIDE-17396 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.Beta3 > > > Creating a server/runtime out of a patch-build wildfly8.1.0.CR4 cannot correctly determine the version of the given home directory. > The reason for this bug is that the class in charge of discovering a server version is looking for a jar that can properly give the versioning information. For wildfly, we are looking to introspect the jar modules/system/layers/org/jboss/as/server/main/*.jar. And we are looking for the manifest.mf property key: JBossAS-Release-Version > Currently, trying to introspect this jar fails, because the jar is an invalid jar file. > It must be recognized that there is now no safe way / agreed-upon API to determine the version of a given server installation when the server is stopped. > There are options: > 1) We respect the module structure / overlay layout and simply look for the correct module folder for "org.jboss.as.server", or > 2) We agree to one single file that will be updated and hold the version information for a given project or product release. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17740) Cannot deploy git-based project to OpenShift

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17740?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17740: --------------------------------------------- afaics this is expected behavior if you import a maven project it will generate .project and other eclipse files possibly resulting in a dirty project. git on command line wont allow you either. > Cannot deploy git-based project to OpenShift > -------------------------------------------- > > Key: JBIDE-17740 > URL: https://issues.jboss.org/browse/JBIDE-17740 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta3 > > Attachments: cannot-create-server-adapter.png, import-failed-uncommitted-changes.png, import.png > > > It is not possible to deploy existing git based project to the OpenShift instance. What's going to happen is that new OpenShift project is created, but existing git project is not merged. As result there is a project based on basic cartridge and not on existing project. There is a issue with git changes - uncommitted changes required to commit first, but it is not possible bcs. remote is still set to the old one git remote. > See log > {code} > !ENTRY org.jboss.tools.openshift.express.ui 4 0 2014-07-02 08:52:28.848 > !MESSAGE Could not import project to the workspace. > !STACK 0 > org.jboss.tools.openshift.express.internal.ui.UnCommittedChangesException: The project jboss-javaee6-webapp has uncommitted changes. Please commit those changes first. > at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.MergeIntoGitSharedProject.execute(MergeIntoGitSharedProject.java:97) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizardModel.mergeIntoGitSharedProject(OpenShiftApplicationWizardModel.java:186) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizard$ImportJob.runInWorkspace(OpenShiftApplicationWizard.java:376) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} > Error shell: > !import.png! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17798) compile failure in jbosstools-server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17798?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17798. --------------------------------- Recent builds are blue, closing. > compile failure in jbosstools-server > ------------------------------------ > > Key: JBIDE-17798 > URL: https://issues.jboss.org/browse/JBIDE-17798 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: Daniel Azarov > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.2.0.Beta3 > > > org.jboss.tools.jmx.jvmmonitor.internal.core.cpu.CpuProfiler > {code} > /* > * @see ICpuProfiler#getSamplingPeriod() > */ > @Override > public Integer getSamplingPeriod() { > IMBeanServer s = jvm.getMBeanServer(); > <<<<<<< HEAD > if( s != null && s instanceof IProfilingMBeanServer) > return ((IProfilingMBeanServer)s).getSamplingPeriod(); > ======= > if( s != null && s instanceof IProfilingMBeanServer) { > return ((IProfilingMBeanServer)s).getSamplingPeriod(); > } > >>>>>>> JBIDE-17311 - moving the jvmmonitor agent code into our plugins folder. > return -1; > } > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17815) Edit Maven Repository dialog invokes Maven Repositories dialog even when Cancel is pressed

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-17815: ---------------------------------- Summary: Edit Maven Repository dialog invokes Maven Repositories dialog even when Cancel is pressed Key: JBIDE-17815 URL: https://issues.jboss.org/browse/JBIDE-17815 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 4.2.0.Beta2 Reporter: Radim Hopp Clicking "Cancel" in AddRepositoryDialog does the same as clicking OK -> invokes ConfigureMavenRepositoriesWizard. I believe this is not desired behaviour. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 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 July 2014