diff options
Diffstat (limited to 'dev-java')
| -rw-r--r-- | dev-java/Manifest.gz | bin | 55541 -> 55542 bytes | |||
| -rw-r--r-- | dev-java/bcel/Manifest | 2 | ||||
| -rw-r--r-- | dev-java/bcel/metadata.xml | 14 | ||||
| -rw-r--r-- | dev-java/jacl/Manifest | 2 | ||||
| -rw-r--r-- | dev-java/jacl/metadata.xml | 52 | ||||
| -rw-r--r-- | dev-java/jtds/Manifest | 2 | ||||
| -rw-r--r-- | dev-java/jtds/metadata.xml | 16 |
7 files changed, 44 insertions, 44 deletions
diff --git a/dev-java/Manifest.gz b/dev-java/Manifest.gz Binary files differindex b6a32702b4f2..6998a03e21a4 100644 --- a/dev-java/Manifest.gz +++ b/dev-java/Manifest.gz diff --git a/dev-java/bcel/Manifest b/dev-java/bcel/Manifest index 69b05df4d9c9..953e5851a316 100644 --- a/dev-java/bcel/Manifest +++ b/dev-java/bcel/Manifest @@ -2,4 +2,4 @@ DIST bcel-6.5.0-sources.tar.gz 1009051 BLAKE2B fd07d8a5144112efe38e30a8d10c3b6a1 DIST bcel-6.5.0-src.tar.gz 1009051 BLAKE2B fd07d8a5144112efe38e30a8d10c3b6a189a4ec70defa96c402fa88027acf84b07c15138d235354baac18bdb798d407c11ccfada7bbe7339532f829e814e2d2c SHA512 c6da4b4d4cbad3ad2b3a4c0208063e3858170356fc4f6670c95ce819f0aea69f103914875a12bf2715a869c2b19a3e79fcb55a695eb269d9937520db25da1e3d EBUILD bcel-6.5.0-r3.ebuild 2846 BLAKE2B 9fc25e787de06a3b795707fd1bb0a5c34f8c2a2b447fcd0ffee564bfb606e8479784c133f8e7c54ef90d0c318bb60ef1e0545aeffb0a289741f2f10541602f50 SHA512 5e519ae1f796b45092a2f3183c060ce0f81bdf13e91e25f3f2da5698001e664dd522dd0777ba7faf0314e0719f08a5e8d4d11b7154fdfe8a05a3700cbae9dae1 EBUILD bcel-6.5.0.ebuild 1076 BLAKE2B 53a7a80536e25669860ec17e197bb5219c965690de1c89832187ebea88738908daf8887772090b20fabcf8f5eca07f033a68f628ea3c8675ce743b0a68a79561 SHA512 c1acb164288524653f5f0aa80b7a7bf9cb0e4003015b100a727940d00cab00d4186c33faed1bf02805b9d2944ef0d7c120a7fb571686feda7e7f351d5e4989a8 -MISC metadata.xml 820 BLAKE2B a425bc2cd30a5f47f2dc92ef014869042d68c09b1ace76007fdb08d53f52162e75f357af8debf6ab4ca5454960bd44d769190e8aae40b07a5e1ad94306f833b1 SHA512 0cb5154eb87c302868af21bd968b588317584d1f8f932e09444dde078efff02ccdb8e1e45a2e2e7fb9574eb04fd6a1c3a2afb45520261601f81ff9e35783bef7 +MISC metadata.xml 824 BLAKE2B bc553409e03ae7f58cc3122683ff49d86133fcae7b528d8a224ec126e1a43ff6dc1d329f84e54ee296c9c00e077ff732309c5a7bfdf516caad770a9f9a98ad2c SHA512 86cc34324c04905815cb84b4e7aaf5395d2d61eae42d521dda76ad74bd9a03614c0ac5ab67ce0c67312f1e150cc48d397efbd2615ee8520835621ad01b667b21 diff --git a/dev-java/bcel/metadata.xml b/dev-java/bcel/metadata.xml index 5d226489e06c..fedca9bbcd0c 100644 --- a/dev-java/bcel/metadata.xml +++ b/dev-java/bcel/metadata.xml @@ -6,13 +6,13 @@ <name>Java</name> </maintainer> <longdescription lang="en"> - This is the main Reference implementation of the BCEL JavaClass API. - The Byte Code Engineering Library (formerly known as JavaClass) is intended - to give users a convenient possibility to analyze, create, and manipulate - (binary) Java class files (those ending with .class). Classes are represented - by objects which contain all the symbolic information of the given class: - methods, fields and byte code instructions, in particular. -</longdescription> + This is the main Reference implementation of the BCEL JavaClass API. + The Byte Code Engineering Library (formerly known as JavaClass) is intended + to give users a convenient possibility to analyze, create, and manipulate + (binary) Java class files (those ending with .class). Classes are represented + by objects which contain all the symbolic information of the given class: + methods, fields and byte code instructions, in particular. + </longdescription> <upstream> <remote-id type="github">apache/commons-bcel</remote-id> </upstream> diff --git a/dev-java/jacl/Manifest b/dev-java/jacl/Manifest index fb06f94a4dbb..b5c2d1ed9791 100644 --- a/dev-java/jacl/Manifest +++ b/dev-java/jacl/Manifest @@ -1,3 +1,3 @@ DIST jacl-1.4.1.tar.gz 1921630 BLAKE2B 1b5693aa79fc50b5ff7a1ef86608b640d0bf391ced72dbe5d30f30fb46b26174535aac9d0ec32e1528f16af9e54def344d2fe38602700f921d612761f706fcce SHA512 e4b906efbd3ef4ab9338e8bf2f50c3b820e25b9fbe61f194e90cc0fa128f68d64eb459f7b05171d4b86b4c9635ef483906a02952bdedcee89ccb92256b789247 EBUILD jacl-1.4.1-r2.ebuild 997 BLAKE2B 6b2f3582d787fe69fda9ae089895747db854fcc4abef997d01e1108c055f308c285a9a87cfdb7ed97a44be138ddac17e178bc1bb9e86183158568f83f92ec730 SHA512 d60647711e6a3228df4d18394fb05f15cf978243c52034b64d01e74428df9f2ab436ab8a23517615fb99b21b716198e5788d06d8e49fe08aadfb30b7943f90d4 -MISC metadata.xml 2117 BLAKE2B a5929a947338b70ae6e55e33385ec8a709d191d75d93122a56c202add8f3b9350a2f54e6c1f87ad1206235bb273c88dac1707446b2d864227b9ae6335dd03bce SHA512 8e41dac5346fafe366423a573ae61149a6f7d451219bc31ab65c1031d8f8e33318791ea08fe340fc79305f4df4fea5c26da821513912c010fca8382a74093fac +MISC metadata.xml 2143 BLAKE2B c11fb3c8aef19cd374c70ea18d5afdc335a4e05d3a899d9676edf9384eca4fe9eb570fa3c6effb57326b447278bb94d75dea3992b83a28448d8055400e539617 SHA512 14bcbe54a5f2e13d7f39b72825ed87f7d6f40975b5772759bbf399862044e07f690d38d711a18d232657a5102d57f05ea44412e760cc2d22c69ab570e0c4a794 diff --git a/dev-java/jacl/metadata.xml b/dev-java/jacl/metadata.xml index 2cb9f05ebf1a..c574f221537a 100644 --- a/dev-java/jacl/metadata.xml +++ b/dev-java/jacl/metadata.xml @@ -6,35 +6,35 @@ <name>Java</name> </maintainer> <longdescription> -The Tcl/Java project's goal is to make integrating the Java platform and the -Tcl scripting language as easy as possible. The project actually consists of -two distinct packages, called Tcl Blend and Jacl. It is important to -understand what each package provides and in what situations one might choose -to use Jacl or Tcl Blend. + The Tcl/Java project's goal is to make integrating the Java platform and the + Tcl scripting language as easy as possible. The project actually consists of + two distinct packages, called Tcl Blend and Jacl. It is important to + understand what each package provides and in what situations one might choose + to use Jacl or Tcl Blend. -Tcl Blend is a Tcl extension that makes use of JNI to facilitate communication -between a Java interpreter and a Tcl interpreter. Tcl Blend is typically used -to load a Java interpreter into an existing Tcl process, so that functionality -implemented in Java can be accessed via Tcl. One can also load Tcl Blend and -Tcl into a Java process, which is a great way to add scripting functionality -to an existing Java application. Because Tcl Blend is a normal Tcl extension, -one can use it with other popular Tcl extensions like Tk, Expect, and Itcl. + Tcl Blend is a Tcl extension that makes use of JNI to facilitate communication + between a Java interpreter and a Tcl interpreter. Tcl Blend is typically used + to load a Java interpreter into an existing Tcl process, so that functionality + implemented in Java can be accessed via Tcl. One can also load Tcl Blend and + Tcl into a Java process, which is a great way to add scripting functionality + to an existing Java application. Because Tcl Blend is a normal Tcl extension, + one can use it with other popular Tcl extensions like Tk, Expect, and Itcl. -Jacl is a self-contained implementation of a Tcl interpreter, written entirely -in Java. Jacl also includes features that facilitate communication between a -Java interpreter and a Tcl interpreter. Jacl is typically used to incorporate -scripting functionality into an existing Java application. For users who want -to avoid adding any native code to their Java applications, Jacl is the ideal -solution. + Jacl is a self-contained implementation of a Tcl interpreter, written entirely + in Java. Jacl also includes features that facilitate communication between a + Java interpreter and a Tcl interpreter. Jacl is typically used to incorporate + scripting functionality into an existing Java application. For users who want + to avoid adding any native code to their Java applications, Jacl is the ideal + solution. -Tcl Blend and Jacl define both a Tcl API and a Java API that make it easy to -call Java code from Tcl or call Tcl code from Java. For example, one could -allocate a Java object in a Tcl script and interactively invoke Java methods -on the object. It is also easy to use the supplied API to evaluate a Tcl -procedure from a Java method or implement Tcl procudures in Java. The flexible -API and wealth of implementation options provided by the Tcl/Java project make -integrating Tcl and Java easy. -</longdescription> + Tcl Blend and Jacl define both a Tcl API and a Java API that make it easy to + call Java code from Tcl or call Tcl code from Java. For example, one could + allocate a Java object in a Tcl script and interactively invoke Java methods + on the object. It is also easy to use the supplied API to evaluate a Tcl + procedure from a Java method or implement Tcl procudures in Java. The flexible + API and wealth of implementation options provided by the Tcl/Java project make + integrating Tcl and Java easy. + </longdescription> <upstream> <remote-id type="sourceforge">tcljava</remote-id> </upstream> diff --git a/dev-java/jtds/Manifest b/dev-java/jtds/Manifest index 3d46c0cca133..7008d60ee6da 100644 --- a/dev-java/jtds/Manifest +++ b/dev-java/jtds/Manifest @@ -1,3 +1,3 @@ DIST jtds-1.3.1-src.zip 3377625 BLAKE2B 2c5ccfa4d7c6fbb1879007b5f0e9bcfd1ae1061fc68174d1679c72f3f9806433af842d5ca8e47da69acf53b8d517522f33a901adfa35867c96a63446da5269c3 SHA512 1744219a52c7167449388d774fd5e834ef551f60548569c4c54e6caefaade1d932a3879a023869d8d9ddb29ce4ab52b6d08bc4c364d5f372ff5fa96bed6d9864 EBUILD jtds-1.3.1-r1.ebuild 868 BLAKE2B 783013e023f8d46d80749afadd51d04b573b14fe2bdf25a094720fd369d2c0f4a26a2d0bb7251ed8e031f06d7edd21b37d24fc330872448d06bc2f13381893d4 SHA512 69b78588494af578bd5897b166d51fbd43d3233eaf8579e27ac6fb18dc5c12e6c48f1377088010ae512933183fc38ac8912fc6359defaf87bf230ad37688574f -MISC metadata.xml 878 BLAKE2B 60f04108c7209daad88d8dd27f45274f7dbb2143f6524b968ac344f84f4155ecfa2a1842c4ce328862e5d341d4da7ddec564816a9d26794d2d1684f889a736a9 SHA512 90012315bece0d428ef9e8546fb439379f6a671b01338f7b112fd0f7f6002250f20a265f366e168e93960587312f28e463a621523cc3843a3748c168ccd481ac +MISC metadata.xml 886 BLAKE2B 3c3b0f91bdecf155d672435559729a8b5d0a94976cea458f6509153300e77c2aaa211f658d24c8967604a75fd25512a69436542ccb7ddb828cc3ffc11862cfdd SHA512 48c68448fec4b0cf50a072056dec281fba6d9996da8c92bf3f12d1f9727072b069d49236b9ce139966370201a6c34f792d87cf63990318b285d469935a395cf0 diff --git a/dev-java/jtds/metadata.xml b/dev-java/jtds/metadata.xml index 7b2a6acb973a..bb04112b5b30 100644 --- a/dev-java/jtds/metadata.xml +++ b/dev-java/jtds/metadata.xml @@ -6,14 +6,14 @@ <name>Java</name> </maintainer> <longdescription> -jTDS is an open source 100% pure Java (type 4) JDBC 3.0 driver for Microsoft SQL -Server (6.5, 7, 2000 and 2005) and Sybase (10, 11, 12). jTDS is based on the -work of the FreeTDS project and is currently the fastest complete JDBC driver -for SQL Server and Sybase. Starting with release 0.9 jTDS is 100% JDBC 3.0 -compatible, supporting forward-only and scrollable/updateable ResultSets, -multiple concurrent (completely independent) Statements per Connection and -implementing all the DatabaseMetaData and ResultSetMetaData methods. -</longdescription> + jTDS is an open source 100% pure Java (type 4) JDBC 3.0 driver for Microsoft SQL + Server (6.5, 7, 2000 and 2005) and Sybase (10, 11, 12). jTDS is based on the + work of the FreeTDS project and is currently the fastest complete JDBC driver + for SQL Server and Sybase. Starting with release 0.9 jTDS is 100% JDBC 3.0 + compatible, supporting forward-only and scrollable/updateable ResultSets, + multiple concurrent (completely independent) Statements per Connection and + implementing all the DatabaseMetaData and ResultSetMetaData methods. + </longdescription> <upstream> <remote-id type="sourceforge">jtds</remote-id> </upstream> |