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
<[email protected]> 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
<[email protected]> 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
<[email protected]> 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: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
