[hudson-dev] Why are we using hpi:create instead of mavne archetypes?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[hudson-dev] Why are we using hpi:create instead of mavne archetypes?

From: Henrik Lynggaard Hansen <henrik@xxxxxxx>
Date: Sun, 15 Jan 2012 19:59:36 +0100
Delivered-to: hudson-dev@xxxxxxxxxxx
List-archive: <http://dev.eclipse.org/mailman/private/hudson-dev>
List-help: <mailto:hudson-dev-request@eclipse.org?subject=help>
List-subscribe: <http://dev.eclipse.org/mailman/listinfo/hudson-dev>, <mailto:hudson-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <http://dev.eclipse.org/mailman/options/hudson-dev>, <mailto:hudson-dev-request@eclipse.org?subject=unsubscribe>

Hi

Subject really says it all, why are we using hpi:create to create a
blank plugin instead of just using standard maven archetypes.

I mean is there a technical reason or is it only history?

Best regards
Henrik

Prev by Date: Re: [hudson-dev] Announcing the Hudson job creator tool.
Next by Date: Re: [hudson-dev] [Hudson-Dev] Re: Why are we using hpi:create instead of mavne archetypes?
Previous by thread: [hudson-dev] Announcing the Hudson job creator tool.
Next by thread: Re: [hudson-dev] [Hudson-Dev] Re: Why are we using hpi:create instead of mavne archetypes?
Index(es):
- Date
- Thread

Breadcrumbs