Grails

run-war https with Tomcat no longer works

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.3.4
  • Fix Version/s: 1.4-M1
  • Component/s: None
  • Labels:
    None

Description

Broken by this change: http://github.com/grails-plugins/grails-tomcat-plugin/commit/3f26f4d6305353588244ee502acbe08109024f5b

The startSecure() method needs to become "war aware".

Issue Links

This issue relates to:
GRAILS-6129 Grails 1.3RC1 run-war does not work - shows 404 error page Blocker Closed
GRAILS-5666 Run-war has some classpath conflicts Critical Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Luke Daley added a comment -

caused by change for GRAILS-5666

Show
Luke Daley added a comment - caused by change for GRAILS-5666
Hide
Permalink
Luke Daley added a comment -

caused by fix for GRAILS-6129

Show
Luke Daley added a comment - caused by fix for GRAILS-6129
Hide
Permalink
Luke Daley added a comment -

Resolved by: http://github.com/alkemist/grails-tomcat-plugin/commit/c0c8197a4aa0e5b0ae4c5652ee1a13f50a733a19

Can someone please pull this into the plugin as I don't have commit rights.

Show
Luke Daley added a comment - Resolved by: http://github.com/alkemist/grails-tomcat-plugin/commit/c0c8197a4aa0e5b0ae4c5652ee1a13f50a733a19 Can someone please pull this into the plugin as I don't have commit rights.
Hide
Permalink
Luke Daley added a comment -

Sorry Jeff, http://github.com/alkemist/grails-tomcat-plugin/commit/c0c8197a4aa0e5b0ae4c5652ee1a13f50a733a19 fixes GRAILS-6689 and not this issue. I commented on the wrong issue.

Show
Luke Daley added a comment - Sorry Jeff, http://github.com/alkemist/grails-tomcat-plugin/commit/c0c8197a4aa0e5b0ae4c5652ee1a13f50a733a19 fixes GRAILS-6689 and not this issue. I commented on the wrong issue.
Hide
Permalink
Lari Hotari added a comment -

System properties specified at the command line should be passed to run-war (tomcat instance) too.

For example we are using something like this to run grails: "grails -Ddevdb.host=dbhost run-war" . This no longer works in Grails 1.3.x . Also noticed that "grails prod run-war" seems to start some other environment?

Show
Lari Hotari added a comment - System properties specified at the command line should be passed to run-war (tomcat instance) too. For example we are using something like this to run grails: "grails -Ddevdb.host=dbhost run-war" . This no longer works in Grails 1.3.x . Also noticed that "grails prod run-war" seems to start some other environment?
Hide
Permalink
Luke Daley added a comment -

Got a bit trigger happy with the assign button.

Show
Luke Daley added a comment - Got a bit trigger happy with the assign button.
Hide
Permalink
Kurt Harriger added a comment -

@LariHotari the issue with the incorrect environment is fixed in 1.3.6 per GRAILS-6842

Show
Kurt Harriger added a comment - @LariHotari the issue with the incorrect environment is fixed in 1.3.6 per GRAILS-6842
Hide
Permalink
Luke Daley added a comment -

Version 1.3.7.1 of the Tomcat plugin brings this feature to the 1.3.x Grails line.

Show
Luke Daley added a comment - Version 1.3.7.1 of the Tomcat plugin brings this feature to the 1.3.x Grails line.

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.1#660-r161644) | Report a problem
Powered by a free Atlassian JIRA open source license for Grails project. Try JIRA - bug tracking software for your team.