can't build from svn

classic Classic list List threaded Threaded
19 messages Options
Reply | Threaded
Open this post in threaded view
|

can't build from svn

Ittay Dror
I checkedout gradle from svn and issued: 'gradle -s -d -Dskip.test=true userguide'. I get:

Build aborted anormally.  Run (additionally) with -f option to get the full (very verbose) stacktrace
Exception is:
org.gradle.api.GradleScriptException: : Warning: Could not find file /work/research/gradle/src/docs/userguide/master.pdf to copy. Buildscript=gradlefile in line(s): 250 240
        at org.gradle.api.internal.DefaultTask.execute(DefaultTask.groovy:101)
        at org.gradle.execution.Dag.execute(Dag.java:256)
        at org.gradle.execution.Dag.execute(Dag.java:247)
        at org.gradle.execution.BuildExecuter.execute(BuildExecuter.groovy:61)
        at org.gradle.Build$_runInternal_closure1.doCall(Build.groovy:78)
        at org.gradle.Build.runInternal(Build.groovy:69)
        at org.gradle.Build.this$2$runInternal(Build.groovy)
        at org.gradle.Build.run(Build.groovy:62)
        at org.gradle.Main.main(Main.groovy:198)
        at org.gradle.ToolsMain.main(ToolsMain.java:71)
Caused by: org.apache.tools.ant.BuildException: Warning: Could not find file /work/research/gradle/src/docs/userguide/master.pdf to copy.
        at org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:420)
        at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
        at org.apache.tools.ant.Task.perform(Task.java:348)
        at gradlefile$_run_closure11_closure50.doCall(gradlefile:262)
        at gradlefile$_run_closure11_closure50.doCall(gradlefile)
        at org.gradle.util.GradleUtil.configure(GradleUtil.groovy:34)
        at org.gradle.api.internal.project.DefaultProject.ant(DefaultProject.groovy:479)
        at org.gradle.api.internal.project.DefaultProject.invokeMethod(DefaultProject.groovy)
        at org.gradle.api.internal.project.BuildScriptProcessor$_replaceMetaclass_closure1.doCall(BuildScriptProcessor.groovy:67)
        at gradlefile$_run_closure11.doCall(gradlefile:252)
        at org.gradle.api.internal.DefaultTask.exe
Reply | Threaded
Open this post in threaded view
|

Re: can't build from svn

hans_d
Administrator
Hi Ittay,

On Jun 2, 2008, at 3:38 PM, Ittay Dror wrote:

>
> I checkedout gradle from svn and issued: 'gradle -s -d -
> Dskip.test=true
> userguide'. I get:

You can only build the userguide if LaTeX is installed. Is LaTeX  
installed on your machine? If not, you should get a nice message that  
this is not the case, not an exception. Otherwise the build has a bug.

You might simulate the LaTeX userguide generation by copying the  
html_single files to build/distributions/exploded/docs/html_single.  
This is where the userguide tasks put them. Then you could try to get  
them in the Wiki.

Those html_single files should be in GRADLE_HOME/docs/html_single.  
But there has been a bug in the build so that the current  
distributions do not contain the docs.

I gonna email you a zip with the html_single files. My local working  
copy isn't buildable right now. I try to send it to you as soon as  
possible.

- Hans


>
> Build aborted anormally.  Run (additionally) with -f option to get  
> the full
> (very verbose) stacktrace
> Exception is:
> org.gradle.api.GradleScriptException: : Warning: Could not find file
> /work/research/gradle/src/docs/userguide/master.pdf to copy.
> Buildscript=gradlefile in line(s): 250 240
> at org.gradle.api.internal.DefaultTask.execute(DefaultTask.groovy:
> 101)
> at org.gradle.execution.Dag.execute(Dag.java:256)
> at org.gradle.execution.Dag.execute(Dag.java:247)
> at org.gradle.execution.BuildExecuter.execute(BuildExecuter.groovy:
> 61)
> at org.gradle.Build$_runInternal_closure1.doCall(Build.groovy:78)
> at org.gradle.Build.runInternal(Build.groovy:69)
> at org.gradle.Build.this$2$runInternal(Build.groovy)
> at org.gradle.Build.run(Build.groovy:62)
> at org.gradle.Main.main(Main.groovy:198)
> at org.gradle.ToolsMain.main(ToolsMain.java:71)
> Caused by: org.apache.tools.ant.BuildException: Warning: Could not  
> find file
> /work/research/gradle/src/docs/userguide/master.pdf to copy.
> at org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:420)
> at
> org.apache.tools.ant.dispatch.DispatchUtils.execute
> (DispatchUtils.java:105)
> at org.apache.tools.ant.Task.perform(Task.java:348)
> at gradlefile$_run_closure11_closure50.doCall(gradlefile:262)
> at gradlefile$_run_closure11_closure50.doCall(gradlefile)
> at org.gradle.util.GradleUtil.configure(GradleUtil.groovy:34)
> at
> org.gradle.api.internal.project.DefaultProject.ant
> (DefaultProject.groovy:479)
> at
> org.gradle.api.internal.project.DefaultProject.invokeMethod
> (DefaultProject.groovy)
> at
> org.gradle.api.internal.project.BuildScriptProcessor
> $_replaceMetaclass_closure1.doCall(BuildScriptProcessor.groovy:67)
> at gradlefile$_run_closure11.doCall(gradlefile:252)
> at org.gradle.api.internal.DefaultTask.exe
> --
> View this message in context: http://www.nabble.com/can%27t-build- 
> from-svn-tp17601562p17601562.html
> Sent from the gradle-dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: can't build from svn

Ittay Dror

hdockter wrote
You can only build the userguide if LaTeX is installed. Is LaTeX  
installed on your machine? If not, you should get a nice message that  
this is not the case, not an exception. Otherwise the build has a bug.
latex is installed. when it was not, i indeed got an error message

ittay
Reply | Threaded
Open this post in threaded view
|

Re: can't build from svn

hans_d
Administrator
In reply to this post by Ittay Dror

On Jun 2, 2008, at 3:38 PM, Ittay Dror wrote:

>
> I checkedout gradle from svn and issued: 'gradle -s -d -
> Dskip.test=true
> userguide'. I get:
>
> Build aborted anormally.  Run (additionally) with -f option to get  
> the full
> (very verbose) stacktrace
> Exception is:
> org.gradle.api.GradleScriptException: : Warning: Could not find file
> /work/research/gradle/src/docs/userguide/master.pdf to copy.

It looks like the LaTeX generation was not successful. Therefore the  
master.pdf file does not exists and therefore an exception is thrown.

The output of the LaTeX pdf process can be found in: build/docs/
userguide/pdfOut

There are three LaTeX generations. pdf, html_single and html.

I was confused in my other email. For uploading to the wiki we don't  
want the content of html_single (a single file) but html (a file per  
chapter).

The html content is also uploaded to the website: http://gradle.org/ 
userguide/release/master.html

- Hans

