[JBoss JIRA] (TOOLSDOC-650) Add Android SDK installation info into the Community docs
by Supriya Bharadwaj (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-650?page=com.atlassian.jira.plug... ]
Supriya Bharadwaj commented on TOOLSDOC-650:
--------------------------------------------
[~mhusnain], I agree with you on this approach. It would be great if you could help me, if the need be, in understanding how to do this the first time around. I have worked in Git just once so I am not very sure how to go about with this. Is this doable?
> Add Android SDK installation info into the Community docs
> ---------------------------------------------------------
>
> Key: TOOLSDOC-650
> URL: https://issues.jboss.org/browse/TOOLSDOC-650
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Sub-task
> Components: General documentation issues
> Reporter: Supriya Bharadwaj
> Assignee: Misha Ali
> Priority: Minor
> Fix For: 4.2.3.Final
>
> Attachments: fh_android_preferences.png, fh_import_install_android_sdk.adoc, first_hybrid_app_android_preferences.png, first_hybrid_app_install_android_sdk.adoc
>
>
> Please add the info in the community versions of the documents
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19848) Include Eclipse Docker Tooling in the Target Platforms
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19848?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19848:
---------------------------------------------
agreed categories are fine for now.
> Include Eclipse Docker Tooling in the Target Platforms
> ------------------------------------------------------
>
> Key: JBIDE-19848
> URL: https://issues.jboss.org/browse/JBIDE-19848
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: docker, target-platform
> Affects Versions: 4.3.0.Alpha2
> Reporter: Xavier Coulon
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta1
>
>
> *Reason:* Include Eclipse Docker Tooling in JBoss Tools and Dev Studio
> *Project page/sources:* http://eclipse.org/linuxtools
> *Version:* 4.0.0
> *License and owner:* EPL
> *Original p2 repo:* http://download.eclipse.org/linuxtools/updates-docker-nightly/
> *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/docker/1.0.0.20... (from https://github.com/jbosstools/jbosstools-download.jboss.org/pull/526 )
> *Include Sources:* Yes
> *Affected projects:* Docker tooling should be installable from JBoss Tools update site and should be part of DevStudio
> *Include in JBDS:* Yes
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> see https://github.com/jbosstools/jbosstools-target-platforms/pull/149
> mistria@mistria-laptop:~/git/jbosstools-target-platforms/jbosstools/multiple$ ~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64/p2diff http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... file:$(pwd)/target/jbosstools-multiple.target.repo
> > com.fasterxml.jackson.jaxrs.jackson-jaxrs-base [2.5.0.v201504171603]
> > javassist [3.13.0.GA_v201209210905]
> > com.fasterxml.jackson.core.jackson-databind [2.5.0.v201504151636]
> > org.glassfish.hk2.osgi-resource-locator [2.3.0.b10_201505192201]
> > org.eclipse.linuxtools.docker.feature.feature.jar [1.0.0.201506030402]
> > org.objectweb.asm [4.0.0.v201302062210]
> > org.glassfish.jersey.core.jersey-common [2.14.0.v201504171603]
> > org.bouncycastle.bcpkix [1.51.0.v201505131810]
> > org.eclipse.linuxtools.docker.feature.feature.group [1.0.0.201506030402]
> > org.glassfish.hk2.locator [2.3.0.b10_201505192201]
> > jnr.ffi [2.0.1.v201505052040]
> > jnr.x86asm [1.0.2.v201505052040]
> > com.kenai.jffi [1.2.7.v201505052040]
> > com.spotify.docker.client [2.7.18.v201505131810]
> > jnr.constants [0.8.6.v201505052040]
> > org.glassfish.jersey.bundles.repackaged.jersey-guava [2.14.0.v201504151636]
> > org.eclipse.linuxtools.docker.docs [1.0.0.201506030402]
> > com.fasterxml.jackson.datatype.jackson-datatype-guava [2.5.0.v201504151636]
> > org.eclipse.linuxtools.docker.core [1.0.0.201506030402]
> > org.glassfish.hk2.utils [2.3.0.b10_201505192201]
> > com.fasterxml.jackson.core.jackson-annotations [2.5.0.v201504151636]
> > org.bouncycastle.bcprov [1.51.0.v201505131810]
> > com.fasterxml.jackson.jaxrs.jackson-jaxrs-json-provider [2.5.0.v201504171603]
> > jnr.posix [3.0.9.v201505052040]
> > org.glassfish.hk2.api [2.3.0.b10_201505192201]
> > org.glassfish.jersey.apache.connector [2.14.0.v201504171603]
> > com.fasterxml.jackson.core.jackson-core [2.5.0.v201504151636]
> > javax.ws.rs [2.0.1.v201504171603]
> > org.glassfish.jersey.core.jersey-client [2.14.0.v201504211925]
> > org.eclipse.linuxtools.docker.ui [1.0.0.201506030402]
> > jnr.enxio [0.6.0.v201505052040]
> > org.aopalliance [1.0.0.v201105210816]
> > jnr.unixsocket [0.5.0.v201505052040]
> > org.glassfish.jersey.media.jersey-media-json-jackson [2.14.0.v201504171603]
> === Summary ===
> file:/home/mistria/git/jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo contains 34 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19463) Cannot connect to remote server in JMX Navigator
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19463:
-------------------------------------
> That is how jmx supported it in the past afaik ?
Old JMX tools from Mesnil (or previous, history uncertain) never allowed adding any jars to the classpath at all.
> Why not just provide option to add these jars ?
I suppose I could add more widgets to the server editor, but past discussions always indicated it was already too cluttered. There's really no other place one *could* put it, since the detail would need to be stored in the IServer object (since there's no runtime).
So if you think this is a valuable addition and is worth adding more server editor widgets, I'd be glad to "make it so".
> Cannot connect to remote server in JMX Navigator
> ------------------------------------------------
>
> Key: JBIDE-19463
> URL: https://issues.jboss.org/browse/JBIDE-19463
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.2.3.CR1, 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
>
> When you start a remote EAP 6.3 server with management enabled and set up and then want to connect in JMX Navigator, it does not work - double clicking the connection will not do anything and when you right-click, there is no Connect item.
> For local servers this works fine - there is a Connect item when you right-click the server in JMX Navigator.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19463) Cannot connect to remote server in JMX Navigator
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19463:
---------------------------------------------
I do not see how this *requires* bundling more jars. That is only needed if you want it to work "Automagically" (Which would be great but as you say it is alot of extra jars).
Why not just provide option to add these jars ?
That is how jmx supported it in the past afaik ?
> Cannot connect to remote server in JMX Navigator
> ------------------------------------------------
>
> Key: JBIDE-19463
> URL: https://issues.jboss.org/browse/JBIDE-19463
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.2.3.CR1, 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
>
> When you start a remote EAP 6.3 server with management enabled and set up and then want to connect in JMX Navigator, it does not work - double clicking the connection will not do anything and when you right-click, there is no Connect item.
> For local servers this works fine - there is a Connect item when you right-click the server in JMX Navigator.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19795) Bower support
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19795?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19795:
---------------------------------------------
Have a preference for the location of node.
If preference is blank/empty, lookup bower in path, if it has a value use that instead.
If either of these fails show error message explaining to user he need to set this property or make node available in the path that eclipse is running with.
> Bower support
> -------------
>
> Key: JBIDE-19795
> URL: https://issues.jboss.org/browse/JBIDE-19795
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: javascript
> 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
[JBoss JIRA] (JBDS-3018) Install screen moves to bottom left corner of the screen
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3018?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3018:
-------------------------------------------
Ah! that explains it. good to know.
> Install screen moves to bottom left corner of the screen
> --------------------------------------------------------
>
> Key: JBDS-3018
> URL: https://issues.jboss.org/browse/JBDS-3018
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer, upstream
> Affects Versions: 7.1.1.GA
> Environment: java version "1.8.0"
> Java(TM) SE Runtime Environment (build 1.8.0-b132)
> Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode)
> OSX 10.9.2
> One monitor
> No additional software for windows management
> Reporter: Arun Gupta
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 8.x, 9.0.x
>
> Attachments: Screen Shot 2014-04-21 at 9.07.53 PM.png
>
>
> I started the install as
> java -jar ~/Downloads/jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar
> Install screen (step 1 of 9) popped up in the middle and then right away went in the bottom left corner of the screen as shown in attachment.
> This does not seem right.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19945) org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite failures
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19945?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19945:
---------------------------------------------
they seem to run fine for me as long as I have the jbosstools.test.jre.5 property set as (now) documented at https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/how_...
> org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite failures
> ---------------------------------------------------------------------------
>
> Key: JBIDE-19945
> URL: https://issues.jboss.org/browse/JBIDE-19945
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Reporter: Daniel Azarov
> Fix For: 4.3.0.Beta1
>
>
> {code}
> -------------------------------------------------------------------------------
> Test set: org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
> -------------------------------------------------------------------------------
> Tests run: 7, Failures: 4, Errors: 1, Skipped: 0, Time elapsed: 22.278 sec <<< FAILURE! - in org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
> testDeployResult(org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest) Time elapsed: 0.002 sec <<< FAILURE!
> junit.framework.AssertionFailedError: The JRE5 location is not right
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.ws.creation.core.test.command.AbstractJBossWSGenerationTest.setUp(AbstractJBossWSGenerationTest.java:69)
> at org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.setUp(JBossWSTopDownCommandTest.java:59)
> testDeployResult(org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest) Time elapsed: 0.508 sec <<< ERROR!
> java.lang.NullPointerException: null
> at org.eclipse.jdt.launching.AbstractVMInstall.setName(AbstractVMInstall.java:120)
> at org.jboss.tools.as.test.core.internal.utils.JREUtils.createJRE(JREUtils.java:104)
> at org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.setUp(JBossWSJavaFirstCommandTest.java:64)
> testInitialClientCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 0 sec <<< FAILURE!
> junit.framework.AssertionFailedError: The JRE5 location is not right
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.ws.creation.core.test.command.AbstractJBossWSGenerationTest.setUp(AbstractJBossWSGenerationTest.java:69)
> at org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.setUp(JBossWSClientCommandTest.java:48)
> testClientCodeGenerationCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 0.001 sec <<< FAILURE!
> junit.framework.AssertionFailedError: The JRE5 location is not right
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.ws.creation.core.test.command.AbstractJBossWSGenerationTest.setUp(AbstractJBossWSGenerationTest.java:69)
> at org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.setUp(JBossWSClientCommandTest.java:48)
> testRemoveClientJarsCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 0 sec <<< FAILURE!
> junit.framework.AssertionFailedError: The JRE5 location is not right
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.ws.creation.core.test.command.AbstractJBossWSGenerationTest.setUp(AbstractJBossWSGenerationTest.java:69)
> at org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.setUp(JBossWSClientCommandTest.java:48)
> testMergeWebXMLCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSMergeWebXMLCommandTest) Time elapsed: 16.904 sec
> testJBIDE6175(org.jboss.tools.ws.creation.core.test.command.JBossWSClientSampleCreationCommandTest) Time elapsed: 4.789 sec
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19945) org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite failures
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19945?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen resolved JBIDE-19945.
-----------------------------------------
Resolution: Cannot Reproduce Bug
> org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite failures
> ---------------------------------------------------------------------------
>
> Key: JBIDE-19945
> URL: https://issues.jboss.org/browse/JBIDE-19945
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Reporter: Daniel Azarov
> Fix For: 4.3.0.Beta1
>
>
> {code}
> -------------------------------------------------------------------------------
> Test set: org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
> -------------------------------------------------------------------------------
> Tests run: 7, Failures: 4, Errors: 1, Skipped: 0, Time elapsed: 22.278 sec <<< FAILURE! - in org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
> testDeployResult(org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest) Time elapsed: 0.002 sec <<< FAILURE!
> junit.framework.AssertionFailedError: The JRE5 location is not right
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.ws.creation.core.test.command.AbstractJBossWSGenerationTest.setUp(AbstractJBossWSGenerationTest.java:69)
> at org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.setUp(JBossWSTopDownCommandTest.java:59)
> testDeployResult(org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest) Time elapsed: 0.508 sec <<< ERROR!
> java.lang.NullPointerException: null
> at org.eclipse.jdt.launching.AbstractVMInstall.setName(AbstractVMInstall.java:120)
> at org.jboss.tools.as.test.core.internal.utils.JREUtils.createJRE(JREUtils.java:104)
> at org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.setUp(JBossWSJavaFirstCommandTest.java:64)
> testInitialClientCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 0 sec <<< FAILURE!
> junit.framework.AssertionFailedError: The JRE5 location is not right
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.ws.creation.core.test.command.AbstractJBossWSGenerationTest.setUp(AbstractJBossWSGenerationTest.java:69)
> at org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.setUp(JBossWSClientCommandTest.java:48)
> testClientCodeGenerationCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 0.001 sec <<< FAILURE!
> junit.framework.AssertionFailedError: The JRE5 location is not right
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.ws.creation.core.test.command.AbstractJBossWSGenerationTest.setUp(AbstractJBossWSGenerationTest.java:69)
> at org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.setUp(JBossWSClientCommandTest.java:48)
> testRemoveClientJarsCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 0 sec <<< FAILURE!
> junit.framework.AssertionFailedError: The JRE5 location is not right
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.ws.creation.core.test.command.AbstractJBossWSGenerationTest.setUp(AbstractJBossWSGenerationTest.java:69)
> at org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.setUp(JBossWSClientCommandTest.java:48)
> testMergeWebXMLCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSMergeWebXMLCommandTest) Time elapsed: 16.904 sec
> testJBIDE6175(org.jboss.tools.ws.creation.core.test.command.JBossWSClientSampleCreationCommandTest) Time elapsed: 4.789 sec
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months