[JBoss JIRA] (JBIDE-19990) "See JBoss Tools Visual Editor FAQ" link is not working.
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19990?page=com.atlassian.jira.plugi... ]
Radim Hopp commented on JBIDE-19990:
------------------------------------
Sooo.. We've made a progress here!
On Vlado's machine, everything worked as expected, but I finally figured out what caused my machine to fail in this case.
As I stated previously, google-chrome was configured as default browser in KDE (Plasma 5) settings and it was used as default browser by all applications respecting that settings. What I had different than Vlado is default application for text/html mimetype. There I had konqueror as default application for handling text/html mimetype (and I think this is default application in Plasma 5 for handling it).
When I changed this to google-chrome or firefox, everything was working fine.
In conclusion: "See JBoss Tools Visual Editor FAQ" link is not working IF Konqueror is configured as default application for text/html mimetype.
> "See JBoss Tools Visual Editor FAQ" link is not working.
> --------------------------------------------------------
>
> Key: JBIDE-19990
> URL: https://issues.jboss.org/browse/JBIDE-19990
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, visual-page-editor-core
> Affects Versions: 4.3.0.Beta1
> Reporter: Radim Hopp
> Assignee: Radim Hopp
> Fix For: 4.3.0.Beta2
>
>
> When the browser cannot be instantiated, error is shown and on the bottom of the editor is "See JBoss Tools Visual Editor FAQ" link (see here: http://i.imgur.com/F2l9Hgi.png).
> This link is not working. Clicking on it just writes into console, from where JBDS/JBT was started, this:
> _env: /home/rhopp/http:/tools.jboss.org/documentation/faq/visualeditor.html: Directory or file does not exist_
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20171) buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20171?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-20171:
---------------------------------------------
looks good. One thing I couldn't spot is where the buildinfo.json for xulrunner is added/stored ? didn't see it in any of PR's/links ?
> buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA
> -------------------------------------------------------------------
>
> Key: JBIDE-20171
> URL: https://issues.jboss.org/browse/JBIDE-20171
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Affects Versions: 4.3.0.Beta2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta2
>
>
> Since the addition of a check that verifies exactly this condition:
> https://github.com/jbosstools/jbosstools-maven-plugins/commit/916f4521ba6...
> I've now got a situation where it's OK to have no SHA in the MANIFEST.MF, but a SHA in buildinfo.json.
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/10216/console}
> [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project org.jboss.tools.site.core: Problem occurred checking upstream buildinfo.json files!
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-xulrunner.json
> [ERROR] contains 2edce933f7d64efbb4d7a5b16be8dadae8de766e, but upstream project's MANIFEST.MF has Eclipse-SourceReferences
> [ERROR] commitId .
> [ERROR] If you have locally built projects which are aggregated here,
> [ERROR] ensure they are built from the latest SHA from HEAD, not a local topic branch.
> [ERROR] Or, use -DskipCheckSHAs=true to bypass this check.
> [ERROR] -> [Help 1]{code}
> This happened after I put a buildinfo.json file here:
> http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2...
> I've since moved the file here to temporarily work around the build failure:
> http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBDS-3479) create just one marketplace entry for developer studio
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3479?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3479:
-------------------------------------------
[~apodhrad] i'm pretty sure your issues regarding JBDSIS/JBTIS are not unique for this issue. Those are separate issues - shouldn't be forgotten but I'm 99.99% sure you would have same error with the existing marketplace.
We are looking for differences, if we just keep the same "bugs" that is fine for this issue ;)
> create just one marketplace entry for developer studio
> ------------------------------------------------------
>
> Key: JBDS-3479
> URL: https://issues.jboss.org/browse/JBDS-3479
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: marketplace
> Affects Versions: 9.0.0.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 9.0.0.Beta1
>
> Attachments: error_log_kepler.txt, jboss_central_kepler.png
>
>
> As discussed on JBIDE-20024 it now makes sense to have just one developer studio entry on markteplace.
> To avoid loss of full stats rename Red Hat JBoss Developer Studio (Kepler): http://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-kep...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBDS-3479) create just one marketplace entry for developer studio
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBDS-3479?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky commented on JBDS-3479:
-----------------------------------------
Hi Mickael Istria, I tried only Luna since there is no Integration Stack for Mars so I tried the following use case
Install JBDS from marketplace into Luna, then install JBDS-IS from JBoss Central (this is OK)
Note that once we install JBDS into Eclipse from marketplace then we are not able to install JBDS-IS from marketplace (because JBDS-IS entry contains JBDS features).
> create just one marketplace entry for developer studio
> ------------------------------------------------------
>
> Key: JBDS-3479
> URL: https://issues.jboss.org/browse/JBDS-3479
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: marketplace
> Affects Versions: 9.0.0.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 9.0.0.Beta1
>
>
> As discussed on JBIDE-20024 it now makes sense to have just one developer studio entry on markteplace.
> To avoid loss of full stats rename Red Hat JBoss Developer Studio (Kepler): http://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-kep...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months