[JBoss JIRA] Created: (JBIDE-8241) ModeShape Tools Should Update Copyright-Related Files To Say 2011
by Dan Florian (JIRA)
ModeShape Tools Should Update Copyright-Related Files To Say 2011
-----------------------------------------------------------------
Key: JBIDE-8241
URL: https://issues.jboss.org/browse/JBIDE-8241
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: modeshape
Affects Versions: 3.2.0.CR1
Reporter: Dan Florian
Assignee: Dan Florian
Fix For: 3.2.1
These files need to be updated:
1. org.jboss.tools.modeshape.rest/about.properties
2. org.jboss.tools.modeshape.rest.feature/COPYRIGHT.txt
3. org.jboss.tools.modeshape.rest.feature/feature.properties
4. org.jboss.tools.modeshape.rest.sdk.feature/COPYRIGHT.txt
5. org.jboss.tools.modeshape.rest.sdk.feature/feature.properties
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-8461) Editing AS Launch Configuration -Djava.library.path
by Burr Sutter (JIRA)
Editing AS Launch Configuration -Djava.library.path
---------------------------------------------------
Key: JBIDE-8461
URL: https://issues.jboss.org/browse/JBIDE-8461
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.2.0.CR1
Environment: Win7 64-bit, 32-bit 1.6 JVM
Reporter: Burr Sutter
It seems that you can not make changes to -Djava.library.path on the Launch configuration properties. In addition, dropping your native libs into this directory are not recognized when the server is launched - I am trying to add the JBoss Native tc-native1.dll to my AS6
The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: D:\servers\jboss-6.0.0.Final\bin\native;
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-7989) Maven bot test plugin has no runnable tests
by Nick Boldt (JIRA)
Maven bot test plugin has no runnable tests
-------------------------------------------
Key: JBIDE-7989
URL: https://issues.jboss.org/browse/JBIDE-7989
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 3.2.0.CR1
Reporter: Nick Boldt
Either the test plugin declares no classes to run as SWT Bot tests, or they're all being excluded from running because of the include/exclude filters in the parent pom.xml (or this plugin's pom.xml).
Log:
[INFO] Command line:
/bin/sh -c cd /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--maven/sources/tests/org.jboss.tools.maven.ui.bot.test && /qa/tools/opt/jdk1.6.0_20/jre/bin/java -Dosgi.noShutdown=false -Dosgi.os=linux -Dosgi.ws=gtk -Dosgi.arch=x86 -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=256m -Dusage_reporting_enabled=false -jar /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--maven/m2-repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.1.0.v20100507/org.eclipse.equinox.launcher-1.1.0.v20100507.jar -data /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--maven/sources/tests/org.jboss.tools.maven.ui.bot.test/target/work/data -dev file:/mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--maven/sources/tests/org.jboss.tools.maven.ui.bot.test/target/dev.properties -install /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--maven/sources/tests/org.jboss.tools.maven.ui.bot.test/target/work -configuration /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--maven/sources/tests/org.jboss.tools.maven.ui.bot.test/target/work/configuration -application org.sonatype.tycho.surefire.osgibooter.uitest -testproperties /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--maven/sources/tests/org.jboss.tools.maven.ui.bot.test/target/surefire.properties -testApplication org.eclipse.ui.ide.workbench -product org.eclipse.sdk.ide
-------------------------------------------------------
T E S T S
-------------------------------------------------------
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] org.jboss.tools.maven.ui.bot.test ................. FAILURE [2:53.025s]
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2_trunk.component--mav...
Solution:
add some test classes or suites, rename some classes or suites, or override the exclude/include filter [1].
[1] https://www.jboss.org/tools/docs/testing#exclude
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-8313) Launch instance wizard: cannot access webapp (404) if using ami-7ad22213
by Rob Stryker (JIRA)
Launch instance wizard: cannot access webapp (404) if using ami-7ad22213
------------------------------------------------------------------------
Key: JBIDE-8313
URL: https://issues.jboss.org/browse/JBIDE-8313
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: deltacloud, JBossAS
Affects Versions: 3.2.0.CR1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.2.1
Despite the fixes in JBIDE-8261, multiple issues seem to persist with remote AS when using this setup.
First, it seems RSE loses the connection at a certain point (10 minutes? not sure), and all efforts to restore it are lost. This means that even efforts to upload new changes fails.
Second, even if i manually scp files (some new Dyn Web proj) to the server and then mv it into the deploy folder, they often are not recognized. In fact, it seems the entire deployment scanner shuts down and all efforts to restart it fail.
Even efforts to craft, on the machine in VI, a new -ds.xml file, and move it in, fails.
Even restarting the deployment scanner with the following commands fails:
/opt/jboss-as6/bin/twiddle.sh -s service:jmx:rmi:///jndi/rmi://EC2-184-72-200-3.COMPUTE-1.AMAZONAWS.COM:1090/jmxrmi -u admin -p admin invoke jboss.deployment:flavor=URL,type=DeploymentScanner stop
/opt/jboss-as6/bin/twiddle.sh -s service:jmx:rmi:///jndi/rmi://EC2-184-72-200-3.COMPUTE-1.AMAZONAWS.COM:1090/jmxrmi -u admin -p admin invoke jboss.deployment:flavor=URL,type=DeploymentScanner start
They do not fail with exceptions, and the twiddle finishes as expected.
So all in all, this is just extremely baffling. It has elements of RSE errors (losing connection), elements of AS6-errors (deployment scanner start / stop really not doing a damn thing), and I'm sure my tools are also not exempt from errors.
Unfortunately, code freeze is here and the best I can do is log errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months