Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What does “basic” and “modular” mean when it comes to AppFuse 2.x archetypes?

0
Posted

What does “basic” and “modular” mean when it comes to AppFuse 2.x archetypes?

0

Basic archetypes are meant for developing web applications with no re-usable backend. This is the recommended archetype to use with AppFuse 2.x. The tutorials assume you’re using this archetype. Unlike Ant, Maven requires you to have a different “module” for each artifact you want to produce (i.e. JAR or WAR). This is what the modular archetypes are for. If you’re an experienced Maven 2 user, you might consider this archetype. It’s also useful if you need a backend that can be used by multiple clients.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123