Bug 1099724 - Jandex -m deletes jars when temp dir is on different filesystem
Summary: Jandex -m deletes jars when temp dir is on different filesystem
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Other
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: DR4
: EAP 6.4.0
Assignee: Rostislav Svoboda
QA Contact: Martin Svehla
URL:
Whiteboard:
: 1191751 (view as bug list)
Depends On:
Blocks: 1148021
TreeView+ depends on / blocked
 
Reported: 2014-05-21 04:18 UTC by James Livingston
Modified: 2019-08-19 12:43 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JANDEX-12 0 Major Resolved -m option does not work when temp dir is on different file system 2018-02-21 09:01:12 UTC
Red Hat Issue Tracker JANDEX-24 0 Major Resolved Jandex -m creates broken jar files 2018-02-21 09:01:12 UTC
Red Hat Knowledge Base (Solution) 890023 0 None None None Never

Description James Livingston 2014-05-21 04:18:45 UTC
If you use jandex wth -m (e.g. from an ant task with modify="true") and Java's temp directory is on a different filesystem, it can result in the jar being deleted.

Comment 2 James Livingston 2014-05-22 06:19:18 UTC
Without the fix for JANDEX-24 too, it will create corrupt files rather than deleting them.

Comment 3 JBoss JIRA Server 2014-05-23 04:37:12 UTC
James Livingston <jlivings> updated the status of jira JANDEX-24 to Resolved

Comment 4 Rostislav Svoboda 2014-09-30 11:27:25 UTC
EAP 6.x PR - https://github.com/jbossas/jboss-eap/pull/1742

Comment 5 Rostislav Svoboda 2014-09-30 12:06:18 UTC
KB article https://access.redhat.com/solutions/409293 is mentioning '-m' option

Comment 6 Martin Svehla 2014-10-13 09:58:21 UTC
Verified with EAP 6.4.0.DR4 (jandex 1.2.2.Final)

Comment 7 Tomaz Cerar 2015-02-11 22:07:33 UTC
*** Bug 1191751 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.