You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Florian R." <ro...@gmx.net> on 2010/04/21 12:37:07 UTC
maven-metadata-central.xml is missing versions in local repo
Hi,
I have a multi module build using maven 2.2.1 and artifactory 2.2.0.
The first submodule requests log4j 1.2.9 resulting in the files [1]
downloaded correctly.
The second submodule request log4j 1.2.14 resulting in some files added [2]
As you can see maven now creates a maven-metadata-central.xml [3] which only
contains log4j 1.2.15+16.
The build fails with:
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Couldn't find a version in [1.2.15, 1.2.16] to match range [1.2.9,1.2.9]
log4j:log4j:jar:null
But Version 1.2.9 is present in the file system!
I wipe out the local repo before the nightly build, this problem only
apperas every two or three weeks and at the moment I cannot say why. But at
the moment I have a VMWare Snapshot where I can reproduce it.
It also appereas also at some other artifacts, especially struts and
cobertura-maven-plugin.
***** [1] *****
D:\mavenrepo\log4j\log4j>dir /s
Datenträger in Laufwerk D: ist HUDSONDATA2
Datenträgernummer: F020-662E
Verzeichnis von D:\mavenrepo\log4j\log4j
21.04.2010 12:15 <DIR> .
21.04.2010 12:15 <DIR> ..
21.04.2010 12:16 <DIR> 1.2.9
0 Datei(en) 0 Bytes
Verzeichnis von D:\mavenrepo\log4j\log4j\1.2.9
21.04.2010 12:16 <DIR> .
21.04.2010 12:16 <DIR> ..
21.04.2010 12:16 352.291 log4j-1.2.9.jar
21.04.2010 12:16 40 log4j-1.2.9.jar.sha1
21.04.2010 12:16 40 log4j-1.2.9.jar.tmp.sha1.tmp
21.04.2010 12:15 144 log4j-1.2.9.pom
21.04.2010 12:15 40 log4j-1.2.9.pom.sha1
21.04.2010 12:15 40 log4j-1.2.9.pom.tmp.sha1.tmp
6 Datei(en) 352.595 Bytes
***** [2] *****
D:\mavenrepo\log4j\log4j>dir /s
Datenträger in Laufwerk D: ist HUDSONDATA2
Datenträgernummer: F020-662E
Verzeichnis von D:\mavenrepo\log4j\log4j
21.04.2010 12:18 <DIR> .
21.04.2010 12:18 <DIR> ..
21.04.2010 12:18 <DIR> 1.2.14
21.04.2010 12:18 <DIR> 1.2.9
21.04.2010 12:18 352 maven-metadata-central.xml
21.04.2010 12:18 40 maven-metadata-central.xml.sha1
2 Datei(en) 392 Bytes
Verzeichnis von D:\mavenrepo\log4j\log4j\1.2.14
21.04.2010 12:18 <DIR> .
21.04.2010 12:18 <DIR> ..
21.04.2010 12:18 2.374 log4j-1.2.14.pom
21.04.2010 12:18 40 log4j-1.2.14.pom.sha1
2 Datei(en) 2.414 Bytes
Verzeichnis von D:\mavenrepo\log4j\log4j\1.2.9
21.04.2010 12:18 <DIR> .
21.04.2010 12:18 <DIR> ..
21.04.2010 12:16 352.291 log4j-1.2.9.jar
21.04.2010 12:16 40 log4j-1.2.9.jar.sha1
21.04.2010 12:15 144 log4j-1.2.9.pom
21.04.2010 12:15 40 log4j-1.2.9.pom.sha1
4 Datei(en) 352.515 Bytes
***** [3] *****
<?xml version="1.0" encoding="UTF-8"?>
<metadata>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.15</version>
<versioning>
<release>1.2.16</release>
<versions>
<version>1.2.15</version>
<version>1.2.16</version>
</versions>
<lastUpdated>20100331042604</lastUpdated>
</versioning>
</metadata>
I am not sure which points to investigate next, it's such a strange bug.
Best Regards
Florian
--
View this message in context: http://old.nabble.com/maven-metadata-central.xml-is-missing-versions-in-local-repo-tp28288000p28288000.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-metadata-central.xml is missing versions in local repo
Posted by "Florian R." <ro...@gmx.net>.
Markku Saarela wrote:
>
> This can be caused by Artifactory if checksums does not match and you
> Artifactory is configured to fail if checksums doesn't match.
>
> Markku
>
Hi,
thank you for the suggestion, but our artifactory is configured to "ignore
and return generated checksums".
Florian
--
View this message in context: http://old.nabble.com/maven-metadata-central.xml-is-missing-versions-in-local-repo-tp28288000p28337643.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-metadata-central.xml is missing versions in local repo
Posted by Markku Saarela <ma...@iki.fi>.
This can be caused by Artifactory if checksums does not match and you
Artifactory is configured to fail if checksums doesn't match.
Markku
On 22.4.2010 12:53, Florian R. wrote:
>
>
> Wayne Fay wrote:
>
>> What MRM are you running -- Nexus, Artifactory, Archiva, etc? Are you
>> sure this is a problem in Maven and not something related to your MRM?
>>
>>
> We are running Artifactory 2.2.0.
> Maven downloads the files (no HTTP 404s or something like that) and can't
> find it afterwards. IMHO this is related to maven.
>
> We partially solved the problem now, it seems the log4j problem was releated
> to a parent pom containing a fixed version and that was confusing maven. But
> the problem is not reproducable with a simplyfied project using exact this
> constellation :(
>
> Does anyone know which fact forces maven to create the
> maven-metadata-central.xml to get some idea why this happens?
>
> Florian
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-metadata-central.xml is missing versions in local repo
Posted by "Florian R." <ro...@gmx.net>.
Wayne Fay wrote:
>
> What MRM are you running -- Nexus, Artifactory, Archiva, etc? Are you
> sure this is a problem in Maven and not something related to your MRM?
>
We are running Artifactory 2.2.0.
Maven downloads the files (no HTTP 404s or something like that) and can't
find it afterwards. IMHO this is related to maven.
We partially solved the problem now, it seems the log4j problem was releated
to a parent pom containing a fixed version and that was confusing maven. But
the problem is not reproducable with a simplyfied project using exact this
constellation :(
Does anyone know which fact forces maven to create the
maven-metadata-central.xml to get some idea why this happens?
Florian
--
View this message in context: http://old.nabble.com/maven-metadata-central.xml-is-missing-versions-in-local-repo-tp28288000p28326625.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Some problems with Archetype Plugin
Posted by Aleksey Didik <di...@magenta-technology.ru>.
Yes, it's a variant.
Thanks a lot.
Aleksey.
22.04.2010 20:14, Tim O'Brien пишет:
> Use archetype:create instead of archetype:generate
>
> See here: http://maven.apache.org/archetype/maven-archetype-plugin/create-mojo.html
>
> Tim
>
> On Thu, Apr 22, 2010 at 11:11 AM, Aleksey Didik
> <di...@magenta-technology.ru> wrote:
>
>> Thanks a lot, Tim.
>> Archetype can be found now, but Maven still try to get archetype catalog
>> from central and print connection fail error to console (we have a proxy).
>> Is it possible to prevent looking for catalog? I needn't to choose
>> archetype, I'm already know what I need.
>>
>> Best regards,
>> Aleksey.
>>
>> 22.04.2010 19:49, Tim O'Brien пишет:
>>
>>> Ok, got it, you'll need to specify the archetype repository. Pass
>>> in a -DarchetypeRepository=<url> that will likely point to your
>>> internal repository group.
>>>
>>> Here's a blog post I wrote ages ago, for Alfresco archetypes which
>>> uses this option: http://bit.ly/8YtLOh
>>>
>>> On Thu, Apr 22, 2010 at 9:58 AM, Aleksey Didik
>>> <di...@magenta-technology.ru> wrote:
>>>
>>>
>>>> Thanks for response, Tim.
>>>>
>>>> Yes, sure, it's my own archetype. I created it and deployed to our
>>>> company
>>>> Nexus.
>>>> Mirror is defined too. It can't be in central, because it's for internal
>>>> company usage only.
>>>> Question is how to generate project from this archetype in this case in
>>>> linking with problems, defined below.
>>>>
>>>> Aleksey.
>>>>
>>>>
>>>>
>>>> 22.04.2010 18:46, Tim O'Brien пишет:
>>>>
>>>>
>>>>> There is no archetype in Central with the artifactId
>>>>> "magenta-basic-project"
>>>>>
>>>>> Maybe you are trying to use an internal artifact? You email is from
>>>>> "magenta-technology.ru", and you are attempting to reference a
>>>>> "com.magenta" groupId. I'd suggest contacting others in your
>>>>> development group to find out what you should put in your
>>>>> ~/.m2/settings.xml. If you are using a repository manager, then you
>>>>> will need to define a mirror in your settings.xml.
>>>>>
>>>>> Tim
>>>>>
>>>>> On Thu, Apr 22, 2010 at 4:19 AM, Aleksey Didik
>>>>> <di...@magenta-technology.ru> wrote:
>>>>>
>>>>>
>>>>>
>>>>>> Hello all,
>>>>>>
>>>>>> I create my own archetype and deploy it to my company repository (Nexus
>>>>>> 1.5).
>>>>>> Now some developers try to use my archetype by calling:
>>>>>> mvn archetype:generate -DarchetypeGroupId=com.magenta.maven.archetypes
>>>>>> -DarchetypeArtifactId=magenta-basic-project
>>>>>> -DarchetypeVersion=0.1-SNAPSHOT
>>>>>>
>>>>>> Archetype plugin failed with unavailability to connect to central repo
>>>>>> and
>>>>>> said me: [WARNING] No archetype found in Remote catalog. Defaulting to
>>>>>> internal Catalog.
>>>>>>
>>>>>> We use proxy server, and it's ok that archetype plugin can't get
>>>>>> central
>>>>>> catalog.
>>>>>> My archetype is not registered in internal archetype-plugin catalog
>>>>>> (it's
>>>>>> predefined).
>>>>>> And my archetype is not registered in local repository catalog, because
>>>>>> it
>>>>>> was installed on another developer computer.
>>>>>> So, archetype plugin can't find my plugin in any available catalog on a
>>>>>> developer computer.
>>>>>>
>>>>>> So my question is: Is archetype-plugin really need to have information
>>>>>> about
>>>>>> archetype in archetype catalog to generate project from it???
>>>>>> And -DarchetypeGroupId=com.magenta.maven.archetypes
>>>>>> -DarchetypeArtifactId=magenta-basic-project
>>>>>> -DarchetypeVersion=0.1-SNAPSHOT
>>>>>> is not enough???
>>>>>> Just before I think, that plugin just looking for archetype in
>>>>>> repositories
>>>>>> like any another artifact.
>>>>>>
>>>>>> Please, solve my doubt.
>>>>>>
>>>>>> Best regards,
>>>>>> Aleksey Didik.
>>>>>>
>>>>>> P.S. Looks like I need to use nexus archetype plugin to create my nexus
>>>>>> archetype catalog and define it usage on a 'generate' goal.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Some problems with Archetype Plugin
Posted by Aleksey Didik <di...@magenta-technology.ru>.
Unfortunately yes :(
Just I need to show my archetype work on the local company "Tech Days".
And errors in console or no-interactive-mode is not good for me.
Aleksey.
22.04.2010 20:41, Wayne Fay пишет:
>> My archetype use interactive mode for defining some project properties.
>> But create goal don't allow to define it by console on a creation step.
>>
> I believe you can set all of those properties via -D... but it is not
> as user-friendly.
>
> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Some problems with Archetype Plugin
Posted by Wayne Fay <wa...@gmail.com>.
> My archetype use interactive mode for defining some project properties.
> But create goal don't allow to define it by console on a creation step.
I believe you can set all of those properties via -D... but it is not
as user-friendly.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Some problems with Archetype Plugin
Posted by Aleksey Didik <di...@magenta-technology.ru>.
Oh, no.
My archetype use interactive mode for defining some project properties.
But create goal don't allow to define it by console on a creation step.
Aleksey.
My archetype
22.04.2010 20:14, Tim O'Brien пишет:
> Use archetype:create instead of archetype:generate
>
> See here: http://maven.apache.org/archetype/maven-archetype-plugin/create-mojo.html
>
> Tim
>
> On Thu, Apr 22, 2010 at 11:11 AM, Aleksey Didik
> <di...@magenta-technology.ru> wrote:
>
>> Thanks a lot, Tim.
>> Archetype can be found now, but Maven still try to get archetype catalog
>> from central and print connection fail error to console (we have a proxy).
>> Is it possible to prevent looking for catalog? I needn't to choose
>> archetype, I'm already know what I need.
>>
>> Best regards,
>> Aleksey.
>>
>> 22.04.2010 19:49, Tim O'Brien пишет:
>>
>>> Ok, got it, you'll need to specify the archetype repository. Pass
>>> in a -DarchetypeRepository=<url> that will likely point to your
>>> internal repository group.
>>>
>>> Here's a blog post I wrote ages ago, for Alfresco archetypes which
>>> uses this option: http://bit.ly/8YtLOh
>>>
>>> On Thu, Apr 22, 2010 at 9:58 AM, Aleksey Didik
>>> <di...@magenta-technology.ru> wrote:
>>>
>>>
>>>> Thanks for response, Tim.
>>>>
>>>> Yes, sure, it's my own archetype. I created it and deployed to our
>>>> company
>>>> Nexus.
>>>> Mirror is defined too. It can't be in central, because it's for internal
>>>> company usage only.
>>>> Question is how to generate project from this archetype in this case in
>>>> linking with problems, defined below.
>>>>
>>>> Aleksey.
>>>>
>>>>
>>>>
>>>> 22.04.2010 18:46, Tim O'Brien пишет:
>>>>
>>>>
>>>>> There is no archetype in Central with the artifactId
>>>>> "magenta-basic-project"
>>>>>
>>>>> Maybe you are trying to use an internal artifact? You email is from
>>>>> "magenta-technology.ru", and you are attempting to reference a
>>>>> "com.magenta" groupId. I'd suggest contacting others in your
>>>>> development group to find out what you should put in your
>>>>> ~/.m2/settings.xml. If you are using a repository manager, then you
>>>>> will need to define a mirror in your settings.xml.
>>>>>
>>>>> Tim
>>>>>
>>>>> On Thu, Apr 22, 2010 at 4:19 AM, Aleksey Didik
>>>>> <di...@magenta-technology.ru> wrote:
>>>>>
>>>>>
>>>>>
>>>>>> Hello all,
>>>>>>
>>>>>> I create my own archetype and deploy it to my company repository (Nexus
>>>>>> 1.5).
>>>>>> Now some developers try to use my archetype by calling:
>>>>>> mvn archetype:generate -DarchetypeGroupId=com.magenta.maven.archetypes
>>>>>> -DarchetypeArtifactId=magenta-basic-project
>>>>>> -DarchetypeVersion=0.1-SNAPSHOT
>>>>>>
>>>>>> Archetype plugin failed with unavailability to connect to central repo
>>>>>> and
>>>>>> said me: [WARNING] No archetype found in Remote catalog. Defaulting to
>>>>>> internal Catalog.
>>>>>>
>>>>>> We use proxy server, and it's ok that archetype plugin can't get
>>>>>> central
>>>>>> catalog.
>>>>>> My archetype is not registered in internal archetype-plugin catalog
>>>>>> (it's
>>>>>> predefined).
>>>>>> And my archetype is not registered in local repository catalog, because
>>>>>> it
>>>>>> was installed on another developer computer.
>>>>>> So, archetype plugin can't find my plugin in any available catalog on a
>>>>>> developer computer.
>>>>>>
>>>>>> So my question is: Is archetype-plugin really need to have information
>>>>>> about
>>>>>> archetype in archetype catalog to generate project from it???
>>>>>> And -DarchetypeGroupId=com.magenta.maven.archetypes
>>>>>> -DarchetypeArtifactId=magenta-basic-project
>>>>>> -DarchetypeVersion=0.1-SNAPSHOT
>>>>>> is not enough???
>>>>>> Just before I think, that plugin just looking for archetype in
>>>>>> repositories
>>>>>> like any another artifact.
>>>>>>
>>>>>> Please, solve my doubt.
>>>>>>
>>>>>> Best regards,
>>>>>> Aleksey Didik.
>>>>>>
>>>>>> P.S. Looks like I need to use nexus archetype plugin to create my nexus
>>>>>> archetype catalog and define it usage on a 'generate' goal.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Some problems with Archetype Plugin
Posted by Tim O'Brien <to...@discursive.com>.
Use archetype:create instead of archetype:generate
See here: http://maven.apache.org/archetype/maven-archetype-plugin/create-mojo.html
Tim
On Thu, Apr 22, 2010 at 11:11 AM, Aleksey Didik
<di...@magenta-technology.ru> wrote:
> Thanks a lot, Tim.
> Archetype can be found now, but Maven still try to get archetype catalog
> from central and print connection fail error to console (we have a proxy).
> Is it possible to prevent looking for catalog? I needn't to choose
> archetype, I'm already know what I need.
>
> Best regards,
> Aleksey.
>
> 22.04.2010 19:49, Tim O'Brien пишет:
>>
>> Ok, got it, you'll need to specify the archetype repository. Pass
>> in a -DarchetypeRepository=<url> that will likely point to your
>> internal repository group.
>>
>> Here's a blog post I wrote ages ago, for Alfresco archetypes which
>> uses this option: http://bit.ly/8YtLOh
>>
>> On Thu, Apr 22, 2010 at 9:58 AM, Aleksey Didik
>> <di...@magenta-technology.ru> wrote:
>>
>>>
>>> Thanks for response, Tim.
>>>
>>> Yes, sure, it's my own archetype. I created it and deployed to our
>>> company
>>> Nexus.
>>> Mirror is defined too. It can't be in central, because it's for internal
>>> company usage only.
>>> Question is how to generate project from this archetype in this case in
>>> linking with problems, defined below.
>>>
>>> Aleksey.
>>>
>>>
>>>
>>> 22.04.2010 18:46, Tim O'Brien пишет:
>>>
>>>>
>>>> There is no archetype in Central with the artifactId
>>>> "magenta-basic-project"
>>>>
>>>> Maybe you are trying to use an internal artifact? You email is from
>>>> "magenta-technology.ru", and you are attempting to reference a
>>>> "com.magenta" groupId. I'd suggest contacting others in your
>>>> development group to find out what you should put in your
>>>> ~/.m2/settings.xml. If you are using a repository manager, then you
>>>> will need to define a mirror in your settings.xml.
>>>>
>>>> Tim
>>>>
>>>> On Thu, Apr 22, 2010 at 4:19 AM, Aleksey Didik
>>>> <di...@magenta-technology.ru> wrote:
>>>>
>>>>
>>>>>
>>>>> Hello all,
>>>>>
>>>>> I create my own archetype and deploy it to my company repository (Nexus
>>>>> 1.5).
>>>>> Now some developers try to use my archetype by calling:
>>>>> mvn archetype:generate -DarchetypeGroupId=com.magenta.maven.archetypes
>>>>> -DarchetypeArtifactId=magenta-basic-project
>>>>> -DarchetypeVersion=0.1-SNAPSHOT
>>>>>
>>>>> Archetype plugin failed with unavailability to connect to central repo
>>>>> and
>>>>> said me: [WARNING] No archetype found in Remote catalog. Defaulting to
>>>>> internal Catalog.
>>>>>
>>>>> We use proxy server, and it's ok that archetype plugin can't get
>>>>> central
>>>>> catalog.
>>>>> My archetype is not registered in internal archetype-plugin catalog
>>>>> (it's
>>>>> predefined).
>>>>> And my archetype is not registered in local repository catalog, because
>>>>> it
>>>>> was installed on another developer computer.
>>>>> So, archetype plugin can't find my plugin in any available catalog on a
>>>>> developer computer.
>>>>>
>>>>> So my question is: Is archetype-plugin really need to have information
>>>>> about
>>>>> archetype in archetype catalog to generate project from it???
>>>>> And -DarchetypeGroupId=com.magenta.maven.archetypes
>>>>> -DarchetypeArtifactId=magenta-basic-project
>>>>> -DarchetypeVersion=0.1-SNAPSHOT
>>>>> is not enough???
>>>>> Just before I think, that plugin just looking for archetype in
>>>>> repositories
>>>>> like any another artifact.
>>>>>
>>>>> Please, solve my doubt.
>>>>>
>>>>> Best regards,
>>>>> Aleksey Didik.
>>>>>
>>>>> P.S. Looks like I need to use nexus archetype plugin to create my nexus
>>>>> archetype catalog and define it usage on a 'generate' goal.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Some problems with Archetype Plugin
Posted by Aleksey Didik <di...@magenta-technology.ru>.
Thanks a lot, Tim.
Archetype can be found now, but Maven still try to get archetype catalog
from central and print connection fail error to console (we have a proxy).
Is it possible to prevent looking for catalog? I needn't to choose
archetype, I'm already know what I need.
Best regards,
Aleksey.
22.04.2010 19:49, Tim O'Brien пишет:
> Ok, got it, you'll need to specify the archetype repository. Pass
> in a -DarchetypeRepository=<url> that will likely point to your
> internal repository group.
>
> Here's a blog post I wrote ages ago, for Alfresco archetypes which
> uses this option: http://bit.ly/8YtLOh
>
> On Thu, Apr 22, 2010 at 9:58 AM, Aleksey Didik
> <di...@magenta-technology.ru> wrote:
>
>> Thanks for response, Tim.
>>
>> Yes, sure, it's my own archetype. I created it and deployed to our company
>> Nexus.
>> Mirror is defined too. It can't be in central, because it's for internal
>> company usage only.
>> Question is how to generate project from this archetype in this case in
>> linking with problems, defined below.
>>
>> Aleksey.
>>
>>
>>
>> 22.04.2010 18:46, Tim O'Brien пишет:
>>
>>> There is no archetype in Central with the artifactId
>>> "magenta-basic-project"
>>>
>>> Maybe you are trying to use an internal artifact? You email is from
>>> "magenta-technology.ru", and you are attempting to reference a
>>> "com.magenta" groupId. I'd suggest contacting others in your
>>> development group to find out what you should put in your
>>> ~/.m2/settings.xml. If you are using a repository manager, then you
>>> will need to define a mirror in your settings.xml.
>>>
>>> Tim
>>>
>>> On Thu, Apr 22, 2010 at 4:19 AM, Aleksey Didik
>>> <di...@magenta-technology.ru> wrote:
>>>
>>>
>>>> Hello all,
>>>>
>>>> I create my own archetype and deploy it to my company repository (Nexus
>>>> 1.5).
>>>> Now some developers try to use my archetype by calling:
>>>> mvn archetype:generate -DarchetypeGroupId=com.magenta.maven.archetypes
>>>> -DarchetypeArtifactId=magenta-basic-project
>>>> -DarchetypeVersion=0.1-SNAPSHOT
>>>>
>>>> Archetype plugin failed with unavailability to connect to central repo
>>>> and
>>>> said me: [WARNING] No archetype found in Remote catalog. Defaulting to
>>>> internal Catalog.
>>>>
>>>> We use proxy server, and it's ok that archetype plugin can't get central
>>>> catalog.
>>>> My archetype is not registered in internal archetype-plugin catalog (it's
>>>> predefined).
>>>> And my archetype is not registered in local repository catalog, because
>>>> it
>>>> was installed on another developer computer.
>>>> So, archetype plugin can't find my plugin in any available catalog on a
>>>> developer computer.
>>>>
>>>> So my question is: Is archetype-plugin really need to have information
>>>> about
>>>> archetype in archetype catalog to generate project from it???
>>>> And -DarchetypeGroupId=com.magenta.maven.archetypes
>>>> -DarchetypeArtifactId=magenta-basic-project
>>>> -DarchetypeVersion=0.1-SNAPSHOT
>>>> is not enough???
>>>> Just before I think, that plugin just looking for archetype in
>>>> repositories
>>>> like any another artifact.
>>>>
>>>> Please, solve my doubt.
>>>>
>>>> Best regards,
>>>> Aleksey Didik.
>>>>
>>>> P.S. Looks like I need to use nexus archetype plugin to create my nexus
>>>> archetype catalog and define it usage on a 'generate' goal.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Some problems with Archetype Plugin
Posted by Tim O'Brien <to...@discursive.com>.
Ok, got it, you'll need to specify the archetype repository. Pass
in a -DarchetypeRepository=<url> that will likely point to your
internal repository group.
Here's a blog post I wrote ages ago, for Alfresco archetypes which
uses this option: http://bit.ly/8YtLOh
On Thu, Apr 22, 2010 at 9:58 AM, Aleksey Didik
<di...@magenta-technology.ru> wrote:
> Thanks for response, Tim.
>
> Yes, sure, it's my own archetype. I created it and deployed to our company
> Nexus.
> Mirror is defined too. It can't be in central, because it's for internal
> company usage only.
> Question is how to generate project from this archetype in this case in
> linking with problems, defined below.
>
> Aleksey.
>
>
>
> 22.04.2010 18:46, Tim O'Brien пишет:
>>
>> There is no archetype in Central with the artifactId
>> "magenta-basic-project"
>>
>> Maybe you are trying to use an internal artifact? You email is from
>> "magenta-technology.ru", and you are attempting to reference a
>> "com.magenta" groupId. I'd suggest contacting others in your
>> development group to find out what you should put in your
>> ~/.m2/settings.xml. If you are using a repository manager, then you
>> will need to define a mirror in your settings.xml.
>>
>> Tim
>>
>> On Thu, Apr 22, 2010 at 4:19 AM, Aleksey Didik
>> <di...@magenta-technology.ru> wrote:
>>
>>>
>>> Hello all,
>>>
>>> I create my own archetype and deploy it to my company repository (Nexus
>>> 1.5).
>>> Now some developers try to use my archetype by calling:
>>> mvn archetype:generate -DarchetypeGroupId=com.magenta.maven.archetypes
>>> -DarchetypeArtifactId=magenta-basic-project
>>> -DarchetypeVersion=0.1-SNAPSHOT
>>>
>>> Archetype plugin failed with unavailability to connect to central repo
>>> and
>>> said me: [WARNING] No archetype found in Remote catalog. Defaulting to
>>> internal Catalog.
>>>
>>> We use proxy server, and it's ok that archetype plugin can't get central
>>> catalog.
>>> My archetype is not registered in internal archetype-plugin catalog (it's
>>> predefined).
>>> And my archetype is not registered in local repository catalog, because
>>> it
>>> was installed on another developer computer.
>>> So, archetype plugin can't find my plugin in any available catalog on a
>>> developer computer.
>>>
>>> So my question is: Is archetype-plugin really need to have information
>>> about
>>> archetype in archetype catalog to generate project from it???
>>> And -DarchetypeGroupId=com.magenta.maven.archetypes
>>> -DarchetypeArtifactId=magenta-basic-project
>>> -DarchetypeVersion=0.1-SNAPSHOT
>>> is not enough???
>>> Just before I think, that plugin just looking for archetype in
>>> repositories
>>> like any another artifact.
>>>
>>> Please, solve my doubt.
>>>
>>> Best regards,
>>> Aleksey Didik.
>>>
>>> P.S. Looks like I need to use nexus archetype plugin to create my nexus
>>> archetype catalog and define it usage on a 'generate' goal.
>>>
>>>
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Some problems with Archetype Plugin
Posted by Aleksey Didik <di...@magenta-technology.ru>.
Thanks for response, Tim.
Yes, sure, it's my own archetype. I created it and deployed to our
company Nexus.
Mirror is defined too. It can't be in central, because it's for internal
company usage only.
Question is how to generate project from this archetype in this case in
linking with problems, defined below.
Aleksey.
22.04.2010 18:46, Tim O'Brien пишет:
> There is no archetype in Central with the artifactId "magenta-basic-project"
>
> Maybe you are trying to use an internal artifact? You email is from
> "magenta-technology.ru", and you are attempting to reference a
> "com.magenta" groupId. I'd suggest contacting others in your
> development group to find out what you should put in your
> ~/.m2/settings.xml. If you are using a repository manager, then you
> will need to define a mirror in your settings.xml.
>
> Tim
>
> On Thu, Apr 22, 2010 at 4:19 AM, Aleksey Didik
> <di...@magenta-technology.ru> wrote:
>
>> Hello all,
>>
>> I create my own archetype and deploy it to my company repository (Nexus
>> 1.5).
>> Now some developers try to use my archetype by calling:
>> mvn archetype:generate -DarchetypeGroupId=com.magenta.maven.archetypes
>> -DarchetypeArtifactId=magenta-basic-project -DarchetypeVersion=0.1-SNAPSHOT
>>
>> Archetype plugin failed with unavailability to connect to central repo and
>> said me: [WARNING] No archetype found in Remote catalog. Defaulting to
>> internal Catalog.
>>
>> We use proxy server, and it's ok that archetype plugin can't get central
>> catalog.
>> My archetype is not registered in internal archetype-plugin catalog (it's
>> predefined).
>> And my archetype is not registered in local repository catalog, because it
>> was installed on another developer computer.
>> So, archetype plugin can't find my plugin in any available catalog on a
>> developer computer.
>>
>> So my question is: Is archetype-plugin really need to have information about
>> archetype in archetype catalog to generate project from it???
>> And -DarchetypeGroupId=com.magenta.maven.archetypes
>> -DarchetypeArtifactId=magenta-basic-project -DarchetypeVersion=0.1-SNAPSHOT
>> is not enough???
>> Just before I think, that plugin just looking for archetype in repositories
>> like any another artifact.
>>
>> Please, solve my doubt.
>>
>> Best regards,
>> Aleksey Didik.
>>
>> P.S. Looks like I need to use nexus archetype plugin to create my nexus
>> archetype catalog and define it usage on a 'generate' goal.
>>
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Some problems with Archetype Plugin
Posted by Tim O'Brien <to...@discursive.com>.
There is no archetype in Central with the artifactId "magenta-basic-project"
Maybe you are trying to use an internal artifact? You email is from
"magenta-technology.ru", and you are attempting to reference a
"com.magenta" groupId. I'd suggest contacting others in your
development group to find out what you should put in your
~/.m2/settings.xml. If you are using a repository manager, then you
will need to define a mirror in your settings.xml.
Tim
On Thu, Apr 22, 2010 at 4:19 AM, Aleksey Didik
<di...@magenta-technology.ru> wrote:
> Hello all,
>
> I create my own archetype and deploy it to my company repository (Nexus
> 1.5).
> Now some developers try to use my archetype by calling:
> mvn archetype:generate -DarchetypeGroupId=com.magenta.maven.archetypes
> -DarchetypeArtifactId=magenta-basic-project -DarchetypeVersion=0.1-SNAPSHOT
>
> Archetype plugin failed with unavailability to connect to central repo and
> said me: [WARNING] No archetype found in Remote catalog. Defaulting to
> internal Catalog.
>
> We use proxy server, and it's ok that archetype plugin can't get central
> catalog.
> My archetype is not registered in internal archetype-plugin catalog (it's
> predefined).
> And my archetype is not registered in local repository catalog, because it
> was installed on another developer computer.
> So, archetype plugin can't find my plugin in any available catalog on a
> developer computer.
>
> So my question is: Is archetype-plugin really need to have information about
> archetype in archetype catalog to generate project from it???
> And -DarchetypeGroupId=com.magenta.maven.archetypes
> -DarchetypeArtifactId=magenta-basic-project -DarchetypeVersion=0.1-SNAPSHOT
> is not enough???
> Just before I think, that plugin just looking for archetype in repositories
> like any another artifact.
>
> Please, solve my doubt.
>
> Best regards,
> Aleksey Didik.
>
> P.S. Looks like I need to use nexus archetype plugin to create my nexus
> archetype catalog and define it usage on a 'generate' goal.
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Some problems with Archetype Plugin
Posted by Aleksey Didik <di...@magenta-technology.ru>.
Hello all,
I create my own archetype and deploy it to my company repository (Nexus
1.5).
Now some developers try to use my archetype by calling:
mvn archetype:generate -DarchetypeGroupId=com.magenta.maven.archetypes
-DarchetypeArtifactId=magenta-basic-project -DarchetypeVersion=0.1-SNAPSHOT
Archetype plugin failed with unavailability to connect to central repo
and said me: [WARNING] No archetype found in Remote catalog. Defaulting
to internal Catalog.
We use proxy server, and it's ok that archetype plugin can't get central
catalog.
My archetype is not registered in internal archetype-plugin catalog
(it's predefined).
And my archetype is not registered in local repository catalog, because
it was installed on another developer computer.
So, archetype plugin can't find my plugin in any available catalog on a
developer computer.
So my question is: Is archetype-plugin really need to have information
about archetype in archetype catalog to generate project from it???
And -DarchetypeGroupId=com.magenta.maven.archetypes
-DarchetypeArtifactId=magenta-basic-project
-DarchetypeVersion=0.1-SNAPSHOT is not enough???
Just before I think, that plugin just looking for archetype in
repositories like any another artifact.
Please, solve my doubt.
Best regards,
Aleksey Didik.
P.S. Looks like I need to use nexus archetype plugin to create my nexus
archetype catalog and define it usage on a 'generate' goal.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-metadata-central.xml is missing versions in local repo
Posted by Wayne Fay <wa...@gmail.com>.
> from the specified remote repositories:
> central (http://maven.uniqa.at/artifacts/repo),
> snapshots (http://maven.uniqa.at/artifacts/repo)
What MRM are you running -- Nexus, Artifactory, Archiva, etc? Are you
sure this is a problem in Maven and not something related to your MRM?
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-metadata-central.xml is missing versions in local repo
Posted by "Florian R." <ro...@gmx.net>.
Hi,
Wayne Fay wrote:
>
> What does your pom file dependency to log4j look like?
>
> Wayne
>
>
This is the dependency:
<dependency>
<groupId>struts</groupId>
<artifactId>struts</artifactId>
</dependency>
Today's nightly build another project failed with
[INFO] Failed to resolve artifact.
No versions are present in the repository for the artifact with a range
[1.2.6,1.2.6]
org.codehaus.xfire:xfire-all:jar:null
from the specified remote repositories:
central (http://maven.uniqa.at/artifacts/repo),
snapshots (http://maven.uniqa.at/artifacts/repo)
with this dependency in the pom.xml
<groupId>org.codehaus.xfire</groupId>
<artifactId>xfire-all</artifactId>
<version>[1.2.6]</version>
Deleting the xfire folder from the local repo and running the build again
resolved the problem (and generated a correct metadata xml file).
Florian
--
View this message in context: http://old.nabble.com/maven-metadata-central.xml-is-missing-versions-in-local-repo-tp28288000p28325521.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-metadata-central.xml is missing versions in local repo
Posted by Wayne Fay <wa...@gmail.com>.
> [INFO] Failed to resolve artifact.
> Couldn't find a version in [1.2.15, 1.2.16] to match range [1.2.9,1.2.9]
> log4j:log4j:jar:null
What does your pom file dependency to log4j look like?
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org