与具体例子结合学习更快速,继续学习书中的例子,来了解maven的核心概念。这是个登录验证的例子,用户要输入用户名、密码、邮箱、验证码,后台会对用户名与邮箱的一致性判断,以及验证码的生成与校验,验证成功后发送邮件进行确认,用户确认后激活账户。这个登录的例子本来可以做在一个模块中,为了学习maven将其拆成了如下的模块:
web层(处理页面和servlet)
service层(用户验证,调用邮件发送和信息保存接口),该层会依赖下面的模块:
email模块,发送邮件
persistent模块,信息保存
首先我们实现单独的email模块,作为一个单独的maven项目建立,方法和helloworld项目一致,只是增加了spring和greenmail的依赖,目录结构式这个样子滴:
pom.xml:
<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.jacky.mavenexamples.account</groupId>
<artifactId>account-email</artifactId>
<version>0.0.1-SNAPSHOT</version>
<dependencies>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-core</artifactId>
<version>2.5.6</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-beans</artifactId>
<version>2.5.6</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-context</artifactId>
<version>2.5.6</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-context-support</artifactId>
<version>2.5.6</version>
</dependency>
<dependency>
<groupId>javax.mail</groupId>
<artifactId>mail</artifactId>
<version>1.4.1</version>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.7</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>com.icegreen</groupId>
<artifactId>greenmail</artifactId>
<version>1.3.1b</version>
<scope>test</scope>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-resources-plugin</artifactId>
<configuration>
<encoding>UTF-8</encoding>
</configuration>
</plugin>
</plugins>
</build>
</project>
AccountEmailServiceImpl.java
public class AccountEmailServiceImpl
implements AccountEmailService
{
private JavaMailSender javaMailSender;
private String systemEmail;
//发送邮件
public void sendMail( String to, String subject, String htmlText )
throws AccountEmailException
{
try
{
MimeMessage msg = javaMailSender.createMimeMessage();
MimeMessageHelper msgHelper = new MimeMessageHelper( msg );
msgHelper.setFrom( systemEmail );
msgHelper.setTo( to );
msgHelper.setSubject( subject );
msgHelper.setText( htmlText, true );
javaMailSender.send( msg );
}
catch ( MessagingException e )
{
throw new AccountEmailException( "Faild to send mail.", e );
}
}
public JavaMailSender getJavaMailSender()
{
return javaMailSender;
}
public void setJavaMailSender( JavaMailSender javaMailSender )
{
this.javaMailSender = javaMailSender;
}
public String getSystemEmail()
{
return systemEmail;
}
public void setSystemEmail( String systemEmail )
{
this.systemEmail = systemEmail;
}
}
account-email.xml
<bean id="propertyConfigurer"
class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
<property name="location" value="classpath:service.properties" />
</bean>
<!-- 邮件发送设置,使用的协议、端口、用户与测试用邮件服务器greenmail相同 -->
<bean id="javaMailSender" class="org.springframework.mail.javamail.JavaMailSenderImpl">
<property name="protocol" value="${email.protocol}" />
<property name="host" value="${email.host}" />
<property name="port" value="${email.port}" />
<property name="username" value="${email.username}" />
<property name="password" value="${email.password}" />
<property name="javaMailProperties">
<props>
<prop key="mail.${email.protocol}.auth">${email.auth}</prop>
</props>
</property>
</bean>
<bean id="accountEmailService"
class="com.jacky.mavenexamples.account.email.AccountEmailServiceImpl">
<property name="javaMailSender" ref="javaMailSender" />
<property name="systemEmail" value="${email.systemEmail}" />
</bean>
AccountEmailServiceTest.java
public class AccountEmailServiceTest
{
private GreenMail greenMail;
@Before
public void startMailServer()
throws Exception
{
greenMail = new GreenMail( ServerSetup.SMTP );
greenMail.setUser( "test@jacky.com", "123456" );
greenMail.start();
}
@Test
public void testSendMail()
throws Exception
{
ApplicationContext ctx = new ClassPathXmlApplicationContext( "account-email.xml" );
AccountEmailService accountEmailService = (AccountEmailService) ctx.getBean( "accountEmailService" );
String subject = "Test Subject";
String htmlText = "<h3>Test</h3>";
accountEmailService.sendMail( "testto@jacky.com", subject, htmlText );
greenMail.waitForIncomingEmail( 2000, 1 );
Message[] msgs = greenMail.getReceivedMessages();
assertEquals( 1, msgs.length );
assertEquals( subject, msgs[0].getSubject() );
assertEquals( htmlText, GreenMailUtil.getBody( msgs[0] ).trim() );
}
@After
public void stopMailServer()
throws Exception
{
greenMail.stop();
}
依赖范围
这里重点关注的是maven配置,可以看到依赖关系中出现了<scope>,因为项目在编译、测试、运行时所引用的classpath不同,maven用scope来进行区分,包括下面几种依赖范围:1.compile.默认范围,对于主代码编译运行,测试代码编译运行的classpath都有效,比如上面的spring依赖
2.test,对于测试代码编译运行有效,比如上面的junit依赖
3.provided,对于主代码的编译,测试代码编译运行有效,对主代码的运行无效。比如servlet-api,在运行时由web容器提供
4.runtime对于主代码的运行,测试代码编译运行有效,对主代码的编译无效。比如jdbc的驱动实现,编译时依赖的只是jdk的jdbc接口。
依赖传递
account-email依赖spring-core,spring-core又会依赖common-logging,则account-email间接依赖common-logging,但这要考虑到项目依赖的scope,书中也给出了依赖传递的规则,一般我们不用去考虑间接依赖的问题,交由maven处理。maven解析后的依赖不会出现goupId和artifactId相同而version不同的情况,在version冲突时会用就近原则。
依赖归类
<properties>
<springframework.version>2.5.6</springframework.version>
</properties>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-core</artifactId>
<version>${springframework.version}</version>
</dependency>
依赖解析树
仓库
有个问题是我们为什么需要快照版本呢?我们可以看到当前项目的version是
0.0.1-SNAPSHOT
为什么不是0.0.1呢?原因是目前处于开发阶段,项目代码经常变更,如果有B项目依赖此A项目,假设A的版本0.0.1,当B项目在依赖引入A的依赖后,从远程仓库下载A到本地仓库,以后无论A项目做了什么修改,B只引用本地仓库的构建,只要A的依赖版本仍然是0.0.1。SNAPSHOT的版本则解决了这个问题,凡是SNAPSHOT依赖都会进行更新,如果有更新,就重新从远程仓库下载到本地仓库,更新的频率默认是每天,也可以自己指定。当项目稳定后,成为稳定版本后就去除掉SNAPSHOT。
生命周期
maven有标准的项目构建周期,maven本身生命周期是抽象的,具体工作交给插件完成,类似于模板方法在父类中规定了生命周期,在子类中具体实现
public abstract class AbstractBuild{
public void build{
compile();
test();
deploy();
}
protected abstract void compile();
protected abstract void test();
protected abstract void deploy();
}
maven包含了3个相互独立的生命周期:clean,default,site,每个生命周期包含许多阶段,每个阶段对应一个插件目标,最重要的是default生命周期,阶段和插件目标对应为:
process-resources maven-resources-plugin:resources
compile maven-compiler-plugin:compile
.....
package maven-jar-plugin:jar
verify
install maven-install-plugin:install
上述阶段只是列举出的一部分,可以看到象verify阶段没有绑定插件目标,那如果要在项目打好jar包后,要再打个源码的包,就可以在这个阶段制定插件目标:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<executions>
<execution>
<id>attach-resource</id>
<phase>verify</phase>
<goals>
<goal>jar-no-fork</goal>
</goals>
</execution>
</executions>
</plugin>
上述插件没有指定版本,因为所有项目都会继承超级POM,超级POM中定义了核心插件的版本
这样在执行mvn verify后,target目录下就会多出account-email-0.0.1-SNAPSHOT-sources.jar文件