Re: Archetype create v. generate
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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Archetype create v. generate
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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Archetype create v. generate
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 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 bit I'd like to avoid. I think I'm using Version: 2.0-alpha-4, which is actually different from the one I *thought* I was using, so I'll re-visit my process and see what's currently happening, but I'd still appreciate any input. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Archetype create v. generate
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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 2.0.9 NullpointerException when running tests
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
Re: Maven 2.0.9 NullpointerException when running tests
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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Archetype create v. generate
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 bit I'd like to avoid. I think I'm using Version: 2.0-alpha-4, which is actually different from the one I *thought* I was using, so I'll re-visit my process and see what's currently happening, but I'd still appreciate any input. Thanks, Dave - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: The Definitive Guide: online vs. print
--- 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 additional commands, e-mail: [EMAIL PROTECTED]
Re: Best Practice for code generation scenarios in Maven
--- 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 build-helper plugin to add source trees. The module contains sub-classes of the generated classes and (famous last words) we don't have any reason to provide the base classes as their own artifact. For now, anyway, keeping things together seemed better. The only real advantage, and it seems slim, is that of locality and cohesiveness. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] archetype repository requires authentication
--- 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 generation fails of course. Is there any possibility to supply credentials? This might help, although I haven't tried it :/ http://maven.apache.org/guides/mini/guide-configuring-maven.html See the Security and Deployment Settings section; it sounds like the server element may do what you want. HTH, Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: newbie: understanding how teams deal with version numbers on dependencies (Best practices)?
--- 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 *released* versions of A shouldn't depend on B-snapshots? In other words, an A-snapshot may use a B-snapshot, but an A-release should not. Every A-release should depend only on a B-release, even if it means releasing an B-n.n.n+1 tag to fix minor B-release issues. (We're revamping some of our build and release policies, and may be using Maven moving forward, so I'm definitely interested in hearing opinions, best practices, and how others deal with this.) Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multi-module site generation?
--- 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 following distributionManagement in the top-level POM in the hopes it would all get dumped to a directory in the parent site, but so far no joy; only the parent shows up. distributionManagement site urlfile://deployed-site/url /site /distributionManagement The parent and two module POMs are at http://pastebin.com/m1c8573cc. I'm assuming that there are multiple things wrong with what I'm doing (finally trying to figure out Maven) so any advice/criticisms/etc. are welcome. I also tried site:stage-deploy, which created the following hierarchy: target/staging/localhost/MultiModCli/... .../MultiModCore/... .../deployed-site/(the parent project) So I'd guess I'm just doing (one of many :) things all cow's legs up, 'cuz it's close. Thanks, Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multi-module site generation?
--- 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 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). Sheesh :/ Thanks much, Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multi-module site generation?
--- 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 the module links it's creating point to the parent POM directory + parent artifactId. Ah; removing *all* the url elements seems to have fixed it; I think my root POM's url messed up all the others. Curious; I'll look into it again tomorrow. Thanks again, Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
