[
https://issues.jboss.org/browse/ARQ-569?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-569:
------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: glassfish_1.0.0.Final
Resolution: Done
pushed upstream
Archive for remote GF-3.1 should not be saved to disk prior to
deployment
-------------------------------------------------------------------------
Key: ARQ-569
URL:
https://issues.jboss.org/browse/ARQ-569
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: GlassFish Containers
Affects Versions: glassfish_1.0.0.CR1
Environment: Ubuntu 11.04 x86, GlassFish Server Open Source Edition 3.1.1 (build
12)
Reporter: Pedro Kowalski
Assignee: Pedro Kowalski
Fix For: glassfish_1.0.0.Final
When I build the deployment archive, it is saved it /tmp/ARCHIVE_FILENAME (I'm
running on GNU/Linux box) with chmod 444 (-r--r--r--). If I run the glassfish server as a
root or as the same user as the maven than there is no problem. But actually I run a
Jenkins build task (user: jenkins) and run the server as another user (user: pedro).
In such case, the Arquillian remote tests fail because the Glassfish cannot use the
/tmp/ARCHIVE_FILENAME (permission denied). If you change the chmod and give others the
write permission - it will work fine.
Aslak suggested avoiding the FileDataBodyPart during deployment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira