[JBoss JIRA] (JBIDE-16011) create install/download section
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16011?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-16011:
-------------------------------
Fix Version/s: 4.2.0.Alpha2
(was: 4.0.x)
> create install/download section
> -------------------------------
>
> Key: JBIDE-16011
> URL: https://issues.jboss.org/browse/JBIDE-16011
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: website
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.2.0.Alpha2
>
>
> should have download section that explains how and where to get jbosstools installed.
> Should have a page pr. specific version download and a "archive" view to get directly to the past versions.
> Should not require more than a few lines with urls to add a new download/install.
> archived links for anything not on actual released update site urls (i.e. previous GA's in same release train) could start by just having download zip url (no updatesite)
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-16011) create install/download section
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16011?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-16011:
----------------------------------
Assignee: Nick Boldt
> create install/download section
> -------------------------------
>
> Key: JBIDE-16011
> URL: https://issues.jboss.org/browse/JBIDE-16011
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: website
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.0.x
>
>
> should have download section that explains how and where to get jbosstools installed.
> Should have a page pr. specific version download and a "archive" view to get directly to the past versions.
> Should not require more than a few lines with urls to add a new download/install.
> archived links for anything not on actual released update site urls (i.e. previous GA's in same release train) could start by just having download zip url (no updatesite)
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-16334) GWT WAR directory is not set properly in Eclipse Google (GWT) plug-in
by Slawa Giterman (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16334?page=com.atlassian.jira.plugi... ]
Slawa Giterman resolved JBIDE-16334.
------------------------------------
Resolution: Out of Date
The problem with warSrcDir was solved in Google Plugin for Eclipse, version 3.5.0. Corresponding ticket: https://code.google.com/p/google-plugin-for-eclipse/issues/detail?id=242
Thank you for your assistance!
> GWT WAR directory is not set properly in Eclipse Google (GWT) plug-in
> ---------------------------------------------------------------------
>
> Key: JBIDE-16334
> URL: https://issues.jboss.org/browse/JBIDE-16334
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.1.0.Final
> Environment: Eclipse Kepler
> m2e 1.2
> m2e-wtp 1.0.1
> Google Plugin for Eclipse 3.4.2
> JBoss Maven GWT Configurator 1.5.4
> Reporter: Slawa Giterman
> Assignee: Denis Golovin
>
> Hello,
> I use Eclipse Kepler, m2e 1.2, m2e-wtp 1.0.1, Google Plugin for Eclipse 3.4.2 and JBoss Maven GWT Configurator 1.5.4.
> My project uses not default warSourceDirectory in Maven pom.xml (<warSourceDirectory>$\{basedir\}/WebContent</warSourceDirectory>).
> The problem is that after each Maven -> Update Project action, GWT WAR directory in Eclipse (Project -> context menu -> Google -> Web Toolkit Settings -> Web Application -> WAR directory) is set to default Maven value "src/main/webapp" and not to the value of warSourceDirectory from pom.xml.
> It seems that WAR Directory value is read from file <ECLIPSE_PROJECT>/.settings/com.google.gdt.eclipse.core.prefs, property *warSrcDir*. This file has also another property, *lastWarOutDir* which tells Google GWT Plugin where to compile the GWT code (this issue was solved in JBIDE-11224)
> Current content of com.google.gdt.eclipse.core.prefs after Maven -> Update Project:
> {code}lastWarOutDir=/applicationserver/WebContent
> warSrcDir=src/main/webapp{code}
> So, the question is, is it possible to set value of warSrcDir to the same value as lastWarOutDir so that Eclipse does not show error "WAR source directory /applicationserver/src/main/webapp is missing" after each update?
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-16416) Shortcut for Redo action is missing
by Victor Rubezhny (JIRA)
Victor Rubezhny created JBIDE-16416:
---------------------------------------
Summary: Shortcut for Redo action is missing
Key: JBIDE-16416
URL: https://issues.jboss.org/browse/JBIDE-16416
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: seam2
Affects Versions: 4.1.0.Final
Reporter: Victor Rubezhny
Assignee: Victor Rubezhny
Fix For: 4.1.2.CR1, 4.2.0.Alpha2
By default, there is no shortcut for Redo action like in Eclipse (ShiftCtrl+Z).
I think it would be cool if there is a shortcut for redo by default ;-)
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-15888) Update the Spring Archetype reference
by Joshua Wilson (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15888?page=com.atlassian.jira.plugi... ]
Joshua Wilson commented on JBIDE-15888:
---------------------------------------
The error is still an issue it appears to only be fixed in Wildfly. We need to get them to do a patch for EAP.
If you use 2.0 like you suggest, the error goes away but it will not run on JBoss then. Please don't change it to 2.0.
Only 1.0, 1.1, and 1.2 are valid.
> Update the Spring Archetype reference
> -------------------------------------
>
> Key: JBIDE-15888
> URL: https://issues.jboss.org/browse/JBIDE-15888
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Joshua Wilson
> Assignee: Radim Hopp
> Labels: spring
> Fix For: 4.1.2.CR1
>
> Attachments: springmvc-test.xml
>
>
> I updated the Spring Archetype. The one in JBDS/JBIDE needs to point to the new version.
--
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
11 years, 11 months