jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Jetty
  • JETTY-796

Ant Plugin Improvements

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 6.1.12.rc5
  • Fix Version/s: None
  • Component/s: Maven
  • Labels:
    None
  • Environment:
    I'm running ant 1.7.0 on Fedora 9.

Description

Following the instructions (http://docs.codehaus.org/display/JETTY/Ant+Jetty+Plugin), I've made jetty launch from my ant build file. I run ant from the command-line, and I see several issues with the jetty/ant integration, although I may well be missing fixes for them:
1.) The Ant build does not fail if the Jetty server does not launch correctly
I've seen this if there already is a jetty server listening at the specified port. In this case, the jetty task returns but the ant build ends successfully.

2.) The jetty server instance is not terminated when the plugin task returns to ant. This causes jetty's termination trace to be mingled with ant's termination trace, which hides ant's termination status. The trace below shows this:
[echo] ============================================================
[echo] ============================================================
[echo] JETTY START-UP FAILED!
[echo] There already be a Jetty running on the port!
[echo] Check the log file!"
[echo] ============================================================
[echo] ============================================================

BUILD FAILED
/home/tony/working_copy/dict11/build.xml:792: JETTY FAILED

Total time: 8 seconds
2008-11-17 14:30:38.366::INFO: Shutdown hook executing
2008-11-17 14:30:38.367:ptweb:INFO: Destroying Spring FrameworkServlet 'main'
2008-11-17 14:30:38.371:ptweb:INFO: Closing Spring root WebApplicationContext
2008-11-17 14:30:38.379:ptweb:INFO: Shutting down log4j
log4j:WARN No appenders could be found for logger (com.mchange.v2.c3p0.impl.NewPooledConnection).
log4j:WARN Please initialize the log4j system properly.
2008-11-17 14:30:38.383::INFO: Shutdown hook complete

I've attached the relevant part of my build file.

  • Options
    • Sort By Name
    • Sort By Date
    • Ascending
    • Descending
    • Download All

Attachments

  1. XML File
    build.xml
    17/Nov/08 1:32 PM
    2 kB
    Tony Strauss

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Jason Porter added a comment - 27/Apr/09 11:50 PM

I'd like to add the ability to fork the process that starts the server. If I'm using ant as my primary build tool (and not an IDE) then I have to stop the server to recompile / repackage the application. The scanning intervals is great, but it would be very helpful to be able to fork the process (and probably have a jettyStop task as well.

Show
Jason Porter added a comment - 27/Apr/09 11:50 PM I'd like to add the ability to fork the process that starts the server. If I'm using ant as my primary build tool (and not an IDE) then I have to stop the server to recompile / repackage the application. The scanning intervals is great, but it would be very helpful to be able to fork the process (and probably have a jettyStop task as well.
Hide
Permalink
Sean Reque added a comment - 25/May/09 12:57 PM

Is there really no way to stop a jetty instance started by the jetty ant task without sending it a SIGKILL? I've wasted far too much time figuring this out and the answer I'm finding so far is no. If one indeed cannot, how could the ant plugin be of practical use to anybody?

Show
Sean Reque added a comment - 25/May/09 12:57 PM Is there really no way to stop a jetty instance started by the jetty ant task without sending it a SIGKILL? I've wasted far too much time figuring this out and the answer I'm finding so far is no. If one indeed cannot, how could the ant plugin be of practical use to anybody?
Hide
Permalink
Santthosh added a comment - 03/Oct/11 2:14 PM

I am also really puzzled on how to stop the jetty (started using this plugin) gracefully... hasn't this been thought about in 2 years? Can someone guide me...

Show
Santthosh added a comment - 03/Oct/11 2:14 PM I am also really puzzled on how to stop the jetty (started using this plugin) gracefully... hasn't this been thought about in 2 years? Can someone guide me...

People

  • Assignee:
    Jakub Pawlowicz
    Reporter:
    Tony Strauss
Vote (2)
Watch (3)

Dates

  • Created:
    17/Nov/08 1:32 PM
    Updated:
    03/Oct/11 2:14 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.