[JBoss JIRA] (JBIDE-20562) WildFly: jsf-impl-2.2.8-jbossorg-1.jar is not in default Runtime list
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20562?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-20562.
---------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.x)
Resolution: Won't Fix
[~zhangxunan] Hi Carl:
Sorry I lost track of this issue. So, we do have a way of adding this which I think you're not aware of. If you select window -> Preferences, then browse to Server / Runtime Environment / Default Classpath, you can select which jboss modules are automatically on the classpath for any given runtime type.
If you then expand the combo, and select your version of wildfly, you'll see what modules we add to the classpath by default. You can then click 'add' and a new dialog comes up. You should select "JBoss Module", and then, depending on your version of wildfly, you'd want to type something like com.sun.jsf-impl with a 'slot' value of "main".
Hopefully this helps. We won't be adding the implementation jars to the default classpath, but you can do it yourself. :)
> WildFly: jsf-impl-2.2.8-jbossorg-1.jar is not in default Runtime list
> ---------------------------------------------------------------------
>
> Key: JBIDE-20562
> URL: https://issues.jboss.org/browse/JBIDE-20562
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.3.0.CR1
> Reporter: carl zhang
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
>
> In Eclipse, I chose WildFly 8.2.0 server as my local web server. Then I created Dynamic Web Project. After done, I check the project Libraries-->WildFly 8.x Runtime libraries. I can see jboss-jsf-api_2.2_spec-2.2.8.jar in the list, but cannot see jsf-impl-2.2.8-jbossorg-1.jar
> So my Java codes related to jsf-impl classes cannot pass the compile. And I cannot manually add jsf-impl.jar into the project WEB_INF/lib because it cause deployment conflict.
> Please add the jsf-impl jar file into default Runtime library list. I don't check 9.0.0 and 10.0.0, if it is not in their default list. Please add it in
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21188) Spinner field is tiny in Fedora 23
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21188?page=com.atlassian.jira.plugi... ]
George Gastaldi updated JBIDE-21188:
------------------------------------
Environment:
Eclipse Mars.2 Release (4.5.2)
JBT 3.1.0.Final-v20150924-2222-B46
Fedora 23 with Cinnamon 2.8.7 (Gnome 3)
Yes, I added to the Environment field. Thanks for looking at this. It is still reproduceable
> Spinner field is tiny in Fedora 23
> ----------------------------------
>
> Key: JBIDE-21188
> URL: https://issues.jboss.org/browse/JBIDE-21188
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Environment: Eclipse Mars.2 Release (4.5.2)
> JBT 3.1.0.Final-v20150924-2222-B46
> Fedora 23 with Cinnamon 2.8.7 (Gnome 3)
> Reporter: George Gastaldi
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha1
>
> Attachments: Screenshot.png
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22204) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [VPE]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22204?page=com.atlassian.jira.plugi... ]
Ilya Buziuk closed JBIDE-22204.
-------------------------------
Resolution: Done
> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [VPE]
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-22204
> URL: https://issues.jboss.org/browse/JBIDE-22204
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: visual-page-editor-core
> Reporter: Rob Stryker
> Assignee: Ilya Buziuk
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [VPE]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master.
> Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in master
> 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-vpe at https://github.com/jbosstools/jbosstools-vpe/
> Searching for commits present in jbosstools-4.3.x and missing from master
> Commit hash "5fdde4" is the last common ancestor of jbosstools-4.3.x and master
> 5fdde4 is 10 commits ago in branch master
> 5fdde4 is 9 commits ago in branch jbosstools-4.3.x
> Commits missing from master that are in jbosstools-4.3.x:
> - https://github.com/jbosstools/jbosstools-vpe//commit/a2b21f1b38c67f967e9a...
> - https://github.com/jbosstools/jbosstools-vpe//commit/32507f22347e7a78b46c...
> - https://github.com/jbosstools/jbosstools-vpe//commit/614fe8ef79e3e14383e9...
> - https://github.com/jbosstools/jbosstools-vpe//commit/342bb8f7a473e668918d...
> - https://github.com/jbosstools/jbosstools-vpe//commit/a9273884abd848332359...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for VPE task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-20753) Text flickering when selecting server types in New Server wizard
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20753?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-20753:
--------------------------------
Component/s: upstream
> Text flickering when selecting server types in New Server wizard
> ----------------------------------------------------------------
>
> Key: JBIDE-20753
> URL: https://issues.jboss.org/browse/JBIDE-20753
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.3.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: regression
> Fix For: 4.4.0.Alpha1
>
>
> When you open the New Server wizard and select a server type, There will be some elements rendered for a fraction of a second. It's Server Runtime Environment and a dropdown menu - it will disappear again, but it's not nice to see something quickly appear and disappear again. You can keep selecting server types and it will keep happening. All of this is on the first page of the dialog.
> I checked and this did not happen in Beta2.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-20753) Text flickering when selecting server types in New Server wizard
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20753?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-20753:
--------------------------------
Fix Version/s: (was: 4.3.x)
> Text flickering when selecting server types in New Server wizard
> ----------------------------------------------------------------
>
> Key: JBIDE-20753
> URL: https://issues.jboss.org/browse/JBIDE-20753
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.3.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: regression
> Fix For: 4.4.0.Alpha1
>
>
> When you open the New Server wizard and select a server type, There will be some elements rendered for a fraction of a second. It's Server Runtime Environment and a dropdown menu - it will disappear again, but it's not nice to see something quickly appear and disappear again. You can keep selecting server types and it will keep happening. All of this is on the first page of the dialog.
> I checked and this did not happen in Beta2.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-20753) Text flickering when selecting server types in New Server wizard
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20753?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-20753:
-------------------------------------
[~mmalina] is this still replicatable?
> Text flickering when selecting server types in New Server wizard
> ----------------------------------------------------------------
>
> Key: JBIDE-20753
> URL: https://issues.jboss.org/browse/JBIDE-20753
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.3.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: regression
> Fix For: 4.4.0.Alpha1
>
>
> When you open the New Server wizard and select a server type, There will be some elements rendered for a fraction of a second. It's Server Runtime Environment and a dropdown menu - it will disappear again, but it's not nice to see something quickly appear and disappear again. You can keep selecting server types and it will keep happening. All of this is on the first page of the dialog.
> I checked and this did not happen in Beta2.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22214) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [BrowserSim]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22214?page=com.atlassian.jira.plugi... ]
Ilya Buziuk closed JBIDE-22214.
-------------------------------
Resolution: Done
> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [BrowserSim]
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-22214
> URL: https://issues.jboss.org/browse/JBIDE-22214
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: browsersim
> Reporter: Rob Stryker
> Assignee: Ilya Buziuk
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [BrowserSim]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master.
> Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in master
> 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-browsersim at https://github.com/jbosstools/jbosstools-browsersim/
> Searching for commits present in jbosstools-4.3.x and missing from master
> Commit hash "ee7642" is the last common ancestor of jbosstools-4.3.x and master
> ee7642 is 17 commits ago in branch master
> ee7642 is 15 commits ago in branch jbosstools-4.3.x
> Commits missing from master that are in jbosstools-4.3.x:
> - https://github.com/jbosstools/jbosstools-browsersim//commit/21d705cda91a5...
> - https://github.com/jbosstools/jbosstools-browsersim//commit/2adc8601840fa...
> - https://github.com/jbosstools/jbosstools-browsersim//commit/e3286f743f5a7...
> - https://github.com/jbosstools/jbosstools-browsersim//commit/381ad6f797173...
> - https://github.com/jbosstools/jbosstools-browsersim//commit/0ba88810356c7...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for BrowserSim task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months