[JBoss JIRA] Created: (JBDS-983) Console not showing up when staritng a EAP/SOA-P Instance
by Jim Tyrrell (JIRA)
Console not showing up when staritng a EAP/SOA-P Instance
---------------------------------------------------------
Key: JBDS-983
URL: https://jira.jboss.org/jira/browse/JBDS-983
Project: JBoss Developer Studio
Issue Type: Feature Request
Affects Versions: 3.0.0.M4
Reporter: Jim Tyrrell
For some reason starting a SOA-P instance by right clicking in the server view does not start/open the console for the output of the server as it is starting. For EAP and Seam projects this does not seem to be the case as often, but I think I have seen it. The current JBDS 3.0 M4 release does seem to not show the console unless I open the console via the Window -> Show View -> General -> Console and then I have to click an icon to enable the "Java Stack Trace Console". Once I have setup the console once as just noted even if I close it it will open as I expect. If I close JBDS and make sure that the console was not left open, I get the same behaviour when I try to right click on the SOA-P instance.
--
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
6 days, 11 hours
[JBoss JIRA] (JBDS-3044) Align installation default path with installer filename
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3044?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3044 at 5/28/14 10:36 AM:
------------------------------------------------------------
Martin did a quick test on OSX to see what the longest file paths are inside JBDS 8 Beta2:
{quote}
{code}
find jbdevstudio-* |awk '{ print length($0) ; }'|sort|uniq|egrep "2.+"
{code}
shows 251 as the longest path on Mac so not really safe
longest is ./studio/configuration/org.eclipse.osgi/949/data/c7ff8a0a591e0e90fe36069138e75f68/1012-1401176993555/org.springframework.ide.eclipse.core.java.ProjectClassLoaderCache$SourceAndOutputLocationResourceChangeListener$SourceAndOutputLocationResourceVisitor
but that is spring and it's data
{quote}
So we're already pushing the limit here for long paths on Windows / NTFS...
Related (with some LOLs): http://blog.codinghorror.com/filesystem-paths-how-long-is-too-long/
There are ways to achieve more-than-260-char paths, but do we want to?
was (Author: nickboldt):
Martin did a quick test on OSX to see what the longest file paths are inside JBDS 8 Beta2:
{quote}
{code}
find jbdevstudio-* |awk '{ print length($0) ; }'|sort|uniq|egrep "2.+"
{code}
shows 251 as the longest path on Mac so not really safe
longest is ./studio/configuration/org.eclipse.osgi/949/data/c7ff8a0a591e0e90fe36069138e75f68/1012-1401176993555/org.springframework.ide.eclipse.core.java.ProjectClassLoaderCache$SourceAndOutputLocationResourceChangeListener$SourceAndOutputLocationResourceVisitor
but that is spring and it's data
{quote}
So we're already pushing the limit here for long paths on Windows / NTFS...
> Align installation default path with installer filename
> -------------------------------------------------------
>
> Key: JBDS-3044
> URL: https://issues.jboss.org/browse/JBDS-3044
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 8.0.0.Beta2
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: discuss
> Fix For: 8.0.0.Beta3
>
>
> Now that Nick changed the installer filenames to jboss-devstudio in JBIDE-16871 (was jbdevstudio), shouldn't the default install path be changed similarly? Because it just went out of sync.
> This question is open for discussion. Nick pointed out some reasons against this suggestion:
> {quote}
> Martin Malina Re: changing the installation folder, I'll hold off on that change for the moment for a few reasons:
> a) Max is AFK, and will want to vet/veto this idea
> b) long paths for Windows users (80% of our user base) = bad news, especially considering how long some file paths can get already within Eclipse workspaces
> c) short paths for Windows (c:\jbdevstudio) & long paths for everyone else ~/jboss-devstudio) would be ill-advised from a documentation and cross-platform user experience
> So, either we stick w/ jbdevstudio, or we shorten to devstudio (losing the "jb" branding fragment). If we move to "jboss-devstudio" we increase the path by only 4 characters.
> Max Rydahl Andersen WDYT?
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
1 month
[JBoss JIRA] (JBDS-2719) Multiple Spring AOP problems when travel example is imported
by Joshua Wilson (JIRA)
[ https://issues.jboss.org/browse/JBDS-2719?page=com.atlassian.jira.plugin.... ]
Joshua Wilson commented on JBDS-2719:
-------------------------------------
[~nickboldt] I will need to test several different configurations to confirm my earlier guess. This is what I know so far.
First I would ask that you test with the [Kitchensink-Spring Quickstarts|https://github.com/jboss-developer/jboss-wfk-quickstarts] as I am working to keep them up to date and error free as much as possible. This specific error can be seen in the [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] quickstart. The Travel and PetClinic will be kept as close to the original as possible (and I haven't had a chance to update them yet).
With that in mind if I Build (with Eclipse/JBDS) [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] in JBDS 7.0.1 with Spring IDE 3.3 installed from JBoss Central, I get the aspectj error. However if I Build while in a standard Eclipse JEE install with JBDS and the stock Spring IDE/STS 3.4 installed, I do NOT get the aspectj error.
In order to truly confirm that adding both "AspectJ Compiler" and "AspectJ Development Tools" will fix the error, I would need to test that on my JBDS 7.0.1/SpringIDE 3.3 set up.
> Multiple Spring AOP problems when travel example is imported
> ------------------------------------------------------------
>
> Key: JBDS-2719
> URL: https://issues.jboss.org/browse/JBDS-2719
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, upstream
> Affects Versions: 7.0.0.GA
> Environment: JBDS 7.0.0.GA, L64, Spring IDE 3.3 installed from JBoss Central
> Reporter: Jiri Peterka
> Assignee: Nick Boldt
> Fix For: 7.1.0.Beta1
>
>
> There are Multiple Spring AOP Errors after travel example is imported:
> {code}
> Build path is incomplete. Cannot find class file for org/aspectj/weaver/reflect/ReflectionWorld$ReflectionWorldException
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
1 month
[JBoss JIRA] (JBIDE-24380) new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME}
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24380?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24380:
-------------------------------
Description:
In order to be able to more easily run server and webservices projects' tests, I suggest we set default values in parent pom:
{code}
- <jbosstools.test.jre.5></jbosstools.test.jre.5>
- <jbosstools.test.jre.6></jbosstools.test.jre.6>
- <jbosstools.test.jre.7></jbosstools.test.jre.7>
- <jbosstools.test.jre.8></jbosstools.test.jre.8>
+ <jbosstools.test.jre.5>${JAVA_HOME}</jbosstools.test.jre.5>
+ <jbosstools.test.jre.6>${JAVA_HOME}</jbosstools.test.jre.6>
+ <jbosstools.test.jre.7>${JAVA_HOME}</jbosstools.test.jre.7>
+ <jbosstools.test.jre.8>${JAVA_HOME}</jbosstools.test.jre.8>
{code}
This way, depending on what your system's definition of JAVA_HOME happens to be, you get a different effective pom, for your required JDK:
{code}
$ export JAVA_HOME=/opt/jdk1.8.0/
$ /opt/maven3/bin/mvn help:effective-pom | grep jbosstools.test.jre
<jbosstools.test.jre.5>/opt/jdk1.8.0/</jbosstools.test.jre.5>
<jbosstools.test.jre.6>/opt/jdk1.8.0/</jbosstools.test.jre.6>
<jbosstools.test.jre.7>/opt/jdk1.8.0/</jbosstools.test.jre.7>
<jbosstools.test.jre.8>/opt/jdk1.8.0/</jbosstools.test.jre.8>
(or, to use the JAVA_HOME set by alternatives...)
$ export JAVA_HOME=$(alternatives --display java | grep bin/java | grep link | sed -e "s#.\+ \(.\+\)bin/java#\1#")
$ /opt/maven3/bin/mvn help:effective-pom | grep jbosstools.test.jre
<jbosstools.test.jre.5>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.5>
<jbosstools.test.jre.6>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.6>
<jbosstools.test.jre.7>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.7>
<jbosstools.test.jre.8>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.8>
{code}
was:
In order to be able to more easily run server and webservices projects' tests, I suggest we set default values in parent pom:
{code}
- <jbosstools.test.jre.5></jbosstools.test.jre.5>
- <jbosstools.test.jre.6></jbosstools.test.jre.6>
- <jbosstools.test.jre.7></jbosstools.test.jre.7>
- <jbosstools.test.jre.8></jbosstools.test.jre.8>
+ <jbosstools.test.jre.5>${JAVA_HOME}</jbosstools.test.jre.5>
+ <jbosstools.test.jre.6>${JAVA_HOME}</jbosstools.test.jre.6>
+ <jbosstools.test.jre.7>${JAVA_HOME}</jbosstools.test.jre.7>
+ <jbosstools.test.jre.8>${JAVA_HOME}</jbosstools.test.jre.8>
{code}
> new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME}
> -------------------------------------------------------------------
>
> Key: JBIDE-24380
> URL: https://issues.jboss.org/browse/JBIDE-24380
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Fix For: 4.5.0.AM1
>
>
> In order to be able to more easily run server and webservices projects' tests, I suggest we set default values in parent pom:
> {code}
> - <jbosstools.test.jre.5></jbosstools.test.jre.5>
> - <jbosstools.test.jre.6></jbosstools.test.jre.6>
> - <jbosstools.test.jre.7></jbosstools.test.jre.7>
> - <jbosstools.test.jre.8></jbosstools.test.jre.8>
> + <jbosstools.test.jre.5>${JAVA_HOME}</jbosstools.test.jre.5>
> + <jbosstools.test.jre.6>${JAVA_HOME}</jbosstools.test.jre.6>
> + <jbosstools.test.jre.7>${JAVA_HOME}</jbosstools.test.jre.7>
> + <jbosstools.test.jre.8>${JAVA_HOME}</jbosstools.test.jre.8>
> {code}
> This way, depending on what your system's definition of JAVA_HOME happens to be, you get a different effective pom, for your required JDK:
> {code}
> $ export JAVA_HOME=/opt/jdk1.8.0/
> $ /opt/maven3/bin/mvn help:effective-pom | grep jbosstools.test.jre
> <jbosstools.test.jre.5>/opt/jdk1.8.0/</jbosstools.test.jre.5>
> <jbosstools.test.jre.6>/opt/jdk1.8.0/</jbosstools.test.jre.6>
> <jbosstools.test.jre.7>/opt/jdk1.8.0/</jbosstools.test.jre.7>
> <jbosstools.test.jre.8>/opt/jdk1.8.0/</jbosstools.test.jre.8>
> (or, to use the JAVA_HOME set by alternatives...)
> $ export JAVA_HOME=$(alternatives --display java | grep bin/java | grep link | sed -e "s#.\+ \(.\+\)bin/java#\1#")
> $ /opt/maven3/bin/mvn help:effective-pom | grep jbosstools.test.jre
> <jbosstools.test.jre.5>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.5>
> <jbosstools.test.jre.6>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.6>
> <jbosstools.test.jre.7>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.7>
> <jbosstools.test.jre.8>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.8>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24380) new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME}
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24380?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24380:
------------------------------------
If you forget to set these variables...
{code}
-Djbosstools.test.jre.5=/path/to/jdk5/or/equivalent
-Djbosstools.test.jre.6=/path/to/jdk6/or/equivalent
-Djbosstools.test.jre.7=/path/to/jdk7/or/equivalent
-Djbosstools.test.jre.8=/path/to/jdk8/or/equivalent
{code}
... on commandline, you get test failures like this:
{code}
[ERROR] com.sun.tools.javac.Main is not available in the classpath, requires Suns JDK version 5.0 or latter.
unknown location
compilation failed, errors should have been reported{code}
... buried inside a *jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/data/.metadata/.log* file.
So by defaulting to JAVA_HOME (which is likely Sun or Open JDK 8), you at least get the tests to succeed.
Surely that's a good thing?
> new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME}
> -------------------------------------------------------------------
>
> Key: JBIDE-24380
> URL: https://issues.jboss.org/browse/JBIDE-24380
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Fix For: 4.5.0.AM1
>
>
> In order to be able to more easily run server and webservices projects' tests, I suggest we set default values in parent pom:
> {code}
> - <jbosstools.test.jre.5></jbosstools.test.jre.5>
> - <jbosstools.test.jre.6></jbosstools.test.jre.6>
> - <jbosstools.test.jre.7></jbosstools.test.jre.7>
> - <jbosstools.test.jre.8></jbosstools.test.jre.8>
> + <jbosstools.test.jre.5>${JAVA_HOME}</jbosstools.test.jre.5>
> + <jbosstools.test.jre.6>${JAVA_HOME}</jbosstools.test.jre.6>
> + <jbosstools.test.jre.7>${JAVA_HOME}</jbosstools.test.jre.7>
> + <jbosstools.test.jre.8>${JAVA_HOME}</jbosstools.test.jre.8>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24380) new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME}
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24380?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24380:
-------------------------------
Fix Version/s: 4.5.0.AM1
> new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME}
> -------------------------------------------------------------------
>
> Key: JBIDE-24380
> URL: https://issues.jboss.org/browse/JBIDE-24380
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Fix For: 4.5.0.AM1
>
>
> In order to be able to more easily run server and webservices projects' tests, I suggest we set default values in parent pom:
> {code}
> - <jbosstools.test.jre.5></jbosstools.test.jre.5>
> - <jbosstools.test.jre.6></jbosstools.test.jre.6>
> - <jbosstools.test.jre.7></jbosstools.test.jre.7>
> - <jbosstools.test.jre.8></jbosstools.test.jre.8>
> + <jbosstools.test.jre.5>${JAVA_HOME}</jbosstools.test.jre.5>
> + <jbosstools.test.jre.6>${JAVA_HOME}</jbosstools.test.jre.6>
> + <jbosstools.test.jre.7>${JAVA_HOME}</jbosstools.test.jre.7>
> + <jbosstools.test.jre.8>${JAVA_HOME}</jbosstools.test.jre.8>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24380) new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME}
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-24380:
----------------------------------
Summary: new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME}
Key: JBIDE-24380
URL: https://issues.jboss.org/browse/JBIDE-24380
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.5.0.AM1
Reporter: Nick Boldt
In order to be able to more easily run server and webservices projects' tests, I suggest we set default values in parent pom:
{code}
- <jbosstools.test.jre.5></jbosstools.test.jre.5>
- <jbosstools.test.jre.6></jbosstools.test.jre.6>
- <jbosstools.test.jre.7></jbosstools.test.jre.7>
- <jbosstools.test.jre.8></jbosstools.test.jre.8>
+ <jbosstools.test.jre.5>${JAVA_HOME}</jbosstools.test.jre.5>
+ <jbosstools.test.jre.6>${JAVA_HOME}</jbosstools.test.jre.6>
+ <jbosstools.test.jre.7>${JAVA_HOME}</jbosstools.test.jre.7>
+ <jbosstools.test.jre.8>${JAVA_HOME}</jbosstools.test.jre.8>
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4383) Add support for installing EAP from devsuite installers
by Nick Boldt (JIRA)
Nick Boldt created JBDS-4383:
--------------------------------
Summary: Add support for installing EAP from devsuite installers
Key: JBDS-4383
URL: https://issues.jboss.org/browse/JBDS-4383
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: integration-platform
Affects Versions: 11.0.0.AM1
Reporter: Nick Boldt
Related to JBDS-4362, when we eliminate the EAP bundled installer jar, we need to also add support to the devsuite installer to install EAP from there instead.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months