March 2020 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-27100) For JBIDE 4.15.0.AM1: Prepare for 4.15.0.AM1 / 12.15.0.AM1 [forge]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27100?page=com.atlassian.jira.plug... ] Stephane Bouchet reassigned JBIDE-27100: ---------------------------------------- Assignee: George Gastaldi > For JBIDE 4.15.0.AM1: Prepare for 4.15.0.AM1 / 12.15.0.AM1 [forge] > ------------------------------------------------------------------ > > Key: JBIDE-27100 > URL: https://issues.redhat.com/browse/JBIDE-27100 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Reporter: Stephane Bouchet > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.15.0.AM1 > > > For JBIDE 4.15.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.15.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.15.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.15.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.14.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.14.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.14.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.14.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. > > [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for forge task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-27101) For JBIDE 4.15.0.AM1: Prepare for 4.15.0.AM1 / 12.15.0.AM1 [fusetools]

by Stephane Bouchet (Jira)

Stephane Bouchet created JBIDE-27101: ---------------------------------------- Summary: For JBIDE 4.15.0.AM1: Prepare for 4.15.0.AM1 / 12.15.0.AM1 [fusetools] Key: JBIDE-27101 URL: https://issues.redhat.com/browse/JBIDE-27101 Project: Tools (JBoss Tools) Issue Type: Task Components: fusetools Reporter: Stephane Bouchet Fix For: 4.15.0.AM1 For JBIDE 4.15.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.15.0.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.15.0.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.15.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.14.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.14.0.Final-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.14.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.14.0.Final-SNAPSHOT {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for fusetools task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-27101) For JBIDE 4.15.0.AM1: Prepare for 4.15.0.AM1 / 12.15.0.AM1 [fusetools]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27101?page=com.atlassian.jira.plug... ] Stephane Bouchet reassigned JBIDE-27101: ---------------------------------------- Assignee: Lars Heinemann > For JBIDE 4.15.0.AM1: Prepare for 4.15.0.AM1 / 12.15.0.AM1 [fusetools] > ---------------------------------------------------------------------- > > Key: JBIDE-27101 > URL: https://issues.redhat.com/browse/JBIDE-27101 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools > Reporter: Stephane Bouchet > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.15.0.AM1 > > > For JBIDE 4.15.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.15.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.15.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.15.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.14.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.14.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.14.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.14.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. > > [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for fusetools task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-27102) For JBIDE 4.15.0.AM1: Prepare for 4.15.0.AM1 / 12.15.0.AM1 [fusetools-extras]

by Stephane Bouchet (Jira)

Stephane Bouchet created JBIDE-27102: ---------------------------------------- Summary: For JBIDE 4.15.0.AM1: Prepare for 4.15.0.AM1 / 12.15.0.AM1 [fusetools-extras] Key: JBIDE-27102 URL: https://issues.redhat.com/browse/JBIDE-27102 Project: Tools (JBoss Tools) Issue Type: Task Components: fusetools-extras Reporter: Stephane Bouchet Fix For: 4.15.0.AM1 For JBIDE 4.15.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.15.0.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.15.0.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.15.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.14.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.14.0.Final-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.14.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.14.0.Final-SNAPSHOT {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for fusetools-extras task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-27102) For JBIDE 4.15.0.AM1: Prepare for 4.15.0.AM1 / 12.15.0.AM1 [fusetools-extras]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27102?page=com.atlassian.jira.plug... ] Stephane Bouchet reassigned JBIDE-27102: ---------------------------------------- Assignee: Lars Heinemann > For JBIDE 4.15.0.AM1: Prepare for 4.15.0.AM1 / 12.15.0.AM1 [fusetools-extras] > ----------------------------------------------------------------------------- > > Key: JBIDE-27102 > URL: https://issues.redhat.com/browse/JBIDE-27102 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools-extras > Reporter: Stephane Bouchet > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.15.0.AM1 > > > For JBIDE 4.15.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.15.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.15.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.15.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.14.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.14.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.14.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.14.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. > > [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for fusetools-extras task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-27103) For JBIDE 4.15.0.AM1: Prepare for 4.15.0.AM1 / 12.15.0.AM1 [hibernate]

by Stephane Bouchet (Jira)

