December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21145) Composite install job does not reliably install all JBT IUs and so does not see changes between CI builds

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21145?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21145: ---------------------------------------- The issue detected by the composite would probably have been detectedfor free by Tycho while aggregating the coretests site. Keep in mind that Tycho already does some good dependency resolution. The suggestion is replace 1. composite-install 2. aggregate 3. publish by # Aggregate # Test aggregate (could be p2diff to check the diff; and/or an install-test like you're doing for composite; or even a UI install-grinder....) # Publish if test decide it's worth it. This basically remove 1 artifact in the build chain, it seems simpler. If we want to have it a bit stricter, the installation-tests could be configured in the pom.xml, hooked on the "verify" phase. So "mvn clean verify" would fail when the content can't be installed. > Composite install job does not reliably install all JBT IUs and so does not see changes between CI builds > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21145 > URL: https://issues.jboss.org/browse/JBIDE-21145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Pavol Srna > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > We have often seen old artifacts on nightly sites (mars and neon too). > It seems that the composite-install job [0], [1] is not reliable. So, the downstream JBT aggregate builds [2], [3] are not triggered automatically to pick up all new changes in the upstream JBT component site builds. > [0] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-... > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-... > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... (latest build shows: "Nov 27, 2015 6:15 AM NOT PUBLISHED: UNCHANGED") > [3] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... (latest build shows: "Nov 27, 2015 3:43 AM NOT PUBLISHED: UNCHANGED") > Please investigate. > Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21138) "Show In -> Web Browser" on EJB module does nothing.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21138?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-21138: ----------------------------------- Assignee: Rob Stryker Resolution: Done pushed > "Show In -> Web Browser" on EJB module does nothing. > ---------------------------------------------------- > > Key: JBIDE-21138 > URL: https://issues.jboss.org/browse/JBIDE-21138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Beta1 > Environment: JBDS 9.1.0.Beta1-v20151122-1948-B143 > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > As title says... Selecting "Show In -> Web Browser" on EJB module does nothing. I would expect this option to be disabled, or web browser to be opened with 404 page. Instead of this, nothing happens. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3489) Publishing existing eclipse project to OpenShift

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3489?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3489: ----------------------------------- failures have been fixed. > Publishing existing eclipse project to OpenShift > ------------------------------------------------ > > Key: JBDS-3489 > URL: https://issues.jboss.org/browse/JBDS-3489 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Critical > Labels: openshift_v3 > Fix For: 9.1.0.Beta1 > > Attachments: project-selection.bmml, project-selection.png > > > As a developer I would like to take an existing eclipse web project and deploy to my existing openshift v3 connection. > * This is equivalent to 'oc new-app' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3489) Publishing existing eclipse project to OpenShift

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3489?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3489: ------------------------------ Target Release: 9.1.0.GA (was: 9.0.0.GA) > Publishing existing eclipse project to OpenShift > ------------------------------------------------ > > Key: JBDS-3489 > URL: https://issues.jboss.org/browse/JBDS-3489 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Critical > Labels: openshift_v3 > Fix For: 9.1.0.Beta1 > > Attachments: project-selection.bmml, project-selection.png > > > As a developer I would like to take an existing eclipse web project and deploy to my existing openshift v3 connection. > * This is equivalent to 'oc new-app' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3489) Publishing existing eclipse project to OpenShift

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3489?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3489: ------------------------------ > Publishing existing eclipse project to OpenShift > ------------------------------------------------ > > Key: JBDS-3489 > URL: https://issues.jboss.org/browse/JBDS-3489 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Critical > Labels: openshift_v3 > Fix For: 9.1.0.Beta1 > > Attachments: project-selection.bmml, project-selection.png > > > As a developer I would like to take an existing eclipse web project and deploy to my existing openshift v3 connection. > * This is equivalent to 'oc new-app' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3489) Publishing existing eclipse project to OpenShift

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3489?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3489: ----------------------------- > Publishing existing eclipse project to OpenShift > ------------------------------------------------ > > Key: JBDS-3489 > URL: https://issues.jboss.org/browse/JBDS-3489 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Critical > Labels: openshift_v3 > Fix For: 9.1.0.Beta1 > > Attachments: project-selection.bmml, project-selection.png > > > As a developer I would like to take an existing eclipse web project and deploy to my existing openshift v3 connection. > * This is equivalent to 'oc new-app' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21190) Should we update wildfly icon / banner?

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21190?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21190: -------------------------------- Attachment: JBIDE-21190_v2.png Second screenshot has the 16-pixel icon not containing a server next to it. > Should we update wildfly icon / banner? > --------------------------------------- > > Key: JBIDE-21190 > URL: https://issues.jboss.org/browse/JBIDE-21190 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.3.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Attachments: JBIDE-21190.png, JBIDE-21190_v2.png > > > Wildfly is still using the jboss-by-redhat logo. Is this still appropriate? How about for the icon for the server itself? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21190) Should we update wildfly icon / banner?

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21190?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21190: -------------------------------- Attachment: JBIDE-21190.png > Should we update wildfly icon / banner? > --------------------------------------- > > Key: JBIDE-21190 > URL: https://issues.jboss.org/browse/JBIDE-21190 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.3.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Attachments: JBIDE-21190.png > > > Wildfly is still using the jboss-by-redhat logo. Is this still appropriate? How about for the icon for the server itself? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21190) Should we update wildfly icon / banner?

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21190?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-21190: ----------------------------------- Assignee: Rob Stryker > Should we update wildfly icon / banner? > --------------------------------------- > > Key: JBIDE-21190 > URL: https://issues.jboss.org/browse/JBIDE-21190 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.3.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > > Wildfly is still using the jboss-by-redhat logo. Is this still appropriate? How about for the icon for the server itself? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21190) Should we update wildfly icon / banner?

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-21190: ----------------------------------- Summary: Should we update wildfly icon / banner? Key: JBIDE-21190 URL: https://issues.jboss.org/browse/JBIDE-21190 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: server Affects Versions: 4.3.0.Final Reporter: Rob Stryker Wildfly is still using the jboss-by-redhat logo. Is this still appropriate? How about for the icon for the server itself? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

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 December 2015