June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-656) JBDS 9 Beta1: Test Install Guide

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-656?page=com.atlassian.jira.plug... ] Misha Ali reassigned TOOLSDOC-656: ---------------------------------- Assignee: Supriya Bharadwaj (was: Misha Ali) > JBDS 9 Beta1: Test Install Guide > -------------------------------- > > Key: TOOLSDOC-656 > URL: https://issues.jboss.org/browse/TOOLSDOC-656 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-656) JBDS 9 Beta1: Test Install Guide

by Misha Ali (JIRA)

Misha Ali created TOOLSDOC-656: ---------------------------------- Summary: JBDS 9 Beta1: Test Install Guide Key: TOOLSDOC-656 URL: https://issues.jboss.org/browse/TOOLSDOC-656 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Reporter: Misha Ali Assignee: Misha Ali -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3408) installer is trying to reach download.jboss.org for content

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3408?page=com.atlassian.jira.plugin.... ] Mickael Istria resolved JBDS-3408. ---------------------------------- Resolution: Done > installer is trying to reach download.jboss.org for content > ----------------------------------------------------------- > > Key: JBDS-3408 > URL: https://issues.jboss.org/browse/JBDS-3408 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Labels: respin-b > Fix For: 9.0.0.Beta1 > > Attachments: JBDS3408.install.jboss-devstudio-9.0.0.Beta1-v20150430-1113-B3095-installer-standalone.jar.log.txt > > > Running latest devstudio 9 installer I caught it in reaching out to download.jboss.org which it should have *zero* links/dependency on. > My guess is there is an updatesite that have bad reference to download.jboss.org that we need fixing. > See screenshot at https://www.dropbox.com/s/wkr30jlvdc7d8wu/Screenshot%202015-04-15%2013.11... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3408) installer is trying to reach download.jboss.org for content

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3408?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-3408: --------------------------------- Labels: respin-b (was: ) > installer is trying to reach download.jboss.org for content > ----------------------------------------------------------- > > Key: JBDS-3408 > URL: https://issues.jboss.org/browse/JBDS-3408 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Labels: respin-b > Fix For: 9.0.0.Beta1 > > Attachments: JBDS3408.install.jboss-devstudio-9.0.0.Beta1-v20150430-1113-B3095-installer-standalone.jar.log.txt > > > Running latest devstudio 9 installer I caught it in reaching out to download.jboss.org which it should have *zero* links/dependency on. > My guess is there is an updatesite that have bad reference to download.jboss.org that we need fixing. > See screenshot at https://www.dropbox.com/s/wkr30jlvdc7d8wu/Screenshot%202015-04-15%2013.11... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3408) installer is trying to reach download.jboss.org for content

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3408?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-3408: --------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Beta2) > installer is trying to reach download.jboss.org for content > ----------------------------------------------------------- > > Key: JBDS-3408 > URL: https://issues.jboss.org/browse/JBDS-3408 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.0.Beta1 > > Attachments: JBDS3408.install.jboss-devstudio-9.0.0.Beta1-v20150430-1113-B3095-installer-standalone.jar.log.txt > > > Running latest devstudio 9 installer I caught it in reaching out to download.jboss.org which it should have *zero* links/dependency on. > My guess is there is an updatesite that have bad reference to download.jboss.org that we need fixing. > See screenshot at https://www.dropbox.com/s/wkr30jlvdc7d8wu/Screenshot%202015-04-15%2013.11... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3408) installer is trying to reach download.jboss.org for content

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3408?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3408: -------------------------------------- Actually, I was believe that this was targeted for Beta1, and I merged the patch for parent pom on both branches. > installer is trying to reach download.jboss.org for content > ----------------------------------------------------------- > > Key: JBDS-3408 > URL: https://issues.jboss.org/browse/JBDS-3408 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.0.Beta1 > > Attachments: JBDS3408.install.jboss-devstudio-9.0.0.Beta1-v20150430-1113-B3095-installer-standalone.jar.log.txt > > > Running latest devstudio 9 installer I caught it in reaching out to download.jboss.org which it should have *zero* links/dependency on. > My guess is there is an updatesite that have bad reference to download.jboss.org that we need fixing. > See screenshot at https://www.dropbox.com/s/wkr30jlvdc7d8wu/Screenshot%202015-04-15%2013.11... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20038) Unable to run older Hybrid Mobile projext with CordovaSim

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20038?page=com.atlassian.jira.plugi... ] Vlado Pakan updated JBIDE-20038: -------------------------------- Attachment: myapp.zip Failing Mobile Hybrid project attached > Unable to run older Hybrid Mobile projext with CordovaSim > --------------------------------------------------------- > > Key: JBIDE-20038 > URL: https://issues.jboss.org/browse/JBIDE-20038 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, cordovasim > Affects Versions: 4.3.0.Beta1 > Environment: JBDS Beta1-v20150605-2014-B34 Fedora 22 KDE Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Priority: Critical > Attachments: cordovasimerror.png, myapp.zip > > > When running older Hybrid Mobile project with CordovaSim I'm getting error: > !cordovasimerror.png! > Project doesn't have set Cordova Engine properly. When setting Cordova Engine for project via project preferences dialog I have to select cordova engine many times to get button OK enabled. > Error log: > {noformat} > !ENTRY org.jboss.tools.browsersim.eclipse 4 0 2015-06-11 10:20:03.754 > !MESSAGE Resource is out of sync with the file system: '/accerror/www/index.html'. > !STACK 1 > org.eclipse.core.internal.resources.ResourceException: Resource is out of sync with the file system: '/accerror/www/index.html'. > at org.eclipse.core.internal.localstore.FileSystemResourceManager.read(FileSystemResourceManager.java:830) > at org.eclipse.core.internal.resources.File.getContents(File.java:269) > at org.eclipse.core.internal.resources.File.getContents(File.java:260) > at org.jboss.tools.cordovasim.eclipse.servlet.internal.WorkspaceFileServlet.doGet(WorkspaceFileServlet.java:56) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808) > at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587) > at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221) > at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127) > at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) > at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061) > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) > at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:332) > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) > at org.eclipse.jetty.server.Server.handle(Server.java:497) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310) > at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257) > at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) > at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) > at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) > at java.lang.Thread.run(Thread.java:745) > !SUBENTRY 1 org.eclipse.core.resources 4 274 2015-06-11 10:20:03.754 > !MESSAGE Resource is out of sync with the file system: '/accerror/www/index.html'. > !ENTRY org.jboss.tools.browsersim.eclipse 4 0 2015-06-11 10:20:03.923 > !MESSAGE Resource is out of sync with the file system: '/accerror/www/index.html'. > !STACK 1 > org.eclipse.core.internal.resources.ResourceException: Resource is out of sync with the file system: '/accerror/www/index.html'. > at org.eclipse.core.internal.localstore.FileSystemResourceManager.read(FileSystemResourceManager.java:830) > at org.eclipse.core.internal.resources.File.getContents(File.java:269) > at org.eclipse.core.internal.resources.File.getContents(File.java:260) > at org.jboss.tools.cordovasim.eclipse.servlet.internal.WorkspaceFileServlet.doGet(WorkspaceFileServlet.java:56) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808) > at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587) > at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221) > at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127) > at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) > at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061) > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) > at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:332) > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) > at org.eclipse.jetty.server.Server.handle(Server.java:497) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310) > at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257) > at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) > at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) > at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) > at java.lang.Thread.run(Thread.java:745) > !SUBENTRY 1 org.eclipse.core.resources 4 274 2015-06-11 10:20:03.923 > !MESSAGE Resource is out of sync with the file system: '/accerror/www/index.html'. > !ENTRY org.jboss.tools.browsersim.eclipse 4 0 2015-06-11 10:20:03.924 > !MESSAGE Resource is out of sync with the file system: '/accerror/www/index.html'. > !STACK 1 > org.eclipse.core.internal.resources.ResourceException: Resource is out of sync with the file system: '/accerror/www/index.html'. > at org.eclipse.core.internal.localstore.FileSystemResourceManager.read(FileSystemResourceManager.java:830) > at org.eclipse.core.internal.resources.File.getContents(File.java:269) > at org.eclipse.core.internal.resources.File.getContents(File.java:260) > at org.jboss.tools.cordovasim.eclipse.servlet.internal.WorkspaceFileServlet.doGet(WorkspaceFileServlet.java:56) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808) > at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587) > at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221) > at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127) > at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) > at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061) > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) > at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:332) > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) > at org.eclipse.jetty.server.Server.handle(Server.java:497) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310) > at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257) > at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) > at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) > at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) > at java.lang.Thread.run(Thread.java:745) > !SUBENTRY 1 org.eclipse.core.resources 4 274 2015-06-11 10:20:03.925 > !MESSAGE Resource is out of sync with the file system: '/accerror/www/index.html'. > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20100) how to make users aware of fuse and other tooling only being available from earlyaccess?

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ] Lars Heinemann commented on JBIDE-20100: ---------------------------------------- I find the idea good to have EA items visible but deactivated if EA isn't activated. And there should be obviously a hint that you need to activate EA in order to be able to install the EA items. If there is no EA version yet it makes no sense to display something I guess. At least it doesn't sound appealing to me that Fuse Tooling shows up for JBDS9 now while not having something atm. > how to make users aware of fuse and other tooling only being available from earlyaccess? > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20100 > URL: https://issues.jboss.org/browse/JBIDE-20100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > > [~jtyrrell] find it confusing when he cannot see Fuse and other earlyaccess features immediately on the install page. > Some comments: > "I install JBDS 8.1 and click on the JBoss Integration and SOA Development, but where is the Fuse tooling in that list." > "<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something." > Suggestion: > "when I picked the Integration Stack a greyed out Fuse IDE thingy in the list of choices, and something like (Select early Access) to enable this feature." > I'm fine exploring options to show early access features more prominently but would prefer we would not need to treat Fuse "special" so maybe we should have a "Early Access" section at the bottom instead of filtered in between everything else ? > and for any connectors that has additional/different features just add a "Extra features available in Early access " comment ? > But what to do when Fuse or others dont even have an earlyaccess out yet ? (like is currently the state for devstudio 9) > [~crobson], [~aileenc] and [~lhein] got any suggestions ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3462) remove /development/ and /staging/ URLs from JBDS artifacts

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3462?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3462: ----------------------------- CDW docs_ack: ? CDW devel_ack: ? CDW pm_ack: + CDW qa_ack: ? CDW release: ? > remove /development/ and /staging/ URLs from JBDS artifacts > ----------------------------------------------------------- > > Key: JBDS-3462 > URL: https://issues.jboss.org/browse/JBDS-3462 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > > There's a TODO in the JBDS 9 release guide which says: > {quote} > when releasing GA make sure to :%s/development/stable/g and :%s/9.0-staging/9.0/g{quote} > Here are a couple files which still need to be tweaked so they don't have to change between milestone releases and GA: > {code} > ./results/build.xml ** > 224-  > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3462) remove /development/ and /staging/ URLs from JBDS artifacts

by Nick Boldt (JIRA)

Nick Boldt created JBDS-3462: -------------------------------- Summary: remove /development/ and /staging/ URLs from JBDS artifacts Key: JBDS-3462 URL: https://issues.jboss.org/browse/JBDS-3462 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: build Affects Versions: 9.0.0.Beta1 Reporter: Nick Boldt Assignee: Nick Boldt There's a TODO in the JBDS 9 release guide which says: {quote} when releasing GA make sure to :%s/development/stable/g and :%s/9.0-staging/9.0/g{quote} Here are a couple files which still need to be tweaked so they don't have to change between milestone releases and GA: {code} ./results/build.xml ** 224-  {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 2015