Why doesn't AppFuse use Maven?
My newest reply for why AppFuse doesn't use Maven is going to be this link. Ant rocks. I still need to update AppFuse's build.xml to use all the Ant 1.6 stuff - that's scheduled for next week's late nights.
The Angular Mini-Book is a guide to getting started with Angular. You'll learn how to develop a bare-bones application, test it, and deploy it. Then you'll move on to adding Bootstrap, Angular Material, continuous integration, and authentication.
Spring Boot is a popular framework for building REST APIs. You'll learn how to integrate Angular with Spring Boot and use security best practices like HTTPS and a content security policy.
For book updates, follow @angular_book on Twitter.
The JHipster Mini-Book is a guide to getting started with hip technologies today: Angular, Bootstrap, and Spring Boot. All of these frameworks are wrapped up in an easy-to-use project called JHipster.
This book shows you how to build an app with JHipster, and guides you through the plethora of tools, techniques and options you can use. Furthermore, it explains the UI and API building blocks so you understand the underpinnings of your great application.
For book updates, follow @jhipster-book on Twitter.
My newest reply for why AppFuse doesn't use Maven is going to be this link. Ant rocks. I still need to update AppFuse's build.xml to use all the Ant 1.6 stuff - that's scheduled for next week's late nights.
The most frustrating experience for all new the users that try to build a project is that maven tries to go on Internet and download the files. A user with no Maven knowledge won't be able to disable this download. And now comes the best: this download thing is supposed to be a good thing. IT IS NOT. If you just test (on a new computer - so no caches) a lot of the open source projects, at least in 40% of them one JAR is missing, so one needs to download it manually.<p/> If one wants to use the project to learn a little - so it will use an IDE, the sources and javadocs for those JARs must be downloaded too, so the "maven automatic download", didn't helped again. Even worst, one must build it first to find out what's required :). I've seen this problem again and again, and maybe this could explain why maven has this "hate/love" user splitting. The users that just in the beginning experience such problems will hate maven.<p/> The last reason: if ANT does every aspect of the build process so good (with excellet IDE support), why use something else? Just for those ugly "maven generated sites" :)? Just look at those open source sites generated with maven: - they all look the same, are ugly and contain no real information: just a lot of links with empty pages. Of course there are exceptions from the rule, and one could fill those pages with information, but mostly it's not so.
Posted by Jake Robwood on February 18, 2005 at 12:15 PM MST #
Posted by Caoilte on February 18, 2005 at 01:14 PM MST #
For me Maven is like Python too :). I don't need it, and IMHO, VERY talented people behind it, instead of improving existing things, "dilute the scene"/"loose time reinventing the wheel" :).
A word about enforcing things "down your throat": standards are a VERY good thing, but only for the things that need to be standard. Otherwise you have communism :). Creativity is however about "not thinking in an enforced way", and I have all the time the impression that maven forces me to do things. ANT on the other side works how I want, and not vice versa.
Posted by Jake Robwood on February 18, 2005 at 01:42 PM MST #
<kbd>maven build:start</kbd>
before the laptop is disconnected from the internet will make sure the local repository is setup correctly.
Posted by caoilte on February 18, 2005 at 02:06 PM MST #
Posted by Patrick on February 18, 2005 at 03:54 PM MST #
Posted by Chakra Yadavalli on February 18, 2005 at 04:11 PM MST #
Posted by Todd Huss on February 18, 2005 at 06:10 PM MST #
Posted by sree on July 20, 2005 at 08:57 AM MDT #
Posted by Maximiliano on August 09, 2006 at 02:21 AM MDT #