December 2018 - jbosstools-issues

[JBoss JIRA] (JBIDE-26483) For JBIDE 4.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [forge]

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26483?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26483: ---------------------------------- Assignee: George Gastaldi > For JBIDE 4.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [forge] > ------------------------------------------------------------------ > > Key: JBIDE-26483 > URL: https://issues.jboss.org/browse/JBIDE-26483 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.11.0.AM1 > > > For JBIDE 4.11.0.AM1 [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 branch{color}* root pom to use the latest parent pom version, *{color:orange}4.11.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.11.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.11.0.AM1-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.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.10.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.10.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.10.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.10.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26483) For JBIDE 4.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [forge]

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26483?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-26483: ------------------------------------ bump up to parent pom version = 4.11.0.AM1-SNAPSHOT > For JBIDE 4.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [forge] > ------------------------------------------------------------------ > > Key: JBIDE-26483 > URL: https://issues.jboss.org/browse/JBIDE-26483 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.11.0.AM1 > > > For JBIDE 4.11.0.AM1 [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 branch{color}* root pom to use the latest parent pom version, *{color:orange}4.11.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.11.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.11.0.AM1-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.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.10.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.10.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.10.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.10.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26483) For JBIDE 4.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [forge]

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26483?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26483. ------------------------------ Resolution: Done > For JBIDE 4.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [forge] > ------------------------------------------------------------------ > > Key: JBIDE-26483 > URL: https://issues.jboss.org/browse/JBIDE-26483 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.11.0.AM1 > > > For JBIDE 4.11.0.AM1 [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 branch{color}* root pom to use the latest parent pom version, *{color:orange}4.11.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.11.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.11.0.AM1-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.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.10.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.10.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.10.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.10.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26484) For JBIDE 4.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [fusetools]

by Jeff MAURY (Jira)

Jeff MAURY created JBIDE-26484: ---------------------------------- Summary: For JBIDE 4.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [fusetools] Key: JBIDE-26484 URL: https://issues.jboss.org/browse/JBIDE-26484 Project: Tools (JBoss Tools) Issue Type: Task Components: fusetools Reporter: Jeff MAURY Fix For: 4.11.0.AM1 For JBIDE 4.11.0.AM1 [fusetools]: 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 branch{color}* root pom to use the latest parent pom version, *{color:orange}4.11.0.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.11.0.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.11.0.AM1-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.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.10.0.AM1-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.10.0.AM1-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.10.0.AM1-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.10.0.AM1-SNAPSHOT {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 fusetools task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26484) For JBIDE 4.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [fusetools]

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26484?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26484: ---------------------------------- Assignee: Lars Heinemann > For JBIDE 4.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [fusetools] > ---------------------------------------------------------------------- > > Key: JBIDE-26484 > URL: https://issues.jboss.org/browse/JBIDE-26484 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools > Reporter: Jeff MAURY > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.11.0.AM1 > > > For JBIDE 4.11.0.AM1 [fusetools]: 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 branch{color}* root pom to use the latest parent pom version, *{color:orange}4.11.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.11.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.11.0.AM1-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.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.10.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.10.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.10.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.10.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 fusetools task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26485) For JBIDE 4.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [fusetools-extras]

by Jeff MAURY (Jira)

Jeff MAURY created JBIDE-26485: ---------------------------------- Summary: For JBIDE 4.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [fusetools-extras] Key: JBIDE-26485 URL: https://issues.jboss.org/browse/JBIDE-26485 Project: Tools (JBoss Tools) Issue Type: Task Components: fusetools-extras Reporter: Jeff MAURY Fix For: 4.11.0.AM1 For JBIDE 4.11.0.AM1 [fusetools-extras]: 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 branch{color}* root pom to use the latest parent pom version, *{color:orange}4.11.0.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.11.0.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.11.0.AM1-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.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.10.0.AM1-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.10.0.AM1-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.10.0.AM1-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.10.0.AM1-SNAPSHOT {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 fusetools-extras task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26485) For JBIDE 4.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [fusetools-extras]

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26485?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26485: ---------------------------------- Assignee: Lars Heinemann > For JBIDE 4.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [fusetools-extras] > ----------------------------------------------------------------------------- > > Key: JBIDE-26485 > URL: https://issues.jboss.org/browse/JBIDE-26485 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools-extras > Reporter: Jeff MAURY > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.11.0.AM1 > > > For JBIDE 4.11.0.AM1 [fusetools-extras]: 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 branch{color}* root pom to use the latest parent pom version, *{color:orange}4.11.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.11.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.11.0.AM1-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.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.10.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.10.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.10.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.10.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 fusetools-extras task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26484) For JBIDE 4.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [fusetools]

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26484?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-26484: ------------------------------------ bump up to parent pom version = 4.11.0.AM1-SNAPSHOT > For JBIDE 4.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [fusetools] > ---------------------------------------------------------------------- > > Key: JBIDE-26484 > URL: https://issues.jboss.org/browse/JBIDE-26484 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools > Reporter: Jeff MAURY > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.11.0.AM1 > > > For JBIDE 4.11.0.AM1 [fusetools]: 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 branch{color}* root pom to use the latest parent pom version, *{color:orange}4.11.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.11.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.11.0.AM1-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.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.10.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.10.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.10.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.10.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 fusetools task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26392) Central New and Noteworthy for 4.10.0.AM1

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26392?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26392: ------------------------------- Fix Version/s: 4.11.0.AM1 (was: 4.10.0.AM1) > Central New and Noteworthy for 4.10.0.AM1 > ---------------------------------------------------- > > Key: JBIDE-26392 > URL: https://issues.jboss.org/browse/JBIDE-26392 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, maven, project-examples > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.11.0.AM1 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Central JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Central, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Central by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26391 #comment Create N&N for Central 4.10.0.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Central for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26391) Create New and Noteworthy for 4.10.0.AM1

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26391?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26391: ------------------------------- Fix Version/s: 4.11.0.AM1 (was: 4.10.0.AM1) > Create New and Noteworthy for 4.10.0.AM1 > ---------------------------------------- > > Key: JBIDE-26391 > URL: https://issues.jboss.org/browse/JBIDE-26391 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.11.0.AM1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N. See subtasks below. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2018