July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17977) Server adapter: "configure markers" missing in server adapter context menu

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17977?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17977: ------------------------------------- Estimated Difficulty: Low > Server adapter: "configure markers" missing in server adapter context menu > -------------------------------------------------------------------------- > > Key: JBIDE-17977 > URL: https://issues.jboss.org/browse/JBIDE-17977 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Max Rydahl Andersen > Labels: server_adapter > Fix For: 4.2.0.CR1 > > > configure markers available from the project context menu should also be accessible from server context menu. > seem to have been missed when we aligned the context markers. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17977) Server adapter: "configure markers" missing in server adapter context menu

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17977?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17977: ------------------------------------- Summary: Server adapter: "configure markers" missing in server adapter context menu (was: configure markers missing in server adapter context menu) > Server adapter: "configure markers" missing in server adapter context menu > -------------------------------------------------------------------------- > > Key: JBIDE-17977 > URL: https://issues.jboss.org/browse/JBIDE-17977 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Max Rydahl Andersen > Labels: server_adapter > Fix For: 4.2.0.CR1 > > > configure markers available from the project context menu should also be accessible from server context menu. > seem to have been missed when we aligned the context markers. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-290) enable jboss tools usage tracking for plugins installed directly

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-290?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-290: ---------------------------------- Looks like you've got the older plugins covered (BPEL, ESB, jBPM - and you've got Modeshape and drools). We could cover the Modeshape JCR and add BPMN2, Fuse Tooling and Teiid Designer. I can drive this with the component owners. > enable jboss tools usage tracking for plugins installed directly > ---------------------------------------------------------------- > > Key: JBTIS-290 > URL: https://issues.jboss.org/browse/JBTIS-290 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Critical > > I think it is time we get integration stack components stats to show up more consistently in stats (right now we only collect switchyard - we should do more) > There are two parts to it. > 1) add a line to https://github.com/jbosstools/jbosstools-base/blob/master/usage/plugins/o... for the key feature we want to count as "one install" > 2) add an *optional* dependency to your plugins to org.jboss.tools.usage - this ensures the statistics gathering happens no matter how the feature gets installed. > The following line should be added to plugins manifest.mf: > {code} > org.jboss.tools.usage;resolution:=optional;x-installation:=greedy > {code} > Example: https://github.com/jbosstools/jbosstools-server/blob/master/archives/plug... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-290) enable jboss tools usage tracking for plugins installed directly

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-290?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-290: -------------------------------- Assignee: Paul Leacu > enable jboss tools usage tracking for plugins installed directly > ---------------------------------------------------------------- > > Key: JBTIS-290 > URL: https://issues.jboss.org/browse/JBTIS-290 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Critical > > I think it is time we get integration stack components stats to show up more consistently in stats (right now we only collect switchyard - we should do more) > There are two parts to it. > 1) add a line to https://github.com/jbosstools/jbosstools-base/blob/master/usage/plugins/o... for the key feature we want to count as "one install" > 2) add an *optional* dependency to your plugins to org.jboss.tools.usage - this ensures the statistics gathering happens no matter how the feature gets installed. > The following line should be added to plugins manifest.mf: > {code} > org.jboss.tools.usage;resolution:=optional;x-installation:=greedy > {code} > Example: https://github.com/jbosstools/jbosstools-server/blob/master/archives/plug... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3078) 7 icon(s) not replaced in laucher.exe @ com.jboss.devstudio.core.site

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3078?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3078: -------------------------------------- Note that if it is easier to maintain, the .product configuration file allows to specify the various icons separately (1 file for each size/depth) instead of aggregating them in a single .ico file. > 7 icon(s) not replaced in laucher.exe @ com.jboss.devstudio.core.site > --------------------------------------------------------------------- > > Key: JBDS-3078 > URL: https://issues.jboss.org/browse/JBDS-3078 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, updatesite > Affects Versions: 8.0.0.Beta3 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 8.0.0.CR1 > > Attachments: 128_jbds_icon.png > > > Building locally: > {code} > [INFO] --- tycho-p2-publisher-plugin:0.20.0:publish-products (default-publish-products) @ com.jboss.devstudio.core.site --- > Error - 7 icon(s) not replaced in /tmp/p2.brandingIron9054877340821028927/launcher.exe using /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/products/com.jboss.devstudio.core.package/jbds.ico > Error - 7 icon(s) not replaced in /tmp/p2.brandingIron489909634983575622/launcher.exe using /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/products/com.jboss.devstudio.core.package/jbds.ico > {code} > Building in Jenkins: > {code} > [INFO] --- tycho-p2-publisher-plugin:0.20.0:publish-products (default-publish-products) @ com.jboss.devstudio.core.site --- > Error - 7 icon(s) not replaced in /tmp/p2.brandingIron5040285231221120320/launcher.exe using /qa/hudson_workspace/workspace/devstudio.product_master/sources/product/site/target/products/com.jboss.devstudio.core.package/jbds.ico > Error - 7 icon(s) not replaced in /tmp/p2.brandingIron8242740933405392439/launcher.exe using /qa/hudson_workspace/workspace/devstudio.product_master/sources/product/site/target/products/com.jboss.devstudio.core.package/jbds.ico{code} > Is this a problem? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3078) 7 icon(s) not replaced in laucher.exe @ com.jboss.devstudio.core.site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3078?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3078: ----------------------------- Attachment: 128_jbds_icon.png [~james.cobb] can you make use a 256x256x32 icon to include in JBDS? Largest one I have on file is this 128x128 one here: https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... !128_jbds_icon.png! > 7 icon(s) not replaced in laucher.exe @ com.jboss.devstudio.core.site > --------------------------------------------------------------------- > > Key: JBDS-3078 > URL: https://issues.jboss.org/browse/JBDS-3078 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, updatesite > Affects Versions: 8.0.0.Beta3 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 8.0.0.CR1 > > Attachments: 128_jbds_icon.png > > > Building locally: > {code} > [INFO] --- tycho-p2-publisher-plugin:0.20.0:publish-products (default-publish-products) @ com.jboss.devstudio.core.site --- > Error - 7 icon(s) not replaced in /tmp/p2.brandingIron9054877340821028927/launcher.exe using /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/products/com.jboss.devstudio.core.package/jbds.ico > Error - 7 icon(s) not replaced in /tmp/p2.brandingIron489909634983575622/launcher.exe using /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/products/com.jboss.devstudio.core.package/jbds.ico > {code} > Building in Jenkins: > {code} > [INFO] --- tycho-p2-publisher-plugin:0.20.0:publish-products (default-publish-products) @ com.jboss.devstudio.core.site --- > Error - 7 icon(s) not replaced in /tmp/p2.brandingIron5040285231221120320/launcher.exe using /qa/hudson_workspace/workspace/devstudio.product_master/sources/product/site/target/products/com.jboss.devstudio.core.package/jbds.ico > Error - 7 icon(s) not replaced in /tmp/p2.brandingIron8242740933405392439/launcher.exe using /qa/hudson_workspace/workspace/devstudio.product_master/sources/product/site/target/products/com.jboss.devstudio.core.package/jbds.ico{code} > Is this a problem? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17988) JAX-RS Explorer doesn't show endpoint URI for fresh project in new workspace

