Menu

Check out from SVN and build

Help
2010-09-24
2016-05-24
  • Thomas Weber

    Thomas Weber - 2010-09-24

    If you want to check out the project from SVN and build from source you will have to follow these steps:

    Check out the project
    a) 0.7 branch (stable)

    svn checkout https://svn.code.sf.net/p/pulse-java/code/branches/0.7/trunk pulse-java
    

    b) trunk (testing)

    svn co https://pulse-java.svn.sourceforge.net/svnroot/pulse-java/trunk pulse-java
    

    Adapt build settings

    cd pulse-java
    cp build.properties.sample build.properties
    cp build.project.properties.sample build.project.properties
    vi build.project.properties
    

    now check for the following setting and adapt as necessary:

    deploy-dir=/var/lib/tomcat5.5/webapps/pulse
    

    then save your changes

    in the "pulse-java" directory simply type

    ant
    

    and pulse will be build and deployed to the directory set in "deploy-dir".

    After you've deployed the webapp make sure the application server can write to the following directories:

    WEB-INF/hibernate-search
    WEB-INF/Vfs-public
    WEB-INF/vfs-private
    

    That's all.

    Make sure to also check "pulse in eight easy steps" for more information regarding the initial configuration.

    Hope this helps,

    Thomas

     

    Last edit: Thomas Weber 2013-02-28
  • ddietz

    ddietz - 2010-09-24

    TYPO:

    the directories for which the application-server does have to have write access are:

    WEB-INF/hibernate-search 
    WEB-INF/vfs-public 
    WEB-INF/vfs-private
    

    PLS. also make shure that the application server can write to the directory specified as location for the pulse log-file….

    instead of the above…

     
  • Zach Metcalf

    Zach Metcalf - 2013-02-25

    Thomas and Daniel,

    Thank you for posting this. I attempted to compile the source for version 0.7 and the current svn branch, but I received errors regarding these lines of code and the changes I made to get it to compile (line numbers are from the current branch):

    Node.java - line 155 changed to protected from private - setParent method

    Node.java - line 120 changed to protected from private - private int position;

    Variant.java - line 253 changed to protected from private - setParentVariant method

    I used the latest versions OpenJDK and Oracle's JDK to compile, but received the same errors. I attached the errors received on the 0.7 source. Is there a change that I should make to get them to compile instead of moving them to protected?

    Also, I just wanted to check that if I compile version .8 pre 3 build r3028, it will not generate tables? I was able to use the tables from a binary instillation I did earlier.

    Great project!

    Zach

     
  • Thomas Weber

    Thomas Weber - 2013-02-26

    Zach,

    thanks for taking your time to post here.

    You have put the finger right into the wound. Actually we were aware of the compile issues with JDK7, but since the targeted platform is still JDK6 and binary versions are working on JRE7 we had postponed the issue for quite some time. So your post has been a great incentive to finally solve this.

    The latest SVN (r3056) contains a version which cleanly compiles with Oracles JDK7. I didn't have the time to check against OpenJDK, but I suppose this will work as well.
    (see: http://pulse.torweg.org/jira/browse/PULSE-265)

    Regarding the problems with the table creation: Actually the tables have been created, but the log messages of "java.sql.DatabaseMetaData" have been confusing at least. This is a result of out upgrade to the most recent Hibernate stable (4.1). I have changed the default log level of "java.sql.DatabaseMetaData" to WARN, as this is an information you rather not see.

    If you checkout the current version all of your problems should be resolved.

    EDITED: Do not use the tables of created by the binary distribution as some of the stored entities have been upgraded and require modified tables.

    Thomas

     

    Last edit: Thomas Weber 2013-02-26
  • Zach Metcalf

    Zach Metcalf - 2013-02-26

    Thomas,

    It worked great! Sorry about the MySQL, I made an oversight on changing the database name on line 78 of pulse.xml.

    If you all would like some help testing the new release, I would be more than happy to help out!

    Thank you,

    Zach

     
  • Thomas Weber

    Thomas Weber - 2013-02-27

    Zach,

    glad it all works now :)

    If you are interested in helping us to test the new release, you are very welcome to do so. Currently we are still working on some enhancements on the JS side of the administration so it will probably take a 2-3 weeks until we are ready.

    Thomas

     

    Last edit: Thomas Weber 2013-02-28
  • Pál Kecskeméti

    Hi,
    I have build problems. After I downloaded the pulse-0.7-final-source.tar.gz and extracted it, I copied the build.properties.sample to build.properties and the build.project.properties.sample to build.project.properties. I edited the deploy-dir and app-server.start-stop-command in build.project.properties, and nothing else. After I runed the ant command in source bundle dir, It was showed BUILD FAILED. (Attached the compile output, Ubuntu 12.04 with Oracle JDK: java version "1.8.0_91").

     
  • kias eae

    kias eae - 2021-05-26
    Post awaiting moderation.

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.