This is great news for the java xml community. I suggest you ask the Maven users list these questions, as they are
sure to get you going in the right direction.
I think there are two use cases which could be resolved here:
1) using saxon he jar as a dependancy in your java project so you can use xslt 2 / xquery / xpath 2 from your java code (for example)
2) customizing / extending saxon he.
I think the first use case would require a complete dependancies section which would allow projects to pull in saxon and its dependencies.
I don't believe this requires building saxon from source, simply that the saxon jar file with appropriate project metadata in the form of a pom.xml
be registered in maven central repository. How to do that would be a subject for the maven community.
The second use case would also be supported by maven. The svn repository to which public access is available would
be referenced by the pom.xml, such that when the system was built, maven would pull the latest source code.
You never know, you might find that a maven saxon he project would fit nicely as a subproject, or profile of a maven saxon project.
We use continuum to build and test our maven project, and although there is a learning curve, my impression is that for multi-developer
situations it is worthwhile.
Although ant integration is supported by maven, I believe through a facility called maven assemblies, that's not "the maven way".
Maven tries to declare dependancies,
and not approach them procedurally. Kind of like XSLT !
I am not an expert with maven, and yes, it is quite complex. But, I think it's worth the effort, sort of like XSLT!
Maybe a separate maven saxon mailing list would be beneficial? I would subscribe :-)
RE: Creating a Saxon-HE Maven project and deploying it to the Maven Central Repository
We have had over the years user requests for making the open source Saxon product available via Maven and I have assigned the task to make it happen.
I am pretty new to Maven and have spent several hours trying to get Saxon-HE deployed to the Maven central repository and still not have had much success. I am hoping that someone on the mailing list has had better success with Maven, which can help or at least
point me in the write direction with some useful advice.
First a question about requirements: is there a need to deploy in such a way that Saxon can be built from the Subversion source repository, or do we only need to deposit the JAR file?
I have read many guides, forum posts and the Maven website itself (
http://maven.apache.org), but it all seems overly complicated and difficult to find the right information. However I found a guide which was somewhat easier to follow:
I have followed the general setup of creating a POM.xml file with the project configuration. If I can get some interest in this topic I will issue the POM.xml file.
Most of the documentation suggests maven needs to build from the source, which isn't easy given the complexity of the Saxon build. Therefore I included the ant plugin which allows us to build the product in an ant script wrapped in Maven. I have reached the
point where I need to deploy the product and it's not tying together the ant build and the compiled code.
It may turn out that I am doing totally the wrong thing. Any offers of help are welcome.