| Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help | Search |
| Name: xom | Distribution: SUSE Linux Enterprise 15 |
| Version: 1.2b1 | Vendor: SUSE LLC <https://www.suse.com/> |
| Release: 10.63 | Build date: Wed Jun 10 00:03:12 2020 |
| Group: Development/Languages/Java | Build host: sheep90 |
| Size: 1507865 | Source RPM: jdom-1.1.3-10.63.src.rpm |
| Packager: https://www.suse.com/ | |
| Url: http://www.jdom.org | |
| Summary: XOM is a new XML object model | |
XOM is designed to be easy to learn and easy to use. It works very straight-forwardly, and has a very shallow learning curve. Assuming you're already familiar with XML, you should be able to get up and running with XOM very quickly. XOM is the only XML API that makes no compromises on correctness. XOM only accepts namespace well-formed XML documents, and only allows you to create namespace well-formed XML documents. (In fact, it's a little stricter than that: it actually guarantees that all documents are round-trippable and have well-defined XML infosets.) XOM manages your XML so you don't have to. With XOM, you can focus on the unique value of your application, and trust XOM to get the XML right. XOM is fairly unique in that it is a dual streaming/tree-based API. Individual nodes in the tree can be processed while the document is still being built. The enables XOM programs to operate almost as fast as the underlying parser can supply data. You don't need to wait for the document to be completely parsed before you can start working with it. XOM is very memory efficient. If you read an entire document into memory, XOM uses as little memory as possible. More importantly, XOM allows you to filter documents as they're built so you don't have to build the parts of the tree you aren't interested in. For instance, you can skip building text nodes that only represent boundary white space, if such white space is not significant in your application. You can even process a document piece by piece and throw away each piece when you're done with it. XOM has been used to process documents that are gigabytes in size. XOM includes built-in support for a number of XML technologies including Namespaces in XML, XPath, XSLT, XInclude, xml:id, and Canonical XML. XOM documents can be converted to and from SAX and DOM.
LGPL-2.1-or-later
* Tue Nov 12 2019 fstrba@suse.com
- Add correct requires for the packages so that they pull all
required artifacts
- Clean up the packaging a bit
* Tue Mar 26 2019 fstrba@suse.com
- Upgrade the jdom component to 1.1.3
- Modified patch:
* jdom-1.1-build.xml.patch
+ Remove unneeded hunk
- Added patch:
* jdom-1.1-OSGiManifest.patch
+ Make jdom an OSGi bundle
* Tue Nov 20 2018 fstrba@suse.com
- Removed patch:
* include-glibj.jar.patch
+ The build works since ages without glibj being present, so
removing any trace of it
* Tue Nov 20 2018 fstrba@suse.com
- Add maven pom files for the distributed jars
- Speed-up build by filtering out the failing files beforehand
and then building all with one javac invocation
* Fri Sep 29 2017 fstrba@suse.com
- Fix build with jdk9: specify java source and target level 1.6
- Modified patch:
* jdom-1.1-build.xml.patch
+ specify java source and target level 1.6
- Add more BuildRequires, in order to build more java files in
stage 1
* Thu Sep 14 2017 fstrba@suse.com
- Build with javac whose syntax is compatible with OpenJDK
* Fri May 19 2017 tchvatal@suse.com
- Expand the buildignore lines for newer jdk
* Tue Mar 31 2015 tchvatal@suse.com
- Provide and obsolete jaxen-bootstrap to avoid file conflict
* Tue Mar 24 2015 tchvatal@suse.com
- Fix namespace clash with javapackages-tools on variables
* Tue Mar 24 2015 tchvatal@suse.com
- Cleanup with spec-cleaner and add debug output
/usr/share/java/xom-1.2b1.jar /usr/share/java/xom.jar /usr/share/maven-metadata/jdom-xom.xml /usr/share/maven-poms/xom-1.2b1.pom
Generated by rpm2html 1.8.1
Fabrice Bellet, Tue Jul 9 15:53:55 2024