May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18772) Include publish steps in pom files

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18772: ----------------------------------- Summary: Include publish steps in pom files (was: Include publish.sh in parent pom as versioned maven dependency) > Include publish steps in pom files > ---------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > Attachments: jbds-publish-to-snapshots.png > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19637) Runtime download not working from New Server dialog

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19637?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-19637: --------------------------------------- The attached PR tries to fix the issue by adding a selection listener after enabling the link. Can anyone test it on Mac? > Runtime download not working from New Server dialog > --------------------------------------------------- > > Key: JBIDE-19637 > URL: https://issues.jboss.org/browse/JBIDE-19637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: help_wanted > Fix For: 4.3.0.Beta1 > > > When you go through Servers view -> New Server -> EAP 6.1 -> New Runtime and then click "Download and install runtime...", it won't do anything. > If you go through Preferences -> Server -> Runtime Environments -> Add -> EAP 6.1+ and then click the Download button, it will work. > This issue applies to both JBDS 8.1.0.GA and JBoss Tools 4.3.0.Alpha2 testing build, but I doubt we will be able to fix this for 4.2.x. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19638) Web Service wizard - drop-down menus too narrow by default

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19638?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-19638: --------------------------------------- I think it is a GTK3 issue. There are a few similar issues: https://bugs.eclipse.org/bugs/show_bug.cgi?id=437850 https://bugs.eclipse.org/bugs/show_bug.cgi?id=431425 I have tried to reproduce the issue on Eclipse Luna, Mars M6 and M7, GTK 3.8.6, GTK 3.10.8 (Ubuntu 14.04), GTK 3.12.0, GTK 3.14.12, but haven't succeeded. Which GTK3 does Fedora 20 use? > Web Service wizard - drop-down menus too narrow by default > ---------------------------------------------------------- > > Key: JBIDE-19638 > URL: https://issues.jboss.org/browse/JBIDE-19638 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.3.0.Alpha2 > Reporter: Jan Richter > Assignee: Brian Fitzpatrick > Priority: Minor > Fix For: 4.3.0.Beta1 > > Attachments: bundles.info, ws.png, wstester.png > > > By default the drop down menus for 'web service type' and 'client type' are too narrow (vertically) for the text inside them to be rendered properly. > Resizing the wizard in any way will resize the drop downs to standard height which won't change from that moment on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19736) Update template list page to get 'openshift' templates and group accordingly

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19736?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19736: --------------------------------------- [~mlabuda] [~adietish] Assuming you have templates loaded into a project namespace and the 'openshift' namespace. # Right click on your OpenShift project namespace and 'create application' # Verify on the first page that list the templates you see two 'root' nodes: openshift & your project namespace # Verify children of the root nodes are the templates for each namespace. > Update template list page to get 'openshift' templates and group accordingly > ---------------------------------------------------------------------------- > > Key: JBIDE-19736 > URL: https://issues.jboss.org/browse/JBIDE-19736 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > > When creating a template, a user should be able to choose from their project templates and those that are part of the configured (openshift) namespace. Update The template list page get templates from openshift namespace and to group templates under an appropriate folder (project or openshift) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19476) Add label validation

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19476?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19476: --------------------------------------- [~mlabuda] Assuming you have templates loaded into your namespace: # Right-click on an OpenShift project and 'Create Application' # Choose a template # Click through the wizard until you come to the 'edit label page' # Validate you can not add, modify, edit, delete 'readonly' labels. Currently only the label 'template' meets this criteria # Validate you can add, edit, modify a label and that you are warned if the value does not meet the allowable format. Validation is duplicated from here: https://github.com/openshift/origin/blob/master/assets/app/scripts/direct... and the ultimate authority is here: https://github.com/openshift/origin/blob/master/Godeps/_workspace/src/git... > Add label validation > -------------------- > > Key: JBIDE-19476 > URL: https://issues.jboss.org/browse/JBIDE-19476 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > Add label key and value validations to the 'label' page in accordance of what is valid in Kubernetes. This should be part of the 'edit label' page that will be presented to a user -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3411) have installer build actually use M6 p2 product build

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3411?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3411: -------------------------------- > have installer build actually use M6 p2 product build > ----------------------------------------------------- > > Key: JBDS-3411 > URL: https://issues.jboss.org/browse/JBDS-3411 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer, updatesite > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.Beta1 > > > talking with [~prapicault] I learned that since M6 the following changes are required for proper working p2 product/osx build: > {code} > <products> > <product> > ... > <rootFolders> > <macosx>MyProduct.app</macosx> > </rootFolders> > </product> > {code} > And to use tycho 0.23-snapshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3411) have installer build actually use M6 p2 product build

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3411?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3411: ------------------------------- CDW qa_ack: + (was: ?) > have installer build actually use M6 p2 product build > ----------------------------------------------------- > > Key: JBDS-3411 > URL: https://issues.jboss.org/browse/JBDS-3411 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer, updatesite > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.Beta1 > > > talking with [~prapicault] I learned that since M6 the following changes are required for proper working p2 product/osx build: > {code} > <products> > <product> > ... > <rootFolders> > <macosx>MyProduct.app</macosx> > </rootFolders> > </product> > {code} > And to use tycho 0.23-snapshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3411) have installer build actually use M6 p2 product build

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3411?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3411: ----------------------------- CDW release: + (was: ?) > have installer build actually use M6 p2 product build > ----------------------------------------------------- > > Key: JBDS-3411 > URL: https://issues.jboss.org/browse/JBDS-3411 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer, updatesite > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.Beta1 > > > talking with [~prapicault] I learned that since M6 the following changes are required for proper working p2 product/osx build: > {code} > <products> > <product> > ... > <rootFolders> > <macosx>MyProduct.app</macosx> > </rootFolders> > </product> > {code} > And to use tycho 0.23-snapshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19757) Consider using main JBT site for server discovery

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19757: ------------------------------------ Excellent, then we should be able to symlink to the latest milestone composite site... but according to Mickael's notes above, that's not what he tested. Can we verify that a composite site (with no site.xml in its child sites) as target for resolving the WTP discovery now works? > Consider using main JBT site for server discovery > ------------------------------------------------- > > Key: JBIDE-19757 > URL: https://issues.jboss.org/browse/JBIDE-19757 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, server > Reporter: Mickael Istria > Fix For: 4.3.0.Beta1 > > > With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml. > Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... ) > In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery. > However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing > {code} > !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088 > !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null". > {code} > because we are lines specifying bundle but no version in the site.xml. > [~nickboldt] What are those site.xml useful for? Could we get rid of them? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18772: ------------------------------------ @max: 0. the target here is Beta1, which gives us lots of time to keep it open and solve remaining questions around how to use angle brackets to publish instead of shell script. But if a new JIRA makes ya'll happ(ier) feel free to open another. How else are we going to get to JBIDE-20000 ? :D 1. This JIRA needs to be renamed. publish.sh is deprecated. You want rsync.sh: https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.3.x/p... See examples/screenshots above which demonstrate how to pass in a -DESTINATION that's not the default server. 2. Publishing must by definition be many steps because, for the best example of JBDS, we publish to two different servers (www.qa and devstudio.redhat). We used to have a publish.sh hardcoded to do all sorts of complicated steps in one call (simply `publish.sh -jbds`) but that was deemed *Just Bad*, so we now have one generic script (rsync.sh) which can push from anywhere to anywhere else. The only caveat is that you now must call it several times to push to multiple destinations. > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > Attachments: jbds-publish-to-snapshots.png > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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 May 2015