Maven, woapplication-archetype not found when using the local catalog
Maven, woapplication-archetype not found when using the local catalog
- Subject: Maven, woapplication-archetype not found when using the local catalog
- From: William Hatch <email@hidden>
- Date: Sat, 06 Dec 2008 13:46:52 -0500
More playing around with getting this to fly; using latest WOLips,
Eclipse 3.4 and I hope (not sure which version of WO you get when
installing with maven) WO 5.4.3.
I've been able to successfully install the WO snapshots and build and
install wonder into my local repository using maven, but when trying
to use the woapplication-archetype as defined in my local archetype-
catalog in ~/.m2/ to create a new project by doing the following:
mvn -e archetype:generate -DarchetypeCatalog=local
and then selecting "1" when presented with this prompt:
Choose archetype: 1: local -> woapplication-archetype (WebObjects
Application Archetype) 2: local -> woframework-archetype (WebObjects
Framework Archetype) Choose a number: (1/2): 1
as documented on the wiki here: http://wiki.objectstyle.org/confluence/display/WOL/woapplication-archetype
I"m getting: org.apache.maven.BuildFailureException: The desired
archetype does not exist
(org.objectstyle.woproject.maven2:woapplication-archetype:2.0.16)
it appears to be trying to grab this from here:
Downloading: http://repo1.maven.org/maven2/org/objectstyle/woproject/maven2/woapplication-archetype/2.0.16/woapplication-archetype-2.0.16.jar
and it's not there.
Here's my archetype-catalog.xml:
<?xml version="1.0" encoding="UTF-8"?><archetype-catalog>
<archetypes>
<archetype>
<groupId>org.objectstyle.woproject.maven2</groupId>
<artifactId>woapplication-archetype</artifactId>
<version>2.0.16</version>
<description>WebObjects Application Archetype</description>
</archetype>
<archetype>
<groupId>org.objectstyle.woproject.maven2</groupId>
<artifactId>woframework-archetype</artifactId>
<version>2.0.16</version>
<description>WebObjects Framework Archetype</description>
</archetype>
</archetypes>
</archetype-catalog>
Do I need to define a different repository someplace, use a different
version number, or... ? I'm not able to wrap my head around the answer
from reading the book or googling, so any help is appreciated. Any
best practices about conventional places to define repositories for
this sort of artifact would be helpful. Should it go in my local
settings.xml, the main settings.xml, included as an attribute within
the archetype-catalog.xml and so on.
Bill
http://web.mac.com/wkhatch
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden