At 15:32 28/01/03 -0800, Morgan Delagrange wrote:
AFAIK the build is currently stable. If you want the most recent versions of jelly and the bean taglib, you could grab them from last night's gump run:http://gump.covalent.net/jars/latest/jakarta-commons-sandbox/
Thanks - "latest" symlink seems to have evaporated, got the jars from http://gump.covalent.net/jars/2003-01-27/jakarta-commons-sandbox/ Great - just what I need.
With regard to your build problem and Maven, my best guess is that either your Maven bootstrap is too old (even a week would not work, welcome to Maven)
:) I'm using a pre-built beta 7 ...
Took half an hour - appeared to be in a dependency loop where it keeps executing the [get-deps] target and downloading all the jars from ibiblio, did this 3 times. Some [ERROR] messages re XMLParser, but it runs to BUILD SUCCESSFUL and buildsor the ibiblio repository of Jelly jars is out of date. Out of date ibiblio jars would also explain your Ant problems. Here's another script you can try from the jelly directory, which will build Jelly, bean, and its dependencies from HEAD from scratch. (Let me know if it works. :) cd jelly ant -f build-all.xml clean-skiplib jar-bean
jelly/target/commons-jelly-1.0-beta-4-SNAPSHOT.jar
jelly/jelly-tags/bean/target/commons-jelly-tags-bean-1.0-SNAPSHOT.jar
which I guess is a success? Will test tomorrow.
or you can try editing your maven environment to build everything from scratch, if you prefer using Maven.
The Ant approach is fine for now - thanks.
I think (don't quote me on this) that you would need to: cd jelly maven clean jar:install-snapshot <edit maven.xml to use the jar:install-snapshot target for tags-build> maven tags-build That build will actually build ALL the tags, rather than just bean and its dependencies. - Morgan
Thanks a lot for your help, I now have *two* versions of the relevant jars. Much appreciated.
Best Regards,
Thomas.
--- Thomas Nichols <[EMAIL PROTECTED]> wrote:
> Jelly-oids,
>
> The current refactoring is causing me some
> head-scratching - am I doing
> something wrong? I'm trying to use BeanTagLibrary
> (thanks to Christian et
> al for pointers) and all was progressing well -
> except for some peculiar
> warnings when running the test suite
> src/test/org/apache/commons/jelly/bean/TestJelly
> -- from memory, [WARN] messages that Customer bean
> was not being added to a
> parent.
>
> After a cvs up -Pd (and some disk thrashing) I no
> longer have access to
> BeanTagLibrary - it seems it's now in a separate jar
> (excellent) which I am
> unable to build (less excellent).
>
> I can build CVS HEAD fine from the jelly dir with
> cvs up -Pd
> maven clean:clean
> maven java:jar
>
> But building the Bean jar breaks for me. I tried
> cd [jellydir]/jelly-tags/bean
> maven java:compile
>
> which breaks with
>
> [ERROR] java.io.FileNotFoundException:
>
/home/thomasn/dev/jakarta-commons-sandbox/jelly/jelly-tags/bean/${basedir}/../tag-project.xml
>
> (No such file or directory)
>
> Running 'ant' in this dir downloads a bunch of
> support jars, then throws a
> compiler error (Uncaught exception,
> BeanPropertyTag.java:129) which looks
> very odd to me, the exception handling looks OK.
>
> I've also tried maven tags-build without success.
>
> What else can I try? BeanTags are exactly what I was
> looking for, is Jelly
> in such a state of flux that I should hold off
> developing to it until the
> API is more stable, or am I doing something very
> wrong? Would I be better
> with a binary distro until the refactoring is
> complete?
>
> Thanks,
> Thomas.
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
=====
Morgan Delagrange
http://jakarta.apache.org/taglibs
http://jakarta.apache.org/commons
http://axion.tigris.org
http://jakarta.apache.org/watchdog
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
