Ken
No. Not at all. That makes sense. My production application is pretty
simple. I was just wondering...
Paul
On Sep 3, 2014, at 11:29 AM, Ken Anderson wrote:
> Paul,
>
> I use a lot of libraries that have pom.xml files, and it seems like it would
> be easier to handle dependencies by d
Paul,
I use a lot of libraries that have pom.xml files, and it seems like it would be
easier to handle dependencies by doing this. You think it’s a bad idea?
Ken
On Sep 3, 2014, at 11:22 AM, Paul Yu wrote:
> Ken
>
> What is the reasoning behind this decision?
>
> Paul
> On Sep 3, 2014, at
Ken
What is the reasoning behind this decision?
Paul
On Sep 3, 2014, at 10:17 AM, John Huss wrote:
> Here are the parts I remember doing. There may be more. You have to have WO
> installed, and if WO is in the standard directories it is easier.
>
> # this file is attached
> mv archetype-cata
Here are the parts I remember doing. There may be more. You have to have
WO installed, and if WO is in the standard directories it is easier.
# this file is attached
mv archetype-catalog.xml ~/.m2/
mvn wobootstrap:install
# Optional
#mvn install:install-file -Dfile=/Users/john/Downloads/ERServl
On Wed, Sep 3, 2014 at 7:39 AM, Ken Anderson wrote:
> All,
>
> I’ve decided to bite the bullet and try and integrate Maven into my
> WOrkflow. Any hints or tips? Is the WOProject-Maven page (
> http://wiki.wocommunity.org/display/WOL/WOProject-Maven) up to date? It
> was last edited in 2011…
>
All,
I’ve decided to bite the bullet and try and integrate Maven into my WOrkflow.
Any hints or tips? Is the WOProject-Maven page
(http://wiki.wocommunity.org/display/WOL/WOProject-Maven) up to date? It was
last edited in 2011…
Thanks!
Ken
___
