Myrna van Lunteren m.v.lunte...@gmail.com writes:
Myrna, if you could add me to the hudson-jobadmin group as described in
the above URL, I could take a look at it.
Done - Thanks Knut Anders, for volunteering to take a look at this.
Thank you, Myrna.
I could log in and access the
That's great news. Thanks, Knut!
Kim
On 11/11/2012 11:26 AM, Knut Anders Hatlen wrote:
Myrna van Lunteren m.v.lunte...@gmail.com writes:
Myrna, if you could add me to the hudson-jobadmin group as described in
the above URL, I could take a look at it.
Done - Thanks Knut Anders, for
as advised by the console log, there is nothing there.
Our build expert, Kristian Waagan, is out on leave until January. Has
anyone else enough knowledge to figure out the build problems? I'm
afraid I do not.
Thanks very much,
Kim
the job is
triggered):
https://builds.apache.org/job/Derby-docs/ws/antoutput.log
Our build expert, Kristian Waagan, is out on leave until January. Has
anyone else enough knowledge to figure out the build problems? I'm
afraid I do not.
I think Kristian is the only one who can access these jobs
from the latest build can
be found on this URL (will be overwritten the next time the job is
triggered):
https://builds.apache.org/job/Derby-docs/ws/antoutput.log
Our build expert, Kristian Waagan, is out on leave until January. Has
anyone else enough knowledge to figure out the build problems
Dave Brosius dbros...@mebigfatguy.com writes:
I pulled derby from svn a week ago and was able to build fine.
Then i pulled a day ago, and get errors where there are duplicate
classes between base class and generated classes, as is documented by
someone else here:
On 02/10/2011 06:49 AM, Knut Anders Hatlen wrote:
Dave Brosiusdbros...@mebigfatguy.com writes:
I pulled derby from svn a week ago and was able to build fine.
Then i pulled a day ago, and get errors where there are duplicate
classes between base class and generated classes, as is documented
I pulled derby from svn a week ago and was able to build fine.
Then i pulled a day ago, and get errors where there are duplicate
classes between base class and generated classes, as is documented by
someone else here:
Martin Zaun [EMAIL PROTECTED] writes:
Hi,
running 'ant javadoc' in the trunk aborts with jdk-1.5-related errors.
I was wondering if they've been worked on already, since there was an
old email thread and we decided to require JDK 1.5.
Also, I'd like to use the [EMAIL PROTECTED] ...} tag for
Hi,
running 'ant javadoc' in the trunk aborts with jdk-1.5-related errors.
I was wondering if they've been worked on already, since there was an
old email thread and we decided to require JDK 1.5.
Also, I'd like to use the [EMAIL PROTECTED] ...} tag for easy quoting of
verbatim
text in
Bryan Pendleton wrote:
If changing the source level to 1.5 fixes it for you, I suggest that we
just cross our fingers and hope that no one vetos the JDK 5 vote (the
polls close at 5 pm PDT today) and check in the fix tomorrow. :)
This change appears to work for me. If no other opinions are
Bryan Pendleton [EMAIL PROTECTED] writes:
I'm having some troubles building the engine javadoc (errors are
pasted below). I think that perhaps there is some new code that
uses JDK 1.5 syntax, and the JavaDoc build doesn't recognize that
code syntax.
Hi Bryan,
It seems to be working fine in
1) Build the javadoc with JAVA_HOME set to a JDK 5 or later
This seems like a reasonable answer to me, since as you say we
are moving to JDK 1.5 as our base development environment.
But, this doesn't completely fix the problem for me. I get
many fewer errors, but I still get some (see
Bryan Pendleton [EMAIL PROTECTED] writes:
1) Build the javadoc with JAVA_HOME set to a JDK 5 or later
This seems like a reasonable answer to me, since as you say we
are moving to JDK 1.5 as our base development environment.
But, this doesn't completely fix the problem for me. I get
many
If changing the source level to 1.5 fixes it for you, I suggest that we
just cross our fingers and hope that no one vetos the JDK 5 vote (the
polls close at 5 pm PDT today) and check in the fix tomorrow. :)
This change appears to work for me. If no other opinions are voiced,
I'll make this
I'm having some troubles building the engine javadoc (errors are
pasted below). I think that perhaps there is some new code that
uses JDK 1.5 syntax, and the JavaDoc build doesn't recognize that
code syntax.
Does this indicate a problem in my build environment? Am I
supposed to be able to build
[
https://issues.apache.org/jira/browse/DERBY-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
V.Narayanan resolved DERBY-2622.
Resolution: Fixed
Fix Version/s: 10.3.0.0
The build problems pointed out related to locator
[
https://issues.apache.org/jira/browse/DERBY-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
V.Narayanan closed DERBY-2622.
--
Closing issue as the build problems have been fixed.
Fix build problems related to locator work
[
https://issues.apache.org/jira/browse/DERBY-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503089
]
V.Narayanan commented on DERBY-2622:
Thank you for looking at this. I will close this issue.
Fix build
[
https://issues.apache.org/jira/browse/DERBY-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502794
]
Myrna van Lunteren commented on DERBY-2622:
---
Looks like no more build problems occurred and the locator
Fix build problems related to locator work
--
Key: DERBY-2622
URL: https://issues.apache.org/jira/browse/DERBY-2622
Project: Derby
Issue Type: Sub-task
Reporter: V.Narayanan
[
https://issues.apache.org/jira/browse/DERBY-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
V.Narayanan reassigned DERBY-2622:
--
Assignee: V.Narayanan
Fix build problems related to locator work
/trunk/java/client/org/apache/derby/client/am/Clob.java
db/derby/code/trunk/java/client/org/apache/derby/client/net/NetCursor.java
Fix build problems related to locator work
--
Key: DERBY-2622
URL: https
' to trunk with revision 536146.
Not resolving this issue, since I don't know whether there will be more work
done or not.
Fix build problems related to locator work
--
Key: DERBY-2622
URL: https://issues.apache.org/jira
.
Fix build problems related to locator work
--
Key: DERBY-2622
URL: https://issues.apache.org/jira/browse/DERBY-2622
Project: Derby
Issue Type: Sub-task
Components: JDBC
Affects Versions
I'm seeing build errors trying to build the javadoc target,
publishedapi. I'm using ant 1.6.2. Any ideas?
BUILD FAILED
C:\_work\svn_linq\trunk\build.xml:597: The following error occurred
while executing this line:
C:\_work\svn_linq\trunk\build.xml:608: The following error occurred
while
On 10/27/06, Daniel John Debrunner [EMAIL PROTECTED] wrote:
I'm seeing build errors trying to build the javadoc target,
publishedapi. I'm using ant 1.6.2. Any ideas?
The executable attribute for the javadoc task was added in Ant 1.6.3.
We need to use the executable attribute to specify the
Hi,
I downloaded the source file derby-10.1.2.1-src. While trying to build
the file, I get the following:
compile_types:
[javac] Compiling 42 source files to C:\soc\db-derby-10.1.2.1-src\db-derby-1
0.1.2.1-src\classes
[javac]
On 7/2/06, Sanket Sharma [EMAIL PROTECTED] wrote:
Hi,
I downloaded the source file derby-10.1.2.1-src. While trying to build
the file, I get the following:
compile_types:
[javac] Compiling 42 source files to C:\soc\db-derby-10.1.2.1-src\db-derby-1
0.1.2.1-src\classes
[javac]
Andrew McIntyre wrote:
On Mar 30, 2005, at 4:40 PM, Jeff Levitt wrote:
The changes create propset values of native for the
dita files that had not been set at all.
Really? I was pretty sure that I got them all with revision 157620.
Perhaps I unknowingly undid this somehow with a later change?
Jean,
could you give a
uname -a
for the machine that did the fedora core 3 build?
thanks,
scott
Jean T. Anderson wrote:
all docs build successfully (html and pdf) on fedora core 3.
-jean
Jeff Levitt wrote:
I opened Jira issue 191:
http://issues.apache.org/jira/browse/DERBY-191
Jean has already
scott hutinger wrote:
Jean,
could you give a
uname -a
for the machine that did the fedora core 3 build?
[EMAIL PROTECTED] trunk]$ uname -a
Linux gertie3.swlogic.net 2.6.10-1.760_FC3 #1 Wed Feb 2 00:12:56 EST
2005 x86_64 x86_64 x86_64 GNU/Linux
This was my first attempt to build so I didn't do
Possibly 64bit has something to do with no failures. Working at a
university, I get the cheapest of everything :-)
At least that is one item to examine beside character encoding. Wow, 3
x86_64 (I thought I saw an echo!)
And yes, thanks for pointing out the src code download. I am pretty
scott hutinger wrote:
Jean,
could you give a
uname -a
for the machine that did the fedora core 3 build?
also it worked for me on Gentoo:
[EMAIL PROTECTED] trunk $ uname -a
Linux gertie-too 2.6.7-gentoo-r11 #3 Thu Aug 12 16:44:12 PDT 2004 i686
Intel(R) Pentium(R) 4 CPU 2.53GHz GenuineIntel
scott hutinger wrote:
Possibly 64bit has something to do with no failures. Working at a
university, I get the cheapest of everything :-)
Actually I just posted gentoo (32bit) successful results, too. :-)
Actually this was my holiday present to myself this year. I was getting
tired of forrest
--- Jean T. Anderson [EMAIL PROTECTED] wrote:
Now, back to topic. I'm only looking at that final
BUILD SUCCESSFUL
message. Somehow I suspect that BUILD SUCCESSFUL may
not mean built
correctly -- that would be a separate issue. I
haven't been checking
the docs themselves.
-jean
36 matches
Mail list logo
