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
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
