Yah, I agree.
If it comes down to having to write something else just to get what we
want to begin with (one-command install), we should just do it correctly.
Self -1
On 10/14/2013 11:15 AM, Michael Berman wrote:
One of the big advantages of an archetype is that it's convenient and
consistent to use...I agree that requiring a download and install in order
to use the archetype really cuts down on its usefulness. I don't get a
vote, but if I did, I think I would need a clean invocation path in order
to give my +1. (And I don't think a custom one-off shell script that
messes with someone's local repo would qualify)
On Mon, Oct 14, 2013 at 7:19 AM, Mike Drob <[email protected]> wrote:
On Oct 14, 2013 12:14 AM, "Josh Elser" <[email protected]> wrote:
Well, dang.
My intent was definitely to *not* make a user have to download, install
and then invoke the archetype, but provide a single maven command to be run
to get up and running.
Could wrap this up in a shell script? Installing to the local repo/catalog
is a pretty nasty side effect though.
I hate doing it, but that might be a non-starter (even as the guy
repeatedly cutting these releases). I haven't decided my opinion on whether
or not this is super important for a 1.4.x version of the code. Thanks for
the information either way, Mike.
On 10/13/2013 12:29 AM, Mike Drob wrote:
There is no archetype-catalog.xml file deployed, so I have to mvn
install
before I am able to generate projects using the archetype. After I
install
however, everything works fine.
