Jason van Zyl jvanzyl

The Takari Lifecycle

TEAM includes an optimized replacement for the Maven default lifecycle. The Takari Lifecycle Plugin provided you access to a number of significant advantages:

One plugin with a small set of dependencies provides equivalent functionality to five plugins with a large set of transitive dependencies. This reduces the download times to retrieve the needed components as well tje storage space requirements in your repositories.

	<div class="stickyFooter">
	<div class="footer">
	<div class="container">
	<div class="row">
	<div class="col-md-4 md-margin-bottom-40">

	</div><!--/col-md-4-->

	<div class="col-md-4 md-margin-bottom-40">

	<?xml version="1.0" encoding="UTF-8"?>
	<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
	<modelVersion>4.0.0</modelVersion>
	<groupId>com.facebook.presto</groupId>
	<artifactId>presto</artifactId>
	<version>0.1.0.generation</version>
	<packaging>pom</packaging>
	<description>Sample Generations Build1</description>
	<properties>

	package io.tesla.maven.plugins.provisio;

	import io.provis.model.Runtime;

	import java.io.File;
	import java.util.HashMap;
	import java.util.List;
	import java.util.Map;
	import java.util.Set;

	<?xml version="1.0" encoding="UTF-8"?>
	<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<modelVersion>4.0.0</modelVersion>
	<groupId>com.acme.testproject</groupId>
	<artifactId>testproject-parent</artifactId>
	<version>1.0.0-SNAPSHOT</version>
	<packaging>pom</packaging>
	<properties>
	<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>

	# JSR330

	High level goal is to use the JSR330 APIs and remove all dependencies on Plexus, and to a lesser extent direct dependencies on Guice. Some observations:

	- maven-core is dependent on Plexus directly for the configurators
	- maven-core is dependent on Guice for session scopes. JSR330 has scopes and we can leverage these in the future
	- maven-plugin-api depends directly on plexus component descriptors, this can be decoupled
	- the Plexus container requires the plexus-component annotations on the classpath to start, even though we do not use classpath scanning. Leaving it as a runtime dependecy while removing the compile-time dependency could help to see where it's used if the IDEs actually scoped dependencies :(
	- there is a lot of crossover betweeen maven-compat and maven-core. For example the interface for the RepositorySystem is in maven-core while the implementation is in maven-compat. i took out the pieces of the RepositorySystem and ArtifactFactory I needed to decouple, seems to be working.
	There

	# The Takari Lifecycle

	TEAM includes an optimized replacement for the Maven default lifecycle. The
	Takari Lifecycle Plugin provided you access to a number of significant
	advantages:

	1. One plugin with a small set of dependencies provides equivalent functionality
	to five plugins with a large set of transitive dependencies. This reduces the
	download times to retrieve the needed components as well tje storage space
	requirements in your repositories.

	org.apache.maven.plugins maven-docck-plugin 1.0 16-Nov-2008
	org.apache.maven.plugins maven-stage-plugin 1.0-alpha-2 10-Jul-2009
	org.apache.maven.plugins maven-toolchains-plugin 1.0 29-Oct-2009
	org.apache.maven.plugins maven-ant-plugin 2.3 07-Nov-2009
	org.apache.maven.plugins maven-patch-plugin 1.1.1 01-Jan-2010
	org.apache.maven.plugins maven-repository-plugin 2.3.1 17-Jul-2010
	org.apache.maven.plugins maven-linkcheck-plugin 1.1 09-Nov-2010
	org.apache.maven.plugins maven-acr-plugin 1.0 26-Mar-2011