July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17989) keyword used for plugin tracking is missing majority of times on GA

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17989?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17989: --------------------------------------------- example query that shows something is not right: https://www.google.com/analytics/web/?hl=en#report/acquisition-channels/a... > keyword used for plugin tracking is missing majority of times on GA > ------------------------------------------------------------------- > > Key: JBIDE-17989 > URL: https://issues.jboss.org/browse/JBIDE-17989 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Reporter: Max Rydahl Andersen > Priority: Blocker > > looking at tracking numbers i'm seeing more and more requests where the keywords are not making it into the result. > Meaning we can't see how many have installed the various plugins. > What is weird *some* do and others do not have it. > Need to track down the reason for that being missed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17986) Bundled version of m2e-mavenarchiver is broken

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17986?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-17986: ------------------------------------- What version did you get? > Bundled version of m2e-mavenarchiver is broken > ---------------------------------------------- > > Key: JBIDE-17986 > URL: https://issues.jboss.org/browse/JBIDE-17986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.2.0.Beta3 > Reporter: Rich DiCroce > > The version of m2e-mavenarchiver that is bundled in JBoss Tools seems to be broken. I was not getting any descriptors generated. Upgrading to the latest version fixes the problem. See http://repository.takari.io:8081/nexus/content/sites/m2e.extras/m2eclipse... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17989) keyword used for plugin tracking is missing majority of times on GA

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-17989: ------------------------------------------- Summary: keyword used for plugin tracking is missing majority of times on GA Key: JBIDE-17989 URL: https://issues.jboss.org/browse/JBIDE-17989 Project: Tools (JBoss Tools) Issue Type: Bug Components: usage Reporter: Max Rydahl Andersen Priority: Blocker looking at tracking numbers i'm seeing more and more requests where the keywords are not making it into the result. Meaning we can't see how many have installed the various plugins. What is weird *some* do and others do not have it. Need to track down the reason for that being missed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-291) New 4.2.0 alpha of base target required

by Paul Richardson (JIRA)

Paul Richardson created JBTIS-291: ------------------------------------- Summary: New 4.2.0 alpha of base target required Key: JBTIS-291 URL: https://issues.jboss.org/browse/JBTIS-291 Project: JBoss Tools Integration Stack Issue Type: Bug Security Level: Public (Everyone can see) Components: target-platform Affects Versions: 4.2.0.Alpha5-TP Reporter: Paul Richardson Priority: Critical Fix For: 4.2.0.Beta1-TP The locus component of the base target has been respun hence the plugins are appended with v20131024-0922-B66 and no longer v20131024-0922-B64. Consequently, the target does not resolve correctly due to {code} Adding repository https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/lo... [exec] [ERROR] Internal error: java.lang.RuntimeException: Failed to resolve target definition /home/scorpion/.m2/repository/org/jboss/tools/target-platforms/komodo/1.0.0-SNAPSHOT/komodo-1.0.0-SNAPSHOT-komodo.target: Could not find "org.jboss .tools.locus.jcip.annotations/1.0.0.Final-v20131024-0922-B64" in the repositories of the current location -> [Help 1] [exec] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Failed to resolve target definition /home/scorpion/.m2/repository/org/jboss/tools/target-platforms/komodo/1.0.0-SNAPSHOT/komodo-1.0.0-SNAPSHOT-komodo. target {code} Note: komodo is the renamed base target. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17700) project archives initialization fails, cascades to server publishing, due to strange classloader

by Oliver Pfau (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17700?page=com.atlassian.jira.plugi... ] Oliver Pfau commented on JBIDE-17700: ------------------------------------- Could not reproduce the problem by now. > project archives initialization fails, cascades to server publishing, due to strange classloader > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-17700 > URL: https://issues.jboss.org/browse/JBIDE-17700 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, maven, server > Environment: Win 7, Eclilpse Luna, JBoss Tools (via market place) > Reporter: Oliver Pfau > Assignee: Rob Stryker > Priority: Critical > Labels: respin-b > Fix For: 4.2.0.Beta3 > > Attachments: jbosstools-diagnostics-20140707141907.zip, jstack.txt, pom.xml > > > When I publish my war to jboss 7.1 the following error occurs: > An internal error occurred during: "Publishing to JBoss AS 7.1...". > Could not initialize class de.schlichtherle.io.ArchiveControllers -- 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)

[ https://issues.jboss.org/browse/JBTIS-290?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-290: ------------------------------------------- Yes, some/most are covered in #1, #2 is the missing piece to track installs that does not involve other plugins that include usage. > 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] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-17686: ---------------------------------------- Summary: get TCF and RSE terminals to coexist without bad UX of multiple terminals (was: ensure TCF terminal is in jboss tools/devstudio) changed title since the issue has moved since then. > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.CR1 > > Attachments: eclipse-can-has-many-consoles.png > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) ensure TCF terminal is in jboss tools/devstudio

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17686: --------------------------------------------- Yes, you are correct this is the problem and no I do not have a implementation suggestion since I have not looked into the details of how it works. I fear it is not doable. I responded with what I knew and it now turns out TCF and RSE are not done in a coherent way thus this issue cannot be solved trivially. The issue is currently assigned to me to look at. If you want to look that would be great and suggest how to fix on RSE/TCF side that would be great but I do not expect it to be fixed in Luna timeframe at this time. > ensure TCF terminal is in jboss tools/devstudio > ----------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.CR1 > > Attachments: eclipse-can-has-many-consoles.png > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14713) jcip.annotations have wrong license in locus

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14713?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14713: --------------------------------------------- [~b.eckenfels] we dont actually use jcip.annotations outside our test suite and we do obey the license by mentioning it in the feature. Not sure what you mean by "for the AS modules" itself ? we don't use this in any of the jboss server tools plugins. > jcip.annotations have wrong license in locus > -------------------------------------------- > > Key: JBIDE-14713 > URL: https://issues.jboss.org/browse/JBIDE-14713 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, locus > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.CR1 > > > jcip.annotations is actually not common creative, its common creative attribution license. Also means anyone that uses this needs to include the copyright notice in their feature.xml > see https://github.com/nickboldt/jbosstools-locus/pull/4 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17960) "The specified JRE installation does not exist"

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17960?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17960: ------------------------------------- Beta3 has been released. Feel free to let us know how this works :) > "The specified JRE installation does not exist" > ----------------------------------------------- > > Key: JBIDE-17960 > URL: https://issues.jboss.org/browse/JBIDE-17960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Karl Pietrzak > Priority: Minor > Fix For: 4.2.0.CR1 > > Attachments: jbossastools-bad.jre.swf > > > h3. What > If you get a ""The specified JRE installation does not exist" error, JBoss Tools puts the entry in the Servers section as "Starting...", which is inaccurate. > h3. Screencast > !jbossastools-bad.jre.swf! > If the above embedded SWF doesn't work for you, you can watch it at http://screencast.com/t/bytN53lp -- 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