May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-641) How-to configure a remote server with JBDS 8.1

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-641?page=com.atlassian.jira.plug... ] Martin Malina commented on TOOLSDOC-641: ---------------------------------------- Hi [~mhusnain], I reviewed the current draft and have a few comments: 4.b Note: If you select Management Operations for the Controlled by field, you must set up an admin user on the server by editing the $SERVER_HOME/bin/add-users.sh file and enter the same credentials in the server editor or during the server start. - this is not correct. You're not supposed to edit the shell script. The shell script is used to add the user. (And also, it's add-users.bat on windows, but I'm not sure how much detailed you want to be.) So instead of "by editing" I would say "by using" 4.c The Server is externally managed. Assume server is started field is used when the user wants to deploy the server but does not want the IDE to stop or start the server for them. - "deploy the server" -> "deploy to the server" 4.d - it's good except for the end: "or leave the box unselected as a default" - this is not true - default is that it is checked (and a new runtime will be created in the next step if there is none existing) 5.a - I suggested that we could say something like "You may need to create a new host." Do you not agree? 5.c.d This location is within the directory specified in the Remote Server Home field. - while technically it is true that it is within the directory, it's not directly there, it's deeper - it's in SERVER_HOME/BASE_DIRECTORY/configuration/ - maybe it would be better explicitly say that? > How-to configure a remote server with JBDS 8.1 > ---------------------------------------------- > > Key: TOOLSDOC-641 > URL: https://issues.jboss.org/browse/TOOLSDOC-641 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Components: General documentation issues > Affects Versions: 4.2.3.Final > Reporter: Misha Ali > Assignee: Misha Ali > Fix For: 4.2.3.Final > > > Requesting QE review for the following content: > https://docs.google.com/a/redhat.com/document/d/1sd5_RaThCjbRxeA4D-YcYjXL... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19795) Bower support

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19795?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-19795: ------------------------------------- [~maxandersen], I guess I do have good news. It seems that we can have full bower support relatively easy (basically, all we need is UI). I have already done "bower update" for now, here is the short demo video - https://vimeo.com/127912643 What's more, I have had fun with embedding git terminal in eclipse (never would I thought it is even possible :-) ) - https://vimeo.com/127914493 All code is in my [fork|https://github.com/ibuziuk/jbosstools-playground/tree/bower] *bower* branch. I'm planning to polish things and make the initial contribution next week. > Bower support > ------------- > > Key: JBIDE-19795 > URL: https://issues.jboss.org/browse/JBIDE-19795 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Affects Versions: 4.3.0.Alpha2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.3.0.Final > > > Need to have initial [Bower|http://bower.io/] tools support: > *The gist* > Bower tooling should initially support several bower API commands : > |Command||Description| > | *bower init* |creates a *bower.json* file| > |*bower install <package>*|installs packages to *bower_components* folder| > |*bower uninstall <package>*|uninstalls a package locally from *bower_components* directory| > |*bower update* |updates installed packages to their newest version according to *bower.json*| > Basically, the main idea of the implementation is the following: > Eclipse plugin that will execute *external* bower commands - implementation will fall back on *native* bower installation via *ILaunchConfiguration* > Native bower tools must be preinstalled > *The main questions & proposals:* > 1. https://github.com/jbosstools/jbosstools-playground is probably the best place for initial implementation of bower stuff (infrastructure / build etc.) > 2. UI. should it be ILaunchShortcuts ("bower init" / "bower update" etc.) + launch configuration enabled for projects with js nature? > 3. Implementation details: > - the way of detecting bower? Should user point to it's installation dir and this location will be used for IExternalToolConstants.ATTR_LOCATION (windows case: *\user\AppData\Roaming\npm\node_modules\bower* ) > - if bower was not detected / installed - "Error message with a link to the bower website with installation details depending on the platform" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-17686 at 5/15/15 12:27 AM: -------------------------------------------------------------- I've gotten the TP to play nicely (validation works even though we now include cdt.native.* platform bits) and to get server to compile & install tm.terminal.connector.local.feature (requires cdt.native feature). PRs updated & ready for review: https://github.com/jbosstools/jbosstools-target-platforms/pull/142/ https://github.com/jbosstools/jbosstools-server/pull/343 https://github.com/jbdevstudio/jbdevstudio-product/pull/308 --- To build the M7 TP: {code} cd /path/to/jbosstools-target-platforms/jbosstools/multiple hub checkout https://github.com/jbosstools/jbosstools-target-platforms/pull/142/ mvn clean install {code} Then you can build Server: {code} cd /path/to/jbosstools-server hub checkout https://github.com/jbosstools/jbosstools-server/pull/343 mvn clean verify -Dtpc.targetKind=multiple {code} Then JBoss Tools aggregate: {code} cd ~/tru/jbosstools-build-sites/aggregate/site mvn clean install -Djbosstools-server-site=file:///home/nboldt/tru/jbosstools-server/site/target/repository/ {code} And JBDS: {code} cd ~/tru/jbdevstudio-product hub checkout https://github.com/jbdevstudio/jbdevstudio-product/pull/308 mvn clean install -Djbosstools-site=file:///home/nboldt/tru/buildsites/aggregate/site/target/repository/ -e {code} was (Author: nickboldt): I've gotten the TP to play nicely (validation works even though we now include cdt.native.* platform bits) and to get server to compile & install tm.terminal.connector.local.feature (requires cdt.native feature). PRs updated & ready for review: https://github.com/jbosstools/jbosstools-target-platforms/pull/142/ https://github.com/jbosstools/jbosstools-server/pull/343 https://github.com/jbdevstudio/jbdevstudio-product/pull/308 > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.0.Beta1 > > Attachments: eclipse-can-has-many-consoles.png, org.jboss.tools.as.management.itests.AS7IntegrationTestSuite.txt > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19776) Create and use Mars M7 target-platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19776?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-19776 at 5/15/15 12:26 AM: -------------------------------------------------------------- To recap changes since I first put this PR together: * remove fest (it was commented out already) * add org.eclipse.tm.terminal.control.feature.feature.group (rse.terminals requires it); remove old org.junit 3.8.2.v3_8_2_v20130308-0410 * add org.eclipse.egit.ui.importer 0.0.1.201505070847 (needed for easymport) * jbosstools-server requests that the new tm.terminal views/connectors be installed along with it, so add org.eclipse.tm.terminal.*, connector.local.feature and org.eclipse.cdt.core.native.feature (JBIDE-17686, JBIDE-19776) * Switch to Mockito 1.9.5.v20131024-0922 (from Locus 1.2.0.Final site) If you haven't tried the latest M7 TP, please do so from this PR: {code} cd /path/to/jbosstools-target-platforms/jbosstools/multiple hub checkout https://github.com/jbosstools/jbosstools-target-platforms/pull/142/ mvn clean install {code} Updated p2diffs: [^jbosstools.p2diff.v20150514.txt] [^jbdevstudio.p2diff.v20150514.txt] Then you can build Server: {code} cd /path/to/jbosstools-server hub checkout https://github.com/jbosstools/jbosstools-server/pull/343 mvn clean verify -Dtpc.targetKind=multiple {code} Then JBoss Tools aggregate: {code} cd ~/tru/jbosstools-build-sites/aggregate/site mvn clean install -Djbosstools-server-site=file:///home/nboldt/tru/jbosstools-server/site/target/repository/ {code} And JBDS: {code} cd ~/tru/jbdevstudio-product hub checkout https://github.com/jbdevstudio/jbdevstudio-product/pull/308 mvn clean install -Djbosstools-site=file:///home/nboldt/tru/buildsites/aggregate/site/target/repository/ -e {code} was (Author: nickboldt): To recap changes since I first put this PR together: * remove fest (it was commented out already) * add org.eclipse.tm.terminal.control.feature.feature.group (rse.terminals requires it); remove old org.junit 3.8.2.v3_8_2_v20130308-0410 * add org.eclipse.egit.ui.importer 0.0.1.201505070847 (needed for easymport) * jbosstools-server requests that the new tm.terminal views/connectors be installed along with it, so add org.eclipse.tm.terminal.*, connector.local.feature and org.eclipse.cdt.core.native.feature (JBIDE-17686, JBIDE-19776) * Switch to Mockito 1.9.5.v20131024-0922 (from Locus 1.2.0.Final site) If you haven't tried the latest M7 TP, please do so from this PR: {code} cd /path/to/jbosstools-target-platforms/jbosstools/multiple hub checkout https://github.com/jbosstools/jbosstools-target-platforms/pull/142/ mvn clean install {code} Updated p2diffs: [^jbosstools.p2diff.v20150514.txt] [^jbdevstudio.p2diff.v20150514.txt] Then you can build Server: {code} cd /path/to/jbosstools-server hub checkout https://github.com/jbosstools/jbosstools-server/pull/343 mvn clean verify -Dtpc.targetKind=multiple {code} Then JBoss Tools aggregate: {code} cd ~/tru/jbosstools-build-sites/aggregate/site mvn clean install -Djbosstools-server-site=file:///home/nboldt/tru/jbosstools-server/site/target/repository/ {code} And JBDS: {code} cd ~/tru/jbdevstudio-product hub checkout https://github.com/jbosstools/jbosstools-target-platforms/pull/142/ mvn clean install -Djbosstools-site=file:///home/nboldt/tru/buildsites/aggregate/site/target/repository/ -e {code} > Create and use Mars M7 target-platform > -------------------------------------- > > Key: JBIDE-19776 > URL: https://issues.jboss.org/browse/JBIDE-19776 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: jbdevstudio.p2diff.txt, jbdevstudio.p2diff.v20150514.txt, jbdevstudio.p2diff.v3.txt, jbosstools.p2diff.txt, jbosstools.p2diff.v20150514.txt, jbosstools.p2diff.v3.txt > > > Mars M7 was released and contains interesting changes. > We need to start using it ASAP to leverage new functionalities and adapt to the most important changes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19776) Create and use Mars M7 target-platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19776?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-19776 at 5/15/15 12:25 AM: -------------------------------------------------------------- To recap changes since I first put this PR together: * remove fest (it was commented out already) * add org.eclipse.tm.terminal.control.feature.feature.group (rse.terminals requires it); remove old org.junit 3.8.2.v3_8_2_v20130308-0410 * add org.eclipse.egit.ui.importer 0.0.1.201505070847 (needed for easymport) * jbosstools-server requests that the new tm.terminal views/connectors be installed along with it, so add org.eclipse.tm.terminal.*, connector.local.feature and org.eclipse.cdt.core.native.feature (JBIDE-17686, JBIDE-19776) * Switch to Mockito 1.9.5.v20131024-0922 (from Locus 1.2.0.Final site) If you haven't tried the latest M7 TP, please do so from this PR: {code} cd /path/to/jbosstools-target-platforms/jbosstools/multiple hub checkout https://github.com/jbosstools/jbosstools-target-platforms/pull/142/ mvn clean install {code} Updated p2diffs: [^jbosstools.p2diff.v20150514.txt] [^jbdevstudio.p2diff.v20150514.txt] Then you can build Server: {code} cd /path/to/jbosstools-server hub checkout https://github.com/jbosstools/jbosstools-server/pull/343 mvn clean verify -Dtpc.targetKind=multiple {code} Then JBoss Tools aggregate: {code} cd ~/tru/jbosstools-build-sites/aggregate/site mvn clean install -Djbosstools-server-site=file:///home/nboldt/tru/jbosstools-server/site/target/repository/ {code} And JBDS: {code} cd ~/tru/jbdevstudio-product hub checkout https://github.com/jbosstools/jbosstools-target-platforms/pull/142/ mvn clean install -Djbosstools-site=file:///home/nboldt/tru/buildsites/aggregate/site/target/repository/ -e {code} was (Author: nickboldt): To recap changes since I first put this PR together: * remove fest (it was commented out already) * add org.eclipse.tm.terminal.control.feature.feature.group (rse.terminals requires it); remove old org.junit 3.8.2.v3_8_2_v20130308-0410 * add org.eclipse.egit.ui.importer 0.0.1.201505070847 (needed for easymport) * jbosstools-server requests that the new tm.terminal views/connectors be installed along with it, so add org.eclipse.tm.terminal.*, connector.local.feature and org.eclipse.cdt.core.native.feature (JBIDE-17686, JBIDE-19776) * Switch to Mockito 1.9.5.v20131024-0922 (from Locus 1.2.0.Final site) If you haven't tried the latest M7 TP, please do so from this PR: https://github.com/jbosstools/jbosstools-target-platforms/pull/142/ Updated p2diffs: [^jbosstools.p2diff.v20150514.txt] [^jbdevstudio.p2diff.v20150514.txt] > Create and use Mars M7 target-platform > -------------------------------------- > > Key: JBIDE-19776 > URL: https://issues.jboss.org/browse/JBIDE-19776 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: jbdevstudio.p2diff.txt, jbdevstudio.p2diff.v20150514.txt, jbdevstudio.p2diff.v3.txt, jbosstools.p2diff.txt, jbosstools.p2diff.v20150514.txt, jbosstools.p2diff.v3.txt > > > Mars M7 was released and contains interesting changes. > We need to start using it ASAP to leverage new functionalities and adapt to the most important changes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17686: ------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-server/pull/343, https://github.com/jbosstools/jbosstools-target-platforms/pull/142/, https://github.com/jbdevstudio/jbdevstudio-product/pull/308 (was: https://github.com/jbosstools/jbosstools-server/pull/343, https://github.com/jbosstools/jbosstools-target-platforms/pull/142/) > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.0.Beta1 > > Attachments: eclipse-can-has-many-consoles.png, org.jboss.tools.as.management.itests.AS7IntegrationTestSuite.txt > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-17686 at 5/15/15 12:21 AM: -------------------------------------------------------------- I've gotten the TP to play nicely (validation works even though we now include cdt.native.* platform bits) and to get server to compile & install tm.terminal.connector.local.feature (requires cdt.native feature). PRs updated & ready for review: https://github.com/jbosstools/jbosstools-target-platforms/pull/142/ https://github.com/jbosstools/jbosstools-server/pull/343 https://github.com/jbdevstudio/jbdevstudio-product/pull/308 was (Author: nickboldt): I've gotten the TP to play nicely (validation works even though we now include cdt.native.* platform bits) and to get server to compile & install tm.terminal.connector.local.feature (requires cdt.native feature). PRs updated & ready for review: https://github.com/jbosstools/jbosstools-server/pull/343 https://github.com/jbosstools/jbosstools-target-platforms/pull/142/ > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.0.Beta1 > > Attachments: eclipse-can-has-many-consoles.png, org.jboss.tools.as.management.itests.AS7IntegrationTestSuite.txt > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19776) Create and use Mars M7 target-platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19776?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19776: ------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-target-platforms/pull/142, https://github.com/jbosstools/jbosstools-server/pull/343, https://github.com/jbdevstudio/jbdevstudio-product/pull/308 (was: https://github.com/jbosstools/jbosstools-target-platforms/pull/142, https://github.com/jbosstools/jbosstools-server/pull/343) > Create and use Mars M7 target-platform > -------------------------------------- > > Key: JBIDE-19776 > URL: https://issues.jboss.org/browse/JBIDE-19776 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: jbdevstudio.p2diff.txt, jbdevstudio.p2diff.v20150514.txt, jbdevstudio.p2diff.v3.txt, jbosstools.p2diff.txt, jbosstools.p2diff.v20150514.txt, jbosstools.p2diff.v3.txt > > > Mars M7 was released and contains interesting changes. > We need to start using it ASAP to leverage new functionalities and adapt to the most important changes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19800) use maven to generate zip and jar md5/sha1 digests at build time instead of when publishing

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19800?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19800: ------------------------------------ I am going to assume that Max's cryptic response to my PR on Skype constitutes a +1. {quote} [3:32:23 PM] Nick Boldt: https://issues.jboss.org/browse/JBIDE-19800 has a PR I think you'll like :D [3:33:34 PM] Max Andersen: hey jbide-19800 ;) {quote} PR for JBT merged; here's one for JBDS: https://github.com/jbdevstudio/jbdevstudio-product/pull/307 > use maven to generate zip and jar md5/sha1 digests at build time instead of when publishing > ------------------------------------------------------------------------------------------- > > Key: JBIDE-19800 > URL: https://issues.jboss.org/browse/JBIDE-19800 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > [~maxandersen] said: {quote} > That we even have bash code for creating md5sum when maven supports it natively is for me the weird part (http://nicoulaj.github.io/checksum-maven-plugin/index.html) > {quote} -- JBIDE-13835 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19813) Optimize incremental rebuild of CDI model

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19813?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19813: ----------------------------------- Sprint: Sprint #3 May 2015 > Optimize incremental rebuild of CDI model > ----------------------------------------- > > Key: JBIDE-19813 > URL: https://issues.jboss.org/browse/JBIDE-19813 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdi > Affects Versions: 4.3.0.Alpha2 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > > One of very common cases is when user modifies java code in editor and saves it. Java and CDI dependencies between classes make it generally a hard problem to do incremental rebuild, but if imports and super types are not changed, we do not need to reset all references to Java model objects in all CDI model objects, as it is done now 'to be on the safe side'. Request to JDT are time consuming and we can gain a lot if only changed CDI model objects reset references. > It is not safe to try this optimization when imports or super types are changed, but they happen not so often as many minor changes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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