September 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20764: ------------------------------------- Affects Version/s: 4.3.0.CR1 > Create Server Adapter for OpenShift 3 applications > -------------------------------------------------- > > Key: JBIDE-20764 > URL: https://issues.jboss.org/browse/JBIDE-20764 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: new_and_noteworthy > Fix For: 4.3.1.Final > > > get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed. > Server status= matching deployment pod status > Possible menus: > - Start/Stop > - Show Web Console > - Port Forwarding > - Stream logs > [~maxandersen] can you think of anything else? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20796) neon update sites gets added out of the blue

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20796?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-20796: ---------------------------------------- Summary: neon update sites gets added out of the blue (was: neon is linked into our Mars CR1 release) > neon update sites gets added out of the blue > -------------------------------------------- > > Key: JBIDE-20796 > URL: https://issues.jboss.org/browse/JBIDE-20796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Critical > Attachments: update-sites.png, update.png > > > When I removed *all* updatesites and added just http://download.jboss.org/jbosstools/mars/development/updates/ (should have just mars cr1), install and then ran check for update my updatesites contained neon references. > See https://www.dropbox.com/s/xo040iyhiw9zhsw/Screenshot%202015-09-24%2009.41... > I'm not sure if I even needed to do the check for updates, but those are the steps I did. > note: I install *everything* and uncheck the "check all updatesites" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20644) Arquillian New and Noteworthy for 4.3.0.CR1

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20644?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-20644. ----------------------------------- All seems fine, closing the issue. > Arquillian New and Noteworthy for 4.3.0.CR1 > ------------------------------------------- > > Key: JBIDE-20644 > URL: https://issues.jboss.org/browse/JBIDE-20644 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.CR1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Arquillian is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Arquillian by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20648) Batch New and Noteworthy for 4.3.0.CR1

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20648?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-20648. ----------------------------------- All seems fine, closing the issue. > Batch New and Noteworthy for 4.3.0.CR1 > -------------------------------------- > > Key: JBIDE-20648 > URL: https://issues.jboss.org/browse/JBIDE-20648 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.CR1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Batch is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Batch by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20622) For JBIDE 4.3.0.CR1: Code Freeze + Branch [Playground]

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20622?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-20622. ----------------------------------- All seems to be OK so I am closing this Jira. > For JBIDE 4.3.0.CR1: Code Freeze + Branch [Playground] > ------------------------------------------------------ > > Key: JBIDE-20622 > URL: https://issues.jboss.org/browse/JBIDE-20622 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: playground > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [Playground]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.CR1 > [Unresolved JIRAs with fixVersion = 4.3.0.CR1, 9.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.x > git push origin jbosstools-4.3.x > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch (until .Final is available). > 4. Close (do not resolve) this JIRA when done. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20152) script the process of branching and tagging based on buildinfo.json

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20152?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-20152 at 9/24/15 4:27 AM: ---------------------------------------------------------------- [~akazakov], so the script worked fine and this JIRA can be closed? I noticed there was no tag for integration tests. Was this omitted intentionally? We don't object, actually it is probably desired to do our own tag when we're ready, but just checking. Also, when you used the script for branching, you did include integration tests. was (Author: mmalina): [~akazakov], so the script worked fine and this JIRA can be closed? I noticed there was no tag for integration tests. Was this omitted intentionally? We don't object, actually it is probably desired to do our own tag when we're ready, but just checking. > script the process of branching and tagging based on buildinfo.json > ------------------------------------------------------------------- > > Key: JBIDE-20152 > URL: https://issues.jboss.org/browse/JBIDE-20152 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.0.CR1 > > > {quote} > Last time I suggested we created a file with a line for each repo, like: > {code}jbosstools/jbosstools-hibernate, 13asd123asd232, jbosstools-4.3.0.Beta1{code} > You had a txt file before that had this information but in a hard-to-parse format. > I can try parse the buildinfo.json too but thought if you had the simpler one I could use that instead. > /max {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20152) script the process of branching and tagging based on buildinfo.json

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20152?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20152: --------------------------------------- [~akazakov], so the script worked fine and this JIRA can be closed? I noticed there was no tag for integration tests. Was this omitted intentionally? We don't object, actually it is probably desired to do our own tag when we're ready, but just checking. > script the process of branching and tagging based on buildinfo.json > ------------------------------------------------------------------- > > Key: JBIDE-20152 > URL: https://issues.jboss.org/browse/JBIDE-20152 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.0.CR1 > > > {quote} > Last time I suggested we created a file with a line for each repo, like: > {code}jbosstools/jbosstools-hibernate, 13asd123asd232, jbosstools-4.3.0.Beta1{code} > You had a txt file before that had this information but in a hard-to-parse format. > I can try parse the buildinfo.json too but thought if you had the simpler one I could use that instead. > /max {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20796) neon is linked into our Mars CR1 release

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20796?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-20796: ---------------------------------------- Priority: Critical (was: Blocker) > neon is linked into our Mars CR1 release > ---------------------------------------- > > Key: JBIDE-20796 > URL: https://issues.jboss.org/browse/JBIDE-20796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Priority: Critical > Attachments: update-sites.png, update.png > > > When I removed *all* updatesites and added just http://download.jboss.org/jbosstools/mars/development/updates/ (should have just mars cr1), install and then ran check for update my updatesites contained neon references. > See https://www.dropbox.com/s/xo040iyhiw9zhsw/Screenshot%202015-09-24%2009.41... > I'm not sure if I even needed to do the check for updates, but those are the steps I did. > note: I install *everything* and uncheck the "check all updatesites" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20778) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Integration Tests]

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20778?page=com.atlassian.jira.plugi... ] Martin Malina reassigned JBIDE-20778: ------------------------------------- Assignee: Martin Malina Resolution: Done Done. > For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Integration Tests] > --------------------------------------------------------------------- > > Key: JBIDE-20778 > URL: https://issues.jboss.org/browse/JBIDE-20778 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [Integration Tests]: Please perform the following tasks: > 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.) > Otherwise: > 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT > {code} > 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20796) neon is linked into our Mars CR1 release

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20796?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20796: --------------------------------------------- Plain eclipse does not fail for me either. Suspicion is on oomph now, so i'm downgrading this one. > neon is linked into our Mars CR1 release > ---------------------------------------- > > Key: JBIDE-20796 > URL: https://issues.jboss.org/browse/JBIDE-20796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Priority: Blocker > Attachments: update-sites.png, update.png > > > When I removed *all* updatesites and added just http://download.jboss.org/jbosstools/mars/development/updates/ (should have just mars cr1), install and then ran check for update my updatesites contained neon references. > See https://www.dropbox.com/s/xo040iyhiw9zhsw/Screenshot%202015-09-24%2009.41... > I'm not sure if I even needed to do the check for updates, but those are the steps I did. > note: I install *everything* and uncheck the "check all updatesites" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 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 September 2015