March 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25585) release webtools site for Eclipse 4.8 Photon to so WTP 3.10 discovery upstream can find it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25585?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25585: ------------------------------- Sprint: devex #145 February 2018, devex #147 April 2018 (was: devex #145 February 2018) > release webtools site for Eclipse 4.8 Photon to so WTP 3.10 discovery upstream can find it > ------------------------------------------------------------------------------------------ > > Key: JBIDE-25585 > URL: https://issues.jboss.org/browse/JBIDE-25585 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, updatesite, upstream > Affects Versions: 4.6.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.6.0.AM1, 4.6.0.Final > > > Need a semi-working placeholder (even if it's a CI build) so that WTP can resolve a valid site for server adapters. > Content that needs to be copied is here: > http://download.jboss.org/jbosstools/oxygen/snapshots/updates/ > Once we release 4.6.0.Final, we can then update the symlink to point here: > http://download.jboss.org/jbosstools/photon/stable/updates/ > Upstream issue: > https://bugs.eclipse.org/529801 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23771) Deploy Docker wizard: Pushing Image into Openshift registry fails

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23771?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23771: ------------------------------------------ Afaik there's no solution to this. Shouldn't we resolve this as WONT_FIX? > Deploy Docker wizard: Pushing Image into Openshift registry fails > ----------------------------------------------------------------- > > Key: JBIDE-23771 > URL: https://issues.jboss.org/browse/JBIDE-23771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Environment: oc version > oc v1.3.2 > kubernetes v1.3.0+52492b4 > features: Basic-Auth GSSAPI Kerberos SPNEGO > Server https://openshift.hughestech.co:8443 > openshift v1.3.2 > kubernetes v1.3.0+52492b4 > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.x > > Attachments: FailedPush.png > > > See the issue created in upstream: https://github.com/openshift/origin/issues/12603 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.5.oxygen update site at code freeze to initiate it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-19933. -------------------------------- Resolution: Out of Date Photon URLs should be already bootstrapped, and after that we probably won't need to do annual breaking releases so we'll just stay on photon / 12. > Copy master snapshot to 4.5.oxygen update site at code freeze to initiate it > ---------------------------------------------------------------------------- > > Key: JBIDE-19933 > URL: https://issues.jboss.org/browse/JBIDE-19933 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.5.3.Final > > > When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master). > Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch. > It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point. > For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25301) [release] externalize common properties to parameterize jobs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25301?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25301: ------------------------------- Fix Version/s: 4.5.3.Final (was: 4.6.x) > [release] externalize common properties to parameterize jobs > ------------------------------------------------------------ > > Key: JBIDE-25301 > URL: https://issues.jboss.org/browse/JBIDE-25301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.3.Final > > > As in JBIDE-25137, we can externalize properties used in Jenkins to run jobs so the jobs are more parameterized. > for example we could set these params in the jbosstools-jenkins.properties files: > {code}TARGET_PLATFORM_VERSION_MIN= > TARGET_PLATFORM_VERSION_MAX= > TARGET_PLATFORM_CENTRAL_MAX= > {code} > Or we could simply remove them and source them from the parent pom. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4671) Errors updating from 11.1.0.GA to latest one

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4671?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4671: -------------------------------- Assignee: Jeff MAURY (was: Nick Boldt) > Errors updating from 11.1.0.GA to latest one > -------------------------------------------- > > Key: JBDS-4671 > URL: https://issues.jboss.org/browse/JBDS-4671 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer, updatesite > Affects Versions: 11.1.0.GA > Environment: Red Hat JBoss Developer Studio 11.1.0.GA with early access activate. > openjdk version "1.8.0_151" .OpenJDK Runtime Environment (build 1.8.0_151-b12) > Operating System: Fedora 27 > Reporter: Roman Martin Gil > Assignee: Jeff MAURY > Fix For: 11.3.0.GA > > Attachments: 01-rhjbds-available-updates.png, 02-rhjbds-about-installation.png, 03-rhjbds-updating-error.png, ds11.2-update-sites.png, ds11.2.0.ga.png, rhjbds11-software-sites.png > > > Since some days I am getting alerts to update my RHJBDS 11.1.0.GA to latest versions however I could not complete anyway. > Everyday I get a update alert with latest versions but it seems that they are not ready to be applied. > After some moments updating the environment I got the following error and stack trace: > {code:java} > An error occurred while collecting items to be installed > session context was:(profile=devstudio, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,com.jboss.devstudio.core,11.3.0.AM1-v20180125-1048-B1900 > No repository found containing: osgi.bundle,com.jboss.devstudio.core.capabilities,11.3.0.v20180124-1725 > No repository found containing: osgi.bundle,com.jboss.devstudio.core.central,11.3.0.AM1-v20180125-1048-B1900 > No repository found containing: osgi.bundle,com.jboss.devstudio.core.project.examples,11.3.0.v20180124-1725 > No repository found containing: osgi.bundle,com.jboss.devstudio.core.usage.branding,11.3.0.v20180124-1725 > No repository found containing: org.eclipse.update.feature,com.jboss.devstudio.core.capabilities.feature,11.3.0.v20180124-1725 > No repository found containing: org.eclipse.update.feature,com.jboss.devstudio.core.feature,11.3.0.v20180125-1048 > No repository found containing: binary,com.jboss.devstudio.core.package.executable.gtk.linux.x86_64,11.3.0.AM1-v20180125-1048-B1900 > No repository found containing: org.eclipse.update.feature,com.jboss.devstudio.core.rpm.feature,11.3.0.v20180125-1048 > No repository found containing: org.eclipse.update.feature,com.jboss.devstudio.core.rpmdeps.feature,11.3.0.v20180124-1725 > No repository found containing: org.eclipse.update.feature,com.jboss.devstudio.fuse.feature,11.3.0.v20180124-1725 > {code} > I attached some screenshots with the process. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23628) Application wizard: Should be able to create a new template parameter

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23628?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23628: ------------------------------------------ Upstream issue https://issues.jboss.org/browse/CLOUD-1170 was resolved. I dont see any real value to creating a new template parameter given that you would also have to alter the template. Thus resolving as REJECTED. > Application wizard: Should be able to create a new template parameter > ---------------------------------------------------------------------- > > Key: JBIDE-23628 > URL: https://issues.jboss.org/browse/JBIDE-23628 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > Fix For: 4.5.3.Final > > > In New OpenShift Application wizard there is a table on second wizard page with template parameter. It is possible only to edit existing, but not to create new one. It should be possible to create a new template parameter. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23628) Application wizard: Should be able to create a new template parameter

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23628?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-23628. -------------------------------------- Fix Version/s: 4.5.3.Final (was: 4.5.x) Assignee: Andre Dietisheim Resolution: Rejected > Application wizard: Should be able to create a new template parameter > ---------------------------------------------------------------------- > > Key: JBIDE-23628 > URL: https://issues.jboss.org/browse/JBIDE-23628 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.5.3.Final > > > In New OpenShift Application wizard there is a table on second wizard page with template parameter. It is possible only to edit existing, but not to create new one. It should be possible to create a new template parameter. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.5.oxygen update site at code freeze to initiate it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19933: ------------------------------- Fix Version/s: 4.5.3.Final (was: 4.5.x) > Copy master snapshot to 4.5.oxygen update site at code freeze to initiate it > ---------------------------------------------------------------------------- > > Key: JBIDE-19933 > URL: https://issues.jboss.org/browse/JBIDE-19933 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.5.3.Final > > > When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master). > Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch. > It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point. > For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23628) Application wizard: Should be able to create a new template parameter

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23628?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-23628. ------------------------------------ > Application wizard: Should be able to create a new template parameter > ---------------------------------------------------------------------- > > Key: JBIDE-23628 > URL: https://issues.jboss.org/browse/JBIDE-23628 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.5.3.Final > > > In New OpenShift Application wizard there is a table on second wizard page with template parameter. It is possible only to edit existing, but not to create new one. It should be possible to create a new template parameter. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24225) publish p2diff app to Nexus for easier use in jenkins jobs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24225?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24225: ------------------------------- Fix Version/s: 4.5.3.Final (was: 4.5.x) > publish p2diff app to Nexus for easier use in jenkins jobs > ---------------------------------------------------------- > > Key: JBIDE-24225 > URL: https://issues.jboss.org/browse/JBIDE-24225 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.3.Final > > Attachments: maven-releng-fetch.png > > > Rather than bootstrapping by hand and having to reference p2diff like this: > {code} > p2diff=/home/hudson/static_build_env/jbds/p2diff/x86$(if [[ $(uname -a | grep x86_64) ]]; then echo _64; fi)/p2diff > {code} > It would be way better if we could just fetch it via a maven step (as we do for other releng scripts) ... > !maven-releng-fetch.png|thumbnail! > ... and automatically unpack it to the workspace. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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 March 2018