Note for the archives: Discussion continued at:
Re: [Proposal] decide the future of forrestdoc
http://marc.info/?t=11841339891
-David
Vincent Siveton wrote:
> Hi guys,
>
> Thanks for your replies.
>
> I created a new JXR issue for this thread.
> http://jira.codehaus.org/browse/JXR-54
>
>
OK, then I'm in.
Vincent Siveton wrote:
Hi,
2007/7/19, Dennis Lundberg <[EMAIL PROTECTED]>:
Vincent,
Do you see that we replace the "engine" currently in JXR that
pretty-prints the Java code and adds anchors to it, with the
corresponding part of ForrestDoc? Or perhaps have it as an alternativ
Hi,
2007/7/19, Dennis Lundberg <[EMAIL PROTECTED]>:
Vincent,
Do you see that we replace the "engine" currently in JXR that
pretty-prints the Java code and adds anchors to it, with the
corresponding part of ForrestDoc? Or perhaps have it as an alternative
engine.
As I proposed, a possibility c
Vincent,
Do you see that we replace the "engine" currently in JXR that
pretty-prints the Java code and adds anchors to it, with the
corresponding part of ForrestDoc? Or perhaps have it as an alternative
engine.
If so I'm in favor of bringing ForrestDoc over here, as it adds value
over what
Vincent Siveton wrote:
Hi,
2007/7/13, Lukas Theussl <[EMAIL PROTECTED]>:
Could you clarify a bit your intentions, I don't know if I missed that
in the discussion so far.
For the log and AFAIK, here is a brief history of the Maven JXR project.
o The orignal JXR code was merged in 2004 with
I'll have a closer look at what Forrestdoc is and if/how it could
enhance JXR.
Vincent Siveton wrote:
Hi,
2007/7/13, Lukas Theussl <[EMAIL PROTECTED]>:
Could you clarify a bit your intentions, I don't know if I missed that
in the discussion so far.
For the log and AFAIK, here is a brief his
Hi Brett,
2007/7/13, Brett Porter <[EMAIL PROTECTED]>:
On 13/07/2007, at 8:37 PM, Vincent Siveton wrote:
> Hi,
>
> FYI, the Forrest Team started a discussion about the future of
> Forrestdoc:
> http://www.nabble.com/-Proposal--decide-the-future-of-forrestdoc-
> tf4060050.html
>
> A key concern
Hi,
2007/7/13, Lukas Theussl <[EMAIL PROTECTED]>:
Could you clarify a bit your intentions, I don't know if I missed that
in the discussion so far.
For the log and AFAIK, here is a brief history of the Maven JXR project.
o The orignal JXR code was merged in 2004 with the Javasrc project
from th
Could you clarify a bit your intentions, I don't know if I missed that
in the discussion so far.
If we accept the code, is it going to stay a separate project or will it
be merged with jxr? Are they going to compete or supplement each other?
What is the concrete advantage for the Maven project
On 13/07/2007, at 8:37 PM, Vincent Siveton wrote:
Hi,
FYI, the Forrest Team started a discussion about the future of
Forrestdoc:
http://www.nabble.com/-Proposal--decide-the-future-of-forrestdoc-
tf4060050.html
A key concern is to know if the Maven community would like to accept
the code.
Hi,
FYI, the Forrest Team started a discussion about the future of Forrestdoc:
http://www.nabble.com/-Proposal--decide-the-future-of-forrestdoc-tf4060050.html
A key concern is to know if the Maven community would like to accept
the code. WDYT?
Cheers,
Vincent
2007/6/6, Vincent Siveton <[EMAIL
Hi guys,
Thanks for your replies.
I created a new JXR issue for this thread.
http://jira.codehaus.org/browse/JXR-54
You could see that I created a Maven Forrestdoc Plugin to handle the
Forrestdoc tool.
Actually, Forrestdoc has several limitations like the hardcoded bottom
and the fact that it i
On Mon, 2007-06-04 at 21:27 +0800, Gav wrote:
>
> > -Original Message-
> > From: Vincent Siveton [mailto:[EMAIL PROTECTED]
> > Sent: Monday, 4 June 2007 8:27 PM
> > To: [EMAIL PROTECTED]
> > Cc: dev@maven.apache.org
> > Subject: Forrestdoc and Maven JXR
> >
> > Hi,
> >
> > The Maven
> -Original Message-
> From: Vincent Siveton [mailto:[EMAIL PROTECTED]
> Sent: Monday, 4 June 2007 8:27 PM
> To: [EMAIL PROTECTED]
> Cc: dev@maven.apache.org
> Subject: Forrestdoc and Maven JXR
>
> Hi,
>
> The Maven Team want to start a discussion about Forrestdoc and JXR
> projects.
>
14 matches
Mail list logo