August 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20477) Template presentation is incorrect in New App wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20477?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20477: -------------------------------- Fix Version/s: 4.3.0.CR1 > Template presentation is incorrect in New App wizard > ----------------------------------------------------- > > Key: JBIDE-20477 > URL: https://issues.jboss.org/browse/JBIDE-20477 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Fred Bricon > Fix For: 4.3.0.CR1 > > Attachments: new app wizard.png > > > Trying to create a new app from template, there are issues in the templates that are displayed and filter which I think are related to being able to choose your project on the first page. > The addition of the project drop down makes the content of the template pane moot. It should be modified to only include the project selected in the project drop down. > The templates in all the projects on the server in question: > {code} > [root@vagrant vagrant]# oc get templates > NAME DESCRIPTION PARAMETERS OBJECTS > [root@vagrant vagrant]# oc get templates -n openshift > NAME DESCRIPTION PARAMETERS OBJECTS > amq6 Application template for ActiveMQ brokers. 13 (2 blank) 8 > amq6-persistent Application template for ActiveMQ brokers using persistent storage. 14 (2 blank) 9 > eap6-amq-persistent-sti Application template for EAP 6 A-MQ applications with persistent storage buil... 23 (7 blank) 11 > eap6-amq-sti Application template for EAP 6 A-MQ applications built using STI. 22 (7 blank) 10 > eap6-basic-sti Application template for EAP 6 applications built using STI. 12 (3 blank) 6 > eap6-https-sti Application template for EAP 6 applications built using STI. 16 (5 blank) 8 > eap6-mongodb-persistent-sti Application template for EAP 6 MongDB applications with persistent storage bu... 28 (14 blank) 11 > eap6-mongodb-sti Application template for EAP 6 MongDB applications built using STI. 27 (14 blank) 10 > eap6-mysql-persistent-sti Application template for EAP 6 MySQL applications with persistent storage bui... 29 (16 blank) 11 > eap6-mysql-sti Application template for EAP 6 MySQL applications built using STI. 28 (16 blank) 10 > eap6-postgresql-persistent-sti Application template for EAP 6 PostgreSQL applications with persistent storag... 26 (13 blank) 11 > eap6-postgresql-sti Application template for EAP 6 PostgreSQL applications built using STI. 25 (13 blank) 10 > jws-tomcat7-basic-sti Application template for JWS applications built using STI. 11 (3 blank) 5 > jws-tomcat7-https-sti Application template for JWS applications built using STI. 15 (4 blank) 7 > jws-tomcat7-mongodb-persistent-sti Application template for JWS MongoDB applications with persistent storage bui... 27 (11 blank) 10 > jws-tomcat7-mongodb-sti Application template for JWS MongoDB applications built using STI. 26 (11 blank) 9 > jws-tomcat7-mysql-persistent-sti Application template for JWS MySQL applications with persistent storage built... 28 (13 blank) 10 > jws-tomcat7-mysql-sti Application template for JWS MySQL applications built using STI. 27 (13 blank) 9 > jws-tomcat7-postgresql-persistent-sti Application template for JWS PostgreSQL applications with persistent storage... 25 (10 blank) 10 > jws-tomcat7-postgresql-sti Application template for JWS PostgreSQL applications built using STI. 24 (10 blank) 9 > jws-tomcat8-basic-sti Application template for JWS applications built using STI. 11 (3 blank) 5 > jws-tomcat8-https-sti Application template for JWS applications built using STI. 15 (4 blank) 7 > jws-tomcat8-mongodb-persistent-sti Application template for JWS MongoDB applications with persistent storage bui... 27 (11 blank) 10 > jws-tomcat8-mongodb-sti Application template for JWS MongoDB applications built using STI. 26 (11 blank) 9 > jws-tomcat8-mysql-persistent-sti Application template for JWS MySQL applications with persistent storage built... 28 (13 blank) 10 > jws-tomcat8-mysql-sti Application template for JWS MySQL applications built using STI. 27 (13 blank) 9 > jws-tomcat8-postgresql-persistent-sti Application template for JWS PostgreSQL applications with persistent storage... 25 (10 blank) 10 > jws-tomcat8-postgresql-sti Application template for JWS PostgreSQL applications built using STI. 24 (10 blank) 9 > [root@vagrant vagrant]# oc get templates -n openshift-dev > NAME DESCRIPTION PARAMETERS OBJECTS > [root@vagrant vagrant]# oc get templates -n openshift-infra > NAME DESCRIPTION PARAMETERS OBJECTS > [root@vagrant vagrant]# > {code} > !new app wizard.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20477) Template presentation is incorrect in New App wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20477?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-20477: ----------------------------------- Assignee: Fred Bricon > Template presentation is incorrect in New App wizard > ----------------------------------------------------- > > Key: JBIDE-20477 > URL: https://issues.jboss.org/browse/JBIDE-20477 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Fred Bricon > Attachments: new app wizard.png > > > Trying to create a new app from template, there are issues in the templates that are displayed and filter which I think are related to being able to choose your project on the first page. > The addition of the project drop down makes the content of the template pane moot. It should be modified to only include the project selected in the project drop down. > The templates in all the projects on the server in question: > {code} > [root@vagrant vagrant]# oc get templates > NAME DESCRIPTION PARAMETERS OBJECTS > [root@vagrant vagrant]# oc get templates -n openshift > NAME DESCRIPTION PARAMETERS OBJECTS > amq6 Application template for ActiveMQ brokers. 13 (2 blank) 8 > amq6-persistent Application template for ActiveMQ brokers using persistent storage. 14 (2 blank) 9 > eap6-amq-persistent-sti Application template for EAP 6 A-MQ applications with persistent storage buil... 23 (7 blank) 11 > eap6-amq-sti Application template for EAP 6 A-MQ applications built using STI. 22 (7 blank) 10 > eap6-basic-sti Application template for EAP 6 applications built using STI. 12 (3 blank) 6 > eap6-https-sti Application template for EAP 6 applications built using STI. 16 (5 blank) 8 > eap6-mongodb-persistent-sti Application template for EAP 6 MongDB applications with persistent storage bu... 28 (14 blank) 11 > eap6-mongodb-sti Application template for EAP 6 MongDB applications built using STI. 27 (14 blank) 10 > eap6-mysql-persistent-sti Application template for EAP 6 MySQL applications with persistent storage bui... 29 (16 blank) 11 > eap6-mysql-sti Application template for EAP 6 MySQL applications built using STI. 28 (16 blank) 10 > eap6-postgresql-persistent-sti Application template for EAP 6 PostgreSQL applications with persistent storag... 26 (13 blank) 11 > eap6-postgresql-sti Application template for EAP 6 PostgreSQL applications built using STI. 25 (13 blank) 10 > jws-tomcat7-basic-sti Application template for JWS applications built using STI. 11 (3 blank) 5 > jws-tomcat7-https-sti Application template for JWS applications built using STI. 15 (4 blank) 7 > jws-tomcat7-mongodb-persistent-sti Application template for JWS MongoDB applications with persistent storage bui... 27 (11 blank) 10 > jws-tomcat7-mongodb-sti Application template for JWS MongoDB applications built using STI. 26 (11 blank) 9 > jws-tomcat7-mysql-persistent-sti Application template for JWS MySQL applications with persistent storage built... 28 (13 blank) 10 > jws-tomcat7-mysql-sti Application template for JWS MySQL applications built using STI. 27 (13 blank) 9 > jws-tomcat7-postgresql-persistent-sti Application template for JWS PostgreSQL applications with persistent storage... 25 (10 blank) 10 > jws-tomcat7-postgresql-sti Application template for JWS PostgreSQL applications built using STI. 24 (10 blank) 9 > jws-tomcat8-basic-sti Application template for JWS applications built using STI. 11 (3 blank) 5 > jws-tomcat8-https-sti Application template for JWS applications built using STI. 15 (4 blank) 7 > jws-tomcat8-mongodb-persistent-sti Application template for JWS MongoDB applications with persistent storage bui... 27 (11 blank) 10 > jws-tomcat8-mongodb-sti Application template for JWS MongoDB applications built using STI. 26 (11 blank) 9 > jws-tomcat8-mysql-persistent-sti Application template for JWS MySQL applications with persistent storage built... 28 (13 blank) 10 > jws-tomcat8-mysql-sti Application template for JWS MySQL applications built using STI. 27 (13 blank) 9 > jws-tomcat8-postgresql-persistent-sti Application template for JWS PostgreSQL applications with persistent storage... 25 (10 blank) 10 > jws-tomcat8-postgresql-sti Application template for JWS PostgreSQL applications built using STI. 24 (10 blank) 9 > [root@vagrant vagrant]# oc get templates -n openshift-dev > NAME DESCRIPTION PARAMETERS OBJECTS > [root@vagrant vagrant]# oc get templates -n openshift-infra > NAME DESCRIPTION PARAMETERS OBJECTS > [root@vagrant vagrant]# > {code} > !new app wizard.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20478) use skipTestsOrITests instead of skipBaselineComparison to skip compare-version-with-baselines execution

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20478?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20478. ------------------------------ Resolution: Done PRs merged and pushed to jobs. Nothing for QE to review, so closing. > use skipTestsOrITests instead of skipBaselineComparison to skip compare-version-with-baselines execution > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20478 > URL: https://issues.jboss.org/browse/JBIDE-20478 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.CR1 > > > The compare-version-with-baselines step, done for every local build, is a waste of time & bandwidth. > Since I'm often building w/o tests, could we set the check/skip constraint to be skipTestsOrITests, so that this test is skipped when unit and integration tests are skipped? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20470) "Early Access enabled/installed" is hidden even though EA stuff is installed.

