[JBoss JIRA] (JBIDE-17656) Forge crashed Eclipse
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17656?page=com.atlassian.jira.plugi... ]
George Gastaldi resolved JBIDE-17656.
-------------------------------------
Resolution: Done
> Forge crashed Eclipse
> ---------------------
>
> Key: JBIDE-17656
> URL: https://issues.jboss.org/browse/JBIDE-17656
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta3
> Environment: Windows 7 64bits, JDK 8.0.0, JBDS 8.0.0.Beta2
> Reporter: Fred Bricon
> Assignee: Vineet Reynolds
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: generate.fsh, hs_err_pid4536.log, hs_err_pid5320.log, hs_err_pid640.log, JVM-GCactivity-heap.png, JVM-GCactivity-Linux.png, JVM-GCactivity.png
>
>
> I tried to reproduce the steps from JBIDE-17655 a 2nd time, Eclipse crashed while forge was scaffolding
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17274) Support JPA 2.1 in Hibernate Tools
by Emmanuel Bernard (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17274?page=com.atlassian.jira.plugi... ]
Emmanuel Bernard commented on JBIDE-17274:
------------------------------------------
Yeah :)
> Support JPA 2.1 in Hibernate Tools
> ----------------------------------
>
> Key: JBIDE-17274
> URL: https://issues.jboss.org/browse/JBIDE-17274
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Reporter: Max Rydahl Andersen
> Assignee: Koen Aers
> Priority: Blocker
> Fix For: 4.2.0.CR1
>
>
> Until now Hibernate tools "survived" that Hibernate 3.5+ could load hibernate 3 and 4 projects metadata without problems.
> With JPA 2.1 this changed and it requires Hibernate 4.3+ to load these metadata.
> We could update hibernate tools to use hibernate 4.3 to load the metadata but in doing so we would gain support for JPA 2.1 but at least loose support for loading Hibernate 3.3-4.2+ projects that uses custom user types (there could be more combinations that fails - figuring out how much requires a lot of work, but for now at least we know the usertypes are not binary compatible anymore).
> To fix this a rethink/reimplementation is needed of how hibernate tools works.
> It basicallly needs to become completely independent of hibernate binaries/classes.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBDS-3018) Install screen moves to bottom left corner of the screen
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3018?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3018:
-------------------------------------------
I cannot reproduce this - running yosemite.
> Install screen moves to bottom left corner of the screen
> --------------------------------------------------------
>
> Key: JBDS-3018
> URL: https://issues.jboss.org/browse/JBDS-3018
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer, upstream
> Affects Versions: 7.1.1.GA
> Environment: java version "1.8.0"
> Java(TM) SE Runtime Environment (build 1.8.0-b132)
> Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode)
> OSX 10.9.2
> One monitor
> No additional software for windows management
> Reporter: Arun Gupta
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 8.0.0.CR1
>
> Attachments: Screen Shot 2014-04-21 at 9.07.53 PM.png
>
>
> I started the install as
> java -jar ~/Downloads/jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar
> Install screen (step 1 of 9) popped up in the middle and then right away went in the bottom left corner of the screen as shown in attachment.
> This does not seem right.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBDS-2843) AngularJS Usability
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2843?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen closed JBDS-2843.
-------------------------------------
Resolution: Done
marking this as closed - angularjs content assist is in JBDS 8 if using Early Access.
Ionic palette is in the html palette for JBDS 8 proper.
> AngularJS Usability
> -------------------
>
> Key: JBDS-2843
> URL: https://issues.jboss.org/browse/JBDS-2843
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: jsp/jsf/xml/html source editing, requirements
> Reporter: Burr Sutter
> Assignee: Alexey Kazakov
> Labels: JBDS80_Approved_Scope
> Fix For: 8.0.0.CR1
>
>
> Related to JBIDE-14597
> Phase 1) Insure that no extraneous error messages are displayed for otherwise "valid" AngularJS constructs in the HTML
> Phase 2) Forge scaffolding of AngularJS apps should produce no warnings/error messages in the IDE from the generated code
> Phase 3) Code Assist (cntrl-space) in .html
> Phase 4) Code Assist (cntrl-space) in .js
> Phase 5) Widget Palette (like our jQuery Mobile palete)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18219) build info such as used git revisions/tags are not archived for our builds
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18219?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18219:
---------------------------------------------
..and we can assume these locations under ../builds/* are not deleted ?
Seems they should be at a more stable location once released?
> build info such as used git revisions/tags are not archived for our builds
> --------------------------------------------------------------------------
>
> Key: JBIDE-18219
> URL: https://issues.jboss.org/browse/JBIDE-18219
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Fix For: 4.2.0.CR1
>
>
> JBIDE-6958 and JBIDE-7444 was done to ensure we had the revision info and other results for a release, but seems we haven't archived this consinstelt over the years.
> We should review what info we definitely need but in general I would think archiving as much build info as possible would be a good practice anyway - at least for the releases (alpha, beta, final, GA etc.)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months