October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18631) For JBIDE 4.2.0.Final: Prepare for Final/GA release [Aerogear]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18631?page=com.atlassian.jira.plugi... ] Gorkem Ercan closed JBIDE-18631. -------------------------------- Resolution: Done > For JBIDE 4.2.0.Final: Prepare for Final/GA release [Aerogear] > -------------------------------------------------------------- > > Key: JBIDE-18631 > URL: https://issues.jboss.org/browse/JBIDE-18631 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.2.0.Final > > > For JBIDE 4.2.0.Final [Aerogear]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 8.0.0.CR2, 4.2.0.Final or 8.0.0.GA. > [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Final-SNAPSHOT</version> > </parent> > {code} > 2. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.40.0.Final-SNAPSHOT > mvn clean verify -Dtpc.version=4.41.0.Final-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 Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18643) For JBIDE 4.2.0.Final: Prepare for Final/GA release [BrowserSim]

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18643?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov closed JBIDE-18643. ------------------------------------------ Resolution: Done > For JBIDE 4.2.0.Final: Prepare for Final/GA release [BrowserSim] > ---------------------------------------------------------------- > > Key: JBIDE-18643 > URL: https://issues.jboss.org/browse/JBIDE-18643 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Labels: task > Fix For: 4.2.0.Final > > > For JBIDE 4.2.0.Final [BrowserSim]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 8.0.0.CR2, 4.2.0.Final or 8.0.0.GA. > [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Final-SNAPSHOT</version> > </parent> > {code} > 2. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.40.0.Final-SNAPSHOT > mvn clean verify -Dtpc.version=4.41.0.Final-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 BrowserSim task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18643) For JBIDE 4.2.0.Final: Prepare for Final/GA release [BrowserSim]

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18643?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov reassigned JBIDE-18643: ---------------------------------------------- Assignee: Konstantin Marmalyukov > For JBIDE 4.2.0.Final: Prepare for Final/GA release [BrowserSim] > ---------------------------------------------------------------- > > Key: JBIDE-18643 > URL: https://issues.jboss.org/browse/JBIDE-18643 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Labels: task > Fix For: 4.2.0.Final > > > For JBIDE 4.2.0.Final [BrowserSim]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 8.0.0.CR2, 4.2.0.Final or 8.0.0.GA. > [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Final-SNAPSHOT</version> > </parent> > {code} > 2. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.40.0.Final-SNAPSHOT > mvn clean verify -Dtpc.version=4.41.0.Final-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 BrowserSim task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18633) For JBIDE 4.2.0.Final: Prepare for Final/GA release [VPE]

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18633?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov reassigned JBIDE-18633: ---------------------------------------------- Assignee: Konstantin Marmalyukov > For JBIDE 4.2.0.Final: Prepare for Final/GA release [VPE] > --------------------------------------------------------- > > Key: JBIDE-18633 > URL: https://issues.jboss.org/browse/JBIDE-18633 > 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.2.0.Final > > > For JBIDE 4.2.0.Final [VPE]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 8.0.0.CR2, 4.2.0.Final or 8.0.0.GA. > [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Final-SNAPSHOT</version> > </parent> > {code} > 2. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.40.0.Final-SNAPSHOT > mvn clean verify -Dtpc.version=4.41.0.Final-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 VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18633) For JBIDE 4.2.0.Final: Prepare for Final/GA release [VPE]

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18633?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov closed JBIDE-18633. ------------------------------------------ Resolution: Done > For JBIDE 4.2.0.Final: Prepare for Final/GA release [VPE] > --------------------------------------------------------- > > Key: JBIDE-18633 > URL: https://issues.jboss.org/browse/JBIDE-18633 > 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.2.0.Final > > > For JBIDE 4.2.0.Final [VPE]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 8.0.0.CR2, 4.2.0.Final or 8.0.0.GA. > [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Final-SNAPSHOT</version> > </parent> > {code} > 2. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.40.0.Final-SNAPSHOT > mvn clean verify -Dtpc.version=4.41.0.Final-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 VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18630) For JBIDE 4.2.0.Final: Prepare for Final/GA release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18630?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18630: ------------------------------------ New (updated) tools to audit these changes & verify builds have completed: https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/getPro... https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/getPro... sample usage: {code} ./getProjectRootPomParents.sh -b jbosstools-4.2.x -pv 4.2.0.Final-SNAPSHOT ./getProjectSHAs.sh -ju nboldt -jp jira_pwd -gu nickboldt(a)gmail.com -gp github_pwd -iu nickboldt -ip jira_pwd -jbt aerogear,arquillian,base,birt,browsersim,central,discovery,forge,freemarker,hibernate,javaee,jst,livereload,openshift,portlet,server,vpe,webservices -jbds product {code} > For JBIDE 4.2.0.Final: Prepare for Final/GA release > --------------------------------------------------- > > Key: JBIDE-18630 > URL: https://issues.jboss.org/browse/JBIDE-18630 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.2.0.Final > > > For JBIDE 4.2.0.Final: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 8.0.0.CR2, 4.2.0.Final or 8.0.0.GA. > [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Final-SNAPSHOT</version> > </parent> > {code} > 2. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.40.0.Final-SNAPSHOT > mvn clean verify -Dtpc.version=4.41.0.Final-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...] > See also: JBDS-3185 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18571) Some platform bundles comes from pre-SR1 build in CR2 builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18571?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18571: ------------------------------- Attachment: missing-bonus-jdt.core-hacked-by-otdt.png To avoid the inevitable "reopen for clarification", here's why there was an extra org.eclipse.jdt.core entry in the Luna SR1 site that is NOT in our mirrors or target platforms -- the extra one is org.eclipse.jdt.core 3.10.0.v_OTDT_r231_201409160728 : [^missing-bonus-jdt.core-hacked-by-otdt.png] > Some platform bundles comes from pre-SR1 build in CR2 builds > ------------------------------------------------------------ > > Key: JBIDE-18571 > URL: https://issues.jboss.org/browse/JBIDE-18571 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.CR2 > Reporter: Martin Malina > Assignee: Mickael Istria > Priority: Minor > Labels: respin-b > Fix For: 4.2.0.CR2 > > Attachments: missing-bonus-jdt.core-hacked-by-otdt.png, p2diff_SR1_SR1a, SR1vSR1a.p2diff.txt > > > JBoss Tools 4.2.0.CR2 / JBDS 8.0.0.CR2 should use Eclipse Luna SR1 (4.4.1), but everywhere we look, we see this Eclipse Platform feature: > org.eclipse.platform_4.4.0.v20140911-0143.jar > In both JBT and JBDS target platforms: > http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/4.... > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... > Also, I can see this version in my local installation of JBDS 8.0.0.CR1 B286. > I know about JBIDE-18539 - that Eclipse didn't upversion the platform, so it's still 4.4.0 for SR1, but at least the time stamp should be v20140925 as mentioned in that JIRA. This seems like we don't have SR1 at all. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18635) For JBIDE 4.2.0.Final: Prepare for Final/GA release [Central Discovery]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18635?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-18635. ------------------------------ Assignee: Nick Boldt Resolution: Done > For JBIDE 4.2.0.Final: Prepare for Final/GA release [Central Discovery] > ----------------------------------------------------------------------- > > Key: JBIDE-18635 > URL: https://issues.jboss.org/browse/JBIDE-18635 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: discovery > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.2.0.Final > > > For JBIDE 4.2.0.Final [Central Discovery]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 8.0.0.CR2, 4.2.0.Final or 8.0.0.GA. > [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Final-SNAPSHOT</version> > </parent> > {code} > 2. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.40.0.Final-SNAPSHOT > mvn clean verify -Dtpc.version=4.41.0.Final-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 Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18655) Project location should be set to "workspace" in Forge Project New wizard by default

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18655?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-18655: ------------------------------- Description: Current implementation is that "Project Location" is set to forge current selection. Which is set for the first project to "workspace", but for any other subsequent project to "forge current_selection" But it doesn't make much sense unless we want nested projects. *Is there a use case for nested projects?* I don't thinks so. Thus I would set "Project Location" to "workspace" by default. was: Current implementation is that "Project Location" is set to forge current selection. Which is set for the first project to "workspace", but for any other subsequent project to "forge current_selection" But it doesn't make much sense unless we want nested projects. Is there a use case for nested projects? I don't thinks so. Thus I would set "Project Location" to "workspace" by default. > Project location should be set to "workspace" in Forge Project New wizard by default > ------------------------------------------------------------------------------------ > > Key: JBIDE-18655 > URL: https://issues.jboss.org/browse/JBIDE-18655 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR2 > Reporter: Pavol Srna > > Current implementation is that "Project Location" is set to forge current selection. Which is set for the first project to "workspace", but for any other subsequent project to "forge current_selection" > But it doesn't make much sense unless we want nested projects. *Is there a use case for nested projects?* I don't thinks so. Thus I would set "Project Location" to "workspace" by default. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18655) Project location should be set to "workspace" in Forge Project New wizard by default

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-18655: ---------------------------------- Summary: Project location should be set to "workspace" in Forge Project New wizard by default Key: JBIDE-18655 URL: https://issues.jboss.org/browse/JBIDE-18655 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 4.2.0.CR2 Reporter: Pavol Srna Current implementation is that "Project Location" is set to forge current selection. Which is set for the first project to "workspace", but for any other subsequent project to "forge current_selection" But it doesn't make much sense unless we want nested projects. Is there a use case for nested projects? I don't thinks so. Thus I would set "Project Location" to "workspace" by default. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 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 October 2014