Ok, here are some tips:
- you need *not* relocate your "local" m2 repository, by default it is <user
home>/.m2/repository.
Now, you can use settings.xml with the <localRepository> element and point
it to somewhere.
So make sure that if you *do* have a localRepository element in
settings.xml, then please
"browse" that folder and see if all the artifacts are present. If they are
*not*, then do
"mvn install" *again* on your j2 source, this should populate your
repository with all j2
artifacts (including the portal archetype).
- second to avoid the prompt, invoke the older version of the archetype
plugin *exactly* as
below:
mvn org.apache.maven.archetype: maven-archetype: 1.0-alpha-7:create <all
your other -D options>
And the prompt should disappear, like I said this is new feature of the
latest archetype plugin which
the maven group have for some reason pushed it, without much warning
(unless you monitor the
mailing list).
Cheers
Mohan
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, February 22, 2008 5:04 PM
To: Jetspeed Users List
Subject: RE: maven repository
I'm afraid that this solves nothing, question still appears.
But I've found some workaround. There in the
http://wiki.apache.org/portals/Jetspeed2/Maven2BuildSupport
"""
Repository relocation
While the default location of the settings.xml file should not be changed,
(e.g. ~/.m2/settings.xml), one can relocate the repository using the '
<localRepository> ' element in the settings.xml file. See the
settings.xml.sample file for an example. Note that the repository path must be
an absolute path and not contain any property expressions.
"""
is said that " ... one can relocate the repository using the '
<localRepository> ' ..."
but one MUST relocate the repository (anywhere), in order to successfuly
execute the
mvn archetype:create -DarchetypeGroupId=org.apache.portals.jetspeed-2
-DarchetypeArtifactId=portal-archetype -DarchetypeVersion=2.1.3
-DgroupId=myportalgroup -DartifactId=myportal -Dversion=1.0
command, after relocating local repo, new custom project was created.
Then the command
mvn -P tomcat
can build the portal and deploy it succesfuly.
What a mess!
Can't it be straightforward? It's really depresing, documentation outdated,
several types
of build...
Hope that's gonna help someone.
V
______________________________________________________________
> Od: [EMAIL PROTECTED]
> Komu: "'Jetspeed Users List'" <[email protected]>
> Datum: 22.02.2008 21:39
> Predmet: RE: maven repository
>
>Ah..they just upgraded to a new version of the archetype plugin, you can use
>the option
>-DinteractiveMode=false
>to avoid the question.
>
>Cheers
> Mohan
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>Sent: Friday, February 22, 2008 12:55 PM
>To: Jetspeed Users List
>Subject: Re: maven repository
>
>There is still one problem with repository,
>
>how can one make his own custom build when the command
>
>mvn archetype:create -DarchetypeGroupId=org.apache.portals.jetspeed-2
>-DarchetypeArtifactId=portal-archetype -DarchetypeVersion=2.1.3
>-DgroupId=myportalgroup -DartifactId=myportal -Dversion=1.0
>
>produces some questions from maven:
>
>
>[INFO] Building Jetspeed-2 Enterprise Portal
>[INFO] task-segment: [archetype:create] (aggregator-style)
>[INFO] ------------------------------------------------------------------------
>[INFO] Preparing archetype:create
>[INFO] No goals needed for project - skipping
>Downloading:
>http://www.bluesunrise.com/maven2/myportalgroup/wagon-http-shared/1.0-beta-2/wagon-http-shared-1.0-beta-2.pom
>Downloading:
>http://repo1.maven.org/maven2/myportalgroup/wagon-http-shared/1.0-beta-2/wagon-http-shared-1.0-beta-2.pom
>Downloading:
>http://www.bluesunrise.com/maven2/myportalgroup/wagon-http-shared/1.0-beta-2/wagon-http-shared-1.0-beta-2.pom
>Downloading:
>http://repo1.maven.org/maven2/myportalgroup/wagon-http-shared/1.0-beta-2/wagon-http-shared-1.0-beta-2.pom
>Downloading:
>http://www.bluesunrise.com/maven/myportalgroup/poms/wagon-http-shared-1.0-beta-2.pom
>Downloading:
>http://dist.codehaus.org/myportalgroup/poms/wagon-http-shared-1.0-beta-2.pom
>Downloading:
>http://repo1.maven.org/maven/myportalgroup/poms/wagon-http-shared-1.0-beta-2.pom
>[INFO] Setting property: classpath.resource.loader.class =>
>'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
>[INFO] Setting property: velocimacro.messages.on => 'false'.
>[INFO] Setting property: resource.loader => 'classpath'.
>[INFO] Setting property: resource.manager.logwhenfound => 'false'.
>[INFO] [archetype:create]
>[WARNING] No archetype repository found.
>[WARNING] Specified archetype not found.
>Choose archetype:
>1: internal -> appfuse-basic-jsf (AppFuse archetype for creating a web
>application with Hibernate, Spring and JSF)
>2: internal -> appfuse-basic-spring (AppFuse archetype for creating a web
>application with Hibernate, Spring and Spring MVC)
>...
>...
>35: internal -> maven-archetype-sar (JBoss Service Archive)
>36: internal -> wicket-archetype-quickstart (A simple Apache Wicket project)
>Choose a number:
>(1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/19/20/21/22/23/24/25/26/27/28/29/30/31/32/33/34/35/36):
>
>
>I've done the previous complete build to populate maven repo and this
>.m2/repository/org/apache/portals/jetspeed-2/portal-archetype/2.1.3/portal-archetype-2.1.3.jar
>
>
>archetype seems to be present.
>
>What am I doing wrong?
>
>______________________________________________________________
>> Od: [EMAIL PROTECTED]
>> Komu: "Jetspeed Users List" <[email protected]>
>> Datum: 18.02.2008 13:51
>> Predmet: Re: maven repository
>>
>>OK,
>>
>>my problems were solved!
>>when I discovered that java 1.6_03 32bit for building on linux is NOT working,
>>I downloaded java 1.5 and suddenly all maven2 builds are successful.
>>
>>It would have been great to have this information sooner. Can you please
>>update
>>the web pages? It's stated there that java 1.4+ will be fine, it's not
>>completly
>>true. It would save time to many people..
>>
>>Vladimir Linhart
>>
>>
>>
>>
>>
>>______________________________________________________________
>>> Od: [EMAIL PROTECTED]
>>> Komu: "Jetspeed Users List" <[email protected]>
>>> Datum: 15.02.2008 11:41
>>> Predmet: Re: maven repository
>>>
>>>>In order to build with Maven, a Maven repository is required to get all
>>>dependencies
>>>>
>>>But why isn't this repo included in any download? how can one
>>>build jetspeed without it? using the maven
>>>
>>>>> what is the binary download for?
>>>>>
>>>>There are binary downloads for installers of demo portals as well as
>>>binary downloads of the entire build including source and documentation
>>>>
>>>>http://portals.apache.org/jetspeed-2/download.html
>>>>
>>>I know how to use the installer, but with the binary build, I don't know how
>>>to deploy to tomcat.
>>>
>>>thanks a lot,
>>>
>>>Vladimir Linhart
>>>
>>>
>>>---------------------------------------------------------------------
>>>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]
