[JBoss JIRA] (JBDS-3258) Docker Tooling (Advanced Integration)
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3258?page=com.atlassian.jira.plugin.... ]
Xavier Coulon edited comment on JBDS-3258 at 6/5/15 5:59 AM:
-------------------------------------------------------------
Postponing to 9.0.0.Beta2 since not all request features have been implemented yet.
was (Author: xcoulon):
Postponing to 9.0.0.Beta2 since not all request features have been implemen
> Docker Tooling (Advanced Integration)
> -------------------------------------
>
> Key: JBDS-3258
> URL: https://issues.jboss.org/browse/JBDS-3258
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: docker, requirements
> Reporter: Burr Sutter
> Assignee: Xavier Coulon
> Fix For: 9.0.0.Beta2
>
>
> Once significant delta between the "basic" and advanced scenarios is that here I wish to custom craft my own docker images instead of using an existing one - where my custom crafted image includes my .war or .ear.
> In addition to the basic integrations of pull, run, stop, commit and push
> boot2docker init
> boot2docker up
> boot2docker down
> boot2docker ip
> docker run -d
> docker ps
> docker rm
> docker rmi
> docker build
> End-user steps:
> 0) assumes boot2docker has been dowloaded and installed
> 1) boot2docker init : required to to insure boot2docker-vm is properly initialized
> 2) boot2docker up : starts the VirtualBox boot2docker-vm
> 3) boot2docker ip : returns the IP address - this will be vital when it comes to testing - it would need to be integrated with our Run - As on Docker capability.
> 4) docker run -i -t -p 80:8080 jboss/wildfly -d : the -d means detached, I may need to run N containers simultaneously
> 5) docker ps : allows me to see all my currently running containers
> 6) docker rm : allows me to kill a currently running container
> 7) docker rmi : allows me to remove a local image
> 8) docker build : assumes that I have crafted a Dockerfile - this will create the local image - with my .war or .ear embedded
> 9) docker run : this new created image
> The docker build scenario can be triggered via a Maven plugin
> The docker build scenario can also be triggered via an Eclipse menu option (like a Maven install)
> We need to figure out the file-system layout so that the Dockerfile and the maven project are all nicely checked into git/svn. So that Jenkins can pick up this repository and perform an automated "docker build" (post Maven install) and then run all the appropriate unit, integration and functional tests.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3258) Docker Tooling (Advanced Integration)
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3258?page=com.atlassian.jira.plugin.... ]
Xavier Coulon updated JBDS-3258:
--------------------------------
Fix Version/s: 9.0.0.Beta2
(was: 9.0.0.Beta1)
> Docker Tooling (Advanced Integration)
> -------------------------------------
>
> Key: JBDS-3258
> URL: https://issues.jboss.org/browse/JBDS-3258
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: docker, requirements
> Reporter: Burr Sutter
> Assignee: Xavier Coulon
> Fix For: 9.0.0.Beta2
>
>
> Once significant delta between the "basic" and advanced scenarios is that here I wish to custom craft my own docker images instead of using an existing one - where my custom crafted image includes my .war or .ear.
> In addition to the basic integrations of pull, run, stop, commit and push
> boot2docker init
> boot2docker up
> boot2docker down
> boot2docker ip
> docker run -d
> docker ps
> docker rm
> docker rmi
> docker build
> End-user steps:
> 0) assumes boot2docker has been dowloaded and installed
> 1) boot2docker init : required to to insure boot2docker-vm is properly initialized
> 2) boot2docker up : starts the VirtualBox boot2docker-vm
> 3) boot2docker ip : returns the IP address - this will be vital when it comes to testing - it would need to be integrated with our Run - As on Docker capability.
> 4) docker run -i -t -p 80:8080 jboss/wildfly -d : the -d means detached, I may need to run N containers simultaneously
> 5) docker ps : allows me to see all my currently running containers
> 6) docker rm : allows me to kill a currently running container
> 7) docker rmi : allows me to remove a local image
> 8) docker build : assumes that I have crafted a Dockerfile - this will create the local image - with my .war or .ear embedded
> 9) docker run : this new created image
> The docker build scenario can be triggered via a Maven plugin
> The docker build scenario can also be triggered via an Eclipse menu option (like a Maven install)
> We need to figure out the file-system layout so that the Dockerfile and the maven project are all nicely checked into git/svn. So that Jenkins can pick up this repository and perform an automated "docker build" (post Maven install) and then run all the appropriate unit, integration and functional tests.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-17814) Empty editor is opened instead of Central editor
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17814?page=com.atlassian.jira.plugi... ]
Radim Hopp commented on JBIDE-17814:
------------------------------------
Reproduced with RC2 and JBT nightly (installed today). I've changed priority to minor as it takes some effort (closing&opening few times) to reproduce and this is nothing someone would do normally.
> Empty editor is opened instead of Central editor
> ------------------------------------------------
>
> Key: JBIDE-17814
> URL: https://issues.jboss.org/browse/JBIDE-17814
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.Beta3
> Environment: Fedora 20
> Reporter: Radim Hopp
> Assignee: Radim Hopp
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
> Attachments: central2.ogv
>
>
> I seems to appear only with repetitive closing/opening Central editor.
> Screencast: http://youtu.be/Z_X_Eo76wV8
> I can reproduce this issue even with GTK2.
> There is no error in error log nor in console output.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19946) running webservice test gives errors
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19946?page=com.atlassian.jira.plugi... ]
Xavier Coulon reassigned JBIDE-19946:
-------------------------------------
Assignee: Brian Fitzpatrick
> running webservice test gives errors
> ------------------------------------
>
> Key: JBIDE-19946
> URL: https://issues.jboss.org/browse/JBIDE-19946
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Reporter: Max Rydahl Andersen
> Assignee: Brian Fitzpatrick
>
> running 4.3.0.Beta1x with jdk's defined I get this error:
> {code}
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
> Retrieving document at 'file:/Users/max/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/data/JBossWSTestProject/hello_world.wsdl'.
> null
> null
> Retrieving document at '/Users/max/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/data/JBossWSTestProject/hello_world.wsdl'.
> Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 272.543 sec <<< FAILURE! - in org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
> testDeployResult(org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest) Time elapsed: 82.428 sec
> testDeployResult(org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest) Time elapsed: 127.267 sec <<< FAILURE!
> junit.framework.AssertionFailedError: ***********************
> Create Web Service Client...
> Create Web Service...
> Create Web Service Operation...
> Exception in thread "main" javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
> at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404)
> at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314)
> at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
> at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
> at com.sun.proxy.$Proxy14.sayHello(Unknown Source)
> at org.example.www.helloworld.clientsample.ClientSample.main(ClientSample.java:14)
> Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
> at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:439)
> at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:83)
> at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:171)
> at org.jboss.ws.core.CommonSOAP11Binding.createMessage(CommonSOAP11Binding.java:59)
> at org.jboss.ws.core.CommonSOAPBinding.bindRequestMessage(CommonSOAPBinding.java:158)
> at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:291)
> at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
> ... 4 more
> 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.JBossWSJavaFirstCommandTest.checkText(JBossWSJavaFirstCommandTest.java:163)
> at org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.testDeployResult(JBossWSJavaFirstCommandTest.java:116)
> testInitialClientCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 15.26 sec
> testClientCodeGenerationCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 17.628 sec
> testRemoveClientJarsCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 14.25 sec
> testMergeWebXMLCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSMergeWebXMLCommandTest) Time elapsed: 9.174 sec
> testJBIDE6175(org.jboss.tools.ws.creation.core.test.command.JBossWSClientSampleCreationCommandTest) Time elapsed: 6.416 sec
> Results :
> Failed tests:
> JBossWSJavaFirstCommandTest.testDeployResult:116->checkText:163 ***********************
> Create Web Service Client...
> Create Web Service...
> Create Web Service Operation...
> Exception in thread "main" javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
> at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404)
> at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314)
> at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
> at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
> at com.sun.proxy.$Proxy14.sayHello(Unknown Source)
> at org.example.www.helloworld.clientsample.ClientSample.main(ClientSample.java:14)
> Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
> at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:439)
> at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:83)
> at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:171)
> at org.jboss.ws.core.CommonSOAP11Binding.createMessage(CommonSOAP11Binding.java:59)
> at org.jboss.ws.core.CommonSOAPBinding.bindRequestMessage(CommonSOAPBinding.java:158)
> at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:291)
> at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
> ... 4 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19946) running webservice test gives errors
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-19946:
-------------------------------------------
Summary: running webservice test gives errors
Key: JBIDE-19946
URL: https://issues.jboss.org/browse/JBIDE-19946
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Reporter: Max Rydahl Andersen
running 4.3.0.Beta1x with jdk's defined I get this error:
{code}
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
Retrieving document at 'file:/Users/max/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/data/JBossWSTestProject/hello_world.wsdl'.
null
null
Retrieving document at '/Users/max/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/data/JBossWSTestProject/hello_world.wsdl'.
Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 272.543 sec <<< FAILURE! - in org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
testDeployResult(org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest) Time elapsed: 82.428 sec
testDeployResult(org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest) Time elapsed: 127.267 sec <<< FAILURE!
junit.framework.AssertionFailedError: ***********************
Create Web Service Client...
Create Web Service...
Create Web Service Operation...
Exception in thread "main" javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
at com.sun.proxy.$Proxy14.sayHello(Unknown Source)
at org.example.www.helloworld.clientsample.ClientSample.main(ClientSample.java:14)
Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:439)
at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:83)
at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:171)
at org.jboss.ws.core.CommonSOAP11Binding.createMessage(CommonSOAP11Binding.java:59)
at org.jboss.ws.core.CommonSOAPBinding.bindRequestMessage(CommonSOAPBinding.java:158)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:291)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
... 4 more
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.JBossWSJavaFirstCommandTest.checkText(JBossWSJavaFirstCommandTest.java:163)
at org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.testDeployResult(JBossWSJavaFirstCommandTest.java:116)
testInitialClientCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 15.26 sec
testClientCodeGenerationCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 17.628 sec
testRemoveClientJarsCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 14.25 sec
testMergeWebXMLCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSMergeWebXMLCommandTest) Time elapsed: 9.174 sec
testJBIDE6175(org.jboss.tools.ws.creation.core.test.command.JBossWSClientSampleCreationCommandTest) Time elapsed: 6.416 sec
Results :
Failed tests:
JBossWSJavaFirstCommandTest.testDeployResult:116->checkText:163 ***********************
Create Web Service Client...
Create Web Service...
Create Web Service Operation...
Exception in thread "main" javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
at com.sun.proxy.$Proxy14.sayHello(Unknown Source)
at org.example.www.helloworld.clientsample.ClientSample.main(ClientSample.java:14)
Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:439)
at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:83)
at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:171)
at org.jboss.ws.core.CommonSOAP11Binding.createMessage(CommonSOAP11Binding.java:59)
at org.jboss.ws.core.CommonSOAPBinding.bindRequestMessage(CommonSOAPBinding.java:158)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:291)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
... 4 more
{code}
--
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 Supriya Bharadwaj (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-650?page=com.atlassian.jira.plug... ]
Supriya Bharadwaj commented on TOOLSDOC-650:
--------------------------------------------
Sure, [~mhusnain]. I'll be in early on Tuesday so that we can discuss this.
> 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