March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2500) synchronize deployed archive in EAP and JBDS project source files.

by Gary Hu (JIRA)

[ https://issues.jboss.org/browse/JBDS-2500?page=com.atlassian.jira.plugin.... ] Gary Hu updated JBDS-2500: -------------------------- Attachment: eclipse.png ibm_rsa.png jboss_try1.png jboss_try2.png Screenshot_Config.jpg > synchronize deployed archive in EAP and JBDS project source files. > ------------------------------------------------------------------ > > Key: JBDS-2500 > URL: https://issues.jboss.org/browse/JBDS-2500 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Gary Hu > Attachments: eclipse.png, ibm_rsa.png, jboss_try1.png, jboss_try2.png, Screenshot_Config.jpg > > > Could JBDS provide a functionality that could synchronize the source and deployment in a two way manner. That is, if any change made at the server side after deploying could be pushed back to the source in the JBDS IDE. > It seems that currently IBM RSA IDE has such feature with IBM WebSphere server. Please check the attached ibm_rsa.png for more details. > Eclipse also could workaround this with Tomcat server by setting the "working directory" as the project workspace location something like ${workspace_loc:Project}. Please check the attached eclipse.png for more details. It doesn't seem that there's any additional functionality at server side that pushes the changes back to eclipse project. It's just a matter of setting eclipse working directory as the project source path. However, the JBDS doesn't seem to allow user to set the "Working directory" in this way. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13814) centralize all jboss tools build doc into a single place, using a single tech/markup

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13814: ---------------------------------- Summary: centralize all jboss tools build doc into a single place, using a single tech/markup Key: JBIDE-13814 URL: https://issues.jboss.org/browse/JBIDE-13814 Project: Tools (JBoss Tools) Issue Type: Bug Components: website Affects Versions: 4.1.0.Alpha1 Reporter: Nick Boldt Assignee: Nick Boldt Currently we have doc in many places: https://community.jboss.org/en/tools/dev?view=documents https://community.jboss.org/wiki/JBossToolsFAQ https://github.com/jbosstools/jbosstools-target-platforms/wiki https://github.com/jbosstools/jbosstools-build/wiki http://www.jboss.org/tools/docs/ http://www.jboss.org/tools/docs/faq http://www.jboss.org/tools/docs/testing.html http://docs.jboss.org/tools/ http://docs.jboss.org/tools/movies/ We should have doc in 1 place. Need to clean up, update, centralize, etc. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13796) rename jbosstools-integration-tests to jbosstools-itests

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13796?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13796: ------------------------------------ The "itest" convention is everywhere, you just need to google a bit: http://maven.apache.org/maven-1.x/plugins/itest/ http://henningpetersen.com/post/5/integration-testing-with-spring-and-maven http://repo1.maven.org/maven2/openejb/openejb-itests/2.1.1/openejb-itests... http://mvnrepository.com/artifact/org.fusesource.fabric.itests/ http://mvnrepository.com/search.html?query=itest http://stackoverflow.com/questions/1228709/best-practices-for-integration... (suggests putting source in src/itest/java) We already have a project called "jbosstools-integration-stack" and another called "jbosstools-integration-tests". These are completely different things, so we should rename one of them for clarity. Renaming jbosstools-integration-stack to jbosstools-is is an option but why not put the itests into projects called jbosstools*-itests? Thus we would have: {code} jbosstools-integration-stack jbosstools-integration-stack-itests jbosstools-* jbosstools-integration-tests {code} > rename jbosstools-integration-tests to jbosstools-itests > -------------------------------------------------------- > > Key: JBIDE-13796 > URL: https://issues.jboss.org/browse/JBIDE-13796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools, updatesite > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Alpha2 > > > To be consistent and more clear about purpose/content, I propose we rename the github project jbosstools-integration-tests to jbosstools-itests. > Once renamed, will need to refactor: > * job name > * destination publishing folder - http://download.jboss.org/jbosstools/updates/nightly/integrationtests/ -> http://download.jboss.org/jbosstools/updates/nightly/itests/ -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13704) Cannot build integration-tests from branch 4.0.x

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13704?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-13704. --------------------------------- Fixed, closing. > Cannot build integration-tests from branch 4.0.x > ------------------------------------------------ > > Key: JBIDE-13704 > URL: https://issues.jboss.org/browse/JBIDE-13704 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: QA > Affects Versions: 4.0.1.Final > Reporter: Tomas Remes > Assignee: Martin Malina > Fix For: 4.0.1.Final > > > Running mvn clean install -DskipTests on the clean repo, I got: > {noformat} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: org.jboss.ide.eclipse.as.ui.bot.test 4.0.0.qualifier > [ERROR] Missing requirement: org.jboss.tools.ui.bot.ext 4.0.0.qualifier requires 'bundle org.eclipse.zest.core 1.2.0' but it could not be found > [ERROR] Cannot satisfy dependency: org.jboss.ide.eclipse.as.ui.bot.test 4.0.0.qualifier depends on: bundle org.jboss.tools.ui.bot.ext 1.0.0 > [ERROR] > [ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.ui.bot.ext 4.0.0.qualifier to bundle org.eclipse.zest.core 1.2.0.", "Unable to satisfy dependency from org.jboss.tools.ui.bot.ext 4.0.0.qualifier to bundle org.eclipse.zest.layouts 1.1.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1] > org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.ui.bot.ext 4.0.0.qualifier to bundle org.eclipse.zest.core 1.2.0.", "Unable to satisfy dependency from org.jboss.tools.ui.bot.ext 4.0.0.qualifier to bundle org.eclipse.zest.layouts 1.1.0.", "No solution found because the problem is unsatisfiable."] > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.ui.bot.ext 4.0.0.qualifier to bundle org.eclipse.zest.core 1.2.0.", "Unable to satisfy dependency from org.jboss.tools.ui.bot.ext 4.0.0.qualifier to bundle org.eclipse.zest.layouts 1.1.0.", "No solution found because the problem is unsatisfiable."] > at org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:77) > at org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:89) > at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:122) > at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:80) > at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:377) > at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:354) > at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:103) > at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:82) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:274) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > ... 11 more > {noformat} -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13213) Simple adding/removing Project Archives capabilities into project

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13213?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-13213. --------------------------------- [~mmurray], please set JIRAs back to their original state after reopening for release notes - this JIRA was closed. Closing again. > Simple adding/removing Project Archives capabilities into project > ----------------------------------------------------------------- > > Key: JBIDE-13213 > URL: https://issues.jboss.org/browse/JBIDE-13213 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Archives > Reporter: Vlado Pakan > Assignee: Max Rydahl Andersen > Labels: new_and_noteworthy > Fix For: 4.0.1.Final > > > It would be useful if we have "Configure -> Add/Remove Project Archive support" option. This option would add/remove Project Archive explorer into project in Project Explorer. Now, Project Archive explorer is visible only after creation of archive with Project Archives view. To remove Project Archives explorer now, .packages files has to be deleted. This approach is not much user friendly. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13813) BrowserSim: need Web SQL API for Cordova Simulator

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13813?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-13813: ------------------------------------- Description: Cordova's Storage API is based on Web SQL API. This API is widely used in Cordova-based applications. The problem is that Safari's Web SQL API is not available in SWT Browser on Windows. A way to provide this API is needed. *Update:* Yahor [created|https://github.com/yradtsevich/pure-js-websql] a basic Web SQL API implementation based on [SQL.js|https://github.com/kripken/sql.js]. Demo is [here|http://htmlpreview.github.com/?https://github.com/yradtsevich/pure-j...]. was: Cordova's Storage API is based on Web SQL API. This API is widely used in Cordova-based applications. The problem is that Safari's Web SQL API is not available in SWT Browser on Windows. A way to provide this API is needed. I [created|https://github.com/yradtsevich/pure-js-websql] a basic Web SQL API implementation based on [SQL.js|https://github.com/kripken/sql.js]. Demo is [here|http://htmlpreview.github.com/?https://github.com/yradtsevich/pure-j...]. > BrowserSim: need Web SQL API for Cordova Simulator > -------------------------------------------------- > > Key: JBIDE-13813 > URL: https://issues.jboss.org/browse/JBIDE-13813 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Visual Page Editor core > Reporter: Yahor Radtsevich > Assignee: Yahor Radtsevich > Fix For: 4.1.0.Beta1 > > > Cordova's Storage API is based on Web SQL API. This API is widely used in Cordova-based applications. > The problem is that Safari's Web SQL API is not available in SWT Browser on Windows. A way to provide this API is needed. > *Update:* > Yahor [created|https://github.com/yradtsevich/pure-js-websql] a basic Web SQL API implementation based on [SQL.js|https://github.com/kripken/sql.js]. Demo is [here|http://htmlpreview.github.com/?https://github.com/yradtsevich/pure-j...]. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13813) BrowserSim: need Web SQL API for Cordova Simulator

by Yahor Radtsevich (JIRA)

Yahor Radtsevich created JBIDE-13813: ---------------------------------------- Summary: BrowserSim: need Web SQL API for Cordova Simulator Key: JBIDE-13813 URL: https://issues.jboss.org/browse/JBIDE-13813 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 4.1.0.Beta1 Cordova's Storage API is based on Web SQL API. This API is widely used in Cordova-based applications. The problem is that Safari's Web SQL API is not available in SWT Browser on Windows. A way to provide this API is needed. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13537) Unable to create EAP6.1 server [4.0.1 maintenance]

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13537?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-13537. ------------------------------------ closing. > Unable to create EAP6.1 server [4.0.1 maintenance] > --------------------------------------------------- > > Key: JBIDE-13537 > URL: https://issues.jboss.org/browse/JBIDE-13537 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers, runtime-detection > Affects Versions: 4.1.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Rob Stryker > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.0.1.Final > > Attachments: New Server Runtime Environment _002.png, New Server Runtime Environment _003.png > > > EAP6.1 is detected via runtime detection but nothing happens when I click OK to create runtime. Also manually adding it through Runtime Enviroment -> add -> EAP6.x does not work. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13796) rename jbosstools-integration-tests to jbosstools-itests

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13796?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13796: --------------------------------------------- thinking about this then i'm +0 on this; if QE is ok with it and our branch CI builds can pull from this new repo instead without too much fuzz its fine by me. > rename jbosstools-integration-tests to jbosstools-itests > -------------------------------------------------------- > > Key: JBIDE-13796 > URL: https://issues.jboss.org/browse/JBIDE-13796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools, updatesite > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Alpha2 > > > To be consistent and more clear about purpose/content, I propose we rename the github project jbosstools-integration-tests to jbosstools-itests. > Once renamed, will need to refactor: > * job name > * destination publishing folder - http://download.jboss.org/jbosstools/updates/nightly/integrationtests/ -> http://download.jboss.org/jbosstools/updates/nightly/itests/ -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13812) openshift-java-client: get rid of external class to (de)code base64

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13812?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13812: ------------------------------------- Bugzilla Update: (was: Perform) > openshift-java-client: get rid of external class to (de)code base64 > ------------------------------------------------------------------- > > Key: JBIDE-13812 > URL: https://issues.jboss.org/browse/JBIDE-13812 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > > We're currently using a class that we copied from a different project to (de)code base64. This contradicts the fedora project which wants to package us into an rpm. They suggested to package the full library instead. > Since we dont want to agument the numbers of dependencies, I'll switch to JDK means to (de)code base64. This will bind us to >= JDK6 which is IMHO perfectly fine. -- 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

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 March 2013