[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bsd.java.mk
All,
I'm working on a combination of 2 documents and a completely revised
bsd.jva.mk. The goal is provide one document for system administrators and
one for port writers. It should explain the bsd.java.mk in detail. The new
bsd.java.mk should do *exactly* what these documents claim.
Major change in the new bsd.java.mk is that you can specify the JDK you want
to use in 4 ways:
* by specifying a minimum Java version, e.g. USE_JAVA=1.2+
* by specifying an exact Java version, e.g. USE_JAVA=1.4
* by specifying a Java port, e.g. JAVA_PORT=java/linux-ibm-jdk13
* by specifying a JDK home directory, e.g. JAVA_HOME=/usr/local/jdk1.3.1
I intend to have this ready on Monday and then present it to
java@xxxxxxxxxxx, ports@FreeBSD and then to portmgr@xxxxxxxxxxx after that.
Ernst
On Wednesday 27 February 2002 14:34, Jesse McConnell wrote:
> Great idea! I think this will really help increase peoples awareness
> for java support on freebsd. I would love to get more people aware of
> how good java is on fbsd. I have run the linux JDK's a lot and they
> just seem prone to failures when you change kernel versions, or
> especially have any differences in the glibc stuff. Never really had a
> problem with java on fbsd. :)
>
> I wanted to comment on that bsd.java.mk file. I really like the
> idea of adding it as I am working jboss ports at the moment. I should
> make that a lot easier. One note that I think we might want to consider
> is where javadoc information could go.
>
> Perhaps if those are chosen to be installed then we could install them
> into ${PREFIX}share/doc/java . All javadoc apis could be installed into
> subdirs based on port name and then tweak a html file in that java
> directory adding the link to that subdir's api info. Then flash a
> message at the end of the port install mentioning that the docs are
> browsable via a local browser or by linking to that directory from
> perhaps /usr/local/www/data. That would all people to link in a page or
> directory which would provide access to all javadoc info.
>
> Another thing I have read talked about is where the jars could go on
> simple things like helper classes. I like the idea of helper classes
> getting installed in something like /usr/local/java/libs or jars. Then
> we could provide a script like the glib12-config and gtk12-config only
> for the classpath.
>
> It would be handy to be able to set your classpath with all those
> special helper classes just by typing:
>
> export CLASSPATH=`java-config`
>
> Anyway, I am about 74 messæges behind on the mailing list so sorry if
> some of this has been talked about already.
>
> my thoughts,
>
> Jesse
--
Ernst de Haan
EuroNet Internet B.V.
"Come to me all who are weary and burdened
and I will give you rest" -- Jesus Christ
To Unsubscribe: send mail to majordomo@xxxxxxxxxxx
with "unsubscribe freebsd-java" in the body of the message