|
Rebuilding local repo metadata using nexus code
Some parts of this message have been removed.
Learn more about Nabble's security policy.
Hi,
I'd like to put together a command line tool for rebuilding a local repository's metadata. Do you think this would be doable by reusing some of the nexus code?
The reason I'd like to do this, is that we run nightly cleanup scripts on our build server that removes unused artifacts and old snapshots. But this is not reflected in the metadata and various plugins we use breaks.
Cheers,
Henric
________________________________
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose to
others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official business of
this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road, London SE1
8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
|
|
Re: Rebuilding local repo metadata using nexus code
I would say that this should be done through a maven plugin and the code donated. Actually, the clean up thing should be a mojo/plugin goal which correctly updates the metadata. Have a look at this goal in the dependency plugin. If it lacks something you need, add it and submit a patch:
http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html/Anders
On Fri, Nov 13, 2009 at 12:18, Henric Larsson <Henric.Larsson@...> wrote:
Hi,
I'd like to put together a command line tool for rebuilding a local repository's metadata. Do you think this would be doable by reusing some of the nexus code?
The reason I'd like to do this, is that we run nightly cleanup scripts on our build server that removes unused artifacts and old snapshots. But this is not reflected in the metadata and various plugins we use breaks.
Cheers,
Henric
________________________________
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose to
others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official business of
this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road, London SE1
8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
|
|
RE: Rebuilding local repo metadata using nexus code
The problem with the dependency plugin is that it works with an existing project, and looks at that projects current dependencies.
The plugin/tool I have in mind works with an entire local repo, and essentially rebuilds all metadata. Just like the rebuild metadata option in nexus.
It might be good to have a plugin that cleans up and at the same time updates the metadata, but then you'd be left out of luck if and when the local repo
gets corrupted.
Cheers,
Henric
I would say that this should be done through a maven plugin and the code donated. Actually, the clean up thing should be a mojo/plugin goal which correctly updates the metadata.
Have a look at this goal in the dependency plugin. If it lacks something you need, add it and submit a patch:
http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html
/Anders
On Fri, Nov 13, 2009 at 12:18, Henric Larsson
<Henric.Larsson@...> wrote:
Hi,
I'd like to put together a command line tool for rebuilding a local repository's metadata. Do you think this would be doable by reusing some of the nexus code?
The reason I'd like to do this, is that we run nightly cleanup scripts on our build server that removes unused artifacts and old snapshots. But this is not reflected in the metadata and various plugins we use breaks.
Cheers,
Henric
________________________________
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose to
others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official business of
this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road, London SE1
8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose
to others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official business
of this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road, London
SE1 8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
|
|
Re: Rebuilding local repo metadata using nexus code
IMO, LocalRepo should be considered transient... The RemoteRepo is the eternal one...
So, in your case, IF you have MRM (and you should!) the fix is trivial:
1. rm -Rf <m2-local-repo>
2. rebuild
And you will end up in populated local repo in no time.
Hope helps, ~t~ On Fri, Nov 13, 2009 at 12:50 PM, Henric Larsson <Henric.Larsson@...> wrote:
The problem with the dependency plugin is that it works with an existing project, and looks at that projects current dependencies.
The plugin/tool I have in mind works with an entire local repo, and essentially rebuilds all metadata. Just like the rebuild metadata option in nexus.
It might be good to have a plugin that cleans up and at the same time updates the metadata, but then you'd be left out of luck if and when the local repo
gets corrupted.
Cheers,
Henric
I would say that this should be done through a maven plugin and the code donated. Actually, the clean up thing should be a mojo/plugin goal which correctly updates the metadata.
Have a look at this goal in the dependency plugin. If it lacks something you need, add it and submit a patch:
http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html
/Anders
On Fri, Nov 13, 2009 at 12:18, Henric Larsson
<Henric.Larsson@...> wrote:
Hi,
I'd like to put together a command line tool for rebuilding a local repository's metadata. Do you think this would be doable by reusing some of the nexus code?
The reason I'd like to do this, is that we run nightly cleanup scripts on our build server that removes unused artifacts and old snapshots. But this is not reflected in the metadata and various plugins we use breaks.
Cheers,
Henric
________________________________
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose to
others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official business of
this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road, London SE1
8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose
to others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official business
of this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road, London
SE1 8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
|
|
Re: Rebuilding local repo metadata using nexus code
Well, you could include a goal in that plugin that only updated the metadata. The limitations are only in your mind. :-) But you're right, the plugin is maybe not what you need. Write a new plugin and donate it. You most likely can re-use some of the logic in the dependency-plugin. (reuse by copy, but still)
/Anders On Fri, Nov 13, 2009 at 12:50, Henric Larsson <Henric.Larsson@...> wrote:
The problem with the dependency plugin is that it works with an existing project, and looks at that projects current dependencies.
The plugin/tool I have in mind works with an entire local repo, and essentially rebuilds all metadata. Just like the rebuild metadata option in nexus.
It might be good to have a plugin that cleans up and at the same time updates the metadata, but then you'd be left out of luck if and when the local repo
gets corrupted.
Cheers,
Henric
I would say that this should be done through a maven plugin and the code donated. Actually, the clean up thing should be a mojo/plugin goal which correctly updates the metadata.
Have a look at this goal in the dependency plugin. If it lacks something you need, add it and submit a patch:
http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html
/Anders
On Fri, Nov 13, 2009 at 12:18, Henric Larsson
<Henric.Larsson@...> wrote:
Hi,
I'd like to put together a command line tool for rebuilding a local repository's metadata. Do you think this would be doable by reusing some of the nexus code?
The reason I'd like to do this, is that we run nightly cleanup scripts on our build server that removes unused artifacts and old snapshots. But this is not reflected in the metadata and various plugins we use breaks.
Cheers,
Henric
________________________________
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose to
others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official business of
this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road, London SE1
8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose
to others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official business
of this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road, London
SE1 8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
|
|
RE: Rebuilding local repo metadata using nexus code
Ok, I'll try to explain a little bit about my scenario.
To begin with, I'm trying to do avoid the rm -Rf solution, it's fine if you've got a few developers, it won't put to much of a strain on the remote repo,
but:
Local repo corruptions does happen from time to time, so developers are advised to delete the local repo if they suspect this being the case. The problem
though is that it's not always clear that a problem is due to a dodgy local repo, so time is wasted finding this out.
We've got hundreds of developers, so there's a lot of time wasted, and a lot of frustration especially from developers that don't know or care much about
maven but just expect it to work. So we try to setup automatic routines to deal with this.
Now we could automate a full clean of the local repo daily, but then that would hit the remote repo quite badly each morning and it's not a scalable solution.
So I'm trying to come up with something that can keep the local repo in a healthy state for longer without constantly refreshing from the remote repo.
IMO, LocalRepo should be considered transient...
The RemoteRepo is the eternal one...
So, in your case, IF you have MRM (and you should!) the fix is trivial:
1. rm -Rf <m2-local-repo>
2. rebuild
And you will end up in populated local repo in no time.
Hope helps,
~t~
On Fri, Nov 13, 2009 at 12:50 PM, Henric Larsson
<Henric.Larsson@...> wrote:
The problem with the dependency plugin is that it works with an existing project, and looks at that projects current dependencies.
The plugin/tool I have in mind works with an entire local repo, and essentially rebuilds all metadata. Just like the rebuild metadata option in nexus.
It might be good to have a plugin that cleans up and at the same time updates the metadata, but then you'd be left out of luck if and when the local repo gets corrupted.
Cheers,
Henric
I would say that this should be done through a maven plugin and the code donated. Actually, the clean up thing should be a mojo/plugin goal which correctly updates the metadata.
Have a look at this goal in the dependency plugin. If it lacks something you need, add it and submit a patch:
http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html
/Anders
On Fri, Nov 13, 2009 at 12:18, Henric Larsson
<Henric.Larsson@...> wrote:
Hi,
I'd like to put together a command line tool for rebuilding a local repository's metadata. Do you think this would be doable by reusing some of the nexus code?
The reason I'd like to do this, is that we run nightly cleanup scripts on our build server that removes unused artifacts and old snapshots. But this is not reflected in the metadata and various plugins we use breaks.
Cheers,
Henric
________________________________
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose to
others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official business of
this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road, London SE1
8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy,
use or disclose to others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official
business of this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road,
London SE1 8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose
to others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official business
of this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road, London
SE1 8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
|
|
Re: Rebuilding local repo metadata using nexus code
I'm voting for a solution where you create a maven plugin that removes artifacts (according to a include/exclude list) and also fixes the metadata. You can most likely reuse a lot of code from the dependency plugin.
/Anders On Fri, Nov 13, 2009 at 13:31, Henric Larsson <Henric.Larsson@...> wrote:
Ok, I'll try to explain a little bit about my scenario.
To begin with, I'm trying to do avoid the rm -Rf solution, it's fine if you've got a few developers, it won't put to much of a strain on the remote repo,
but:
Local repo corruptions does happen from time to time, so developers are advised to delete the local repo if they suspect this being the case. The problem
though is that it's not always clear that a problem is due to a dodgy local repo, so time is wasted finding this out.
We've got hundreds of developers, so there's a lot of time wasted, and a lot of frustration especially from developers that don't know or care much about
maven but just expect it to work. So we try to setup automatic routines to deal with this.
Now we could automate a full clean of the local repo daily, but then that would hit the remote repo quite badly each morning and it's not a scalable solution.
So I'm trying to come up with something that can keep the local repo in a healthy state for longer without constantly refreshing from the remote repo.
Hence the wish for having a "Rebuild metadata" option for the local repository.
Any thoughts? Am I'm doing it all wrong?
Cheers,
Henric
IMO, LocalRepo should be considered transient...
The RemoteRepo is the eternal one...
So, in your case, IF you have MRM (and you should!) the fix is trivial:
1. rm -Rf <m2-local-repo>
2. rebuild
And you will end up in populated local repo in no time.
Hope helps,
~t~
On Fri, Nov 13, 2009 at 12:50 PM, Henric Larsson
<Henric.Larsson@...> wrote:
The problem with the dependency plugin is that it works with an existing project, and looks at that projects current dependencies.
The plugin/tool I have in mind works with an entire local repo, and essentially rebuilds all metadata. Just like the rebuild metadata option in nexus.
It might be good to have a plugin that cleans up and at the same time updates the metadata, but then you'd be left out of luck if and when the local repo gets corrupted.
Cheers,
Henric
I would say that this should be done through a maven plugin and the code donated. Actually, the clean up thing should be a mojo/plugin goal which correctly updates the metadata.
Have a look at this goal in the dependency plugin. If it lacks something you need, add it and submit a patch:
http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html
/Anders
On Fri, Nov 13, 2009 at 12:18, Henric Larsson
<Henric.Larsson@...> wrote:
Hi,
I'd like to put together a command line tool for rebuilding a local repository's metadata. Do you think this would be doable by reusing some of the nexus code?
The reason I'd like to do this, is that we run nightly cleanup scripts on our build server that removes unused artifacts and old snapshots. But this is not reflected in the metadata and various plugins we use breaks.
Cheers,
Henric
________________________________
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose to
others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official business of
this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road, London SE1
8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy,
use or disclose to others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official
business of this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road,
London SE1 8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose
to others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official business
of this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road, London
SE1 8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
|
|
Re: Rebuilding local repo metadata using nexus code
Btw, you do have a corporate repo manager that proxies central (and other remote repos)? If not, this is what you should get to start with. /Anders On Fri, Nov 13, 2009 at 13:31, Henric Larsson <Henric.Larsson@...> wrote:
Ok, I'll try to explain a little bit about my scenario.
To begin with, I'm trying to do avoid the rm -Rf solution, it's fine if you've got a few developers, it won't put to much of a strain on the remote repo,
but:
Local repo corruptions does happen from time to time, so developers are advised to delete the local repo if they suspect this being the case. The problem
though is that it's not always clear that a problem is due to a dodgy local repo, so time is wasted finding this out.
We've got hundreds of developers, so there's a lot of time wasted, and a lot of frustration especially from developers that don't know or care much about
maven but just expect it to work. So we try to setup automatic routines to deal with this.
Now we could automate a full clean of the local repo daily, but then that would hit the remote repo quite badly each morning and it's not a scalable solution.
So I'm trying to come up with something that can keep the local repo in a healthy state for longer without constantly refreshing from the remote repo.
Hence the wish for having a "Rebuild metadata" option for the local repository.
Any thoughts? Am I'm doing it all wrong?
Cheers,
Henric
IMO, LocalRepo should be considered transient...
The RemoteRepo is the eternal one...
So, in your case, IF you have MRM (and you should!) the fix is trivial:
1. rm -Rf <m2-local-repo>
2. rebuild
And you will end up in populated local repo in no time.
Hope helps,
~t~
On Fri, Nov 13, 2009 at 12:50 PM, Henric Larsson
<Henric.Larsson@...> wrote:
The problem with the dependency plugin is that it works with an existing project, and looks at that projects current dependencies.
The plugin/tool I have in mind works with an entire local repo, and essentially rebuilds all metadata. Just like the rebuild metadata option in nexus.
It might be good to have a plugin that cleans up and at the same time updates the metadata, but then you'd be left out of luck if and when the local repo gets corrupted.
Cheers,
Henric
I would say that this should be done through a maven plugin and the code donated. Actually, the clean up thing should be a mojo/plugin goal which correctly updates the metadata.
Have a look at this goal in the dependency plugin. If it lacks something you need, add it and submit a patch:
http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html
/Anders
On Fri, Nov 13, 2009 at 12:18, Henric Larsson
<Henric.Larsson@...> wrote:
Hi,
I'd like to put together a command line tool for rebuilding a local repository's metadata. Do you think this would be doable by reusing some of the nexus code?
The reason I'd like to do this, is that we run nightly cleanup scripts on our build server that removes unused artifacts and old snapshots. But this is not reflected in the metadata and various plugins we use breaks.
Cheers,
Henric
________________________________
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose to
others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official business of
this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road, London SE1
8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy,
use or disclose to others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official
business of this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road,
London SE1 8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose
to others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official business
of this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road, London
SE1 8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
|
|
RE: Rebuilding local repo metadata using nexus code
I hear you, but my initial question was whether it would be feasible to reuse the code from Nexus that does the rebuild index bit.
And yes, we have a corporate repo manager, wouldn't be asking question on this list otherwise would I? :)
I'm voting for a solution where you create a maven plugin that removes artifacts (according to a include/exclude list) and also fixes the metadata. You can most likely reuse a lot of code from the dependency plugin.
/Anders
On Fri, Nov 13, 2009 at 13:31, Henric Larsson
<Henric.Larsson@...> wrote:
Ok, I'll try to explain a little bit about my scenario.
To begin with, I'm trying to do avoid the rm -Rf solution, it's fine if you've got a few developers, it won't put to much of a strain on the remote repo, but:
Local repo corruptions does happen from time to time, so developers are advised to delete the local repo if they suspect this being the case. The problem though is that it's not always
clear that a problem is due to a dodgy local repo, so time is wasted finding this out.
We've got hundreds of developers, so there's a lot of time wasted, and a lot of frustration especially from developers that don't know or care much about maven but just expect it
to work. So we try to setup automatic routines to deal with this.
Now we could automate a full clean of the local repo daily, but then that would hit the remote repo quite badly each morning and it's not a scalable solution. So I'm trying to come
up with something that can keep the local repo in a healthy state for longer without constantly refreshing from the remote repo.
Hence the wish for having a "Rebuild metadata" option for the local repository.
Any thoughts? Am I'm doing it all wrong?
Cheers,
Henric
IMO, LocalRepo should be considered transient...
The RemoteRepo is the eternal one...
So, in your case, IF you have MRM (and you should!) the fix is trivial:
1. rm -Rf <m2-local-repo>
2. rebuild
And you will end up in populated local repo in no time.
Hope helps,
~t~
On Fri, Nov 13, 2009 at 12:50 PM, Henric Larsson
<Henric.Larsson@...> wrote:
The problem with the dependency plugin is that it works with an existing project, and looks at that projects current dependencies.
The plugin/tool I have in mind works with an entire local repo, and essentially rebuilds all metadata. Just like the rebuild metadata option in nexus.
It might be good to have a plugin that cleans up and at the same time updates the metadata, but then you'd be left out of luck if and when the local repo gets corrupted.
Cheers,
Henric
I would say that this should be done through a maven plugin and the code donated. Actually, the clean up thing should be a mojo/plugin goal which correctly updates the metadata.
Have a look at this goal in the dependency plugin. If it lacks something you need, add it and submit a patch:
http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html
/Anders
On Fri, Nov 13, 2009 at 12:18, Henric Larsson
<Henric.Larsson@...> wrote:
Hi,
I'd like to put together a command line tool for rebuilding a local repository's metadata. Do you think this would be doable by reusing some of the nexus code?
The reason I'd like to do this, is that we run nightly cleanup scripts on our build server that removes unused artifacts and old snapshots. But this is not reflected in the metadata and various plugins we use breaks.
Cheers,
Henric
________________________________
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose to
others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official business of
this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road, London SE1
8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or
disclose to others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official
business of this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road,
London SE1 8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy,
use or disclose to others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official
business of this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road,
London SE1 8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose
to others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official business
of this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road, London
SE1 8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
|
|
Re: Rebuilding local repo metadata using nexus code
Ok. The Sonatype people need to answer that. That code is for remote repo metadata though. There are differences. That's why I'm pointing at the dependency plugin - it updates local repo metadata. /Anders
On Fri, Nov 13, 2009 at 13:39, Henric Larsson <Henric.Larsson@...> wrote:
I hear you, but my initial question was whether it would be feasible to reuse the code from Nexus that does the rebuild index bit.
And yes, we have a corporate repo manager, wouldn't be asking question on this list otherwise would I? :)
Sent: 13 November 2009 12:35
To: nexus-user@...
Subject: Re: [nexus-user] Rebuilding local repo metadata using nexus code
I'm voting for a solution where you create a maven plugin that removes artifacts (according to a include/exclude list) and also fixes the metadata. You can most likely reuse a lot of code from the dependency plugin.
/Anders
On Fri, Nov 13, 2009 at 13:31, Henric Larsson
<Henric.Larsson@...> wrote:
Ok, I'll try to explain a little bit about my scenario.
To begin with, I'm trying to do avoid the rm -Rf solution, it's fine if you've got a few developers, it won't put to much of a strain on the remote repo, but:
Local repo corruptions does happen from time to time, so developers are advised to delete the local repo if they suspect this being the case. The problem though is that it's not always
clear that a problem is due to a dodgy local repo, so time is wasted finding this out.
We've got hundreds of developers, so there's a lot of time wasted, and a lot of frustration especially from developers that don't know or care much about maven but just expect it
to work. So we try to setup automatic routines to deal with this.
Now we could automate a full clean of the local repo daily, but then that would hit the remote repo quite badly each morning and it's not a scalable solution. So I'm trying to come
up with something that can keep the local repo in a healthy state for longer without constantly refreshing from the remote repo.
Hence the wish for having a "Rebuild metadata" option for the local repository.
Any thoughts? Am I'm doing it all wrong?
Cheers,
Henric
IMO, LocalRepo should be considered transient...
The RemoteRepo is the eternal one...
So, in your case, IF you have MRM (and you should!) the fix is trivial:
1. rm -Rf <m2-local-repo>
2. rebuild
And you will end up in populated local repo in no time.
Hope helps,
~t~
On Fri, Nov 13, 2009 at 12:50 PM, Henric Larsson
<Henric.Larsson@...> wrote:
The problem with the dependency plugin is that it works with an existing project, and looks at that projects current dependencies.
The plugin/tool I have in mind works with an entire local repo, and essentially rebuilds all metadata. Just like the rebuild metadata option in nexus.
It might be good to have a plugin that cleans up and at the same time updates the metadata, but then you'd be left out of luck if and when the local repo gets corrupted.
Cheers,
Henric
I would say that this should be done through a maven plugin and the code donated. Actually, the clean up thing should be a mojo/plugin goal which correctly updates the metadata.
Have a look at this goal in the dependency plugin. If it lacks something you need, add it and submit a patch:
http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html
/Anders
On Fri, Nov 13, 2009 at 12:18, Henric Larsson
<Henric.Larsson@...> wrote:
Hi,
I'd like to put together a command line tool for rebuilding a local repository's metadata. Do you think this would be doable by reusing some of the nexus code?
The reason I'd like to do this, is that we run nightly cleanup scripts on our build server that removes unused artifacts and old snapshots. But this is not reflected in the metadata and various plugins we use breaks.
Cheers,
Henric
________________________________
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose to
others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official business of
this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road, London SE1
8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or
disclose to others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official
business of this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road,
London SE1 8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy,
use or disclose to others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official
business of this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road,
London SE1 8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose
to others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official business
of this company shall be understood as neither given nor endorsed by it. IG Index Ltd is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road, London
SE1 8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
|
|
Re: Rebuilding local repo metadata using nexus code
I think you just need to delete all the metadata in the repo, then
rebuild and the metadata would be updated from the repo manager
without incurring much extra load because the jars would still be
cached on the local machines.
The nexus maven metadata process is much more involved and I don't
know how applicable it would be for a local repo. The current code
assumes that what is in the current repo is all the data that exists
for rebuilding (it's meant for repairing hosted repos). Therefore if
you were to run this on a repo with only 1 version present, the
resulting metadata would include only that version, not the rest of
them that may be present remotely.
On Fri, Nov 13, 2009 at 7:36 AM, Anders Hammar < anders@...> wrote:
> Btw, you do have a corporate repo manager that proxies central (and other
> remote repos)?
> If not, this is what you should get to start with.
>
> /Anders
>
> On Fri, Nov 13, 2009 at 13:31, Henric Larsson < Henric.Larsson@...>
> wrote:
>>
>> Ok, I'll try to explain a little bit about my scenario.
>>
>> To begin with, I'm trying to do avoid the rm -Rf solution, it's fine if
>> you've got a few developers, it won't put to much of a strain on the remote
>> repo, but:
>>
>> Local repo corruptions does happen from time to time, so developers are
>> advised to delete the local repo if they suspect this being the case. The
>> problem though is that it's not always clear that a problem is due to a
>> dodgy local repo, so time is wasted finding this out.
>>
>> We've got hundreds of developers, so there's a lot of time wasted, and a
>> lot of frustration especially from developers that don't know or care much
>> about maven but just expect it to work. So we try to setup automatic
>> routines to deal with this.
>>
>> Now we could automate a full clean of the local repo daily, but then that
>> would hit the remote repo quite badly each morning and it's not a scalable
>> solution. So I'm trying to come up with something that can keep the local
>> repo in a healthy state for longer without constantly refreshing from the
>> remote repo.
>>
>> Hence the wish for having a "Rebuild metadata" option for the local
>> repository.
>>
>> Any thoughts? Am I'm doing it all wrong?
>>
>> Cheers,
>> Henric
>>
>>
>>
>> ________________________________
>> From: t.cservenak@... [mailto: t.cservenak@...] On Behalf Of
>> Tamás Cservenák
>> Sent: 13 November 2009 11:54
>> To: nexus-user@...
>> Subject: Re: [nexus-user] Rebuilding local repo metadata using nexus code
>>
>> IMO, LocalRepo should be considered transient...
>> The RemoteRepo is the eternal one...
>> So, in your case, IF you have MRM (and you should!) the fix is trivial:
>> 1. rm -Rf <m2-local-repo>
>> 2. rebuild
>> And you will end up in populated local repo in no time.
>> Hope helps,
>> ~t~
>>
>> On Fri, Nov 13, 2009 at 12:50 PM, Henric Larsson
>> < Henric.Larsson@...> wrote:
>>>
>>> The problem with the dependency plugin is that it works with an existing
>>> project, and looks at that projects current dependencies.
>>>
>>> The plugin/tool I have in mind works with an entire local repo, and
>>> essentially rebuilds all metadata. Just like the rebuild metadata option in
>>> nexus.
>>>
>>> It might be good to have a plugin that cleans up and at the same time
>>> updates the metadata, but then you'd be left out of luck if and when the
>>> local repo gets corrupted.
>>>
>>> Cheers,
>>> Henric
>>>
>>>
>>> ________________________________
>>> From: anders.g.hammar@... [mailto: anders.g.hammar@...] On
>>> Behalf Of Anders Hammar
>>> Sent: 13 November 2009 11:23
>>> To: nexus-user@...
>>> Subject: Re: [nexus-user] Rebuilding local repo metadata using nexus code
>>>
>>> I would say that this should be done through a maven plugin and the code
>>> donated. Actually, the clean up thing should be a mojo/plugin goal which
>>> correctly updates the metadata.
>>> Have a look at this goal in the dependency plugin. If it lacks something
>>> you need, add it and submit a patch:
>>>
>>> http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html>>>
>>> /Anders
>>>
>>> On Fri, Nov 13, 2009 at 12:18, Henric Larsson
>>> < Henric.Larsson@...> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I'd like to put together a command line tool for rebuilding a local
>>>> repository's metadata. Do you think this would be doable by reusing some of
>>>> the nexus code?
>>>>
>>>> The reason I'd like to do this, is that we run nightly cleanup scripts
>>>> on our build server that removes unused artifacts and old snapshots. But
>>>> this is not reflected in the metadata and various plugins we use breaks.
>>>>
>>>> Cheers,
>>>> Henric
>>>>
>>>> ________________________________
>>>> The information contained in this email is strictly confidential and for
>>>> the use of the addressee only, unless otherwise indicated. If you are not
>>>> the intended recipient, please do not read, copy, use or disclose to others
>>>> this message or any attachment. Please also notify the sender by replying to
>>>> this email or by telephone (+44 (0)20 7896 0011) and then delete the email
>>>> and any copies of it. Opinions, conclusions (etc.) that do not relate to the
>>>> official business of this company shall be understood as neither given nor
>>>> endorsed by it. IG Index Ltd is a company registered in England and Wales
>>>> under number 01190902. VAT registration number 761 2978 07. Registered
>>>> Office: Friars House, 157-168 Blackfriars Road, London SE1 8EZ. Authorised
>>>> and regulated by the Financial Services Authority. FSA Register number
>>>> 114059.
>>>
>>>
>>> ________________________________
>>> The information contained in this email is strictly confidential and for
>>> the use of the addressee only, unless otherwise indicated. If you are not
>>> the intended recipient, please do not read, copy, use or disclose to others
>>> this message or any attachment. Please also notify the sender by replying to
>>> this email or by telephone (+44 (0)20 7896 0011) and then delete the email
>>> and any copies of it. Opinions, conclusions (etc.) that do not relate to the
>>> official business of this company shall be understood as neither given nor
>>> endorsed by it. IG Index Ltd is a company registered in England and Wales
>>> under number 01190902. VAT registration number 761 2978 07. Registered
>>> Office: Friars House, 157-168 Blackfriars Road, London SE1 8EZ. Authorised
>>> and regulated by the Financial Services Authority. FSA Register number
>>> 114059.
>>
>>
>> ________________________________
>> The information contained in this email is strictly confidential and for
>> the use of the addressee only, unless otherwise indicated. If you are not
>> the intended recipient, please do not read, copy, use or disclose to others
>> this message or any attachment. Please also notify the sender by replying to
>> this email or by telephone (+44 (0)20 7896 0011) and then delete the email
>> and any copies of it. Opinions, conclusions (etc.) that do not relate to the
>> official business of this company shall be understood as neither given nor
>> endorsed by it. IG Index Ltd is a company registered in England and Wales
>> under number 01190902. VAT registration number 761 2978 07. Registered
>> Office: Friars House, 157-168 Blackfriars Road, London SE1 8EZ. Authorised
>> and regulated by the Financial Services Authority. FSA Register number
>> 114059.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...
|
|
Re: Rebuilding local repo metadata using nexus code
+1 for that. Deleting metadata and having MRMs serve them as needed is a good solution.
And this solves the "repopulation" issue also, since the biggest content (JARs and other artifacts) will be still on the disk in local repo...
~t~ On Fri, Nov 13, 2009 at 1:47 PM, Brian Fox <brianf@...> wrote:
I think you just need to delete all the metadata in the repo, then
rebuild and the metadata would be updated from the repo manager
without incurring much extra load because the jars would still be
cached on the local machines.
The nexus maven metadata process is much more involved and I don't
know how applicable it would be for a local repo. The current code
assumes that what is in the current repo is all the data that exists
for rebuilding (it's meant for repairing hosted repos). Therefore if
you were to run this on a repo with only 1 version present, the
resulting metadata would include only that version, not the rest of
them that may be present remotely.
On Fri, Nov 13, 2009 at 7:36 AM, Anders Hammar < anders@...> wrote:
> Btw, you do have a corporate repo manager that proxies central (and other
> remote repos)?
> If not, this is what you should get to start with.
>
> /Anders
>
> On Fri, Nov 13, 2009 at 13:31, Henric Larsson < Henric.Larsson@...>
> wrote:
>>
>> Ok, I'll try to explain a little bit about my scenario.
>>
>> To begin with, I'm trying to do avoid the rm -Rf solution, it's fine if
>> you've got a few developers, it won't put to much of a strain on the remote
>> repo, but:
>>
>> Local repo corruptions does happen from time to time, so developers are
>> advised to delete the local repo if they suspect this being the case. The
>> problem though is that it's not always clear that a problem is due to a
>> dodgy local repo, so time is wasted finding this out.
>>
>> We've got hundreds of developers, so there's a lot of time wasted, and a
>> lot of frustration especially from developers that don't know or care much
>> about maven but just expect it to work. So we try to setup automatic
>> routines to deal with this.
>>
>> Now we could automate a full clean of the local repo daily, but then that
>> would hit the remote repo quite badly each morning and it's not a scalable
>> solution. So I'm trying to come up with something that can keep the local
>> repo in a healthy state for longer without constantly refreshing from the
>> remote repo.
>>
>> Hence the wish for having a "Rebuild metadata" option for the local
>> repository.
>>
>> Any thoughts? Am I'm doing it all wrong?
>>
>> Cheers,
>> Henric
>>
>>
>>
>> ________________________________
>> From: t.cservenak@... [mailto: t.cservenak@...] On Behalf Of
>> Tamás Cservenák
>> Sent: 13 November 2009 11:54
>> To: nexus-user@...
>> Subject: Re: [nexus-user] Rebuilding local repo metadata using nexus code
>>
>> IMO, LocalRepo should be considered transient...
>> The RemoteRepo is the eternal one...
>> So, in your case, IF you have MRM (and you should!) the fix is trivial:
>> 1. rm -Rf <m2-local-repo>
>> 2. rebuild
>> And you will end up in populated local repo in no time.
>> Hope helps,
>> ~t~
>>
>> On Fri, Nov 13, 2009 at 12:50 PM, Henric Larsson
>> < Henric.Larsson@...> wrote:
>>>
>>> The problem with the dependency plugin is that it works with an existing
>>> project, and looks at that projects current dependencies.
>>>
>>> The plugin/tool I have in mind works with an entire local repo, and
>>> essentially rebuilds all metadata. Just like the rebuild metadata option in
>>> nexus.
>>>
>>> It might be good to have a plugin that cleans up and at the same time
>>> updates the metadata, but then you'd be left out of luck if and when the
>>> local repo gets corrupted.
>>>
>>> Cheers,
>>> Henric
>>>
>>>
>>> ________________________________
>>> From: anders.g.hammar@... [mailto: anders.g.hammar@...] On
>>> Behalf Of Anders Hammar
>>> Sent: 13 November 2009 11:23
>>> To: nexus-user@...
>>> Subject: Re: [nexus-user] Rebuilding local repo metadata using nexus code
>>>
>>> I would say that this should be done through a maven plugin and the code
>>> donated. Actually, the clean up thing should be a mojo/plugin goal which
>>> correctly updates the metadata.
>>> Have a look at this goal in the dependency plugin. If it lacks something
>>> you need, add it and submit a patch:
>>>
>>> http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html
>>>
>>> /Anders
>>>
>>> On Fri, Nov 13, 2009 at 12:18, Henric Larsson
>>> < Henric.Larsson@...> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I'd like to put together a command line tool for rebuilding a local
>>>> repository's metadata. Do you think this would be doable by reusing some of
>>>> the nexus code?
>>>>
>>>> The reason I'd like to do this, is that we run nightly cleanup scripts
>>>> on our build server that removes unused artifacts and old snapshots. But
>>>> this is not reflected in the metadata and various plugins we use breaks.
>>>>
>>>> Cheers,
>>>> Henric
>>>>
>>>> ________________________________
>>>> The information contained in this email is strictly confidential and for
>>>> the use of the addressee only, unless otherwise indicated. If you are not
>>>> the intended recipient, please do not read, copy, use or disclose to others
>>>> this message or any attachment. Please also notify the sender by replying to
>>>> this email or by telephone (+44 (0)20 7896 0011) and then delete the email
>>>> and any copies of it. Opinions, conclusions (etc.) that do not relate to the
>>>> official business of this company shall be understood as neither given nor
>>>> endorsed by it. IG Index Ltd is a company registered in England and Wales
>>>> under number 01190902. VAT registration number 761 2978 07. Registered
>>>> Office: Friars House, 157-168 Blackfriars Road, London SE1 8EZ. Authorised
>>>> and regulated by the Financial Services Authority. FSA Register number
>>>> 114059.
>>>
>>>
>>> ________________________________
>>> The information contained in this email is strictly confidential and for
>>> the use of the addressee only, unless otherwise indicated. If you are not
>>> the intended recipient, please do not read, copy, use or disclose to others
>>> this message or any attachment. Please also notify the sender by replying to
>>> this email or by telephone (+44 (0)20 7896 0011) and then delete the email
>>> and any copies of it. Opinions, conclusions (etc.) that do not relate to the
>>> official business of this company shall be understood as neither given nor
>>> endorsed by it. IG Index Ltd is a company registered in England and Wales
>>> under number 01190902. VAT registration number 761 2978 07. Registered
>>> Office: Friars House, 157-168 Blackfriars Road, London SE1 8EZ. Authorised
>>> and regulated by the Financial Services Authority. FSA Register number
>>> 114059.
>>
>>
>> ________________________________
>> The information contained in this email is strictly confidential and for
>> the use of the addressee only, unless otherwise indicated. If you are not
>> the intended recipient, please do not read, copy, use or disclose to others
>> this message or any attachment. Please also notify the sender by replying to
>> this email or by telephone (+44 (0)20 7896 0011) and then delete the email
>> and any copies of it. Opinions, conclusions (etc.) that do not relate to the
>> official business of this company shall be understood as neither given nor
>> endorsed by it. IG Index Ltd is a company registered in England and Wales
>> under number 01190902. VAT registration number 761 2978 07. Registered
>> Office: Friars House, 157-168 Blackfriars Road, London SE1 8EZ. Authorised
>> and regulated by the Financial Services Authority. FSA Register number
>> 114059.
>
>
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...
|
