| Issue 107: | Repository for JMesa | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Hi Jeff, Did you manage to set up a maven repository for JMesa? I read in here that you wanted to do so...: http://mail-archives.apache.org/mod_mbox/maven-issues/200804.mbox/%3C17536455.1207018318280.JavaMail.haus-jira@codehaus01.managed.contegix.com%3E I am using your component in a maven 2 project and I'd really like to get the version 2.3 via maven rather than downloading it and installing it manually. Thank you! Oscar
Jun 4, 2008
#1
oscarfer...@gmail.com
Jun 4, 2008
I got stalled out when the pom.xml was not accepted by the Maven folks. I do not use Maven myself so I really want the community to maintain that file. I do try to keep it up to date but I do not do anything with it. I would also be willing to set up my subversion repository (or Go Daddy Site) to act as a place to download the jmesa.jar file but someone would have to show me what it takes to set that up. I remember someone was going to help me with that but I never did hear back from that person. -Jeff Johnston
Jun 5, 2008
Hi, I send you attached a pom file for the version 2.3.1 as well as the bundled jar. I have added images, css and js files in the bundled jar and I have changed the version of xhtmlrenderer so that it matches an existing version in mvnrepository.com . I may have made some mistakes so please double check those and feel free to correct the pom.xml at your disposal. I think that now your project should get accepted in mvnrepository.com as they have included xhtmlrenderer :)
Jun 5, 2008
After testing the pom.xml myself I found some problems with non-existing dependencies. I fixed them all. The only problem is that I didn't find itext-paulo. I used itext 1.3.1 instead. Not sure if it is the same though... Anyway I don't need pdf export so even if it is not the same library for me this pom.xml works fine. Br, Oscar
Jun 5, 2008
Thanks! I will try getting it uploaded to the Maven repositories again. Is there a way that developers could download it from my site? You know, some way to set up my site as a repository for the jmesa.jar file.
Jun 6, 2008
Sorry I have no experience myself but what I know is that you need to set up a maven repository. I found this article that seems pretty good but I guess you can find better info by googling a bit http://www.theserverside.com/tt/articles/article.tss?l=SettingUpMavenRepository It'd be really nice if you set up a maven repo :) Thanks! Oscar
Jul 30, 2008
(No comment was entered for this change.)
Labels:
-Type-Defect Type-Task
Oct 12, 2008
The real issue here is not finding a repository perse but that jmesa (and hence the maven pomfile) references dependencies that have not been deployed to a global maven repository themselves. If we can tidy up the dependencies then deploying to the global maven repositories will be the easy and appropriate option. Some of the dependency issues look like they can be resolved easily and I have attached a pomfile for jmesa 2.3.4 with the corrections that I am trying to work with at present. Several of the artifacts referenced in the jmesa 2.3.1 attachment further up in this thread have been deployed to the global repositories but not with the specified groupid/artifactid details. I have updated the following entries to reflect this: - jexcel - poi - xhtmlrenderer/core-renderer - tagsoup (check the attached pomfile for specific details of the changes) I am less certain about the dependency on groupId:xhtmlrenderer; artifactId:itext-pauloversion:155 This looks like it should be groupId:com.lowagie; artifactId:itext but v155 was never deployed to the global repositories The itext history page http://www.1t3xt.com/about/history.php suggests that there's a reasonable chance that anything that was in the v155 branch is probably in the current version by now so it'd be nice if someone could actually test that theory. Unfortunately I don't have any pdf test cases on hand to see if it works or not. Once that is sorted there should be no issues with getting jmesa itself deployed to the global maven repositories and there would be marginal value (if any) having your own repository here. The only value I would see in hosting your own public repository is for beta testing of snapshot versions. Laurie
Oct 13, 2008
Thank you! This is great. I will look into it this week yet and try applying your patch. I was hoping someone from the community would pick this up again. The original pom.xml file was donated to the project, but not maintained... I was only suggesting the separate repository when it looked like the Maven folks were not going to accept the pom.xml file because of dependencies missing. Ideally I could just upload JMesa to the regular repositories.
Oct 13, 2008
Ah but the critical bit is still the itext dependancy. If jMesa can build and function correctly with the version here: http://repo1.maven.org/maven2/com/lowagie/itext/2.1.3/ then we'll be on a roll.
Oct 14, 2008
I'm sure that fine. What about the javax.portlet? It is needed at compile time, but is an optional runtime feature. I marked it as provided but does that mean that I need to install it locally myself?
Status:
Accepted
Oct 21, 2008
Provided (http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html): This is much like compile (which is the default scope), but indicates you expect the JDK or a container to provide the dependency at runtime. For example, when building a web application for the Java Enterprise Edition, you would set the dependency on the Servlet API and related Java EE APIs to scope provided because the web container provides those classes. This scope is only available on the compilation and test classpath, and is not transitive. The pom.xml file kindly submitted by chorrylan fixed some dependency artifacts, but the dependencies in the file was still not in sync with the ones specified in the ivy.xml. I've done an attempt at fixing this in the attached file.
Oct 22, 2008
When I tried to submit the JMesa jar a few releases ago for the maven repository they
required that all the jars listed in the pom.xml be in the repository. They are not
all in there and I do not want to have to put them in there myself. I don't agree
with the Maven folks being so particular about getting jar files into their
repository. I know there can be a dependency issue for some projects, but I would
think they would want to make it easy for projects to get their jars into Maven.
I do find the repository listing interesting although I wouldn't want people to start
using my site as a repository for all the jar files. I think Google would shut me
down if I did that.
But I wonder if I could put a copy of the JMesa jar file up on my GoDaddy site in a
Maven friendly folder structure. If I did that could I just ask people to put this
repository listing in their pom.xml just to grab the JMesa file? I think my site
could handle that bandwidth and it would be very convenient.
I have a jar file up there but I see that Maven is going to try and download from my
site first. If I did this it would be nice to be able to specify my site last.
<repositories>
<repository>
<id>jmesa</id>
<url>http://jmesa.org/maven</url>
</repository>
</repositories>
Oct 25, 2008
I do appreciate the help I have been given with the Maven pom.xml file. However what I would really need is for someone to create a pom.xml file that works perfectly and is something that the Maven team would be willing to accept. In addition I would need the community to work with the Maven team to submit the jar. Right now having a broken pom.xml file is confusing to developers that want to run the project locally. So, with that I have decided to let go of the Maven support. I am very happy with my Groovy build scripts and they work well. I would be fine keeping the JMesa jar file on my GoDaddy site though and people are welcome to link to it.
Status:
WontFix
Owner: jeff.johnston.mn
Oct 25, 2008
Heres a link to the wiki page... https://code.google.com/p/jmesa/wiki/MavenSupport
Mar 18, 2009
Hi, i'm using the jmesa2.4.1 and it seems that the repo http://jmesa.org/maven it doesn't exist any more... I have worked with this some weeks ago. What append to this Repo?
Mar 18, 2009
Thanks for the heads up! I will check into this first thing when I get home tonight...
Mar 18, 2009
It is still accessible. But for it to show up in the browser you have to go to one of the links that have something in it! http://jmesa.org/maven/jmesa/jmesa/2.4.1/jmesa-2.4.1.jar http://jmesa.org/maven/pom.xml |