by Catherine Robson (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20470?page=com.atlassian.jira.plugi... ] Catherine Robson commented on JBIDE-20470: ------------------------------------------ I would recommend keeping it below the banner but reducing the font size significantly. Alternatively it could go to the right of the "Welcome to JBoss!" tagline. I wouldn't want to put it top left as a diagonal banner because it is the first thing you see on the page, and distracts you from the other content. I think this is "nice to know" information but don't think we need to raise it as the first thing that users see on the page like the diagonal design would do. I also think just "Early access enabled" is enough - can we remove the "/installed"? > "Early Access enabled/installed" is hidden even though EA stuff is installed. > ----------------------------------------------------------------------------- > > Key: JBIDE-20470 > URL: https://issues.jboss.org/browse/JBIDE-20470 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Beta2 > Reporter: Radim Hopp > Assignee: Fred Bricon > Attachments: earlyaccess.png > > > In previous version (4.2) the message varied of EA installed, EA enabled, EA enabled/installed. > Now the message just says that EA is enabled/installed, but only depends on the checkbox on Software/Update page. > When EA stuff is installed, but the checkbox is unchecked, the message is hidden even though it should be still shown imho. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-482) Migrate to using license feature in JBT IS 4.3 / JBDS IS 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-482?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-482: ---------------------------------- [~pleacu] I'll let you open subtasks for all your projects so they can track this requirement: * jbpm * integration-stack * modeshape * esb * bpel * fuseide * ... any any project which contains an old license.txt or license.html. If you see "Legal Affairs" it's the old license; the new one has "General Counsel". You might also like this checkFeatureLicenses.sh script I wrote: https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.3.x/u... > Migrate to using license feature in JBT IS 4.3 / JBDS IS 9 > ---------------------------------------------------------- > > Key: JBTIS-482 > URL: https://issues.jboss.org/browse/JBTIS-482 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > Attachments: jbide20194-portlet-not-updated.png > > > Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100 (probably already done when you moved from Luna to Mars). > 2. Switch to using the new o.j.t.foundation.license.feature, which includes the new Red Hat license address -- see JBIDE-19826 for more details. > Instructions for migration are here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > STEPS TO VERIFY THAT YOUR CHANGES WORKED: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-482) Migrate to using license feature in JBT IS 4.3 / JBDS IS 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-482?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBTIS-482: -------------------------------- Assignee: Paul Leacu (was: Nick Boldt) > Migrate to using license feature in JBT IS 4.3 / JBDS IS 9 > ---------------------------------------------------------- > > Key: JBTIS-482 > URL: https://issues.jboss.org/browse/JBTIS-482 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > Attachments: jbide20194-portlet-not-updated.png > > > Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100 (probably already done when you moved from Luna to Mars). > 2. Switch to using the new o.j.t.foundation.license.feature, which includes the new Red Hat license address -- see JBIDE-19826 for more details. > Instructions for migration are here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > STEPS TO VERIFY THAT YOUR CHANGES WORKED: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-482) Migrate to using license feature in JBT IS 4.3 / JBDS IS 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-482?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-482: ----------------------------- Description: Please perform the following tasks: 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100 (probably already done when you moved from Luna to Mars). 2. Switch to using the new o.j.t.foundation.license.feature, which includes the new Red Hat license address -- see JBIDE-19826 for more details. Instructions for migration are here: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... 2. Resolve this JIRA when done. QE can then verify and close it later. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] STEPS TO VERIFY THAT YOUR CHANGES WORKED: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... was: Please perform the following tasks: 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100 (probably already done when you moved from Luna to Mars). 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... 2. Resolve this JIRA when done. QE can then verify and close it later. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] STEPS TO VERIFY THAT YOUR CHANGES WORKED: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > Migrate to using license feature in JBT IS 4.3 / JBDS IS 9 > ---------------------------------------------------------- > > Key: JBTIS-482 > URL: https://issues.jboss.org/browse/JBTIS-482 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > Attachments: jbide20194-portlet-not-updated.png > > > Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100 (probably already done when you moved from Luna to Mars). > 2. Switch to using the new o.j.t.foundation.license.feature, which includes the new Red Hat license address -- see JBIDE-19826 for more details. > Instructions for migration are here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > STEPS TO VERIFY THAT YOUR CHANGES WORKED: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-482) Migrate to using license feature in JBT IS 4.3 / JBDS IS 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-482?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-482: ----------------------------- Description: Please perform the following tasks: 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100 (probably already done when you moved from Luna to Mars). 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... 2. Resolve this JIRA when done. QE can then verify and close it later. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] STEPS TO VERIFY THAT YOUR CHANGES WORKED: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... was: For JBIDE 4.3.0.CR1: Please perform the following tasks: 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... 2. Resolve this JIRA when done. QE can then verify and close it later. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] See also: JBDS-3481 STEPS TO VERIFY THAT IT WORKED: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > Migrate to using license feature in JBT IS 4.3 / JBDS IS 9 > ---------------------------------------------------------- > > Key: JBTIS-482 > URL: https://issues.jboss.org/browse/JBTIS-482 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > Attachments: jbide20194-portlet-not-updated.png > > > Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100 (probably already done when you moved from Luna to Mars). > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > STEPS TO VERIFY THAT YOUR CHANGES WORKED: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-482) Migrate to using license feature in JBT IS 4.3 / JBDS IS 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-482?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-482: ----------------------------- Project: JBoss Tools Integration Stack (was: Tools (JBoss Tools)) Key: JBTIS-482 (was: JBIDE-20516) Component/s: distribution (was: build) Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.CR1) > Migrate to using license feature in JBT IS 4.3 / JBDS IS 9 > ---------------------------------------------------------- > > Key: JBTIS-482 > URL: https://issues.jboss.org/browse/JBTIS-482 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > Attachments: jbide20194-portlet-not-updated.png > > > For JBIDE 4.3.0.CR1: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3481 > STEPS TO VERIFY THAT IT WORKED: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20516) Migrate to using license feature in JBT IS 4.3 / JBDS IS 9

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20516: ---------------------------------- Summary: Migrate to using license feature in JBT IS 4.3 / JBDS IS 9 Key: JBIDE-20516 URL: https://issues.jboss.org/browse/JBIDE-20516 Project: Tools (JBoss Tools) Issue Type: Task Components: build Reporter: Nick Boldt Assignee: Nick Boldt Priority: Blocker Fix For: 4.3.0.CR1 Attachments: jbide20194-portlet-not-updated.png For JBIDE 4.3.0.CR1: Please perform the following tasks: 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... 2. Resolve this JIRA when done. QE can then verify and close it later. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] See also: JBDS-3481 STEPS TO VERIFY THAT IT WORKED: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 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 August 2015