January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3331) Installation of JBDS/JBoss Tools into Red Hat Developer Toolset

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3331?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3331: ---------------------------------- Workarounds and related upstream problems reported here: JBIDE-16290 and JBIDE-18667 > Installation of JBDS/JBoss Tools into Red Hat Developer Toolset > --------------------------------------------------------------- > > Key: JBDS-3331 > URL: https://issues.jboss.org/browse/JBDS-3331 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: updatesite > Environment: RHEL Desktop > Reporter: Burr Sutter > Assignee: Burr Sutter > Attachments: Download_EAP.png, log, Non_reproducible_error.png, RH_Dev_Toolset.png, Welcome.png > > > As a RHEL Desktop user and application developer, I wish to install the JBDS/JBoss Tools features/plug-ins into my previously installed version of DTS - Developer Toolset > https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/ > Help - Install New Software -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19056: ------------------------------------ Good point -- I'm just wondering how much duplication we need in terms of checking. But this would certainly be better than having to nag people via JIRAs (JBIDE-19073, JBIDE-19074, JBIDE-19075, JBIDE-19076, JBIDE-19077) and the mailing list since they'd see the failure immediately in their local builds. Assuming they run them locally, of course. ;) > A Mojo to validate a version (compared to baseline) > --------------------------------------------------- > > Key: JBIDE-19056 > URL: https://issues.jboss.org/browse/JBIDE-19056 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > > We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released. > Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-382) BPMN2 modeler is available at JBDS-IS 8.0.0.CR1 site

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-382?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-382: ----------------------------- Attachment: tp1.png tp2.png Categorized looks fine. Uncategorized exposes JBTIS TP dependencies - by default unchecked. > BPMN2 modeler is available at JBDS-IS 8.0.0.CR1 site > ---------------------------------------------------- > > Key: JBTIS-382 > URL: https://issues.jboss.org/browse/JBTIS-382 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.CR1 > Environment: 8.0.2.GA + JBDS-IS 8.0.0.CR1 (no early access) > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: tp1.png, tp2.png > > > BPMN2 modeler is available at JBDS-IS 8.0.0.CR1 site where should not be. > By default this feature is not visible when you install integration stack from the update site. But when you uncheck "Group item by category" the feature is available and can be installed. Moreover, the old version of BPMN2 modeler is installed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19056: ---------------------------------------- Yes, but the main thing is that this is done automatically, at build time, so this makes build fails immediatly if version is not bumped. So we notice issue before publishing the artifacts instead of discovering this in the last development build or when staging a new release. It's much faster and earlier feedback. > A Mojo to validate a version (compared to baseline) > --------------------------------------------------- > > Key: JBIDE-19056 > URL: https://issues.jboss.org/browse/JBIDE-19056 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > > We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released. > Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19056: ------------------------------------ Sounds like something in vwatch already... https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/vwatch instead of defining a single URL baseline, it uses up to N JBDS installs as baselines and can diff plugin/feature versions, compare MD5 sums, etc. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... See also JBIDE-19072 and linked/child issues. > A Mojo to validate a version (compared to baseline) > --------------------------------------------------- > > Key: JBIDE-19056 > URL: https://issues.jboss.org/browse/JBIDE-19056 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > > We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released. > Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3331) Installation of JBDS/JBoss Tools into Red Hat Developer Toolset

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3331?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3331: ------------------------------- Attachment: log Non_reproducible_error.png Download_EAP.png Welcome.png RH_Dev_Toolset.png Performed these steps on RHEL 6.5: Configured access to Red Hat Developer Toolset sudo subscription-manager repos --enable rhel-workstation-rhscl-6-beta-debug-rpms sudo subscription-manager repos --enable rhel-workstation-rhscl-6-beta-source-rpms sudo subscription-manager repos --enable rhel-workstation-rhscl-6-debug-rpms sudo subscription-manager repos --enable rhel-workstation-rhscl-6-source-rpms sudo subscription-manager repos --enable rhel-workstation-rhscl-6-beta-rpms sudo subscription-manager repos --enable rhel-workstation-rhscl-6-beta-debug-rpms sudo subscription-manager repos --enable rhel-workstation-rhscl-6-rpms Installed Red Hat Developer Toolset sudo yum install devtoolset-3 Opened Eclipse, installed (Abridged) JBoss Tools 4.2.2 from: http://download.jboss.org/jbosstools/updates/stable/luna/ (Welcome screen is blank/white) Restarted Eclipse, Attempted to Install Kitchensink web quickstart Exception raised in trying to download/install EAP runtime: Unhandled event loop exception No more handles (java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: no swt-xulrunner-gtk-4427 in java.library.path no swt-xulrunner-gtk in java.library.path Can't load library: /home/jbossqa/.swt/lib/linux/x86_64/libswt-xulrunner-gtk-4427.so Can't load library: /home/jbossqa/.swt/lib/linux/x86_64/libswt-xulrunner-gtk.so ) (Installed EAP 6.2 outside of IDE and continued) Maven repo updated correctly, app builds. Installed JBoss helloworld app Builds cleanly, deploys, app can be accessed fron client See attached screenshots and eclipse log file. > Installation of JBDS/JBoss Tools into Red Hat Developer Toolset > --------------------------------------------------------------- > > Key: JBDS-3331 > URL: https://issues.jboss.org/browse/JBDS-3331 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: updatesite > Environment: RHEL Desktop > Reporter: Burr Sutter > Assignee: Len DiMaggio > Attachments: Download_EAP.png, log, Non_reproducible_error.png, RH_Dev_Toolset.png, Welcome.png > > > As a RHEL Desktop user and application developer, I wish to install the JBDS/JBoss Tools features/plug-ins into my previously installed version of DTS - Developer Toolset > https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/ > Help - Install New Software -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3331) Installation of JBDS/JBoss Tools into Red Hat Developer Toolset

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3331?page=com.atlassian.jira.plugin.... ] Len DiMaggio reassigned JBDS-3331: ---------------------------------- Assignee: Burr Sutter (was: Len DiMaggio) > Installation of JBDS/JBoss Tools into Red Hat Developer Toolset > --------------------------------------------------------------- > > Key: JBDS-3331 > URL: https://issues.jboss.org/browse/JBDS-3331 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: updatesite > Environment: RHEL Desktop > Reporter: Burr Sutter > Assignee: Burr Sutter > Attachments: Download_EAP.png, log, Non_reproducible_error.png, RH_Dev_Toolset.png, Welcome.png > > > As a RHEL Desktop user and application developer, I wish to install the JBDS/JBoss Tools features/plug-ins into my previously installed version of DTS - Developer Toolset > https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/ > Help - Install New Software -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19056: ---------------------------------------- Single current rule is: If baseline contains an artifact with same id but higher version, or with same major.minor.micro, then fail. Another rule I'd like to implement before using it in "production" would be that if x.y.z.qualifier are equals, then artifact must be identical (or it would fail). > A Mojo to validate a version (compared to baseline) > --------------------------------------------------- > > Key: JBIDE-19056 > URL: https://issues.jboss.org/browse/JBIDE-19056 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > > We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released. > Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19056: ---------------------------------- Assignee: Mickael Istria > A Mojo to validate a version (compared to baseline) > --------------------------------------------------- > > Key: JBIDE-19056 > URL: https://issues.jboss.org/browse/JBIDE-19056 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > > We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released. > Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19056: ------------------------------- Affects Version/s: 4.2.2.Final > A Mojo to validate a version (compared to baseline) > --------------------------------------------------- > > Key: JBIDE-19056 > URL: https://issues.jboss.org/browse/JBIDE-19056 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > > We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released. > Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...) -- 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