Open GoogleCodeExporter opened 8 years ago
Please search for "maven" in the past issues, as this has been discussed
before. There are no plans for adding Maven support, but if someone wants to
do it, please feel free to contribute.
Original comment by sype...@gmail.com
on 2 Jul 2012 at 9:04
Original comment by sype...@gmail.com
on 2 Jul 2012 at 9:17
Issue 133 has been merged into this issue.
Original comment by sype...@gmail.com
on 12 Jul 2012 at 9:45
I have made a pom file and some modifications that should make javapns play
well with Maven projects. I had to make the following changes:
1. javapns uses a customized version of org.json, which could cause conflicts
in projects that actually use the standard version. So, I refactored this
custom library into a javapns name space.
2. Added a pom file.
The attached patch is against tag 2.2, so I named the internal version 2.2.1
(since it requires a package refactoring)
Original comment by t...@teamunify.com
on 24 Aug 2012 at 6:43
Attachments:
Bill and I already had something in the works for this, although admittedly
we're no Maven experts. So I combined Bill's work with mine and yours as best
as I could and committed everything to the trunk. Could you take a look at it
and let us know if it works "as is" or if modifications are needed?
Original comment by sype...@gmail.com
on 8 Sep 2012 at 3:33
http://maven.apache.org/guides/mini/guide-central-repository-upload.html
Another thing a lot of projects do is simply host a repository directly in
their source control directory...something like /mvn-repo under the root.
http://stackoverflow.com/questions/1280470/maven-repository-for-google-code-proj
ect
Original comment by guidewir...@gmail.com
on 19 Oct 2012 at 5:32
P.S. there's also oss.sonatype.org
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage
+Guide
Original comment by guidewir...@gmail.com
on 19 Oct 2012 at 5:36
The maven pom file on the trunk isn't compiling sources into the jar file. The
jar file ends up with nothing put the pom file in it. There might be a way to
fix this without reorganizing the source tree, but i was able to get the jar
building via the maven pom (mostly as-is) by moving sources into maven's
expected project hierarchy:
src/main/java/javapns/...
src/test/java/javapns/...
i could branch and push my changes to make it work if you like.
Original comment by cr...@fancred.com
on 2 Dec 2012 at 4:47
Original issue reported on code.google.com by
raupach....@googlemail.com
on 3 May 2012 at 12:58