Forrestdoc and Maven JXR

[Vincent Siveton]

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.

What is the status of Forrestdoc? Any release available? Could we join
our efforts?

Thanks,

Vincent

[1] http://people.apache.org/~nicolaken/whiteboard/forrestdoc/
[2] http://maven.apache.org/jxr/

---------- Forwarded message ----------
From: Brett Porter <brett@...>
Date: 3 juin 2007 21:55
Subject: Re: Discuss about JXR issues
To: Maven Developers List <dev@...>


It looks like that hasn't been released, and so couldn't be used as a
dependency. And a separate plugin wouldn't be able to integrate it
into JXR, would it?

If there's some way it can be reused from there, that'd be great.
Probably worth pinging the forrest team to see what they think too.

- Brett

On 04/06/2007, at 2:02 AM, Vincent Siveton wrote:

> Hi folks,
>
> Some issues in JXR (JXR-10, JXR-13) could be handled by Forrestdoc
> [1], part of the the Apache Forrest project.
>
> Which do you think is the better approach:
> * close them
> * created a new plugin that include forrestdoc librairies. Maybe we
> could work with the Forrest's team?
> * other idea
>
> Cheers,
>
> Vincent
>
> [1] http://svn.apache.org/repos/asf/forrest/trunk/whiteboard/
> forrestdoc/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Gav....]

> -----Original Message-----
> From: Vincent Siveton [mailto:vincent.siveton@...]
> Sent: Monday, 4 June 2007 8:27 PM
> To: dev@...
> Cc: dev@...
> 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.

>
> What is the status of Forrestdoc? Any release available? Could we join
> our efforts?

I don't think Forrestdoc has been worked on very much in the last couple of
years, apart from some general maintenance as part of the rest of the
peoject.

It is in our 'Whiteboard' currently, our testing ground, no official
releases come from there, they need to be voted out of whiteboard into
the main code, probably as a plugin such as it is now. It can be worked
on from there though until it is voted out.

I would certainly help out where I can see something I can do, not being a
Java person though that may be a bit limited, willing to learn though :)

Can't speak for the rest of the Forrest team though, where the code is
worked on and where it ends up needs talking through, so I'll await other
opinions on that.

Gav...

>
> Thanks,
>
> Vincent
>
> [1] http://people.apache.org/~nicolaken/whiteboard/forrestdoc/
> [2] http://maven.apache.org/jxr/
>
> ---------- Forwarded message ----------
> From: Brett Porter <brett@...>
> Date: 3 juin 2007 21:55
> Subject: Re: Discuss about JXR issues
> To: Maven Developers List <dev@...>
>
>
> It looks like that hasn't been released, and so couldn't be used as a
> dependency. And a separate plugin wouldn't be able to integrate it
> into JXR, would it?
>
> If there's some way it can be reused from there, that'd be great.
> Probably worth pinging the forrest team to see what they think too.
>
> - Brett
>
> On 04/06/2007, at 2:02 AM, Vincent Siveton wrote:
>
> > Hi folks,
> >
> > Some issues in JXR (JXR-10, JXR-13) could be handled by Forrestdoc
> > [1], part of the the Apache Forrest project.
> >
> > Which do you think is the better approach:
> > * close them
> > * created a new plugin that include forrestdoc librairies. Maybe we
> > could work with the Forrest's team?
> > * other idea
> >
> > Cheers,
> >
> > Vincent
> >
> > [1] http://svn.apache.org/repos/asf/forrest/trunk/whiteboard/
> > forrestdoc/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@...
> > For additional commands, e-mail: dev-help@...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.472 / Virus Database: 269.8.6/828 - Release Date: 6/1/2007
> 11:22 AM

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Thorsten Scherler-3]

On Mon, 2007-06-04 at 21:27 +0800, Gav.... wrote:

>
> > -----Original Message-----
> > From: Vincent Siveton [mailto:vincent.siveton@...]
> > Sent: Monday, 4 June 2007 8:27 PM
> > To: dev@...
> > Cc: dev@...
> > 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: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Vincent Siveton]

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 <thorsten.scherler.ext@...>:

> On Mon, 2007-06-04 at 21:27 +0800, Gav.... wrote:
> >
> > > -----Original Message-----
> > > From: Vincent Siveton [mailto:vincent.siveton@...]
> > > Sent: Monday, 4 June 2007 8:27 PM
> > > To: dev@...
> > > Cc: dev@...
> > > 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: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Vincent Siveton]

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 <vincent.siveton@...>:

