October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21012: ------------------------------------ One will discard the other. 20 mins ago, I saw "Latest Build: 1.5.100-SNAPSHOT (Alpha1-v20151026-1942-B311)" in https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr... and https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... contains that same content: "Latest Build: 1.5.100-SNAPSHOT (Alpha1-v20151026-1942-B311)" Then I rebuilt with BUILD_ALIAS=Alpha0 to test this theory: http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-freemarker... (Alpha0) http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-freemarker... {code} 11:47:35 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (2944 KB at 2914.6 KB/sec) {code} Now, this URL is 404'd: https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr... and instead we have these: https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr... (no longer Alpha1; instead Alpha0) https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr... (not sure why this has appeared -- wasn't there when I did an Alpha1 build) > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-488) JBTIS/JBDSIS target platform contains old version of org.jboss.tools.foundation.security.linux.feature; needs update to latest

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-488?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-488: ---------------------------------- Rechecked this - this issue has nothing to do with the IS TP - the issue is that the IS is pulling in the Luna version of Teiid Designer which contains the 1.1.2.Final foundation feature. http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac... > JBTIS/JBDSIS target platform contains old version of org.jboss.tools.foundation.security.linux.feature; needs update to latest > ------------------------------------------------------------------------------------------------------------------------------ > > Key: JBTIS-488 > URL: https://issues.jboss.org/browse/JBTIS-488 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > > Update site at > http://www.qa.jboss.com/binaries/RHDS/mars/development/updates/integratio... > contains > org.jboss.tools.foundation.security.linux_1.1.2.Final-v20150325-0456-B99 > but JBDS 9 contains org.jboss.tools.foundation.security.linux_1.2.0.Beta2-v20150724-1456-B25. So, if we try to install all features (uncheck 'Group items by category'), we will get an error > Cannot complete the request. See the error log for details. > "JBoss Tools Foundation Security for Linux" will be ignored because a newer version is already installed. > This feature is required by Teiid Designer and it was included in JBTIS-112 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21027) Central offers to install Early Access content when importing project examples (EA disabled)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21027?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21027: ---------------------------------------- Assigning to [~mickael_istria] because it should be aligned with JBIDE-20609 > Central offers to install Early Access content when importing project examples (EA disabled) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-21027 > URL: https://issues.jboss.org/browse/JBIDE-21027 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.3.0.Final > Reporter: Alexey Kazakov > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: angular.png > > > 1. Open Central with EA disabled > 2. Try to import kitchensink-angularjs project example > 3. AngularJS (EA version) is offered to install: > !angular.png! > 4. Press "Download & Install". > 5. AngularJS is installed without any warning that it's an EA content. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21027) Central offers to install Early Access content when importing project examples (EA disabled)

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-21027: -------------------------------------- Summary: Central offers to install Early Access content when importing project examples (EA disabled) Key: JBIDE-21027 URL: https://issues.jboss.org/browse/JBIDE-21027 Project: Tools (JBoss Tools) Issue Type: Bug Components: central, project-examples Affects Versions: 4.3.0.Final Reporter: Alexey Kazakov Assignee: Mickael Istria Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 Attachments: angular.png 1. Open Central with EA disabled 2. Try to import kitchensink-angularjs project example 3. AngularJS (EA version) is offered to install: !angular.png! 4. Press "Download & Install". 5. AngularJS is installed without any warning that it's an EA content. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20801) New hibernate configuration wizard controls invisible in Unix

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20801?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-20801. ------------------------------- Resolution: Done > New hibernate configuration wizard controls invisible in Unix > ------------------------------------------------------------- > > Key: JBIDE-20801 > URL: https://issues.jboss.org/browse/JBIDE-20801 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.0.CR1 > Reporter: Dmitry Bocharov > Assignee: Koen Aers > Priority: Minor > Fix For: 4.4.0.Alpha1 > > Attachments: Fedora22.png, Windows7.png > > > Screenshots from Fefora22 and Windows7 are attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21026) New hibernate configuration wizard controls invisible in Unix

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21026?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-21026: ------------------------------ Fix Version/s: 4.3.1.Beta1 (was: 4.4.0.Alpha1) > New hibernate configuration wizard controls invisible in Unix > ------------------------------------------------------------- > > Key: JBIDE-21026 > URL: https://issues.jboss.org/browse/JBIDE-21026 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.0.CR1 > Reporter: Dmitry Bocharov > Assignee: Koen Aers > Priority: Minor > Fix For: 4.3.1.Beta1 > > Attachments: Fedora22.png, Windows7.png > > > Screenshots from Fefora22 and Windows7 are attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21026) New hibernate configuration wizard controls invisible in Unix

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21026?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-21026. ------------------------------- Resolution: Done > New hibernate configuration wizard controls invisible in Unix > ------------------------------------------------------------- > > Key: JBIDE-21026 > URL: https://issues.jboss.org/browse/JBIDE-21026 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.0.CR1 > Reporter: Dmitry Bocharov > Assignee: Koen Aers > Priority: Minor > Fix For: 4.3.1.Beta1 > > Attachments: Fedora22.png, Windows7.png > > > Screenshots from Fefora22 and Windows7 are attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21026) New hibernate configuration wizard controls invisible in Unix

by Koen Aers (JIRA)

Koen Aers created JBIDE-21026: --------------------------------- Summary: New hibernate configuration wizard controls invisible in Unix Key: JBIDE-21026 URL: https://issues.jboss.org/browse/JBIDE-21026 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 4.3.0.CR1 Reporter: Dmitry Bocharov Assignee: Koen Aers Priority: Minor Fix For: 4.4.0.Alpha1 Screenshots from Fefora22 and Windows7 are attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20801) New hibernate configuration wizard controls invisible in Unix

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20801?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-20801: ------------------------------ Fix Version/s: 4.4.0.Alpha1 > New hibernate configuration wizard controls invisible in Unix > ------------------------------------------------------------- > > Key: JBIDE-20801 > URL: https://issues.jboss.org/browse/JBIDE-20801 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.0.CR1 > Reporter: Dmitry Bocharov > Assignee: Koen Aers > Priority: Minor > Fix For: 4.4.0.Alpha1 > > Attachments: Fedora22.png, Windows7.png > > > Screenshots from Fefora22 and Windows7 are attached. -- 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-508: ---------------------------------- Since this is ALSO the latest content for the JBT & JBDS development sites (the latest stable milestone = 9.0.0.GA / 4.3.0.Final = latest release too) should you not also update these four /development/ URLs too? [1] https://devstudio.redhat.com/9.0/development/updates/ composite*.xml [2] https://devstudio.redhat.com/9.0/development/updates/earlyaccess/ composite*.xml [3] http://download.jboss.org/jbosstools/mars/development/updates/ composite*.xml [4] http://download.jboss.org/jbosstools/mars/development/updates/earlyaccess/ composite*.xml Are all these manual changes reflected in your updated release guide, so that you'll update BOTH stable and development as appropriate when you release your next Alpha or Beta bits? Can you link to that document here? > 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2015