If you using the maven, than have you the dependencies to common-chain
and automatically dependency to servlet api. Ok, you can es excluded
with maven. But you have a code with possible Errors.
Niall Pemberton schrieb:
On Fri, May 15, 2009 at 8:28 AM, Alexander Vaysberg wrote:
Hi,
i like
On Fri, May 15, 2009 at 8:28 AM, Alexander Vaysberg wrote:
> Hi,
> i like the common-chain. That is a simple and nice. But chain in one jar has
> a problem. The chain has a dependency to servlet api. I think this not gut.
> The better was it separate to chain-core.jar (for project without servlet
> I am a new in dev group and I don't how I it's make? Can you me help with
> this?
Please read this:
http://commons.apache.org/patches.html
basically it says you should check out the component, do your mod and
then create the patch. If you use eclipse, it has some cool features
in the context me
I am a new in dev group and I don't how I it's make? Can you me help
with this?
Christian Grobmeier schrieb:
i like the common-chain. That is a simple and nice. But chain in one jar has
a problem. The chain has a dependency to servlet api. I think this not gut.
The better was it separate to chai
> i like the common-chain. That is a simple and nice. But chain in one jar has
> a problem. The chain has a dependency to servlet api. I think this not gut.
> The better was it separate to chain-core.jar (for project without servlet
> api) and chain- web.jar(for web.). And with maven module was si
Hi,
i like the common-chain. That is a simple and nice. But chain in one jar
has a problem. The chain has a dependency to servlet api. I think this
not gut. The better was it separate to chain-core.jar (for project
without servlet api) and chain- web.jar(for web.). And with maven
module was s
