RAD中集成Maven的M2Eclipse插件包及教程资源-CSDN文库

共20个文件

jar：17个

xml：2个

pdf：1个

Maven

M2Eclipse

需积分: 10 68 浏览量 2011-10-25 09:47:30 上传评论收藏 11.99MB RAR 举报

资源推荐

资源详情

资源评论

收起资源包目录

M2Eclipse.rar （20个子文件）

M2Eclipse

features

org.maven.ide.eclipse.feature_0.12.1.20110112-1712.jar 6KB

org.maven.ide.eclipse.site_0.12.1.20110112-1712.jar 6KB

org.maven.ide.eclipse.sdk.feature_0.12.1.20110112-1712.jar 5KB

content.xml 104KB

plugins

org.maven.ide.eclipse.maven_model_edit_0.12.1.20110112-1712.jar 388KB

org.maven.ide.eclipse_0.12.1.20110112-1712.jar 933KB

org.maven.ide.eclipse.jdt_0.12.1.20110112-1712.jar 119KB

org.maven.ide.eclipse.nexus_indexer_0.12.1.20110112-1712.jar 773KB

org.maven.ide.eclipse.archetype_common_0.12.1.20110112-1712.jar 1.78MB

org.maven.ide.eclipse.pr_0.12.1.20110112-1712.jar 1.66MB

org.maven.ide.eclipse.editor_0.12.1.20110112-1712.jar 625KB

org.maven.ide.eclipse.launching_0.12.1.20110112-1712.jar 81KB

org.maven.ide.eclipse.tests.common_0.12.1.20110112-1712.jar 831KB

org.maven.ide.eclipse.integration.tests.common_0.12.1.20110112-1712.jar 61KB

org.maven.ide.eclipse.dependency_tree_0.12.1.20110112-1712.jar 34KB

org.maven.ide.eclipse.refactoring_0.12.1.20110112-1712.jar 55KB

org.maven.ide.eclipse.maven_embedder_0.12.1.20110112-1712.jar 3.65MB

org.maven.ide.eclipse.editor.xml_0.12.1.20110112-1712.jar 90KB

artifacts.xml 7KB

RAD_755_MAVEN_0601.pdf 1.91MB

Page 1 of 30

Java EE Development using Rational Application

Developer 7.5.5 and Maven

by Chuck Bridgham, IBM

Introduction

IBM® Rational® Application Developer for WebSphere® 7.5 delivers a wide range of

integrated productivity enhancing tools for building Java™ EE, Web service, Portal, and

SOA solutions. Whether you are developing applications using the new EJB 3 or JPA

annotation tools, or reviewing existing applications using static code analysis, Rational

Application Developer is an IDE that integrates tools for designing, developing, testing,

and deploying your applications, effortlessly transitioning developers through the

software lifecycle.

The Apache Maven project has been around for a while, and many users have adopted the

build system’s practices and procedures, but are unsure how to integrate with a powerful

IDE such as Rational Application Developer.

This article is going to explore the basics of the Maven projects, and how they interact

with their Rational Application Developer equivalents. We’ll explore some best practices

building a Java EE 5 application targeting WebSphere Application Server 7.0. We’ll also

cover how nested projects can be used in Rational Application Developer, and what to

watch out for using a team SCM system. We’ll briefly cover some open source projects

aimed at automating many of the steps needed to integrate build environments within an

Eclipse™-based IDE such as Rational Application Developer. Finally, we’ll show a

Maven build in action using the Rational Team Concert build engine, integrated into the

Rational Application Developer 7.5 environment.

The Maven story

Whether you’re thinking about using Maven for the first time, or have been a long time

user, the benefits of the open build framework become quickly apparent. The following

is a very brief overview of Maven; more details are available on the Apache Maven home

