Re: Maven question...
Re: Maven question...
- Subject: Re: Maven question...
- From: Lachlan Deck <email@hidden>
- Date: Tue, 28 Jul 2009 05:16:02 +1000
Hi Michael,
On 28/07/2009, at 12:37 AM, Michael Halliday wrote:
Hey List,
Don't know if this is the correct list to be discussing Maven stuff
or not.
Good a place as any.
But, I have been trying to get Maven running ... and I think I have
succeeded. I have wonder building and it installs into my repository
just fine.
Great.
So, now comes the fun part ... I have a ton of frameworks and apps
currently all building with ant and the FBL. What is the "best
practise" (or is there one), to get my existing stuff converted to
Maven. I love the "concept" of Maven and want to try to embrace it
lovingly ... lol. I know it's a touchy subject :).
I can see the soldier ants gathering in formation already ;-)
There's two ways forward:
1) keeping your project layout as-is (keeps your choices open)
To understand what's going on some of what's mentioned here (though
I've not reviewed that for a while) might be helpful
http://wiki.objectstyle.org/confluence/display/WOL/Maven+Kicking+the+tyres+without+changing+your+project+structure
However, have a look at the pom files for Wonder (which also uses FBL)
for more complete examples. Notice that the resources mapping is not
necessary to specify as the wolifecycle plugin AFAIK only needs you to
specify <sourceDirectory>Sources</sourceDirectory> in order to know
that FBL is in play.
2) adopt the usual maven layout (fully embraced)
a) # assuming use of svn
svn rm Libraries
svn mv --parents Sources src/main/java
svn mv Components src/main/components
svn mv Resources src/main/resources
svn mv WebServerResources src/main/webserver-resources
if [ -f CustomInfo.plist ]; then
svn mv CustomInfo.plist src/main/resources/
fi
svn rm build.xml
rm -rf bin
b) grab a pom.xml file from an example
c) update eclipse files:
$ mvn eclipse:m2eclipse
I have read the wikis ... i know they are not "complete"
Yeah, work in progress might be an appropriate description...
but I have a few questions on that front as well ... the
woapplication-archetype page here: http://wiki.objectstyle.org/confluence/display/WOL/woapplication-archetype
tells us we need have the most recent version of the archetype-
catalog.xml ... is the version their up-to-date?
It is now :) Thanks for the prod.
It's actually just a convenience and not needed btw. So long as your
~/.m2/settings.xml file references the wocommunity repo you can create
your projects just fine. The local catalog just lets you specify
favourites.
You can always update your local catalog based on what's either...
Released:
http://wo-repository.moleque.com.br/nexus/content/groups/public/org/objectstyle/woproject/maven2/
or SNAPSHOTed
http://wo-repository.moleque.com.br/nexus/content/groups/public-snapshots/org/objectstyle/woproject/maven2/
It looks like it refers to version 2.0.17-SNAPSHOT ... but that's
not true anymore is it? Perhaps I'm just confused and don't know
what I'm talking about ... it's Monday morning and I've only had one
coffee :)
No caffein required :)
with regards,
--
Lachlan Deck
_______________________________________________
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