[
http://nagoya.apache.org/jira/browse/JELLY-168?page=comments#action_55964 ]
carsten madsen commented on JELLY-168:
--
I got jelly from the CVS rep. I only fetched the jelly module from cvs.
cvs co jakarta-commons/jelly
with:
[
http://nagoya.apache.org/jira/browse/JELLY-168?page=comments#action_55965 ]
Paul Libbrecht commented on JELLY-168:
--
Things are actually quite dark.
http://www.ibiblio.org/commons-jelly/jars/commons-jelly-SNAPSHOT.jar
supposedly the daily
Craig,
Joe Germuska (details below) was a sandbox committer for email:
developer
nameJoe Germuska/name
idgermuska/id
email[EMAIL PROTECTED]/email
/developer
Eric Pugh
-
To unsubscribe, e-mail: [EMAIL
Testing fails in JDK 1.5
Key: JELLY-169
URL: http://nagoya.apache.org/jira/browse/JELLY-169
Project: jelly
Type: Bug
Components: core / taglib.core
Versions: 1.0-beta-4
Reporter: Paul Libbrecht
Currently, running maven jar
[
http://nagoya.apache.org/jira/browse/JELLY-169?page=comments#action_55966 ]
Paul Libbrecht commented on JELLY-169:
--
Tuning up (and sorry for the pollution):
- building with JDK 1.5 is now working with Swing... I had forgotten the
DISPLAY
[
http://nagoya.apache.org/jira/browse/JELLY-168?page=comments#action_55967 ]
Paul Libbrecht commented on JELLY-168:
--
Sorry, I was too quick with my tests... I can run maven jar in jdk 1.5 once
the install-snapshot is done... I just had to have
Ok, this would do it too.
The other way would it make nicer, but you are right it is not required
absolutly. (One advantage would be that the parametrized version coulkd
use a more efficient type of string processing)
Than we should do the isXXXEnabled tests propertly. Because the most
logging
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32260.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32410.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Hi guys,
I move the gump project file from jakarta-commons-sandbox.xml to
jakarta-commons.xml. You should be notified of a success/failure later
today.
Eric
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
epugh 2004/11/29 01:58:33
Modified:email/src/test/org/apache/commons/mail/settings
EmailConfiguration.java
Log:
Revision ChangesPath
1.2 +2 -2
jakarta-commons/email/src/test/org/apache/commons/mail/settings/EmailConfiguration.java
epugh 2004/11/29 01:59:12
Modified:email/src/test/org/apache/commons/mail HtmlEmailTest.java
SendWithAttachmentsTest.java
MultiPartEmailTest.java SimpleEmailTest.java
emailproject.properties
email/xdocs
My take on this is that users of [email] are looking for a package that
simplifies the JavaMail api. And one of the big simplifing aspects is that
the Exceptions that they have to catch are minimized. Most users will
probably not care *what* the exception was, only that there *was* an
exception,
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-resources has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-ant has an issue affecting its community integration.
This
Okay 2 commons.mail exceptions sounds like an improvement. So the goal
is to minimise the catch statements the user needs to use, sound
reasonable. Throwing everything would mean 2 catches, so I can see the
value in catching once.
I'll look into a way of having a 1.4+ build option in the build
On Mon, 29 Nov 2004 10:42:08 +0100, Stefan Lützkendorf
[EMAIL PROTECTED] wrote:
Ok, this would do it too.
The other way would it make nicer, but you are right it is not required
absolutly. (One advantage would be that the parametrized version coulkd
use a more efficient type of string
Great, thanks!
Oliver
On Mon, 29 Nov 2004 10:54:01 +0100, Eric Pugh
[EMAIL PROTECTED] wrote:
Hi guys,
I move the gump project file from jakarta-commons-sandbox.xml to
jakarta-commons.xml. You should be notified of a success/failure later
today.
Eric
I've created the exceptions and I'm now working through the test cases.
If I summit a patch with the exception testing in a ExceptionTestCase
what's the likelyhood of this being patched? This isn't a question of
style its a question of maintainabilty and now, I'm faced with the
task of weeding
Simon Kitching wrote:
If each subproject has a 'tags'/'branches' directory, then doesn't it
become impossible to check out the latest source of *all* the commons
projects without ending up with a copy of every branch of that project
ever made?
You would check out the trunk for each
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32094.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
I would prefer an Exception Test case per base class, especially for
the larger files. I know most of the tests I wrote, but I think that
if anything the files are too long and would be much more usable if
they were shorter and more focused. Does anyone have any objections
to gave more (but
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32094.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32094.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32094.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Hi,
I feel the same as Senor Colebourne to a large extent. Not -1, but not
a +1 either -- a true neutral 0 on this one.
When we do move, we need to make sure the relevant documentation for
potential contributors, e.g.
http://www.apache.org/dev/contributors.html, and all related pages which
My thoughts on the test cases are that they should throw exception,
and then have the exception testing separate. This would make the
cases shorter also, perhaps this is what you mean.
public void testFoo() throws Exception
{
Foo foo = new Foo();
foo.setBar(testvar);
}
For example, if
Paulo Gaspar wrote:
To complitelly avoid ambiguities, why not calling it getParentPath()
instead?
Keep it simple...
Any file-system object (file or directory) has a name and a path
to it. The simple rule is
fileNameAndPath := FilenameUtils.getFullPath( fileNameAndPath )
+
And isn't it always simpler if the name of the method perfectly explains
its functionality instead of relying on some convention?
(Ok, that is not always possible, but it IS in this case.)
Regards,
Paulo
Christoph Reck wrote:
Paulo Gaspar wrote:
To complitelly avoid ambiguities, why not calling
Humm... I typically make all my unit tests throw Exception. It reduces
the length of each test, especially when all you are doing is logging that
it failed with a fail(ex.getMessage).
However, if you are actually TESTING that an exception gets thrown:
try {
email.doSomething();
fail(should
This is exactly what I was trying to say, just not so elegantly :-)
Eg. Tests for the HtmlEmail class should be in teh HtmlEmailTest class
or is this becomes too big and you want to separate the exceptions,
then there should be two classes HtmlEmailTest (for normal test cases)
and
Eric,
If you could change the group permissions recursively on the email site
so that it can be updated by others that would be great. Afterwards,
I'll be glad to run the site generation to cleanup the existing site.
[EMAIL PROTECTED]:/www/jakarta.apache.org/commons/email ls -a -l
total 390
Okay I'll take a look tommorrow and sumbit my patch with the test
cases in with the Other test methods.
Judging from you example, you agree that unexpected exceptions should
just get thrown and that exceptions should be tested independently to
normal tests, which all sounds good to me. Or am i
Fixed -- Joe now has commit access on jakarta-commons as well.
Craig
On Mon, 29 Nov 2004 10:23:53 +0100, Eric Pugh [EMAIL PROTECTED] wrote:
Craig,
Joe Germuska (details below) was a sandbox committer for email:
developer
nameJoe Germuska/name
idgermuska/id
It's true that the svn tools aren't as good as the cvs tools yet.
However, Struts recently moved to svn and it's amazing how easy it's been
to refactor and rearrange the code base after the switch. The change has
really livened up that project. Also, I was able to use Subclipse to work
with the
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32094.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32410.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=18968.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32260.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
I have the same feelings as Stephen.
Without built-in Eclipse support, this is a pain for me to deal with. I
deal with CVS everyday for work no matter what. Dealing with SVN means
extra hoops and is a disincentive for me. Yes, playing with a new toy
would be fun but at the end of the day, I need
Mark,
I think I did the right chmod. Can you just double check?
Eric
-Original Message-
From: Mark R. Diggory [mailto:[EMAIL PROTECTED]
Sent: Monday, November 29, 2004 5:08 PM
To: Jakarta Commons Developers List
Cc: [EMAIL PROTECTED]
Subject: [email] site cleanup
Eric,
If
I've applied a stack of changes, including Mark's EmailException, to the
codebase. I don't really care much about how the unit tests look, as long
as the jcoverage keeps going up!
At this point, I think all the API changes are done, and my gut feeling is
that we should look to final testing,
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32364.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32410.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
I doubt Eclipse will ever have built-in svn support because there are
several third party plugins available. Since adding a plugin update site
is so trivial in Eclipse I wouldn't think this would be a big deal.
The plugin I use with Struts svn is http://subclipse.tigris.org/. It
works largely
luetzkendorf2004/11/29 10:28:17
Modified:transaction/src/java/org/apache/commons/transaction/util/xa
AbstractXAResource.java XidWrapper.java
transaction/src/java/org/apache/commons/transaction/file
FileResourceManager.java
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30858.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Paulo Gaspar wrote:
And isn't it always simpler if the name of the method perfectly explains
its functionality instead of relying on some convention?
That was exactly the reason for my previous email.
The function getPath() is already straightforward. Any element
in a file system has a path -
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30858.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
You'll need to change the `email` directory as well
drwxr-xr-x 8 epughjakarta 1024 Nov 25 04:21 email
thnx again,
Mark
Eric Pugh wrote:
Mark,
I think I did the right chmod. Can you just double check?
Eric
-Original Message-
From: Mark R. Diggory [mailto:[EMAIL PROTECTED]
Okay, done.. I tried ls -l email and couldn't get it, I got every
directory, but I think I did it correctly. Thanks for the handholding.
-Original Message-
From: Mark R. Diggory [mailto:[EMAIL PROTECTED]
Sent: Monday, November 29, 2004 8:24 PM
To: Jakarta Commons Developers List
On 29 Nov 2004, at 14:15, Shapira, Yoav wrote:
Hi,
I feel the same as Senor Colebourne to a large extent. Not -1, but not
a +1 either -- a true neutral 0 on this one.
When we do move, we need to make sure the relevant documentation for
potential contributors, e.g.
Hi,
I agree it's not a huge effort. I was (am) just saying it's a
prerequisite.
Yoav Shapira http://www.yoavshapira.com
-Original Message-
From: robert burrell donkin
[mailto:[EMAIL PROTECTED]
Sent: Monday, November 29, 2004 3:15 PM
To: Jakarta Commons Developers List
Subject: Re:
I doubt Eclipse will ever have built-in svn support because there are
several third party plugins available. Since adding a plugin
update site
is so trivial in Eclipse I wouldn't think this would be a big deal.
The plugin I use with Struts svn is http://subclipse.tigris.org/. It
works
On Tue, 30 Nov 2004 09:31:25 +1300, Sharples, Colin
[EMAIL PROTECTED] wrote:
I doubt Eclipse will ever have built-in svn support because there are
several third party plugins available. Since adding a plugin
update site
is so trivial in Eclipse I wouldn't think this would be a big deal.
This looks like a lot of tiresome work, thanks for doing it :)
Oliver
On 29 Nov 2004 18:28:17 -, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
luetzkendorf2004/11/29 10:28:17
Modified:transaction/src/java/org/apache/commons/transaction/util/xa
[ http://nagoya.apache.org/jira/browse/JELLY-169?page=history ]
dion gillard resolved JELLY-169:
Resolution: Duplicate
Fix Version: 1.0
Dupe of JELLY-166
Testing fails in JDK 1.5
Key: JELLY-169
[
http://nagoya.apache.org/jira/browse/JELLY-169?page=comments#action_55998 ]
dion gillard commented on JELLY-169:
Which version of Maven are you using.
This sounds awfully like a bug I reported which has only surfaced on Maven
1.1-SNAPSHOT so
[
http://nagoya.apache.org/jira/browse/JELLY-169?page=comments#action_56002 ]
Paul Libbrecht commented on JELLY-169:
--
The maven versions were 1.0 and 1.0.1, for me... nothing fancy in there.
paul
Testing fails in JDK 1.5
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32350.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32350.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Ah! Now I understand your reasoning. (Had to reread your previous email
too.)
This seems to be a simple issue of terminology. And I already had that
same problem: it is hard to choose an unambigous terminology because
sometimes people call path of an item to the full name of the directory
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32350.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Ok, the plan is to add a new collapsed menu item to the jelly home
page called Tag Reference which will contain all the tags as items
underneath it.
For each tag, there will be a page similar to the ant task page with:
- description
- attributes
- nested elements (if needed)
- examples.
Have a
I like it. Could the list of tags also appear on the overview page?
-Original Message-
From: Dion Gillard [mailto:[EMAIL PROTECTED]
Sent: Monday, November 29, 2004 6:54 PM
To: dan tran; Jakarta Commons Developers List
Subject: [jelly] documentation on all tags
Ok, the plan is to add a
It's a really long list. I'd be happier if it was in one place only.
Or did you have some way of summarising it or shortening it?
On Mon, 29 Nov 2004 19:31:26 -0500, Hans Gilde
[EMAIL PROTECTED] wrote:
I like it. Could the list of tags also appear on the overview page?
-Original
skitching2004/11/29 18:25:20
jakarta-commons/digester/src/examples/api/dbinsert - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
skitching2004/11/29 18:27:01
Modified:digester/src/examples/api readme.txt
Log:
Added info on new dbinsert example. Also added missing document-markup
example.
Revision ChangesPath
1.4 +3 -1 jakarta-commons/digester/src/examples/api/readme.txt
Index:
skitching2004/11/29 18:38:24
Added: digester/src/examples/api/dbinsert Main.java Row.java
RowInserterRule.java Table.java build.xml
example.xml readme.txt
Log:
Added examples, inspired by Michael Schuerig.
Revision Changes
skitching2004/11/29 18:57:17
Modified:digester/src/java/org/apache/commons/digester package.html
Log:
Added information about using digester as a sax event handler.
Revision ChangesPath
1.33 +12 -1
skitching2004/11/29 19:06:27
Modified:digester/src/java/org/apache/commons/digester
SetPropertyRule.java
Log:
Added comment only (re PropertyUtils.isWriteable).
Revision ChangesPath
1.19 +4 -1
skitching2004/11/29 19:08:55
Modified:digester/src/java/org/apache/commons/digester
CallMethodRule.java CallParamRule.java
Log:
Added comments only, re behaviour when passing body of element and the
element is empty (empty string passed, not null).
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32441.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Sounds good to me, I have a stack of things waiting for the next version.
Also I think most of the bugs have been cleared off by your recent
commits so there shouldnt be any reason to stop us from a RC1
-Corey
On Mon, 29 Nov 2004 19:01:00 +0100, Eric Pugh [EMAIL PROTECTED] wrote:
I've
+1
Brent Worden
-Original Message-
From: Phil Steitz [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 27, 2004 10:32 AM
To: Jakarta Commons Developers List
Subject: [vote][math] Release Math 1.0
There have been no bug reports against commons-math-1.0-RC2,
which has been
skitching2004/11/29 20:36:46
Modified:digester/src/test/org/apache/commons/digester
SetNestedPropertiesRuleTestCase.java
Log:
Added test case for bugzilla#31393, reported by James Pine.
SetNestedPropertiesRule fails when invoked re-entrantly.
Revision
skitching2004/11/29 20:40:54
Modified:digester/src/java/org/apache/commons/digester
SetNestedPropertiesRule.java
Log:
Fix for bugzilla #31393, reported by James Pine. SetNestedPropertiesRule
failed when executed re-entrantly; removed over-zealous
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31393.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
dion2004/11/29 21:01:09
jakarta-commons/jelly/xdocs/tag-reference - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
dion2004/11/29 21:01:13
Added: jelly/xdocs/tag-reference ant_setProperty.xml ant_ant.xml
index.xml ant_fileScanner.xml template.xml
Log:
Add initial tag ref prototype
Revision ChangesPath
1.1
dion2004/11/29 21:01:57
Modified:jelly/xdocs navigation.xml
Log:
Add initial tag ref prototype
Revision ChangesPath
1.27 +411 -1jakarta-commons/jelly/xdocs/navigation.xml
Index: navigation.xml
dion2004/11/29 21:03:33
Modified:jelly/xdocs/tag-reference index.xml
Log:
add simple statement about list
Revision ChangesPath
1.2 +4 -0 jakarta-commons/jelly/xdocs/tag-reference/index.xml
Index: index.xml
dion2004/11/29 21:13:21
Added: jelly/xdocs/tag-reference example.xml
Removed: jelly/xdocs/tag-reference template.xml
Log:
xdoc doesn't like template.xml
Revision ChangesPath
1.1 jakarta-commons/jelly/xdocs/tag-reference/example.xml
dion2004/11/29 21:13:29
Modified:jelly/xdocs navigation.xml
Log:
xdoc doesn't like template.xml
Revision ChangesPath
1.28 +200 -200 jakarta-commons/jelly/xdocs/navigation.xml
Index: navigation.xml
dion2004/11/29 21:14:30
Modified:jelly/xdocs navigation.xml
Log:
Remove dupe
Revision ChangesPath
1.29 +0 -205jakarta-commons/jelly/xdocs/navigation.xml
Index: navigation.xml
===
RCS
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-antlr has an issue affecting its community
integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-http has an issue affecting its community
integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-swing has an issue affecting its community
integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-email has an issue affecting its community
integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-interaction has an issue affecting its community
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-swt has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-id has an issue affecting its community integration.
This issue affects
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-junit has an issue affecting its community
integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-log has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-betwixt has an issue affecting its community
integration.
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-dynabean has an issue affecting its community
integration.
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-jetty has an issue affecting its community
integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-sql has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-util has an issue affecting its community
integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-bean has an issue affecting its community
integration.
This
1 - 100 of 125 matches
Mail list logo
