mmit 1815316 from [~rhillegas] in branch 'code/trunk'
[ https://svn.apache.org/r1815316 ]
DERBY-6974: Change byte code level generated by Derby build from Java 8 to Java
9; commit derby-6974-02-ab-minVersion9.diff.
> Deprecate support for building
4-02-ab-minVersion9.diff.
> Deprecate support for building Derby under JDK 8
>
>
> Key: DERBY-6974
> URL: https://issues.apache.org/jira/browse/DERBY-6974
> Project: Derby
>
for the extra explanation!
> Deprecate support for building Derby under JDK 8
>
>
> Key: DERBY-6974
> URL: https://issues.apache.org/jira/browse/DERBY-6974
> Project: Derby
>
adjusts the min version to 9
rather than 1.9. I suspect that 1.9 is an undocumented synonym for 9. I am
re-running the tests.
> Deprecate support for building Derby under JDK 8
>
>
> Key: DERBY-6974
>
(1.8 was a synonym for level 8). I will refresh the
patch. Does that answer your question?
> Deprecate support for building Derby under JDK 8
>
>
> Key: DERBY-6974
> URL: https://issues.apache.org/ji
iler level for Ant affect the version that
Derby runs with?
Did you mean to say, "Derby no longer *builds* on Java 8 and earlier"?
Or is this compilerproperties setting somehow embedded into our distributed
binaries?
> Deprecate support for building
/properties/defaultcompiler.properties
> Deprecate support for building Derby under JDK 8
>
>
> Key: DERBY-6974
> URL: https://issues.apache.org/jira/browse/DERBY-6974
> Project: Derby
>
ties/defaultcompiler.properties still needs to be changed:
min.version needs to be 1.9 rather than 1.8
> Deprecate support for building Derby under JDK 8
>
>
> Key: DERBY-6974
> URL: https://issues.apache.org/jir
mmit 1813709 from [~rhillegas] in branch 'code/trunk'
[ https://svn.apache.org/r1813709 ]
DERBY-6974: Convert Derby build to JDK 9 and compile at Java 9 byte code level.
> Deprecate support for building Derby under JDK 8
>
>
>
1-ab-deprecateJDK8.diff. Tests were run on
sane and insane jars. Tests included full upgrade tests, starting at every
previous release of Derby. Verified that javadoc builds cleanly.
I believe that this patch is ready to be committed.
> Deprecate support for building Derby unde
. This corrects a bug in the
previous patch: the client jar file did not include the JCBC 4.2 support. I
will continue running tests.
> Deprecate support for building Derby under JDK 8
>
>
> Key: DERBY-6974
>
to jdk8-specific build variables.
3) Simplifies the instructions for building Derby.
Touches the following files:
M java/build/org/apache/derbyBuild/javadoc/DiskLayoutTaglet.java
M java/build/org/apache/derbyBuild/javadoc/EndFormatTaglet.java
M java
Rick Hillegas created DERBY-6974:
Summary: Deprecate support for building Derby under JDK 8
Key: DERBY-6974
URL: https://issues.apache.org/jira/browse/DERBY-6974
Project: Derby
Issue Type
[
https://issues.apache.org/jira/browse/DERBY-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6857:
-
Fix Version/s: 10.14.0.0
> Deprecate support for building Derby under JDKs 6 an
When I think about it, this build step doesn't make much sense unless you
got the source from a Subversion repository... If you're not building Derby
release artifacts (i.e. producing an official Apache Derby release) you can
safely ignore those warnings and skip installing software you
Den ons. 5. jul. 2017, 20:58 skrev Indumni Ayomi >:
>
>> Hello,
>>
>> I got a error when building Derby jar files. But it shows as BUILD
>> SUCCESSFUL. I couldn't figure out the reason for this.
>> The screenshot is attached below.
>>
>
miss a version specification in the JAR file manifest(s).
Regards,
--
Kristian
Den ons. 5. jul. 2017, 20:58 skrev Indumni Ayomi :
> Hello,
>
> I got a error when building Derby jar files. But it shows as BUILD
> SUCCESSFUL. I couldn't figure out the reason for this.
> The screenshot is attached below.
>
Hello,
I got a error when building Derby jar files. But it shows as BUILD
SUCCESSFUL. I couldn't figure out the reason for this.
The screenshot is attached below.
[
https://issues.apache.org/jira/browse/DERBY-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas closed DERBY-6857.
> Deprecate support for building Derby under JDKs 6 an
issue.
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
> Key: DERBY-6857
> URL: https://issues.apache.org/jira/browse/DERBY-6857
> Project: Derby
>
e on this issue?
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
> Key: DERBY-6857
> URL: https://issues.apache.org/jira/browse/DERBY-6857
> Project: Derby
>
mmit 1740656 from [~rhillegas] in branch 'code/branches/10.12'
[ https://svn.apache.org/r1740656 ]
DERBY-6857: Port 1727680 (derby-6857-04-aa-pruneConstantClasses.diff) from
trunk to the 10.12 branch.
> Deprecate support for building Derby u
in DERBY-6236, from when
we dropped support for JDK 5.
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
> Key: DERBY-6857
> URL: https://issues.apache.org/jira/browse/DERBY-6857
>
constants for Java 6 and 7
from the JVMInfo class, since those Java versions are no longer supported.
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
> Key: DERBY-6857
>
mmit 1728767 from [~knutanders] in branch 'code/trunk'
[ https://svn.apache.org/r1728767 ]
DERBY-6857: Deprecate support for building Derby under JDKs 6 and 7
Remove the JVMInfo constants for Java 6 and 7, since they are no longer
supported.
> Deprecate support for building Derby u
mmit 1728732 from [~knutanders] in branch 'code/trunk'
[ https://svn.apache.org/r1728732 ]
DERBY-6857: Deprecate support for building Derby under JDKs 6 and 7
Make ClassInvestigator understand the new byte codes added in Java 7
to support InvokeDynamic and lambda. Also transform an in
the VMDescriptor interface are described in more
detail here:
https://docs.oracle.com/javase/specs/jvms/se8/html/jvms-4.html#jvms-4.4
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
>
aches ClassInvestigator how to handle the new byte codes,
and it transforms an inner class into a lambda expression to verify that it
works.
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
>
ort for building Derby under JDKs 6 and 7
> ---
>
> Key: DERBY-6857
> URL: https://issues.apache.org/jira/browse/DERBY-6857
> Project: Derby
> Issue Type: Bug
> Componen
mmit 1728371 from [~knutanders] in branch 'code/trunk'
[ https://svn.apache.org/r1728371 ]
DERBY-6857: Change source level to 1.8 in the NetBeans project configuration
> Deprecate support for building Derby u
rated for inlined constant.
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
> Key: DERBY-6857
> URL: https://issues.apache.org/jira/browse/DERBY-6857
> Projec
mmit 1727680 from [~rhillegas] in branch 'code/trunk'
[ https://svn.apache.org/r1727680 ]
DERBY-6857: Make classlister prune the constants files from the rosters of jar
file contents; commit derby-6857-04-aa-pruneConstantClasses.diff.
> Deprecate support for building Derby u
The full tests ran cleanly for me.
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
> Key: DERBY-6857
> URL: https://issues.apache.org/jira/browse/DERBY-6857
> Project:
n my latest build, and nothing showed up
that contained any hint of a class-packaging problem, so your patch
seems like good news to me.
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
>
ecate support for building Derby under JDKs 6 and 7
> ---
>
> Key: DERBY-6857
> URL: https://issues.apache.org/jira/browse/DERBY-6857
> Project: Derby
> Issue Type: Bug
problem which you are
seeing on Windows?
Touches the following file:
M java/build/org/apache/derbyBuild/classlister.java
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
> Key
are seeing.
I will need your help to verify that the build works smoothly for you on
Windows after I check in the improvement to classlister. Thanks!
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
>
compiler is
acting differently than the compilers on the Mac and on Linux.
I'm fine with your proposed change to ClassLister; let me know if there's
anything I can do to help.
> Deprecate support for building Derby under JDKs 6 and 7
>
n everyone having the latest version of JDK 8. I recommend that we
adjust classlister so that it omits the files of pure constants. I am happy to
make this change.
What are your thoughts?
Thanks,
-Rick
> Deprecate support for building Derby under
\apache\derby\iapi\types
01/25/2016 09:17 PM20,068 TypeId.class
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
> Key: DERBY-6857
> URL: https://issues.apache.org/jira/br
ools or in other
structures.
Thanks,
-Rick
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
> Key: DERBY-6857
> URL: https://issues.apache.org/jira/browse/DERBY-6857
>
is 6602-B38E
Directory of C:\Users\Bryan\derby\trunk\classes\org\apache\derby\iapi\reference
01/25/2016 09:17 PM 6,705 DRDAConstants.class
1 File(s) 6,705 bytes
> Deprecate support for building Derby un
mac-derby-jar-verbose.txt). Maybe that will give us more information about
how those files are being pulled into your build of derby.jar.
Thanks,
-Rick
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
>
mmit 1726721 from [~rhillegas] in branch 'code/trunk'
[ https://svn.apache.org/r1726721 ]
DERBY-6857: Replace hardcoded references to 1.8 in the build scripts with a
min.version constant; commit derby-6857-03-aa-minimumVersion.diff.
> Deprecate support for building Derby u
tion: You don't need JDK 7 in order to build or run
Derby any more. The trunk won't compile or run on that old JDK. Thanks.
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
> Key: DERBY-6857
&g
ava/client/build.xml
M build.xml
M tools/ant/properties/defaultcompiler.properties
M tools/l10n/build.xml
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
> Key: DERBY-6857
>
rive, Bryan. I will give some thought to the
jardriftcheck issues.
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
> Key: DERBY-6857
> URL: https://issues.apache.org/jir
I run jardriftcheck
to be able to successfully build my sane jars under jdk 1.8 on Windows.
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
> Key: DERBY-6857
> URL: https://issues.apache.o
'ant buildjars' completes successfully, but
Subversion
now shows that I have modified '*.lastcontents' files in my derbybuild folder.
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
see these jardriftcheck errors, though.
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
> Key: DERBY-6857
> URL: https://issues.apache.org/jira/browse/DERBY-6857
> Projec
on I should try to retain JDK 7 on my Derby-related
equipment?
Or should I just go fully to JDK 8 at this time?
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
> Key: DERBY-6857
>
mmit 1726535 from [~rhillegas] in branch 'code/trunk'
[ https://svn.apache.org/r1726535 ]
DERBY-6857: Remove references to jsr 169 from the build machinery; commit
derby-6857-02-aa-cleanupOldJdks.diff.
> Deprecate support for building Derby u
ate support for building Derby under JDKs 6 and 7
> ---
>
> Key: DERBY-6857
> URL: https://issues.apache.org/jira/browse/DERBY-6857
> Project: Derby
> Issue Type: Bug
>
mmit 1726495 from [~rhillegas] in branch 'code/trunk'
[ https://svn.apache.org/r1726495 ]
DERBY-6857: Remove support for java 6 and 7; compile Derby completely into java
8 byte code; commit derby-6857-01-aa-remove6and7.diff.
> Deprecate support for building Derby u
are similar.
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
> Key: DERBY-6857
> URL: https://issues.apache.org/jira/browse/DERBY-6857
> Project: Derby
>
are similar.
> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
> Key: DERBY-6857
> URL: https://issues.apache.org/jira/browse/DERBY-6857
> Project: Derby
>
at
org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:460)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
FAILURE
g.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:460)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
FAILURES!!!
Tests ru
ting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:443)
at
org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:460)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
Adjustments to build scripts to compile classes into JDK 8 bytecode.
--
M BUILDING.html
Removes support for JDKs 6 and 7 from the build instructions.
> Deprecate support for building Derby under JDKs 6 an
Rick Hillegas created DERBY-6857:
Summary: Deprecate support for building Derby under JDKs 6 and 7
Key: DERBY-6857
URL: https://issues.apache.org/jira/browse/DERBY-6857
Project: Derby
Issue
On 9/26/13 4:34 AM, Bergquist, Brett wrote:
Thanks Rick I appreciate the time you take to answer my questions!
On Sep 25, 2013, at 9:45 PM, Rick Hillegas wrote:
Hi Brett,
Some responses inline...
On 9/25/13 5:55 PM, Bergquist, Brett wrote:
When trying to open an existing database with the
Thanks Rick I appreciate the time you take to answer my questions!
On Sep 25, 2013, at 9:45 PM, Rick Hillegas wrote:
> Hi Brett,
>
> Some responses inline...
>
> On 9/25/13 5:55 PM, Bergquist, Brett wrote:
>> When trying to open an existing database with the derby that I built from
>> the tru
Hi Brett,
Some responses inline...
On 9/25/13 5:55 PM, Bergquist, Brett wrote:
When trying to open an existing database with the derby that I built from the
trunk I get:
ERROR XJ040: Failed to start database '/Users/brett/.netbeans-derby/csemdb'
with class loader sun.misc.Launcher$AppClassLo
When trying to open an existing database with the derby that I built from the
trunk I get:
ERROR XJ040: Failed to start database '/Users/brett/.netbeans-derby/csemdb'
with class loader sun.misc.Launcher$AppClassLoader@39172e08, see the next
exception for details.
ERROR XCW00: Unsupported upgrad
15, 2013 4:32 PM
Subject: Re: Building Derby 10.8.3.0
On 2/15/2013 1:05 PM, Oskar Zinger wrote:
That actually helped. The reason I had quotes there, initially, build or ant or
something else did not like spaces in the Java path, so I enclosed it into
quotes, then I renamed the directory to
On 2/15/2013 1:05 PM, Oskar Zinger wrote:
That actually helped. The reason I had quotes there, initially, build
or ant or something else did not like spaces in the Java path, so I
enclosed it into quotes, then I renamed the directory to have no
spaces
So two possibilities
1) Now that th
:\Apache\db-derby-10.8.3.0-src>
Thanks,
Oskar
From: Katherine Marsden
To: derby-dev@db.apache.org
Sent: Friday, February 15, 2013 3:54 PM
Subject: Re: Building Derby 10.8.3.0
On 2/15/2013 11:59 AM, Oskar Zinger wrote:
Yes I get the same error, with
\Apache\db-derby-10.8.3.0-src>
*From:* Katherine Marsden
*To:* derby-dev@db.apache.org
*Sent:* Friday, February 15, 2013 2:48 PM
*Subject:* Re: Building Derby 10.8.3.0
On 2/15/2013 11:20 AM, Oskar Zinger wrote:
Kathey, I have done as you requested:
Some
, AOT enabled)
J9VM - 20090923_042924
JIT - r9_20090902_1330ifx1
GC - 20090817_AA)
JCL - 20090924_01
C:\Apache\db-derby-10.8.3.0-src>
From: Katherine Marsden
To: derby-dev@db.apache.org
Sent: Friday, February 15, 2013 2:48 PM
Subject: Re: Building Derby 10.8.3.0
On 2/15/2013 11:20 AM, Oskar Zinger wrote:
Kathey, I have done as you requested:
Some classes do compile but only few.
Here is local.properties:
jdk16="C:/IBM/Java_SDK_1.6"
j16lib=${jdk16}/jre/lib
java16compile.classpath=${j16lib}/sql.jar;${j16lib}/xml.jar;${j16lib}/ibmjcefw.jar;${j16lib}/secu
instructions for building Derby can be found at the top of
the subversion source in BUILDING.html. If you're not having any luck
setting j16lib, the next line of attack is generally to set
java16compile.classpath. As Kathey said, setting
"printCompilerProperties=true" will give
C:/IBM/Java_SDK_1.6"/jre/lib/security.jar;"C:/IBM/Java_SDK_1.6"/jre/lib/vm.jar;"C:/IBM/Java_SDK_1.6"/jre/lib/java.util.jar;"C:/IBM/Java
_SDK_1.6"/jre/lib/jndi.jar;"C:/IBM/Java_SDK_1.6"/jre/lib/logging.jar;"C:/IBM/Java_SDK_1.6"/jre/lib/jlm.jar
On 2/15/2013 10:52 AM, Oskar Zinger wrote:
Now - I get the following:
It cannot find core java.lang package - even though I have specified
rt.jar
C:\Apache\db-derby-10.8.3.0-src>ant -quiet buildsource
[javac] Fatal Error: Unable to find package java.lang in classpath
or bootclasspath
Sent: Friday, February 15, 2013 1:48 PM
Subject: Re: Building Derby 10.8.3.0
On 2/15/2013 10:35 AM, Oskar Zinger wrote:
Hi Kathey,
>
>Thanks for that, it got me a little further, but now I get the
following:
>
>C:\Apache\db-derby-10.8.3.0-src\build.xml:241: Don't
On 2/15/2013 10:35 AM, Oskar Zinger wrote:
Hi Kathey,
Thanks for that, it got me a little further, but now I get the following:
C:\Apache\db-derby-10.8.3.0-src\build.xml:241: Don't know how to set
java16compile.classpath using this environment:
Try adding
java16compile.classpath=${j16lib}/
gt;
Thanks,
Oskar
From: Katherine Marsden
To: derby-dev@db.apache.org
Sent: Friday, February 15, 2013 1:28 PM
Subject: Re: Building Derby 10.8.3.0
On 2/15/2013 10:20 AM, Oskar Zinger wrote:
Trying to build Derby 10.8.3.0 and getting the following error:
>
>
>
>C:\Ap
On 2/15/2013 10:20 AM, Oskar Zinger wrote:
Trying to build Derby 10.8.3.0 and getting the following error:
C:\Apache\db-derby-10.8.3.0-src>ant -quiet buildsource
BUILD FAILED
C:\Apache\db-derby-10.8.3.0-src\build.xml:241: Don't know how to set
java15compile.classpath, java16compile.classpath u
Trying to build Derby 10.8.3.0 and getting the following error:
C:\Apache\db-derby-10.8.3.0-src>ant -quiet buildsource
BUILD FAILED
C:\Apache\db-derby-10.8.3.0-src\build.xml:241: Don't know how to set
java15compile.classpath, java16compile.classpath using this environment:
java.vendor = IBM Co
Thanks for keeping our build documentation up to date, Bryan. Some
comments inline...
On 1/28/12 9:08 AM, Bryan Pendleton wrote:
In http://svn.apache.org/viewvc/db/derby/code/trunk/BUILDING.html
shouldn't the section on "Testing Derby" be changed?
It currently reads:
If you want to build and
In http://svn.apache.org/viewvc/db/derby/code/trunk/BUILDING.html
shouldn't the section on "Testing Derby" be changed?
It currently reads:
If you want to build and run the Derby tests, make sure that you have
downloaded the JUnit test framework. Then build all of the Derby
sources, including the
e OS X Java version detection
code save for 1.6. Any developer with a reasonably current
MacOS X install (read: the past three years) -- i.e. most
developers -- will encounter this failure building Derby on OS X.
Hi Brett,
You're right, the logic for Apple VMs
ms like the build should be updated to "do the right
>> thing" in the OS X environment. If Derby is capable of building in a pure
>> 1.6 environment (as it seems to be with Windows), I would recommend ripping
>> out all of the OS X Java version detection code save for 1.
tall (read: the past three years) -- i.e. most developers
-- will encounter this failure building Derby on OS X.
Hi Brett,
You're right, the logic for Apple VMs is different in the Derby build.
As a matter of fact, it isn't doing any detection at all - it's only
using defa
ill encounter this failure building Derby on OS X.
-Brett
/Users/brettw/Documents/dev/derby/10.6/java/engine/org/apache/derby/iapi/types/SqlXmlUtil.java:60:
package org.apache.xpath does not exist
[javac] import org.apache.xpath.XPath;
This is just a complete stab in the dark, but perhaps the Sun JDK's have a copy
of
Apache Xerces built into them
Kristian,
Here is the output of "ant -DprintCompilerProperties=true buildsource" after
removing all of my properties files (ant.properties, local.properties).
setCompilerProperties:
printCompilerProperties:
[echo] Before setting properties: compilerPropsAlreadySet =
${compilerPropsAlready
va on Macs runs on Apple's JVM, which might (it
shouldn't, but might) have some strange behavior sometimes.
Tiago
- Original Message
From: Rick Hillegas
To: derby-dev@db.apache.org
Sent: Fri, 4 June, 2010 14:03:42
Subject: Re: Building Derby on MacOS X
Hi Brett,
As Kr
building Derby on my Macbook Pro for several years now,
using both the Java 5 and the Java 6 compilers.
Thanks for your help in improving this.
Regards,
-Rick
Kristian Waagan wrote:
On 04.06.10 05:24, Brett Wooldridge wrote:
I'm looking for a little guidance on building Derby on OS X.
I ch
On 04.06.10 05:24, Brett Wooldridge wrote:
I'm looking for a little guidance on building Derby on OS X.
I checked out the trunk from SVN, and followed the build instructions:
http://svn.apache.org/viewvc/db/derby/code/trunk/BUILDING.html?view=co
While seemingly simple, I've run int
I'm looking for a little guidance on building Derby on OS X.
I checked out the trunk from SVN, and followed the build instructions:
http://svn.apache.org/viewvc/db/derby/code/trunk/BUILDING.html?view=co
While seemingly simple, I've run into a series of issues. First attempt
failed qu
Hi Nirmal,
Thanks for pointing me out.Seems like big task. Can you send me html build.
Thanks
Eranda
On Sun, Apr 25, 2010 at 10:44 AM, Nirmal Fernando wrote:
> Hi Eranda,
>
> It seems that you have to revert to JDK 1.4.2 and give a try.
> Read this
> http://mail-archives.apache.org/mod_mbox/db-der
Hi Eranda,
It seems that you have to revert to JDK 1.4.2 and give a try.
Read this
http://mail-archives.apache.org/mod_mbox/db-derby-dev/200702.mbox/%3c17891.12541.275867.705...@gargle.gargle.howl%3e,
Dag faced this problem before.
But in my case I am using JDK 1.6.0_16, and build was fine.
O
Hi Nirmal,
Thanks for reply.I try them but no Improvement. Same excetions again and
again.
Thanks
Eranda
On Sun, Apr 25, 2010 at 10:21 AM, Nirmal Fernando wrote:
> Hi Eranda,
>
> I checked out revision 937596 yesterday, and the tools built fine in
> Vista. Give another try after re-checkout the D
Hi Eranda,
I checked out revision 937596 yesterday, and the tools built fine in
Vista. Give another try after re-checkout the Derby docs, and before
that have a check on DITA version (you need DITA-OT1.1.2.1)
Hope this will help you.
On Sun, Apr 25, 2010 at 10:11 AM, Eranda Sooriyabandara
wrot
Hi Bryan,
Sorry for being late to reply.
Yes this is my first time on building this. I use ant html to build the
code.
Also when I am builing this with the command "ant html.tools" I got the same
exception.
Thanks
Eranda
On Sat, Apr 24, 2010 at 6:11 AM, Bryan Pendleton wrote:
> Eranda Sooriyaban
Eranda Sooriyabandara wrote:
[xslt] com.sun.org.apache.bcel.internal.generic.ClassGenException:
Branch target offset too large for short
What can be the wrong?
Hi Eranda,
I've never seen this error before.
Is this the first time you tried to build the docs on this machine?
Which docs
Hi,
I try it to build on Windows Vista and I got a exception,
[xslt] com.sun.org.apache.bcel.internal.generic.ClassGenException:
Branch target offset too large for short
What can be the wrong?
Thanks
Eranda
On Fri, Apr 23, 2010 at 8:46 PM, Rick Hillegas wrote:
> Knut Anders Hatlen wrote:
Knut Anders Hatlen wrote:
On 04/23/10 03:20, Myrna van Lunteren wrote:
On Thu, Apr 22, 2010 at 5:50 PM, Bryan Pendleton
wrote:
C:\derbyt\docs\trunk\DITA-OT1.1.2.1\pretargets.xml:136: Fatal error
during transformation
Make sure you're using JDK 1.4. At least, that's what works
On 04/23/10 03:20, Myrna van Lunteren wrote:
> On Thu, Apr 22, 2010 at 5:50 PM, Bryan Pendleton
> wrote:
>>> C:\derbyt\docs\trunk\DITA-OT1.1.2.1\pretargets.xml:136: Fatal error
>>> during transformation
>>
>> Make sure you're using JDK 1.4. At least, that's what works for me.
>>
>> thanks,
>>
>> b
1 - 100 of 149 matches
Mail list logo
