This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 274636 - Artifact fails to create but no errors
Summary: Artifact fails to create but no errors
Status: RESOLVED WORKSFORME
Alias: None
Product: Tigerstripe (Archived)
Classification: Technology
Component: Core (show other bugs)
Version: 0.4.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 0.5M0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-01 07:15 EDT by Richard Craddock CLA
Modified: 2011-11-23 11:00 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Craddock CLA 2009-05-01 07:15:30 EDT 
I discovered this as we were importing the SID.

There is a package in the imported document called xxx.aux

'aux' is not a valid package name in eclipse apparently - the java editor will not let you create it.

Anyway, the artifact Manager will create it, and return it, and let you set the name of it, but the underlying file is never created. So an audit cleans up and the artifact just disappears. There are no exceptions thrown at any time

There appears to be no way to trap this situation at the moment. In the SID import case, the log file is clean, but the artifacts is simply not in the imported project - not ideal
Comment 1 Navid Mehregani CLA 2011-11-23 11:00:09 EST 
I'm able to create an 'aux' package and the artifacts in this package are not removed after a clean audit.  If this issue still exists, please reopen with more details.