December 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18965) use Tycho 0.22 to build JBT 4.3/JBDS 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18965?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18965: ------------------------------------ PR adjusted and replaced. Now it builds jbosstools-base w/o errors. > use Tycho 0.22 to build JBT 4.3/JBDS 9 > -------------------------------------- > > Key: JBIDE-18965 > URL: https://issues.jboss.org/browse/JBIDE-18965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.2.1.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > Tycho 0.22 is out; we should use it to build JBT 4.3/JBDS 9, and see what new fun goodies we can take advantage of, too. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-575) Add abstract to JBDS CP articles

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-575?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-575: ------------------------------------------ More abstracts added: *Create Your First Mobile Web App with JBoss Developer Studio* This article shows you how to create a new mobile web application in JBoss Developer Studio. Using a provided sample application, this article demonstrates how to generate and customize the application, deploy the application to a server, and test the application with the LiveReload-enabled mobile browser simulator BrowserSim. *Deploy Application to a Local Server with JBoss Developer Studio* This article shows you how to deploy an application to a local server from the IDE using JBoss Developer Studio tooling. The article demonstrates how to configure the IDE for available local servers, such as JBoss EAP, and use the generated server adapter for easy server management and application publishing. > Add abstract to JBDS CP articles > -------------------------------- > > Key: TOOLSDOC-575 > URL: https://issues.jboss.org/browse/TOOLSDOC-575 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: General documentation issues > Affects Versions: 4.2.0.Final > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.2.1.Final > > > There is an abstract field for CP articles. It's important that this is filled in. If the article is only accessible to subscribers that users no signed in will only see the abstract. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18669) HTML5 Palette: Group for last used/most popular items

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18669?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18669: ----------------------------------- Summary: HTML5 Palette: Group for last used/most popular items (was: HTML5 Palette: Custom palette group) > HTML5 Palette: Group for last used/most popular items > ----------------------------------------------------- > > Key: JBIDE-18669 > URL: https://issues.jboss.org/browse/JBIDE-18669 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > Attachments: palette.png > > > It would be nice to have custom HTML5 Palette group. > It should be possible for users to select which items to show in that group: > 1. Last used items > 2. The most popular items > It should be possible to limit number of items. > *Video*: http://youtu.be/cmgU4eKzJDQ > !palette.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18981) New Text Input wizard for HTML5 palette

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18981?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18981: ----------------------------------- Attachment: input.png !input.png! > New Text Input wizard for HTML5 palette > --------------------------------------- > > Key: JBIDE-18981 > URL: https://issues.jboss.org/browse/JBIDE-18981 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > Attachments: input.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18669) HTML5 Palette: Custom palette group

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18669?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18669: ----------------------------------- Description: It would be nice to have custom HTML5 Palette group. It should be possible for users to select which items to show in that group: 1. Last used items 2. The most popular items It should be possible to limit number of items. *Video*: http://youtu.be/cmgU4eKzJDQ !palette.png! was: It would be nice to have custom HTML5 Palette group. It should be possible for users to select which items to show in that group: 1. Last used items 2. The most popular items It should be possible to limit number of items. > HTML5 Palette: Custom palette group > ----------------------------------- > > Key: JBIDE-18669 > URL: https://issues.jboss.org/browse/JBIDE-18669 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > Attachments: palette.png > > > It would be nice to have custom HTML5 Palette group. > It should be possible for users to select which items to show in that group: > 1. Last used items > 2. The most popular items > It should be possible to limit number of items. > *Video*: http://youtu.be/cmgU4eKzJDQ > !palette.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18669) HTML5 Palette: Custom palette group

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18669?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18669: ----------------------------------- Attachment: palette.png > HTML5 Palette: Custom palette group > ----------------------------------- > > Key: JBIDE-18669 > URL: https://issues.jboss.org/browse/JBIDE-18669 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > Attachments: palette.png > > > It would be nice to have custom HTML5 Palette group. > It should be possible for users to select which items to show in that group: > 1. Last used items > 2. The most popular items > It should be possible to limit number of items. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18869) migrate Thym from TP to being an aggregated component

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18869?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18869: ------------------------------------ {quote} In that case Jenkins job to update and with the generic URL seems the best solution to me {quote} So we should set the parent pom to point to a generic URL like http://download.jboss.org/jbosstools/builds/staging/jbosstools-requiremen... and then only run a fresh mirror pull when you're ready to release something? Or would you prefer to set a specific versioned URL in the parent pom? > migrate Thym from TP to being an aggregated component > ----------------------------------------------------- > > Key: JBIDE-18869 > URL: https://issues.jboss.org/browse/JBIDE-18869 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, build, target-platform, updatesite > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > Because Thym changes frequently, and because Gorkem runs the project, we should treat it like a JBT project, not part of the TP. > This would allow it to be incorporated into builds more easily and would avoid TP churn. > This should be fixed in master then backported for 4.2.2 (or 4.2.3). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3296) P2 reports several locations without repositories in case product installed on different device from user home directory

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3296?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3296: ---------------------------------- So to confirm, the bug is that Eclipse or JBDS assumes the install drive can be deduced from $\{user.home}, and therefore update fails in weird ways if user.home = c:\something and install dir is d:\something-else. Correct? Can this be reproduced w/ just Eclipse doing an update of an EPP product (eg., from Luna R to SR1)? Or is this strictly a JBDS product bug? Also, is this only for Windows, because of the way it maps / to c:/ (and therefore d:\ is not accessible from a linux-like path) ? > P2 reports several locations without repositories in case product installed on different device from user home directory > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3296 > URL: https://issues.jboss.org/browse/JBDS-3296 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Affects Versions: 8.0.0.GA, 8.0.1.GA > Reporter: Denis Golovin > Assignee: Nick Boldt > Attachments: fixed.png > > > {code}org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.redhat.com/updates/8.0-development/central/core/. > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102) > at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83) > at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} > {code}org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.redhat.com/updates/8.0/central/core/. > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102) > at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83) > at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18869) migrate Thym from TP to being an aggregated component

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18869?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18869: ------------------------------------ I've created a Jenkins job to perform the mirroring from Eclipse to JBoss: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-requireme... By default it'll push to http://download.jboss.org/jbosstools/builds/staging/jbosstools-requiremen... But if you want to cut over a specific milestone into /updates/requirements/, you can pass in some value of version, such as 0.1.0-SNAPSHOT-201412181815, and end up with: http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... Then all we need to do is ensure that the JBT parent pom uses the correct mirror URL. Note that when we start rolling out the path changes in JBDS-3208, this job will need to be tweaked to publish to the new paths too. (cc: [~mickael_istria] [~gercan] [~maxandersen]) {quote}And am I blind or is there not a PR for the parent pom that is missing to define the thym repo ?{quote} Do you mean the first PR listed above? https://github.com/jbosstools/jbosstools-build/pull/161/files {quote}this is just for 4.3.0 not 4.2.0 ?{quote} We could backport this to 8.1 if we wanted. Depends on how many more Thym builds will be needed in the 8.x stream, I guess. > migrate Thym from TP to being an aggregated component > ----------------------------------------------------- > > Key: JBIDE-18869 > URL: https://issues.jboss.org/browse/JBIDE-18869 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, build, target-platform, updatesite > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > Because Thym changes frequently, and because Gorkem runs the project, we should treat it like a JBT project, not part of the TP. > This would allow it to be incorporated into builds more easily and would avoid TP churn. > This should be fixed in master then backported for 4.2.2 (or 4.2.3). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3295) Product update fails on windows if installation folder and user home are on different devices

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3295?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3295: ------------------------------------- I put this steps as to workarounds field. It would let to stay on the same device and get jbdevstudio updated. Thanks :) > Product update fails on windows if installation folder and user home are on different devices > --------------------------------------------------------------------------------------------- > > Key: JBDS-3295 > URL: https://issues.jboss.org/browse/JBDS-3295 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: p2-product > Affects Versions: 8.0.1.GA > Environment: Windows > Reporter: Denis Golovin > Assignee: Denis Golovin > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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 December 2014