9:35 a.m.
Author: fbricon
Date: 2012-09-13 10:35:35 -0400 (Thu, 13 Sep 2012)
New Revision: 43652
Added:
trunk/documentation/whatsnew/images/dependency_conversion.png
trunk/documentation/whatsnew/maven/maven-news-4.0.0.Alpha1.html
Modified:
trunk/documentation/whatsnew/index.html
Log:
Maven N&N for 4.0.0.Alpha1
Added: trunk/documentation/whatsnew/images/dependency_conversion.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/whatsnew/images/dependency_conversion.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Modified: trunk/documentation/whatsnew/index.html
===================================================================
--- trunk/documentation/whatsnew/index.html 2012-09-13 14:21:25 UTC (rev 43651)
+++ trunk/documentation/whatsnew/index.html 2012-09-13 14:35:35 UTC (rev 43652)
@@ -55,6 +55,8 @@
<p><a href="cdi/cdi-news-4.0.0.Alpha1.html">CDI
Tools</a></p>
<p><a href="jst/jst-news-4.0.0.Alpha1.html">JST/JSF
Tools</a></p>
+ <p><a href="maven/maven-news-4.0.0.Alpha1.html">Maven
Tools</a></p>
+
</td>
</tr>
Added: trunk/documentation/whatsnew/maven/maven-news-4.0.0.Alpha1.html
===================================================================
--- trunk/documentation/whatsnew/maven/maven-news-4.0.0.Alpha1.html
(rev 0)
+++ trunk/documentation/whatsnew/maven/maven-news-4.0.0.Alpha1.html 2012-09-13 14:35:35
UTC (rev 43652)
@@ -0,0 +1,139 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Language" content="en-us" />
+<meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1" />
+<link rel="stylesheet" href="../whatsnew.css" />
+<title>What's New in Maven Tools</title>
+<script type="text/javascript">
+
+ var _gaq = _gaq || [];
+ _gaq.push(['_setAccount', 'UA-17645367-5']);
+ _gaq.push(['_trackPageview']);
+
+ (function() {
+ var ga = document.createElement('script'); ga.type =
'text/javascript'; ga.async = true;
+ ga.src = ('https:' == document.location.protocol ? 'https://ssl' :
'http://www') + '.google-analytics.com/ga.js';
+ var s = document.getElementsByTagName('script')[0];
s.parentNode.insertBefore(ga, s);
+ })();
+
+</script></head>
+<body>
+<h1>Maven Tools</h1>
+
+<p align="right"><a href="../index.html">< Main
Index</a> <a
+href="../jst/jst-news-4.0.0.Alpha1.html">JST/JSF
></a></p>
+<table border="0" cellpadding="10" cellspacing="0"
width="80%">
+ <tr>
+ <td colspan="2">
+ <hr />
+ <h3>JBoss Maven Integration</h3>
+ <hr />
+ </td>
+ </tr>
+
+ <tr>
+ <td valign="top" align="left">
+ <a name="m2e-wtp-migration"
id="m2e-wtp-migration"></a><b>New m2e-wtp 0.16.0 (eclipse.org)
requirement</b></td>
+ <td valign="top">
+ m2eclipse-wtp is moving to Eclipse.org as <a
href="https://www.eclipse.org/m2e-wtp/">m2e-wtp</a>;. As such the
existing dependency on m2eclipse-wtp as been changed to <a
href="http://wiki.eclipse.org/M2E-WTP/New_and_Noteworthy/0.16"&...
0.16.0</a>.
+ Since the two plugins overlap and can not coexist, upgrading JBoss Tools is gonna
be a bit trickier this time around :
+ <ul>
+ <li>If you added the JBoss Tools 4.0 update site to your list of Available
Update Sites, doing "Help > Find Updates" should (after a looong time) find
m2e-wtp as a suitable replacement for m2eclipse-wtp, and everything should update
properly</li>
+ <li>If you try to update your JBoss Tools installation via "Help >
Install New Software...", m2e-wtp won't install because of the conflict with
m2eclipse-wtp (this is a bug in p2)</li>
+ <li>the safest path is to uninstall all previous Maven plugins/features or
start from a fresh Eclipse installation</li>
+ </ul>
+
+ On a somewhat related note, we made sure our JBoss Tools Maven features are fully
compatible with the new m2e 1.2 (Juno SR1).
+ </p>
+
+ <small>
+ See <a
href="https://issues.jboss.org/browse/JBIDE-12293">JBIDE-122... for
more details.
+
+ </small></p>
+ </td>
+ </tr>
+
+ <tr>
+ <td colspan="2">
+ <hr/>
+ </td>
+ </tr>
+
+
+ <tr>
+ <td valign="top" align="left">
+ <a name="conversion"
id="conversion"></a><b>Conversion of classpath entries to Maven
dependencies</b></td>
+ <td valign="top">
+ <p>Converting a java project to Maven is not always an easy task. m2e 1.1
introduced a new API that could help improve that conversion process.
+ For instance, m2e and m2e-wtp can help you convert your Java (EE) eclipse project
settings to their maven plugin configuration counterparts,
+ but so far converting Java dependencies has been a tedious manual chore.
+ </p>
+ <p>
+ In JBoss Tools 4.0, we've been toying with a new Classpath Dependency
conversion mechanism, hooked to the maven conversion process aforementioned.
+ Select a legacy Eclipse Java project, right-click then "Configure >
Convert to Maven ...". After selecting the project's maven coordinate,
+ a new Wizard will pop up, trying to identify all the project's classpath
entries as their equivalent Maven dependencies :
+ </p>
+ <img src="../images/dependency_conversion.png" />
+
+<p> Here is how it works currently:
+ <ul>
+ <li>Upon display, the wizard spawns a bunch of identification requests in
parallel</li>
+ <li>Identified dependencies are then resolved by Maven against the current
settings.xml known repositories. If they don't resolve, a warning will be
displayed</li>
+ <li>Unidentified dependencies appear with a red icon</li>
+ <li>Double-clicking on any Maven dependency will open a dialog page to edit the
dependency's details (groupId, artifactId, version, scope ...).</li>
+ </ul>
+</p>
+<p>
+ The identification mechanism itself is based on a refactored version of our previous
<a href="maven-news-3.3.0.Beta3.html"> Source Lookup feature</a> and
tries several identification methods :
+ <ul>
+ <li>checks if the jar contains maven descriptors under
META-INF/maven.</li>
+ <li>checks if the SHA1 checksum of the jar can be found in m2e's nexus
indexes.</li>
+ <li>checks if the SHA1 checksum of the jar can be identified from one of the
remote Nexus repository instances defined in Window > Preferences > JBoss Tools >
Remote Repositories.</li>
+ </ul>
+</p>
+<p>
+ Once you click Finish, any selected dependencies will be added to the generated
pom.xml. If you checked "Delete classpath entries from project",
+ all the project classpath entries will be removed from the eclipse classpath, as we
expect the Maven Dependencies Library to provide all these dependencies.
+</p>
+
+ <p><strong>Be aware this is a very alpha quality
work-in-progress</strong>.
+ For instance, UI freezes should be expected in this first iteration, caused by
the Maven resolution part;
+ "In-progress" Identification status is not correclty reported.
+ </p>
+ <p>
+ You can contribute to improve that feature by testing and reporting bug /
enhancement requests to JIRA, using the <i><a
href="https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true...
label.
+ </p>
+<p>
+ As a final note, this conversion tool is made to help you kickstart your project
migration to Maven, but won't solve all your problems :
+ <ul>
+ <li>the identification mechanism will not identify
<strong>everything</strong> (for instance, jar that are "classifier"
versions of an artifact can not be identified).</li>
+ <li>after all the dependencies have been added to your pom.xml, it's your
responsibility to prune them from any unwanted transitive dependencies.</li>
+ </ul>
+</p>
+
+
+ <p>
+ <small>
+ See <a
href="https://issues.jboss.org/browse/JBIDE-8973">JBIDE-8973... for
more details.
+ </small></p>
+ </td>
+ </tr>
+
+<tr>
+ <td colspan="2">
+ <hr/>
+ </td>
+ </tr>
+
+
+
+</table>
+
+</body>
+
+</html>
+
+