> 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 <thorsten.scherler.ext@...>:
> > On Mon, 2007-06-04 at 21:27 +0800, Gav.... wrote:
> > >
> > > > -----Original Message-----
> > > > From: Vincent Siveton [mailto:vincent.siveton@...]
> > > > Sent: Monday, 4 June 2007 8:27 PM
> > > > To: dev@...
> > > > Cc: dev@...
> > > > 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: dev-unsubscribe@...
> > For additional commands, e-mail: dev-help@...
> >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[brettporter]

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. WDYT?

I think that's up to you and the others working on JXR at present.  
There seems to be a high overlap and good extra value, so it sounds  
worthwhile. I'm in agreement with David's comments on that thread  
above. This seems like the best home right now, it's best to have one  
copy, and if someone gets active from forrest again later we can work  
on it together.

Cheers,
Brett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Lukas Theussl-4]

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 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.

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.

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 <vincent.siveton@...>:
>
>> 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 <thorsten.scherler.ext@...>:
>> > On Mon, 2007-06-04 at 21:27 +0800, Gav.... wrote:
>> > >
>> > > > -----Original Message-----
>> > > > From: Vincent Siveton [mailto:vincent.siveton@...]
>> > > > Sent: Monday, 4 June 2007 8:27 PM
>> > > > To: dev@...
>> > > > Cc: dev@...
>> > > > 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: dev-unsubscribe@...
>> > For additional commands, e-mail: dev-help@...
>> >
>> >
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Vincent Siveton]

Hi,

2007/7/13, Lukas Theussl <ltheussl@...>:
> 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 <vincent.siveton@...>:
> >
> >> 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 <thorsten.scherler.ext@...>:
> >> > On Mon, 2007-06-04 at 21:27 +0800, Gav.... wrote:
> >> > >
> >> > > > -----Original Message-----
> >> > > > From: Vincent Siveton [mailto:vincent.siveton@...]
> >> > > > Sent: Monday, 4 June 2007 8:27 PM
> >> > > > To: dev@...
> >> > > > Cc: dev@...
> >> > > > 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: dev-unsubscribe@...
> >> > For additional commands, e-mail: dev-help@...
> >> >
> >> >
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@...
> > For additional commands, e-mail: dev-help@...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Vincent Siveton]

Hi Brett,

2007/7/13, Brett Porter <brett@...>:

>
> 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. WDYT?
>
> I think that's up to you and the others working on JXR at present.
> There seems to be a high overlap and good extra value, so it sounds
> worthwhile. I'm in agreement with David's comments on that thread
> above. This seems like the best home right now, it's best to have one
> copy, and if someone gets active from forrest again later we can work
> on it together.

Do we need a formal vote to go ahead?

Cheers,

Vincent

> Cheers,
> Brett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[dennisl-2]

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 <ltheussl@...>:
>> 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 <vincent.siveton@...>:
>> >
>> >> 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
>> <thorsten.scherler.ext@...>:
>> >> > On Mon, 2007-06-04 at 21:27 +0800, Gav.... wrote:
>> >> > >
>> >> > > > -----Original Message-----
>> >> > > > From: Vincent Siveton [mailto:vincent.siveton@...]
>> >> > > > Sent: Monday, 4 June 2007 8:27 PM
>> >> > > > To: dev@...
>> >> > > > Cc: dev@...
>> >> > > > 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: dev-unsubscribe@...
>> >> > For additional commands, e-mail: dev-help@...
>> >> >
>> >> >
>> >>
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@...
>> > For additional commands, e-mail: dev-help@...
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

--
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Lukas Theussl-4]

Vincent Siveton wrote:

> Hi,
>
> 2007/7/13, Lukas Theussl <ltheussl@...>:
>
>> 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

Just for the sake of completeness, I know a little bit about its history
too (actually I have quite fond memories since the very first patch I
ever submitted to maven was for the m1 jxr plugin :) ): after it was
taken from the alexandria project, the code was first maintained within
the m1 jxr plugin. In Sep 2005 it was voted to fork the base and create
a separate library. The first release was version 1.0 in January 2006.
AFAIK, until now jxr is the only instance where an m1 plugin is making
full and consistent use of an m2 library... ;)


> 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.

Ok, also waiting for Dennis' opinion. I think the essential thing is
that the code is maintained and cared for. Being somewhat familiar with
the jxr code, I am willing to help in case we bring it over.

-Lukas

>
> 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
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[dennisl-2]

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 we have today. The problem I see is that there seems to be
other code as well in ForrestDoc. I have not looked in detail but
references to Ant and JavaScript show up. How do we handle those?

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 <ltheussl@...>:
>>> 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 <vincent.siveton@...>:
>>> >
>>> >> 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
>>> <thorsten.scherler.ext@...>:
>>> >> > On Mon, 2007-06-04 at 21:27 +0800, Gav.... wrote:
>>> >> > >
>>> >> > > > -----Original Message-----
>>> >> > > > From: Vincent Siveton [mailto:vincent.siveton@...]
>>> >> > > > Sent: Monday, 4 June 2007 8:27 PM
>>> >> > > > To: dev@...
>>> >> > > > Cc: dev@...
>>> >> > > > 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: dev-unsubscribe@...
>>> >> > For additional commands, e-mail: dev-help@...
>>> >> >
>>> >> >
>>> >>
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: dev-unsubscribe@...
>>> > For additional commands, e-mail: dev-help@...
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>> For additional commands, e-mail: dev-help@...
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
>

