July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17525) Visual Editor: Nothing shown in preview after opening page source in browsersim

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17525?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-17525: ------------------------------------- For now The error message "Preview can't handle external files" will be shown > Visual Editor: Nothing shown in preview after opening page source in browsersim > ------------------------------------------------------------------------------- > > Key: JBIDE-17525 > URL: https://issues.jboss.org/browse/JBIDE-17525 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, visual-page-editor-core > Affects Versions: 4.2.0.Beta2 > Reporter: Konstantin Marmalyukov > Assignee: Ilya Buziuk > Fix For: 4.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17525) Visual Editor: Nothing shown in preview after opening page source in browsersim

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17525?page=com.atlassian.jira.plugi... ] Ilya Buziuk edited comment on JBIDE-17525 at 7/8/14 6:12 AM: ------------------------------------------------------------- For 4.2 release the error message "Preview can't handle external files" will be shown was (Author: ibuziuk): For now The error message "Preview can't handle external files" will be shown > Visual Editor: Nothing shown in preview after opening page source in browsersim > ------------------------------------------------------------------------------- > > Key: JBIDE-17525 > URL: https://issues.jboss.org/browse/JBIDE-17525 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, visual-page-editor-core > Affects Versions: 4.2.0.Beta2 > Reporter: Konstantin Marmalyukov > Assignee: Ilya Buziuk > Fix For: 4.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3087) Consider new installer packages

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3087?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3087: -------------------------------------- Need to check, but it seems to me that the p2-installer from repo linked above creates multiplatform distributions. Having spent some time in the past with the IzPack installer, I find it very difficult to maintain. It's really an old piece of code relying on a technology that no-one seems to support anymore, and on technologies that are not the most comfortable for our team (Swing, Ant...). Migrating to newer IzPack is not trivial and require a big amount of work. But I agree that this change doesn't require such a migration to a new installer technology, I'm just taking this jira as an opportunity to tell how much I dislike IzPack 4. > Consider new installer packages > ------------------------------- > > Key: JBDS-3087 > URL: https://issues.jboss.org/browse/JBDS-3087 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta2 > Reporter: Nick Boldt > > Today we have two installers: > * Stand-alone Installer (504M) > * Installer with EAP (642M) > Both can be used for offline install, but both are large downloads. > When installing JBDS IS offline, a user must download several archives: > * JBDS installer jar (or update site zip) > * JBDS target platform zip > * JBDS IS zip > And, there's no "stub installer for online" which would simply fetch the content needed to do the install from the update site, making the installer a much smaller (initial) download footprint. > Therefore Max has suggested that we might want to add two new installers, resulting in this list: > * Stand-alone Installer (504M) > * Installer with EAP (642M) > * Installer with Integration Stack (~750M) > * Stub Installer (~10M) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17818) Visual Editor: Need to handle external html / htm files

by Ilya Buziuk (JIRA)

