July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20268) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Aerogear]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20268?page=com.atlassian.jira.plugi... ] Gorkem Ercan reassigned JBIDE-20268: ------------------------------------ Assignee: Gorkem Ercan > For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Aerogear] > ------------------------------------------------------ > > Key: JBIDE-20268 > URL: https://issues.jboss.org/browse/JBIDE-20268 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.Beta2 [Aerogear]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta2x > git push origin jbosstools-4.3.0.Beta2x > {code} > 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and > * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 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 Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20215) Version property is not replaced with a value defined in parent pom

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20215?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20215: ------------------------------------- So Maven 3.2.3 CLI produces different results than Maven 3.3.3 CLI? If that's the case, that's a regression in Maven itself, that needs to be addressed upstream. You should open a ticket at https://jira.codehaus.org/browse/MNG then > Version property is not replaced with a value defined in parent pom > ------------------------------------------------------------------- > > Key: JBIDE-20215 > URL: https://issues.jboss.org/browse/JBIDE-20215 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.Alpha1 > Environment: JBDS 9.0.0.Alpha1 > Reporter: Matous Jobanek > > Consider this situation: > There is a parent pom where a version property is defined. > {code:xml} > <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> > <modelVersion>4.0.0</modelVersion> > <groupId>jira</groupId> > <artifactId>jira-reproducer-parent</artifactId> > <version>1.0</version> > <packaging>pom</packaging> > <properties> > <reproducer.child.version>1.1.Final</reproducer.child.version> > </properties> > </project> > {code} > Then there is a child pom and version of this pom is the property defined in the parent pom. > {code:xml} > <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> > <modelVersion>4.0.0</modelVersion> > <parent> > <groupId>jira</groupId> > <artifactId>jira-reproducer-parent</artifactId> > <version>1.0</version> > <relativePath>../pom.xml</relativePath> > </parent> > <artifactId>jira-reproducer-child</artifactId> > <version>${reproducer.child.version}</version> > </project> > {code} > Then the generated pom at target/classes/META-INF/maven/jira/jira-reproducer-child/pom.xml doesn't contain the replaced value from the parent pom, but the original property: > {code:xml} > <version>${reproducer.child.version}</version> > {code} > should be: > {code:xml} > <version>1.1.Final</version> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20270) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [VPE]

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20270?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov closed JBIDE-20270. ------------------------------------------ Assignee: Konstantin Marmalyukov Resolution: Done > For JBIDE 4.3.0.Beta2: Code Freeze + Branch [VPE] > ------------------------------------------------- > > Key: JBIDE-20270 > URL: https://issues.jboss.org/browse/JBIDE-20270 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.Beta2 [VPE]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta2x > git push origin jbosstools-4.3.0.Beta2x > {code} > 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and > * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 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 VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20282) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [BrowserSim]

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20282?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov closed JBIDE-20282. ------------------------------------------ Resolution: Done > For JBIDE 4.3.0.Beta2: Code Freeze + Branch [BrowserSim] > -------------------------------------------------------- > > Key: JBIDE-20282 > URL: https://issues.jboss.org/browse/JBIDE-20282 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.Beta2 [BrowserSim]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta2x > git push origin jbosstools-4.3.0.Beta2x > {code} > 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and > * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 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 BrowserSim task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20293) Project wizard: error text is too verbose, shows json

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20293?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20293: ------------------------------------- Labels: projects_wizard (was: ) > Project wizard: error text is too verbose, shows json > ----------------------------------------------------- > > Key: JBIDE-20293 > URL: https://issues.jboss.org/browse/JBIDE-20293 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: projects_wizard > Fix For: 4.3.0.Beta2 > > Attachments: verbose-error.png > > > steps to reproduce: > # ASSERT: make sure that you have a project in a v3 openshift connection > # EXEC: launch app wizard and hit "Manage Projects" > # ASSERT: project wizard pops up listing your project(s) > # EXEC: hit "New..." and provide a name that you already used > Result: > An error pops up as expected, since the project couldnt be created. But the error message shows json > !verbose-error.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20293) Project wizard: error text is too verbose, shows json

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20293?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20293: ------------------------------------------ merged and pushed to upstream/master > Project wizard: error text is too verbose, shows json > ----------------------------------------------------- > > Key: JBIDE-20293 > URL: https://issues.jboss.org/browse/JBIDE-20293 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Beta2 > > Attachments: verbose-error.png > > > steps to reproduce: > # ASSERT: make sure that you have a project in a v3 openshift connection > # EXEC: launch app wizard and hit "Manage Projects" > # ASSERT: project wizard pops up listing your project(s) > # EXEC: hit "New..." and provide a name that you already used > Result: > An error pops up as expected, since the project couldnt be created. But the error message shows json > !verbose-error.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20293) Project wizard: error text is too verbose, shows json

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20293?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20293: ------------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.CR1) > Project wizard: error text is too verbose, shows json > ----------------------------------------------------- > > Key: JBIDE-20293 > URL: https://issues.jboss.org/browse/JBIDE-20293 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Beta2 > > Attachments: verbose-error.png > > > steps to reproduce: > # ASSERT: make sure that you have a project in a v3 openshift connection > # EXEC: launch app wizard and hit "Manage Projects" > # ASSERT: project wizard pops up listing your project(s) > # EXEC: hit "New..." and provide a name that you already used > Result: > An error pops up as expected, since the project couldnt be created. But the error message shows json > !verbose-error.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20293) Project wizard: error text is too verbose, shows json

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20293?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-20293: ---------------------------------------- Assignee: Andre Dietisheim > Project wizard: error text is too verbose, shows json > ----------------------------------------------------- > > Key: JBIDE-20293 > URL: https://issues.jboss.org/browse/JBIDE-20293 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta2 > > Attachments: verbose-error.png > > > steps to reproduce: > # ASSERT: make sure that you have a project in a v3 openshift connection > # EXEC: launch app wizard and hit "Manage Projects" > # ASSERT: project wizard pops up listing your project(s) > # EXEC: hit "New..." and provide a name that you already used > Result: > An error pops up as expected, since the project couldnt be created. But the error message shows json > !verbose-error.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20293) Project wizard: error text is too verbose, shows json

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-20293: ---------------------------------------- Summary: Project wizard: error text is too verbose, shows json Key: JBIDE-20293 URL: https://issues.jboss.org/browse/JBIDE-20293 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.0.Beta2 Reporter: Andre Dietisheim Fix For: 4.3.0.CR1 Attachments: verbose-error.png steps to reproduce: # ASSERT: make sure that you have a project in a v3 openshift connection # EXEC: launch app wizard and hit "Manage Projects" # ASSERT: project wizard pops up listing your project(s) # EXEC: hit "New..." and provide a name that you already used Result: An error pops up as expected, since the project couldnt be created. But the error message shows json !verbose-error.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20293) Project wizard: error text is too verbose, shows json

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20293?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20293: ------------------------------------- Attachment: verbose-error.png > Project wizard: error text is too verbose, shows json > ----------------------------------------------------- > > Key: JBIDE-20293 > URL: https://issues.jboss.org/browse/JBIDE-20293 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.CR1 > > Attachments: verbose-error.png > > > steps to reproduce: > # ASSERT: make sure that you have a project in a v3 openshift connection > # EXEC: launch app wizard and hit "Manage Projects" > # ASSERT: project wizard pops up listing your project(s) > # EXEC: hit "New..." and provide a name that you already used > Result: > An error pops up as expected, since the project couldnt be created. But the error message shows json > !verbose-error.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 July 2015