looks like the scheduling takes place on /r/mechanicalkeyboards on Reddit

now i have a 2nd reason to go back to NL. The first one being a stop in Rotterdam

well the plugin is reading the parameters 🙂 we are getting somewhere

Fantastic 🙂

No play time for me today, taking care of the wife.

good

I am going to hook it into CreateManifest the same way you are doing it with the gradle plugin

then once that is working I am going to see if I can hook up that scp library

but first just lets get the base functionality working

OK. Later we can just access createmanifest as a lib.

That would be much better, and probably even easier.

yes

If the format is known I prefer JAXB.

@edvin Oh, I've always used Groovy Builders/Parsers/Slurpers (http://www.groovy-lang.org/processing-xml.html) and never heard about JAXB.

@hastebrot It does all the heavy lifting and works incredibly well. You can configure custom transforms as well. Extremely easy to configure the resulting XML.

Kotlin has lightweight "kotlinx.dom" which provides useful extension properties/functions for JAXB/JAXP/StAX.

Wonder what they provide for JAXB.

E.g. builders (https://github.com/Kotlin/kotlinx.dom/blob/master/src/main/kotlin/Builder.kt) and "query functions" (https://github.com/Kotlin/kotlinx.dom/blob/master/src/main/kotlin/Dom.kt)

Ok this is primarily for

org.w3c.dom

The

kotlin.jvm

subdirectory also has functions (https://github.com/Kotlin/kotlinx.dom/blob/master/src/main/kotlin.jvm/DomJVM.kt) for

javax.xml.parsers

and

javax.xml.transform

.

JABX doesn't really require any extra tools, it's pretty complete already 🙂

I like JAXB too

not the fastest, but it works quite well

Ahh, and JAXB is primarily in

javax.xml.bind

. Have to take a deeper look into the API/examples.

I dont like the internals of maven

Its the base most webservices are build upon as with javax.rs all the marshaling unmarschalling is done behind the scene for you just annotate with

@XmlRootElement

Yeah, and only the actual root element needs that annotation.

getting the actual artifacts from the repository with maven is not a nice way to do

I have the list of artifacts and am now trying to find a decent way to get them from the repository. There is an ArtifactResolver object but it nees a ProcessRequest Object and I have not found a way yet to get that. Seems its only available when the plugin is attached to a phase. I am reading the shade plugin source to see how they do it