[JBoss JIRA] (JBDS-3345) Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBDS-3345?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBDS-3345:
------------------------------------
Attachment: installed_jre.png
runtime_jre.png
> Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8
> -----------------------------------------------------------------
>
> Key: JBDS-3345
> URL: https://issues.jboss.org/browse/JBDS-3345
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: runtime
> Affects Versions: 8.0.2.GA
> Environment: Fedora 21 x86_64
> JBDS 8.0.2.GA with Oracle JDK 1.8.0_25 and Oracle JDK 1.7.0_71
> Reporter: Andrej Podhradsky
> Priority: Critical
> Attachments: errors.txt, installed_jre.png, runtime_jre.png
>
>
> FSW 6.0.0.GA supports java 6 and 7, so if we want to run this server on JBDS 8 with jdk 8 we need to add another jdk to the JBDS, e.g. jdk 7. But this doesn't work, see errors in the attached file.
> Moreover, we are not able to stop the server from IDE, the process is still alive and we have to kill it manually.
> Note that this happens only when we install JBDS 8.0.2 with jdk 8, if we install it with jdk 7 the server works fine.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19119) Tern error when opening a jsp file
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19119?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-19119:
-----------------------------------------
Yes, latest snapshots and the release of 0.7.0 have this issue.
> Tern error when opening a jsp file
> ----------------------------------
>
> Key: JBIDE-19119
> URL: https://issues.jboss.org/browse/JBIDE-19119
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, upstream
> Affects Versions: 4.3.0.Beta2
> Reporter: Martin Malina
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha2
>
> Attachments: tern-error.png
>
>
> I was just verying something in master for Rob and hit this issue:
> I created a dynamic web project, then a jsp file. Once the jsp was opened in Eclipse, I got this error popup immediately:
> !tern-error.png!
> This was in the workspace log:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2015-01-29 17:04:14.678
> !MESSAGE An internal error occurred during: "Refresh tern project job".
> !STACK 0
> java.lang.IllegalArgumentException: Attempted to beginRule: R/, does not match outer scope rule: P/dynproj2
> at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
> at org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java:134)
> at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:333)
> at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:85)
> at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:298)
> at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:118)
> at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2251)
> at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1347)
> at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1401)
> at tern.eclipse.ide.internal.core.builder.TernBuilder.addTernBuilder(TernBuilder.java:231)
> at tern.eclipse.ide.internal.core.resources.IDETernProject.doLoad(IDETernProject.java:186)
> at tern.resources.TernProject.load(TernProject.java:332)
> at tern.eclipse.ide.internal.core.resources.RefreshTernProjectJob.runInWorkspace(RefreshTernProjectJob.java:49)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> This was JBT nightly from today (2015/01/29) from http://download.jboss.org/jbosstools/updates/nightly/mars/ on top of Eclipse Mars M4. On top of that, I had one server PR of Rob's installed, but that shouldn't have any effect.
> My platform is OS X 10.10 Yosemite, running Oracle JDK 1.7.
> I realize this is master and it might be a known issue, but better to be safe :)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-17710) error importing kitchensink angularjs quickstart when no jboss-eap runtime available
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17710?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-17710:
-----------------------------------
ok thx, i'll take a look at it
> error importing kitchensink angularjs quickstart when no jboss-eap runtime available
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-17710
> URL: https://issues.jboss.org/browse/JBIDE-17710
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, upstream
> Affects Versions: 4.2.0.Beta2
> Environment: Linux 64 (Fedora 18), JDK 1.8
> Reporter: Nick Boldt
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.3.0.Alpha2
>
> Attachments: config-jboss-maven.png, error-quickstart-kitchensink-angularjs.png, install-jpa2-NPE.txt, jbds8b3a-jdk8-quickstart-angularjs-launch-no-NPE-thrown-simpler-settings.xml.png, jbds8b3a-jdk8-quickstart-angularjs-launch-no-server-runtime-found-imports-fine-only-1-warning-compiles-ok.png, jbds8b3a-jdk8-quickstart-angularjs-launch-no-server-runtime-found.png, jbds8b3a-jdk8-quickstart-angularjs-launch-NPE-thrown.log.txt, settings.xml
>
>
> 1. install JBDS 8.0.0.Beta2-v20140617-2058-B166 from update site into Eclipse 4.4.0.R Luna JEE bundle.
> 2. Install Arquillian from JBoss Central EA site (using -D flags above)
> 3. launch kitchensink-angularjs quickstart.
> 4. Get NPE installing JPA 2.0
> 5. Get numerous import problems in MemberRegistrationTest.java and other source files; quickfixes don't work.
> Also had the same issues with JBT 4.2.0.Beta2, so it doesn't seem this is a JBDS only issue.
> !error-quickstart-kitchensink-angularjs.png!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3345) Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3345?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3345:
-------------------------------------------
I perfectly understand why you are doing this. We have multiple runtime/server support in devstudio for this *exact* reason.
But your logs are showing deployments errors and nothing shows it is not starting. It shows deployments compiled for Java 8 is failing when you are running it with Java 7.
The way to change what version your server is started with is to open the server, click runtime config and see what the Execution/Java environment is used.
Is that Java 7 or Java 8 ?
Also please show the *full* log then we should be able to see the jdk actually used.
> Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8
> -----------------------------------------------------------------
>
> Key: JBDS-3345
> URL: https://issues.jboss.org/browse/JBDS-3345
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: runtime
> Affects Versions: 8.0.2.GA
> Environment: Fedora 21 x86_64
> JBDS 8.0.2.GA with Oracle JDK 1.8.0_25 and Oracle JDK 1.7.0_71
> Reporter: Andrej Podhradsky
> Priority: Critical
> Attachments: errors.txt
>
>
> FSW 6.0.0.GA supports java 6 and 7, so if we want to run this server on JBDS 8 with jdk 8 we need to add another jdk to the JBDS, e.g. jdk 7. But this doesn't work, see errors in the attached file.
> Moreover, we are not able to stop the server from IDE, the process is still alive and we have to kill it manually.
> Note that this happens only when we install JBDS 8.0.2 with jdk 8, if we install it with jdk 7 the server works fine.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-7379) Importing / Exporting of AS servers ignore command line args, filesets, xpaths, and even runtimes
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/JBIDE-7379?page=com.atlassian.jira.plugin... ]
Paul Richardson commented on JBIDE-7379:
----------------------------------------
Hey [~rob.stryker]
Firstly my apologies to now answering sooner and that you have done so much work on this. I also created a topic branch with a version of import/export but was in [Teiid's repository||https://github.com/phantomjinx/teiid-designer/commits/TEIIDDE...] rather than jboss'. Anyway, they look pretty similar although your API has made some assumptions which I tried to avoid, ie.
* The exported storage unit would be a zip. I used a non-specific IStorageSource interface then implement a DirectorySource initially for testing purposes;
* The config/artefacts being exported would only be parts of an IServer;
* Export constituents (IStorageUnit) would declare themselves part of categories, which become sub-directories in the directory storage source or in a zip/jar storage source.
The upshot of this is that with your API only expecting to export server configuration, only the Teiid server configuration would be exportable. However, Teiid also has file artefacts, stored in other parts of the workspace which need a separate storage unit (not implemented yet).
I was intending to implement this as extensions of the Import.../Export... actions in Eclipse. You may have done the same, just cannot see it at the moment, what do you think?
Not sure where next with this. TEIIDDES-1119 work has stood still since June due to my switching to working on the Teiid Komodo engine. I think I am due to return to it when the engine has been stood up but that probably will not be for about 6 months or so. Thus, don't know whether to ignore my branch, merge in some of its ideas ... Anyway, let me know your thoughts/plans.
Apologies for not replying sooner.
Paul
> Importing / Exporting of AS servers ignore command line args, filesets, xpaths, and even runtimes
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-7379
> URL: https://issues.jboss.org/browse/JBIDE-7379
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 3.2.0.Beta1
> Reporter: Rob Stryker
> Assignee: Paul Richardson
> Fix For: 4.3.x
>
>
> Exporting of servers is incomplete. It does not export any saved filesets, xpaths, or custom launch configuration args.
> Importing of servers is also incomplete, not importing any of these elements. Also, while the servers themselves are imported, sometimes their runtimes are not created at all, and you get a server with no runtime. This has been very hard to track down, but no runtimeAdded event is ever fired, and in our code it looks as if they're not even created or looked for.
> This needs to be re-visited and tested extensively. I expect I will move import / export functionality into the AS plugin for now since hte o.j.t.runtime plugin already depends on AS. This will allow me to use classes already in the AS test suite for filesets and xpaths properly. I will keep the handler in the runtimes plugin but merely have it delegate to the functionality stored in the as plugin.
> It currently seems to be saving only servers and not the runtimes.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19260) Investigate expanding more "command line" options into UI and the IRuntime
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19260?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19260:
---------------------------------------------
majority of these are not relevant to show to the user.
Should be moved to an "Advanced..." section or other means of making it not necessary for default users to have to get asked about these ?
Maybe just have a table of property values users can set and we can provide browse button for that knows how these properties are assoicated ? i.e. that standalone.xml is to found inside what config.dir is pointing to if it is a relative path.
also I think anything that can be defaulted (as in "do not store hardcoded value in our setup but let the runtime figure it out") would be better than we explictily override everything.
> Investigate expanding more "command line" options into UI and the IRuntime
> --------------------------------------------------------------------------
>
> Key: JBIDE-19260
> URL: https://issues.jboss.org/browse/JBIDE-19260
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.3.0.Alpha2
> Reporter: Rob Stryker
> Attachments: JBIDE-19260.png
>
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1191153
> Investigate whether it makes sense to expose the following command line options in the UI and API for IRuntime:
> jboss.server.config.dir = jboss.server.base.dir/configuration
> jboss.server.data.dir = jboss.server.base.dir/data
> jboss.server.log.dir = jboss.server.base.dir/log
> jboss.server.temp.dir = jboss.server.base.dir/tmp
> jboss.server.deploy.dir = jboss.server.data.dir/content
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3345) Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBDS-3345?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBDS-3345:
------------------------------------
Steps to Reproduce:
0. Install FSW 6.0.0.GA (with or without patch) with JDK 7
1. Install JBDS 8 with JDK 8
2. Window > Preferences > Java > Installed JREs
3. Add standard VM with JDK 7
4. Create new server using JBoss Enterprise Application Platform 6.1+
5. Specify FSW path and set runtime jre to JDK 7 (added in step 3)
6. Start the server
was:
0. Install FSW 6.0.0.GA (with or without patch) with JDK 7
1. Install JBDS 8 with JDK 8
2. Window > Preferences > Java > Installed JREs
3. Add standard VM with JDK 7
4. Create new server with Create the appropriate runtime for FSW in JBDS and set runtime jre to JDK 7
5. Start the server
> Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8
> -----------------------------------------------------------------
>
> Key: JBDS-3345
> URL: https://issues.jboss.org/browse/JBDS-3345
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: runtime
> Affects Versions: 8.0.2.GA
> Environment: Fedora 21 x86_64
> JBDS 8.0.2.GA with Oracle JDK 1.8.0_25 and Oracle JDK 1.7.0_71
> Reporter: Andrej Podhradsky
> Priority: Critical
> Attachments: errors.txt
>
>
> FSW 6.0.0.GA supports java 6 and 7, so if we want to run this server on JBDS 8 with jdk 8 we need to add another jdk to the JBDS, e.g. jdk 7. But this doesn't work, see errors in the attached file.
> Moreover, we are not able to stop the server from IDE, the process is still alive and we have to kill it manually.
> Note that this happens only when we install JBDS 8.0.2 with jdk 8, if we install it with jdk 7 the server works fine.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months