[ARCH-12] Improve and update archetypes Created: 10/Nov/10  Updated: 14/Mar/14  Resolved: 28/Aug/13

Status: Closed
Project: Archetypes
Component/s: None
Affects Version/s: None
Fix Version/s: 1.1

Type: Bug Priority: Neutral
Reporter: Joerg Bellmann Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File magnolia-module-old.png     PNG File my-module-archetype.png    
Issue Links:
relation
is related to FORGE-5 Maven archetypes for Magnolia modules... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Hi Grégory,

maybe you remember my forge-request for an archetype-project 4 weeks ago? When I was in Basel to an magnolia course christian ringele told us that the archetypes provided in svn aren't really usable. So I created an archetype that, maybe, brings better support for the community and my company. I had a look at the archetypes in svn and tried to create a module-project with them. I got strange log-messages from maven I've never seen before and the result was not acceptable. Here are my points for working:

  • throw away the old archetypes with a tag in svn
  • create new (or take mine) archetypes for module-projects and webapp-projects in trunk
  • create a separate parent-module that allows to release archetypes independently
  • provide/maintain a catalog-file in a directory in svn (accessable by http) with updated archetype informations that can be used in IDE and on console to create new projects
  • improve/extend documentation on project creation in the wiki and maybe with small screencasts (on youtube embedded in wiki-pages when possible)


 Comments   
Comment by Joerg Bellmann [ 10/Nov/10 ]

Maybe someone is interested in the log-message I got and a screenshot of the directory-layout from the old archetype:

[WARNING] 
[WARNING] 
[WARNING] *******************************************************
[WARNING] Deprecation Alert:
[WARNING] No mojo descriptors were found in this project which has a packaging type of maven-plugin.
[WARNING] In future versions of the plugin tools, this will fail the build.
[WARNING] If this project is an archetype, change the packaging type from maven-plugin to maven-archetype.
[WARNING] ********************************************************
[WARNING] 
Comment by Joerg Bellmann [ 10/Nov/10 ]

directory-layout from archetype in trunk

Comment by Joerg Bellmann [ 10/Nov/10 ]

directory-layout my archetype

Comment by Joerg Bellmann [ 10/Nov/10 ]

command i used on console:

...
...
307: remote -> circumflex-archetype (null)
Choose a number: 86: 8
Define value for property 'groupId': : de.jbellmann.magnolia
Define value for property 'artifactId': : my-module-test
Define value for property 'version': 1.0-SNAPSHOT: 
Define value for property 'package': de.jbellmann.magnolia: 
Define value for property 'module-name': my-module-test: my-module
Confirm properties configuration:
groupId: de.jbellmann.magnolia
artifactId: my-module-test
version: 1.0-SNAPSHOT
package: de.jbellmann.magnolia
module-name: my-module
Y: Y
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 53 seconds
[INFO] Finished at: Wed Nov 10 00:14:17 CET 2010
[INFO] Final Memory: 13M/309M
[INFO] ------------------------------------------------------------------------
jbellmann@belloNotebook:~/DEV/WORK/MAGNOLIA/MY_ARCHETYPE$ 
Comment by Magnolia International [ 18/Nov/10 ]

ho hi Joerg. Sorry I completely missed this ticket so far !

All very valid points.
Regarding the catalog file, I /think/ our Nexus can provide that transparently.
I will check the state of our current archetypes, but I am not surprised they don't work as well as they should. (archetype2 was in early alpha stages when i started working on those)

I think part of the problem comes from the fact that those were written as a "wrapper" kind of archetype, i.e how it was done with archetype v1, where the stuff under src/resources/archetype would be extracted.

I'll be happy to replace all of that with your suggestions and grant you commit permissions - feel free to attach anything to this issue

Comment by Joerg Bellmann [ 02/Dec/10 ]

Hi Grègory,

happy about the fact that you accept my improvements I tried to commit some files last weekend. But I didn't got them into svn. So please, can you check that you granted commit permissions for my account? Is it correct that the checkins go over an unsecured http connection? I looked at the wiki but did not found any hints to that point.

Comment by Magnolia International [ 21/Dec/10 ]

Hey Joerg,

Sorry for the late reply, once again missed this comment. I'd appreciate seeing a few patches before granting commit access. Thinking about it, it might be more efficient to start with a forge project for now, since I don't think I'll have much time to look into this further in before the new year. (I'll go ahead and create it for you)

And yes, that's correct, we only have http, no https, for svn at the moment. It's something I'm hoping to get solved soon too. See SYS-8.

Comment by Magnolia International [ 18/Mar/11 ]

Joerg, if there's anything else you'd like to do ...

Comment by Magnolia International [ 28/Aug/13 ]

Well, I think this is it.
The archetypes can still be improved of course, but the main infrastructure is there.
I'll try to see what we can do to remove the "old" ones from the catalog generated by Nexus.

Generated at Sun Feb 11 23:22:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.