commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james_strac...@yahoo.co.uk>
Subject Re: [jelly] enhanced new tag, and maven repo update needed (was cvs commit: jakarta-commons-sandbox/jelly/...)
Date Thu, 28 Nov 2002 08:36:20 GMT
From: "Rodney Waldhoff" <rwaldhoff@apache.org>
> This commit extends the core:new tag slightly to add support for invoking
> constructors that take arguments (see the commit msg and test cases for
> details).

Great stuff! I was just thinking yesterday of how it'd be nice to be able to
easily instantiate objects (like java.io.File instances) easily from <j:new>
or <j:useBean/>

> This functionality depends upon the new ConstructorUtils class
> added to commons-beanutils earlier this week (this appears in the 27 Nov
> nightly at least, maybe a bit sooner).  I guess this means the
> beanutils-SNAPSHOT.jar in the maven repository at ibiblio needs to be
> updated.
>
> I know I've seen this answered before, but how do I go about getting that
> snapshot jar updated?  A message to maven-user?  Do I need to subscribe to
> that list to have it go through?  Is there a way we could get maven to
> pull JARs out of the gump output or project-specific nightlies?

Right now just mailing maven-dev will do the trick. I've just updated it.
Essentially any repository administrator can just do

    maven jar:deploy-snapshot

Though I really hope that one day really soon all maven-ized projects at
Jakarta will be built nightly, have a nightly distribution put in a
canonical place and the jar added to the repository.


> If you need it working in the meantime, I simply changed the beanutils
> <version> tag to an arbitrary value and manually added the nightly build
> of beanutils to my local repository.  There may be a cleaner way, but that
> works at least.

The snapshot is updated now, so maven builds will just pick up the new
version.


> Also, on an unrelated note, I notice that the
> org.apache.commons.jelly.ant.TestJelly suite is failing (12 tests, 4
> errors), at least for me.

Wanna try it again with CVS HEAD? I found that having the
maven.junit.fork=true, which is now in project.properties, fixed this
class-loading issue. Lemme know if its still broken for you.

Thanks for a great patch Rod - I'll be using this very soon!

James
-------
http://radio.weblogs.com/0112098/

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

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


Mime
View raw message