-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 With jstl fixed, I just rebuilt successfully on linux but encountered a few other minor issues.
* On my linux server, the files have the correct read permissions (this is the problem on our macs). That is, everything looks the same as Ate's listing below. * However, we're missing a logs directory: [gateway@gridfarm018 rave-0.1-incubating-SNAPSHOT]$ ./bin/startup.sh Using CATALINA_BASE: /tmp/rave-0.1-incubating-SNAPSHOT Using CATALINA_HOME: /tmp/rave-0.1-incubating-SNAPSHOT Using CATALINA_TMPDIR: /tmp/rave-0.1-incubating-SNAPSHOT/temp Using JRE_HOME: /globalhome/globalbin/jdk1.6.0_16/ Using CLASSPATH: /tmp/rave-0.1-incubating-SNAPSHOT/bin/bootstrap.jar touch: cannot touch `/tmp/rave-0.1-incubating-SNAPSHOT/logs/catalina.out': No such file or directory /tmp/rave-0.1-incubating-SNAPSHOT/bin/catalina.sh: line 372: /tmp/rave-0.1-incubating-SNAPSHOT/logs/catalina.out: No such file or directory * The .zip version does have the correct .sh files. I also rebuilt on my mac and found them. So no problem here. * However, the .sh files in the .zip that I built on linux do not have executable permissions. This is also true on my mac. * And the .zip is also missing /logs/ Marlon On 6/16/11 8:22 PM, Ate Douma wrote: > I again did a clean checkout, build and test on OS X using the latest > trunk and still have no permissions problems as you can see below: > > hal79-mac:ravetest ate$ ls -trl > total 120760 > -rw-r--r-- 1 ate staff 61825979 Jun 17 01:51 > rave-0.1-incubating-SNAPSHOT-bin.tar.gz > > hal79-mac:ravetest ate$ tar -zxf rave-0.1-incubating-SNAPSHOT-bin.tar.gz > > hal79-mac:ravetest ate$ ls -trl > total 120760 > drwxr-xr-x 12 ate staff 408 Jun 17 01:51 > rave-0.1-incubating-SNAPSHOT > -rw-r--r-- 1 ate staff 61825979 Jun 17 01:51 > rave-0.1-incubating-SNAPSHOT-bin.tar.gz > > hal79-mac:ravetest ate$ ls -trl rave-0.1-incubating-SNAPSHOT/bin > total 1216 > -rwxr-xr-x 1 ate staff 853 Jun 15 01:34 setenv.sh > -rw-r--r-- 1 ate staff 891 Jun 16 22:58 setenv.bat > -rwxr-xr-x 1 ate staff 1567 Jun 17 01:51 version.sh > -rw-r--r-- 1 ate staff 2113 Jun 17 01:51 version.bat > -rwxr-xr-x 1 ate staff 3472 Jun 17 01:51 tool-wrapper.sh > -rw-r--r-- 1 ate staff 3479 Jun 17 01:51 tool-wrapper.bat > -rw-r--r-- 1 ate staff 241274 Jun 17 01:51 tomcat-native.tar.gz > -rw-r--r-- 1 ate staff 26532 Jun 17 01:51 tomcat-juli.jar > -rwxr-xr-x 1 ate staff 1956 Jun 17 01:51 startup.sh > -rw-r--r-- 1 ate staff 2109 Jun 17 01:51 startup.bat > -rwxr-xr-x 1 ate staff 1563 Jun 17 01:51 shutdown.sh > -rw-r--r-- 1 ate staff 2108 Jun 17 01:51 shutdown.bat > -rwxr-xr-x 1 ate staff 4114 Jun 17 01:51 setclasspath.sh > -rw-r--r-- 1 ate staff 3150 Jun 17 01:51 setclasspath.bat > -rwxr-xr-x 1 ate staff 1624 Jun 17 01:51 digest.sh > -rw-r--r-- 1 ate staff 2108 Jun 17 01:51 digest.bat > -rw-r--r-- 1 ate staff 1342 Jun 17 01:51 cpappend.bat > -rw-r--r-- 1 ate staff 23546 Jun 17 01:51 commons-daemon.jar > -rw-r--r-- 1 ate staff 199453 Jun 17 01:51 commons-daemon-native.tar.gz > -rwxr-xr-x 1 ate staff 17592 Jun 17 01:51 catalina.sh > -rw-r--r-- 1 ate staff 11797 Jun 17 01:51 catalina.bat > -rw-r--r-- 1 ate staff 2374 Jun 17 01:51 catalina-tasks.xml > -rw-r--r-- 1 ate staff 22226 Jun 17 01:51 bootstrap.jar > > I've uploaded both my .tar.gz and .zip archives on google docs here: > > > https://docs.google.com/leaf?id=0B6BPc1fPmqgSYWY5NzRhMjAtODEwOC00NWIwLWI0MGUtNDhjYzQ5ZThjYTdm&authkey=CPeR5pAK > > > > https://docs.google.com/leaf?id=0B6BPc1fPmqgSNTY2ZjExZWQtNzIxNy00OWYxLWI5YzYtODE4NzNlYTVhOGIx&authkey=CPfMlI8H > > > Can you try them out and see if they work for you? > If they do, there must be something different during building on your > (and Raminder) machine. If these too fail, there must be something > different with the extraction process and/or (default) permissions on > your system. > > Both the .tar.gz and .zip should and do contain the same content. > The .zip archive is merely provided as convenience for Windows users > which often are not accustomed to tar.gz type archives. > BTW: the .zip can be used on Linux/Mac just as well (the execution bit > should be retained even within .zip archives nowadays). > > Regards, > > Ate > > On 06/16/2011 05:53 PM, Marlon Pierce wrote: > I just tried to build on a clean linux machine but the build failed: > > [ERROR] Failed to execute goal on project rave-portal: Could not > resolve dependencies for project > org.apache.rave:rave-portal:war:0.1-incubating-SNAPSHOT: Could not > find artifact javax.servlet:jstl:jar:1.2 in java.net > (http://download.java.net/maven/2/) -> [Help 1] > > I'll file a Jira ticket. > > I get the permission problems with the .tar.gz on two different macs: > > 129-79-49-102:ravetest2 mpierce$ tar -zxf > rave-0.1-incubating-SNAPSHOT-bin.tar.gz > 129-79-49-102:ravetest2 mpierce$ ls -trl > total 121696 > d-wxr----x 7 mpierce wheel 238 Jun 16 11:46 > rave-0.1-incubating-SNAPSHOT > -rw-r--r-- 1 mpierce wheel 62306184 Jun 16 11:48 > rave-0.1-incubating-SNAPSHOT-bin.tar.gz > > > and > > 129-79-49-102:ravetest2 mpierce$ sudo ls -trl > rave-0.1-incubating-SNAPSHOT/bin > total 1104 > --w----r-- 1 mpierce wheel 2113 Jun 16 11:46 version.bat > --w----r-- 1 mpierce wheel 3479 Jun 16 11:46 tool-wrapper.bat > --w----r-- 1 mpierce wheel 241274 Jun 16 11:46 tomcat-native.tar.gz > --w----r-- 1 mpierce wheel 26532 Jun 16 11:46 tomcat-juli.jar > --w----r-- 1 mpierce wheel 2109 Jun 16 11:46 startup.bat > --w----r-- 1 mpierce wheel 2108 Jun 16 11:46 shutdown.bat > --w----r-- 1 mpierce wheel 3150 Jun 16 11:46 setclasspath.bat > --w----r-- 1 mpierce wheel 2108 Jun 16 11:46 digest.bat > --w----r-- 1 mpierce wheel 1342 Jun 16 11:46 cpappend.bat > --w----r-- 1 mpierce wheel 23546 Jun 16 11:46 commons-daemon.jar > --w----r-- 1 mpierce wheel 199453 Jun 16 11:46 > commons-daemon-native.tar.gz > --w----r-- 1 mpierce wheel 11797 Jun 16 11:46 catalina.bat > --w----r-- 1 mpierce wheel 2374 Jun 16 11:46 catalina-tasks.xml > --w----r-- 1 mpierce wheel 22226 Jun 16 11:46 bootstrap.jar > > Also, is it intended for the .zip file to have only .bat and not .sh > files? This is what I get (on mac again). > > > Marlon > > > > > On 6/16/11 11:03 AM, Ate Douma wrote: >>>> On 06/15/2011 04:19 AM, Marlon Pierce wrote: >>>> Permissions of the .tar.gz are screwy on my mac: the directory doesn't >>>> have "read" permissions after I unpack it. >>>> >>>>> Hi Marlon, >>>> >>>>> I just build the distributions natively under OS X but it all simply >>>>> just works as expected. I don't have any permissions problems >>>>> either. I tried also to extract the tar.gz and .zip archives which I >>>>> build under Linux and those too worked without an issue. >>>> >>>>> Not sure therefore what exactly could be wrong on your environment. >>>>> Can others please test this as well and provide some feedback? >>>>> I haven't yet tried and tested on Windows either, but maybe someone >>>>> else did? >>>> >>>>> Ate >>>> >>>> >>>> >>>> Marlon >>>> >>>> >>>> On 6/14/11 9:52 PM, Ate Douma (JIRA) wrote: >>>>>>> >>>>>>> [ >>>>>>> https://issues.apache.org/jira/browse/RAVE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049569#comment-13049569 >>>>>>> ] >>>>>>> >>>>>>> Ate Douma commented on RAVE-59: >>>>>>> ------------------------------- >>>>>>> >>>>>>> I've committed a basic working automation for building a Rave >>>>>>> demo/bin distribution using maven-assembly-plugin and leveraging >>>>>>> the cargo plugin to setup and pre-deployed rave portal on Tomcat. >>>>>>> >>>>>>> The distribution packages can be build from the rave-project >>>>>>> folder using the "dist" profile by running: $mvn -P dist >>>>>>> This will enforce a maven clean + install and thereafter build a >>>>>>> rave-<version>-bin.tar.gz and rave-<version>-bin.zip archive. >>>>>>> Note: these artifacts are build in the rave-portal/target directory! >>>>>>> >>>>>>> Furthermore, I disabled the default enabled maven-assembly-plugin >>>>>>> attaching of these "artifacts" to the project, meaning these will >>>>>>> *not* be deployed to the remote maven repository (Nexus) during a >>>>>>> release. >>>>>>> You would need to specify -P dist anyway to get it to work, so in >>>>>>> practice this is not really needed, but for sanity reasons I'd >>>>>>> rather make sure it can't happen anyway. >>>>>>> >>>>>>> Can everyone please test drive this, including building the >>>>>>> distributions on a Windows environment and verify if these >>>>>>> distributions thereafter still are valid to be extracted and >>>>>>> executed/run on a Linux environment? >>>>>>> Specifically, please verify if the execution bit for shell scripts >>>>>>> is still set, etc. >>>>>>> >>>>>>> Furthermore, and IMO more importantly, what needs to be done is >>>>>>> providing the appropriate LICENSE and NOTICE files for the binary >>>>>>> distributions (including the rave-shindig.war and rave-portal.war). >>>>>>> I created a separate RAVE-63 issue for that. >>>>>>> >>>>>>> Finally, I've provided basic/skeleton CHANGELOG file in the >>>>>>> rave-project folder and a demo/bin specific README file, both to >>>>>>> be included in the demo distributions. >>>>>>> These also need to be filled in, for which I created issue RAVE-64 >>>>>>> >>>>>>> >>>>>>> >>>>>>>> Create automation for building of demo package >>>>>>>> ---------------------------------------------- >>>>>>>> >>>>>>>> Key: RAVE-59 >>>>>>>> URL: https://issues.apache.org/jira/browse/RAVE-59 >>>>>>>> Project: Rave >>>>>>>> Issue Type: Sub-task >>>>>>>> Reporter: Matt Franklin >>>>>>>> Assignee: Ate Douma >>>>>>>> Fix For: 0.1-INCUBATING >>>>>>>> >>>>>>>> >>>>>>>> C >>>>>>> >>>>>>> -- >>>>>>> This message is automatically generated by JIRA. >>>>>>> For more information on JIRA, see: >>>>>>> http://www.atlassian.com/software/jira >>>>>>> >>>>>>> -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJN+q+TAAoJEOEgD2XReDo5IK8H/RK7eM8IxflbkGIBeoMSzmrF 0Z5tIQSgO+aIn+CwTgnvhvcykcB75PCT3rUerailUhbcc6660aK9ln0+R6jnf0pw SbXeAyoP7lu2DyNk0DijPQoezgeOoIzowx5aKSPb0eJEg9HbGURX9ox/oO/sSjI7 wrMQERwMJAa+WnjfuZR6N5M8I+hX4dQU0OUyRV7d2Rh3A24woSJUTQFojm+sgU8y a8lWFl4Mjzwcfwz5dOm93Z48t9sVVa31HQQDu7f+oV09KqasLR22IpJkiVVKrDJI nXFvsddeTD73DNYQSyaVRGLTdZNhn4MLEV3zG//BX4iR28eCCq825CwCcLpjhDY= =n3ad -----END PGP SIGNATURE-----
