Hubert Iwaniuk wrote:
Hi Dave,create is deprecate, generate is a way to go.
If you want it not interactive, read:
http://maven.apache.org/plugins/maven-archetype-plugin/examples/generate-batch.html
HTH,
It does--thanks much!
Dave
Raphaël Piéroni wrote:
Yup this is normal.
archetype:create is the old way a copy/paste from the old
archetype-1.0-alpha plugin
that is kept only for backaward compatibility.
archetype:generate is the prefered way to do things.
Great--thanks for the info.
Dave
Just a ping to see if anybody had any input--I haven't had a chance to
investigate further yet but need to commit some changes to some
archetypes and update some documentation soon.
Thanks,
Dave
Dave Newton wrote:
What's the approved way to create archetypes when there's an archetype
Raphaël Piéroni wrote:
One can call the generate goal in batch mode w/
mvn -B archetype:generate -DarchetypeGroupId=...
Oh, I missed that--thanks!
Is it normal that my archetype:create isn't paying attention to the
archetype-metadata file, or am I missing other things too?
Thanks,
Dave
Geoffrey Wiseman wrote:
Or version4.4/version.
Does 4.5 not work?
Dave
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Geoffrey Wiseman wrote:
On Sun, Jan 25, 2009 at 7:21 PM, Dave Newton newton.d...@yahoo.com wrote:
Does 4.5 not work?
I was just responding to Amin's comment about JUnit 4.4 [...]
Ah, missed that--never mind :)
Dave
Howdy,
What's the approved way to create archetypes when there's an archetype
metadata file?
So far it seems like I can either do archetype:create, which (so far)
isn't shuffling the files around from my archetype metadata file, or
archetype:generate, which does, but has that interactive
--- On Wed, 10/1/08, Baptiste MATHUS wrote:
Beta 0.16. And there's a foreword about this versioning: [...]
I wonder how they'll update my print copy that came last week?
Dave
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
--- On Tue, 9/23/08, stug23 wrote:
Does anyone on this group do this differently than what I
sketched out here? If so, why and what are the advantages
of your alternative approach?
I'm currently generating source into various /target/generated-sources
sub-directories and using the
--- On Sat, 9/20/08, Adrian Herscu wrote:
I have written an archetype and deployed to my remote
repository.
The repository requires authentication.
The problem is when somebody runs mvn archetype:generate
...
-DarchetypeRepository=http://my.repo he gets a 401 from the
server and
--- On Sat, 9/13/08, Graham Leggett wrote:
In other words, use the maven-release-plugin to publish
formal releases of code, and make sure that project A
never depends on a snapshot of project B if you can
possibly avoid it. Use proper version numbers.
Would it be reasonable to say that
--- On Fri, 9/12/08, Wendy Smoak wrote:
What are you trying to do by setting those values?
Preview it locally before deploying it?
That was the initial goal, but it's likely the final site will be deployed to a
local directory location on the CI machine.
I've tried site:deploy with the
--- On Fri, 9/12/08, Wendy Smoak wrote:
http://maven.apache.org/guides/mini/guide-site.html
(site-deploy is a lifecycle phase, while site:deploy means
to run one specific goal of the site plugin.)
Oh. Hrm. Something new every day, and all that.
Running site-deploy works, as long as I define
--- On Fri, 9/12/08, Dave Newton lied:
Running site-deploy works, as long as I define a file URI
that isn't broken. Which I couldn't.
Turns out site:deploy works just fine too (once the sites
have been generated, I mean).
Spoke too soon; I thought it had worked at one point but now
14 matches
Mail list logo
