Dennis Lundberg wrote:
> 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 history of the Maven JXR
project.
>> o The orignal JXR code was merged in 2004 with the Javasrc project
>> from the defunct Jakarta Alexandria project.
>> o 14/May/06 version 2.0 released: around 8 issues fixed
>> o 05/Apr/07 version 2.1 released: around 24 issues fixed
>>
>> During the last year, Dennis and myself are the main committers on
>> this JXR project. So I would like to hear Dennis about this proposal.
>>
>> Actually, IMHO the JXR project is stable (currently only 8 open issues
>> [1], mainly to add more transformers and to provide javadoc like
>> features). Some issues could be done by the Forrestdoc tool. The main
>> addons with Forrestdoc are for JXR-10, JXR-13. You could see the
>> differences here (see JXR-54):
>> http://people.apache.org/~vsiveton/forrestdoc/my-proj/xref/index.html
>>
http://people.apache.org/~vsiveton/forrestdoc/my-proj/javasrc/index.html
>>
>>> 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 to import this
>>> code, as opposed to, say, let the forrest people vote you in as
>>> committer and/or try to get a release from there.
>>
>> If the Forrest Team wants to handover the code, I think we could do
>> the following:
>> o first, create a JXR sandbox project with new code and mavenize it
>> o secondly, graduate it by merging it with the JXR code (and maybe
>> supplement it with a version 3.0 for instance, not sure actually)
>>
>> The key advantage is that this new code would be shared by the Maven
>> community so we would basically be free to do whatever we feel is
>> appropriate.
>> The Forrest team doesnt want to provide POM in the Maven repositories,
>> "while Forrest has no other presence there". It is clear to me that
>> the Forrest community will always be welcome and just like Brett said,
>> we could work together in the future.
>>
>>> As I understand, you are (still) the only one actually working on the
>>> code, so you should decide what is most convenient for you, and if
you
>>> volunteer to maintain it I see no problem to take it over, just to
get
>>> an idea on what is going to happen.
>>
>> To be honnest, my involvement in the Forrestdoc tool was only related
>> to the development of some patches so far. Obviously, I'm willing to
>> participate on the maintenance of the integration if other team
>> members are ready to get their hands dirty as well. Dennis: Would you
>> like to get involve it this?
>>
>> HTH,
>>
>> Cheers,
>>
>> Vincent
>>
>>> cheers
>>> -Lukas
>>>
>>>
>>> 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. WDYT?
>>> >
>>> > Cheers,
>>> >
>>> > Vincent
>>> >
>>> > 2007/6/6, Vincent Siveton <[EMAIL PROTECTED]>:
>>> >
>>> >> 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 is not possible to aggregate several Maven
>>> >> projects.
>>> >>
>>> >> Your feedback are of course welcome.
>>> >>
>>> >> Cheers,
>>> >>
>>> >> Vincent
>>> >>
>>> >> 2007/6/5, Thorsten Scherler
>>> <[EMAIL PROTECTED]>:
>>> >> > 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 Team want to start a discussion about Forrestdoc
>>> and JXR
>>> >> > > > projects.
>>> >> > > >
>>> >> > > > Background:
>>> >> > > > Forrestdoc [1]: Forrestdoc is a Javadoc/Source
>>> code/Documentation
>>> >> > > > management system.
>>> >> > > > JXR [2]: JXR is a source cross reference generator.
>>> >> > > >
>>> >> > > > It sounds that these projects are very similar.
>>> >> > >
>>> >> > > I believe both originated from the same code at Alexandria.
>>> >> >
>>> >> > http://issues.apache.org/jira/browse/FOR-820 has a nice link
>>> >> > http://marc.theaimsgroup.com/?l=forrest-dev&m=114082527806288
>>> >> >
>>> >> > Yes both are using Alexandria and working together seems to be a
>>> topic
>>> >> > before as well.
>>> >> >
>>> >> > >
>>> >> > > >
>>> >> > > > What is the status of Forrestdoc? Any release available?
Could
>>> >> we join
>>> >> > > > our efforts?
>>> >> >
>>> >> > You are always welcome to join. A release does not exists ATM
>>> and like
>>> >> > Gavin said it had not much attention over the last years.
>>> >> >
>>> >> > I had a quick look on the example and the code. Seems to be
pretty
>>> >> > useful. Not sure how much time I will find (and when) to have a
>>> closer
>>> >> > look but working together on it could really speed things up.
>>> >> >
>>> >> > salu2
>>> >> > --
>>> >> > Thorsten Scherler
>>> >> thorsten.at.apache.org
>>> >> > Open Source Java consulting, training and
>>> >> solutions
>>> >> >
>>> >> >
>>> >> >
>>> ---------------------------------------------------------------------
>>> >> > 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]
>>>
>>> ---------------------------------------------------------------------
>>> 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]
>>
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