Stephane Bouchet created JBIDE-27103: ---------------------------------------- Summary: For JBIDE 4.15.0.AM1: Prepare for 4.15.0.AM1 / 12.15.0.AM1 [hibernate] Key: JBIDE-27103 URL: https://issues.redhat.com/browse/JBIDE-27103 Project: Tools (JBoss Tools) Issue Type: Task Components: hibernate Reporter: Stephane Bouchet Fix For: 4.15.0.AM1 For JBIDE 4.15.0.AM1 [hibernate]: 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.15.0.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.15.0.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.15.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.14.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.14.0.Final-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.14.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.14.0.Final-SNAPSHOT {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for hibernate task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-27103) For JBIDE 4.15.0.AM1: Prepare for 4.15.0.AM1 / 12.15.0.AM1 [hibernate]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27103?page=com.atlassian.jira.plug... ] Stephane Bouchet reassigned JBIDE-27103: ---------------------------------------- Assignee: Koen Aers > For JBIDE 4.15.0.AM1: Prepare for 4.15.0.AM1 / 12.15.0.AM1 [hibernate] > ---------------------------------------------------------------------- > > Key: JBIDE-27103 > URL: https://issues.redhat.com/browse/JBIDE-27103 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Stephane Bouchet > Assignee: Koen Aers > Priority: Blocker > Labels: task > Fix For: 4.15.0.AM1 > > > For JBIDE 4.15.0.AM1 [hibernate]: 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.15.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.15.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.15.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.14.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.14.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.14.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.14.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. > > [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for hibernate task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-27098) For JBIDE 4.15.0.AM1: Prepare for 4.15.0.AM1 / 12.15.0.AM1 [foundation]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27098?page=com.atlassian.jira.plug... ] Stephane Bouchet reassigned JBIDE-27098: ---------------------------------------- Assignee: Rob Stryker > For JBIDE 4.15.0.AM1: Prepare for 4.15.0.AM1 / 12.15.0.AM1 [foundation] > ----------------------------------------------------------------------- > > Key: JBIDE-27098 > URL: https://issues.redhat.com/browse/JBIDE-27098 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: foundation > Reporter: Stephane Bouchet > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.15.0.AM1 > > > For JBIDE 4.15.0.AM1 [foundation]: 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.15.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.15.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.15.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.14.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.14.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.14.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.14.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. > > [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for foundation task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-27098) For JBIDE 4.15.0.AM1: Prepare for 4.15.0.AM1 / 12.15.0.AM1 [foundation]

by Stephane Bouchet (Jira)

Stephane Bouchet created JBIDE-27098: ---------------------------------------- Summary: For JBIDE 4.15.0.AM1: Prepare for 4.15.0.AM1 / 12.15.0.AM1 [foundation] Key: JBIDE-27098 URL: https://issues.redhat.com/browse/JBIDE-27098 Project: Tools (JBoss Tools) Issue Type: Task Components: foundation Reporter: Stephane Bouchet Fix For: 4.15.0.AM1 For JBIDE 4.15.0.AM1 [foundation]: 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.15.0.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.15.0.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.15.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.14.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.14.0.Final-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.14.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.14.0.Final-SNAPSHOT {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for foundation task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-26480) Missing org.eclipse.epp.logging.aeri.ide plugin in devstudio

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-26480?page=com.atlassian.jira.plug... ] Stephane Bouchet commented on JBIDE-26480: ------------------------------------------ testing using osgi console with 4.14.0.Final give me an error : {code:java} osgi> ss aeri "Framework is launched." id State Bundle 341 STARTING org.eclipse.epp.logging.aeri.core_2.0.7.v20180504-0806 342 INSTALLED org.eclipse.epp.logging.aeri.ide_2.0.7.v20180504-0806 osgi> start 342 org.osgi.framework.BundleException: Could not resolve module: org.eclipse.epp.logging.aeri.ide [342] Unresolved requirement: Import-Package: org.apache.lucene.document; version="[7.1.0,8.0.0)" {code} despite the fact that this Import-Package is correctly resolved to the org.apache.lucene.core_7.5.0 bundle. After looking at the upstream bugzilla, aeri is not used anymore in the release train. the only reference i can find is from reddeer. maybe it's time to remove this dependency ? > Missing org.eclipse.epp.logging.aeri.ide plugin in devstudio > ------------------------------------------------------------- > > Key: JBIDE-26480 > URL: https://issues.redhat.com/browse/JBIDE-26480 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.10.0.AM1 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.15.0.AM1 > > > Moving TP from 4.9 to 4.10 caused missing org.eclipse.epp.logging.aeri.ide plugin. > One case how to reproduce this issue is to install RedDeer 2.4.0.M2 (Maybe even older 2.3.0.Final release) which requires aeri.core and aeri.ide plugins to be available. Restarting of devstudio after instalaltion or RD will shows in error log this: > {code} > Error > Tue Nov 20 10:11:03 CET 2018 > FrameworkEvent ERROR > org.osgi.framework.BundleException: Could not resolve module: org.eclipse.reddeer.eclipse.test [1196] > Unresolved requirement: Require-Bundle: org.eclipse.epp.logging.aeri.ide > -> Bundle-SymbolicName: org.eclipse.epp.logging.aeri.ide; bundle-version="2.0.7.v20180504-0806"; singleton:="true" > org.eclipse.epp.logging.aeri.ide [345] > Unresolved requirement: Import-Package: org.apache.lucene.document; version="[7.1.0,8.0.0)" > {code} > This is suggesting that it has something in common with lucene.core plugin. this might help identifying the root cause. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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 March 2020