January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3306) Create Deployment from Template

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3306?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3306: ----------------------------- CDW pm_ack: ? CDW release: ? > Create Deployment from Template > ------------------------------- > > Key: JBDS-3306 > URL: https://issues.jboss.org/browse/JBDS-3306 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Reporter: Burr Sutter > Priority: Blocker > > Use Case #3 > Create Deployment from Template > a) Assume OpenShift is started remotely and provides an entrypoint URL > b) Assume end-user is logged in (ignore auth for now) > c) Eclipse user will open a dialog and enter the URL from step a > d) Eclipse user will then be presented with a list of templates from the template library > (initially a set of files on the local filesystem until openshift has a real template library api) > e) The template list should allow sorting so that higher priority items are at the top > We will likely need some form of categorization for templates also > f) The template list should be searchable by keyword > g) Eclipse user will select a particular template and > h) Create a new openshift deployment based on selected template > i) follow steps JBDS-3297 f through j (clone, import, project facets, etc) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3306) Create Deployment from Template

by Burr Sutter (JIRA)

Burr Sutter created JBDS-3306: --------------------------------- Summary: Create Deployment from Template Key: JBDS-3306 URL: https://issues.jboss.org/browse/JBDS-3306 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Reporter: Burr Sutter Priority: Blocker Use Case #3 Create Deployment from Template a) Assume OpenShift is started remotely and provides an entrypoint URL b) Assume end-user is logged in (ignore auth for now) c) Eclipse user will open a dialog and enter the URL from step a d) Eclipse user will then be presented with a list of templates from the template library (initially a set of files on the local filesystem until openshift has a real template library api) e) The template list should allow sorting so that higher priority items are at the top We will likely need some form of categorization for templates also f) The template list should be searchable by keyword g) Eclipse user will select a particular template and h) Create a new openshift deployment based on selected template i) follow steps JBDS-3297 f through j (clone, import, project facets, etc) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18872) Promote JBoss Tools CAT in JBT/JBDS About box

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18872?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-18872: ----------------------------------- Assignee: (was: Xavier Coulon) > Promote JBoss Tools CAT in JBT/JBDS About box > --------------------------------------------- > > Key: JBIDE-18872 > URL: https://issues.jboss.org/browse/JBIDE-18872 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.2.0.Final > Reporter: Vlado Pakan > Fix For: 4.2.2.Final > > > Would be nice to put link to JBT CAT or JBT CAT logo with link to it to JBDS/JBT About box to make JBT CAT more visible. > New link/image should be visible without resizing About box -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18872) Promote JBoss Tools CAT in JBT/JBDS About box

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18872?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18872: ---------------------------------------- I'm not convinced this would help much... Do our user really look at this "About" dialog? > Promote JBoss Tools CAT in JBT/JBDS About box > --------------------------------------------- > > Key: JBIDE-18872 > URL: https://issues.jboss.org/browse/JBIDE-18872 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.2.0.Final > Reporter: Vlado Pakan > Assignee: Xavier Coulon > Fix For: 4.2.2.Final > > > Would be nice to put link to JBT CAT or JBT CAT logo with link to it to JBDS/JBT About box to make JBT CAT more visible. > New link/image should be visible without resizing About box -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18872) Promote JBoss Tools CAT in JBT/JBDS About box

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18872?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18872: ----------------------------------- Component/s: central (was: build) > Promote JBoss Tools CAT in JBT/JBDS About box > --------------------------------------------- > > Key: JBIDE-18872 > URL: https://issues.jboss.org/browse/JBIDE-18872 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.2.0.Final > Reporter: Vlado Pakan > Assignee: Xavier Coulon > Fix For: 4.2.2.Final > > > Would be nice to put link to JBT CAT or JBT CAT logo with link to it to JBDS/JBT About box to make JBT CAT more visible. > New link/image should be visible without resizing About box -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18948) Include new jbosstools-javaee/batch component into aggregated update site

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18948?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18948: ---------------------------------------- If this becomes part of Core Tools and Marketplace listing, then there is no value in putting it in Central for the same version since we can explect that everyone who installed JBoss Tools would automatically get the batch tools included. > Include new jbosstools-javaee/batch component into aggregated update site > ------------------------------------------------------------------------- > > Key: JBIDE-18948 > URL: https://issues.jboss.org/browse/JBIDE-18948 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15135) Attach metadata during assembly instead of publish time

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15135?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-15135: ----------------------------------- Fix Version/s: 4.3.0.Alpha1 (was: 4.2.x) > Attach metadata during assembly instead of publish time > ------------------------------------------------------- > > Key: JBIDE-15135 > URL: https://issues.jboss.org/browse/JBIDE-15135 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > In order to make it easier to deal with Nexus and to have an homogeneous way to access build metadata (commit id), it would be interesting to move creation of metadata at assembly time (same time as when we create index and so on), and put it directly into the site. > Then whether we use Nexus or a home-made publication, we are sure that we can access metadata whenever we can access the binaries. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-166) Deploying BPEL project to a server is not working

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-166?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-166: ---------------------------------- [~apodhrad] [~bbrodt] - Hey - since this is exceedingly old but has already been re-opened - is there consensus that it can be closed? > Deploying BPEL project to a server is not working > ------------------------------------------------- > > Key: JBTIS-166 > URL: https://issues.jboss.org/browse/JBTIS-166 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPEL > Affects Versions: 4.1.2 > Environment: Eclipse 3.7.2 + JBoss AS 5.1.0 + RiftSaw 2.3.0 > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Priority: Critical > Attachments: deploying_as51.log, deploying_as51.png, running_as51.log, running_as51.png > > > This bug was moved from JBIDE (from version 3.3) and is still present. The problem is as follows: > Installing the BPEL feature from JBTIS 4.1.2 update site is not enough for full working with BPEL and JBoss AS. > You need to install JBoss AS feature from JBT Core update site. Note that this doesn't happen in JBDS (there already is the AS plugin). > Without explicit installing AS plugin I'm getting two erros (when starting the server and when trying to deploy bpel project). > See the attachments. > Original description: > Deploying BPEL project to a server, which is created using JBoss AS 5.1 adapter, is not working - it seems that nothing happens. > But if I try to deploy the same project to a server created using JBoss Application Platform 5.x, it works fine. > In JBDS 4 and 5 it works fine for both adapters. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18995) Early Access features can be installed from JBoss Tools p2 repository even if 'Enable Early Access' is disabled in Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18995?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18995: ---------------------------------------- Those files are better being updated manually on download.jboss.org. Release process shouldn't depend on this files from the discovery plugins, and should instead depend on the ones on download.jboss.org. IMO, the simplest thing is to remove them, and to fix the release process accordingly so it doesn't need those files. > Early Access features can be installed from JBoss Tools p2 repository even if 'Enable Early Access' is disabled in Central > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18995 > URL: https://issues.jboss.org/browse/JBIDE-18995 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.1.Final > Reporter: Denis Golovin > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.2.1.Final > > Attachments: ea-disabled.png, ea-installed.png > > > I noticed central has "(Early Access Installed)" sign in after I installed everything from JBos Tools stable p2 repository. > !ea-installed.png! > "Enable Early Access" checkbox is not set by default in Central Editor > !ea-disabled.png! > This means I bypassed warning dialog in this scenario. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18995) Early Access features can be installed from JBoss Tools p2 repository even if 'Enable Early Access' is disabled in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18995?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18995: ------------------------------------ As I started removing them I realized that this impacts the release process (because ide-config.properties points to the staging discovery site, which includes the earlyaccess.properties file), so maybe we should add these files into the EA site itself? That way when we publish a new EA site + zip to staging or release, we'll just have the new file colocated in the update site, and publishing is simpler (ide-config.props can just point at the staging EA site, instead of the staging discovery site). [~mickael_istria] If you agree, I can add this change/requirement to JBIDE-18984. > Early Access features can be installed from JBoss Tools p2 repository even if 'Enable Early Access' is disabled in Central > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18995 > URL: https://issues.jboss.org/browse/JBIDE-18995 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.1.Final > Reporter: Denis Golovin > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.2.1.Final > > Attachments: ea-disabled.png, ea-installed.png > > > I noticed central has "(Early Access Installed)" sign in after I installed everything from JBos Tools stable p2 repository. > !ea-installed.png! > "Enable Early Access" checkbox is not set by default in Central Editor > !ea-disabled.png! > This means I bypassed warning dialog in this scenario. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 January 2015