Due to obviously correct advice, the vote is canceled.
I'll try to promote a new build as soon as i can.
Brian, how can we have the catalog auto-generated for central on sync or
weekly ?
Regards,
Raphaël
2009/5/4 Brett Porter br...@apache.org
Also, I thought having the archetype catalog
We could create a CLI tool out of Nexus Archetype Plugin in similar manner
as Nexus Indexer CLI exists (or even make those two CLIs
one?) Naturally, the Archetype CLI would required Nexus Indexer CLI (to be
able to use Nexus Index to generate the catalog).
Of course, if there is some other
Maybe that code could be rolled into the indexer since it's the source
of the data.
Tamás Cservenák wrote:
We could create a CLI tool out of Nexus Archetype Plugin in similar manner
as Nexus Indexer CLI exists (or even make those two CLIs
one?) Naturally, the Archetype CLI would required
Don't we already have the archetype:crawl mojo?
On 05/05/2009, at 3:52 AM, Brian Fox wrote:
Maybe that code could be rolled into the indexer since it's the
source of the data.
Tamás Cservenák wrote:
We could create a CLI tool out of Nexus Archetype Plugin in similar
manner
as Nexus
Why crawl the repo a second time? Tamas has code to generate the
archetype data directly from the index.
Brett Porter wrote:
Don't we already have the archetype:crawl mojo?
On 05/05/2009, at 3:52 AM, Brian Fox wrote:
Maybe that code could be rolled into the indexer since it's the
source of
On 05/05/2009, at 10:16 AM, Brian Fox wrote:
Why crawl the repo a second time? Tamas has code to generate the
archetype data directly from the index.
True. Is there a way for the indexer to generate it during the first
crawl? Putting it into the index and pulling it back out again seems
Yeah, that's what made me think about combining them.
Brett Porter wrote:
On 05/05/2009, at 10:16 AM, Brian Fox wrote:
Why crawl the repo a second time? Tamas has code to generate the
archetype data directly from the index.
True. Is there a way for the indexer to generate it during the
