commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From (Jeffrey D. Brekke)
Subject [NET] Re: dependency dilemma
Date Sat, 01 Mar 2003 04:06:06 GMT


I'm replying on the commons-dev list...

"Steve Cohen" <> writes:

> I began working on incorporating my changes to commons-net and came
> fairly quickly to the first hurdle:
> Many of my changes depend on jakarta-oro which is not now included
> in the build process of the project.  In fact, I saw in one of the
> docs,, that
> commons-net depends on no other projects.  I don't know if this is
> an immutable law, and I certainly don't want to introduce circular
> dependencies, so I'm kind of stymied here.
> I suppose the build script must have been different before the
> current setup was introduced, or I/we were somehow jamming
> jakarta-oro onto the classpath.  Is it okay to introduce such a
> dependency now, and if so, what is the right way to do it?  If not,
> how else can we build regular expression parsing into the library?
> I'm sure going to jdk 1.4 is not an option.

We had the dependency in there for quite some time before we moved the
code into proposal.  You could look in cvsweb at older versions of
project.xml to add the dependency.  Basically its:


Moving the tests into src/test, maven will pull in the junit
dependency for us so we don't need to explictly list it.

Jeffrey D. Brekke                         
Wisconsin,  USA                           

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message