Java DB is Sun's supported distribution of the open source Apache Derby 100% Java technology database. It is fully transactional, secure, easy-to-use, standards-based SQL, JDBC API, and Java EE yet small, only 2MB. The Apache Derby project has a strong and growing community that includes developers from large companies such as Sun Microsystems and IBM as well as individual contributors. WWW: http://developers.sun.com/javadb/ Generated with FreeBSD Port Tools 0.77
Hi Yoshihiro, "make fetch" doesn't work with your port. You defined a variable DOWNLOAD_URL, but a user trying to install the port never sees the URL. You might want to have a look at how this is done in java/jdk16/Makefile. Furthermore, I'd suggest to install the documentation into DOCSDIR and use the PORTDOCS variable as described in the porter's handbook to cut down the size of pkg-plist. Can you re-send an updated version of your port? Regards, Stefan [1]: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html
Stefan: Thank you for your feedback. I was aware that the "fetch" command was not able to access to the right file. In addition, it appears that address I had became invalid. I wanted avoid manual download but it seems necessary at this point. Which documents should I move to DOCSDIR, docs only or all of docs, javadoc, and demo? Thanks, Hiro On Tue, 16 Dec 2008 17:12:44 +0100 Stefan Walter <stefan@freebsd.org> wrote: > Hi Yoshihiro, > > "make fetch" doesn't work with your port. You defined a variable > DOWNLOAD_URL, but a user trying to install the port never sees the URL. > You might want to have a look at how this is done in java/jdk16/Makefile. > Furthermore, I'd suggest to install the documentation into DOCSDIR and use > the PORTDOCS variable as described in the porter's handbook to cut down > the size of pkg-plist. > > Can you re-send an updated version of your port? > > Regards, > Stefan > > [1]: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html
Yoshihiro Ota, 17.12.08, 08:59h CET: > Stefan: > > Thank you for your feedback. > > I was aware that the "fetch" command was not able to access to the right file. > In addition, it appears that address I had became invalid. > I wanted avoid manual download but it seems necessary at this point. > > Which documents should I move to DOCSDIR, docs only or all of docs, javadoc, and demo? IMO, docs and javadoc should go to DOCSDIR, demo should go to EXAMPLESDIR. If the jar files installed by this port are supposed to be used by other ports, they should be installed to JAVAJARDIR. Regards, Stefan
Responsible Changed From-To: freebsd-ports-bugs->apache apache team
I've done all except EXAMPLESDIR. I created this port to use from NetBeans. Unfortunately, I haven't been able to use javadb from NetBeans due to lack of time and of familiarities with NetBeans, yet. Therefore, I am not fully sure if moving to these FreeBSD specific directory will still work with NetBeans. Once I have more time, I want to come back to this and verify. Thanks, Hiro On Wed, 17 Dec 2008 11:08:00 +0100 Stefan Walter <stefan@freebsd.org> wrote: > Yoshihiro Ota, 17.12.08, 08:59h CET: > > > Stefan: > > > > Thank you for your feedback. > > > > I was aware that the "fetch" command was not able to access to the right file. > > In addition, it appears that address I had became invalid. > > I wanted avoid manual download but it seems necessary at this point. > > > > Which documents should I move to DOCSDIR, docs only or all of docs, javadoc, and demo? > > IMO, docs and javadoc should go to DOCSDIR, demo should go to EXAMPLESDIR. > If the jar files installed by this port are supposed to be used by other > ports, they should be installed to JAVAJARDIR. > > Regards, > Stefan
Responsible Changed From-To: apache->freebsd-ports-bugs Over to maintainer.
State Changed From-To: open->feedback I am sorry that no committer was interested in your port until now Current version of JVAVA DB is 10.5.3.0. If you are still interested in getting this into the ports tree, you could update this port to the latest version.
State Changed From-To: feedback->closed feedback timeout