Added a pull request with a first pass at moving all of this to a maven
build. builds and generates javadoc fine. Might need some more fine tuning.
On 09/29/2015 08:27 PM, Dave Brosius wrote:
Also the source code is not in the proper package structure. The
class's have packages, but are just dumped directly in src. There is
javadoc, but just dumped in the main folder. I just dump that, and
having support building the javadoc from build tools. Setting the
structure of the project up into some sane will help get people to
look at it. I'd again strongly recommend getting this into a maven
standard project format.
If you want help putting this project into a healthy state,
layout/build wise let me know, i could spare a few cycles.
--dave
On 09/29/2015 08:11 PM, Dave Brosius wrote:
Perhaps i am blind, but i don't see any maven, ant or gradle build
files. You really need to add these for your code base to be
accessible to others wanted to uptake it. (Hopefully maven).
--dave
On 09/29/2015 06:55 PM, Gary Gregory wrote:
Norman,
Hello and welcome to Apache Commons.
It's not clear to me why Naomi is better than regular expressions.
Pointing
to Javadocs is not the best way to get traction.
Your project would be better served by having some documentation on
your
front page with an example driven tutorial.
Is Naomi faster than REs?
What can I do in Naomi that REs can't do? And vice-versa.
Examples of this on your front page would help you at least get
folks to
consider learning a brand new way of doing things...
Gary
On Tue, Sep 29, 2015 at 1:06 PM, <n...@dad.org> wrote:
My colleague Jeff Rothenberg and I, retirees, have developed an
alternative to
using regular expressions for searching for (and optionally replacing)
patterns in text. We believe it is generally useful to Java
programmers and
would like to contribute it to Apache Commons, where we will
continue to be
active in maintaining the software. You can find the software and
associated
documentation at https://github.com/NormanShapiro/Naomi/tree/gh-pages.
Please let us know what further steps we should take to have our
contribution
considered.
Thank you,
Norman Shapiro
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
