ion of the catalog in repo1)
> >
>
> Why don't you just setup archetype:crawl to be run periodically on the
> repo1 box?
>
> regards,
> Eugene
>
>
> --
> View this message in context:
> http://www.nabble.com/archetype-completely-broken-or-
e nexus index. talked with tamas some weeks ago to add
> this feature (the automatic creation of the catalog in repo1)
>
Why don't you just setup archetype:crawl to be run periodically on the
repo1 box?
regards,
Eugene
--
View this message in context:
http://www.nabble.co
Ok I probably did have a snapshot since I had built/deployed everything to the
new repo.
-Original Message-
From: Raphaël Piéroni [mailto:raphaelpier...@gmail.com]
Sent: Sunday, February 22, 2009 1:10 PM
To: Maven Developers List
Subject: Re: archetype completely broken or just me?
Are
Are you using the latest unreleased snapshot ?
If yep, that could be the problem.
The next release will change the default catalog location from internal
(created at release time using MAVENUSER) to
repo1/maven2/archetype-catalog.xml.
Obviously, that release will be postponed until the creation
I used it just day before yesterday, with no problems. Maybe you have a
corrupt file in your .m2 dir somewhere?
Brian E. Fox wrote:
[WARNING] Error reading archetype catalog http://repo1.maven.org/maven2
org.apache.maven.archetype.source.ArchetypeDataSourceException: Error
parsing ar
chetype
[WARNING] Error reading archetype catalog http://repo1.maven.org/maven2
org.apache.maven.archetype.source.ArchetypeDataSourceException: Error
parsing ar
chetype catalog.
at
org.apache.maven.archetype.source.CatalogArchetypeDataSource.readCata
log(CatalogArchetypeDataSource.java:202)
