DO NOT REPLY [Bug 25349] - Javadoc useexternalfile option fails with directory names with spaces

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25349

Javadoc useexternalfile option fails with directory names with spaces

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
  everconfirmed|0   |1

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [VOTE] Jose Alberto Fernandez as committer

[Jan . Materne]

+1 
Jan

> -Original Message-
> From: Conor MacNeill [mailto:[EMAIL PROTECTED]
> Sent: Sunday, December 14, 2003 11:17 PM
> To: Ant Developers List
> Subject: Re: [VOTE] Jose Alberto Fernandez as committer
> 
> 
> On Fri, 12 Dec 2003 09:08 pm, Antoine Lévy-Lambert wrote:
> > Hi,
> >
> > I would like to propose a vote for Jose Alberto Fernandez as new ant
> > committer.
> >
> 
> +1
> 
> Conor
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

RE: Release date of ant 1.6

[Jan . Materne]

> > I would like to release ant 1.6 on Thursday, December 18th, in the
> > evening.
> 
> I'll be on vacation already, assume you have my provisional +1.

I wish you a nice holiday :-)


> > Enhancement reports asked by our users can be dealt with in minor
> > releases of ant 1.6 or in ant 1.7.
> 
> As well as the open bug reports.  A zero-bug release will never
> happen, no matter how long we wait 8-)

well said ...


> What about the name?  1.6 or 1.6.0?  I tend to prefer 1.6.0 as we know
> pretty well that a 1.6.1 is going to happen.

I prefer 1.6 according to the earlier names. Personally I add a ".0" to
each version number of software I see :-)
But how you say on Unix? "Namen sind Schall und Rauch" (names doesn´t
matter).


Jan

Re: problems with logging (message priority level)

[Peter Reilly]

This problem came up before in a different context (but
I forgot to follow it up).
The logging for stderr is set to priority error unless the task
is run in a different jvm, in which case it is at level warning.
This is inconsistent and it would appear to be incorrect to set
the priority to "error".
I think we should change the priority in this case to warning. This
is of course not backward compatible.
Peter
Falko Wiese wrote:
Hi,
we wrote our own xsl stylesheet for parsing ant log infos. With the 
message priorities (debug, info, warn, error) we want to decide 
whether our build run is complete, failed etc. We use ant version 1.5.4.

The output for the command 'ant -logger org.apache.tools.ant.XmlLogger 
-Dant.XmlLogger.stylesheet.uri= -logfile  
 -verbose  >/dev/null 2>&1' is the following:

...







...
Has anyone an idea, why the message priority is not 'warn'? Thanks a 
lot for help,

Falko Wiese.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25540] New: - echo hyperlinks

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25540

echo hyperlinks

   Summary: echo hyperlinks
   Product: Ant
   Version: 1.5.4
  Platform: All
OS/Version: All
Status: NEW
  Severity: Enhancement
  Priority: Other
 Component: Core tasks
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


I use the apache XmlLogger and log.xsl to format my build output.
I would find it extremely useful if I could add hyperlinks to this output 
(perhaps via the echo task), but output messages are logged as CDATA and thus 
any html is taken literally as text.

Scenario:
I have an external process executed via an exec task that produces a log file.
It would be extremely useful if I could add a hyperlink to this external log 
file so that I can browse straight from the log.xsl-styled build output to the 
external log file from my browser.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25544] New: - record task overwrites existing log file (doc says it appends)

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25544

record task overwrites existing log file (doc says it appends)

   Summary: record task overwrites existing log file (doc says it
appends)
   Product: Ant
   Version: 1.5.3
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Core tasks
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Running ant -f twice with the following file:








should produce two sets of log output in the broken_append_default.log file.
Instead, only one set of log output is recorded. This is because the file is
overwritten. The doc (http://ant.apache.org/manual/CoreTasks/recorder.html) says
that the default for tha append attribute is 'yes', but the actual default seems
to be no. 
Workaround is to hardcode the append attribute to 'yes'.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25544] - record task overwrites existing log file (doc says it appends)

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25544

record task overwrites existing log file (doc says it appends)

[EMAIL PROTECTED] changed:

   What|Removed |Added

Version|1.5.3   |1.5.4



--- Additional Comments From [EMAIL PROTECTED]  2003-12-15 20:58 ---
Also tested with Ant 1.5.4. Same behavior as Ant 1.5.3. Changed Version to 
1.5.4.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25546] New: - Option "-propertyfile" don't work right.

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25546

Option "-propertyfile" don't work right.

   Summary: Option "-propertyfile" don't work right.
   Product: Ant
   Version: 1.5.4
  Platform: Other
OS/Version: Other
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Other
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


When I try execute my build executing with -propertyfile buil.properties, the
properties that contain references to other properties are missundertanding.
Example:

build.properties

project.dir=/tmp/proj/myProj

proj.lib.dir=${project.dir}/lib


A Task using this in build.xml:




When this target is executed by ant ommiting -propertiesfile, the execution is
ok (the directory /tmp/proj/MyProj/lib is created).
But if I execute this task using "-propertyfile build.properties", the directory
maked is ${project.dir}/lib in current directory.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25546] - Option "-propertyfile" don't work right.

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25546

Option "-propertyfile" don't work right.





--- Additional Comments From [EMAIL PROTECTED]  2003-12-15 21:08 ---
Correct in example:
my task is:

   



Sorry,
:)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]