Re: [saxon] Saxon-HE on Maven
|
From: Johannes.Lichtenberger <Johannes.Lichtenberger@un...> - 2012-03-07 16:14:00
|
On 03/07/2012 03:58 PM, O'Neil Delpratt wrote: > 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. I have not too much experience with maven especially deploying directly to the central maven repo (you can setup your own repo as well), but in your case maybe it's easier to use mvn deploy:deploy-file[2] to create the POM on the fly. Other than that we haven't used Ant at all, but developed a multimodule-maven project[1], maybe that would be also interesting for instance to seperate XPath, XSLT and XQuery into seperate modules, but I suppose there are too many dependencies between the different XSLT/XPath/XQuery packages. Currently our project is also restructured, but I think the maven part is done ;-) Just a remark, I think our build process is really easy, that is we have included all dependencies in the POM-files and a simple mvn deploy will work (with a settings.xml), executing the unit tests and deploying a JAR-file with all dependencies included. Especially IMHO the dependency management is well done in maven, even though I think complex POMs are too verbose (yeah well, XML ;-)) Maybe today I would use Gradle. kind regards, Johannes [1] https://github.com/disy/treetank [2] http://maven.apache.org/plugins/maven-deploy-plugin/usage.html |
Thread view
|
From: O'Neil Delpratt <oneil@sa...> - 2012-03-07 14:58:29
Attachments:
Message as HTML
|
RE: Creating a Saxon-HE Maven project and deploying it to the Maven Central Repository Dear All, 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 <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: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide 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. Kind regards, -- O'Neil Delpratt Software Developer, Saxonica Limited Email: oneil@... <mailto:oneil@...> Tel: +44 118 946 5894 Web: http://www.saxonica.com Saxonica Community Site: http://dev.saxonica.com |
|
From: Alan Painter <alan.painter@gm...> - 2012-03-07 15:50:46
|
Hi O'Neil, Very happy to see Saxonica moving to nexus deployment. That will make things simpler for a lot of people and remove yet one more hurdle to Saxonica integration/adoption. I'm not a maven expert but I can make a few suggestions. If you haven't already, I might suggest that you set up a local nexus server so that you can get a feel for it. (http://www.sonatype.org/nexus/). A local nexus isn't as constraining as maven central (doesn't require signed artifacts, etc). You can indeed upload already-built artifacts. See section (7b) "Stage Existing Artifacts" from https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide . This section uses the maven command to sign your already-built artifacts and then deploy them to the sonatype oss repository, given the POM that you've created which describes groupId/artifactId/version. That may be the simplest way, given that you are compiling from ant. Section (7c) gives an example of how to deploy from Ant as well. I can give no recommendation on this as haven't tried from Ant myself. very best wishes on this and looking forward to seeing an official saxon in maven central. -alan On Wed, Mar 7, 2012 at 3:58 PM, O'Neil Delpratt <oneil@...> wrote: > RE: Creating a Saxon-HE Maven project and deploying it to the Maven Central > Repository > > Dear All, > > 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: > > https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide > > 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. > > Kind regards, > > -- > O'Neil Delpratt > Software Developer, Saxonica Limited > Email: oneil@... > Tel: +44 118 946 5894 > Web: http://www.saxonica.com > Saxonica Community Site: http://dev.saxonica.com > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > saxon-help mailing list archived at http://saxon.markmail.org/ > saxon-help@... > https://lists.sourceforge.net/lists/listinfo/saxon-help |
|
From: Rushforth, Peter <Peter.Rushforth@NRCan-RNCan.gc.ca> - 2012-03-07 16:02:40
Attachments:
Message as HTML
|
Hi O'Neil, 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 :-) Good luck! Regards, Peter ________________________________ From: O'Neil Delpratt [mailto:oneil@...] Sent: March 7, 2012 09:58 To: Mailing list for the SAXON XSLT and XQuery processor Subject: [saxon] Saxon-HE on Maven RE: Creating a Saxon-HE Maven project and deploying it to the Maven Central Repository Dear All, 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<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: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide 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. Kind regards, -- O'Neil Delpratt Software Developer, Saxonica Limited Email: oneil@...<mailto:oneil@...> Tel: +44 118 946 5894 Web: http://www.saxonica.com Saxonica Community Site: http://dev.saxonica.com |
|
From: Johannes.Lichtenberger <Johannes.Lichtenberger@un...> - 2012-03-07 16:52:44
|
On 03/07/2012 04:50 PM, Rushforth, Peter wrote: > 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. I would definately like a source-JAR and maybe a test-JAR, for instance by using http://maven.apache.org/plugins/maven-source-plugin/usage.html http://maven.apache.org/guides/mini/guide-attached-tests.html kind regards, Johannes |
|
From: Johannes.Lichtenberger <Johannes.Lichtenberger@un...> - 2012-03-07 16:14:00
|
On 03/07/2012 03:58 PM, O'Neil Delpratt wrote: > 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. I have not too much experience with maven especially deploying directly to the central maven repo (you can setup your own repo as well), but in your case maybe it's easier to use mvn deploy:deploy-file[2] to create the POM on the fly. Other than that we haven't used Ant at all, but developed a multimodule-maven project[1], maybe that would be also interesting for instance to seperate XPath, XSLT and XQuery into seperate modules, but I suppose there are too many dependencies between the different XSLT/XPath/XQuery packages. Currently our project is also restructured, but I think the maven part is done ;-) Just a remark, I think our build process is really easy, that is we have included all dependencies in the POM-files and a simple mvn deploy will work (with a settings.xml), executing the unit tests and deploying a JAR-file with all dependencies included. Especially IMHO the dependency management is well done in maven, even though I think complex POMs are too verbose (yeah well, XML ;-)) Maybe today I would use Gradle. kind regards, Johannes [1] https://github.com/disy/treetank [2] http://maven.apache.org/plugins/maven-deploy-plugin/usage.html |
|
From: Nowakowski, Mateusz <Mateusz.Nowakowski@sa...> - 2012-03-07 16:17:27
Attachments:
Message as HTML
|
I'm not the Maven Master, but I can give some hints which seems reasonable for me. First of all I'm glad that this is really happening! >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? If the product is already build from Ant - the easiest way is to build application as it is and then deploy the Saxon artifacts with some pom.xml to the repository. In other words Saxon build remains the same, but pom.xml is needed to write. BTW There is some Saxon in the central Maven repo already: http://search.maven.org/remotecontent?filepath=net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.pom but it is bad, because it doesn't mention about Saxon dependencies. So good pom.xml should have: - Dependencies along with versions - Optional/Runtime dependencies - if necessary and nice to have: - Should have packaging bundle, not jar. However this is not trivial, because it requires making Saxon OSGI compliant. I would try to do first deployment with SNAPSHOT version of Saxon - to test different pom.xml So that better Maven masters would provide feedback whether Saxon pom.xml is only good or it is a masterpiece :) -- Regards, Mateusz Nowakowski From: O'Neil Delpratt [mailto:oneil@...] Sent: Wednesday, March 07, 2012 3:58 PM To: Mailing list for the SAXON XSLT and XQuery processor Subject: [saxon] Saxon-HE on Maven RE: Creating a Saxon-HE Maven project and deploying it to the Maven Central Repository Dear All, 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<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: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide 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. Kind regards, -- O'Neil Delpratt Software Developer, Saxonica Limited Email: oneil@...<mailto:oneil@...> Tel: +44 118 946 5894 Web: http://www.saxonica.com Saxonica Community Site: http://dev.saxonica.com |
|
From: Michael Kay <mike@sa...> - 2012-03-08 09:09:42
Attachments:
Message as HTML
|
> BTW There is some Saxon in the central Maven repo already: > > http://search.maven.org/remotecontent?filepath=net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.pom > > but it is bad, because it doesn't mention about Saxon dependencies. > > It's an unauthorised copy, and it's also bad because (a) whoever put it there didn't read the license conditions, which say that when you distribute the JAR file, you also have to distribute various notices acknowledging third-party components. We're still working out how best to do that. (b) whoever put it there didn't accept that there was a responsibility to keep it up to date. Michael Kay Saxonica |
|
From: O'Neil Delpratt <oneil@sa...> - 2012-03-09 17:14:15
Attachments:
Message as HTML
|
Thanks very much to all those who gave helpful advice on Saxon-HE and maven. I managed to deploy Saxon-HE 9.4 to the central repository, which should now be available to maven users. Please see: https://oss.sonatype.org/content/groups/public/net/sf/saxon/Saxon-HE/ As suggested in section 7c in the setup guide below, I used the ant script for the deploying. I also found the following useful when uploading the required files and releasing the project: https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository kind regards, O'Neil On 07/03/12 14:58, O'Neil Delpratt wrote: > RE: Creating a Saxon-HE Maven project and deploying it to the Maven > Central Repository > > Dear All, > > 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 <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: > > https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide > > 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. > > Kind regards, > > -- > O'Neil Delpratt > Software Developer, Saxonica Limited > Email: oneil@... <mailto:oneil@...> > Tel: +44 118 946 5894 > Web: http://www.saxonica.com > Saxonica Community Site: http://dev.saxonica.com > > > ------------------------------------------------------------------------------ > Virtualization& Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > > > _______________________________________________ > saxon-help mailing list archived at http://saxon.markmail.org/ > saxon-help@... > https://lists.sourceforge.net/lists/listinfo/saxon-help -- O'Neil Delpratt Software Developer, Saxonica Limited Email: oneil@... <mailto:oneil@...> Tel: +44 118 946 5894 Web: http://www.saxonica.com Saxonica Community Site: http://dev.saxonica.com |
|
From: Alan Painter <alan.painter@gm...> - 2012-03-09 17:23:12
Attachments:
Message as HTML
|
Congratulations and thanks very much. -alan On Mar 9, 2012 6:16 PM, "O'Neil Delpratt" <oneil@...> wrote: > Thanks very much to all those who gave helpful advice on Saxon-HE and > maven. I managed to deploy Saxon-HE 9.4 to the central repository, which > should now be available to maven users. Please see: > > https://oss.sonatype.org/content/groups/public/net/sf/saxon/Saxon-HE/ > > As suggested in section 7c in the setup guide below, I used the ant script > for the deploying. I also found the following useful when uploading the > required files and releasing the project: > > https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository > > kind regards, > O'Neil > > > > > > > On 07/03/12 14:58, O'Neil Delpratt wrote: > > RE: Creating a Saxon-HE Maven project and deploying it to the Maven > Central Repository > > Dear All, > > 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: > > > https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide > > 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. > > Kind regards, > > -- > O'Neil Delpratt > Software Developer, Saxonica Limited > Email: oneil@... > Tel: +44 118 946 5894 > Web: http://www.saxonica.com > Saxonica Community Site: http://dev.saxonica.com > > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service.http://www.accelacomm.com/jaw/sfnl/114/51521223/ > > > > _______________________________________________ > saxon-help mailing list archived at http://saxon.markmail.org/saxon-help@...://lists.sourceforge.net/lists/listinfo/saxon-help > > > > -- > O'Neil Delpratt > Software Developer, Saxonica Limited > Email: oneil@... > Tel: +44 118 946 5894 > Web: http://www.saxonica.com > Saxonica Community Site: http://dev.saxonica.com > > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > saxon-help mailing list archived at http://saxon.markmail.org/ > saxon-help@... > https://lists.sourceforge.net/lists/listinfo/saxon-help > |