[JBoss JIRA] Created: (JBDS-1322) jbpm4 feature and two versions of jbpm-convert plugin/feature in latest JBDS 4 build
by Nick Boldt (JIRA)
jbpm4 feature and two versions of jbpm-convert plugin/feature in latest JBDS 4 build
------------------------------------------------------------------------------------
Key: JBDS-1322
URL: https://jira.jboss.org/browse/JBDS-1322
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Build
Affects Versions: 4.0.0.M2
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Here's what's in the latest 4.0M2 build:
[10:51:07]nboldt@x2lappy:~/jbdevstudio-4.0.0.v201009142310R-H472-M2-eap
$ find . -maxdepth 4 -name "*jbpm*" |sort
./jboss-eap/seam/lib/jbpm-jpdl.jar
./studio/eclipse/features/org.jboss.tools.jbpm3.feature_3.2.0.v20100908-1606-H23-M2
./studio/eclipse/features/org.jboss.tools.jbpm4.feature_4.0.0.v20100908-1606-H23-M2
./studio/eclipse/features/org.jboss.tools.jbpm.common.feature_4.4.0.v20100908-1606-H23-M2
./studio/eclipse/features/org.jboss.tools.jbpm.convert.feature_1.0.0.v20100908-1606-H23-M2
./studio/eclipse/features/org.jboss.tools.jbpm.convert.feature_1.2.0.v201009142310R-H472-M2
./studio/eclipse/features/org.jbpm.gd.jpdl.feature_3.2.0.v20100908-1606-H23-M2
./studio/eclipse/plugins/org.jboss.tools.jbpm.common_4.4.0.v20100908-1606-H23-M2.jar
./studio/eclipse/plugins/org.jboss.tools.jbpm.convert_1.2.0.v20100908-1606-H23-M2.jar
./studio/eclipse/plugins/org.jboss.tools.jbpm.convert_1.2.0.v201009142310R-H472-M2.jar
./studio/eclipse/plugins/org.jboss.tools.jsf.vpe.jbpm_3.2.0.v201009142310R-H472-M2
./studio/eclipse/plugins/org.jbpm.gd.jpdl_3.3.0.v20100908-1606-H23-M2.jar
One bit of weirdness -- there are two versions of the jbpm.convert feature/plugin, and the jbpm4 feature is included too (but no jbpm4 plugins). Not sure that's a good thing.
Solution:
* filter *jbpm4* from files to include when unzipping the jbpm runnable zip for input into installer.
* disable jbpm-convert builder in uberbuilder since it's now provided in the jbpm runnable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 6 months
[JBoss JIRA] Created: (JBIDE-7036) RSE Deployment do not respect "Remote Server Home" settings
by Dominik Pospisil (JIRA)
RSE Deployment do not respect "Remote Server Home" settings
-----------------------------------------------------------
Key: JBIDE-7036
URL: https://jira.jboss.org/browse/JBIDE-7036
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.M2
Environment: jbosstools-3.2.0.M2.aggregate-Update-2010-09-08_17-17-54-H243.zip
Reporter: Dominik Pospisil
Assignee: Rob Stryker
Priority: Critical
Remote deployment do not respect "Remote Server Home" directory set in server preferences pages. Instead of that, runtime's home folder is used for remote deployment.
Therefore, it is impossible to deploy to remote system if the server on remote system resides on different path than on local developer system.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 6 months
[JBoss JIRA] Created: (JBIDE-7078) Multiple servers wih one runtime mismatch
by Dominik Pospisil (JIRA)
Multiple servers wih one runtime mismatch
-----------------------------------------
Key: JBIDE-7078
URL: https://jira.jboss.org/browse/JBIDE-7078
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.M2
Reporter: Dominik Pospisil
Assignee: Rob Stryker
If I create two servers using single runtime - one local and one remote, starting / stopping / publishing on those servers simultaneously does not work as expected. If I start the local server first, all subsequent operations are attempted to be completed locally and vice-versa.
Steps to reproduce:
1) Create new server rutime (EAP 5.1.CR2)
2) Create new local server using created runtime
3) Create new remote server using the same runtime
4) Start / stop local server
5) Start / deploy on remote server
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 6 months
[JBoss JIRA] Created: (JBIDE-6227) JMX Core Tests fails to find example project's .project file
by Nick Boldt (JIRA)
JMX Core Tests fails to find example project's .project file
------------------------------------------------------------
Key: JBIDE-6227
URL: https://jira.jboss.org/jira/browse/JBIDE-6227
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 3.2.next
Reporter: Nick Boldt
Running JMX tests on local or in Hudson, I get:
[INFO] --- maven-osgi-test-plugin:0.9.0-SNAPSHOT:test (default-test) @ org.jboss.tools.jmx.core.test ---
[INFO] Expected eclipse log file: /home/nboldt/eclipse/workspace-jboss/jbosstools-trunk/jmx/tests/org.jboss.tools.jmx.core.test/target/work/data/.metadata/.log
[INFO] Command line:
/bin/sh -c cd /home/nboldt/eclipse/workspace-jboss/jbosstools-trunk/jmx/tests/org.jboss.tools.jmx.core.test && /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java -Dosgi.noShutdown=false -Dosgi.os=linux -Dosgi.ws=gtk -Dosgi.arch=x86 -jar /home/nboldt/.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/nboldt/eclipse/workspace-jboss/jbosstools-trunk/jmx/tests/org.jboss.tools.jmx.core.test/target/work/data -dev file:/home/nboldt/eclipse/workspace-jboss/jbosstools-trunk/jmx/tests/org.jboss.tools.jmx.core.test/target/dev.properties -install /home/nboldt/eclipse/workspace-jboss/jbosstools-trunk/jmx/tests/org.jboss.tools.jmx.core.test/target/work -configuration /home/nboldt/eclipse/workspace-jboss/jbosstools-trunk/jmx/tests/org.jboss.tools.jmx.core.test/target/work/configuration -application org.codehaus.tycho.surefire.osgibooter.uitest -testproperties /home/nboldt/eclipse/workspace-jboss/jbosstools-trunk/jmx/tests/org.jboss.tools.jmx.core.test/target/surefire.properties -testApplication org.eclipse.ui.ide.workbench -product org.eclipse.sdk.ide
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.tools.jmx.core.test.JMXCoreAllTests
Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.106 sec <<< FAILURE!
testConnection(org.jboss.tools.jmx.core.test.DefaultProviderTest) Time elapsed: 0.009 sec <<< ERROR!
org.eclipse.core.internal.resources.ResourceException()[567]: java.io.FileNotFoundException: /home/nboldt/eclipse/workspace-jboss/jbosstools-trunk/jmx/tests/org.jboss.tools.jmx.core.test/target/work/data/JMX_EXAMPLE/.project (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:137)
at org.eclipse.core.internal.resources.ProjectDescriptionReader.read(ProjectDescriptionReader.java:626)
at org.eclipse.core.internal.resources.Workspace.loadProjectDescription(Workspace.java:1478)
at org.jboss.tools.jmx.core.test.util.TestProjectProvider.importExistingProject(TestProjectProvider.java:109)
at org.jboss.tools.jmx.core.test.util.TestProjectProvider.init(TestProjectProvider.java:97)
at org.jboss.tools.jmx.core.test.util.TestProjectProvider.<init>(TestProjectProvider.java:65)
at org.jboss.tools.jmx.core.test.DefaultProviderTest.testConnection(DefaultProviderTest.java:80)
Results :
Tests in error:
testConnection(org.jboss.tools.jmx.core.test.DefaultProviderTest)
Tests run: 7, Failures: 0, Errors: 1, Skipped: 0
------------
Did some digging and it seems that the .../jmx/tests/org.jboss.tools.jmx.core.test/target/work/data/JMX_EXAMPLE/ folder is empty. However, the content that's supposed to be checked out into that dir is definitely in the target/org.jboss.tools.jmx.core.test-1.1.0-SNAPSHOT.jar jar, so I would think the problem is in how the test is doing its unpacking, rather than how the jar is being built.
--------
Same error in Hudson:
http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-tycho-mod...
To run test in Hudson:
http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-tycho-mod... -> Build Now -> only need these components to be built: tests,common,jmx; may need to use -Dbuild.if.sources.unchanged=true flag too.
To run test locally from a fresh checkout:
cd /tmp; svn co http://anonsvn.jboss.org/repos/jbosstools/trunk/build/
or
cd /tmp; svn co http://anonsvn.jboss.org/repos/jbosstools/branches/modular_build/build/
then
cd /tmp/build; ant -DCOMPONENTS=tests,common,jmx
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 6 months
[JBoss JIRA] Created: (JBIDE-6596) New Seam WAR project has incorrect deployment artifact structure
by Dominik Pospisil (JIRA)
New Seam WAR project has incorrect deployment artifact structure
----------------------------------------------------------------
Key: JBIDE-6596
URL: https://jira.jboss.org/browse/JBIDE-6596
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.0.M1
Environment: JBT 3.2.0.M1
EAP 5.0, EAP 5.1.CR1
Reporter: Dominik Pospisil
Assignee: Alexey Kazakov
New Seam Project wizard creates project with incorrect structure, deployment of the project fails.
The deployed artifact contains:
/WEB-INF/lib/jboss-seam.jar/jboss-seam.jar
instead of:
/WEB-INF/lib/jboss-seam.jar
Steps to reproduce:
1) Register and start EAP 5.0 runtime
2) File -> New -> Seam Web project, choose EAP 5.0 runtime and EAP 5.0 Seam, WAR packaging option
3) Wait until project gets deployed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 6 months