Ilya Buziuk created JBIDE-17818: ----------------------------------- Summary: Visual Editor: Need to handle external html / htm files Key: JBIDE-17818 URL: https://issues.jboss.org/browse/JBIDE-17818 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: visual-page-editor-core Affects Versions: 4.2.0.Beta2 Reporter: Ilya Buziuk Assignee: Ilya Buziuk Fix For: 4.3.x Now VPE / HTML Preview can handle only workspace's files. Need to add external files support -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17816) [regression] Default values for Project name, Archetype ID etc. are not filled for archetype project wizards

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17816?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-17816: -------------------------------- Fix Version/s: 4.2.0.Beta3 > [regression] Default values for Project name, Archetype ID etc. are not filled for archetype project wizards > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-17816 > URL: https://issues.jboss.org/browse/JBIDE-17816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.2.0.Beta3 > Reporter: Radim Hopp > Assignee: Fred Bricon > Labels: respin-a > Fix For: 4.2.0.Beta3 > > > In JBT 4.2.0.Beta2 and earlier version New project example wizard for archetypes (HTML5 project, Richfaces project, ...) fileld lot of fields automatically. > Now almost all fields are left blank (Project Name, Package, Group Id, Artifact Id) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17816) [regression] Default values for Project name, Archetype ID etc. are not filled for archetype project wizards

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17816?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-17816: -------------------------------- Labels: respin-a (was: ) > [regression] Default values for Project name, Archetype ID etc. are not filled for archetype project wizards > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-17816 > URL: https://issues.jboss.org/browse/JBIDE-17816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.2.0.Beta3 > Reporter: Radim Hopp > Assignee: Fred Bricon > Labels: respin-a > > In JBT 4.2.0.Beta2 and earlier version New project example wizard for archetypes (HTML5 project, Richfaces project, ...) fileld lot of fields automatically. > Now almost all fields are left blank (Project Name, Package, Group Id, Artifact Id) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3087) Consider new installer packages

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3087?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3087: ------------------------------------------- One of the drivers of this suggestion is to avoid having to mess with multiple updatesites for the offline install case. But it wouldn't have *all* of central unless we actually also add that into the installer - but then these installers need to rev rather often. > Consider new installer packages > ------------------------------- > > Key: JBDS-3087 > URL: https://issues.jboss.org/browse/JBDS-3087 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta2 > Reporter: Nick Boldt > > Today we have two installers: > * Stand-alone Installer (504M) > * Installer with EAP (642M) > Both can be used for offline install, but both are large downloads. > When installing JBDS IS offline, a user must download several archives: > * JBDS installer jar (or update site zip) > * JBDS target platform zip > * JBDS IS zip > And, there's no "stub installer for online" which would simply fetch the content needed to do the install from the update site, making the installer a much smaller (initial) download footprint. > Therefore Max has suggested that we might want to add two new installers, resulting in this list: > * Stand-alone Installer (504M) > * Installer with EAP (642M) > * Installer with Integration Stack (~750M) > * Stub Installer (~10M) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3087) Consider new installer packages

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3087?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3087: ------------------------------------------- [~mickael_istria] the problem with the native p2 installer is that this would triple the amount of installers we would need. if that p2-installer can run with pure "java -jar p2installer.jar" then yes that would be relevant. btw. you are aware that our current installer does use p2 director to do its install today so the installer today can actually do what is suggested here. Just need to repackage it to use remote site instead of bundled one. > Consider new installer packages > ------------------------------- > > Key: JBDS-3087 > URL: https://issues.jboss.org/browse/JBDS-3087 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta2 > Reporter: Nick Boldt > > Today we have two installers: > * Stand-alone Installer (504M) > * Installer with EAP (642M) > Both can be used for offline install, but both are large downloads. > When installing JBDS IS offline, a user must download several archives: > * JBDS installer jar (or update site zip) > * JBDS target platform zip > * JBDS IS zip > And, there's no "stub installer for online" which would simply fetch the content needed to do the install from the update site, making the installer a much smaller (initial) download footprint. > Therefore Max has suggested that we might want to add two new installers, resulting in this list: > * Stand-alone Installer (504M) > * Installer with EAP (642M) > * Installer with Integration Stack (~750M) > * Stub Installer (~10M) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17808) Identify which installed IUs are from Early Access vs. supported/tested versions

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17808?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17808: ---------------------------------------- Yes, it's because at that time, we didn't figure out that using certification id would do the trick. Now, if it comes to comparing an installation with the set of supported artifacts, since the set of supported artifacts isn't set in stone and is subject to change independently of what user install/uninstall, I have the feeling that we'll indeed need a remote reference of what's supported, just like it seemed necessary at the beginning, before we started relying on certificationId. However, the list of supported plugins is actually already there: it's the content of main JBDS site + Discovery (non Early Access) site. So this issue just becomes a comparison between an installation, and the content of remote sites. > Identify which installed IUs are from Early Access vs. supported/tested versions > -------------------------------------------------------------------------------- > > Key: JBIDE-17808 > URL: https://issues.jboss.org/browse/JBIDE-17808 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Reporter: Nick Boldt > Fix For: 4.2.0.Beta3 > > > [~maxandersen] brought up a good point on a call today: > we have no way from within JBDS of identifying which installed IUs were installed from Early Access vs. those what were installed from Central or another "supported" location. > Thus we need some sort of UI to list installed IUs that are "Early Access". > This could be... (brainstorming now): > * a text file with the list of things installed from Early Access (features and plugins) > * a set of asterisks added to the Help > About dialogs when browsing for installed features / plugins > * a way to filter the plugin view (Help > About) to show only EA content (or exclude it) > * ... ? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3086) Change Central Discovery URLs?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3086?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3086: ------------------------------------------- I took the liberty and not repeat the base url three times. My suggestion does not change the physical arrangement of the content of sites. The root <site>, i.e. '/' is already a composite. I just suggest to composite the central location into '/' AND I suggest we don't have earlyaccess under central nor '/' because this seem to strenghten the false assumption that earlyaccess content is *part* of central. I don't follow what this would relate to with respect to discovery.xml besides changing its target url. > Change Central Discovery URLs? > ------------------------------ > > Key: JBDS-3086 > URL: https://issues.jboss.org/browse/JBDS-3086 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build, discovery, updatesite > Affects Versions: 8.0.0.Beta3 > Reporter: Nick Boldt > Assignee: Nick Boldt > > Today, the Central discovery plugin for JBDS is points to this URL: > <site>/central/core/ > and for Early Access discovery: > <site>/central/earlyaccess/ > However, Max has suggested that we simplify the first, and change the second. > I believe he wants something like this: > https://devstudio.jboss.com/updates/8.0-staging/ > https://devstudio.jboss.com/updates/8.0-development > https://devstudio.jboss.com/updates/8.0/ > and > https://devstudio.jboss.com/earlyaccess/8.0-staging/ > https://devstudio.jboss.com/earlyaccess/8.0-development/ > https://devstudio.jboss.com/earlyaccess/8.0/ > What do people think about this proposed change? > [~mickael_istria] [~maxandersen] [~dgolovin] -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 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 July 2014