[jira] (JETTY-1494) jetty:run-forked does not honor <webApp> configuration

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] (JETTY-1494) jetty:run-forked does not honor <webApp> configuration

JIRA jira@codehaus.org
Simone Bordet  created JETTY-1494:
-------------------------------------

             Summary: jetty:run-forked does not honor <webApp> configuration
                 Key: JETTY-1494
                 URL: https://jira.codehaus.org/browse/JETTY-1494
             Project: Jetty
          Issue Type: Bug
          Components: Maven
    Affects Versions: 7.6.1
            Reporter: Simone Bordet
            Assignee: Jan Bartel


When specifying a configuration for {{jetty:run-forked}} of
{code}
<plugin>
    <groupId>org.mortbay.jetty</groupId>
    <artifactId>jetty-maven-plugin</artifactId>
    <version>${project.version}</version>
    <configuration>
        <stopPort>8888</stopPort>
        <stopKey>quit</stopKey>
        <webApp>
            <contextPath>/</contextPath>
        </webApp>
    </configuration>
</plugin>
{code}
the {{<contextPath>}} is not honored.

The configuration only works with {{<contextPath>}} is put outside of {{<webApp>}}.

I believe also other settings within {{<webApp>}} are not honored, but {{<contextPath>}} is immediately visible and testable.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

[jira] (JETTY-1494) jetty:run-forked does not honor <webApp> configuration

JIRA jira@codehaus.org

    [ https://jira.codehaus.org/browse/JETTY-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293447#comment-293447 ]

Jan Bartel commented on JETTY-1494:
-----------------------------------

Simone,

Yes, this is clearly stated in the docs here:
http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin#jetty:run-forked__:__Running_an_unassembled_webapp_in_a_separate_jvm

The reason is that the <webApp> you are configuring is the WebAppContext instance that belongs to the plugin, *not* that of the WebAppContext created by the forked jvm.

Transfering the config of the <webApp> instance in the pom to the instance in the forked jvm is not trivial, so I decided that we would only expose some configuration options for it, and see how that suits users who want a forked execution.  Most users who want a forked execution don't also want to use it non-forked, so I don't believe that the pom is cluttered with 2 different configs, although I welcome feedback on that.

I'm changing this to an enhancement request and if there's enough interest we can try and figure out a reasonable way of transferring the <webApp> to the forked jvm.

cheers
Jan


               

> jetty:run-forked does not honor <webApp> configuration
> ------------------------------------------------------
>
>                 Key: JETTY-1494
>                 URL: https://jira.codehaus.org/browse/JETTY-1494
>             Project: Jetty
>          Issue Type: Bug
>          Components: Maven
>    Affects Versions: 7.6.1
>            Reporter: Simone Bordet
>            Assignee: Jan Bartel
>
> When specifying a configuration for {{jetty:run-forked}} of
> {code}
> <plugin>
>     <groupId>org.mortbay.jetty</groupId>
>     <artifactId>jetty-maven-plugin</artifactId>
>     <version>${project.version}</version>
>     <configuration>
>         <stopPort>8888</stopPort>
>         <stopKey>quit</stopKey>
>         <webApp>
>             <contextPath>/</contextPath>
>         </webApp>
>     </configuration>
> </plugin>
> {code}
> the {{<contextPath>}} is not honored.
> The configuration only works with {{<contextPath>}} is put outside of {{<webApp>}}.
> I believe also other settings within {{<webApp>}} are not honored, but {{<contextPath>}} is immediately visible and testable.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

[jira] (JETTY-1494) jetty:run-forked does not honor <webApp> configuration

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

     [ https://jira.codehaus.org/browse/JETTY-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Bartel updated JETTY-1494:
------------------------------

    Issue Type: Improvement  (was: Bug)
   

> jetty:run-forked does not honor <webApp> configuration
> ------------------------------------------------------
>
>                 Key: JETTY-1494
>                 URL: https://jira.codehaus.org/browse/JETTY-1494
>             Project: Jetty
>          Issue Type: Improvement
>          Components: Maven
>    Affects Versions: 7.6.1
>            Reporter: Simone Bordet
>            Assignee: Jan Bartel
>
> When specifying a configuration for {{jetty:run-forked}} of
> {code}
> <plugin>
>     <groupId>org.mortbay.jetty</groupId>
>     <artifactId>jetty-maven-plugin</artifactId>
>     <version>${project.version}</version>
>     <configuration>
>         <stopPort>8888</stopPort>
>         <stopKey>quit</stopKey>
>         <webApp>
>             <contextPath>/</contextPath>
>         </webApp>
>     </configuration>
> </plugin>
> {code}
> the {{<contextPath>}} is not honored.
> The configuration only works with {{<contextPath>}} is put outside of {{<webApp>}}.
> I believe also other settings within {{<webApp>}} are not honored, but {{<contextPath>}} is immediately visible and testable.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

[jira] (JETTY-1494) jetty:run-forked does not honor <webApp> configuration

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org
Jan Bartel resolved Improvement JETTY-1494 as Won't Fix

Agreed it would be desirable, but any solution seems too fragile to bother with. This behaviour is documented as mentioned previously. Closing this issue for now. Reopen if you think of an elegant way to handle this.

Jan

Change By: Jan Bartel (03/Sep/12 1:45 AM)
Resolution: Won't Fix
Status: Open Resolved
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
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email