September 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4054) publish rpms + metadata to /latest/ locations so they can be easily installed by QE

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4054?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4054: ---------------------------------- Resolving this issue and opening TOOLSDOC-752 to track the doc issue. > publish rpms + metadata to /latest/ locations so they can be easily installed by QE > ----------------------------------------------------------------------------------- > > Key: JBDS-4054 > URL: https://issues.jboss.org/browse/JBDS-4054 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, rpm > Affects Versions: 10.1.0.GA, 10.2.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: doc_writer_needed, docs_installation_guide, new_and_noteworthy > Fix For: 10.2.0.AM2 > > Attachments: rh-eclipse46-devstudio.repo > > > Next step is publishing these yum repos (metadata + rpms) to a location that can be made easily available to RHEL users, eg., > * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_master/l... > * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_10.0.neo... > * https://devstudio.redhat.com/10.0/staging/builds/devstudio-10.1.0.GA-buil... > * https://devstudio.redhat.com/static/10.0/stable/builds/devstudio-10.1.0.G... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-752) Document installation path for devstudio rpm

by Nick Boldt (JIRA)

Nick Boldt created TOOLSDOC-752: ----------------------------------- Summary: Document installation path for devstudio rpm Key: TOOLSDOC-752 URL: https://issues.jboss.org/browse/TOOLSDOC-752 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Feature Request Components: Installation Guide Affects Versions: 10.x Reporter: Nick Boldt Assignee: Misha Ali We need to document how to install devstudio rpm on RHEL 7. Could also add info for how to install on Fedora 24/25 (requires additional repo(s) to resolve required rh-eclipse* packages needed by rh-eclipse46-devstudio) Could additionaly document how to use alien to convert the .rpm to a .deb using alien (for installation on ubuntu). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4054) publish rpms + metadata to /latest/ locations so they can be easily installed by QE

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4054?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4054: ----------------------------- Labels: doc_writer_needed docs_installation_guide new_and_noteworthy (was: ) > publish rpms + metadata to /latest/ locations so they can be easily installed by QE > ----------------------------------------------------------------------------------- > > Key: JBDS-4054 > URL: https://issues.jboss.org/browse/JBDS-4054 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, rpm > Affects Versions: 10.1.0.GA, 10.2.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: doc_writer_needed, docs_installation_guide, new_and_noteworthy > Fix For: 10.2.0.AM2 > > Attachments: rh-eclipse46-devstudio.repo > > > Next step is publishing these yum repos (metadata + rpms) to a location that can be made easily available to RHEL users, eg., > * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_master/l... > * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_10.0.neo... > * https://devstudio.redhat.com/10.0/staging/builds/devstudio-10.1.0.GA-buil... > * https://devstudio.redhat.com/static/10.0/stable/builds/devstudio-10.1.0.G... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4054) publish rpms + metadata to /latest/ locations so they can be easily installed by QE

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4054?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4054: ---------------------------------- s/devstudio.jboss.com/devstudio.redhat.com/g and add URL tracker > publish rpms + metadata to /latest/ locations so they can be easily installed by QE > ----------------------------------------------------------------------------------- > > Key: JBDS-4054 > URL: https://issues.jboss.org/browse/JBDS-4054 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, rpm > Affects Versions: 10.1.0.GA, 10.2.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM2 > > Attachments: rh-eclipse46-devstudio.repo > > > Next step is publishing these yum repos (metadata + rpms) to a location that can be made easily available to RHEL users, eg., > * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_master/l... > * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_10.0.neo... > * https://devstudio.redhat.com/10.0/staging/builds/devstudio-10.1.0.GA-buil... > * https://devstudio.redhat.com/static/10.0/stable/builds/devstudio-10.1.0.G... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4054) publish rpms + metadata to /latest/ locations so they can be easily installed by QE

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4054?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-4054. ------------------------------ Resolution: Done > publish rpms + metadata to /latest/ locations so they can be easily installed by QE > ----------------------------------------------------------------------------------- > > Key: JBDS-4054 > URL: https://issues.jboss.org/browse/JBDS-4054 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, rpm > Affects Versions: 10.1.0.GA, 10.2.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM2 > > Attachments: rh-eclipse46-devstudio.repo > > > Next step is publishing these yum repos (metadata + rpms) to a location that can be made easily available to RHEL users, eg., > * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_master/l... > * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_10.0.neo... > * https://devstudio.redhat.com/10.0/staging/builds/devstudio-10.1.0.GA-buil... > * https://devstudio.redhat.com/static/10.0/stable/builds/devstudio-10.1.0.G... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4054) publish rpms + metadata to /latest/ locations so they can be easily installed by QE

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4054?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4054 at 9/30/16 4:29 PM: ----------------------------------------------------------- Currently we have two snapshot URLs people can use: https://devstudio.redhat.com/10.0/snapshots/rpms/10.1.0/x86_64/ (from 4.4.1.x branch) https://devstudio.redhat.com/10.0/snapshots/rpms/10.2.0/x86_64/ (from master branch) These will always point to the latest builds, and can be used in yum.repos.d/*.repo files. I've also got *build* folders - here we keep a series of builds including their build logs, which will persist until they're old enough to be auto-garbage-collected: https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_10.0.neon/ https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_master/ I can set up a dummy URL (empty yum repo) for what we might want to embed OOTB when installing rh-eclipse46-base, so that devstudio can be discovered via yum. For that we just need agreement on what URLs to use. How does this sound? (Note: /static/ is used to enable Akamai mirroring for better download performance.) https://devstudio.redhat.com/static/10.0/stable/rpms/x86_64 (points at latest 10.x release) was (Author: nickboldt): Currently we have two snapshot URLs people can use: https://devstudio.jboss.com/10.0/snapshots/rpms/10.1.0/x86_64/ (from 4.4.1.x branch) https://devstudio.jboss.com/10.0/snapshots/rpms/10.2.0/x86_64/ (from master branch) These will always point to the latest builds, and can be used in yum.repos.d/*.repo files. I've also got *build* folders - here we keep a series of builds including their build logs, which will persist until they're old enough to be auto-garbage-collected: https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_10.0.neon/ https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_master/ I can set up a dummy URL (empty yum repo) for what we might want to embed OOTB when installing rh-eclipse46-base, so that devstudio can be discovered via yum. For that we just need agreement on what URLs to use. How does this sound? (Note: /static/ is used to enable Akamai mirroring for better download performance.) https://devstudio.jboss.com/static/10.0/stable/rpms/x86_64 (points at latest 10.x release) > publish rpms + metadata to /latest/ locations so they can be easily installed by QE > ----------------------------------------------------------------------------------- > > Key: JBDS-4054 > URL: https://issues.jboss.org/browse/JBDS-4054 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, rpm > Affects Versions: 10.1.0.GA, 10.2.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM2 > > Attachments: rh-eclipse46-devstudio.repo > > > Next step is publishing these yum repos (metadata + rpms) to a location that can be made easily available to RHEL users, eg., > * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_master/l... > * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_10.0.neo... > * https://devstudio.redhat.com/10.0/staging/builds/devstudio-10.1.0.GA-buil... > * https://devstudio.redhat.com/static/10.0/stable/builds/devstudio-10.1.0.G... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4054) publish rpms + metadata to /latest/ locations so they can be easily installed by QE

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4054?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4054 at 9/30/16 4:28 PM: ----------------------------------------------------------- I've added a README.html to the yum_repo folder. https://github.com/jbdevstudio/jbdevstudio-product/commit/36b51c99b4d6557... Should be available in about 20 mins when the next master build is done: http://wonka.mw.lab.eng.bos.redhat.com/jenkins/job/devstudio.rpm_master/1... https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_master/l... https://devstudio.redhat.com/10.0/snapshots/rpms/10.2.0/x86_64/ was (Author: nickboldt): I've added a README.html to the yum_repo folder. https://github.com/jbdevstudio/jbdevstudio-product/commit/36b51c99b4d6557... Should be available in about 20 mins when the next master build is done: http://wonka.mw.lab.eng.bos.redhat.com/jenkins/job/devstudio.rpm_master/1... https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_master/la... https://devstudio.jboss.com/10.0/snapshots/rpms/10.2.0/x86_64/ > publish rpms + metadata to /latest/ locations so they can be easily installed by QE > ----------------------------------------------------------------------------------- > > Key: JBDS-4054 > URL: https://issues.jboss.org/browse/JBDS-4054 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, rpm > Affects Versions: 10.1.0.GA, 10.2.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM2 > > Attachments: rh-eclipse46-devstudio.repo > > > Next step is publishing these yum repos (metadata + rpms) to a location that can be made easily available to RHEL users, eg., > * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_master/l... > * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_10.0.neo... > * https://devstudio.redhat.com/10.0/staging/builds/devstudio-10.1.0.GA-buil... > * https://devstudio.redhat.com/static/10.0/stable/builds/devstudio-10.1.0.G... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23278) Validation of class reference in job.xml produces false-positive warning

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23278?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23278: ----------------------------------- Fix Version/s: 4.5.x > Validation of class reference in job.xml produces false-positive warning > ------------------------------------------------------------------------ > > Key: JBIDE-23278 > URL: https://issues.jboss.org/browse/JBIDE-23278 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.4.2.AM1 > Environment: Fedora 24 > Reporter: Lukáš Valach > Fix For: 4.5.x > > Attachments: BatchRenameManualTest.zip, Rename-Warning.png > > > When I refer to some class using fully qualified name and that class is annotated by @Named or is mentioned in bean.xml, then the eclipse shows warning "Item ... not found." although class exists and code is valid (test passes). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23278) Validation of class reference in job.xml produces false-positive warning

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23278?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-23278: -------------------------------------- Assignee: Alexey Kazakov > Validation of class reference in job.xml produces false-positive warning > ------------------------------------------------------------------------ > > Key: JBIDE-23278 > URL: https://issues.jboss.org/browse/JBIDE-23278 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.4.2.AM1 > Environment: Fedora 24 > Reporter: Lukáš Valach > Assignee: Alexey Kazakov > Fix For: 4.5.x > > Attachments: BatchRenameManualTest.zip, Rename-Warning.png > > > When I refer to some class using fully qualified name and that class is annotated by @Named or is mentioned in bean.xml, then the eclipse shows warning "Item ... not found." although class exists and code is valid (test passes). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-912) Some BPMN2 bundles have incorrect versions

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-912?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-912: ---------------------------------- Mirrored and push to the IS: https://issues.jboss.org/browse/JBTIS-919 http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/1... > Some BPMN2 bundles have incorrect versions > ------------------------------------------ > > Key: JBTIS-912 > URL: https://issues.jboss.org/browse/JBTIS-912 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2 > Affects Versions: 10.0.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > > Some BPMN2 bundles have incorrect versions (missing build number) > {code} > org.eclipse.bpmn2_1.3.0.Final-v20160119-1832 > org.eclipse.bpmn2.edit_1.3.0.Final-v20160119-1832 > org.eclipse.bpmn2.editor_1.3.0.Final-v20160119-1832 > org.eclipse.bpmn2.modeler.core_1.3.1.Final-v20160831-1132-B55 > org.eclipse.bpmn2.modeler.help_1.3.1.Final-v20160831-1132-B55 > org.eclipse.bpmn2.modeler.runtime.jboss.jbpm_1.3.1.Final-v20160831-1132-B55 > org.eclipse.bpmn2.modeler.ui_1.3.1.Final-v20160831-1132-B55 > {code} > Notice that the last 4 bundles have correct version with a build number. But the first 3 of them are missing the build number. > EDIT: Note that all BPMN2 bundles in JBDS-IS 9.0.2.CR1 have correct versions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

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 September 2016