Maven support

[GoogleCodeExporter]

It would be great to have a public Maven repo for WAX/waxy. Since I
couldn't find one I'm now using xmlwriter
(http://mvnrepository.com/artifact/xmlwriter/xmlwriter) which seems to take
a similar, but more verbose, approach.

If you need help/assistance with this, just drop me a line. In theory it
shouldn't be hard to get this into the main Maven repo, given that it has
no external dependencies.

Original issue reported on code.google.com by daniel.l...@gmail.com on 30 Sep 2009 at 1:18

[GoogleCodeExporter]

I don't have enough experience with Maven to set that up, but if you'd like to 
do it,
I'll give you whatever access permissions you need to the project.  Just let me 
know
what you need.

Original comment by r.mark.v...@gmail.com on 1 Oct 2009 at 12:48

[GoogleCodeExporter]

Mark,

If you and daniel haven't worked out a way to get the WAX api into Maven, I'll 
gladly
help.

Thanks,
Christian

Original comment by christia...@gmail.com on 23 Oct 2009 at 10:08

[GoogleCodeExporter]

Christian,

I haven't heard anything else from Daniel, so if you'd like to proceed, that 
would be
wonderful!  Let me know if you need anything from me.

Original comment by r.mark.v...@gmail.com on 24 Oct 2009 at 12:08

[GoogleCodeExporter]

Yeah, unfortunately I let this slide. So Christian, it would be great if you 
could
get this going.

Original comment by daniel.l...@gmail.com on 24 Oct 2009 at 9:04

[GoogleCodeExporter]

Added Non-Java label.

Original comment by bgilst...@gmail.com on 23 Nov 2009 at 9:13

• Added labels: Non-Java

[GoogleCodeExporter]

Removed Non-Java label.

Original comment by bgilst...@gmail.com on 23 Nov 2009 at 9:47

• Removed labels: Non-Java

[GoogleCodeExporter]

A nice option would be to utilize codehaus' plumbing, it syncs with maven 
central. I'd be happy to mavenize the code if you are ok with it - just assign 
to me.

Original comment by manosbat...@gmail.com on 23 Aug 2011 at 2:10

• Added labels: Type-Enhancement, Usability
• Removed labels: Type-Defect

[GoogleCodeExporter]

Original comment by r.mark.v...@gmail.com on 23 Aug 2011 at 6:06

[GoogleCodeExporter]

Manos, have you had time to work on adding WAX to Maven? I got another request 
to have this done yesterday and I want to let them know the status.

Original comment by r.mark.v...@gmail.com on 2 Sep 2011 at 1:13

[GoogleCodeExporter]

Here's a patch to set up a very basic POM that allows compiling for Java 5, 
packaging and testing.

Cobertura, Emma, FindBugs and Retroweaver are not integrated yet, I'll have to 
find out how to do that later (the first three, at least, have Maven plugins).

This is sort-of usable, but incomplete. I wanted to get your feedback before 
going further.

Original comment by mwanji on 19 Dec 2011 at 8:47

Attachments:

• 01-add-pom.txt

[GoogleCodeExporter]

Wow totally forgot about this guys, sorry. mwanji that pom wont work, the main 
question is whether we want to follow Maven's Standard Directory Layout. This 
has many advantages, but the minimal changes to the java project layout are 
from:

java
    doc
    lib
    src
        com
            ociweb
    test
        com
            ociweb

to 

java

    doc
    lib
    src
        main
            java
                com
                    ociweb
        test
            java
                com
                    ociweb

at this point i can quickly patch up pom using the current layout this week 
(probably weekend) and we'll see how it goes.

Original comment by manosbat...@gmail.com on 19 Dec 2011 at 6:00

[GoogleCodeExporter]

Do you mean the POM won't work technically, won't let you integrate plugins or 
won't fit in with the project? Because I'm pretty sure it generates a usable 
JAR.

I vote for changing the project's layout to the standard if it's no big deal, 
but setting a custom layout seems fully supported.

Original comment by mwanji on 19 Dec 2011 at 6:09

[GoogleCodeExporter]

I just want to reiterate that I do plan to accept whatever patches you guys 
come up with to make a Maven POM a reality. I'm assuming that won't require all 
users of WAX to use Maven, but will provide better support for users that do 
use Maven.

Original comment by r.mark.v...@gmail.com on 19 Dec 2011 at 6:56

[GoogleCodeExporter]

Mostly meant plugin incompatibilities with non-standard directory layout are 
common. Other than that I haven't tested your pom but saw 

+       <sourceDirectory>src</sourceDirectory>
+       <testSourceDirectory>test</testSourceDirectory>

but this is just the tip of the iceberg, think of resources, docs etc. Overall 
i think we can make this work with the current directory layout and provide a 
how-to for converting to the standard. 

Original comment by manosbat...@gmail.com on 19 Dec 2011 at 7:33