Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 405224 - repository not created if mvn verify used (instead of mvn install)
Summary: repository not created if mvn verify used (instead of mvn install)
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 4.2.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Releng-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-08 20:21 EDT by David Williams CLA
Modified: 2013-04-12 16:42 EDT (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 David Williams CLA 2013-04-08 20:21:56 EDT 
I've not systematically had a chance to study this, but appears, doing local test builds, if I use 

mvn clean verify

as recommended in bug 403352 comment 44. 

There could be other reasons for it ... but ... I'm going to switch back to mvn clean install, and see if it works. 

If 'install' works and 'verify' does not, it makes me wonder if something else is defined wrong. This is the full text of the error I was getting (which is one that comes from our scripts, not from Tycho or Maven, per se. 

 ERROR: /shared/eclipse/builds/4I/master/gitCache/eclipse.platform.releng.aggregator/eclipse.platform.repository/target/repository did not exist in fn-slice-repo

But eclipse.platform.repository/target/repository is our "main" repository, that should have everything in it.
Comment 1 David Williams CLA 2013-04-12 16:42:23 EDT 
I think this works as expected after all. I think the failure observed was due to other failures that were not well captured. 

While not scientifically studied, using mvn verify ends up leaving a "localMavenRepo" of about 200 Megabytes (pre-reqs, tools, etc., I assume) but using mvn install was leaving a localMavenRepo of over 8 Gigabytes! In contrast, our resulting p2 repositories are about 550 Megabytes each. Would be interesting to know what else is in that 8 gigabytes when we "install" instead of "verify"!