olupotd / jspf

Automatically exported from code.google.com/p/jspf
0 stars 0 forks source link

Maven repository is not available #26

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Maven repository is not available for this description.

<repository>
     <id>jspf</id>
     <name>JSPF</name>                            <url>http://jspf.googlecode.com/svn/trunk/JSPF/repository/</url>
</repository>

Original issue reported on code.google.com by igor.y...@gmail.com on 7 Mar 2011 at 1:35

GoogleCodeExporter commented 9 years ago
I've found this question/answer how to provide a fast/simple maven repo for 
your googel code project here:
http://stackoverflow.com/questions/1280470/maven-repository-for-google-code-proj
ect

jqno in his/her question links to the HowTo (s)he used to create the maven repo 
within the google-code svn repo from an ANT build process and provides his/her 
the ANT build script as example.

Original comment by hartmut....@gmail.com on 9 Mar 2011 at 9:48

GoogleCodeExporter commented 9 years ago
Two remarks:

1) The SVN repository is outdated, we only use Mercurial.
2) I have no business with Maven, however, if anyone of you is willing to 
invest some time to investigate this it might be included / hosted / provided 
on our project page. However, the solution should be completely decoupled from 
the project (e.g., don't alter the build process) and rather descriptive (e.g. 
an XML linking to some already hosted resources). 

Original comment by r.biedert on 16 Mar 2011 at 2:51

GoogleCodeExporter commented 9 years ago
Added Rick's changes to the build process, his mail below:

---

I've made a change locally to support installing jspf to a local Maven 
repository. I'm using this to push the code to my local repo then build from 
that. It's pretty unobtrusive in how it does this:
In the core build.xml, it creates two extra jars, jspf.core-1.0.2-javadoc.jar 
and jspf.core-1.0.2-sources.jar
In the top-level build.xml, it uses maven-ant-tasks to install the files into 
your local repository
If you don't use Maven or don't want to do this, you won't notice any change at 
all. If you want to use this to install to your local Maven repo, you need to 
do the following:
Put the maven-ant-tasks jar file in the lib folder of your Ant installation, on 
the Ant classpath, or specify the library using the -lib command-line option to 
Ant (see the maven-ant-tasks installation instructions)
Run the jspf build per normal (e.g. just type ant from within the jspf source 
folder).
Run ant maven to actually do the local repo installation.
One caveat to this is that jcores is called out in the pom that's generated and 
that's not available on Maven yet (I saw that there's an issue for it in the 
jcores tracking system). This will require you to install jcores in your local 
repo as well.

Hope this helps out those who are trying to use this in a Maven project!

Original comment by r.biedert on 25 May 2011 at 1:52

GoogleCodeExporter commented 9 years ago
Appears to be fixed. Please comment if you disagree. 

Original comment by r.biedert on 16 Jun 2011 at 8:57

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Installing jspf to a local Maven repository from mercurial repository.

Instructions: 

$ hg clone https://code.google.com/p/jspf/
$ cd jspf/
$ ant
$ cd dist/
$ mvn install:install-file -Dfile=jspf.core-1.0.3.jar -DgroupId=net.xeon 
-DartifactId=jspf.core -Dversion=1.0.3 -Dpackaging=jar -DgeneratePom=true
$ mvn install:install-file -Dfile=jspf.core-1.0.3-sources.jar 
-DgroupId=net.xeon -DartifactId=jspf.core -Dversion=1.0.3 -Dpackaging=jar 
-Dclassifier=sources -DgeneratePom=true
$ mvn install:install-file -Dfile=jspf.core-1.0.3-javadoc.jar 
-DgroupId=net.xeon -DartifactId=jspf.core -Dversion=1.0.3 -Dpackaging=jar 
-Dclassifier=javadoc -DgeneratePom=true

Hope this help...

Original comment by abiliofe...@planet-of-bets.com on 10 May 2012 at 10:42

GoogleCodeExporter commented 9 years ago
Hey. I was willing to try JSPF (seems to match my needs), a few years later, 
still not published in a maven repository ?

Original comment by serge.simon on 26 Nov 2014 at 4:21

GoogleCodeExporter commented 9 years ago
Looking for it in Maven as well.  Maybe project is dead?

Original comment by merlin...@gmail.com on 5 Mar 2015 at 9:29