Hi Benjamin,
2008/4/12, Benjamin Bentmann [EMAIL PROTECTED]:
Hi,
According to the APT Reference [0] and the output delivered by the Maven
Site Plugin 2.0-beta-6, the construct
{{{foo}baa}}
denotes an internal link to the anchor foo in the current document. I
believe this kind of
Not sure. Take a look to the renderer [1] and the source [2]. Link are
external for {{{guide-testing-releases.html} test releases}}
I just stumbled upon this in r647420 [0]. After some other tries I figured
out:
- {{{foo.html}baa}} is external
- {{{foo.txt}baa}} is internal
i.e. the linking
Coming back to your original mail, I actually don't quite see the
necessity of the change. Intuitive is probably a subjective concept, but
I don't find the current behavior that un-intuitive. If current apt
makes {{foo}bar}} an internal link then I would intuitively expect that
{{foo.x}bar}}
Benjamin Bentmann wrote:
See my comment at http://jira.codehaus.org/browse/DOXIA-208
Your proposal at
http://docs.codehaus.org/display/DOXIA/Proposed+Changes+to+the+APT+Format
already suggests to break compat with the original APT format. I beg you to
go this route down to its end and make
Intuitive is probably a subjective concept
Agreed.
I don't find the current behavior that un-intuitive. If current apt makes
{{foo}bar}} an internal link then I would intuitively expect that
{{foo.x}bar}} is an internal link too
Let's remember that this expectation is in general not true
Hi,
The guide Plugin Documentation Standard [0] linked to a page from the
Javadoc Plugin which was published back in 2006 [1]. Do we have means to
purge the output directory for the site on the web server to get rid of
those relics?
Benjamin
[0]
Hi Benjamin,
2008/4/12, Benjamin Bentmann [EMAIL PROTECTED]:
Hi,
The guide Plugin Documentation Standard [0] linked to a page from the
Javadoc Plugin which was published back in 2006 [1]. Do we have means to
purge the output directory for the site on the web server to get rid of
those
I've checked JIRA now and found this issue that describes what I was
experiencing.
http://jira.codehaus.org/browse/MRELEASE-123
To be able to do the release I disabled the aggregation by commenting
out the modules element.
What is the purpose of having a modules element for our plugins?
What is the purpose of having a modules element for our plugins? It's
not like we want to build all plugins in one go, is it?
Hudson used to do this if I remember correctly (the plugin ITs seem to have
been removed recently).
Benjamin
Hudson uses this to detect the children so we need this in there.
-Original Message-
From: Benjamin Bentmann [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 12, 2008 8:47 AM
To: Maven Developers List
Subject: Re: [regression] Cannot release plugins parent!
What is the purpose of having
You could do it. Just go to people.apache.org and delete old files in
/www/maven.apache.org
Thanks, good to know. I just kicked the whole maven-javadoc-plugin dir and
redeployed the site from the 2.4 tag.
Ideally, deleting a directory should become a Wagon feature some day such
that manual
I created http://svn.apache.org/viewvc/maven/sandbox/branches/MNG-2216/
with javadoc and jxr plugins branches to test the change, and sample use
case.
no reaction: I suppose this is lazy consensus :)
I'll start to merge to plugins trunks tomorrow
regards
Hervé
Al the work is being put on a branch right? That was where I saw the discussion
with Jason going.
-Original Message-
From: Hervé BOUTEMY [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 12, 2008 10:06 AM
To: Maven Developers List
Subject: Re: [VOTE] POM Element for Source File Encoding
Wendy told me in the past that the sync is every day, so be patient :)
Hm, out of curiosity: How is this sync realized? The pages of the Javadoc
Plugin now print 2008-04-12 as last published so I assume the sync
happened. However, the obsolete page [0] is still online. Will the sync ever
delete
It uses rsync and the option to delete files not present at the source
must be off.
On 12-Apr-08, at 9:05 AM, Benjamin Bentmann wrote:
Wendy told me in the past that the sync is every day, so be
patient :)
Hm, out of curiosity: How is this sync realized? The pages of the
Javadoc
Plugin
2008/4/12, Benjamin Bentmann [EMAIL PROTECTED]:
Wendy told me in the past that the sync is every day, so be patient :)
Hm, out of curiosity: How is this sync realized? The pages of the Javadoc
Plugin now print 2008-04-12 as last published so I assume the sync
happened. However, the
It only deletes once a day.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 12, 2008 12:42 PM
To: Maven Developers List
Subject: Re: Delete Obsolete Site Contents
It uses rsync and the option to delete files not present at the source
must be off.
Le samedi 12 avril 2008, Brian E. Fox a écrit :
Al the work is being put on a branch right? That was where I saw the
discussion with Jason going.
I did the work on 2 plugins in a branch:
- jxr: http://svn.apache.org/viewvc?rev=645260view=rev
- javadoc:
Is that to prevent you from having to set up 39 individual projects in
Hudson (or any other CI server) ?
Brian E. Fox wrote:
Hudson uses this to detect the children so we need this in there.
-Original Message-
From: Benjamin Bentmann [mailto:[EMAIL PROTECTED]
Sent: Saturday, April
Yes that's one reason. I often go into that folder and do a top to
bottom build or resolve all dependencies etc. Modules is a normal part
of the build hierarchy and we should start axing it out because of a
release plugin bug. If you want to comment it out so you can do your
release and put it
For a situation like this where a parent is also being used
sometimes for building all the children although that is not its
primary purpose, how about putting the modules in a profile that e.g.
hudson can use?
thanks
david jencks
On Apr 12, 2008, at 4:18 PM, Brian E. Fox wrote:
Yes
I saw leave it as it is because that is the normal scenario and the one
users are most likely to have. This way we see and fix the same things
they will need.
-Original Message-
From: David Jencks [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 12, 2008 7:26 PM
To: Maven Developers List
Vincet,
I don't see these merged back to trunk?
Also, it'd be really helpful to add tests for these changes.
Thanks,
Brett
On 12/04/2008, at 11:33 PM, [EMAIL PROTECTED] wrote:
Author: vsiveton
Date: Sat Apr 12 06:33:37 2008
New Revision: 647446
URL:
23 matches
Mail list logo
