September 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-3044) Align installation default path with installer filename

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3044?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3044 at 5/28/14 10:36 AM: ------------------------------------------------------------ Martin did a quick test on OSX to see what the longest file paths are inside JBDS 8 Beta2: {quote} {code} find jbdevstudio-* |awk '{ print length($0) ; }'|sort|uniq|egrep "2.+" {code} shows 251 as the longest path on Mac so not really safe longest is ./studio/configuration/org.eclipse.osgi/949/data/c7ff8a0a591e0e90fe36069138e75f68/1012-1401176993555/org.springframework.ide.eclipse.core.java.ProjectClassLoaderCache$SourceAndOutputLocationResourceChangeListener$SourceAndOutputLocationResourceVisitor but that is spring and it's data {quote} So we're already pushing the limit here for long paths on Windows / NTFS... Related (with some LOLs): http://blog.codinghorror.com/filesystem-paths-how-long-is-too-long/ There are ways to achieve more-than-260-char paths, but do we want to? was (Author: nickboldt): Martin did a quick test on OSX to see what the longest file paths are inside JBDS 8 Beta2: {quote} {code} find jbdevstudio-* |awk '{ print length($0) ; }'|sort|uniq|egrep "2.+" {code} shows 251 as the longest path on Mac so not really safe longest is ./studio/configuration/org.eclipse.osgi/949/data/c7ff8a0a591e0e90fe36069138e75f68/1012-1401176993555/org.springframework.ide.eclipse.core.java.ProjectClassLoaderCache$SourceAndOutputLocationResourceChangeListener$SourceAndOutputLocationResourceVisitor but that is spring and it's data {quote} So we're already pushing the limit here for long paths on Windows / NTFS... > Align installation default path with installer filename > ------------------------------------------------------- > > Key: JBDS-3044 > URL: https://issues.jboss.org/browse/JBDS-3044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta2 > Reporter: Martin Malina > Assignee: Denis Golovin > Priority: Blocker > Labels: discuss > Fix For: 8.0.0.Beta3 > > > Now that Nick changed the installer filenames to jboss-devstudio in JBIDE-16871 (was jbdevstudio), shouldn't the default install path be changed similarly? Because it just went out of sync. > This question is open for discussion. Nick pointed out some reasons against this suggestion: > {quote} > Martin Malina Re: changing the installation folder, I'll hold off on that change for the moment for a few reasons: > a) Max is AFK, and will want to vet/veto this idea > b) long paths for Windows users (80% of our user base) = bad news, especially considering how long some file paths can get already within Eclipse workspaces > c) short paths for Windows (c:\jbdevstudio) & long paths for everyone else ~/jboss-devstudio) would be ill-advised from a documentation and cross-platform user experience > So, either we stick w/ jbdevstudio, or we shorten to devstudio (losing the "jb" branding fragment). If we move to "jboss-devstudio" we increase the path by only 4 characters. > Max Rydahl Andersen WDYT? > {quote} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

1 week, 5 days

2
2
0 / 0

[JBoss JIRA] (JBDS-2719) Multiple Spring AOP problems when travel example is imported

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/JBDS-2719?page=com.atlassian.jira.plugin.... ] Joshua Wilson commented on JBDS-2719: ------------------------------------- [~nickboldt] I will need to test several different configurations to confirm my earlier guess. This is what I know so far. First I would ask that you test with the [Kitchensink-Spring Quickstarts|https://github.com/jboss-developer/jboss-wfk-quickstarts] as I am working to keep them up to date and error free as much as possible. This specific error can be seen in the [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] quickstart. The Travel and PetClinic will be kept as close to the original as possible (and I haven't had a chance to update them yet). With that in mind if I Build (with Eclipse/JBDS) [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] in JBDS 7.0.1 with Spring IDE 3.3 installed from JBoss Central, I get the aspectj error. However if I Build while in a standard Eclipse JEE install with JBDS and the stock Spring IDE/STS 3.4 installed, I do NOT get the aspectj error. In order to truly confirm that adding both "AspectJ Compiler" and "AspectJ Development Tools" will fix the error, I would need to test that on my JBDS 7.0.1/SpringIDE 3.3 set up. > Multiple Spring AOP problems when travel example is imported > ------------------------------------------------------------ > > Key: JBDS-2719 > URL: https://issues.jboss.org/browse/JBDS-2719 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, upstream > Affects Versions: 7.0.0.GA > Environment: JBDS 7.0.0.GA, L64, Spring IDE 3.3 installed from JBoss Central > Reporter: Jiri Peterka > Assignee: Nick Boldt > Fix For: 7.1.0.Beta1 > > > There are Multiple Spring AOP Errors after travel example is imported: > {code} > Build path is incomplete. Cannot find class file for org/aspectj/weaver/reflect/ReflectionWorld$ReflectionWorldException > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5287) Block comment doesn't remove if code selected by 'Ctrl+A' for xhtml file.

by Svetlana Yasenovich (JIRA)

Block comment doesn't remove if code selected by 'Ctrl+A' for xhtml file. ------------------------------------------------------------------------- Key: JBIDE-5287 URL: https://jira.jboss.org/jira/browse/JBIDE-5287 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Environment: JBoss Developer Studio Version: 3.0.0.M4 Build id: v200911180352M Reporter: Svetlana Yasenovich Priority: Minor 1. Open .xhtml file. 2. click 'Ctrl+A' -> all code selected 3. click 'Ctrl+Shift+/' (Source->Add Block Comment) ->all code commented 4. click 'Ctrl+A' 5. click 'Ctrl+Shift+\' (Source->Remove Block Comment) -> nothing happened Expected Result : Remove Block Comment for all code -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

5 months

3
7
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: ---------------------------------- 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)

8 years, 12 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)

8 years, 12 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)

8 years, 12 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)

8 years, 12 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)

8 years, 12 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)

8 years, 12 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)

8 years, 12 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2016