September 2015 - 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] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.... ] Paul Leacu edited comment on JBTIS-508 at 9/30/15 4:17 PM: ----------------------------------------------------------- Okay - [~nickboldt] - if you have a chance - please review this PR (Max too if you'd like): https://github.com/jbosstools/jbosstools-integration-stack/pull/438 I've updated the jbosstools and devstudio discovery site generation to create separate released and earlyaccess JBoss Central discovery sites (no mixing of the streams). For example - building like this: {code} mvn -B -U \ -DCOMPOSITE_URLS=http://download.jboss.org/jbosstools/mars/development/updates/core/,http://download.jboss.org/jbosstools/mars/integration/updates/integration-stack/4.3.0.Alpha2,http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbtis/REPO \ -DCOMPOSITE_EA_URLS=http://download.jboss.org/jbosstools/mars/development/updates/core/,http://download.jboss.org/jbosstools/mars/integration/updates/integration-stack/4.3.0.Alpha2/earlyaccess,http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbtis/earlyaccess/REPO clean install {code} produces composites like this for released: {code} <?xml version='1.0' encoding='UTF-8'?> <?compositeArtifactRepository version='1.0.0'?> <repository name='JBoss Tools Integration Stack Central - composite staging site' type='org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository' version='1.0.0'> <properties size='2'> <property name='p2.timestamp' value='1443643601057'/> <property name='p2.compressed' value='true'/> </properties> <children size='3'> <child location='http://download.jboss.org/jbosstools/mars/development/updates/core/'/> <child location='http://download.jboss.org/jbosstools/mars/integration/updates/integration...'/> <child location='http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Be...'/> </children> </repository> {code} and this for early access: {code} <?xml version='1.0' encoding='UTF-8'?> <?compositeArtifactRepository version='1.0.0'?> <repository name='JBoss Tools Integration Stack Central - composite staging site' type='org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository' version='1.0.0'> <properties size='2'> <property name='p2.timestamp' value='1443643601510'/> <property name='p2.compressed' value='true'/> </properties> <children size='3'> <child location='http://download.jboss.org/jbosstools/mars/development/updates/core/'/> <child location='http://download.jboss.org/jbosstools/mars/integration/updates/integration...'/> <child location='http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Be...'/> </children> </repository> {code} The generated jbosstools-integration-stack-directory.xml for released: {code} <?xml version='1.0' encoding='UTF-8'?> <directory xmlns="http://www.eclipse.org/mylyn/discovery/directory/"> <entry url="http://download.jboss.org/jbosstools/mars/development/updates/discovery.c..." permitCategories="true"/> <entry url="http://download.jboss.org/jbosstools/mars/development/updates/discovery.c..." permitCategories="true"/> <entry url="plugins/org.jboss.tools.central.discovery.integration-stack_4.3.0.Alpha2-v20130101-0001-B1.jar" permitCategories="true"/> </directory> {code} and the generated jbosstools-integration-stack-directory.xml for early access: {code} <?xml version='1.0' encoding='UTF-8'?> <directory xmlns="http://www.eclipse.org/mylyn/discovery/directory/"> <entry url="http://download.jboss.org/jbosstools/mars/development/updates/discovery.c..." permitCategories="true"/> <entry url="http://download.jboss.org/jbosstools/mars/development/updates/discovery.c..." permitCategories="true"/> <entry url="plugins/org.jboss.tools.central.discovery.integration-stack.earlyaccess_4.3.0.Alpha2-v20130101-0001-B1.jar" permitCategories="true"/> </directory> {code} Similar results for devstudio. How these sites are merged with the parent JBT/JBDS discovery sites is next - but they need to be generated which is this PR. WDYT? was (Author: pleacu): Okay - [~nickboldt] - if you have a chance - please review this PR (Max too if you'd like): https://github.com/jbosstools/jbosstools-integration-stack/pull/438 I've update the jbosstools and devstudio discovery site generation to create separate released and earlyaccess JBoss Central discovery sites (no mixing of the streams). For example - building like this: {code} mvn -B -U \ -DCOMPOSITE_URLS=http://download.jboss.org/jbosstools/mars/development/updates/core/,http://download.jboss.org/jbosstools/mars/integration/updates/integration-stack/4.3.0.Alpha2,http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbtis/REPO \ -DCOMPOSITE_EA_URLS=http://download.jboss.org/jbosstools/mars/development/updates/core/,http://download.jboss.org/jbosstools/mars/integration/updates/integration-stack/4.3.0.Alpha2/earlyaccess,http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbtis/earlyaccess/REPO clean install {code} produces composites like this for released: {code} <?xml version='1.0' encoding='UTF-8'?> <?compositeArtifactRepository version='1.0.0'?> <repository name='JBoss Tools Integration Stack Central - composite staging site' type='org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository' version='1.0.0'> <properties size='2'> <property name='p2.timestamp' value='1443643601057'/> <property name='p2.compressed' value='true'/> </properties> <children size='3'> <child location='http://download.jboss.org/jbosstools/mars/development/updates/core/'/> <child location='http://download.jboss.org/jbosstools/mars/integration/updates/integration...'/> <child location='http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Be...'/> </children> </repository> {code} and this for early access: {code} <?xml version='1.0' encoding='UTF-8'?> <?compositeArtifactRepository version='1.0.0'?> <repository name='JBoss Tools Integration Stack Central - composite staging site' type='org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository' version='1.0.0'> <properties size='2'> <property name='p2.timestamp' value='1443643601510'/> <property name='p2.compressed' value='true'/> </properties> <children size='3'> <child location='http://download.jboss.org/jbosstools/mars/development/updates/core/'/> <child location='http://download.jboss.org/jbosstools/mars/integration/updates/integration...'/> <child location='http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Be...'/> </children> </repository> {code} The generated jbosstools-integration-stack-directory.xml for released: {code} <?xml version='1.0' encoding='UTF-8'?> <directory xmlns="http://www.eclipse.org/mylyn/discovery/directory/"> <entry url="http://download.jboss.org/jbosstools/mars/development/updates/discovery.c..." permitCategories="true"/> <entry url="http://download.jboss.org/jbosstools/mars/development/updates/discovery.c..." permitCategories="true"/> <entry url="plugins/org.jboss.tools.central.discovery.integration-stack_4.3.0.Alpha2-v20130101-0001-B1.jar" permitCategories="true"/> </directory> {code} and the generated jbosstools-integration-stack-directory.xml for early access: {code} <?xml version='1.0' encoding='UTF-8'?> <directory xmlns="http://www.eclipse.org/mylyn/discovery/directory/"> <entry url="http://download.jboss.org/jbosstools/mars/development/updates/discovery.c..." permitCategories="true"/> <entry url="http://download.jboss.org/jbosstools/mars/development/updates/discovery.c..." permitCategories="true"/> <entry url="plugins/org.jboss.tools.central.discovery.integration-stack.earlyaccess_4.3.0.Alpha2-v20130101-0001-B1.jar" permitCategories="true"/> </directory> {code} Similar results for devstudio. How these sites are merged with the parent JBT/JBDS discovery sites is next - but they need to be generated which is this PR. WDYT? > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-508: ---------------------------------- Okay - [~nickboldt] - if you have a chance - please review this PR (Max too if you'd like): https://github.com/jbosstools/jbosstools-integration-stack/pull/438 I've update the jbosstools and devstudio discovery site generation to create separate released and earlyaccess JBoss Central discovery sites (no mixing of the streams). For example - building like this: {code} mvn -B -U \ -DCOMPOSITE_URLS=http://download.jboss.org/jbosstools/mars/development/updates/core/,http://download.jboss.org/jbosstools/mars/integration/updates/integration-stack/4.3.0.Alpha2,http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbtis/REPO \ -DCOMPOSITE_EA_URLS=http://download.jboss.org/jbosstools/mars/development/updates/core/,http://download.jboss.org/jbosstools/mars/integration/updates/integration-stack/4.3.0.Alpha2/earlyaccess,http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbtis/earlyaccess/REPO clean install {code} produces composites like this for released: {code} <?xml version='1.0' encoding='UTF-8'?> <?compositeArtifactRepository version='1.0.0'?> <repository name='JBoss Tools Integration Stack Central - composite staging site' type='org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository' version='1.0.0'> <properties size='2'> <property name='p2.timestamp' value='1443643601057'/> <property name='p2.compressed' value='true'/> </properties> <children size='3'> <child location='http://download.jboss.org/jbosstools/mars/development/updates/core/'/> <child location='http://download.jboss.org/jbosstools/mars/integration/updates/integration...'/> <child location='http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Be...'/> </children> </repository> {code} and this for early access: {code} <?xml version='1.0' encoding='UTF-8'?> <?compositeArtifactRepository version='1.0.0'?> <repository name='JBoss Tools Integration Stack Central - composite staging site' type='org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository' version='1.0.0'> <properties size='2'> <property name='p2.timestamp' value='1443643601510'/> <property name='p2.compressed' value='true'/> </properties> <children size='3'> <child location='http://download.jboss.org/jbosstools/mars/development/updates/core/'/> <child location='http://download.jboss.org/jbosstools/mars/integration/updates/integration...'/> <child location='http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Be...'/> </children> </repository> {code} The generated jbosstools-integration-stack-directory.xml for released: {code} <?xml version='1.0' encoding='UTF-8'?> <directory xmlns="http://www.eclipse.org/mylyn/discovery/directory/"> <entry url="http://download.jboss.org/jbosstools/mars/development/updates/discovery.c..." permitCategories="true"/> <entry url="http://download.jboss.org/jbosstools/mars/development/updates/discovery.c..." permitCategories="true"/> <entry url="plugins/org.jboss.tools.central.discovery.integration-stack_4.3.0.Alpha2-v20130101-0001-B1.jar" permitCategories="true"/> </directory> {code} and the generated jbosstools-integration-stack-directory.xml for early access: {code} <?xml version='1.0' encoding='UTF-8'?> <directory xmlns="http://www.eclipse.org/mylyn/discovery/directory/"> <entry url="http://download.jboss.org/jbosstools/mars/development/updates/discovery.c..." permitCategories="true"/> <entry url="http://download.jboss.org/jbosstools/mars/development/updates/discovery.c..." permitCategories="true"/> <entry url="plugins/org.jboss.tools.central.discovery.integration-stack.earlyaccess_4.3.0.Alpha2-v20130101-0001-B1.jar" permitCategories="true"/> </directory> {code} Similar results for devstudio. How these sites are merged with the parent JBT/JBDS discovery sites is next - but they need to be generated which is this PR. WDYT? > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20836) Xcodebuild is failing with cordova-ios >= 3.9.0

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20836?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20836: ------------------------------------ Built: http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... >=42 Building: http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... >=122 http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... >=119 > Xcodebuild is failing with cordova-ios >= 3.9.0 > ----------------------------------------------- > > Key: JBIDE-20836 > URL: https://issues.jboss.org/browse/JBIDE-20836 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Priority: Critical > Labels: respin-a > Fix For: 4.3.0.Final > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=478645 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20843) enable automated cleanup for versionwatch reports

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20843?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20843. ------------------------------ Resolution: Done Additional fixes were needed: https://github.com/jbosstools/jbosstools-versionwatch/commit/c82d4ac1ba0c... > enable automated cleanup for versionwatch reports > ------------------------------------------------- > > Key: JBIDE-20843 > URL: https://issues.jboss.org/browse/JBIDE-20843 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.CR1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.CR2, 4.4.0.Alpha1 > > > Currently, versionwatch dumps 4 log files into a folder; 1000s of builds later, the folder is unmanageable. > So, migrate to use rsync.sh instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3533) Unable to update/install the plug-ins

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3533?page=com.atlassian.jira.plugin.... ] Alexey Kazakov edited comment on JBDS-3533 at 9/30/15 3:11 PM: --------------------------------------------------------------- [~vikramjammula] I'm going to close this issue as a duplicate. Please install JBDS 8.1.0.GA or JBDS 9.0.0.CR1 where this issue with failing update is fixed. If you can install a newer version or prefer to stay with 8.0 for whatever reason then try a workaround described in JBDS-3295. It should help. Please let us know if you still can reproduce it on JBDS 8.1/9.0. was (Author: akazakov): [~vikramjammula] I'm closing this issue as a duplicate. Please install JBDS 8.1.0.GA or JBDS 9.0.0.CR1 where this issue with failing update is fixed. If you can install a newer version or prefer to stay with 8.0 for whatever reason then try a workaround described in JBDS-3295. It should help. Please re-open the issue if you still can reproduce it on JBDS 8.1/9.0. > Unable to update/install the plug-ins > ------------------------------------- > > Key: JBDS-3533 > URL: https://issues.jboss.org/browse/JBDS-3533 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.0.0.GA > Environment: Development > Reporter: Vikram Jammula > Assignee: Denis Golovin > Priority: Minor > Fix For: 9.x > > Attachments: check Updates.png, security.jpg > > > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3533) Unable to update/install the plug-ins

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3533?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3533: --------------------------------- Fix Version/s: 9.x > Unable to update/install the plug-ins > ------------------------------------- > > Key: JBDS-3533 > URL: https://issues.jboss.org/browse/JBDS-3533 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.0.0.GA > Environment: Development > Reporter: Vikram Jammula > Assignee: Denis Golovin > Priority: Minor > Fix For: 9.x > > Attachments: check Updates.png, security.jpg > > > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3533) Unable to update/install the plug-ins

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3533?page=com.atlassian.jira.plugin.... ] Alexey Kazakov closed JBDS-3533. -------------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.x) Resolution: Duplicate Issue [~vikramjammula] I'm closing this issue as a duplicate. Please install JBDS 8.1.0.GA or JBDS 9.0.0.CR1 where this issue with failing update is fixed. If you can install a newer version or prefer to stay with 8.0 for whatever reason then try a workaround described in JBDS-3295. It should help. Please re-open the issue if you still can reproduce it on JBDS 8.1/9.0. > Unable to update/install the plug-ins > ------------------------------------- > > Key: JBDS-3533 > URL: https://issues.jboss.org/browse/JBDS-3533 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.0.0.GA > Environment: Development > Reporter: Vikram Jammula > Assignee: Denis Golovin > Priority: Minor > Fix For: 9.0.0.Beta2 > > Attachments: check Updates.png, security.jpg > > > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 2015