--
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Vincent Siveton]

Hi,

2007/7/19, Dennis Lundberg <dennisl@...>:
> 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 could be a merge of both, or a
replacement (maybe in version 3.x). We need to evaluate these
possibilities.

> If so I'm in favor of bringing ForrestDoc over here, as it adds value
> over what we have today. The problem I see is that there seems to be
> other code as well in ForrestDoc. I have not looked in detail but
> references to Ant and JavaScript show up. How do we handle those?

As Ross said "Forrest is not maintaining the code", so we will free to
reorganize the code and separate Ant and JS in modules (see FOR-1028):
JXR would become a source code documentation management system.

Cheers,

Vincent

> 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 <ltheussl@...>:
> >>> 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 <vincent.siveton@...>:
> >>> >
> >>> >> 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
> >>> <thorsten.scherler.ext@...>:
> >>> >> > On Mon, 2007-06-04 at 21:27 +0800, Gav.... wrote:
> >>> >> > >
> >>> >> > > > -----Original Message-----
> >>> >> > > > From: Vincent Siveton [mailto:vincent.siveton@...]
> >>> >> > > > Sent: Monday, 4 June 2007 8:27 PM
> >>> >> > > > To: dev@...
> >>> >> > > > Cc: dev@...
> >>> >> > > > 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: dev-unsubscribe@...
> >>> >> > For additional commands, e-mail: dev-help@...
> >>> >> >
> >>> >> >
> >>> >>
> >>> >
> >>> > ---------------------------------------------------------------------
> >>> > To unsubscribe, e-mail: dev-unsubscribe@...
> >>> > For additional commands, e-mail: dev-help@...
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@...
> >>> For additional commands, e-mail: dev-help@...
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@...
> >> For additional commands, e-mail: dev-help@...
> >>
> >
> >
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[dennisl-2]

OK, then I'm in.

Vincent Siveton wrote:

> Hi,
>
> 2007/7/19, Dennis Lundberg <dennisl@...>:
>> 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 could be a merge of both, or a
> replacement (maybe in version 3.x). We need to evaluate these
> possibilities.
>
>> If so I'm in favor of bringing ForrestDoc over here, as it adds value
>> over what we have today. The problem I see is that there seems to be
>> other code as well in ForrestDoc. I have not looked in detail but
>> references to Ant and JavaScript show up. How do we handle those?
>
> As Ross said "Forrest is not maintaining the code", so we will free to
> reorganize the code and separate Ant and JS in modules (see FOR-1028):
> JXR would become a source code documentation management system.
>
> Cheers,
>
> Vincent
>
>> 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 <ltheussl@...>:
>> >>> 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 <vincent.siveton@...>:
>> >>> >
>> >>> >> 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
>> >>> <thorsten.scherler.ext@...>:
>> >>> >> > On Mon, 2007-06-04 at 21:27 +0800, Gav.... wrote:
>> >>> >> > >
>> >>> >> > > > -----Original Message-----
>> >>> >> > > > From: Vincent Siveton [mailto:vincent.siveton@...]
>> >>> >> > > > Sent: Monday, 4 June 2007 8:27 PM
>> >>> >> > > > To: dev@...
>> >>> >> > > > Cc: dev@...
>> >>> >> > > > 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: dev-unsubscribe@...
>> >>> >> > For additional commands, e-mail: dev-help@...
>> >>> >> >
>> >>> >> >
>> >>> >>
>> >>> >
>> >>> >
>> ---------------------------------------------------------------------
>> >>> > To unsubscribe, e-mail: dev-unsubscribe@...
>> >>> > For additional commands, e-mail: dev-help@...
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: dev-unsubscribe@...
>> >>> For additional commands, e-mail: dev-help@...
>> >>>
>> >>>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@...
>> >> For additional commands, e-mail: dev-help@...
>> >>
>> >
>> >
>>
>>
>> --
>> Dennis Lundberg
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

--
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[David Crossley]

Note for the archives: Discussion continued at:
 Re: [Proposal] decide the future of forrestdoc
 http://marc.info/?t=118413398900001

-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
>
> 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
>
> Thorsten Scherler wrote:
> >Gav.... wrote:
> >> From: Vincent Siveton
> >> >
> >> > 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.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...