[JBoss JIRA] (JBIDE-19801) Why is skipTestOrITest only defined for jbosstools-server/as/itests, but not wtp/itests/ ?
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19801?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19801:
---------------------------------------------
I suggest just start by adding this small piece of into to testing.adoc.
> Why is skipTestOrITest only defined for jbosstools-server/as/itests, but not wtp/itests/ ?
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-19801
> URL: https://issues.jboss.org/browse/JBIDE-19801
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
>
> 3 questions:
> a) why is the variable skipTestOrITest, and not skipTestsOrITests ?
> b) why isn't it defined in your root pom such that it can be reused in other itests/ folders? I see skipITests being used in as/itests/ and wtp/itests/ but only as/itests is resolving the skipTestOrITest flag.
> c) was there a JIRA to push this into the parent pom, too?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[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], we had a talk with Gorkem about this environmental issue on califonication.
Basically, I have already make a prototype that works. The idea is the following: we need two preferences: *Node location* & *Bower location* (firstly we will try to find them on the system and if we will fail to do it - tell user to define them in preferences). Then we will run *node* as external process and tell it to execute bower script file with an appropriate command (for now *update*). Doing things this way we are not depending on base environment setup. Seems to be the neatest approach.
> 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-3452) Certify JBDS 9.0 with Supported EAP Releases
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3452?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-3452:
-------------------------------------
[~ldimaggio], what is this JIRA about? We have been testing JBDS with different versions of EAP for many years now - we never stopped. So does certified mean tested in this sense? Or is this about something more than that?
Yes, I looked at the linked EAP7 jira, but I still don't understand what this JBDS means.
> Certify JBDS 9.0 with Supported EAP Releases
> --------------------------------------------
>
> Key: JBDS-3452
> URL: https://issues.jboss.org/browse/JBDS-3452
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: runtime
> Affects Versions: 9.0.0.Beta1
> Reporter: Len DiMaggio
> Assignee: Martin Malina
> Fix For: 9.0.0.Beta1
>
>
> See: EAP7-194
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (TOOLSDOC-650) Add Android SDK installation info into the Community docs
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-650?page=com.atlassian.jira.plug... ]
Misha Ali commented on TOOLSDOC-650:
------------------------------------
Sure. If you can log in early-ish on Tuesday, I can walk you through it.
> 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-19641) Big war deployment via management API gets stuck
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on JBIDE-19641:
------------------------------------------
If you see anything in the IDE code that I should add to that simple test method, please let me know. The DeploymentPlanBuilder call in my comment above didn't include "andDeploy()" because it wasn't necessary to do the upload part, but just in case that was relevant I added it. Still worked.
> Big war deployment via management API gets stuck
> ------------------------------------------------
>
> Key: JBIDE-19641
> URL: https://issues.jboss.org/browse/JBIDE-19641
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta2
>
> Attachments: stuck-deploy-eap-jstack-osx.log, stuck-deploy-eap-jstack-rhel.log, stuck-deploy-jstack-osx.log, stuck-deploy-jstack-rhel.log
>
>
> When you try to deploy some really big war (~500 MB) to EAP 6.3 via management api, it will not go through.
> This is a follow-up of JBIDE-19350 which previously reported this, but Rob eventually used that JIRA to fix a side issue - the stuck operation could not be canceled.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19926) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Webservices]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19926?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-19926:
---------------------------------------
thanks for the branching, [~maxandersen].
> For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Webservices]
> ---------------------------------------------------------
>
> Key: JBIDE-19926
> URL: https://issues.jboss.org/browse/JBIDE-19926
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: webservices
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Beta1
>
>
> For JBIDE 4.3.0.Beta1 [Webservices]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 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 from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
> or
> mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Beta1x
> git push origin jbosstools-4.3.0.Beta1x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and
> * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran
> 7. Close (do not resolve) this JIRA when done.
> 8. 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 Webservices 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, 10 months
[JBoss JIRA] (JBIDE-19641) Big war deployment via management API gets stuck
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19641:
---------------------------------------
[~brian.stansberry], I think the closest is EAP 6.1.0 Beta (-redhat-4 at the end of artifacts), but yes, 7.2.0 is close also.
I can reproduce this with any host really - localhost or other - so no need for a remote host. So it seems right now it's still only reproducible from within the IDE :-\
> Big war deployment via management API gets stuck
> ------------------------------------------------
>
> Key: JBIDE-19641
> URL: https://issues.jboss.org/browse/JBIDE-19641
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta2
>
> Attachments: stuck-deploy-eap-jstack-osx.log, stuck-deploy-eap-jstack-rhel.log, stuck-deploy-jstack-osx.log, stuck-deploy-jstack-rhel.log
>
>
> When you try to deploy some really big war (~500 MB) to EAP 6.3 via management api, it will not go through.
> This is a follow-up of JBIDE-19350 which previously reported this, but Rob eventually used that JIRA to fix a side issue - the stuck operation could not be canceled.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19641) Big war deployment via management API gets stuck
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on JBIDE-19641:
------------------------------------------
Progress report:
Adding this into the 7.2.0.Final code (which is quite close to the versions Rob reported), I don't get failures uploading to EAP 6.3. The file I used is 797MB.
I tested using an external IP address, not just localhost, but I'm traveling so I can't test against an actual remote server.
{code}
public class HugeDeploymentTestCase {
private static final String addr = System.getProperty("management.address", "localhost");
@Test
public void test() throws IOException, ExecutionException, InterruptedException {
ModelControllerClient client = ModelControllerClient.Factory.create(addr, 9999);
ServerDeploymentManager manager = ServerDeploymentManager.Factory.create(client);
File f = new File("/home/me/tmp/kitchensink-huge.ear");
Assert.assertTrue(f.exists());
DeploymentPlan plan = manager.newDeploymentPlan().add("kitchensink-huge.ear", f).build();
Future<ServerDeploymentPlanResult> future = manager.execute(plan);
ServerDeploymentPlanResult result = future.get();
}
}
{code}
> Big war deployment via management API gets stuck
> ------------------------------------------------
>
> Key: JBIDE-19641
> URL: https://issues.jboss.org/browse/JBIDE-19641
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta2
>
> Attachments: stuck-deploy-eap-jstack-osx.log, stuck-deploy-eap-jstack-rhel.log, stuck-deploy-jstack-osx.log, stuck-deploy-jstack-rhel.log
>
>
> When you try to deploy some really big war (~500 MB) to EAP 6.3 via management api, it will not go through.
> This is a follow-up of JBIDE-19350 which previously reported this, but Rob eventually used that JIRA to fix a side issue - the stuck operation could not be canceled.
--
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 updated JBIDE-19463:
--------------------------------
Fix Version/s: 4.3.0.Beta2
(was: 4.3.0.Beta1)
> 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.Beta2
>
>
> 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 Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19463:
---------------------------------------
[~rob.stryker], thanks for all the explanations. Now I get that it's probably not feasible to add all the client jars. And I'm not really sure if adding the option for users to add their client jar would help - if they have the jar, they likely have the whole server on the disk, so why not create the runtime and then it works?
So again, I think it would be good to warn users about this somewhere - as I suggested in one of my previous comments.
> 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