July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20272) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20272: ---------------------------------- Summary: For JBIDE 4.3.0.Beta2: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] Key: JBIDE-20272 URL: https://issues.jboss.org/browse/JBIDE-20272 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: build Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.0.Beta2 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; {code} git checkout master git pull origin master git checkout -b jbosstools-4.3.0.Beta2x git push origin jbosstools-4.3.0.Beta2x {code} 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. {code} git checkout master git pull origin master {code} 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.CR1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran 4. Close (do not resolve) this JIRA when done. 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] 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 build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20273) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Server]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20273: ---------------------------------- Summary: For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Server] Key: JBIDE-20273 URL: https://issues.jboss.org/browse/JBIDE-20273 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: server Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.0.Beta2 [Server]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; {code} git checkout master git pull origin master git checkout -b jbosstools-4.3.0.Beta2x git push origin jbosstools-4.3.0.Beta2x {code} 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. {code} git checkout master git pull origin master {code} 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.CR1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran 4. Close (do not resolve) this JIRA when done. 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] 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 Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3483) For JBDS 9.0.0.Beta2: Code Freeze + Branch

by Nick Boldt (JIRA)

Nick Boldt created JBDS-3483: -------------------------------- Summary: For JBDS 9.0.0.Beta2: Code Freeze + Branch Key: JBDS-3483 URL: https://issues.jboss.org/browse/JBDS-3483 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: installer Reporter: Nick Boldt Priority: Blocker Fix For: 9.0.0.Beta2 For JBDS 9.0.0.Beta2: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; {code} git checkout master git pull origin master git checkout -b jbosstools-4.3.0.Beta2x git push origin jbosstools-4.3.0.Beta2x {code} 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. {code} git checkout master git pull origin master {code} 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.CR1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran 4. Close (do not resolve) this JIRA when done. 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20268) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Aerogear]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20268: ---------------------------------- Summary: For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Aerogear] Key: JBIDE-20268 URL: https://issues.jboss.org/browse/JBIDE-20268 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: aerogear-hybrid, cordovasim Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.0.Beta2 [Aerogear]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; {code} git checkout master git pull origin master git checkout -b jbosstools-4.3.0.Beta2x git push origin jbosstools-4.3.0.Beta2x {code} 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. {code} git checkout master git pull origin master {code} 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.CR1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran 4. Close (do not resolve) this JIRA when done. 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] 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 Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20267) For JBIDE 4.3.0.Beta2: Code Freeze + Branch

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20267: ---------------------------------- Summary: For JBIDE 4.3.0.Beta2: Code Freeze + Branch Key: JBIDE-20267 URL: https://issues.jboss.org/browse/JBIDE-20267 Project: Tools (JBoss Tools) Issue Type: Task Components: build Reporter: Nick Boldt Priority: Blocker Fix For: 4.3.0.Beta2 For JBIDE 4.3.0.Beta2: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; {code} git checkout master git pull origin master git checkout -b jbosstools-4.3.0.Beta2x git push origin jbosstools-4.3.0.Beta2x {code} 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. {code} git checkout master git pull origin master {code} 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.CR1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran 4. Close (do not resolve) this JIRA when done. 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] See also: JBDS-3483 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20269) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Central Discovery]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20269: ---------------------------------- Summary: For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Central Discovery] Key: JBIDE-20269 URL: https://issues.jboss.org/browse/JBIDE-20269 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: discovery Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.0.Beta2 [Central Discovery]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; {code} git checkout master git pull origin master git checkout -b jbosstools-4.3.0.Beta2x git push origin jbosstools-4.3.0.Beta2x {code} 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. {code} git checkout master git pull origin master {code} 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.CR1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran 4. Close (do not resolve) this JIRA when done. 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] 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 Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20270) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [VPE]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20270: ---------------------------------- Summary: For JBIDE 4.3.0.Beta2: Code Freeze + Branch [VPE] Key: JBIDE-20270 URL: https://issues.jboss.org/browse/JBIDE-20270 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: visual-page-editor-core Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.0.Beta2 [VPE]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; {code} git checkout master git pull origin master git checkout -b jbosstools-4.3.0.Beta2x git push origin jbosstools-4.3.0.Beta2x {code} 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. {code} git checkout master git pull origin master {code} 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.CR1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran 4. Close (do not resolve) this JIRA when done. 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] 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 VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20271) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Integration Tests]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20271: ---------------------------------- Summary: For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Integration Tests] Key: JBIDE-20271 URL: https://issues.jboss.org/browse/JBIDE-20271 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: qa Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.0.Beta2 [Integration Tests]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; {code} git checkout master git pull origin master git checkout -b jbosstools-4.3.0.Beta2x git push origin jbosstools-4.3.0.Beta2x {code} 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. {code} git checkout master git pull origin master {code} 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.CR1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran 4. Close (do not resolve) this JIRA when done. 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] 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 Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20216) Include Mylyn Wikitext Asciidoc editor in JBT/JBDS "CoreTools" update site category (not in Central, Marketplace or BYOE)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20216?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20216: ------------------------------- Summary: Include Mylyn Wikitext Asciidoc editor in JBT/JBDS "CoreTools" update site category (not in Central, Marketplace or BYOE) (was: Include Mylyn Wikitext Asciidoc editor in JBT/JBDS CoreTools category on update site (not in Central or BYOE)) > Include Mylyn Wikitext Asciidoc editor in JBT/JBDS "CoreTools" update site category (not in Central, Marketplace or BYOE) > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20216 > URL: https://issues.jboss.org/browse/JBIDE-20216 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, updatesite, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 4.3.0.Beta2 > > > Wiki page: https://wiki.eclipse.org/Mylyn/WikiText/AsciiDoc > Update site: http://download.eclipse.org/mylyn/snapshots/nightly/docs/ (wikitext-extra) > Features to include: > * org.eclipse.mylyn.wikitext.extras > * org.eclipse.mylyn.wikitext_feature (already in TP: https://github.com/jbosstools/jbosstools-target-platforms/blob/4.50.x/jbo... [ see JBDS-3259 ] > * DONE: pull a mirror: http://download.jboss.org/jbosstools/updates/requirements/mylyn-extras/2.... (done) > * DONE: add it to JBT/JBDS TP: https://github.com/jbosstools/jbosstools-target-platforms/pull/158 (Nightly versions, not the mix of versions suggested in PR 159) > TODO: add asciidoctor plugin (not whole feature) to CoreTools for JBT/JBDS: https://github.com/jbosstools/jbosstools-build-sites/pull/197 and https://github.com/jbdevstudio/jbdevstudio-product/pull/320 > TODO? add new connector to JBT/JBDS Central? Early Access? > TODO? add to JBDS BYOE feature https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > TODO? add to Central/Marketplace requires a feature wrapper, or just use org.eclipse.mylyn.wikitext.extras feature > TODO: @max to look at other plugins in org.eclipse.mylyn.wikitext.extras feature to see if anything is "scary" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20216) Include Mylyn Wikitext Asciidoc editor in JBT/JBDS CoreTools category on update site (not in Central or BYOE)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20216?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20216: ------------------------------- Summary: Include Mylyn Wikitext Asciidoc editor in JBT/JBDS CoreTools category on update site (not in Central or BYOE) (was: Include Mylyn Wikitext Asciidoc editor in JBT/JBDS) > Include Mylyn Wikitext Asciidoc editor in JBT/JBDS CoreTools category on update site (not in Central or BYOE) > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20216 > URL: https://issues.jboss.org/browse/JBIDE-20216 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, updatesite, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 4.3.0.Beta2 > > > Wiki page: https://wiki.eclipse.org/Mylyn/WikiText/AsciiDoc > Update site: http://download.eclipse.org/mylyn/snapshots/nightly/docs/ (wikitext-extra) > Features to include: > * org.eclipse.mylyn.wikitext.extras > * org.eclipse.mylyn.wikitext_feature (already in TP: https://github.com/jbosstools/jbosstools-target-platforms/blob/4.50.x/jbo... [ see JBDS-3259 ] > * DONE: pull a mirror: http://download.jboss.org/jbosstools/updates/requirements/mylyn-extras/2.... (done) > * DONE: add it to JBT/JBDS TP: https://github.com/jbosstools/jbosstools-target-platforms/pull/158 (Nightly versions, not the mix of versions suggested in PR 159) > TODO: add asciidoctor plugin (not whole feature) to CoreTools for JBT/JBDS: https://github.com/jbosstools/jbosstools-build-sites/pull/197 and https://github.com/jbdevstudio/jbdevstudio-product/pull/320 > TODO? add new connector to JBT/JBDS Central? Early Access? > TODO? add to JBDS BYOE feature https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > TODO? add to Central/Marketplace requires a feature wrapper, or just use org.eclipse.mylyn.wikitext.extras feature > TODO: @max to look at other plugins in org.eclipse.mylyn.wikitext.extras feature to see if anything is "scary" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 July 2015