June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22551) Prepare parent pom for 4.4.1 / 10.1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22551?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-22551. ------------------------------ Resolution: Done > Prepare parent pom for 4.4.1 / 10.1 > ----------------------------------- > > Key: JBIDE-22551 > URL: https://issues.jboss.org/browse/JBIDE-22551 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Alpha1 > > > * upversion parent pom to 4.4.1.Alpha1 > * set new lastStableRepository = http://download.jboss.org/jbosstools/neon/staging/updates/ to ensure baseline checks look at 4.4.0.Final instead of 4.3.x versions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22565) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Forge]

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22565?page=com.atlassian.jira.plugi... ] George Gastaldi closed JBIDE-22565. ----------------------------------- Resolution: Done > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Forge] > -------------------------------------------------------- > > Key: JBIDE-22565 > URL: https://issues.jboss.org/browse/JBIDE-22565 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Nick Boldt > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.4.1.Alpha1 > > > For JBIDE 4.4.1.Alpha1 [Forge]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.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 Forge 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)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3929) Uncategorized category on update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3929?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3929: ---------------------------------- This appears to be the result of having both a content.jar and a new content.xml.xz file. One is massaged by the removeDefaultCategory = true directive in jbdevstudio-product/site/pom.xml when calling generate-repository-facade on line 93. The new .xz file is however, NOT. So we end up with this in the content.xml inside content.xml.xz, on lines 50482 onward: {code} 50482- <unit id='GA-v20160603-2200.Default' version='1.0.0.CBEDQEOIcLUivEEl2Je8bAVHMOc9-X3vChuDdBLAJg7C5'> 50483- <properties size='3'> 50484: <property name='org.eclipse.equinox.p2.name' value='Uncategorized'/> 50485- <property name='org.eclipse.equinox.p2.description' value='Default category for otherwise uncategorized features'/> 50486- <property name='org.eclipse.equinox.p2.type.category' value='true'/> {code} > Uncategorized category on update site > ------------------------------------- > > Key: JBDS-3929 > URL: https://issues.jboss.org/browse/JBDS-3929 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: updatesite > Affects Versions: 10.0.0.GA > Reporter: Andrej Podhradsky > > The category 'Uncategorized' is on the follwoing update site > https://devstudio.redhat.com/10.0/staging/updates/ > Note that this categore contains source features which should not be in any category. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22424) JPA Generate Entities does not generate entities

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22424?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-22424: ----------------------------------------- Perhaps an enhancement would be to have PUBLIC or the default schema chosen by default. I'll open a JIRA in FORGE about that. Thank you very much > JPA Generate Entities does not generate entities > ------------------------------------------------ > > Key: JBIDE-22424 > URL: https://issues.jboss.org/browse/JBIDE-22424 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.4.0.Alpha2 > Reporter: Pavol Srna > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.4.0.Final > > > There is no exception in error log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22424) JPA Generate Entities does not generate entities

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22424?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-22424. ------------------------------ Resolution: Done > JPA Generate Entities does not generate entities > ------------------------------------------------ > > Key: JBIDE-22424 > URL: https://issues.jboss.org/browse/JBIDE-22424 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.4.0.Alpha2 > Reporter: Pavol Srna > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.4.0.Final > > > There is no exception in error log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22424) JPA Generate Entities does not generate entities

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22424?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-22424: ------------------------------------ You are right, with public schema it works. PUBLIC schema was chosen by default in previous builds, that's why I've missed it by automatically clicking on check all button and not checking the default schema values. > JPA Generate Entities does not generate entities > ------------------------------------------------ > > Key: JBIDE-22424 > URL: https://issues.jboss.org/browse/JBIDE-22424 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.4.0.Alpha2 > Reporter: Pavol Srna > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.4.0.Final > > > There is no exception in error log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22424) JPA Generate Entities does not generate entities

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22424?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-22424: ----------------------------------------- Ah I see you are generating the INFORMATION_SCHEMA schema. Does it work if you choose the PUBLIC schema instead? > JPA Generate Entities does not generate entities > ------------------------------------------------ > > Key: JBIDE-22424 > URL: https://issues.jboss.org/browse/JBIDE-22424 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.4.0.Alpha2 > Reporter: Pavol Srna > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.4.0.Final > > > There is no exception in error log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22565) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Forge]

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22565?page=com.atlassian.jira.plugi... ] George Gastaldi reassigned JBIDE-22565: --------------------------------------- Assignee: George Gastaldi > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Forge] > -------------------------------------------------------- > > Key: JBIDE-22565 > URL: https://issues.jboss.org/browse/JBIDE-22565 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Nick Boldt > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.4.1.Alpha1 > > > For JBIDE 4.4.1.Alpha1 [Forge]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.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 Forge 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)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22571) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [LiveReload]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-22571: ---------------------------------- Summary: For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [LiveReload] Key: JBIDE-22571 URL: https://issues.jboss.org/browse/JBIDE-22571 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: livereload Reporter: Nick Boldt Priority: Blocker For JBIDE 4.4.1.Alpha1 [LiveReload]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.1.Alpha1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) {code} mvn clean verify -Dtpc.version=4.60.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 LiveReload 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)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22560) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Base]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-22560: ---------------------------------- Summary: For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Base] Key: JBIDE-22560 URL: https://issues.jboss.org/browse/JBIDE-22560 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: usage, common/jst/core Reporter: Nick Boldt Priority: Blocker For JBIDE 4.4.1.Alpha1 [Base]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.1.Alpha1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) {code} mvn clean verify -Dtpc.version=4.60.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 Base 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)

9 years, 10 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 June 2016