January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3319) JBDS 8.0.2 EAP installer displays incorrect storage requirements to user

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3319?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3319 at 1/15/15 4:48 PM: ----------------------------------------------------------- Repeating the above using jboss-devstudio-8.0.2.GA-v20150114-2029-B382-installer-eap.jar (a *688M file*), I got these numbers: {quote}Required Disk Space (as reported by installer): *585.78 MB* Actual disk space used by install, `du -shc`: *811M* After first startup, `du -shc`: *811M*{quote} was (Author: nickboldt): Repeating the above using jboss-devstudio-8.0.2.GA-v20150114-2029-B382-installer-eap.jar (a *688M file*), I got these numbers: {quote}Required Disk Space (as reported by installer): *585.78 MB* Actual disk space used by install, `du -shc`: 811M After first startup, `du -shc`: 811M{quote} > JBDS 8.0.2 EAP installer displays incorrect storage requirements to user > ------------------------------------------------------------------------ > > Key: JBDS-3319 > URL: https://issues.jboss.org/browse/JBDS-3319 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.2.GA > Reporter: Len DiMaggio > Assignee: Nick Boldt > > The (eap embedded) installer for JBDS 8.0.2 informs the user that this much disk space is required: > Disk Space: > Available Disk Space: 31.64 GB Required Disk Space: 585.78 MB > The actual install uses this much: > du -sh installdir/ > 822M installdir/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19046) Upgrade Forge Runtime to 2.13.1.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19046?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-19046: ----------------------------------------- Here is the release announcement: http://forge.jboss.org/news/2015-01-15/forge-2.13.1.final-%28ingot%29-is-... > Upgrade Forge Runtime to 2.13.1.Final > ------------------------------------- > > Key: JBIDE-19046 > URL: https://issues.jboss.org/browse/JBIDE-19046 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.2.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.2.3.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18860) Publish to Wildfly AS does not update files

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18860?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-18860. ------------------------------------ Resolution: Rejected > Publish to Wildfly AS does not update files > ------------------------------------------- > > Key: JBIDE-18860 > URL: https://issues.jboss.org/browse/JBIDE-18860 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Final > Environment: Windows7 64bit, JDK8u25 > Reporter: Darryl Miles > Priority: Critical > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > Attachments: org.example.jbide18860.tar.gz, org.example.jbide18860_v2.tar.gz, org.example.jbide18860_v3.zip > > > I think I am on JBIDE product 4.2.0.Final (but features show as 3.6.0.Final and Plugins as 3.0.0.Final-v20141016) > I have an EAR Maven project published to Wildfly 8.x. > there is a file in the project TOPLEVEL/src/main/application/META-INF/jboss-deployment-structure.xml > If this file is edited and saved, and I perform publish operation on server. The change is never made to the deployments directory. > If I manually delete the file from the deployments direcory, then perform clean operation and publish operation and full publish operation, the file is never re-crearted. > The only way is to REMOVE EAR module from server, clean server, stop server, ADD EAR module to server, publish server, start server. > Now the file is updated. > I also note that I have a number of workspace JPA/JAR projects that should be included in the EAR in the lib/* folder but they are never copied there. > I have found a copy in a folder like workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\WildFly_8.1.0.Final\tempRemoteDeploy\ in here are the JARs I expected to find in the server runtime folder wildfly-8.1.0.Final\standalone\deployments\com.company.ear\lib\** > The timestamps on the files in this directory appear to be up-to-date at each publish event. > As a workaround I use "Make As Deployable" on the file workspace\com.company.ear\target\com.company.ear-1.2.3-SNAPSHOW.ear and I use a manual Maven build profile to create this file. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18860) Publish to Wildfly AS does not update files

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18860?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-18860: ---------------------------------------- I'm resolving this issue. [~dlmiles] please test Fred's project and if you still can reproduce the problem then please reopen the issue. Thanks! > Publish to Wildfly AS does not update files > ------------------------------------------- > > Key: JBIDE-18860 > URL: https://issues.jboss.org/browse/JBIDE-18860 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Final > Environment: Windows7 64bit, JDK8u25 > Reporter: Darryl Miles > Priority: Critical > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > Attachments: org.example.jbide18860.tar.gz, org.example.jbide18860_v2.tar.gz, org.example.jbide18860_v3.zip > > > I think I am on JBIDE product 4.2.0.Final (but features show as 3.6.0.Final and Plugins as 3.0.0.Final-v20141016) > I have an EAR Maven project published to Wildfly 8.x. > there is a file in the project TOPLEVEL/src/main/application/META-INF/jboss-deployment-structure.xml > If this file is edited and saved, and I perform publish operation on server. The change is never made to the deployments directory. > If I manually delete the file from the deployments direcory, then perform clean operation and publish operation and full publish operation, the file is never re-crearted. > The only way is to REMOVE EAR module from server, clean server, stop server, ADD EAR module to server, publish server, start server. > Now the file is updated. > I also note that I have a number of workspace JPA/JAR projects that should be included in the EAR in the lib/* folder but they are never copied there. > I have found a copy in a folder like workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\WildFly_8.1.0.Final\tempRemoteDeploy\ in here are the JARs I expected to find in the server runtime folder wildfly-8.1.0.Final\standalone\deployments\com.company.ear\lib\** > The timestamps on the files in this directory appear to be up-to-date at each publish event. > As a workaround I use "Make As Deployable" on the file workspace\com.company.ear\target\com.company.ear-1.2.3-SNAPSHOW.ear and I use a manual Maven build profile to create this file. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18274) AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18274?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18274: ----------------------------------- Fix Version/s: (was: 4.2.3.Final) > AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname > ------------------------------------------------------------------------------- > > Key: JBIDE-18274 > URL: https://issues.jboss.org/browse/JBIDE-18274 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.0.Alpha1 > > Attachments: server-adapter.png, server-editor.png, server-logs.png, server-runtime.png > > > This is a follow up of JBIDE-17935 . > Previously, Rob fixed this: > {quote} > I've surprisingly been able to replicate this and it's a race-condition. I'll need to synchronize some variables in this class here. > {quote} > But in this rare case it still fails for me. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19003) Promote JBoss Tools CAT in Dialog Similar to Usage

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19003?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-19003: ---------------------------------------- [~ldimaggio] could you please provide me a text for the current usage dialog regarding CAT? I would add this to the dialog and make a screenshot to show how it might look. > Promote JBoss Tools CAT in Dialog Similar to Usage > -------------------------------------------------- > > Key: JBIDE-19003 > URL: https://issues.jboss.org/browse/JBIDE-19003 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa, usage > Affects Versions: 4.2.1.Final > Reporter: Len DiMaggio > Assignee: Alexey Kazakov > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > > Can we add a "join JBT Cat?" dialog for new users? The dialog should appear only once so that we don't annoy the users. Thx! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19003) Promote JBoss Tools CAT in Dialog Similar to Usage

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19003?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19003: ----------------------------------- Fix Version/s: 4.3.0.Alpha1 > Promote JBoss Tools CAT in Dialog Similar to Usage > -------------------------------------------------- > > Key: JBIDE-19003 > URL: https://issues.jboss.org/browse/JBIDE-19003 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa, usage > Affects Versions: 4.2.1.Final > Reporter: Len DiMaggio > Assignee: Alexey Kazakov > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > > Can we add a "join JBT Cat?" dialog for new users? The dialog should appear only once so that we don't annoy the users. Thx! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19003) Promote JBoss Tools CAT in Dialog Similar to Usage

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19003?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19003: -------------------------------------- Assignee: Alexey Kazakov (was: Xavier Coulon) > Promote JBoss Tools CAT in Dialog Similar to Usage > -------------------------------------------------- > > Key: JBIDE-19003 > URL: https://issues.jboss.org/browse/JBIDE-19003 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa, usage > Affects Versions: 4.2.1.Final > Reporter: Len DiMaggio > Assignee: Alexey Kazakov > Fix For: 4.2.3.Final > > > Can we add a "join JBT Cat?" dialog for new users? The dialog should appear only once so that we don't annoy the users. Thx! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19046) Upgrade Forge Runtime to 2.13.1.Final

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19046?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19046: ------------------------------------- Any links to other bug reports justifying we update forge in 4.2.x? > Upgrade Forge Runtime to 2.13.1.Final > ------------------------------------- > > Key: JBIDE-19046 > URL: https://issues.jboss.org/browse/JBIDE-19046 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.2.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.2.3.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19046) Upgrade Forge Runtime to 2.13.1.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19046?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-19046: ------------------------------------ Issue Type: Component Upgrade (was: Feature Request) > Upgrade Forge Runtime to 2.13.1.Final > ------------------------------------- > > Key: JBIDE-19046 > URL: https://issues.jboss.org/browse/JBIDE-19046 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.2.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.2.3.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2015