Thanks all,
I just restarted cygwin and the build went thru.. Not sure what was causing
the issue earlier.
With Regards
Jayaram
On Fri, Apr 25, 2014 at 8:31 PM, Dag H. Wanvik dag.wan...@oracle.comwrote:
You cygwin environment is missing uname(1), which could possibly trip up
ant. See if
The parser build targets aren't very fault tolerant. Try ant clobber
followed by ant buildsource.
Hope this helps,
-Rick
On 4/24/14 7:24 PM, rsjay1976 . wrote:
Hi,
When trying to build source i am facing the following issue.. running
on java6 on windows 7 server..
$ java -version
java
You cygwin environment is missing uname(1), which could possibly trip up
ant. See if installing it makes a difference, cf. this stanza of the
ant script:
:
case `uname` in
CYGWIN*) cygwin=true ;;
Darwin*) darwin=true*
*:
its absence would make the cygwin=true setting fail...
Thanks,
Dag
Hi,
When trying to build source i am facing the following issue.. running on
java6 on windows 7 server..
$ java -version
java version 1.6.0_14
Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
Java HotSpot(TM) 64-Bit Server VM (build 14.0-b16, mixed mode)
$ ant -quiet buildsource
On 01/26/2014 08:53 PM, Madushanka Fonseka wrote:
Hi,
I have been working with Apache Derby for few months to innovate Derby
to support queries based on fuzzylogy. There I had to create an external
jar which I suppose to use in Derby. In the ant build file I gave the
correct references so
Hi,
I have been working with Apache Derby for few months to innovate Derby to
support queries based on fuzzylogy. There I had to create an external jar
which I suppose to use in Derby. In the ant build file I gave the correct
references so buildsource worked fine. When I run the buildjars it
HI All,
Yes there was a conflict for basetestcase file and i did MC(My conflict) as
an option... Is that what caused the issue ?
With Regards
Jayaram
On Fri, Aug 19, 2011 at 12:47 AM, Kathey Marsden
kmarsdende...@sbcglobal.net wrote:
On 8/18/2011 8:04 PM, Jayaram Subramanian wrote:
Hi
On 8/19/2011 4:37 AM, Jayaram Subramanian wrote:
HI All,
Yes there was a conflict for basetestcase file and i did MC(My
conflict) as an option... Is that what caused the issue ?
Probably that is the issue. There is some conflict for which your
changes took precedence and you lost the changes
Hi All,
When doing ant all, i suddenly ended up getting the following issue.. Any
clues?
compilet1:
[javac] Compiling 162 source files to C:\java\derby\source\trunk\classes
[javac]
C:\java\derby\source\trunk\java\testing\org\apache\derbyTesting\func
On 8/18/2011 8:04 PM, Jayaram Subramanian wrote:
Hi All,
When doing ant all, i suddenly ended up getting the following issue..
Any clues?
compilet1:
[javac] Compiling 162 source files to
C:\java\derby\source\trunk\classes
[javac]
Kathey Marsden kmarsdende...@sbcglobal.net writes:
I have seen this before after recent message changes. I am guessing
that perhaps the tool checks the values in the jars in your classpath
instead of the build tree, but haven't verified this, because usually
Yes, I think that's correct; have
Hi:
I am trying to build trunk with sun JDK 1.6, ANT 1.7.1 and junit 3.8.2.
I am getting error like:
c:\derby\10.5\build.xml:203: Don't know how to set java15compile.classpath, java
16compile.classpath using this environment:
java.vendor = Sun Microsystems Inc.
java.home =
Lily Wei lily...@yahoo.com writes:
Hi:
I am trying to build trunk with sun JDK 1.6, ANT 1.7.1 and junit 3.8.2.
I am getting error like:
c:\derby\10.5\build.xml:203: Don't know how to set java15compile.classpath,
java
16compile.classpath using this environment:
java.vendor =
Knut Anders Hatlen knut.hat...@sun.com writes:
Since Derby's build script is supposed to do the right thing with the
classpath if it only finds JDK 6, you may have more luck if you try
again with only this in ant.properties:
jdk16=c:/sun/sdk/jdk
j16lib=${jdk16}/jre/lib
But with your setup
jdk
directory to jdk1.6.0 should make it build.
Hope this helps,
--
Knut Anders
From: Knut Anders Hatlen knut.hat...@sun.com
To: derby-dev@db.apache.org
Sent: Monday, June 8, 2009 4:29:41 PM
Subject: Re: Help with build issue
Lily Wei wrote:
Thank you, Knut.
I was able to build all the source after changin my jdk to jdk1.6.0.
I am seeing the following error when I try to build my test:
runmessagecheck:
[runMessageBundleTest] WARNING: Message id XRE04.U.2 in
messages_en.properties i
s not referenced in either
I have seen this before after recent message changes. I am guessing
that perhaps the tool checks the values in the jars in your classpath
instead of the build tree, but haven't verified this, because usually
when I rebuild the issue goes away. Try the following from your source
root:
svn
I am seeing this build issue with XATestUtil.
Is it just me?
compile:
[javac] Compiling 31 source files to D:\p4\marsden_patch\classes
[javac]
D:\p4\marsden_patch\opensource\java\testing\org\apache\derbyTesting\functionTests\util\XATestUtil.java:29:
package javax.transaction.xa does
Kathey Marsden wrote:
I am seeing this build issue with XATestUtil.
Is it just me?
Probably my fault - I did check this on another clean client and it
worked for me, though I think there is a problem with the build. If the
class gets built through XATest it will be ok, but if it is modified
Daniel John Debrunner wrote:
Kathey Marsden wrote:
I am seeing this build issue with XATestUtil.
Is it just me?
Should be fixed now, sorry.
Dan.
20 matches
Mail list logo