This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 287518 - Dependency must be in base directory
Summary: Dependency must be in base directory
Status: CLOSED FIXED
Alias: None
Product: Tigerstripe (Archived)
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   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-08-25 02:36 EDT by Marc FLAUW CLA
Modified: 2012-04-17 09:41 EDT (History)
1 user (show)

See Also:

Attachments
SPM project with dependency at root (1.91 MB, application/x-zip-compressed)
2009-08-25 02:36 EDT, Marc FLAUW CLA 		no flags Details
View All 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 Marc FLAUW CLA 2009-08-25 02:36:24 EDT 
Created attachment 145514 [details]
SPM project with dependency at root

Hello,

I am using Tigerstripe 0.5 (0.5.0.200907102330NGT). 
I would like to add a module (tip_common_model_0.0.2_temp.zip) as a dependency of my project. 

This file is located in the sub-directory TigerstripeGenerators. 
If I add this file as a dependency, it seems to work and it creates a lib at the root of the project, but when I open this lib, the files in it are not recognized as Tigerstripe files: the source attachment does not contain the source for the file CapacityExceeded.class. I have tried to use the button to re-attch to the zip, either from the workspace or from an externla location, but no success.

However, if I moved this zip file at the root of the project, then it works fine. 

Today, this file is automatically provided by our maven build, so having to move it to the base directory is a strong inconvenience.

Best regards,

Marc