January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13338) BrowserSim: integrate weinre functionality to BrowserSim

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13338?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13338: --------------------------------------------- this looks interesting but i'm not following what this feature does ? Does it auto-inject some code or is it just auto-opening a weinre url ? > BrowserSim: integrate weinre functionality to BrowserSim > -------------------------------------------------------- > > Key: JBIDE-13338 > URL: https://issues.jboss.org/browse/JBIDE-13338 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Visual Page Editor core > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.1.0.Alpha1 > > Attachments: example.png, weinre.bmml, weinre.png > > > It will be good to have debug capabilities in browserSim. Weinre can provide it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13346) DirectoryScanner fails on non-existing folders

by Jesper Skov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13346?page=com.atlassian.jira.plugi... ] Jesper Skov updated JBIDE-13346: -------------------------------- Attachment: org.eclipse.wst.common.component EAR .settings file containing the Deployment Assembly setup for the project in question. > DirectoryScanner fails on non-existing folders > ---------------------------------------------- > > Key: JBIDE-13346 > URL: https://issues.jboss.org/browse/JBIDE-13346 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Archives > Affects Versions: 4.0.0.Final > Environment: Windows XP/Windows 7 > Eclipse 4.3M4 > Reporter: Jesper Skov > Assignee: Rob Stryker > Attachments: org.eclipse.wst.common.component > > > DirectoryScanner can be made to fail on non-existing folders. > In our setup, these folders are possibly picked up from the Deployment Assembly settings. > The folders are created by our custom Builder with highest priority, so appears to work properly with everything else in Eclipse. > But it seems the Archive DirectoryScanner runs before our builder. > The stack trace looks like this: > > {code} > java.lang.IllegalStateException: basedir C:\udvikler\ws\plugins\jb.it.reuters\build\gen-lib-deployable is not a directory > at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scanPrepare(DirectoryScanner.java:552) > at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scan(DirectoryScanner.java:588) > at org.jboss.ide.eclipse.archives.core.model.DirectoryScannerFactory.createDirectoryScanner(DirectoryScannerFactory.java:66) > at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent$WorkspaceFilter.<init>(WorkspaceFilesetVirtualComponent.java:100) > at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent.getRootFolder(WorkspaceFilesetVirtualComponent.java:53) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.consumeComponent(FlatVirtualComponent.java:203) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.addConsumedReferences(FlatVirtualComponent.java:196) > at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.optimize(ClasspathLibraryExpander.java:47) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.cacheResources(FlatVirtualComponent.java:119) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.fetchResources(FlatVirtualComponent.java:101) > at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.fetchResource(ClasspathLibraryExpander.java:74) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.getBaseEARLibRefs(J2EEComponentClasspathContainer.java:463) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.requiresUpdate(J2EEComponentClasspathContainer.java:208) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.refresh(J2EEComponentClasspathContainer.java:540) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.processModules(J2EEComponentClasspathUpdater.java:311) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.access$4(J2EEComponentClasspathUpdater.java:295) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob$1.run(J2EEComponentClasspathUpdater.java:336) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.run(J2EEComponentClasspathUpdater.java:321) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13346) DirectoryScanner fails on non-existing folders

by Jesper Skov (JIRA)

