Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 363589 - still seeing some pollution of update sites in Java EE M3
Summary: still seeing some pollution of update sites in Java EE M3
Status: RESOLVED WORKSFORME
Alias: None
Product: EPP
Classification: Technology
Component: jee-package (show other bugs)
Version: 1.4.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 1.4.0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-11 10:16 EST by David Williams CLA
Modified: 2011-11-13 23:59 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 David Williams CLA 2011-11-11 10:16:45 EST 
Per bug 358415 there should not be many updated sites "pulled in" just by accessing the common repository. 

But, in M3 Java EE Package, I still see quite a few ... about 40 ... being pulled in. 

I'll need to investigate to see if I "regressed" the common site" or coming from somewhere else.
Comment 1 David Williams CLA 2011-11-11 10:18:09 EST 
Oh, you know, I bet these are coming from M1 site, still, since /releases/juno is a composite of M1 + M2 + M3. 

I'll confirm (and decide if anything needs to be done for M4 ... or, maybe by then they'll just fade away).
Comment 2 David Williams CLA 2011-11-13 23:59:13 EST 
I checked and this is a side effect of M1 still being in the composite. If I use only M2 and M3 as a composite, there are no extraneous ones picked up. So, for M4, when we limit the composite to M4, M3, and M2, there should be no extraneous ones added from common repo.