> Buildscript=gradlefile in line(s): 250 240
> at org.gradle.api.internal.DefaultTask.execute(DefaultTask.groovy:
> 101)
> at org.gradle.execution.Dag.execute(Dag.java:256)
> at org.gradle.execution.Dag.execute(Dag.java:247)
> at org.gradle.execution.BuildExecuter.execute(BuildExecuter.groovy:
> 61)
> at org.gradle.Build$_runInternal_closure1.doCall(Build.groovy:78)
> at org.gradle.Build.runInternal(Build.groovy:69)
> at org.gradle.Build.this$2$runInternal(Build.groovy)
> at org.gradle.Build.run(Build.groovy:62)
> at org.gradle.Main.main(Main.groovy:198)
> at org.gradle.ToolsMain.main(ToolsMain.java:71)
> Caused by: org.apache.tools.ant.BuildException: Warning: Could not  
> find file
> /work/research/gradle/src/docs/userguide/master.pdf to copy.
> at org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:420)
> at
> org.apache.tools.ant.dispatch.DispatchUtils.execute
> (DispatchUtils.java:105)
> at org.apache.tools.ant.Task.perform(Task.java:348)
> at gradlefile$_run_closure11_closure50.doCall(gradlefile:262)
> at gradlefile$_run_closure11_closure50.doCall(gradlefile)
> at org.gradle.util.GradleUtil.configure(GradleUtil.groovy:34)
> at
> org.gradle.api.internal.project.DefaultProject.ant
> (DefaultProject.groovy:479)
> at
> org.gradle.api.internal.project.DefaultProject.invokeMethod
> (DefaultProject.groovy)
> at
> org.gradle.api.internal.project.BuildScriptProcessor
> $_replaceMetaclass_closure1.doCall(BuildScriptProcessor.groovy:67)
> at gradlefile$_run_closure11.doCall(gradlefile:252)
> at org.gradle.api.internal.DefaultTask.exe
> --
> View this message in context: http://www.nabble.com/can%27t-build- 
> from-svn-tp17601562p17601562.html
> Sent from the gradle-dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: can't build from svn

Ittay Dror

hdockter wrote
It looks like the LaTeX generation was not successful. Therefore the  
master.pdf file does not exists and therefore an exception is thrown.

The output of the LaTeX pdf process can be found in: build/docs/
userguide/pdfOut
it seems it can't find upquote.sty. in ubuntu, this is in a separate package called texlive-latex-extra.

the build should have failed then, right? not continue.

ittay
Reply | Threaded
Open this post in threaded view
|

Re: can't build from svn

hans_d
Administrator

On Jun 2, 2008, at 5:27 PM, Ittay Dror wrote:

>
>
>
> hdockter wrote:
>>
>> It looks like the LaTeX generation was not successful. Therefore the
>> master.pdf file does not exists and therefore an exception is thrown.
>>
>> The output of the LaTeX pdf process can be found in: build/docs/
>> userguide/pdfOut
>>
> it seems it can't find upquote.sty. in ubuntu, this is in a  
> separate package
> called texlive-latex-extra.
>
> the build should have failed then, right? not continue.

right

>
> ittay
>
> --
> View this message in context: http://www.nabble.com/can%27t-build- 
> from-svn-tp17601562p17603995.html
> Sent from the gradle-dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: can't build from svn

Ittay Dror
It still fails, but now I don't know enough about latex (meaning, i harly know it) to understand what is wrong:
This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)
 %&-line parsing enabled.
