Re: [jboss-dev-forums] [JBoss AS 7 Development] - Design of AS7 multi-JSF feature
by Anthony O.
Anthony O. [https://community.jboss.org/people/aogier] commented on the document
"Design of AS7 multi-JSF feature"
To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47689#comment-11789
--------------------------------------------------
OK the https://github.com/jbossas/jboss-as/pull/3390/files multi-JSF feature doesn't handle the new module structure of JBoss 7.2.0.Final (someone should create a new Jira :p )
I've copied all the "1.2" and "main" directory to the modules I've added in a separated modules directory (and added JBOSS_MODULEPATH="$JBOSS_HOME/modules:THE_PATH_TO_MY_OTHER_DIRECTORY" to standalone.conf).
Now it seems to bootstrap correctly.
But now I've got :
13:35:22,563 SEVERE [org.apache.myfaces.webapp.AbstractFacesInitializer] (ServerService Thread Pool -- 67) An error occured while initializing MyFaces: Class org.jboss.as.weld.webtier.jsf.WeldApplicationFactory is no javax.faces.application.ApplicationFactory: java.lang.IllegalArgumentException: Class org.jboss.as.weld.webtier.jsf.WeldApplicationFactory is no javax.faces.application.ApplicationFactory
at javax.faces.FactoryFinder.newFactoryInstance(FactoryFinder.java:354) [myfaces-api-2.1.10.jar:2.1.10] (...)
I've tried the https://community.jboss.org/docs/DOC-47689#comment-11484 workaround of Stan Silvert (by the way, modules/org/jboss/as/weld/main/modules.xml doesn't depend on javax.faces.api in JBoss 7.2.0.Final), but nothing changed, I still have got that stack...
Any idea ?
--------------------------------------------------
13 years, 1 month
Re: [jboss-dev-forums] [JBoss AS 7 Development] - Design of AS7 multi-JSF feature
by Stan Silvert
Stan Silvert [https://community.jboss.org/people/ssilvert] commented on the document
"Design of AS7 multi-JSF feature"
To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47689#comment-11788
--------------------------------------------------
Yes, the sample install scripts are out of date since we changed the module path. Thanks for bringing that to my attention.
You have a couple of options. You can change the value of the web.xml context param to myfaces-2.1.10 or you can change the default impl in the jsf subsystem. Since you've apparently removed the defaault "main" impl and you've only got myfaces installed, you should change the default impl anyway.
/subsystem=jsf/:write-attribute(name=default-jsf-impl-slot,value=myfaces-2.1.10)
Then you don't need to declare org.jboss.jbossfaces.JSF_CONFIG_NAME in your web.xml.
Stan
--------------------------------------------------
13 years, 1 month
Re: [jboss-dev-forums] [JBoss AS 7 Development] - Design of AS7 multi-JSF feature
by Anthony O.
Anthony O. [https://community.jboss.org/people/aogier] commented on the document
"Design of AS7 multi-JSF feature"
To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47689#comment-11787
--------------------------------------------------
I've tried that method with https://github.com/jbossas/jboss-as/tree/7.2.0.Final JBoss 7.2.0.final and MyFaces 2.1.10 and I had to modify the generated files a bit : for org/jboss/as/jsf-injection/myfaces-2.1.10/module.xml , I changed the "<resource-root" to path "../../../../../system/layers/base/org/jboss/as/jsf-injection/main/jboss-as-jsf-injection-7.2.0.Final.jar".
But now, when I try to start my JSF webapp, I have :
11:09:30,528 WARN [org.jboss.as.jsf] (MSC service thread 1-13) JBAS012603: Unknown JSF version 'Mojarra-2.0'. Default version 'main' will be used instead.
11:09:30,529 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-13) MSC00001: Failed to start service jboss.deployment.unit."sinistre-web.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."sinistre-web.war".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "sinistre-web.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Final.jar:7.2.0.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) [rt.jar:1.6.0_27]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.6.0_27]
at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_27]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS012656: Default JSF implementation slot 'main' is invalid
at org.jboss.as.jsf.deployment.JSFDependencyProcessor.deploy(JSFDependencyProcessor.java:79)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Final.jar:7.2.0.Final]
... 5 more
And here is the result for /subsystem=jsf/:list-active-jsf-impls :
{
"outcome" => "success",
"result" => ["myfaces-2.1.10"]
}
... any idea ?
--------------------------------------------------
13 years, 1 month
[jBPM Development] - IllegalStateException Using StatefulKnowledgeSession
by irshad mansuri
irshad mansuri [https://community.jboss.org/people/irs] created the discussion
"IllegalStateException Using StatefulKnowledgeSession"
To view the discussion, visit: https://community.jboss.org/message/803811#803811
--------------------------------------------------------------
Hi i have created a workflow using humantask with database. But when i am deploying the process i am getting this error "*java.lang.IllegalStateException: java.lang.reflect.InvocationTargetException".*
I debugged the java code and found the its not able to create "*StatefulKnowledgeSession". * This is the code which i am implementing.
*
*
@Test
public void processInstancePersistentTest() throws Exception{
KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder();
kbuilder.add(new ClassPathResource("HumanWorkflow.bpmn"), ResourceType.BPMN2);
System.out.println("=== Knowledge Base Called ====");
KnowledgeBase kbase = KnowledgeBaseFactory.newKnowledgeBase();
kbase.addKnowledgePackages(kbuilder.getKnowledgePackages());
Environment env = EnvironmentFactory.newEnvironment();
EntityManagerFactory emf = Persistence.createEntityManagerFactory("org.jbpm.task");
env.set(EnvironmentName.ENTITY_MANAGER_FACTORY, emf);
env.set(EnvironmentName.TRANSACTION_MANAGER, TransactionManagerServices.getTransactionManager());
System.out.println("=== Stateful Knowledge Session Called ====");
final StatefulKnowledgeSession ksession = JPAKnowledgeService.newStatefulKnowledgeSession(kbase, null, env);
int sessionId = ksession.getId();
assertNotNull(sessionId);
assertTrue(sessionId != 0);
System.out.println("=== Human Task Handler Called ====");
@SuppressWarnings("deprecation")
CommandBasedWSHumanTaskHandler taskHandler = new CommandBasedWSHumanTaskHandler(ksession);
ksession.getWorkItemManager().registerWorkItemHandler("Human Task", taskHandler);
ProcessInstance processInstance = ksession.createProcessInstance("com.sample.hello", null);
System.out.println(">>> Let's Start the Process Instance");
long processInstanceOne = processInstance.getId();
ksession.startProcessInstance(processInstanceOne);
ksession.dispose();
}
and this is the error which i am getting on debugging the code.
java.lang.IllegalStateException: java.lang.reflect.InvocationTargetException
at org.drools.persistence.jpa.KnowledgeStoreServiceImpl.buildCommandService(KnowledgeStoreServiceImpl.java:142)
at org.drools.persistence.jpa.KnowledgeStoreServiceImpl.newStatefulKnowledgeSession(KnowledgeStoreServiceImpl.java:66)
at org.drools.persistence.jpa.JPAKnowledgeService.newStatefulKnowledgeSession(JPAKnowledgeService.java:122)
at com.sample.HelloProcesTest.processInstancePersistentTest(HelloProcesTest.java:58)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.jbpm.test.KnowledgeSessionCleanup$1.evaluate(KnowledgeSessionCleanup.java:28)
at org.junit.rules.TestWatchman$1.evaluate(TestWatchman.java:48)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.drools.persistence.jpa.KnowledgeStoreServiceImpl.buildCommandService(KnowledgeStoreServiceImpl.java:128)
... 29 more
Caused by: java.lang.NullPointerException
at org.drools.persistence.SingleSessionCommandService.<init>(SingleSessionCommandService.java:168)
... 34 more
Let me know if i am missing out something.
Thanks
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/803811#803811]
Start a new discussion in jBPM Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 1 month
[jBPM Development] - jBPM process and instance management Android Client
by samo42
samo42 [https://community.jboss.org/people/samo42] created the discussion
"jBPM process and instance management Android Client"
To view the discussion, visit: https://community.jboss.org/message/803704#803704
--------------------------------------------------------------
Hi all!
It was a long (very long) and difficult (I had to elarn everything from beginning) journey but finaly, I did it!
My first android application is alive!
And now it's your turn to test it and recommend what to improve (not just technical but also language mistakes!).
I tried this app on 4 different emulators (tablet, big screen smartphone, 2 small screen smartphones) and with com.sample.evaluation. But I need real devices and real users.
So if this app do something wrong, please tell me what were you doing (refreshing, starting instance, by which process).
Here are some things I want to add later:
1. display flipping
2. diagram zoom in and out.
3. in list of instances show instance id as big text and proess id as small (I forgot about it and I don't want to export and sign .apk again with just this change)
4. optimize the s**t out of it.
*Here is the .apk file* (and also in attachment)
https://dl.dropbox.com/u/24366262/MainActivity.apk https://dl.dropbox.com/u/24366262/MainActivity.apk
Just comment below if you want source code, I can post it on GitHub or somewhere.
https://community.jboss.org/servlet/JiveServlet/showImage/2-803704-20465/... https://community.jboss.org/servlet/JiveServlet/downloadImage/2-803704-20...
screen 1: log in. first, you have to set up server (menu->set up server), then, you can log in.
https://community.jboss.org/servlet/JiveServlet/showImage/2-803704-20466/... https://community.jboss.org/servlet/JiveServlet/downloadImage/2-803704-20...
screen 2: list of processes (well, process in this case), with opened Menu. Clicking on one cause screen 3.
https://community.jboss.org/servlet/JiveServlet/showImage/2-803704-20467/... https://community.jboss.org/servlet/JiveServlet/downloadImage/2-803704-20...
screen 3: list of instances. You see them. (3.1). By longclicking them, you can do things to them (3.2). By clicking Meny you can start new (3.3). Clicking on one cause screen 4.
https://community.jboss.org/servlet/JiveServlet/showImage/2-803704-20468/... https://community.jboss.org/servlet/JiveServlet/downloadImage/2-803704-20...
screen 4: diagram. With green things by active nodes. Don't let the -/+ thing on the bottom distract you. It doesn't work.
Questions?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/803704#803704]
Start a new discussion in jBPM Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 1 month
[JBoss Tools Development] - Remote Debugging for Eclipse Test Plug-in Running by Tycho
by Rob Stryker
Rob Stryker [https://community.jboss.org/people/rob.stryker] modified the document:
"Remote Debugging for Eclipse Test Plug-in Running by Tycho"
To view the document, visit: https://community.jboss.org/docs/DOC-15209
--------------------------------------------------------------
When I report issue in bug tracking system about nightly build's JUnit test error I usually get simple answer that it is supposed to be working because it is working on developer's workstation. After that routine conversation starts and it turns out that tests were running from development environment under Eclipse. Here I usually have to explain again and again that's not the same running tests from development environment and in build.
The right way to make yourself sure your tests will work in most cases without errors in nightly build is to start tests the same way as nightly build does. It was not easy for JBoss Tools tests until we created experimental branch and switched to Maven Tycho project. That means it is fairly easy to run tests now. Basically you need to change current directory and execute maven install goal. If it runs in development environment and in maven your tests are good and in most cases it should be fine in nightly build. Problems begin if it runs in development environment but it doesn't in maven. In this scenario you need to debug tests running in Tycho somehow and fix it. Fortunately it can be done using Java remote debugging support.
First of all you need to be sure you have built your sources you're going to debug and there is no differences between .java and .class files. If you're going find problem from previous build just get right tagged version and build it before debugging session.
There are two options to use remote debugger
1. Simple use of *-DdebugPort=8001* or what ever port you would like to use
2. Add full argLine for remote debugging configuration im pom.xml
h1. Use debugPort system property (Recommended)
To use this just add *-DdebugPort=<portNumber>* to your maven command line replacing <portNumber> for desired port and make sure you have the same port configured in your Remote Java Application configuration in Eclipse Debug Configuration dialog as it explained for second option below.
h1. Or use Full argLine for Remote Debugging Configuration in pom.xml (Deprecated)
Open pom.xml for your Eclipse Test Plug-in and add Java VM arguments like it shown below (actual port numbers, server names and other parameters may be different, it depends from your environment)
<build>
<plugins>
<plugin>
<groupid>org.sonatype.tycho</groupid>
<artifactid>maven-osgi-test-plugin</artifactid>
<version>${tycho-version}</version>
<configuration>
<argLine>-Xdebug -Xrunjdwp:transport=dt_socket,address=8001,server=y,suspend=y</argLine>
</configuration>
</plugin>
</plugins>
</build>
This snipped configured for remote debugging in OpenJDK 6, if your is different you might need to read #r1 [1] and configure it right for your JVM version.
Configure java projects with sources you're going to debug in Eclipse and create Remote Java Application configuration in Eclipse Debug Configuration dialog. Fill 'host' and 'port' fields with the same values from pom.xml argLine element. Press Apply button to save your changes and start your test plug-in from terminal like
$mvn install
It will go through build process and finally you ll see something like
[INFO] Expected eclipse log file: /home/eskimo/Projects/jbt-modular/jst/tests/org.jboss.tools.jst.web.kb.test/target/work/data/.metadata/.log
[INFO] Command line:
/bin/sh -c cd /home/eskimo/Projects/jbt-modular/jst/tests/org.jboss.tools.jst.web.kb.test && /usr/lib/jvm/java-6-openjdk/jre/bin/java -Dosgi.noShutdown=false -Dosgi.os=linux -Dosgi.ws=gtk -Dosgi.arch=x86 -agentlib:jdwp=transport=dt_socket,address=8001,server=y,suspend=y -jar /home/eskimo/.m2/repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.0.201.R35x_v20090715/org.eclipse.equinox.launcher-1.0.201.R35x_v20090715.jar -data /home/eskimo/Projects/jbt-modular/jst/tests/org.jboss.tools.jst.web.kb.test/target/work/data -dev file:/home/eskimo/Projects/jbt-modular/jst/tests/org.jboss.tools.jst.web.kb.test/target/dev.properties -install /home/eskimo/Projects/jbt-modular/jst/tests/org.jboss.tools.jst.web.kb.test/target/work -configuration /home/eskimo/Projects/jbt-modular/jst/tests/org.jboss.tools.jst.web.kb.test/target/work/configuration -application org.codehaus.tycho.surefire.osgibooter.uitest -testproperties /home/eskimo/Projects/jbt-modular/jst/tests/org.jboss.tools.jst.web.kb.test/target/surefire.properties
Listening for transport dt_socket at address: 8001
At this point build is waiting for you to attach remote debugger to the process because of using
suspend=y
in argLine element of your pom.xml file. So you need to return to eclipse and hit 'Debug' button in dialog opened before.
Build will continue at this point and stop on your break points so you can find out what is wrong with tests during nightly build.
[1] http://java.sun.com/javase/technologies/core/toolsapis/jpda/#Invocation Java Platform Debugger Architecture - http://java.sun.com/javase/technologies/core/toolsapis/jpda/#Invocation
h1. Words of Warning
When building and debugging your code locally, be aware that your eclipse environment or target platform inside the running eclipse should match the environment used to launch your tests. When running locally via the *mvn clean verify* command, tycho will default to using a MINIMUM configuration for both building AND testing your code. To ensure the code is compiled, and tests are launched, against a SPECIFIC target platform, make sure to use the *-Pminimum or * *-Pmaximum* flags in your build command.
When debugging from within eclipse, if your current environment does NOT match the environment tycho uses to launch your tests, you may experience many types of confusing behavior. The most obvious will be if the source code lines do not match up to what is being executed, but other problems such as inaccessible or unhit breakpoints, or illogical code flows, may confuse you for a very long time. If you are running your tests with a *-Pminimum* flag, ensure your eclipse is set up to use that configuration. Similarly, If you are running your tests with a *-Pmaximum* flag, make sure you are using an environment which matches that target platform.
This will save you many hours ;)
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-15209]
Create a new document in JBoss Tools Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
13 years, 1 month
[JBoss Tools Development] - Remote Debugging for Eclipse Test Plug-in Running by Tycho
by Mickael Istria
Mickael Istria [https://community.jboss.org/people/mickael_istria] modified the document:
"Remote Debugging for Eclipse Test Plug-in Running by Tycho"
To view the document, visit: https://community.jboss.org/docs/DOC-15209
--------------------------------------------------------------
When I report issue in bug tracking system about nightly build's JUnit test error I usually get simple answer that it is supposed to be working because it is working on developer's workstation. After that routine conversation starts and it turns out that tests were running from development environment under Eclipse. Here I usually have to explain again and again that's not the same running tests from development environment and in build.
The right way to make yourself sure your tests will work in most cases without errors in nightly build is to start tests the same way as nightly build does. It was not easy for JBoss Tools tests until we created experimental branch and switched to Maven Tycho project. That means it is fairly easy to run tests now. Basically you need to change current directory and execute maven install goal. If it runs in development environment and in maven your tests are good and in most cases it should be fine in nightly build. Problems begin if it runs in development environment but it doesn't in maven. In this scenario you need to debug tests running in Tycho somehow and fix it. Fortunately it can be done using Java remote debugging support.
First of all you need to be sure you have built your sources you're going to debug and there is no differences between .java and .class files. If you're going find problem from previous build just get right tagged version and build it before debugging session.
There are two options to use remote debugger
1. Simple use of *-DdebugPort=8001* or what ever port you would like to use
2. Add full argLine for remote debugging configuration im pom.xml
h1. Use debugPort system property (Recommended)
To use this just add *-DdebugPort=<portNumber>* to your maven command line replacing <portNumber> for desired port and make sure you have the same port configured in your Remote Java Application configuration in Eclipse Debug Configuration dialog as it explained for second option below.
h1. Or use Full argLine for Remote Debugging Configuration in pom.xml (Deprecated)
Open pom.xml for your Eclipse Test Plug-in and add Java VM arguments like it shown below (actual port numbers, server names and other parameters may be different, it depends from your environment)
<build>
<plugins>
<plugin>
<groupid>org.sonatype.tycho</groupid>
<artifactid>maven-osgi-test-plugin</artifactid>
<version>${tycho-version}</version>
<configuration>
<argLine>-Xdebug -Xrunjdwp:transport=dt_socket,address=8001,server=y,suspend=y</argLine>
</configuration>
</plugin>
</plugins>
</build>
This snipped configured for remote debugging in OpenJDK 6, if your is different you might need to read #r1 [1] and configure it right for your JVM version.
Configure java projects with sources you're going to debug in Eclipse and create Remote Java Application configuration in Eclipse Debug Configuration dialog. Fill 'host' and 'port' fields with the same values from pom.xml argLine element. Press Apply button to save your changes and start your test plug-in from terminal like
$mvn install
It will go through build process and finally you ll see something like
[INFO] Expected eclipse log file: /home/eskimo/Projects/jbt-modular/jst/tests/org.jboss.tools.jst.web.kb.test/target/work/data/.metadata/.log
[INFO] Command line:
/bin/sh -c cd /home/eskimo/Projects/jbt-modular/jst/tests/org.jboss.tools.jst.web.kb.test && /usr/lib/jvm/java-6-openjdk/jre/bin/java -Dosgi.noShutdown=false -Dosgi.os=linux -Dosgi.ws=gtk -Dosgi.arch=x86 -agentlib:jdwp=transport=dt_socket,address=8001,server=y,suspend=y -jar /home/eskimo/.m2/repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.0.201.R35x_v20090715/org.eclipse.equinox.launcher-1.0.201.R35x_v20090715.jar -data /home/eskimo/Projects/jbt-modular/jst/tests/org.jboss.tools.jst.web.kb.test/target/work/data -dev file:/home/eskimo/Projects/jbt-modular/jst/tests/org.jboss.tools.jst.web.kb.test/target/dev.properties -install /home/eskimo/Projects/jbt-modular/jst/tests/org.jboss.tools.jst.web.kb.test/target/work -configuration /home/eskimo/Projects/jbt-modular/jst/tests/org.jboss.tools.jst.web.kb.test/target/work/configuration -application org.codehaus.tycho.surefire.osgibooter.uitest -testproperties /home/eskimo/Projects/jbt-modular/jst/tests/org.jboss.tools.jst.web.kb.test/target/surefire.properties
Listening for transport dt_socket at address: 8001
At this point build is waiting for you to attach remote debugger to the process because of using
suspend=y
in argLine element of your pom.xml file. So you need to return to eclipse and hit 'Debug' button in dialog opened before.
Build will continue at this point and stop on your break points so you can find out what is wrong with tests during nightly build.
[1] http://java.sun.com/javase/technologies/core/toolsapis/jpda/#Invocation Java Platform Debugger Architecture - http://java.sun.com/javase/technologies/core/toolsapis/jpda/#Invocation
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-15209]
Create a new document in JBoss Tools Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
13 years, 1 month
