Gradle Un article de Wikipédia, l'encyclopédie libre. Gradle allie les atouts de Apache Maven et Apache Ant : il allie l'utilisation de conventions à la manière de Maven (convention plutôt que configuration) avec la flexibilité de Ant pour décrire les tâches de constructions, avec une cohérence forte dans l'interface de programmation des tâches. Présentation[modifier | modifier le code] Gradle permet d'écrire des tâches de constructions dans un fichier de construction en utilisant le langage Groovy. Il est possible d'importer des tâches standards qui permettent de construire des programmes utilisant un ou plusieurs langages (Java, Groovy…) ou qui permettent d’exécuter des activités d’ingénierie logicielle telles qu'exécuter les tests unitaires, assurer la qualité du code (SonarQube, Checkstyle)… Gradle reprend certaines des idées fortes de Maven : convention plutôt que configurationcycle de viegestion des dépendances à la manière d'Apache Ivy ou Mavenréférentiel (ou entrepôts)
Setup Grunt on Jenkins Gruntis suitable for building JavaScript project as concat, minify, jshint and unit test.Jenkinsis suitable for CI as using SCM polling, scheduler. I think these tools makes our development faster. This is sample of front-end javascript project and building with Grunt on Jenkins. Awesome project src Script files dist Compressed production files dist/cov Test coverage dist/metrics JavaScript static analysis test Test code .jshintrc jshint config file Gruntfile.js Grunt config file package.json Project config file jenkins-grunt.sh Kick grunt on jenkins View sample code on GitHub Gruntfile.js Executejshint,testem,clean,qunit-cov,plato,concat,uglify jshint Detect errors and potential problems in JavaScript code and can be used to enforce coding conventions. testem Execute browser testing framework automatically. clean Cleaning production and coverage directiory before building qunit-cov Coverage unit test in qunit plato JavaScript source code visualization, static analysis, and complexity tool concat Concatenate files Add
Hibernate - JBoss Community Git Grunt Spring Maven secrets: filtering sources - Connect The default Maven root project object model provides very good defaults that declare what needs to be done in most cases. Sometimes you need a bit more or different and Maven lets you do that. In this first episode I’ll show you how to filter your source files. Why filter source files? Well there are many use cases you can think of. public static final String DOMAIN = "${pom.groupId}"; public static final String WCB_ID = "${pom.artifactId}"; Note: We could discuss if this is a good approach compared to using resource files (that are filtered by default) and can be loaded from the classpath at runtime, but that is beyond the scope of this post ;) Filtering in Maven Filtering is a standard feature in Maven and any typical project uses it extensively. Note: Always make sure binary resources are NOT being filtered. Configuring the resources plugin So, in order to filter the source files we need to tell the resources plugin to use them as resources. <project...> ... <project...> ... Conclusion
Compiling / Optimizing A Subset Of A RequireJS Application In my last few blog posts, I explored the lazy-loading of a RequireJS module within a modular JavaScript application. I don't know if such an approach is really worthwhile - I'm not convinced that it wouldn't just be better to concatenate everything into a single, front-loaded file; but, I thought it was a fun mental exercise. To continue on in the same vein, I wanted to think about how this approach would work in a build script. It's one thing to lazy load a module when all modules remain independent; but, what happens to lazy-loading when you need to start building and optimizing your scripts? Life is simple when you keep your modules in individual files - you make requests to load one module and RequireJS magically handles all the dependencies. r.js works by analyzing and walking your dependency tree, inlining and compacting each module along the way. To start off this exploration, I used the same lazy-loaing FAQ code that I had in my previous two blog posts. faq.js - Our FAQ Module
Maven - Welcome to Apache Maven Add Javadoc You are wondering why Netbeans give you code completion but no javadoc, rather saying “javadoc not found” ? It is not part of the Netbeans Installer or the regular JDK package. You need to download it separately (link), copy the zip file to a folder of your choice and configure the javadoc in Java platforms. Netbeans Java Platform Like this: Like Loading...
Yeoman Netbeans IDE NetBeans IDE lets you quickly and easily develop Java desktop, mobile, and web applications, as well as HTML5 applications with HTML, JavaScript, and CSS. The IDE also provides a great set of tools for PHP and C/C++ developers. It is free and open source and has a large community of users and developers around the world. Best Support for Latest Java Technologies NetBeans IDE provides first-class comprehensive support for the newest Java technologies and latest Java specification enhancements before other IDEs. It is the first free IDE providing support for JDK 8, JDK 7, Java EE 7 including its related HTML5 enhancements, and JavaFX 2. With its constantly improving Java Editor, many rich features and an extensive range of tools, templates and samples, NetBeans IDE sets the standard for developing with cutting edge technologies out of the box. Fast & Smart Code Editing An IDE is much more than a text editor. More information Easy & Efficient Project Management Rapid User Interface Development
jrburke/almond Grunt by Example - A Tutorial for JavaScript's Task Runner - Brian Chu What’s Grunt used for? Automating front-end and JavaScript workflow tasks. Refreshing the browser when you change a script. Minifying and concatenating. Running tests. Enter Grunt by Example! The catch - Grunt configuration files can be fairly convoluted at first glance, usually due to the fact that developers add more and more steps to their workflow over time. Grunt is just a task runner. npm search grunt to view literally every grunt plugin available. Get the command line interface: npm install -g grunt-cli Add the actual grunt task runner as a development dependency to your project (--save-dev adds the package as a dependency to package.json): npm install --save-dev grunt Let’s follow a process of gradual expansion. Create an empty Gruntfile.js file in your project root. Let’s say that the first task we want to add to our workflow is to be able to concatenate several JavaScript files into one. Run npm install --save-dev grunt-contrib-concat. Running grunt preview will now run both tasks.