[shrinkwrap-issues] [JBoss JIRA] Commented: (SHRINKWRAP-197) Export archive to a temporary file name

[Dan Allen (JIRA)]

    [ https://jira.jboss.org/browse/SHRINKWRAP-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12537244#action_12537244 ] 

Dan Allen commented on SHRINKWRAP-197:
--------------------------------------

Actually, the context path is already being set in the ShrinkWrapWebAppContext (the jetty adapter)

this.setContextPath(ROOT + baseName);

So the name of the archive doesn't matter. In fact, Jetty immediately takes that archive and extracts it to another random temporary directory anyway, so it doubly doesn't matter what the archive is called.

> Export archive to a temporary file name
> ---------------------------------------
>
>                 Key: SHRINKWRAP-197
>                 URL: https://jira.jboss.org/browse/SHRINKWRAP-197
>             Project: ShrinkWrap
>          Issue Type: Bug
>          Components: ext-jetty
>    Affects Versions: 1.0.0-alpha-10
>            Reporter: Dan Allen
>            Assignee: Dan Allen
>             Fix For: 1.0.0-alpha-11
>
>
> The archive is exported to a file with the same name as the archive in the temporary directory. That file is set to be deleted when the JVM exits. However, if there is more than one deployment in the same test suite that uses the same test name (typically test.war), then the second deployment will fail because there is a file in the way.
> The expected behavior is that the archive is exported to a unique temporary file. It shouldn't matter what the name of the file is as its purpose is to pass the archive contents to Jetty to be extracted.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira