[JBoss JIRA] (JBTIS-422) Lots of errors when we try to install JBDS-IS 8.0.1.GA from central
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-422?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBTIS-422:
------------------------------------
Attachment: error_log.txt
> Lots of errors when we try to install JBDS-IS 8.0.1.GA from central
> -------------------------------------------------------------------
>
> Key: JBTIS-422
> URL: https://issues.jboss.org/browse/JBTIS-422
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 8.0.1.GA
> Reporter: Andrej Podhradsky
> Attachments: error_log.txt
>
>
> Specify the integration stack discovery artifact:
> {code}
> ./jbdevstudio -vmargs \
> -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA/devstudio-integration-stack-directory.xml \
> -Djboss.discovery.site.url=https://devstudio.redhat.com/updates/8.0-development/ \
> -Djboss.discovery.earlyaccess.site.url=https://devstudio.redhat.com/earlyaccess/8.0-development/ \
> -Djboss.discovery.earlyaccess.list.url=https://devstudio.redhat.com/updates/8.0-development/devstudio-earlyaccess.properties \
> -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA
> {code}
> then select Software/Update in JBoss Central and open Error Log
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBTIS-422) Lots of errors when we try to install JBDS-IS 8.0.1.GA from central
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-422:
---------------------------------------
Summary: Lots of errors when we try to install JBDS-IS 8.0.1.GA from central
Key: JBTIS-422
URL: https://issues.jboss.org/browse/JBTIS-422
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: distribution
Affects Versions: 8.0.1.GA
Reporter: Andrej Podhradsky
Specify the integration stack discovery artifact:
{code}
./jbdevstudio -vmargs \
-Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA/devstudio-integration-stack-directory.xml \
-Djboss.discovery.site.url=https://devstudio.redhat.com/updates/8.0-development/ \
-Djboss.discovery.earlyaccess.site.url=https://devstudio.redhat.com/earlyaccess/8.0-development/ \
-Djboss.discovery.earlyaccess.list.url=https://devstudio.redhat.com/updates/8.0-development/devstudio-earlyaccess.properties \
-Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA
{code}
then select Software/Update in JBoss Central and open Error Log
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-19410 at 4/9/15 4:39 AM:
----------------------------------------------------------------
{quote}Mickael, considering your last change related to wrapping updateTitle(heading) inside display.asyncExec() you never ran the actual code, did you? {quote}
I have to admit I didn't try the last patch before pushing ;) But I just gave it a try now, and it's working fine on my machine. What did you find wrong? I'm just changing the asyncExec by a syncExec because async in an (async) job is too much async.
The root cause of this failure are explained in previous comments (mainly #2 and #8). This is a corner-case of using PDE Launch Configuration without p2 enabled, such issue doesn't exist in real package and the change is actually just some "powder" to hide the fact that dev-mode doesn't support p2 by default. Since this doesn't happen in "real-life", I don't think we need more effort regarding messages.
If you want to fully try the Central functionality in dev-mode, you have to tweak your PDE Launch Configuration to enable p2, as explained in comment #2.
was (Author: mickael_istria):
{quote}Mickael, considering your last change related to wrapping updateTitle(heading) inside display.asyncExec() you never ran the actual code, did you? {quote}
I have to admit I didn't try the last patch ;) But I just gave it a try now, and it's working fine on my machine. What did you find wrong? I'm just changing the asyncExec by a syncExec because async in an (async) job is too much async.
The root cause of this failure are explained in previous comments (mainly #2 and #8). This is a corner-case of using PDE Launch Configuration without p2 enabled, such issue doesn't exist in real package and the change is actually just some "powder" to hide the fact that dev-mode doesn't support p2 by default. Since this doesn't happen in "real-life", I don't think we need more effort regarding messages.
If you want to fully try the Central functionality in dev-mode, you have to tweak your PDE Launch Configuration to enable p2, as explained in comment #2.
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19410:
----------------------------------------
{quote}Mickael, considering your last change related to wrapping updateTitle(heading) inside display.asyncExec() you never ran the actual code, did you? {quote}
I have to admit I didn't try the last patch ;) But I just gave it a try now, and it's working fine on my machine. What did you find wrong? I'm just changing the asyncExec by a syncExec because async in an (async) job is too much async.
The root cause of this failure are explained in previous comments (mainly #2 and #8). This is a corner-case of using PDE Launch Configuration without p2 enabled, such issue doesn't exist in real package and the change is actually just some "powder" to hide the fact that dev-mode doesn't support p2 by default. Since this doesn't happen in "real-life", I don't think we need more effort regarding messages.
If you want to fully try the Central functionality in dev-mode, you have to tweak your PDE Launch Configuration to enable p2, as explained in comment #2.
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-15714) Dynamic content assist for AngularJS expressions in html files
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15714?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-15714:
---------------------------------------------
I would say if the user has disabled refresh then I would be fine saying he won't get uptodate content assist.
Thus i'm still not really following what the problem is besides that on the very first content assist the browser might not be fully initialized ?
> Dynamic content assist for AngularJS expressions in html files
> --------------------------------------------------------------
>
> Key: JBIDE-15714
> URL: https://issues.jboss.org/browse/JBIDE-15714
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Priority: Critical
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: Diagram.gliffy, vpe.png
>
>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19425) Error when loading projects in Central with Java 9
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19425?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19425:
---------------------------------------
Hmm, that seems strange.
The truth is that there is no rt.jar in the jdk.
But maybe it has been reorganized and is somewhere else now? And Eclipse is not yet fully ready? But I don't really know where it could be.
Like in the case of javafx (JBIDE-19050).
> Error when loading projects in Central with Java 9
> --------------------------------------------------
>
> Key: JBIDE-19425
> URL: https://issues.jboss.org/browse/JBIDE-19425
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Fred Bricon
> Labels: Java9
> Fix For: 4.3.x
>
>
> Today I wanted to try out the latest build of Oracle JDK 1.9 beta and discovered a problem with central.
> When I started JBDS, I immediately got an error window pop up:
> {code}
> Refreshing JBoss Tutorials... has encountered a problem.
> An internal error occurred during: "Refreshing JBoss Tutorials...".
> javax/xml/bind/JAXBException
> {code}
> This is in the workspace log:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2015-03-10 17:12:52.346
> !MESSAGE An internal error occurred during: "Refreshing JBoss Tutorials...".
> !STACK 0
> java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.fetchCategories(ProjectExampleUtil.java:389)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:266)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:257)
> at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:52)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException cannot be found by org.jboss.tools.project.examples_3.0.0.Alpha1-v20150213-0945-B3
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> ... 5 more
> {code}
> I used JBDS 9.0.0.Alpha1 installed on OS X 10.10 Yosemite with Oracle JDK 1.9:
> {code}
> nattura:9.0.0 rasp$ java -version
> java version "1.9.0-ea"
> Java(TM) SE Runtime Environment (build 1.9.0-ea-b53)
> Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b53, mixed mode)
> {code}
> The consequence of this is that the "Start from scratch" section in Central is not loaded and shows "No entries found".
> Note: When I installed the same JBDS with Java 8, there was no error.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TOOLSDOC-624) JBDS-IS 8.0.1: Update Install Document
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-624?page=com.atlassian.jira.plug... ]
Misha Ali updated TOOLSDOC-624:
-------------------------------
Description:
1. Installation Guide - in Fuse, we have our own Fuse Tooling Installation Guide. After comparing the content of the two installation guides, I don't have objections to getting rid of ours and reusing the one from JBDS IS. But:
a) the guide should include (a link to) JBDS installation instructions; this information is currently missing and imo is very important in the isolated context of individual products' docs suites. Update: Four installation instructions are provided in the Install Guide at the moment. The first two are for installing JBDS, the latter two are for JBDS-IS. The latter two should have a prerequisite step that tells you to install JBDS and links to the relevant topics (the first two ways to install).
b) the "From the table of categories, select the JBoss Developer Studio Integration Stack functionality you want to install and click Next." step of each procedure should be expanded with specific instructions for individual products, i.e. what components of the IS to install for Fuse, DV and B*MS
was:
1. Installation Guide - in Fuse, we have our own Fuse Tooling Installation Guide. After comparing the content of the two installation guides, I don't have objections to getting rid of ours and reusing the one from JBDS IS. But:
a) the guide should include (a link to) JBDS installation instructions; this information is currently missing and imo is very important in the isolated context of individual products' docs suites
b) the "From the table of categories, select the JBoss Developer Studio Integration Stack functionality you want to install and click Next." step of each procedure should be expanded with specific instructions for individual products, i.e. what components of the IS to install for Fuse, DV and B*MS
> JBDS-IS 8.0.1: Update Install Document
> ---------------------------------------
>
> Key: TOOLSDOC-624
> URL: https://issues.jboss.org/browse/TOOLSDOC-624
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Reporter: Misha Ali
> Assignee: Misha Ali
>
> 1. Installation Guide - in Fuse, we have our own Fuse Tooling Installation Guide. After comparing the content of the two installation guides, I don't have objections to getting rid of ours and reusing the one from JBDS IS. But:
> a) the guide should include (a link to) JBDS installation instructions; this information is currently missing and imo is very important in the isolated context of individual products' docs suites. Update: Four installation instructions are provided in the Install Guide at the moment. The first two are for installing JBDS, the latter two are for JBDS-IS. The latter two should have a prerequisite step that tells you to install JBDS and links to the relevant topics (the first two ways to install).
> b) the "From the table of categories, select the JBoss Developer Studio Integration Stack functionality you want to install and click Next." step of each procedure should be expanded with specific instructions for individual products, i.e. what components of the IS to install for Fuse, DV and B*MS
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TOOLSDOC-624) JBDS-IS 8.0.1: Update Install Document
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-624?page=com.atlassian.jira.plug... ]
Misha Ali reassigned TOOLSDOC-624:
----------------------------------
Assignee: Supriya Bharadwaj (was: Misha Ali)
> JBDS-IS 8.0.1: Update Install Document
> ---------------------------------------
>
> Key: TOOLSDOC-624
> URL: https://issues.jboss.org/browse/TOOLSDOC-624
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Reporter: Misha Ali
> Assignee: Supriya Bharadwaj
>
> 1. Installation Guide - in Fuse, we have our own Fuse Tooling Installation Guide. After comparing the content of the two installation guides, I don't have objections to getting rid of ours and reusing the one from JBDS IS. But:
> a) the guide should include (a link to) JBDS installation instructions; this information is currently missing and imo is very important in the isolated context of individual products' docs suites. Update: Four installation instructions are provided in the Install Guide at the moment. The first two are for installing JBDS, the latter two are for JBDS-IS. The latter two should have a prerequisite step that tells you to install JBDS and links to the relevant topics (the first two ways to install).
> b) the "From the table of categories, select the JBoss Developer Studio Integration Stack functionality you want to install and click Next." step of each procedure should be expanded with specific instructions for individual products, i.e. what components of the IS to install for Fuse, DV and B*MS
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19569) Unable to switch pages shown in visual preview when editing mobile html5
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19569?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19569:
---------------------------------------
[~kmarmaliykov], so at least that seems to be a bug then? That you can click a button in the visual preview and it will take you to the next page (where the link leads).
> Unable to switch pages shown in visual preview when editing mobile html5
> ------------------------------------------------------------------------
>
> Key: JBIDE-19569
> URL: https://issues.jboss.org/browse/JBIDE-19569
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.3.Final
> Reporter: Martin Malina
> Assignee: Konstantin Marmalyukov
>
> I'm not sure if my use case is valid or not.
> But today I tried something [1] and had a html5 using the jQuery Mobile 1.4 template, then I created a new page. The Visual part of the editor shows the first page (div with data-role="page") in the html, but it's impossible to show the second one.
> So I thought: OK, I will add a button to the first page linking to the second page. But once I clicked the button, there was no way to get back and show the first page in the visual preview.
> Shouldn't we offer some kind of navigation? Either the possibility to view different pages in the html, or at least a Back button?
> But maybe I just just misunderstand how this works - maybe this is not a valid request - I'll be happy to be corrected :)
> [1] I was reviewing a howto document that actually describes exactly this scenario - create html5 from the template and then add a new Page to it using the palette.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years