entering extended mode
(./master.tex
LaTeX2e <2005/12/01>
Babel <v3.8h> and hyphenation patterns for english, usenglishmax, dumylang, noh
yphenation, loaded.
(/usr/share/texmf-texlive/tex/latex/base/book.cls
Document Class: book 2005/09/16 v1.4f Standard LaTeX document class
(/usr/share/texmf-texlive/tex/latex/base/bk10.clo))
(/usr/share/texmf-texlive/tex/latex/upquote/upquote.sty
(/usr/share/texmf-texlive/tex/latex/base/textcomp.sty
(/usr/share/texmf-texlive/tex/latex/base/ts1enc.def)))
(/usr/share/texmf-texlive/tex/latex/tools/tabularx.sty
(/usr/share/texmf-texlive/tex/latex/tools/array.sty))
(/usr/share/texmf-texlive/tex/latex/fancyvrb/fancyvrb.sty
Style option: `fancyvrb' v2.6, with DG/SPQR fixes <1998/07/17> (tvz)
(/usr/share/texmf-texlive/tex/latex/graphics/keyval.sty)
No file fancyvrb.cfg.
) (/usr/share/texmf-texlive/tex/latex/ccaption/ccaption.sty)
(/usr/share/texmf-texlive/tex/latex/graphics/color.sty
(/etc/texmf/tex/latex/config/color.cfg)
(/usr/share/texmf-texlive/tex/latex/pdftex-def/pdftex.def))
(/usr/share/texmf-texlive/tex/latex/hyperref/hyperref.sty
(/usr/share/texmf-texlive/tex/latex/hyperref/pd1enc.def)
(/etc/texmf/tex/latex/config/hyperref.cfg)
(/usr/share/texmf-texlive/tex/latex/oberdiek/kvoptions.sty)
Implicit mode ON; LaTeX internals redefined
(/usr/share/texmf-texlive/tex/latex/ltxmisc/url.sty))
*hyperref using default driver hpdftex*
(/usr/share/texmf-texlive/tex/latex/hyperref/hpdftex.def) (./master.aux
(./introduction.aux) (./buildScripts.aux) (./javaTutorial.aux)
(./thisAndThat.aux) (./overview.aux) (./projectTaskApi.aux) (./tasks.aux)
(./plugins.aux

LaTeX Warning: Label `sec:summary' multiply defined.

) (./javaPlugin.aux) (./groovyPlugin.aux

LaTeX Warning: Label `sec:compile' multiply defined.

) (./depMngmt.aux)) (/usr/share/texmf-texlive/tex/latex/base/ts1cmr.fd)
(/usr/share/texmf-texlive/tex/latex/hyperref/nameref.sty
(/usr/share/texmf-texlive/tex/latex/oberdiek/refcount.sty)) (./master.out)
(./master.out) (../../../build/docs/userguide/data/version.tex) [1{/var/lib/tex
mf/fonts/map/pdftex/updmap/pdftex.map}] (./master.toc) [1] (./introduction.tex
Chapter 1.
)pdfTeX warning (ext4): destination with the same identifier (name{page.1}) has
 been already used, duplicate ignored
<to be read again> 
                   \relax
l.71 \include{introduction}
                            [1]
No file buildScripts.tex.
(./javaTutorial.tex
Chapter 2.
(/usr/share/texmf-texlive/tex/latex/base/ts1cmtt.fd) [2]) [3]
(./thisAndThat.tex
Chapter 3.

Overfull \hbox (7.11407pt too wide) in paragraph at lines 16--18
\OT1/cmr/m/n/10 If the rules for skip-ping a task can't be ex-pressed with a si
m-ple prop-erty, you can use the \OT1/cmtt/m/n/10 StopExecutionException[]\OT1/
cmr/m/n/10 .
[4]

LaTeX Warning: Reference `ide_support' on page 5 undefined on input line 22.


LaTeX Warning: Reference `cha:command_line' on page 5 undefined on input line 2
5.


Underfull \hbox (badness 10000) in paragraph at lines 25--27


Overfull \hbox (40.31412pt too wide) in paragraph at lines 42--48
[][]
[5]
Overfull \hbox (12.98004pt too wide) in paragraph at lines 65--66
[]\OT1/cmr/m/n/10 There is also the pos-si-bil-ity to di-rectly add prop-er-tie
s to your project ob-jects. You can place a \OT1/cmtt/m/n/10 gradle.properties
) [6] (./overview.tex
Chapter 4.
[7]) [8] (./projectTaskApi.tex
Chapter 5.

LaTeX Warning: Reference `cha:gradle_core_tutorial' on page 9 undefined on inpu
t line 7.


LaTeX Warning: Reference `cha:gradle_core_tutorial' on page 9 undefined on inpu
t line 19.


LaTeX Warning: Reference `cha:multi_project_builds' on page 9 undefined on inpu
t line 23.

) [9] (./tasks.tex
Chapter 6.

LaTeX Warning: Reference `cha:gradle_core_tutorial' on page 10 undefined on inp
ut line 4.

[10]) [11] (./plugins.tex
Chapter 7.

LaTeX Warning: Reference `cha:ide_support' on page 12 undefined on input line 2
3.


LaTeX Warning: Reference `cha:organizing_build_logic' on page 12 undefined on i
nput line 29.

[12]) [13] (./javaPlugin.tex
Chapter 8.
[14] [15]
Overfull \hbox (25.89717pt too wide) in paragraph at lines 129--131
\OT1/cmr/m/n/10 The \OT1/cmtt/m/n/10 resources \OT1/cmr/m/n/10 task of-fers in-
cludes and ex-cludes di-rec-tives as well as fil-ters. Have a look at [][]org.g
radle.api.tasks.Resources[][]

LaTeX Warning: Reference `' on page 16 undefined on input line 150.

[16] [17]
Overfull \hbox (73.75406pt too wide) in paragraph at lines 253--254
\OT1/cmr/m/n/10 The con-ven-tion ob-ject of the JavaPlu-gin has a \OT1/cmtt/m/n
/10 manifest \OT1/cmr/m/n/10 prop-erty point-ing to an in-stance of [][]org.gra
dle.api.bundling.GradleManifest[][].
) [18] (./groovyPlugin.tex
Chapter 9.
[19]) [20] (./depMngmt.tex
Chapter 10.
[21] [22]

LaTeX Warning: Reference `cha:multi_project_builds' on page 23 undefined on inp
ut line 110.

[23] [24] [25]

LaTeX Warning: Reference `sub:resolver_container' on page 26 undefined on input
 line 219.

)
Runaway argument?
{To make things more flexible (or complicated). By default the build \ETC.
! File ended while scanning use of \@footnotetext.
<inserted text> 
                \par
l.81 \include{depMngmt}
                       
?
! Emergency stop.
<inserted text> 
                \par
l.81 \include{depMngmt}
                       
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on master.log.

hdockter wrote
On Jun 2, 2008, at 5:27 PM, Ittay Dror wrote:

>
>
>
> hdockter wrote:
>>
>> It looks like the LaTeX generation was not successful. Therefore the
>> master.pdf file does not exists and therefore an exception is thrown.
>>
>> The output of the LaTeX pdf process can be found in: build/docs/
>> userguide/pdfOut
>>
> it seems it can't find upquote.sty. in ubuntu, this is in a  
> separate package
> called texlive-latex-extra.
>
> the build should have failed then, right? not continue.

right

>
> ittay
>
> --
> View this message in context: http://www.nabble.com/can%27t-build- 
> from-svn-tp17601562p17603995.html
> Sent from the gradle-dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|

Re: can't build from svn

hans_d
Administrator
Sorry for all your trouble. It looks like I have yesterday submitted  
a LaTeX file with a bug. Our continuous integration servers don't  
have LaTeX installed, therefore such bugs are not recognized by our  
CI builds.

I try to fix this as soon as possible. Hopefully I can manage to do  
it this evening.

- Hans

On Jun 2, 2008, at 5:50 PM, Ittay Dror wrote:

>
> It still fails, but now I don't know enough about latex (meaning, i  
> harly
> know it) to understand what is wrong:
> This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)
>  %&-line parsing enabled.
> entering extended mode
> (./master.tex
> LaTeX2e <2005/12/01>
> Babel <v3.8h> and hyphenation patterns for english, usenglishmax,  
> dumylang,
> noh
> yphenation, loaded.
> (/usr/share/texmf-texlive/tex/latex/base/book.cls
> Document Class: book 2005/09/16 v1.4f Standard LaTeX document class
> (/usr/share/texmf-texlive/tex/latex/base/bk10.clo))
> (/usr/share/texmf-texlive/tex/latex/upquote/upquote.sty
> (/usr/share/texmf-texlive/tex/latex/base/textcomp.sty
> (/usr/share/texmf-texlive/tex/latex/base/ts1enc.def)))
> (/usr/share/texmf-texlive/tex/latex/tools/tabularx.sty
> (/usr/share/texmf-texlive/tex/latex/tools/array.sty))
> (/usr/share/texmf-texlive/tex/latex/fancyvrb/fancyvrb.sty
> Style option: `fancyvrb' v2.6, with DG/SPQR fixes <1998/07/17> (tvz)
> (/usr/share/texmf-texlive/tex/latex/graphics/keyval.sty)
> No file fancyvrb.cfg.
> ) (/usr/share/texmf-texlive/tex/latex/ccaption/ccaption.sty)
> (/usr/share/texmf-texlive/tex/latex/graphics/color.sty
> (/etc/texmf/tex/latex/config/color.cfg)
> (/usr/share/texmf-texlive/tex/latex/pdftex-def/pdftex.def))
> (/usr/share/texmf-texlive/tex/latex/hyperref/hyperref.sty
> (/usr/share/texmf-texlive/tex/latex/hyperref/pd1enc.def)
> (/etc/texmf/tex/latex/config/hyperref.cfg)
> (/usr/share/texmf-texlive/tex/latex/oberdiek/kvoptions.sty)
> Implicit mode ON; LaTeX internals redefined
> (/usr/share/texmf-texlive/tex/latex/ltxmisc/url.sty))
> *hyperref using default driver hpdftex*
> (/usr/share/texmf-texlive/tex/latex/hyperref/hpdftex.def) (./
> master.aux
> (./introduction.aux) (./buildScripts.aux) (./javaTutorial.aux)
> (./thisAndThat.aux) (./overview.aux) (./projectTaskApi.aux) (./
> tasks.aux)
> (./plugins.aux
>
> LaTeX Warning: Label `sec:summary' multiply defined.
>
> ) (./javaPlugin.aux) (./groovyPlugin.aux
>
> LaTeX Warning: Label `sec:compile' multiply defined.
>
> ) (./depMngmt.aux)) (/usr/share/texmf-texlive/tex/latex/base/
> ts1cmr.fd)
> (/usr/share/texmf-texlive/tex/latex/hyperref/nameref.sty
> (/usr/share/texmf-texlive/tex/latex/oberdiek/refcount.sty)) (./
> master.out)
> (./master.out) (../../../build/docs/userguide/data/version.tex)
> [1{/var/lib/tex
> mf/fonts/map/pdftex/updmap/pdftex.map}] (./master.toc) [1]
> (./introduction.tex
> Chapter 1.
> )pdfTeX warning (ext4): destination with the same identifier (name
> {page.1})
> has
>  been already used, duplicate ignored
> <to be read again>
>                    \relax
> l.71 \include{introduction}
>                             [1]
> No file buildScripts.tex.
> (./javaTutorial.tex
> Chapter 2.
> (/usr/share/texmf-texlive/tex/latex/base/ts1cmtt.fd) [2]) [3]
> (./thisAndThat.tex
> Chapter 3.
>
> Overfull \hbox (7.11407pt too wide) in paragraph at lines 16--18
> \OT1/cmr/m/n/10 If the rules for skip-ping a task can't be ex-
> pressed with a
> si
> m-ple prop-erty, you can use the \OT1/cmtt/m/n/10
> StopExecutionException[]\OT1/
> cmr/m/n/10 .
> [4]
>
> LaTeX Warning: Reference `ide_support' on page 5 undefined on input  
> line 22.
>
>
> LaTeX Warning: Reference `cha:command_line' on page 5 undefined on  
> input
> line 2
> 5.
>
>
> Underfull \hbox (badness 10000) in paragraph at lines 25--27
>
>
> Overfull \hbox (40.31412pt too wide) in paragraph at lines 42--48
> [][]
> [5]
> Overfull \hbox (12.98004pt too wide) in paragraph at lines 65--66
> []\OT1/cmr/m/n/10 There is also the pos-si-bil-ity to di-rectly add
> prop-er-tie
> s to your project ob-jects. You can place a \OT1/cmtt/m/n/10
> gradle.properties
> ) [6] (./overview.tex
> Chapter 4.
> [7]) [8] (./projectTaskApi.tex
> Chapter 5.
>
> LaTeX Warning: Reference `cha:gradle_core_tutorial' on page 9  
> undefined on
> inpu
> t line 7.
>
>
> LaTeX Warning: Reference `cha:gradle_core_tutorial' on page 9  
> undefined on
> inpu
> t line 19.
>
>
> LaTeX Warning: Reference `cha:multi_project_builds' on page 9  
> undefined on
> inpu
> t line 23.
>
> ) [9] (./tasks.tex
> Chapter 6.
>
> LaTeX Warning: Reference `cha:gradle_core_tutorial' on page 10  
> undefined on
> inp
> ut line 4.
>
> [10]) [11] (./plugins.tex
> Chapter 7.
>
> LaTeX Warning: Reference `cha:ide_support' on page 12 undefined on  
> input
> line 2
> 3.
>
>
> LaTeX Warning: Reference `cha:organizing_build_logic' on page 12  
> undefined
> on i
> nput line 29.
>
> [12]) [13] (./javaPlugin.tex
> Chapter 8.
> [14] [15]
> Overfull \hbox (25.89717pt too wide) in paragraph at lines 129--131
> \OT1/cmr/m/n/10 The \OT1/cmtt/m/n/10 resources \OT1/cmr/m/n/10 task  
> of-fers
> in-
> cludes and ex-cludes di-rec-tives as well as fil-ters. Have a look at
> [][]org.g
> radle.api.tasks.Resources[][]
>
> LaTeX Warning: Reference `' on page 16 undefined on input line 150.
>
> [16] [17]
> Overfull \hbox (73.75406pt too wide) in paragraph at lines 253--254
> \OT1/cmr/m/n/10 The con-ven-tion ob-ject of the JavaPlu-gin has a
> \OT1/cmtt/m/n
> /10 manifest \OT1/cmr/m/n/10 prop-erty point-ing to an in-stance of
> [][]org.gra
> dle.api.bundling.GradleManifest[][].
> ) [18] (./groovyPlugin.tex
> Chapter 9.
> [19]) [20] (./depMngmt.tex
> Chapter 10.
> [21] [22]
>
> LaTeX Warning: Reference `cha:multi_project_builds' on page 23  
> undefined on
> inp
> ut line 110.
>
> [23] [24] [25]
>
> LaTeX Warning: Reference `sub:resolver_container' on page 26  
> undefined on
> input
>  line 219.
>
> )
> Runaway argument?
> {To make things more flexible (or complicated). By default the  
> build \ETC.
> ! File ended while scanning use of \@footnotetext.
> <inserted text>
>                 \par
> l.81 \include{depMngmt}
>
> ?
> ! Emergency stop.
> <inserted text>
>                 \par
> l.81 \include{depMngmt}
>
> !  ==> Fatal error occurred, no output PDF file produced!
> Transcript written on master.log.
>
>
> hdockter wrote:
>>
>>
>> On Jun 2, 2008, at 5:27 PM, Ittay Dror wrote:
>>
>>>
>>>
>>>
>>> hdockter wrote:
>>>>
>>>> It looks like the LaTeX generation was not successful. Therefore  
>>>> the
>>>> master.pdf file does not exists and therefore an exception is  
>>>> thrown.
>>>>
>>>> The output of the LaTeX pdf process can be found in: build/docs/
>>>> userguide/pdfOut
>>>>
>>> it seems it can't find upquote.sty. in ubuntu, this is in a
>>> separate package
>>> called texlive-latex-extra.
>>>
>>> the build should have failed then, right? not continue.
>>
>> right
>>
>>>
>>> ittay
>>>
>>> --
>>> View this message in context: http://www.nabble.com/can%27t-build-
>>> from-svn-tp17601562p17603995.html
>>> Sent from the gradle-dev mailing list archive at Nabble.com.
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe from this list, please visit:
>>>
>>>     http://xircles.codehaus.org/manage_email
>>>
>>>
>>
>> --
>> Hans Dockter
>> Gradle Project lead
>> http://www.gradle.org
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/can%27t-build- 
> from-svn-tp17601562p17604520.html
> Sent from the gradle-dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: can't build from svn

hans_d
Administrator
Hi Ittay,

On Jun 2, 2008, at 6:00 PM, Hans Dockter wrote:

> Sorry for all your trouble. It looks like I have yesterday  
> submitted a LaTeX file with a bug. Our continuous integration  
> servers don't have LaTeX installed, therefore such bugs are not  
> recognized by our CI builds.
>
> I try to fix this as soon as possible. Hopefully I can manage to do  
> it this evening.

I think it was a trivial bug which I have hopefully fixed just now. I  
can't try it out myself as my working copy is not buildable right  
now. Please do a svn update and try again.

- Hans

>
> - Hans
>
> On Jun 2, 2008, at 5:50 PM, Ittay Dror wrote:
>
>>
>> It still fails, but now I don't know enough about latex (meaning,  
>> i harly
>> know it) to understand what is wrong:
>> This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)
>>  %&-line parsing enabled.
>> entering extended mode
>> (./master.tex
>> LaTeX2e <2005/12/01>
>> Babel <v3.8h> and hyphenation patterns for english, usenglishmax,  
>> dumylang,
>> noh
>> yphenation, loaded.
>> (/usr/share/texmf-texlive/tex/latex/base/book.cls
>> Document Class: book 2005/09/16 v1.4f Standard LaTeX document class
>> (/usr/share/texmf-texlive/tex/latex/base/bk10.clo))
>> (/usr/share/texmf-texlive/tex/latex/upquote/upquote.sty
>> (/usr/share/texmf-texlive/tex/latex/base/textcomp.sty
>> (/usr/share/texmf-texlive/tex/latex/base/ts1enc.def)))
>> (/usr/share/texmf-texlive/tex/latex/tools/tabularx.sty
>> (/usr/share/texmf-texlive/tex/latex/tools/array.sty))
>> (/usr/share/texmf-texlive/tex/latex/fancyvrb/fancyvrb.sty
>> Style option: `fancyvrb' v2.6, with DG/SPQR fixes <1998/07/17> (tvz)
>> (/usr/share/texmf-texlive/tex/latex/graphics/keyval.sty)
>> No file fancyvrb.cfg.
>> ) (/usr/share/texmf-texlive/tex/latex/ccaption/ccaption.sty)
>> (/usr/share/texmf-texlive/tex/latex/graphics/color.sty
>> (/etc/texmf/tex/latex/config/color.cfg)
>> (/usr/share/texmf-texlive/tex/latex/pdftex-def/pdftex.def))
>> (/usr/share/texmf-texlive/tex/latex/hyperref/hyperref.sty
>> (/usr/share/texmf-texlive/tex/latex/hyperref/pd1enc.def)
>> (/etc/texmf/tex/latex/config/hyperref.cfg)
>> (/usr/share/texmf-texlive/tex/latex/oberdiek/kvoptions.sty)
>> Implicit mode ON; LaTeX internals redefined
>> (/usr/share/texmf-texlive/tex/latex/ltxmisc/url.sty))
>> *hyperref using default driver hpdftex*
>> (/usr/share/texmf-texlive/tex/latex/hyperref/hpdftex.def) (./
>> master.aux
>> (./introduction.aux) (./buildScripts.aux) (./javaTutorial.aux)
>> (./thisAndThat.aux) (./overview.aux) (./projectTaskApi.aux) (./
>> tasks.aux)
>> (./plugins.aux
>>
>> LaTeX Warning: Label `sec:summary' multiply defined.
>>
>> ) (./javaPlugin.aux) (./groovyPlugin.aux
>>
>> LaTeX Warning: Label `sec:compile' multiply defined.
>>
>> ) (./depMngmt.aux)) (/usr/share/texmf-texlive/tex/latex/base/
>> ts1cmr.fd)
>> (/usr/share/texmf-texlive/tex/latex/hyperref/nameref.sty
>> (/usr/share/texmf-texlive/tex/latex/oberdiek/refcount.sty)) (./
>> master.out)
>> (./master.out) (../../../build/docs/userguide/data/version.tex)
>> [1{/var/lib/tex
>> mf/fonts/map/pdftex/updmap/pdftex.map}] (./master.toc) [1]
>> (./introduction.tex
>> Chapter 1.
>> )pdfTeX warning (ext4): destination with the same identifier (name
>> {page.1})
>> has
>>  been already used, duplicate ignored
>> <to be read again>
>>                    \relax
>> l.71 \include{introduction}
>>                             [1]
>> No file buildScripts.tex.
>> (./javaTutorial.tex
>> Chapter 2.
>> (/usr/share/texmf-texlive/tex/latex/base/ts1cmtt.fd) [2]) [3]
>> (./thisAndThat.tex
>> Chapter 3.
>>
>> Overfull \hbox (7.11407pt too wide) in paragraph at lines 16--18
>> \OT1/cmr/m/n/10 If the rules for skip-ping a task can't be ex-
>> pressed with a
>> si
>> m-ple prop-erty, you can use the \OT1/cmtt/m/n/10
>> StopExecutionException[]\OT1/
>> cmr/m/n/10 .
>> [4]
>>
>> LaTeX Warning: Reference `ide_support' on page 5 undefined on  
>> input line 22.
>>
>>
>> LaTeX Warning: Reference `cha:command_line' on page 5 undefined on  
>> input
>> line 2
>> 5.
>>
>>
>> Underfull \hbox (badness 10000) in paragraph at lines 25--27
>>
>>
>> Overfull \hbox (40.31412pt too wide) in paragraph at lines 42--48
>> [][]
>> [5]
>> Overfull \hbox (12.98004pt too wide) in paragraph at lines 65--66
>> []\OT1/cmr/m/n/10 There is also the pos-si-bil-ity to di-rectly add
>> prop-er-tie
>> s to your project ob-jects. You can place a \OT1/cmtt/m/n/10
>> gradle.properties
>> ) [6] (./overview.tex
>> Chapter 4.
>> [7]) [8] (./projectTaskApi.tex
>> Chapter 5.
>>
>> LaTeX Warning: Reference `cha:gradle_core_tutorial' on page 9  
>> undefined on
>> inpu
>> t line 7.
>>
>>
>> LaTeX Warning: Reference `cha:gradle_core_tutorial' on page 9  
>> undefined on
>> inpu
>> t line 19.
>>
>>
>> LaTeX Warning: Reference `cha:multi_project_builds' on page 9  
>> undefined on
>> inpu
>> t line 23.
>>
>> ) [9] (./tasks.tex
>> Chapter 6.
>>
>> LaTeX Warning: Reference `cha:gradle_core_tutorial' on page 10  
>> undefined on
>> inp
>> ut line 4.
>>
>> [10]) [11] (./plugins.tex
>> Chapter 7.
>>
>> LaTeX Warning: Reference `cha:ide_support' on page 12 undefined on  
>> input
>> line 2
>> 3.
>>
>>
>> LaTeX Warning: Reference `cha:organizing_build_logic' on page 12  
>> undefined
>> on i
>> nput line 29.
>>
>> [12]) [13] (./javaPlugin.tex
>> Chapter 8.
>> [14] [15]
>> Overfull \hbox (25.89717pt too wide) in paragraph at lines 129--131
>> \OT1/cmr/m/n/10 The \OT1/cmtt/m/n/10 resources \OT1/cmr/m/n/10  
>> task of-fers
>> in-
>> cludes and ex-cludes di-rec-tives as well as fil-ters. Have a look at
>> [][]org.g
>> radle.api.tasks.Resources[][]
>>
>> LaTeX Warning: Reference `' on page 16 undefined on input line 150.
>>
>> [16] [17]
>> Overfull \hbox (73.75406pt too wide) in paragraph at lines 253--254
>> \OT1/cmr/m/n/10 The con-ven-tion ob-ject of the JavaPlu-gin has a
>> \OT1/cmtt/m/n
>> /10 manifest \OT1/cmr/m/n/10 prop-erty point-ing to an in-stance of
>> [][]org.gra
>> dle.api.bundling.GradleManifest[][].
>> ) [18] (./groovyPlugin.tex
>> Chapter 9.
>> [19]) [20] (./depMngmt.tex
>> Chapter 10.
>> [21] [22]
>>
>> LaTeX Warning: Reference `cha:multi_project_builds' on page 23  
>> undefined on
>> inp
>> ut line 110.
>>
>> [23] [24] [25]
>>
>> LaTeX Warning: Reference `sub:resolver_container' on page 26  
>> undefined on
>> input
>>  line 219.
>>
>> )
>> Runaway argument?
>> {To make things more flexible (or complicated). By default the  
>> build \ETC.
>> ! File ended while scanning use of \@footnotetext.
>> <inserted text>
>>                 \par
>> l.81 \include{depMngmt}
>>
>> ?
>> ! Emergency stop.
>> <inserted text>
>>                 \par
>> l.81 \include{depMngmt}
>>
>> !  ==> Fatal error occurred, no output PDF file produced!
>> Transcript written on master.log.
>>
>>
>> hdockter wrote:
>>>
>>>
>>> On Jun 2, 2008, at 5:27 PM, Ittay Dror wrote:
>>>
>>>>
>>>>
>>>>
>>>> hdockter wrote:
>>>>>
>>>>> It looks like the LaTeX generation was not successful.  
>>>>> Therefore the
>>>>> master.pdf file does not exists and therefore an exception is  
>>>>> thrown.
>>>>>
>>>>> The output of the LaTeX pdf process can be found in: build/docs/
>>>>> userguide/pdfOut
>>>>>
>>>> it seems it can't find upquote.sty. in ubuntu, this is in a
>>>> separate package
>>>> called texlive-latex-extra.
>>>>
>>>> the build should have failed then, right? not continue.
>>>
>>> right
>>>
>>>>
>>>> ittay
>>>>
>>>> --
>>>> View this message in context: http://www.nabble.com/can%27t-build-
>>>> from-svn-tp17601562p17603995.html
>>>> Sent from the gradle-dev mailing list archive at Nabble.com.
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe from this list, please visit:
>>>>
>>>>     http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>
>>> --
>>> Hans Dockter
>>> Gradle Project lead
>>> http://www.gradle.org
>>>
>>>
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe from this list, please visit:
>>>
>>>     http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>>
>>
>> --
>> View this message in context: http://www.nabble.com/can%27t-build- 
>> from-svn-tp17601562p17604520.html
>> Sent from the gradle-dev mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
>
> --
> Hans Dockter
> Gradle Project lead
> http://www.gradle.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: can't build from svn

Russel Winder-2
Hans,

On Mon, 2008-06-02 at 18:04 +0200, Hans Dockter wrote:

> I think it was a trivial bug which I have hopefully fixed just now. I  
> can't try it out myself as my working copy is not buildable right  
> now. Please do a svn update and try again.

I strongly recommend using Bazaar.  In a shared repository you create a
mirror of the Subversion repository, then in the same shared repository
you branch the mirror for you working branch.  Then you have a local
mirror which is always buildable.  You can even make corrections such as
this one and then pull the changes into you working branch so as to keep
it up to date.  Then use rebase to realign the working branch to the
mirror.

I have three different experiments going on with Gant but always I have
a way of building Gant.

The trick here is not to use Subversion as your client :-)

--
Russel.
====================================================
Dr Russel Winder                 Partner

Concertant LLP                   t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road,              f: +44 8700 516 084
London SW11 1EN, UK.             m: +44 7770 465 077

signature.asc (196 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: can't build from svn

hans_d
Administrator
Hi Russel,

On Jun 2, 2008, at 6:30 PM, Russel Winder wrote:

> Hans,
>
> On Mon, 2008-06-02 at 18:04 +0200, Hans Dockter wrote:
>
>> I think it was a trivial bug which I have hopefully fixed just now. I
>> can't try it out myself as my working copy is not buildable right
>> now. Please do a svn update and try again.
>
> I strongly recommend using Bazaar.  In a shared repository you  
> create a
> mirror of the Subversion repository, then in the same shared  
> repository
> you branch the mirror for you working branch.  Then you have a local
> mirror which is always buildable.  You can even make corrections  
> such as
> this one and then pull the changes into you working branch so as to  
> keep
> it up to date.  Then use rebase to realign the working branch to the
> mirror.
>
> I have three different experiments going on with Gant but always I  
> have
> a way of building Gant.
>
> The trick here is not to use Subversion as your client :-)

I've heard that subversion 1.5 is supposed to be better in this  
respect compared to 1.4. Have you had a look at it?

- Hans

>
> --
> Russel.
> ====================================================
> Dr Russel Winder                 Partner
>
> Concertant LLP                   t: +44 20 7585 2200, +44 20 7193 9203
> 41 Buckmaster Road,              f: +44 8700 516 084
> London SW11 1EN, UK.             m: +44 7770 465 077

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: can't build from svn

Russel Winder-2
Hans,

On Mon, 2008-06-02 at 18:54 +0200, Hans Dockter wrote:

> I've heard that subversion 1.5 is supposed to be better in this  
> respect compared to 1.4. Have you had a look at it?

I guess the question is will 1.5 ever be released?

It is true that it is supposed to have merge tracking and things, but it
is still a centralized system with all that goes with it -- including
complete inability to do anything useful if you are not connected to the
Internet.

Basically distributed version control is the future and centralized is
the past -- even the Subversion people admit this.  For some proprietary
developments centralized may still be a way forward but for FOSS,
centralized is anathema!
 
--
Russel.
====================================================
Dr Russel Winder                 Partner

Concertant LLP                   t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road,              f: +44 8700 516 084
London SW11 1EN, UK.             m: +44 7770 465 077

signature.asc (196 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: can't build from svn

hans_d
Administrator
In reply to this post by hans_d

On Jun 2, 2008, at 6:04 PM, Hans Dockter wrote:

> Hi Ittay,
>
> On Jun 2, 2008, at 6:00 PM, Hans Dockter wrote:
>
>> Sorry for all your trouble. It looks like I have yesterday  
>> submitted a LaTeX file with a bug. Our continuous integration  
>> servers don't have LaTeX installed, therefore such bugs are not  
>> recognized by our CI builds.
>>
>> I try to fix this as soon as possible. Hopefully I can manage to  
>> do it this evening.
>
> I think it was a trivial bug which I have hopefully fixed just now.  
> I can't try it out myself as my working copy is not buildable right  
> now. Please do a svn update and try again.

Damn. I've submitted the fix only to the 0.1 branch. Now I have also  
submitted it to head. I can build the userguide from head now.

- Hans

>
> - Hans
>
>>
>> - Hans
>>
>> On Jun 2, 2008, at 5:50 PM, Ittay Dror wrote:
>>
>>>
>>> It still fails, but now I don't know enough about latex (meaning,  
>>> i harly
>>> know it) to understand what is wrong:
>>> This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)
>>>  %&-line parsing enabled.
>>> entering extended mode
>>> (./master.tex
>>> LaTeX2e <2005/12/01>
>>> Babel <v3.8h> and hyphenation patterns for english, usenglishmax,  
>>> dumylang,
>>> noh
>>> yphenation, loaded.
>>> (/usr/share/texmf-texlive/tex/latex/base/book.cls
>>> Document Class: book 2005/09/16 v1.4f Standard LaTeX document class
>>> (/usr/share/texmf-texlive/tex/latex/base/bk10.clo))
>>> (/usr/share/texmf-texlive/tex/latex/upquote/upquote.sty
>>> (/usr/share/texmf-texlive/tex/latex/base/textcomp.sty
>>> (/usr/share/texmf-texlive/tex/latex/base/ts1enc.def)))
>>> (/usr/share/texmf-texlive/tex/latex/tools/tabularx.sty
>>> (/usr/share/texmf-texlive/tex/latex/tools/array.sty))
>>> (/usr/share/texmf-texlive/tex/latex/fancyvrb/fancyvrb.sty
>>> Style option: `fancyvrb' v2.6, with DG/SPQR fixes <1998/07/17> (tvz)
>>> (/usr/share/texmf-texlive/tex/latex/graphics/keyval.sty)
>>> No file fancyvrb.cfg.
>>> ) (/usr/share/texmf-texlive/tex/latex/ccaption/ccaption.sty)
>>> (/usr/share/texmf-texlive/tex/latex/graphics/color.sty
>>> (/etc/texmf/tex/latex/config/color.cfg)
>>> (/usr/share/texmf-texlive/tex/latex/pdftex-def/pdftex.def))
>>> (/usr/share/texmf-texlive/tex/latex/hyperref/hyperref.sty
>>> (/usr/share/texmf-texlive/tex/latex/hyperref/pd1enc.def)
>>> (/etc/texmf/tex/latex/config/hyperref.cfg)
>>> (/usr/share/texmf-texlive/tex/latex/oberdiek/kvoptions.sty)
>>> Implicit mode ON; LaTeX internals redefined
>>> (/usr/share/texmf-texlive/tex/latex/ltxmisc/url.sty))
>>> *hyperref using default driver hpdftex*
>>> (/usr/share/texmf-texlive/tex/latex/hyperref/hpdftex.def) (./
>>> master.aux
>>> (./introduction.aux) (./buildScripts.aux) (./javaTutorial.aux)
>>> (./thisAndThat.aux) (./overview.aux) (./projectTaskApi.aux) (./
>>> tasks.aux)
>>> (./plugins.aux
>>>
>>> LaTeX Warning: Label `sec:summary' multiply defined.
>>>
>>> ) (./javaPlugin.aux) (./groovyPlugin.aux
>>>
>>> LaTeX Warning: Label `sec:compile' multiply defined.
>>>
>>> ) (./depMngmt.aux)) (/usr/share/texmf-texlive/tex/latex/base/
>>> ts1cmr.fd)
>>> (/usr/share/texmf-texlive/tex/latex/hyperref/nameref.sty
>>> (/usr/share/texmf-texlive/tex/latex/oberdiek/refcount.sty)) (./
>>> master.out)
>>> (./master.out) (../../../build/docs/userguide/data/version.tex)
>>> [1{/var/lib/tex
>>> mf/fonts/map/pdftex/updmap/pdftex.map}] (./master.toc) [1]
>>> (./introduction.tex
>>> Chapter 1.
>>> )pdfTeX warning (ext4): destination with the same identifier (name
>>> {page.1})
>>> has
>>>  been already used, duplicate ignored
>>> <to be read again>
>>>                    \relax
>>> l.71 \include{introduction}
>>>                             [1]
>>> No file buildScripts.tex.
>>> (./javaTutorial.tex
>>> Chapter 2.
>>> (/usr/share/texmf-texlive/tex/latex/base/ts1cmtt.fd) [2]) [3]
>>> (./thisAndThat.tex
>>> Chapter 3.
>>>
>>> Overfull \hbox (7.11407pt too wide) in paragraph at lines 16--18
>>> \OT1/cmr/m/n/10 If the rules for skip-ping a task can't be ex-
>>> pressed with a
>>> si
>>> m-ple prop-erty, you can use the \OT1/cmtt/m/n/10
>>> StopExecutionException[]\OT1/
>>> cmr/m/n/10 .
>>> [4]
>>>
>>> LaTeX Warning: Reference `ide_support' on page 5 undefined on  
>>> input line 22.
>>>
>>>
>>> LaTeX Warning: Reference `cha:command_line' on page 5 undefined  
>>> on input
>>> line 2
>>> 5.
>>>
>>>
>>> Underfull \hbox (badness 10000) in paragraph at lines 25--27
>>>
>>>
>>> Overfull \hbox (40.31412pt too wide) in paragraph at lines 42--48
>>> [][]
>>> [5]
>>> Overfull \hbox (12.98004pt too wide) in paragraph at lines 65--66
>>> []\OT1/cmr/m/n/10 There is also the pos-si-bil-ity to di-rectly add
>>> prop-er-tie
>>> s to your project ob-jects. You can place a \OT1/cmtt/m/n/10
>>> gradle.properties
>>> ) [6] (./overview.tex
>>> Chapter 4.
>>> [7]) [8] (./projectTaskApi.tex
>>> Chapter 5.
>>>
>>> LaTeX Warning: Reference `cha:gradle_core_tutorial' on page 9  
>>> undefined on
>>> inpu
>>> t line 7.
>>>
>>>
>>> LaTeX Warning: Reference `cha:gradle_core_tutorial' on page 9  
>>> undefined on
>>> inpu
>>> t line 19.
>>>
>>>
>>> LaTeX Warning: Reference `cha:multi_project_builds' on page 9  
>>> undefined on
>>> inpu
>>> t line 23.
>>>
>>> ) [9] (./tasks.tex
>>> Chapter 6.
>>>
>>> LaTeX Warning: Reference `cha:gradle_core_tutorial' on page 10  
>>> undefined on
>>> inp
>>> ut line 4.
>>>
>>> [10]) [11] (./plugins.tex
>>> Chapter 7.
>>>
>>> LaTeX Warning: Reference `cha:ide_support' on page 12 undefined  
>>> on input
>>> line 2
>>> 3.
>>>
>>>
>>> LaTeX Warning: Reference `cha:organizing_build_logic' on page 12  
>>> undefined
>>> on i
>>> nput line 29.
>>>
>>> [12]) [13] (./javaPlugin.tex
>>> Chapter 8.
>>> [14] [15]
>>> Overfull \hbox (25.89717pt too wide) in paragraph at lines 129--131
>>> \OT1/cmr/m/n/10 The \OT1/cmtt/m/n/10 resources \OT1/cmr/m/n/10  
>>> task of-fers
>>> in-
>>> cludes and ex-cludes di-rec-tives as well as fil-ters. Have a  
>>> look at
>>> [][]org.g
>>> radle.api.tasks.Resources[][]
>>>
>>> LaTeX Warning: Reference `' on page 16 undefined on input line 150.
>>>
>>> [16] [17]
>>> Overfull \hbox (73.75406pt too wide) in paragraph at lines 253--254
>>> \OT1/cmr/m/n/10 The con-ven-tion ob-ject of the JavaPlu-gin has a
>>> \OT1/cmtt/m/n
>>> /10 manifest \OT1/cmr/m/n/10 prop-erty point-ing to an in-stance of
>>> [][]org.gra
>>> dle.api.bundling.GradleManifest[][].
>>> ) [18] (./groovyPlugin.tex
>>> Chapter 9.
>>> [19]) [20] (./depMngmt.tex
>>> Chapter 10.
>>> [21] [22]
>>>
>>> LaTeX Warning: Reference `cha:multi_project_builds' on page 23  
>>> undefined on
>>> inp
>>> ut line 110.
>>>
>>> [23] [24] [25]
>>>
>>> LaTeX Warning: Reference `sub:resolver_container' on page 26  
>>> undefined on
>>> input
>>>  line 219.
>>>
>>> )
>>> Runaway argument?
>>> {To make things more flexible (or complicated). By default the  
>>> build \ETC.
>>> ! File ended while scanning use of \@footnotetext.
>>> <inserted text>
>>>                 \par
>>> l.81 \include{depMngmt}
>>>
>>> ?
>>> ! Emergency stop.
>>> <inserted text>
>>>                 \par
>>> l.81 \include{depMngmt}
>>>
>>> !  ==> Fatal error occurred, no output PDF file produced!
>>> Transcript written on master.log.
>>>
>>>
>>> hdockter wrote:
>>>>
>>>>
>>>> On Jun 2, 2008, at 5:27 PM, Ittay Dror wrote:
>>>>
>>>>>
>>>>>
>>>>>
>>>>> hdockter wrote:
>>>>>>
>>>>>> It looks like the LaTeX generation was not successful.  
>>>>>> Therefore the
>>>>>> master.pdf file does not exists and therefore an exception is  
>>>>>> thrown.
>>>>>>
>>>>>> The output of the LaTeX pdf process can be found in: build/docs/
>>>>>> userguide/pdfOut
>>>>>>
>>>>> it seems it can't find upquote.sty. in ubuntu, this is in a
>>>>> separate package
>>>>> called texlive-latex-extra.
>>>>>
>>>>> the build should have failed then, right? not continue.
>>>>
>>>> right
>>>>
>>>>>
>>>>> ittay
>>>>>
>>>>> --
>>>>> View this message in context: http://www.nabble.com/can%27t-build-
>>>>> from-svn-tp17601562p17603995.html
>>>>> Sent from the gradle-dev mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> ---
>>>>> To unsubscribe from this list, please visit:
>>>>>
>>>>>     http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>
>>>> --
>>>> Hans Dockter
>>>> Gradle Project lead
>>>> http://www.gradle.org
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe from this list, please visit:
>>>>
>>>>     http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context: http://www.nabble.com/can%27t-build- 
>>> from-svn-tp17601562p17604520.html
>>> Sent from the gradle-dev mailing list archive at Nabble.com.
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe from this list, please visit:
>>>
>>>     http://xircles.codehaus.org/manage_email
>>>
>>>
>>
>> --
>> Hans Dockter
>> Gradle Project lead
>> http://www.gradle.org
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>
> --
> Hans Dockter
> Gradle Project lead
> http://www.gradle.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: can't build from svn

Ittay Dror
In reply to this post by Russel Winder-2

Russel Winder-4 wrote
I strongly recommend using Bazaar.  In a shared repository you create a
mirror of the Subversion repository, then in the same shared repository
you branch the mirror for you working branch.  Then you have a local
mirror which is always buildable.  You can even make corrections such as
this one and then pull the changes into you working branch so as to keep
it up to date.  Then use rebase to realign the working branch to the
mirror.
I recommend using Git. It has great support for SVN and is very popular (linux kernel, x.org, wine, ruby-on-rails, to name a few). You can do amazing things with it. In general I find that DVCS is great for keeping a clean history.

Here is a link to a presentation that explains Git's internals: http://s3.amazonaws.com/chacon/git-talk.pdf

Ittay
Reply | Threaded
Open this post in threaded view
|

Re: can't build from svn

Russel Winder-2
On Wed, 2008-06-04 at 21:36 -0700, Ittay Dror wrote:

>
>
> Russel Winder-4 wrote:
> >
> > I strongly recommend using Bazaar.  In a shared repository you create a
> > mirror of the Subversion repository, then in the same shared repository
> > you branch the mirror for you working branch.  Then you have a local
> > mirror which is always buildable.  You can even make corrections such as
> > this one and then pull the changes into you working branch so as to keep
> > it up to date.  Then use rebase to realign the working branch to the
> > mirror.
> >
> I recommend using Git. It has great support for SVN and is very popular
> (linux kernel, x.org, wine, ruby-on-rails, to name a few). You can do
> amazing things with it. In general I find that DVCS is great for keeping a
> clean history.
Git with git-svn certainly can do the task.  If you know Git it can be
very powerful, but it is bitty, inconsistent, really awkward for
anything other than the Linux development process, and it is oh so easy
to really make a total mess of your repository.  I find Bazaar with
bzr-svn much more comfortable to use.  The Bazaar way of handling
branches using a shared repository is, for me, easier to work with that
the Git way of handling branches in a repository.  

Git treats a Subversion store as a second class citizen, whereas Bazaar
treats a Subversion repository as a place to store a Bazaar branch.
Depending on what you are trying to do, both of these have their merits.
But I think that is the point, there is no one right tool in this
situation because there is no one tool that does the right thing in all
situations.

As a client for working on a Subversion I try to use Bazaar because I
feel more comfortable with it, yet there are things that Git does do
better, so sometimes it is right to use it.

If I were being totally honest, for some Subversion repositories I have
both Bazaar and Git repoistories, I use the Bazaar ones mostly but
occasionally use Git.  I just wish that there was a git-bzr plugin and
that the bzr-git plugin worked better.
 
The moral of the story is actually:  Do not use Subversion as a client
to a Subversion repository.

A subsidiary moral is:  branching and merging is a DVCS thing, not a
Subversion thing, so development branching is easier in Bazaar, Git, or
Mercurial (which hasn't had a mention yet, but does deserve it).

--
Russel.
====================================================
Dr Russel Winder                 Partner

Concertant LLP                   t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road,              f: +44 8700 516 084
London SW11 1EN, UK.             m: +44 7770 465 077

signature.asc (196 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: can't build from svn

hans_d
Administrator
In reply to this post by Ittay Dror
I haven't tried any of the DVCS systems yet but I'm starting to  
understand the deficiencies of Svn.

In the last article I've read about this they were recommending  
Mercurial. They said Mercurial and GIT are very similar but Mercurial  
has much better support for windows machines. Well, I'm on a Mac but  
many are on windows. This article also says that Arch, Bazaar, Darcs  
or SVK are not much used.

The biggest pain I have with SVN is when working on two branches at  
the same time and always having to manually merge from one to the  
other. I suppose that SVN 1.5 will be much better here.

Tool Support is another worry when thinking about switching.

- Hans

On Jun 5, 2008, at 6:36 AM, Ittay Dror wrote:

>
>
>
> Russel Winder-4 wrote:
>>
>> I strongly recommend using Bazaar.  In a shared repository you  
>> create a
>> mirror of the Subversion repository, then in the same shared  
>> repository
>> you branch the mirror for you working branch.  Then you have a local
>> mirror which is always buildable.  You can even make corrections  
>> such as
>> this one and then pull the changes into you working branch so as  
>> to keep
>> it up to date.  Then use rebase to realign the working branch to the
>> mirror.
>>
> I recommend using Git. It has great support for SVN and is very  
> popular
> (linux kernel, x.org, wine, ruby-on-rails, to name a few). You can do
> amazing things with it. In general I find that DVCS is great for  
> keeping a
> clean history.
>
> Here is a link to a presentation that explains Git's internals:
> http://s3.amazonaws.com/chacon/git-talk.pdf
>
> Ittay
>
> --
> View this message in context: http://www.nabble.com/can%27t-build- 
> from-svn-tp17601562p17661928.html
> Sent from the gradle-dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: can't build from svn

Russel Winder-2
On Thu, 2008-06-05 at 12:49 +0200, Hans Dockter wrote:
> I haven't tried any of the DVCS systems yet but I'm starting to  
> understand the deficiencies of Svn.

I believe that even 1.5 when (if?) it is ever released will not cure the
problems -- though it will solve the svnmerge problem I am told.

> In the last article I've read about this they were recommending  
> Mercurial. They said Mercurial and GIT are very similar but Mercurial  
> has much better support for windows machines. Well, I'm on a Mac but  
> many are on windows. This article also says that Arch, Bazaar, Darcs  
> or SVK are not much used.

Arch has been overtaken by events: a group of the Arch developers left
to start Bazaar.  SVK was a possible solution to the problems of
Subversion.  It uses Perl on the Subversion libraries.  However, given
the ability of Bazaar and Git to work with Subversion repositories, SVK
will never take off.  Darcs has some interesting features but due to the
problems of some merges taking longer than the life of the universe,
people tended to look elsewhere.  Darcs2 fixes the problem I believe,
but opportunity has passed Darcs by, ditto Aegis, Vesta, and whole load
fo other interesting systems.

Bazaar, Mercurial and Git are the players, the article was wrong to
indicate that Bazaar was not.

Mercurial looks to be a good system but as far as I am aware interaction
with Subversion repositories is still poor -- Bazaar and Git already
have this working well.  This puts me very much in the Bazaar camp.  

Jim Hague and I did a session on Mercurial and Bazaar at ACCU 2008 the
slides are at  http://www.concertant.com/Presentationa/accu2008_dvcs.pdf

> The biggest pain I have with SVN is when working on two branches at  
> the same time and always having to manually merge from one to the  
> other. I suppose that SVN 1.5 will be much better here.

Alternatively just treat the Subversion repository as the published
trunk and do everything else with Bazaar or Git.  I find Launchpad very
useful for working with Bazaar branches, I would guess there is an
equivalent for Git.

> Tool Support is another worry when thinking about switching.

I very much agree.  This is all very platform dependent and whether you
work with command line or GUI.
--
Russel.
====================================================
Dr Russel Winder                 Partner

Concertant LLP                   t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road,              f: +44 8700 516 084
London SW11 1EN, UK.             m: +44 7770 465 077

signature.asc (196 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: can't build from svn

David Freels-2
In reply to this post by Ittay Dror
Mercurial already has good integration with the major IDEs. Not sure about Git and Bazaar.

 David Freels


----- Original Message ----
From: Russel Winder <[hidden email]>
To: [hidden email]
Sent: Thursday, June 5, 2008 7:59:07 AM
Subject: Re: [gradle-dev] can't build from svn

On Thu, 2008-06-05 at 12:49 +0200, Hans Dockter wrote:
> I haven't tried any of the DVCS systems yet but I'm starting to  
> understand the deficiencies of Svn.

I believe that even 1.5 when (if?) it is ever released will not cure the
problems -- though it will solve the svnmerge problem I am told.

> In the last article I've read about this they were recommending  
> Mercurial. They said Mercurial and GIT are very similar but Mercurial  
> has much better support for windows machines. Well, I'm on a Mac but  
> many are on windows. This article also says that Arch, Bazaar, Darcs  
> or SVK are not much used.

Arch has been overtaken by events: a group of the Arch developers left
to start Bazaar.  SVK was a possible solution to the problems of
Subversion.  It uses Perl on the Subversion libraries.  However, given
the ability of Bazaar and Git to work with Subversion repositories, SVK
will never take off.  Darcs has some interesting features but due to the
problems of some merges taking longer than the life of the universe,
people tended to look elsewhere.  Darcs2 fixes the problem I believe,
but opportunity has passed Darcs by, ditto Aegis, Vesta, and whole load
fo other interesting systems.

Bazaar, Mercurial and Git are the players, the article was wrong to
indicate that Bazaar was not.

Mercurial looks to be a good system but as far as I am aware interaction
with Subversion repositories is still poor -- Bazaar and Git already
have this working well.  This puts me very much in the Bazaar camp.  

Jim Hague and I did a session on Mercurial and Bazaar at ACCU 2008 the
slides are at  http://www.concertant.com/Presentationa/accu2008_dvcs.pdf

> The biggest pain I have with SVN is when working on two branches at  
> the same time and always having to manually merge from one to the  
> other. I suppose that SVN 1.5 will be much better here.

Alternatively just treat the Subversion repository as the published
trunk and do everything else with Bazaar or Git.  I find Launchpad very
useful for working with Bazaar branches, I would guess there is an
equivalent for Git.

> Tool Support is another worry when thinking about switching.

I very much agree.  This is all very platform dependent and whether you
work with command line or GUI.
--
Russel.
====================================================
Dr Russel Winder                 Partner

Concertant LLP                   t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road,              f: +44 8700 516 084
London SW11 1EN, UK.             m: +44 7770 465 077



     

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: can't build from svn

Russel Winder-2
On Thu, 2008-06-05 at 05:55 -0700, David Freels wrote:
> Mercurial already has good integration with the major IDEs. Not sure about Git and Bazaar.

Mercurial certainly has good integration in NetBeans ( Sun has chosen
Mercurial as its VCS and has followed that through to NetBeans support),
Bazaar and Git I think are sadly lacking.  Eclipse has Bazaar, Mercurial
and Git support I believe but CVS is still the only system integrally
supported in Eclipse, even Subclipse and Subversive are mere add-ons.

I think Bazaar, Mercurial and Git are all supported in the only IDE that
matters, Emacs ;-)

--
Russel.
====================================================
Dr Russel Winder                 Partner

Concertant LLP                   t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road,              f: +44 8700 516 084
London SW11 1EN, UK.             m: +44 7770 465 077

signature.asc (196 bytes) Download Attachment