page. (http://maven.apache.org/)

Maven assists developers and build coordinators to unify the wide range of build

requirements and standards into one system that is flexible enough for customization

while providing a common API that can be learned once and deployed company wide.

Maven has been available since 2001, and began with the desire to remove some of the

drudgery and duplication around creating ant scripts by specifying standards on simple

project types.

Page 2 of 30

With the addition of Maven plugins, standard build capabilities (goals) can be customized

and expanded. Maven archetypes are used as project templates, making it easy to enable

standards within your organization. The Maven repository not only provides a database

of sharable resources, but also shareable tasks, templates, and scripts.

What additional capabilities does Maven provide over ant?

• Predefined build conventions(or standards)

• Heavy use of defaulting

• Default tasks

• Default project structures

• Smart structured repository system

• Tools for continuous integration

Each Maven project provides a project object model (POM) file that captures

dependencies plus project properties, All of the default values can be overridden, which

adds to the size of the default POM.xml file.

Rational Application Developer can interact with Maven project structures by

understanding the project design and restrictions. The two tools can co-exist peacefully

with just a few rules and best practices.

Example 1: Rational Application Developer integration

for Maven projects

Part 1: Maven Sample Projects Explained

For this example, we will take an existing Java EE 5 application in Maven consisting of

several modules set up in a typical Maven structure, using a root project that contains an

EAR, EJB, utility, and servlet folders. We will demonstrate how to integrate these

projects into Rational Application Developer by creating projects around these existing

folders. This example will show how easy it is to compile, package, and install Maven

projects. This example does not demonstrate server test integration, because this is one of

Rational Application Developer’s strengths, which allows you to easily deploy and debug

Java EE applications to different server environments without the extra steps of

packaging and install. This example also does not integrate with any external plugins

such as m2eclipse that assist in the project classpath management based on the Maven

POM. By default, Rational Application Developer classpath management continues to

rely on static project MANIFEST files that convey the runtime availability of dependent

modules. Changing the POM.XML file will require also changing Rational Application

Developer’s dependency management located under each project’s J2EE Jar

Dependencies property sheet.

Page 3 of 30

The Maven project folder layout is standard, and is used to easily inherit properties and

behaviors from parent projects, keeping the leaf module pom.xml very clean.

Figure 1: Maven project layout

This Java EE 5 application has optional deployment descriptors in both the EJB and EAR

projects. This application will be targeting the WebSphere Application Server 7.0

runtime, which will provide the Java and Java EE runtime JAR files for compilation.

WebSphere Application Server ships a number of thin client JAR files for standalone

compilation, and are appropriate for installing into a MAVEN repository. More

information on the WebSphere Application Server 7 client JAR files is located here:

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websph

ere.base.doc/info/aes/ae/tcli_developthin.html

WebSphere Application Server provides ant tasks for deployment and server

operations

See the following information center topic

(http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.we

bsphere.base.doc/info/aes/ae/tovr_ant.html)

These tasks can be integrated using the maven-antrun-plugin

(http://maven.apache.org/plugins/maven-antrun-plugin/)

Page 4 of 30

Earlier versions of WebSphere Application Server also provide similar JAR files, and

should always be used to reflect the intended target environment. Here is an example of

installing a couple of these provided JAR files into your local Maven repository using the

WebSphere Application Server release level to specify the MAVEN artifact version.

Part 2: Preparing Maven Projects

Our two examples use most of the Maven project packaging and plugin defaults, but

several key properties are set to help integrate into the Rational Application Developer

workspace environment, and also integrate with the m2e plugins

Looking at the existing EJB project pom.xml file, you will notice the dependency to the

data project containing JPA entity classes, the EJB client JAR file, and the WebSphere

Application Server client JAR file. Some plugin properties are also set, such as the EJB

level to 3.0 to allow for an optional deployment descriptor, and specifying the existing

MANIFEST file location to use during maven packaging.

This allows Rational Application Developer to use a predefined MANIFEST file for its

development time classpath setup, rather than generating at publish time. This is an

important difference with m2eclipse sample shown later, where the MANIFEST is

generated based on the POM file contents.

mvn install:install-file -

Dfile=D:\IBM\SDP\runtimes\base_v7\runtimes\com.ibm.ws.ejb.thinclient_7.0.0.jar -

DgroupId=websphere -DartifactId=com.ibm.ws.ejb.thinclient -Dversion=7.0.0 -

Dpackaging=jar

mvn install:install-file -

Dfile=D:\IBM\SDP\runtimes\base_v7\runtimes\com.ibm.ws.jpa.thinclient_7.0.0.jar -

DgroupId=websphere -DartifactId=com.ibm.ws.jpa.thinclient -Dversion=7.0.0 -

Dpackaging=jar

Page 5 of 30

Listing 1: EJB pom.xml

Next, in the EAR project pom file, include the dependent projects, which are used to

generate an application.xml. In our example for Java EE 5, we designated this file to be

omitted, and we added this option and EAR plugin version because this is a very new

feature, not available in versions prior to v2.3.2. If this was an EAR with an existing

application.xml file, you must set the applicationXML parameter of the EAR plugin.

<groupId>root.SampleProject</groupId>

<artifactId>MyCompanyEJB</artifactId>

<name>enterprise java beans</name>

<artifactId>SampleProject</artifactId>

</parent>

<groupId>root.SampleProject.Utilities</groupId>

<artifactId>DataProject</artifactId>

</dependency>

<groupId>root.SampleProject.Utilities</groupId>

<artifactId>MyCompanyEJBClient</artifactId>

</dependency>

<groupId>websphere</groupId>

<artifactId>com.ibm.ws.ejb.thinclient</artifactId>

<scope>provided</scope>

</dependency>

</dependencies>

<build>

<finalName>${project.artifactId}</finalName>

<artifactId>maven-ejb-plugin</artifactId>

</manifest>

</archive>

</configuration>

</plugin>

<groupId>org.apache.maven.plugins</groupId>

<artifactId>maven-jar-plugin</artifactId>

<manifestFile>src/main/java/META-INF/MANIFEST.MF</manifestFile>

</archive>

</configuration>

</plugin>

</plugins>

</build>

</project>

评论收藏

内容反馈

miaoyu220

粉丝: 0
资源: 4

RAD中集成Maven的M2Eclipse插件包及教程

m2eclipse maven插件

m2eclipse插件_使用maven必备

mavenMaven的安装、配置及使用入门 -

maven安装配置指南

经过修改的eclipse一个插件

rad下集成开发web services.doc

eclipse-properties文件插件

rad下集成开发web+services.doc

RadStudio10.4.2视频安装教程.exe

使用RadStudio XE8开发iOS及Android移动应用的官方教程

RAD Studio 12 安装激活说明及常见问题

Embarcadero RAD Studio Alexandria11.1下载和安装说明

RAD Studio Delphi XE7简体中文一键汉化

RADStudio11.1KeyPatch

jad eclipse 执行文件和插件jar

IBM RAD v7.0 自带的中文安装手册

rad资料---简介

IBM RAD7.5开发指南part1(全图文教程,超灵)

RADStudio10.4.2KeyPatch.rar

RAD Studio 10.2.3 Tokyo 东京 RAD10.2 Release 3 架构师安装破解指导

IBM RAD7.5开发指南part3(全图文教程,超灵)

RadStudio 10_2_3_2631Keygen

Java第十五届蓝桥杯大赛软件JavaB组真题

SwitchHosts

安卓期末大作业（AndroidStudio开发），垃圾分类助手app，分为前台后台，代码有注释，均能正常运行

Notepad++安装包

2024北森能力测评题库.7z

微信小程序源码-合集1.rar

Java面试八股文2023最新版

最新资源