by Radoslav Rábara (JIRA)

Radoslav Rábara created JBIDE-17988: --------------------------------------- Summary: JAX-RS Explorer doesn't show endpoint URI for fresh project in new workspace Key: JBIDE-17988 URL: https://issues.jboss.org/browse/JBIDE-17988 Project: Tools (JBoss Tools) Issue Type: Bug Components: webservices Affects Versions: 4.2.0.Beta3 Environment: Java 7, WildFly 8.1, Ubuntu 12.04 Reporter: Radoslav Rábara Fix For: 4.2.0.CR1 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-290) enable jboss tools usage tracking for plugins installed directly

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBTIS-290: ----------------------------------------- Summary: enable jboss tools usage tracking for plugins installed directly Key: JBTIS-290 URL: https://issues.jboss.org/browse/JBTIS-290 Project: JBoss Tools Integration Stack Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Max Rydahl Andersen Priority: Critical I think it is time we get integration stack components stats to show up more consistently in stats (right now we only collect switchyard - we should do more) There are two parts to it. 1) add a line to https://github.com/jbosstools/jbosstools-base/blob/master/usage/plugins/o... for the key feature we want to count as "one install" 2) add an *optional* dependency to your plugins to org.jboss.tools.usage - this ensures the statistics gathering happens no matter how the feature gets installed. The following line should be added to plugins manifest.mf: {code} org.jboss.tools.usage;resolution:=optional;x-installation:=greedy {code} Example: https://github.com/jbosstools/jbosstools-server/blob/master/archives/plug... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17983) track installations of JBoss Fuse Tooling

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17983?page=com.atlassian.jira.plugi... ] Lars Heinemann edited comment on JBIDE-17983 at 7/29/14 7:03 AM: ----------------------------------------------------------------- FUSE("org.fusesource.ide.camel.editor.feature") would be the current naming. Thats the camel editor feature and I guess most will install it. Later on we could use a "core" feature shared by all the other features...see etherpad about reorg fuse tooling. was (Author: lhein): FUSE("org.fusesource.ide.camel.editor.feature") would be the current naming. > track installations of JBoss Fuse Tooling > ----------------------------------------- > > Key: JBIDE-17983 > URL: https://issues.jboss.org/browse/JBIDE-17983 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: usage > Affects Versions: 4.2.0.Beta3 > Reporter: Lars Heinemann > Assignee: Max Rydahl Andersen > > We should track installations of JBoss Fuse Tooling. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17983) track installations of JBoss Fuse Tooling

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17983?page=com.atlassian.jira.plugi... ] Lars Heinemann commented on JBIDE-17983: ---------------------------------------- FUSE("org.fusesource.ide.camel.editor.feature") would be the current naming. > track installations of JBoss Fuse Tooling > ----------------------------------------- > > Key: JBIDE-17983 > URL: https://issues.jboss.org/browse/JBIDE-17983 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: usage > Affects Versions: 4.2.0.Beta3 > Reporter: Lars Heinemann > Assignee: Max Rydahl Andersen > > We should track installations of JBoss Fuse Tooling. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 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