I created a xml library to make the use of the standard library easier

Hey everybody,

as the title says, I created a library, to make operations with scala-xml just less frustrating.

There was a need in my daily programming work to manipulate xml-structures and the rule transformers were just unbelievably unwieldy, so I tried to write something that addresses that. The other thing I am trying to achieve is a simple saving mechanism. I don’t want to think about parsing, encoding or decoding objects, so I added functionality to basically safe and load any object.

Have there been libraries to do the same? Yes.

Though up till now they never really made anything easier and just increased the dependencies in the project.

The main goal was to make the use as easy as possible, without use of external libraries and with extensive code documentation.

The documentation hopefully helps others in creating similar things with macros or reflections.

Please check it out! ( …and if somebody knows how to use GitHub Packages, please instruct me. That would be helpful for this library)

Link to library:

Looks useful, but GitHub Packages might be a distraction. The usual way to make something available is through Maven, often using sbt-sonatype. (Yes, this is a mild hassle to set up, but once you have everything installed it’s pretty straightforward to use.)

1 Like

or even better, sbt-ci-release


I guess that would be the way to go. Thank you for the suggestions!
I am using Gradle at the moment, though. Would the switch to sbt be worthwile for this or should I look for an alternative Gradle option?

Gradle won’t let you cross compile for multiple scala versions, so probably worth switching.


That’s a good point. I will switch the build process, once I got a little more free time.
In the mean time, a new section for similar projects was added to scala/scala-xml.
So, if somebody knows some libraries similar to mine, they can be added there now.

1 Like

After finally resolving issues with sona-type, this library can be found here:


Github Packages might be a hassle that we are all better getting used to, because it is way more convenient to the people doing the publishing. It will become very prevalent.

Isn’t github packages artefact repo per source repo (or user, not sure)? This pretty much makes it a non-starter as nobody will include external repo per dependency.