I figured it had something to do with Maven (of which I know nothing.)
Thanks for the concise explanation. Sorry but I won't be able to
help out on this one!
sean
On Wed, 1 Dec 2004 10:14:08 -0800, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> The build.xml scripts for Commons Email and Common
The build.xml scripts for Commons Email and Commons Chain were
generated by Maven, and include attempts to download all their
dependencies. The problem is that the email and JSF jars required by
these packages have license restrictions that prohibit them being
posted on the repository -- so the An
Greetings,
I'm just back from a long (one month) vacation to Australia. I've
been catching up on my mailing lists ...
Apparently there are the issues with the build file and JSF. I took a
look at my old copy of the source code and that was building just fine
with the RI. I'm assuming I just do
On Wed, 1 Dec 2004 14:07:20 +0800, Brett Porter <[EMAIL PROTECTED]> wrote:
> If you'd like to put together a feature request to file, I'm sure we'd be able
> to get someone to take a look.
http://jira.codehaus.org/browse/MPANT-20
Craig
Quoting Craig McClanahan <[EMAIL PROTECTED]>:
> I'm a Maven newbie, but it's not obvious to me that the proposed
> change will do what I think we need. It sounds like this change
> applies the overrides when you *generate* the build.xml file -- so the
> overrides in effect will be for those of th
On Tue, 30 Nov 2004 10:00:07 -0800, Martin Cooper <[EMAIL PROTECTED]> wrote:
> On Tue, 30 Nov 2004 00:06:52 -0800, Craig McClanahan <[EMAIL PROTECTED]>
> wrote:
> > -1
> >
> > Besides the fact that this change bundle breaks the "ant clean dist"
> > command that is necessary for the current ngihtly
I'm a Maven newbie, but it's not obvious to me that the proposed
change will do what I think we need. It sounds like this change
applies the overrides when you *generate* the build.xml file -- so the
overrides in effect will be for those of the person running the
generation.
In Commons, we've bee
Quoting Craig McClanahan <[EMAIL PROTECTED]>:
> It would be really nice if the generated build.xml produced by Maven
> would allow Ant property replacements for the paths to all the
> dependencies, instead of hard coding them, so you could just define
> your exceptions in a local build.properties
On Tue, 30 Nov 2004 20:05:16 -0800, Martin Cooper <[EMAIL PROTECTED]> wrote:
> On Tue, 30 Nov 2004 19:11:00 -0500, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
>
>
> > Eric Pugh wrote:
> > > I'd guess that the JSF jar's are not distributable on IBiblio,
> > > just like the JavaMail ones?
> >
> > Ch
On Tue, 30 Nov 2004 19:11:00 -0500, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
> Eric Pugh wrote:
> > I'd guess that the JSF jar's are not distributable on IBiblio,
> > just like the JavaMail ones?
>
> Check the license, but if it is the SBCL, then the restriction applies.
> This would be a good r
Eric Pugh wrote:
> I'd guess that the JSF jar's are not distributable on IBiblio,
> just like the JavaMail ones?
Check the license, but if it is the SBCL, then the restriction applies.
This would be a good reason to use MyFaces, of course. :-)
Martin Cooper wrote:
> One alternative, I suppose,
to:[EMAIL PROTECTED]
> > Sent: Tuesday, November 30, 2004 7:00 PM
> > To: Jakarta Commons Developers List; [EMAIL PROTECTED]
> > Subject: Re: cvs commit:
> > jakarta-commons/chain/src/java/org/apache/commons/chain/web/servlet
> > ChainProcessor.java ServletApp
ED]
> Subject: Re: cvs commit:
> jakarta-commons/chain/src/java/org/apache/commons/chain/web/servlet
> ChainProcessor.java ServletApplicationScopeMap.java
> ServletHeaderValuesMap.java ServletRequestScopeMap.java
> ServletSessionScopeMap.java
>
>
> On Tue, 30 Nov 2004 00:06:
On Tue, 30 Nov 2004 10:00:07 -0800, Martin Cooper <[EMAIL PROTECTED]> wrote:
> On Tue, 30 Nov 2004 00:06:52 -0800, Craig McClanahan <[EMAIL PROTECTED]>
> wrote:
> > -1
> >
> > Besides the fact that this change bundle breaks the "ant clean dist"
> > command that is necessary for the current ngihtly
On Tue, 30 Nov 2004 00:06:52 -0800, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> -1
>
> Besides the fact that this change bundle breaks the "ant clean dist"
> command that is necessary for the current ngihtly build scripts to
> work
I don't believe that's why the build broke. The problem is that
-1
Besides the fact that this change bundle breaks the "ant clean dist"
command that is necessary for the current ngihtly build scripts to
work, it alters the semantics with changes like this:
> Index: Catalog.java
> ===
> RCS
16 matches
Mail list logo