Jesper Skov created JBIDE-13346: ----------------------------------- Summary: DirectoryScanner fails on non-existing folders Key: JBIDE-13346 URL: https://issues.jboss.org/browse/JBIDE-13346 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Archives Affects Versions: 4.0.0.Final Environment: Windows XP/Windows 7 Eclipse 4.3M4 Reporter: Jesper Skov Assignee: Rob Stryker DirectoryScanner can be made to fail on non-existing folders. In our setup, these folders are possibly picked up from the Deployment Assembly settings. The folders are created by our custom Builder with highest priority, so appears to work properly with everything else in Eclipse. But it seems the Archive DirectoryScanner runs before our builder. The stack trace looks like this: {code} java.lang.IllegalStateException: basedir C:\udvikler\ws\plugins\jb.it.reuters\build\gen-lib-deployable is not a directory at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scanPrepare(DirectoryScanner.java:552) at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scan(DirectoryScanner.java:588) at org.jboss.ide.eclipse.archives.core.model.DirectoryScannerFactory.createDirectoryScanner(DirectoryScannerFactory.java:66) at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent$WorkspaceFilter.<init>(WorkspaceFilesetVirtualComponent.java:100) at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent.getRootFolder(WorkspaceFilesetVirtualComponent.java:53) at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.consumeComponent(FlatVirtualComponent.java:203) at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.addConsumedReferences(FlatVirtualComponent.java:196) at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.optimize(ClasspathLibraryExpander.java:47) at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.cacheResources(FlatVirtualComponent.java:119) at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.fetchResources(FlatVirtualComponent.java:101) at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.fetchResource(ClasspathLibraryExpander.java:74) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.getBaseEARLibRefs(J2EEComponentClasspathContainer.java:463) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.requiresUpdate(J2EEComponentClasspathContainer.java:208) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.refresh(J2EEComponentClasspathContainer.java:540) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.processModules(J2EEComponentClasspathUpdater.java:311) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.access$4(J2EEComponentClasspathUpdater.java:295) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob$1.run(J2EEComponentClasspathUpdater.java:336) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.run(J2EEComponentClasspathUpdater.java:321) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13345) Hide help button from examples and quickstarts wizard (or provide some content)

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13345?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-13345: ------------------------------- Attachment: help.png > Hide help button from examples and quickstarts wizard (or provide some content) > ------------------------------------------------------------------------------- > > Key: JBIDE-13345 > URL: https://issues.jboss.org/browse/JBIDE-13345 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: project-examples > Affects Versions: 4.0.0.Final > Reporter: Radim Hopp > Assignee: Snjezana Peco > Priority: Optional > Attachments: help.png > > > Right now, there is help button (question mark in lower left corner) in wizards of project examples and quickstarts with no content (nothing is shown when it's clicked on). > Shouldn't we provide some basic help or hide the help button completely? > !help.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13345) Hide help button from examples and quickstarts wizard (or provide some content)

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-13345: ---------------------------------- Summary: Hide help button from examples and quickstarts wizard (or provide some content) Key: JBIDE-13345 URL: https://issues.jboss.org/browse/JBIDE-13345 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: project-examples Affects Versions: 4.0.0.Final Reporter: Radim Hopp Assignee: Snjezana Peco Priority: Optional Attachments: help.png Right now, there is help button (question mark in lower left corner) in wizards of project examples and quickstarts with no content (nothing is shown when it's clicked on). Shouldn't we provide some basic help or hide the help button completely? !help.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13329) should unified.target includes sources?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13329?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-13329: ----------------------------------- Fix Version/s: 4.1.0.Alpha1 > should unified.target includes sources? > --------------------------------------- > > Key: JBIDE-13329 > URL: https://issues.jboss.org/browse/JBIDE-13329 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.0.0.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > I was under the impression that the generated multiple.target would include source features, while the generated unified.target would not. > However: > {code} > unified-4.2.1.a-20121220.173723-14-unified.target: > <location includeAllPlatforms="false" includeMode="planner" includeSource="true" type="InstallableUnit"> > multiple-4.2.1.a-20121220.173233-14-multiple.target: > <location includeAllPlatforms="false" includeMode="planner" type="InstallableUnit" includeSource="true"> > {code} > And the generated update site for 4.2.1.a (SR1a) target platform contains many feature.source bundles: > http://download.jboss.org/jbosstools/updates/juno/SR1a/REPO/features/ > Is this intentional? Or is there a bug in your flatten mojo? > https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2411) Update JBoss Server Manager Red Guide to include updated info for as7.1 tooling

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-2411?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-2411: ----------------------------------- Michelle: When was this pushed in? I made all relevent changes already in the big patch I sent to you. > Update JBoss Server Manager Red Guide to include updated info for as7.1 tooling > ------------------------------------------------------------------------------- > > Key: JBDS-2411 > URL: https://issues.jboss.org/browse/JBDS-2411 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: documentation > Reporter: Martin Malina > Assignee: Michelle Murray > Fix For: 6.0.x > > Attachments: new-eap6.png > > > The information at https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/5.0... is not up2date. When you create an AS7 server (7.0.2+) you can check if you want to expose the management port. Also, for most servers you can check if the server is to be bound to all interfaces. > Note that for a local server you don't really need to expose the management port - it is bound to localhost by default. But for remote servers you need to use it if you want to make a jmx connection to the server. > Also, if this option is checked, it will set the startup poller for that server to JBoss 7 Manager Service. For the startup poller and jmx connection to work you need to have a user created on the given remote server. > Please let me or Rob know if you need more info on this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2256) Add chapter about how to configure JBoss AS startup parameters in eclipse

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-2256?page=com.atlassian.jira.plugin.... ] Rob Stryker resolved JBDS-2256. ------------------------------- Resolution: Done This was pushed / merged in right after the f2f > Add chapter about how to configure JBoss AS startup parameters in eclipse > ------------------------------------------------------------------------- > > Key: JBDS-2256 > URL: https://issues.jboss.org/browse/JBDS-2256 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Doc - JBossAS > Affects Versions: 5.0.0.GA > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 6.0.1.GA > > > There is no documentation about JBoss AS server startup parameters configuration (see forum reference for details) would be good to have it covered somewhere. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13342) kitchensink-html5-mobile - Readme isn't shown when importing for first time with empty local repository

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13342?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-13342: ------------------------------------ I'm not able to reproduce the issue with those plugins you provided, so I think it could be considered as resolved. > kitchensink-html5-mobile - Readme isn't shown when importing for first time with empty local repository > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13342 > URL: https://issues.jboss.org/browse/JBIDE-13342 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.0.0.Final > Reporter: Radim Hopp > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha1 > > Attachments: projectExamples.zip > > > When importing kitchensink-html5-mobile for the first time (with clean maven repo & freshly started JBT), readme isn't shown and project has one error marker: > {noformat} > Project configuration is not up-to-date with pom.xml. Run Maven->Update Project or use Quick Fix > {noformat} > When trying to import for the second time, everything behaves as it should (readme is shown and no errors are present) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2440) JBDS 6.0.1 - Archetypes available in JBoss Central are using versions of the BOM which aren't in the EAP 6.0.1 Maven repo

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2440?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-2440: ----------------------------------- Is it still considered a blocker, given the EAP 6.0.1 artifacts are supposed to be added to https://maven.repository.redhat.com/techpreview/all/ And I know some people don't have access to internet, but they could still access to a mirror repo. > JBDS 6.0.1 - Archetypes available in JBoss Central are using versions of the BOM which aren't in the EAP 6.0.1 Maven repo > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2440 > URL: https://issues.jboss.org/browse/JBDS-2440 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 6.0.1.GA > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 6.0.1.GA > > > This problem will not be solved in a JBDS build, but it must be resolved in time for the JBDS 6.0.1 release. > The issue is that the archetypes didn't get properly checked for EAP 6.0.1. As a result they are still using versions of the BOM which aren't in the EAP 6.0.1 Maven repo. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 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 January 2013