please open an enhancement request for this. Though I think that this
is probably not not very common scenario and it won't be high priority
for the project team. However we will be glad to take patch if someone
would want to implement this functionality. Or you can prove me wrong by
collecting votes on your enhancement requests.
The major problem with this is to how uniquely identify each index.
For example, "central" index could actually point to different
locations, especially after we will use mirrors configuration from
Maven's settings.xml
regards,
Eugene
Yang Gu wrote:
Hi,
I am working on different workspace and all project is base on
maven.Obviously the m2eclipse is the one of the most important tools
for our eclipse.It's very delightful seeing the m2eclipse get more
powerful day by day.Thanks for the m2eclipse teams.
But the m2eclipse use a repository index for every workspace, which
resided at $WORKSPACE$/.metadata/.plugins/org.maven.ide.eclipse.So
every workspace will update the index theirself ,but sometimes the
index zip file is very large such as the central maven index which is
24M.Forther more maybe workspace1 had updated all the index to the
latest,but the workspace2 still update the index again.So I think it's
must be more useful if m2eclipse use global maven repository index
setting instead of workspace level index setting.Do you think so?
Of cource ,To avoid repeat updating ,you can copy all the index from
the updated workspace to the workspace that required updating .
Thanks for the m2eclipse teams again.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
