July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3002) JBDS 7.1.1 installer contains jars signed by GTECyberTrust, which may not be installed on all linux systems

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3002?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3002: -------------------------------------- Fix Version/s: 8.0.0.CR1 (was: 7.1.x) > JBDS 7.1.1 installer contains jars signed by GTECyberTrust, which may not be installed on all linux systems > ----------------------------------------------------------------------------------------------------------- > > Key: JBDS-3002 > URL: https://issues.jboss.org/browse/JBDS-3002 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, updatesite > Affects Versions: 7.1.1.GA > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Fix For: 8.0.0.CR1 > > > We have jars in JBDS 7.1.1.GA which were signed using GTECyberTrust. Some linux installs do not include this root cert, so when installing, p2 rejects the cert: > {code}One or more certificates rejected. Cannot proceed with installation.{code} > Full details: https://community.jboss.org/message/866868 > *Platform details:* > {code} > Debian Jessie 64 bit > $ uname -a: > Linux Name 3.13-1-amd64 #1 SMP Debian 3.13.7-1 (2014-03-25) x86_64 GNU/Linux > $ java -version > java version "1.7.0_51" > OpenJDK Runtime Environment (IcedTea 2.4.5) (7u51-2.4.5-2) > OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode) > {code} > Note that Debian 8.0 "Jessie" is not yet released nor has a date for release been announced [0]. The latest stable Debian [1] is 7.4 "Wheezy", released on Feb 8, 2014. [2] The description for "testing" releases like Jessie is "Security updates are irregular and unreliable." [3] So... I don't think we support this OS yet. :) > [0] http://www.debian.org/releases/jessie/ > [1] http://www.debian.org/releases/ > [2] http://www.debian.org/releases/wheezy/ > [3] https://release.debian.org/ > *Steps to repro on the above platform:* > 1. Downloaded jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar > 2. Ran java -jar jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar stuck to the defaults and clicked thru > 3. Install failed with an error re certificates not being trusted > 4. Log message in ~/jbdevstudio/studio/p2/director/configuration/1396752621141.log as follows: > !ENTRY org.eclipse.equinox.p2.engine 8 0 2014-04-06 08:21:42.061 > !MESSAGE One or more certificates rejected. Cannot proceed with installation. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

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

by Rich DiCroce (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17986?page=com.atlassian.jira.plugi... ] Rich DiCroce commented on JBIDE-17986: -------------------------------------- 0.16.0.201405271551 > 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)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2513) Error: Could not create the Java Virtual Machine

by Ryan Gourley (JIRA)

[ https://issues.jboss.org/browse/JBDS-2513?page=com.atlassian.jira.plugin.... ] Ryan Gourley commented on JBDS-2513: ------------------------------------ [~maxandersen] My work machine has 8GB of RAM but with Chrome and Outlook open, there is only about 4GB left to play with. I'm not sure why 1024m didn't work in the first place, but I may play around with it without any other applications open. Thanks for the heads up! > Error: Could not create the Java Virtual Machine > ------------------------------------------------ > > Key: JBDS-2513 > URL: https://issues.jboss.org/browse/JBDS-2513 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Environment: Windows 7 64-bit, Java 7 32-bit JVM > Reporter: Burr Sutter > Assignee: Denis Golovin > Priority: Minor > Fix For: 7.0.0.Beta2 > > Attachments: 2012-11-30_1425.png, 2012-11-30_1425_001.png, Installer_JVM_Settings.png > > > Running the installer with a JRE can create an improper installation. See screenshots -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

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

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-291?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-291: -------------------------------- Assignee: Paul Leacu > 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 > Assignee: Paul Leacu > 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)

10 years, 1 month

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)

[ 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)

10 years, 1 month

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)

10 years, 1 month

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)

10 years, 1 month

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)

10 years, 1 month

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)

10 years, 1 month

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)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2014