Archetype in nexus
|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
 |
Archetype in nexus
by Mansour Al Akeel
::
Rate this Message:
Hello all:
I have been trying to get nexus to reflect the archtypes I am using. For example: I have to build a project from hippo cms mvn archetype:generate\ -DarchetypeRepository=http://repository.hippocms.org/maven2\ -DarchetypeGroupId=org.onehippo.ecm.hst\ -DarchetypeArtifactId=hst-archetype\ -DarchetypeVersion=2.03.09\ -Dversion=1.01.00-SNAPSHOT\ -DgroupId=com.mycompany\ -DartifactId=myproject If I have built the artifacts on the same machine, I can use "mvn archetype:generate", but I want to make it availabe for other machines as well through a centeral nexus. Is there a way to make it available in my nexus without having to build and deploy it locally ? In other words just to use: mvn archetype:generate And see it there on the list from any machine. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: nexus-user-unsubscribe@... For additional commands, e-mail: nexus-user-help@... |
|
|
Re: Archetype in nexus
by Tamás Cservenák
::
Rate this Message:
Yes, there is: just deploy them on your central nexus, and add the archetype plugin to it too.
This way, all the deployed archetypes will become available in the published archetype catalog (published by plugin).
For this to work, you need this OSS plugin: ~t~
On Mon, Oct 26, 2009 at 1:36 AM, Mansour Al Akeel <mansour.alakeel@...> wrote: Hello all: |
|
|
Re: Archetype in nexus
by Mansour Al Akeel
::
Rate this Message:
Hello Tamas:
Thank you for your reply. What do you mean by "deploy them on your central Nexus" ? At this point I have to get the source code for the atchetype, and build it localy. If I need to make it available in my Nexux, then I have to deploy it to my central nexus. When newer versions of the archetype are released, then I have to repeat. Or just use the long formate to generate an archatype !! It will be great if the archtypes can be available the same way a dependecy, when used it's stored in nexes for the next time. I will try the plugin you suggested. But I don't know if that's what I need. Thank you. 2009/10/26 Tamás Cservenák <tamas@...>: > Yes, there is: just deploy them on your central nexus, and add the archetype > plugin to it too. > This way, all the deployed archetypes will become available in the published > archetype catalog (published by plugin). > For this to work, you need this OSS plugin: > https://docs.sonatype.org/display/Nexus/Nexus+Archetype+Plugin > ~t~ > > On Mon, Oct 26, 2009 at 1:36 AM, Mansour Al Akeel > <mansour.alakeel@...> wrote: >> >> Hello all: >> I have been trying to get nexus to reflect the archtypes I am using. >> For example: >> I have to build a project from hippo cms >> >> mvn archetype:generate\ >> -DarchetypeRepository=http://repository.hippocms.org/maven2\ >> -DarchetypeGroupId=org.onehippo.ecm.hst\ >> -DarchetypeArtifactId=hst-archetype\ >> -DarchetypeVersion=2.03.09\ >> -Dversion=1.01.00-SNAPSHOT\ >> -DgroupId=com.mycompany\ >> -DartifactId=myproject >> >> If I have built the artifacts on the same machine, I can use "mvn >> archetype:generate", but I want to make it availabe for other machines >> as well through a centeral nexus. >> Is there a way to make it available in my nexus without having to >> build and deploy it locally ? In other words just to use: >> >> mvn archetype:generate >> >> And see it there on the list from any machine. >> >> Thank you. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: nexus-user-unsubscribe@... >> For additional commands, e-mail: nexus-user-help@... >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: nexus-user-unsubscribe@... For additional commands, e-mail: nexus-user-help@... |
|
|
Re: Archetype in nexus
by Mansour Al Akeel
::
Rate this Message:
Ok, there's one thing I don't understand. I have added
http://scala-tools.org/repo-releases and I can see scala archetypes from this repo when I do "mvn archetype:generate". But I can not see archetypes from http://repository.hippocms.org/maven2/ . I added them both in the same way. I downloaded and installed the plugin you suggested, but no difference. what do I need to do ? Thank you. On Mon, Oct 26, 2009 at 10:31 AM, Mansour Al Akeel <mansour.alakeel@...> wrote: > Hello Tamas: > Thank you for your reply. > > What do you mean by "deploy them on your central Nexus" ? > At this point I have to get the source code for the atchetype, and > build it localy. If I need to make it available in my Nexux, then I > have to deploy it to my central nexus. When newer versions of the > archetype are released, then I have to repeat. Or just use the long > formate to generate an archatype !! > It will be great if the archtypes can be available the same way a > dependecy, when used it's stored in nexes for the next time. > > I will try the plugin you suggested. But I don't know if that's what I > need. Thank you. > > > 2009/10/26 Tamás Cservenák <tamas@...>: >> Yes, there is: just deploy them on your central nexus, and add the archetype >> plugin to it too. >> This way, all the deployed archetypes will become available in the published >> archetype catalog (published by plugin). >> For this to work, you need this OSS plugin: >> https://docs.sonatype.org/display/Nexus/Nexus+Archetype+Plugin >> ~t~ >> >> On Mon, Oct 26, 2009 at 1:36 AM, Mansour Al Akeel >> <mansour.alakeel@...> wrote: >>> >>> Hello all: >>> I have been trying to get nexus to reflect the archtypes I am using. >>> For example: >>> I have to build a project from hippo cms >>> >>> mvn archetype:generate\ >>> -DarchetypeRepository=http://repository.hippocms.org/maven2\ >>> -DarchetypeGroupId=org.onehippo.ecm.hst\ >>> -DarchetypeArtifactId=hst-archetype\ >>> -DarchetypeVersion=2.03.09\ >>> -Dversion=1.01.00-SNAPSHOT\ >>> -DgroupId=com.mycompany\ >>> -DartifactId=myproject >>> >>> If I have built the artifacts on the same machine, I can use "mvn >>> archetype:generate", but I want to make it availabe for other machines >>> as well through a centeral nexus. >>> Is there a way to make it available in my nexus without having to >>> build and deploy it locally ? In other words just to use: >>> >>> mvn archetype:generate >>> >>> And see it there on the list from any machine. >>> >>> Thank you. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: nexus-user-unsubscribe@... >>> For additional commands, e-mail: nexus-user-help@... >>> >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: nexus-user-unsubscribe@... For additional commands, e-mail: nexus-user-help@... |
|
|
Re: Archetype in nexus
by Brian Fox
::
Rate this Message:
Ah, that plugin looks in the index and builds the archetype from
there. If the scala-tools.org is publishing indexes it should work, but if not then the only thing Nexus would have indexed are things it has already proxied. In otherwords, you may have to run archetype a few times manually to proxy the archetypes and then it should appear in the index and the archetype.xml On Mon, Oct 26, 2009 at 10:33 AM, Mansour Al Akeel <mansour.alakeel@...> wrote: > Ok, there's one thing I don't understand. I have added > http://scala-tools.org/repo-releases > and I can see scala archetypes from this repo when I do "mvn > archetype:generate". But I can not see archetypes from > http://repository.hippocms.org/maven2/ . > > I added them both in the same way. I downloaded and installed the > plugin you suggested, but no difference. > what do I need to do ? > Thank you. > > On Mon, Oct 26, 2009 at 10:31 AM, Mansour Al Akeel > <mansour.alakeel@...> wrote: >> Hello Tamas: >> Thank you for your reply. >> >> What do you mean by "deploy them on your central Nexus" ? >> At this point I have to get the source code for the atchetype, and >> build it localy. If I need to make it available in my Nexux, then I >> have to deploy it to my central nexus. When newer versions of the >> archetype are released, then I have to repeat. Or just use the long >> formate to generate an archatype !! >> It will be great if the archtypes can be available the same way a >> dependecy, when used it's stored in nexes for the next time. >> >> I will try the plugin you suggested. But I don't know if that's what I >> need. Thank you. >> >> >> 2009/10/26 Tamás Cservenák <tamas@...>: >>> Yes, there is: just deploy them on your central nexus, and add the archetype >>> plugin to it too. >>> This way, all the deployed archetypes will become available in the published >>> archetype catalog (published by plugin). >>> For this to work, you need this OSS plugin: >>> https://docs.sonatype.org/display/Nexus/Nexus+Archetype+Plugin >>> ~t~ >>> >>> On Mon, Oct 26, 2009 at 1:36 AM, Mansour Al Akeel >>> <mansour.alakeel@...> wrote: >>>> >>>> Hello all: >>>> I have been trying to get nexus to reflect the archtypes I am using. >>>> For example: >>>> I have to build a project from hippo cms >>>> >>>> mvn archetype:generate\ >>>> -DarchetypeRepository=http://repository.hippocms.org/maven2\ >>>> -DarchetypeGroupId=org.onehippo.ecm.hst\ >>>> -DarchetypeArtifactId=hst-archetype\ >>>> -DarchetypeVersion=2.03.09\ >>>> -Dversion=1.01.00-SNAPSHOT\ >>>> -DgroupId=com.mycompany\ >>>> -DartifactId=myproject >>>> >>>> If I have built the artifacts on the same machine, I can use "mvn >>>> archetype:generate", but I want to make it availabe for other machines >>>> as well through a centeral nexus. >>>> Is there a way to make it available in my nexus without having to >>>> build and deploy it locally ? In other words just to use: >>>> >>>> mvn archetype:generate >>>> >>>> And see it there on the list from any machine. >>>> >>>> Thank you. >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: nexus-user-unsubscribe@... >>>> For additional commands, e-mail: nexus-user-help@... >>>> >>> >>> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: nexus-user-unsubscribe@... > For additional commands, e-mail: nexus-user-help@... > > --------------------------------------------------------------------- To unsubscribe, e-mail: nexus-user-unsubscribe@... For additional commands, e-mail: nexus-user-help@... |
|
|
Re: Archetype in nexus
by Mansour Al Akeel
::
Rate this Message:
Brian, thank you for the reply. Can you please explain to me what do
you mean by "run archetype a few times manually to proxy the archetypes" ? On Mon, Oct 26, 2009 at 1:06 PM, Brian Fox <brianf@...> wrote: > Ah, that plugin looks in the index and builds the archetype from > there. If the scala-tools.org is publishing indexes it should work, > but if not then the only thing Nexus would have indexed are things it > has already proxied. In otherwords, you may have to run archetype a > few times manually to proxy the archetypes and then it should appear > in the index and the archetype.xml > > On Mon, Oct 26, 2009 at 10:33 AM, Mansour Al Akeel > <mansour.alakeel@...> wrote: >> Ok, there's one thing I don't understand. I have added >> http://scala-tools.org/repo-releases >> and I can see scala archetypes from this repo when I do "mvn >> archetype:generate". But I can not see archetypes from >> http://repository.hippocms.org/maven2/ . >> >> I added them both in the same way. I downloaded and installed the >> plugin you suggested, but no difference. >> what do I need to do ? >> Thank you. >> >> On Mon, Oct 26, 2009 at 10:31 AM, Mansour Al Akeel >> <mansour.alakeel@...> wrote: >>> Hello Tamas: >>> Thank you for your reply. >>> >>> What do you mean by "deploy them on your central Nexus" ? >>> At this point I have to get the source code for the atchetype, and >>> build it localy. If I need to make it available in my Nexux, then I >>> have to deploy it to my central nexus. When newer versions of the >>> archetype are released, then I have to repeat. Or just use the long >>> formate to generate an archatype !! >>> It will be great if the archtypes can be available the same way a >>> dependecy, when used it's stored in nexes for the next time. >>> >>> I will try the plugin you suggested. But I don't know if that's what I >>> need. Thank you. >>> >>> >>> 2009/10/26 Tamás Cservenák <tamas@...>: >>>> Yes, there is: just deploy them on your central nexus, and add the archetype >>>> plugin to it too. >>>> This way, all the deployed archetypes will become available in the published >>>> archetype catalog (published by plugin). >>>> For this to work, you need this OSS plugin: >>>> https://docs.sonatype.org/display/Nexus/Nexus+Archetype+Plugin >>>> ~t~ >>>> >>>> On Mon, Oct 26, 2009 at 1:36 AM, Mansour Al Akeel >>>> <mansour.alakeel@...> wrote: >>>>> >>>>> Hello all: >>>>> I have been trying to get nexus to reflect the archtypes I am using. >>>>> For example: >>>>> I have to build a project from hippo cms >>>>> >>>>> mvn archetype:generate\ >>>>> -DarchetypeRepository=http://repository.hippocms.org/maven2\ >>>>> -DarchetypeGroupId=org.onehippo.ecm.hst\ >>>>> -DarchetypeArtifactId=hst-archetype\ >>>>> -DarchetypeVersion=2.03.09\ >>>>> -Dversion=1.01.00-SNAPSHOT\ >>>>> -DgroupId=com.mycompany\ >>>>> -DartifactId=myproject >>>>> >>>>> If I have built the artifacts on the same machine, I can use "mvn >>>>> archetype:generate", but I want to make it availabe for other machines >>>>> as well through a centeral nexus. >>>>> Is there a way to make it available in my nexus without having to >>>>> build and deploy it locally ? In other words just to use: >>>>> >>>>> mvn archetype:generate >>>>> >>>>> And see it there on the list from any machine. >>>>> >>>>> Thank you. >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: nexus-user-unsubscribe@... >>>>> For additional commands, e-mail: nexus-user-help@... >>>>> >>>> >>>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: nexus-user-unsubscribe@... >> For additional commands, e-mail: nexus-user-help@... >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: nexus-user-unsubscribe@... > For additional commands, e-mail: nexus-user-help@... > > --------------------------------------------------------------------- To unsubscribe, e-mail: nexus-user-unsubscribe@... For additional commands, e-mail: nexus-user-help@... |
| Free embeddable forum powered by Nabble | Forum Help |
