June 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26031) org.jboss.tools.jst.web.kb.FaceletValidatorExclude references validator ids that do not exist in org.eclipse.jst.jsf

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26031?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26031: ------------------------------- Fix Version/s: 4.6.0.AM3 (was: 4.6.x) > org.jboss.tools.jst.web.kb.FaceletValidatorExclude references validator ids that do not exist in org.eclipse.jst.jsf > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26031 > URL: https://issues.jboss.org/browse/JBIDE-26031 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.6.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.6.0.AM3 > > > Two validator IDs are referenced which do not exist. > {code} > 15:54:54 !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" > references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist.{code} > {code} > 15:54:54 !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" > references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} > As seen in https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26029) Incorrect warning for @Inject ServletContext

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26029?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26029: ------------------------------- Fix Version/s: 4.6.0.AM3 (was: 4.6.x) > Incorrect warning for @Inject ServletContext > -------------------------------------------- > > Key: JBIDE-26029 > URL: https://issues.jboss.org/browse/JBIDE-26029 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.5.3.Final > Reporter: Rich DiCroce > Assignee: Jeff MAURY > Fix For: 4.6.0.AM3 > > > If you inject ServletContext into a CDI bean, it gets flagged with this warning: > {quote} > No bean is eligible for injection to the injection point [JSR-346 §5.2.2] > {quote} > This warning appears to be correct for CDI 1.0, but not for later versions. From CDI 2.0 spec section 18.8 (also CDI 1.1/1.2 section 3.8): > {quote} > A servlet container must provide the following built-in beans, all of which have qualifier @Default: > * a bean with bean type javax.servlet.http.HttpServletRequest, allowing injection of a reference to the HttpServletRequest > * a bean with bean type javax.servlet.http.HttpSession, allowing injection of a reference to the HttpSession, > * a bean with bean type javax.servlet.ServletContext, allowing injection of a reference to the ServletContext, > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26133) For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [webservices]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26133?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26133. ------------------------------ Resolution: Done > For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [webservices] > ------------------------------------------------------------------------ > > Key: JBIDE-26133 > URL: https://issues.jboss.org/browse/JBIDE-26133 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.6.0.Final > > > For JBIDE 4.6.0.Final [webservices]: 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.6.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.6.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.6.0.Final-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.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-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 webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26135) For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [updatesite]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26135?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-26135: ---------------------------------- Assignee: Nick Boldt > For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [updatesite] > ----------------------------------------------------------------------- > > Key: JBIDE-26135 > URL: https://issues.jboss.org/browse/JBIDE-26135 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.6.0.Final > > > For JBIDE 4.6.0.Final [updatesite]: 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.6.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.6.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.6.0.Final-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.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-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 updatesite task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26136) For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [central-update]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26136?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-26136: ---------------------------------- Assignee: Nick Boldt > For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [central-update] > --------------------------------------------------------------------------- > > Key: JBIDE-26136 > URL: https://issues.jboss.org/browse/JBIDE-26136 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.6.0.Final > > > For JBIDE 4.6.0.Final [central-update]: 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.6.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.6.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.6.0.Final-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.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-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 central-update task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26135) For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [updatesite]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-26135: ---------------------------------- Summary: For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [updatesite] Key: JBIDE-26135 URL: https://issues.jboss.org/browse/JBIDE-26135 Project: Tools (JBoss Tools) Issue Type: Task Components: updatesite Reporter: Nick Boldt Priority: Blocker Fix For: 4.6.0.Final For JBIDE 4.6.0.Final [updatesite]: 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.6.0.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.6.0.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.6.0.Final-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.80.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.80.0.Final-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 updatesite task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26136) For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [central-update]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-26136: ---------------------------------- Summary: For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [central-update] Key: JBIDE-26136 URL: https://issues.jboss.org/browse/JBIDE-26136 Project: Tools (JBoss Tools) Issue Type: Task Components: central-update Reporter: Nick Boldt Priority: Blocker Fix For: 4.6.0.Final For JBIDE 4.6.0.Final [central-update]: 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.6.0.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.6.0.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.6.0.Final-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.80.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.80.0.Final-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 central-update task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26132) For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [visual-page-editor-core]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26132?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-26132: ---------------------------------- Assignee: Ilya Buziuk > For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [visual-page-editor-core] > ------------------------------------------------------------------------------------ > > Key: JBIDE-26132 > URL: https://issues.jboss.org/browse/JBIDE-26132 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: visual-page-editor-core > Reporter: Nick Boldt > Assignee: Ilya Buziuk > Priority: Blocker > Labels: task > Fix For: 4.6.0.Final > > > For JBIDE 4.6.0.Final [visual-page-editor-core]: 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.6.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.6.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.6.0.Final-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.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-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 visual-page-editor-core task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26133) For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [webservices]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-26133: ---------------------------------- Summary: For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [webservices] Key: JBIDE-26133 URL: https://issues.jboss.org/browse/JBIDE-26133 Project: Tools (JBoss Tools) Issue Type: Task Components: webservices Reporter: Nick Boldt Priority: Blocker Fix For: 4.6.0.Final For JBIDE 4.6.0.Final [webservices]: 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.6.0.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.6.0.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.6.0.Final-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.80.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.80.0.Final-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 webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26133) For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [webservices]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26133?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-26133: ---------------------------------- Assignee: Jeff MAURY > For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [webservices] > ------------------------------------------------------------------------ > > Key: JBIDE-26133 > URL: https://issues.jboss.org/browse/JBIDE-26133 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.6.0.Final > > > For JBIDE 4.6.0.Final [webservices]: 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.6.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.6.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.6.0.Final-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.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-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 webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 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 2018