I am new to Maven, and I am really in love with it in theory.
But the problem I'm experiencing is that I don't see very much information on any given archetype - at most I am seeing a one line description. (Is there generally more, anywhere?)
And I don't know where to find comments and ratings on archetypes. As the number of them grows, this seems to me to be a critical issue to address. I don't have the time to track down and research each of hundreds of archetypes.
I'm starting a new project (described in post I made yesterday). This is a project very important to me, so I want it to come off well, and so at the very least, I don't want to select a bad Maven archetype to begin with.
So please, list the stinkers here. This will let their authors know about deficiencies and improve them, and help me in my search. If there is a more standard, natural place for this type of information, please share that information with the community here also.
Thanks for your help. We are making the world better with our work.
If you love me, you will visit docs.opensimplatform.org
(FYI, Getting it tattooed on is a bit much.)
All an archetype is is a template project with some basic automated configuration. Anybody can create one. The best ones are the ones that match what your shop requires, which typically means roll-your-own.
There's not (apparently) enough interest in archetypes for people to actively vote on them, but some suggestions would be to give a higher level of consideration to "name" suppliers such as apache.org and to check their ages, since that only indicates the level of effort being made to keep them current. Since an archtetype is a snapshot of a project, the older it is, the more antiquated the components in its constructed dependencies will be. Which may or may not be a good thing.
There is room in the POM for a detailed description, but I don't know about any services that make it easy to browse archetypes and get it. Fortunately, the "one-liner" is usually a good clue. When in doubt, however, just run maven against the archetype of interest and see if you like what it generates. If not, find another one and try again, since the effort required is usually not that great. Chances are that the "ideal" archetype will be one that you build from someone else's archetype with updates and customizations.
Then again, if you're like me, you'll forget that there even are archetypes and simply clone an in-house project.
An IDE is no substitute for an Intelligent Developer.
Joined: Jan 05, 2001
This is great information, and will help me in my search.
I do find it unfortunate that there is not enough interest for people to vote on them. Even something simple, like the number of downloads or the number of uses would be helpful. Maybe as the tool evolves, that may eventually come.