Donnie Berkholz wrote:
> On 06:58 Fri 21 Sep , Alistair Bush wrote:
>> normally java-pkg_do_write_ is called to write the package.env out, as
>> can be seen, and is the default behavior for the function. What I am
>> adding is the ability to _do_write of a "[virtual|provider].env" file.
>> W
On 06:58 Fri 21 Sep , Alistair Bush wrote:
> normally java-pkg_do_write_ is called to write the package.env out, as
> can be seen, and is the default behavior for the function. What I am
> adding is the ability to _do_write of a "[virtual|provider].env" file.
> While at present it only contain
Donnie Berkholz wrote:
> On 23:20 Thu 20 Sep , Alistair Bush wrote:
>> -# Create package.env
>> -(
>> -echo "DESCRIPTION=\"${DESCRIPTION}\""
>> -echo "GENERATION=\"2\""
>> -
>> -[[ -n "${JAVA_PKG_CLASSPATH}" ]
On 23:20 Thu 20 Sep , Alistair Bush wrote:
> - # Create package.env
> - (
> - echo "DESCRIPTION=\"${DESCRIPTION}\""
> - echo "GENERATION=\"2\""
> -
> - [[ -n "${JAVA_PKG_CLASSPATH}" ]] && echo
> "CLASSPATH=\"${
I would like to commit a new java eclass within the next week.
This eclass is designed to support the functionality that Betelgeuse
outlined within a previous post.[1]
As you will be able to see, this eclass is very simple and only uses
functionality that will be provided by the java-utils-2.ecla
