From 20a512240e37d0520397b9036726fbbcd78d4732 Mon Sep 17 00:00:00 2001 From: Jason van Zyl Date: Wed, 12 Oct 2005 14:26:16 +0000 Subject: [PATCH] o incorporating m1 doco git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@314927 13f79535-47bb-0310-9956-ffa450edef68 --- .../mini/guide-coping-with-sun-jars.apt | 43 ++++++++++++++++--- 1 file changed, 38 insertions(+), 5 deletions(-) diff --git a/maven-site/src/site/apt/guides/mini/guide-coping-with-sun-jars.apt b/maven-site/src/site/apt/guides/mini/guide-coping-with-sun-jars.apt index de3c0198c1..d985a02f6b 100644 --- a/maven-site/src/site/apt/guides/mini/guide-coping-with-sun-jars.apt +++ b/maven-site/src/site/apt/guides/mini/guide-coping-with-sun-jars.apt @@ -18,14 +18,47 @@ Coping with SUN JARs Another problem is that Sun's appears not to have any sort of convention for naming their own JARs so we have taken steps in suggesting some common names for Sun's artifacts. You can find a list of our suggestions here: - - ~~ Incorporate this document here. jvz. - - http://maven.apache.org/reference/standard-sun-jar-names.html - + +*-------------------------------------------+-------------------+----------------+ +|Product artifact | Group ID | Artifact ID +*-------------------------------------------+-------------------+----------------+ +| Java Activation Framework | javax.activation | activation +*-------------------------------------------+-------------------+----------------+ +| J2EE | javax.j2ee | j2ee +*-------------------------------------------+-------------------+----------------+ +| JDO | javax.jdo | jdo +*-------------------------------------------+-------------------+----------------+ +| JMS | javax.jms | jms +*-------------------------------------------+-------------------+----------------+ +| JavaMail | javax.mail | mail +*-------------------------------------------+-------------------+----------------+ +| EJB 3 | javax.persistence | ejb +*-------------------------------------------+-------------------+----------------+ +| J2EE Connector Architecture | javax.resource | connector-api +*-------------------------------------------+-------------------+----------------+ +| Java Authorization Contract for Containers| javax.security | jacc +*-------------------------------------------+-------------------+----------------+ +| Servlet | javax.servlet | servlet-api +*-------------------------------------------+-------------------+----------------+ +| Servlet JSP | javax.servlet | jsp-api +*-------------------------------------------+-------------------+----------------+ +| Servlet JSTL | javax.servlet | jstl +*-------------------------------------------+-------------------+----------------+ +| JDBC 2.0 Optional Package | javax.sql | jdbc-stdext +*-------------------------------------------+-------------------+----------------+ +| Java Transaction API (JTA) | javax.transaction | jta +*-------------------------------------------+-------------------+----------------+ +| Java XML RPC | javax.xml | jaxrpc +*-------------------------------------------+-------------------+----------------+ +| Portlet | javax.portlet | portlet-api +*-------------------------------------------+-------------------+----------------+ +| JNDI | javax.naming | jndi +*-------------------------------------------+-------------------+----------------+ + When you add a Sun dependency to your POM if you use the our suggestions as noted above then Maven 2.x can help you locate the JARs by providing the site where they can be retrieved. It is important that you follow the suggested naming conventions as even though we cannot store the JARs at Ibiblio we can store metadata about those JARs and it is the metadata that contains location and retrieval information. +