Fix LICENSE to LGPL-2.1 wrt bug #172161 and remove trailing white space from metadata.xml.

(Portage version: 2.1.2.2)

4 files changed, 21 insertions, 16 deletions

diff --git a/dev-java/gnu-jaf/ChangeLog b/dev-java/gnu-jaf/ChangeLog
index e65008b07e87..ad1941edeb93 100644
--- a/dev-java/gnu-jaf/ChangeLog
+++ b/dev-java/gnu-jaf/ChangeLog
@@ -1,6 +1,11 @@
 # ChangeLog for dev-java/gnu-jaf
-# Copyright 1999-2006 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/dev-java/gnu-jaf/ChangeLog,v 1.11 2006/12/09 09:17:40 flameeyes Exp $
+# Copyright 1999-2007 Gentoo Foundation; Distributed under the GPL v2
+# $Header: /var/cvsroot/gentoo-x86/dev-java/gnu-jaf/ChangeLog,v 1.12 2007/03/26 15:20:48 betelgeuse Exp $
+
+  26 Mar 2007; Petteri Räty <betelgeuse@gentoo.org> metadata.xml,
+  gnu-jaf-1.0-r1.ebuild, gnu-jaf-1.0-r2.ebuild:
+  Fix LICENSE to LGPL-2.1 wrt bug #172161 and remove trailing white space from
+  metadata.xml.
 
   09 Dec 2006; Diego Pettenò <flameeyes@gentoo.org> gnu-jaf-1.0-r2.ebuild:
   Add ~x86-fbsd keyword.
diff --git a/dev-java/gnu-jaf/gnu-jaf-1.0-r1.ebuild b/dev-java/gnu-jaf/gnu-jaf-1.0-r1.ebuild
index 09bd65a208ce..51dbb8d26e11 100644
--- a/dev-java/gnu-jaf/gnu-jaf-1.0-r1.ebuild
+++ b/dev-java/gnu-jaf/gnu-jaf-1.0-r1.ebuild
@@ -1,6 +1,6 @@
-# Copyright 1999-2006 Gentoo Foundation
+# Copyright 1999-2007 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/dev-java/gnu-jaf/gnu-jaf-1.0-r1.ebuild,v 1.5 2006/10/05 15:43:58 gustavoz Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-java/gnu-jaf/gnu-jaf-1.0-r1.ebuild,v 1.6 2007/03/26 15:20:48 betelgeuse Exp $
 
 inherit java-pkg
 
@@ -8,7 +8,7 @@ DESCRIPTION="GNU JAF: JavaBeans Activation Framework"
 HOMEPAGE="http://www.gnu.org/software/classpathx/jaf/jaf.html"
 SRC_URI="mirror://gnu/classpathx/activation-${PV}.tar.gz"
 
-LICENSE="GPL-2"
+LICENSE="LGPL-2.1"
 SLOT="1"
 KEYWORDS="amd64 ppc ppc64 x86"
 IUSE="doc source"
diff --git a/dev-java/gnu-jaf/gnu-jaf-1.0-r2.ebuild b/dev-java/gnu-jaf/gnu-jaf-1.0-r2.ebuild
index 1a33230a9456..ef6ae0a254bd 100644
--- a/dev-java/gnu-jaf/gnu-jaf-1.0-r2.ebuild
+++ b/dev-java/gnu-jaf/gnu-jaf-1.0-r2.ebuild
@@ -1,6 +1,6 @@
-# Copyright 1999-2006 Gentoo Foundation
+# Copyright 1999-2007 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/dev-java/gnu-jaf/gnu-jaf-1.0-r2.ebuild,v 1.3 2006/12/09 09:17:40 flameeyes Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-java/gnu-jaf/gnu-jaf-1.0-r2.ebuild,v 1.4 2007/03/26 15:20:48 betelgeuse Exp $
 
 inherit java-pkg-2
 
@@ -8,7 +8,7 @@ DESCRIPTION="GNU implementation of the JavaBeans Activation Framework"
 HOMEPAGE="http://www.gnu.org/software/classpathx/jaf/jaf.html"
 SRC_URI="mirror://gnu/classpathx/activation-${PV}.tar.gz"
 
-LICENSE="GPL-2"
+LICENSE="LGPL-2.1"
 SLOT="1"
 KEYWORDS="~amd64 ~ppc ~ppc64 ~x86 ~x86-fbsd"
 IUSE="doc source"
diff --git a/dev-java/gnu-jaf/metadata.xml b/dev-java/gnu-jaf/metadata.xml
index 7a0b159e1452..003d6fb8d011 100644
--- a/dev-java/gnu-jaf/metadata.xml
+++ b/dev-java/gnu-jaf/metadata.xml
@@ -9,14 +9,14 @@ type data. Content handler beans can be defined to handle particular
 MIME content. The JAF unites internet standards for declaring content
 with JavaBeans™.
 
-The JAF defines two mechanisms within the framework. The first, the 
-file type map, specifies the MIME content type for a given file. The 
-default implementation of this uses the UNIX mime.types format to map 
-filename extensions to MIME types. The second mechanism, the command 
-map, specifies the actions that can be applied to a given MIME content 
-type. The default implementation of this uses the standard mailcap format 
-to map actions to JavaBean™ classes. These beans can then view, edit, 
-print, or perform whatever other action is required on the underlying 
+The JAF defines two mechanisms within the framework. The first, the
+file type map, specifies the MIME content type for a given file. The
+default implementation of this uses the UNIX mime.types format to map
+filename extensions to MIME types. The second mechanism, the command
+map, specifies the actions that can be applied to a given MIME content
+type. The default implementation of this uses the standard mailcap format
+to map actions to JavaBean™ classes. These beans can then view, edit,
+print, or perform whatever other action is required on the underlying
 resource.
 </longdescription>