Return-Path: 
 <dev-return-105130-apmail-commons-dev-archive=commons.apache.org@commons.apache.org>
Delivered-To: apmail-commons-dev-archive@www.apache.org
Received: (qmail 56289 invoked from network); 28 Sep 2007 22:55:34 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 28 Sep 2007 22:55:34 -0000
Received: (qmail 38522 invoked by uid 500); 28 Sep 2007 22:55:23 -0000
Delivered-To: apmail-commons-dev-archive@commons.apache.org
Received: (qmail 38455 invoked by uid 500); 28 Sep 2007 22:55:23 -0000
Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@commons.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@commons.apache.org>
List-Post: <mailto:dev@commons.apache.org>
List-Id: <dev.commons.apache.org>
Reply-To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Delivered-To: mailing list dev@commons.apache.org
Received: (qmail 38445 invoked by uid 99); 28 Sep 2007 22:55:23 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Sep 2007 15:55:23 -0700
X-ASF-Spam-Status: No, hits=1.2 required=10.0
	tests=SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Received: from [64.233.166.178] (HELO py-out-1112.google.com) (64.233.166.178)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Sep 2007 22:55:22 +0000
Received: by py-out-1112.google.com with SMTP id u52so2334548pyb
        for <dev@commons.apache.org>; Fri, 28 Sep 2007 15:54:59 -0700 (PDT)
Received: by 10.65.93.19 with SMTP id v19mr8834494qbl.1191020098833;
        Fri, 28 Sep 2007 15:54:58 -0700 (PDT)
Received: by 10.142.79.2 with HTTP; Fri, 28 Sep 2007 15:54:58 -0700 (PDT)
Message-ID: <f2e8eedf0709281554t4cc74746v1e9dadf6dbc94a6a@mail.gmail.com>
Date: Fri, 28 Sep 2007 18:54:58 -0400
From: "James Carman" <james@carmanconsulting.com>
Sender: jcarman@carmanconsulting.com
To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Subject: Re: [proxy] Cutting a release...
In-Reply-To: <46FD7A63.4070104@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <f2e8eedf0709280345j56c37ef2g7ab8a8bbe35d23f6@mail.gmail.com>
	 <46FD55EC.7020309@j-hohwiller.de>
	 <6185d22e0709281238h464fc66cy4a2aeaf87c21e2f@mail.gmail.com>
	 <f2e8eedf0709281443m1260b3dree71b7c13a1fdf83@mail.gmail.com>
	 <46FD7A63.4070104@apache.org>
X-Google-Sender-Auth: 86d828eaf852d05d
X-Virus-Checked: Checked by ClamAV on apache.org

Ok, then I'll change mine to optional.  Thanks for the clarification, Denni=
s.

On 9/28/07, Dennis Lundberg <dennisl@apache.org> wrote:
> Optional means that you can use the product without these dependencies
> present. Take commons-logging as an example. It has optional
> dependencies on log4j and the other logging implementations. In the real
> world though it will only use one of these. So they are optional.
>
> Provided means that that dependency will be provided by the target
> environment. A good example of this is the servlet-api, which will be
> provided by the servlet container.
>
> James Carman wrote:
> > The dependencies are truly optional.  I marked them as provided so
> > that they wouldn't get picked up transitively (as you stated) by
> > client projects.  If they want to use the pieces of commons-proxy that
> > need those extra libs, then they can explicitly add them to their POM.
> >  So, does that mean I should be using optional rather than provided?
> >
> > On 9/28/07, Ben Speakmon <bspeakmon@apache.org> wrote:
> >> Using <scope>provided</scope> doesn't tell maven to ignore the depende=
ncy,
> >> it just means that it's expected that the user will install it into hi=
s
> >> local repository himself or that it will be on the same classloader as=
 the
> >> application when it's running. maven will still complain if it can't f=
ind
> >> it.
> >>
> >> Optional dependencies are available from the repository, but not downl=
oaded
> >> unless specifically requested in the POM.
> >>
> >> Projects with optional dependencies where client code doesn't call the=
m are
> >> supposed to not break when the optionals are missing. Several projects
> >> happily violate this rule, but I think we should hold ourselves to a h=
igher
> >> standard :)
> >>
> >> On 9/28/07, Joerg Hohwiller <joerg@j-hohwiller.de> wrote:
> >>> -----BEGIN PGP SIGNED MESSAGE-----
> >>> Hash: SHA1
> >>>
> >>> James Carman wrote:
> >>>> All,
> >>> Hi James,
> >>>> It's been a while since Commons Proxy has had any attention, but I
> >>>> have received two emails in the past two days about it.  So, I would
> >>>> like to cut a 1.0 release for it.
> >>> A 1.0 would be excellent. I am also still hoping this project will co=
me
> >>> out of
> >>> sandbox. The problem seems to be that the apache foundation started t=
o
> >>> only put projects out on the official places if there is a "healty
> >>> community".
> >>> However commons-proxy is a lib with a tight focus and already does wh=
at is
> >>> needs
> >>> to do. There are no great new features to discuss.
> >>> In my opinion we should bring out a 1.0 that is well tested
> >>> and then I personally do NOT see why it should remain in sandbox.
> >>>
> >>> Can someone give a reason against?
> >>>
> >>> Should otherwise the project start to add various of other utilities
> >>> into commons-proxy only in order that the community grows, bugs are m=
ade
> >>> and
> >>> fixed, etc.?
> >>>
> >>> If I look at maven2 -what is an excellent tool- and the
> >>> dependency-management
> >>> it introduces, then I see that if I depend on axis2, I also depend on
> >>> commons-fileupload, commons-httpclient and on commons-logging and
> >>> therefore on
> >>> avalon-framework, junit, logkit, etc. etc. So my client needs JUnit o=
r
> >>> avalon to
> >>> talk SOAP?
> >>>
> >>> Maven2 is right with the way it goes. But projects have to focus more=
 on
> >>> specific issues. This is exactly what commons-proxy does.
> >>>
> >>> BTW: I have seen that commons-proxy is declaring its dependencies wit=
h the
> >>> scope
> >>> "provided" what prevents from the problem noted above with the transi=
tive
> >>> dependencies. Maybe you should have a chat with the maven guyz if it
> >>> should be
> >>> <optional>true</optional> instead. Do you know the difference? I can =
not
> >>> remember right now...
> >>>
> >>>> I know I need to do a little work,
> >>>> since the site is a bit out-dated (the SVN links are incorrect) from
> >>>> the TLP move.  Were there any more objections to anything fundamenta=
l
> >>>> with Proxy?  I believe my last release candidate failed because of
> >>>> some signature problems or something.  I can't remember.
> >>>>
> >>>> James
> >>> Regards
> >>>   J=F6rg
> >>> -----BEGIN PGP SIGNATURE-----
> >>> Version: GnuPG v1.4.5 (GNU/Linux)
> >>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> >>>
> >>> iD8DBQFG/VXsmPuec2Dcv/8RAgBIAKCPSUsAOR+UcEN1kwIkMzEk/n2BqQCdFSZ3
> >>> 4JVYZ352nRGIbO4a27q9u/w=3D
> >>> =3DlB27
> >>> -----END PGP SIGNATURE-----
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >>> For additional commands, e-mail: dev-help@commons.apache.org
> >>>
> >>>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
>
> --
> Dennis Lundberg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

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