Re: [digester] Problem building javadoc w/ Ant on Windows
On Tue, 2005-01-18 at 08:40 +0100, Dennis Lundberg wrote: I did some digging in the mail-archives and found the thread I was talking about earlier. It can be found here: http://mail-archives.apache.org/eyebrowse/[EMAIL PROTECTED]by=threadfrom=666491 Note that eyebrowse sorts the e-mails with newest-first, so start reading from the bottom up... Let me know if there's anything I can do to help. That's very useful indeed. So escaping of quotes in the bottom text for javadoc is necessary on Windows but not on Linux or Mac. And escaping the quotes can be done with backslashes, but if you do that then those come through to the generated html page on Linux. Yecch. Well, I think I'll raise a bugzilla entry with this info, as a reminder to think about this further. But for the moment, I'm inclined to leave digester as it is, until Robert Donkin reappears and lets us know why this was added in the first place. Maybe a comment in the build.xml would be useful too... Anyone got any alternative suggestions? Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Email] To release or not to release
h..., I just set up my box. checked out [email] but build fails because of the old story regarding download of javamail I run maven jar:install I have forgotten, what to do... After all works (again) for me, I will do produce and signing the release, since I have commit priviledg. Thanks! -Original Message- From: Matthias Wessendorf [mailto:[EMAIL PROTECTED] Sent: Monday, January 17, 2005 4:20 PM To: 'Jakarta Commons Developers List'; 'Dion Gillard' Subject: RE: [Email] To release or not to release +1 -Original Message- From: Dion Gillard [mailto:[EMAIL PROTECTED] Sent: Monday, January 17, 2005 11:32 AM To: Jakarta Commons Developers List; Corey Scott Subject: Re: [Email] To release or not to release I'm +1. On Mon, 17 Jan 2005 17:12:20 +0800, Corey Scott [EMAIL PROTECTED] wrote: Can someone with commit priviledge please change email over from RC1 to v.1.0? The RC has been out for quite a while now and so far there are no complaints about this. There are several other things waiting for this release, e.g. a proposed change to the jelly email classes (change to Commons Email) and some proposed extensions to Email itself, so completing the release would be greatly appreciated. Many Thanks, Corey - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-commons/digester build.xml
skitching2005/01/18 02:04:33
Modified:digester build.xml
Log:
Add comment re javadoc target not working on MS-Windows.
Revision ChangesPath
1.57 +6 -1 jakarta-commons/digester/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-commons/digester/build.xml,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -r1.56 -r1.57
--- build.xml 20 Sep 2004 21:59:23 - 1.56
+++ build.xml 18 Jan 2005 10:04:33 - 1.57
@@ -221,6 +221,11 @@
description=Clean and compile all components/
+ !--
+- Note that this javadoc target currently does not work on MS-Windows.
+- As a temporary measure, the bottom attribute can be removed when
+- building on that platform.
+--
target name=javadoc depends=compile
description=Create component Javadoc documentation
mkdir dir=${dist.home}/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (JELLY-175) patch for jelly-tags-interaction
[ http://issues.apache.org/jira/browse/JELLY-175?page=comments#action_57712 ] Brett Porter commented on JELLY-175: I've contacted the author, as the docs suggest that he is open to other licensing. The project hasn't been touched in a year and a half, so we'll see. Hopefully he is still around and interested in opening up the license a little so it can be included. patch for jelly-tags-interaction Key: JELLY-175 URL: http://issues.apache.org/jira/browse/JELLY-175 Project: jelly Type: Improvement Environment: I've tested this in windows with and without cygwin. Reporter: Ryan Christanson Priority: Minor Attachments: patch.txt I've attached a patch to the commons-jelly-tags-interaction jar. This patch makes it so the interaction task will try to use jline: http://jline.sourceforge.net/ Jline makes it so a java console will have tab completion, and history, and other goodies. This is great, because the maven-console plugin uses the commons-jelly-tags-interaction jar. So if you update the commons-jelly-tags-interaction jar, and then tell the maven console plugin to use the new jar, then your maven console will have history, and tab completion. I've set it up to remember all of the commands typed in any console, further it uses that history as the tab completion source - so you can tab complete past commands. I've tested this in windows and it works great, but in windows with cygwin, it doesn't do the fancy completion, but still works. By the way, in windows, jline's lib doesn't support arrows for history, so use CONTROL+P and CONTROL+N. Its possible that there might be a better way to integrate jline into this lib, i've just done what looked like the quickest way to get it working so my maven console would have history and tab completion. Maybe this feature could be enabled with a tag attribute? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32441] - [dbcp] SQLException When PoolablePreparedStatement Already Closed
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. http://issues.apache.org/bugzilla/show_bug.cgi?id=32441 [EMAIL PROTECTED] changed: What|Removed |Added Severity|minor |major --- Additional Comments From [EMAIL PROTECTED] 2005-01-18 15:40 --- Note this is realated to 23185. Same type of problem. This is with prepared statements, that with Connections. In both cases, the general contract says they should be close()-able multiple times. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23185] - [dbcp] PoolableConnection.close() won't allow multiple close
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=23185. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=23185 --- Additional Comments From [EMAIL PROTECTED] 2005-01-18 15:42 --- Note this is also related to 32441 - that one refers to the same problem with PoolablePreparedStatements. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Email] To release or not to release
At 10:04 AM +0100 1/18/05, Matthias Wessendorf wrote: h..., I just set up my box. checked out [email] but build fails because of the old story regarding download of javamail I run maven jar:install I have forgotten, what to do... After all works (again) for me, I will do produce and signing the release, since I have commit priviledg. You need to do one of two things: 1) manually install the JARs where Maven wants them: $MAVEN_LOCAL_REPO/javamail/jars/javamail-1.3.2.jar $MAVEN_LOCAL_REPO/activation/jars/activation-1.0.2.jar 2) indicate with Maven properties that you want to override those specifications. You can do this on the command line with -D, but I prefer to use a build.properties file in the project directory. It would look something like this: maven.jar.override=on maven.jar.javamail=/path/to/javamail.jar maven.jar.activation=/path/to/activation.jar (You can also specify simply a version number in the value to the override properties, if the jars are in your Maven repository. details at http://maven.apache.org/reference/user-guide.html#Overriding_Stated_Dependencies) Joe Thanks! -Original Message- From: Matthias Wessendorf [mailto:[EMAIL PROTECTED] Sent: Monday, January 17, 2005 4:20 PM To: 'Jakarta Commons Developers List'; 'Dion Gillard' Subject: RE: [Email] To release or not to release +1 -Original Message- From: Dion Gillard [mailto:[EMAIL PROTECTED] Sent: Monday, January 17, 2005 11:32 AM To: Jakarta Commons Developers List; Corey Scott Subject: Re: [Email] To release or not to release I'm +1. On Mon, 17 Jan 2005 17:12:20 +0800, Corey Scott [EMAIL PROTECTED] wrote: Can someone with commit priviledge please change email over from RC1 to v.1.0? The RC has been out for quite a while now and so far there are no complaints about this. There are several other things waiting for this release, e.g. a proposed change to the jelly email classes (change to Commons Email) and some proposed extensions to Email itself, so completing the release would be greatly appreciated. Many Thanks, Corey - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com Narrow minds are weapons made for mass destruction -The Ex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 33154] New: - jsvc assumes posix capabilities loaded
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=33154. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=33154 Summary: jsvc assumes posix capabilities loaded Product: Commons Version: unspecified Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Daemon AssignedTo: commons-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] later versions of linux (e.g. 2.6.x) may have capability management configured as a module rather than compiled in. A LKML discussion is ongoing as to if this is a good idea or not, but the upshot is that jsvc will fail on capset if the kernel doesn't have the module loaded. I'd suggest a note in the release notes and/or linux faq section discussing the issue. I'd be happy to propose a doc patch -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 33154] - [daemon] jsvc assumes posix capabilities loaded
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=33154. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=33154 [EMAIL PROTECTED] changed: What|Removed |Added Summary|jsvc assumes posix |[daemon] jsvc assumes posix |capabilities loaded |capabilities loaded -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-commons-sandbox/feedparser/src/java/org/apache/commons/feedparser/locate AnchorParser.java DiscoveryLocator.java EntityDecoder.java FeedLocator.java ProbeLocator.java
burton 2005/01/18 11:39:36
Modified:feedparser build.xml
feedparser/src/java/org/apache/commons/feedparser/locate
AnchorParser.java DiscoveryLocator.java
EntityDecoder.java FeedLocator.java
ProbeLocator.java
Log:
Fixed major bug in our anchor parser that would actually cause the page stop
being parsed
Revision ChangesPath
1.11 +4 -0 jakarta-commons-sandbox/feedparser/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-commons-sandbox/feedparser/build.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- build.xml 22 Oct 2004 00:37:08 - 1.10
+++ build.xml 18 Jan 2005 19:39:36 - 1.11
@@ -119,7 +119,9 @@
classname=org.apache.commons.feedparser.locate.TestFeedLocator
fork=true
failonerror=true
+
sysproperty key=feedparser.home value=${feedparser.home}/
+
/java
/target
@@ -131,7 +133,9 @@
classname=org.apache.commons.feedparser.test.TestProbeLocator
fork=true
failonerror=true
+
sysproperty key=feedparser.home value=${feedparser.home}/
+
/java
/target
1.6 +50 -8
jakarta-commons-sandbox/feedparser/src/java/org/apache/commons/feedparser/locate/AnchorParser.java
Index: AnchorParser.java
===
RCS file:
/home/cvs/jakarta-commons-sandbox/feedparser/src/java/org/apache/commons/feedparser/locate/AnchorParser.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- AnchorParser.java 29 Dec 2004 02:18:21 - 1.5
+++ AnchorParser.java 18 Jan 2005 19:39:36 - 1.6
@@ -22,7 +22,8 @@
/**
*
- * Given HTML pull out an array of anchors
+ * Given a string of HTML content, parse out anchors and fire events with all
+ * the data when they are found.
*
* @author a href=mailto:[EMAIL PROTECTED]Kevin A. Burton/a
*/
@@ -51,26 +52,67 @@
int index = 0;
-//FIXME: what if href isn't the first attribute? It will fail
here...
+//FIXME: what if href isn't the first attribute? Will it fail
here???
+
+//FIXME: how do we pass back the content of the href: a href=''
this
+//is the content /a which would pass a string this is the content
Matcher m = pattern.matcher( content );
-LinkedList list = new LinkedList();
-
while ( m.find() ) {
-//expand this link
+HashMap map = DiscoveryLocator.getAttributes( m.group( 0 ) );
String resource = EntityDecoder.decode( m.group( 1 ) );
-String title = EntityDecoder.decode( m.group( 2 ).trim() );
+//String title = EntityDecoder.decode( m.group( 2 ).trim() );
+String title = (String)map.get( title );
+
+if ( title != null ) {
+title = title.trim();
+title = EntityDecoder.decode( title );
+}
+
+String rel = (String)map.get( rel );
+
if ( resource == null || resource.equals( ) )
-return;
+continue;
-if ( ! listener.onAnchor( resource, null, title ) )
+if ( ! listener.onAnchor( resource, rel, title ) )
return;
}
+
+}
+
+public static void main( String[] args ) throws Exception {
+
+AnchorParserListener listener = new AnchorParserListener() {
+
+public boolean onAnchor( String href, String rel, String
title ) {
+
+System.out.println( href: + href );
+System.out.println( rel: + rel );
+System.out.println( title: + title );
+return true;
+}
+
+public Object getResult() {
+return null;
+}
+public void setContext( Object context ) {}
+
+};
+
+//FIXME: won't work with single quotes
+//FIXME: won't work with a /
+//parse( a href=\http://peerfear.org\; rel=\linux\
title=\linux\ adf/a, listener );
+
+//parse( a rel=\linux\ href=\http://peerfear.org\;
title=\linux\ adf/a, listener );
+//parse( a title=\linux\ rel=\linux\
href=\http://peerfear.org\; adf/a, listener );
+
+parse( a href='http://peerfear.org' rel='linux' title='linux'
adf/a, listener );
+
}
1.14 +2 -2
[jelly] the .project and .classpath files
Hey, does anyone use the .project or .classpath files in the Jelly directory? How do you substitute the MAVEN_REPO variable in the paths? Hans
Re: [jelly] the .project and .classpath files
Hans Gilde wrote: Hey, does anyone use the .project or .classpath files in the Jelly directory? No How do you substitute the MAVEN_REPO variable in the paths? If I what I remember still serves, you set a path variable MAVEN_REPO in your Eclipse configuration (in the dependencies section). Sorry, I can't point you to anything directly. - Brett Hans - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Commons Wiki] New: SigningReleases
(bit late on this thread) FWIW i'd say that the right approach would be to start by supporting BouncyCastles. i've noticed that most folks just want a simple set of instructions (something which is pretty difficult when dealing with code signing). it'd probably pay to go for a single, simple system that can be explained in detail. those with more experience who already have a preference for GPG or PGP should be capable of importing their code signing keys into bouncy castle. - robert On 7 Jan 2005, at 18:14, Mark R. Diggory wrote: Thats one of the major reasons I stalled in development of it. It's very platform/application specific in that case. Either force the Ant task to be using only BouncyCastle and have everyone import their keys into BouncyCastles config, or allow users to configure which application was doing the signing and call the application externally. Which would be logical in that the Ant task would be generic and there would be build.properties the user could define to establish which implementation did the signing. -Mark Martin Cooper wrote: On Fri, 07 Jan 2005 12:47:06 -0500, Mark R. Diggory [EMAIL PROTECTED] wrote: I've been lurking on this discussion. +1 PGP Signing files needs to be just like the current md5 signing that maven supplies on artifacts. You should be able to supply signing Keys and get artifacts signed. The catch to this is that different people use different tools to do the signing. Some people use PGP, others use GPG, people have different versions. It's not clear to me that you'd be able to get everyone to use the same tool. -- Martin Cooper I initially was working on libraries to do this in Ant/Maven using BouncyCastle. But alas, time and money has me unable to contribute. I highly recommend having this be a task in Ant that Maven can also take advantage of, this way it can also be included into the generate build.xml files that projects may use for also building releases. -Mark robert burrell donkin wrote: AIUI there some work underway on this over in mavenland. hopefully brett will jump now with a progress report and tasks which are still needed volunteers... - robert On 6 Jan 2005, at 20:53, Rory Winston wrote: +1 Tim O'Brien wrote: -Original Message- From: Phil Steitz [mailto:[EMAIL PROTECTED] 2) A real maven expert (Brett ;) could probably figure out how to automate almost everything in a way that could be reused across all maven-built projects. Including the signing, hashing and verification in the maven build would be great. I agree with Robert that this probably belongs in the maven community. I am willing to help in any case, either working on plugins to get things to work or documenting how to use maven to cut releases. Ah, a release plugin that would be a good thing! -- --- 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Mark Diggory Software Developer Harvard MIT Data Center http://www.hmdc.harvard.edu - 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] -- Mark Diggory Software Developer Harvard MIT Data Center http://www.hmdc.harvard.edu - 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]
[jira] Created: (JELLY-196) SwitchTag can not be reused if default encountered
SwitchTag can not be reused if default encountered
--
Key: JELLY-196
URL: http://issues.apache.org/jira/browse/JELLY-196
Project: jelly
Type: Bug
Components: core / taglib.core
Versions: 1.0
Environment: 1.0-RC2-SNAPSHOT
Reporter: Marc DeXeT
Script as
j:forEach var=var items=a,b
j:switch on=${var}
j:case value=unencountered1
j:set var=res value=1/
/j:case
j:case value=unencountered2
j:set var=res value=2/
/j:case
j:default
j:set var=res value=default/
/j:default
/j:switch
/j:forEach
throws default should be the last tag within a switch because of
SwitchTag boolean property defaultEncountered is not reset.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[launcher] prepare for 1.2
Hi all, A couple of days ago I committed some launcher fixes/enhancements and will be releasing 1.2 in a week or two. If anyone has some patches laying around, now is the time to submit them :-) Cheers Dirk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (JELLY-196) SwitchTag can not be reused if default encountered
[ http://issues.apache.org/jira/browse/JELLY-196?page=history ]
Marc DeXeT updated JELLY-196:
-
Attachment: patch_2005.01.18_switchTag.txt
SwitchTag can not be reused if default encountered
--
Key: JELLY-196
URL: http://issues.apache.org/jira/browse/JELLY-196
Project: jelly
Type: Bug
Components: core / taglib.core
Versions: 1.0
Environment: 1.0-RC2-SNAPSHOT
Reporter: Marc DeXeT
Attachments: patch_2005.01.18_switchTag.test.txt,
patch_2005.01.18_switchTag.txt
Script as
j:forEach var=var items=a,b
j:switch on=${var}
j:case value=unencountered1
j:set var=res value=1/
/j:case
j:case value=unencountered2
j:set var=res value=2/
/j:case
j:default
j:set var=res value=default/
/j:default
/j:switch
/j:forEach
throws default should be the last tag within a switch because of
SwitchTag boolean property defaultEncountered is not reset.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (JELLY-196) SwitchTag can not be reused if default encountered
[ http://issues.apache.org/jira/browse/JELLY-196?page=history ]
Marc DeXeT updated JELLY-196:
-
Attachment: patch_2005.01.18_switchTag.test.txt
SwitchTag can not be reused if default encountered
--
Key: JELLY-196
URL: http://issues.apache.org/jira/browse/JELLY-196
Project: jelly
Type: Bug
Components: core / taglib.core
Versions: 1.0
Environment: 1.0-RC2-SNAPSHOT
Reporter: Marc DeXeT
Attachments: patch_2005.01.18_switchTag.test.txt,
patch_2005.01.18_switchTag.txt
Script as
j:forEach var=var items=a,b
j:switch on=${var}
j:case value=unencountered1
j:set var=res value=1/
/j:case
j:case value=unencountered2
j:set var=res value=2/
/j:case
j:default
j:set var=res value=default/
/j:default
/j:switch
/j:forEach
throws default should be the last tag within a switch because of
SwitchTag boolean property defaultEncountered is not reset.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dbcp] Wait forever when get Ceonnction from data source
Paul,
The problem is that you cannot safely interrupt the network
communication that's going on inside the driver. If the driver doesn't
expose the network layer timeout then you're stuck.
The only thing you can do is doing the driver.getConnection() in a
separate thread and then your application thread can continue if no
connection becomes available before the pool timeout.
If you are willing to experiment with this then I can give you some
pointers. When you/we find a solution then it will be included into
the official release. (that's the apache way)
So we need a seperate thread creating connections. Luckely this thread
already exists. The evictor thread allocates new connections when
needed. Set the timeBetweenEvictionRunsMillis property to start the
thread. Using the minIdle property you can set the minimum number of
connections that should be available in the pool.
The last thing is to disable the creation of new connections when an
application thread borrows a connection from the pool (and the pool is
empty). Unfortunally there isn't a configuration setting for this yet.
You will have to change commons-pool.
Create an extra property boolean autoCreate;
and change the following line in GenericObjectPool
http://jakarta.apache.org/commons/pool/xref/org/apache/commons/pool/impl/GenericObjectPool.html#789
if(_maxActive 0 || _numActive _maxActive) {
to
if (autoCreate (_maxActive 0 || _numActive _maxActive)) {
In your case you set autoCreate to false and the application threads
will wait until the background thread has created a connection (or
another application thread returned one back into the pool).
The maxWait still applies.
http://jakarta.apache.org/commons/pool/xref/org/apache/commons/pool/impl/GenericObjectPool.html#799
The maxWait property is the connection timeout you needed.
Hope this helps, please report back the results of this experiment.
Cheers
Dirk
Paul Hsu wrote:
Dirk,
Thank you for help. So you think there is no way we can ask DBCP to
abandon long waiting connection request via jdbc/odbc driver? But if
the odbc driver does not provide the property to set up the connection
time out, it is better for DBCP to support. I think it will nice if
Jakata DBCP project can implement this. I write a time out java program
to abandon the connection request in certain period, but it is even
better if DBCP project team can add this to project.
BTW, I thought that the maxWait is the max waiting time of a client can
borrow the connection from pool before return.
Paul
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [jelly] the .project and .classpath files
Windows - Preferences... Then in the tree menu of configuration panels, choose: Java - Build Path - Classpath Variables Create a new variable MAVEN_REPO, point it at ~/.maven/repository Tim O'Brien [EMAIL PROTECTED] -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] How do you substitute the MAVEN_REPO variable in the paths? If I what I remember still serves, you set a path variable MAVEN_REPO in your Eclipse configuration (in the dependencies section). Sorry, I can't point you to anything directly. - Brett Hans - 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]
BeanUtilsBean setProperty conversion not allowing String[] to Object
I'm having a hard time understanding the philosophy behind
org.apache.commons.beanutils.BeanUtilsBean's
setProperty(Object bean, String name, Object value) method. There seems to
be a design decision to eliminate
the inheritance of arrays from Object. I looked through bugzilla on
issues.appache.org and found id=16525 and 32874 interesting and somewhat
related but I guess I still don't get it.
Here is the background:
I'm using commons-beanutils-1.7.0 in a Struts 1.2.x application.
My program has the following form (bean):
public class MyForm extends ActionForm{
Object o = null;
public void setObject(Object toSet){
o = toSet;
}
public Object getObject(){
return o;
}
Given that an array is an Object, you should be able to:
String t = test;
String[] sa = {t,t};
MyForm myForm = new MyForm();
HashMap map = new HashMap(1);
map.put(object,sa);
BeanUtils.populate(myForm,map);
//myForm.setObject(sa); // cause this line works
you then should be able to successfully compile and execute:
String[] sa2 = (String[])myForm.getObject();
assert(sa[0].equals(t));
assert(sa[1].equals(t));
Instead I'm getting no sa[1] from getObject() and o is now a simple String
with value test.
My discovery:
BeanUtilsBean.setProperty reflects the myForm.setObject method and assumes
property Object is scalar;
which is an invalid assumption as Object could be an array. It appears that
setProperty then
converts the sa String array to a simple String using the first element
of the array (hardcoded 0) and
drops the rest of the array. This is lossy at best and quietly violates
data-in equals data-out.
This lossy behavior can be traced to lines 1003-1005 in BeanUtilsBean's
setProperty method as follows:
} else if (value instanceof String[]) {
newValue = getConvertUtils().convert(((String[]) value)[0],
type);
Again, the above code appears to render invalid the inheritance of arrays
from Object and precludes me from writing a Converter for String[] to
Object.
Suggested fix:
BeanUtilsBean.setProperty should reflect the named property's set method
and check if sa (the String[] argument) is
an instanceof Object (the set method's parameter type) and simply pass the
array into the set method unchanged.
What would be the impact of changing line 1003-5 in BeanUtilsBean from:
} else if (value instanceof String[]) {
newValue = getConvertUtils().convert(((String[]) value)[0],
type);
to something like:
} else if (value instanceof String[] !(value instanceof
type) ) {
newValue = getConvertUtils().convert(((String[]) value)[0],
type);
???
I realize the design allows for making my own Converter and registering with
ConvertUtils but it is not obvious to me
how I can circumnavigate the intrinsic assumption that Object is scalar.
Besides, adding conversions for common types
to their parents seems to add unnecessarily to maintenance costs, violate
the principles of OO and
limits the flexibilty of polymorphism.
I anxiously await work-arounds, debate, criticism, alternative solutions,
pointers, hacks, etc...
Mark Rines
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [digester] Problem building javadoc w/ Ant on Windows
On 18 Jan 2005, at 08:53, Simon Kitching wrote: snip Well, I think I'll raise a bugzilla entry with this info, as a reminder to think about this further. But for the moment, I'm inclined to leave digester as it is, until Robert Donkin reappears and lets us know why this was added in the first place. IANAL my level of legal paranoia is higher than some other committers. at the time, we needed *everything* licensed with ASL2.0 ASAP. (there are some jurisdictions which may - in theory - require explicit - rather than implied - licenses for anything and everything.) so, i added them everywhere i could including the documentation. i've never actually been convinced by the prevailing copyright theories around apache concerning documentation (these are that implied copyright is sufficient). so, if it's causing problems, i'd be happy for the license to be removed. /IANAL - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Looking for WHEN_POOLSIZEMAX_BLOCK
Hello,
There does not seem to an API which can determine the collective size of
the commons collection pool. What I am looking for is a way to tell the
factory block until the collection size goes below a threshold value.
Basically I am interested in heap size consumed by the pool , since
there is not a good way to figure that out in java , I guess it would
be helpful if there is a way we can associate size of the object to the
pooled object so that factory framework can figure that out. Something
like
Class MyObject implements MemorySizable{
{
//Estimated size of the object
Int size_in_bytes = 8;
Public int getSizeinBytes()
{
Return size_in_bytes;
}
}
Let me know if you have any suggestions or I missed something which can
provide me the functionality.
Thanks
Anand
[jira] Commented: (JELLY-196) SwitchTag can not be reused if default encountered
[
http://issues.apache.org/jira/browse/JELLY-196?page=comments#action_57741 ]
Marc DeXeT commented on JELLY-196:
--
Patch file are attached with one unit test case TestSeveralSwitchCall.
Standard TestSwitchTag unit tests have been checked and are clear with patch.
SwitchTag can not be reused if default encountered
--
Key: JELLY-196
URL: http://issues.apache.org/jira/browse/JELLY-196
Project: jelly
Type: Bug
Components: core / taglib.core
Versions: 1.0
Environment: 1.0-RC2-SNAPSHOT
Reporter: Marc DeXeT
Attachments: patch_2005.01.18_switchTag.test.txt,
patch_2005.01.18_switchTag.txt
Script as
j:forEach var=var items=a,b
j:switch on=${var}
j:case value=unencountered1
j:set var=res value=1/
/j:case
j:case value=unencountered2
j:set var=res value=2/
/j:case
j:default
j:set var=res value=default/
/j:default
/j:switch
/j:forEach
throws default should be the last tag within a switch because of
SwitchTag boolean property defaultEncountered is not reset.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[logging] New participant introduction
Hello everybody, my name is Tomas Znamenacek, I am an employee of IBM and I have been working with Richard Sitze on the proposal for enterprise level Commons Logging. I have joined this community to participate in the discussion about the proposal that has been presented and provide comments/input based on my experience with Commons Logging and Java Logging in J2EE environment. I have reviewed all the responses posted to the original proposal and I tried to identify all the issues raised. I think it might be useful to revisit them in separate threads, just to make the navigation a bit easier. At this moment, I think following aspects of the proposal need more discussion, in order to come to a agreement as a community: 1. Logging interface - methods for logging entry and exit events. 2. Logging interface - i18n and l10n support 3. Discovery process 4. Packaging, versioning and name Tomas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[logging] API - methods for logging entry and exit events
This discussion thread is regarding proposed methods for logging method entry and exit events. For each issue I have found in previous discussions I'm offering my comment or recommendation, if I have any. 1. Refactoring a method containing calls to log.enter() and log.exit(), with hardcoded method name, will render these calls inaccurate. Such refactoring is a feature of development tools and I see no point in constraining an API because of tooling deficiency, even that it is a concern from ease of use point of view. I'm sure the tools will adapt to what developers need and until they do, the developers would need to use Search/Replace functionality when refactoring methods/classes. Also, in this case, AOP can help with a around pointcut that would prevent execution of the original logging calls and execute proper ones, where class name and method name are obtained at runtime(which means they are always correct). This approach however is just a workaround because it has a dependency on AspectJ. 2. Adding enter() and exit() methods is not necessary because the same can be achieved with AspectJ using the methods on current Log interface. The Aspect oriented programming certainly offers a great flexibility for adding enter/exit logging calls without having to write them manually, however, similar to previous point, the tooling ability should not prevent us from defining a complete API that does not require the developer to use a specific development tool/language in order to implement proper logging. 3. There is no clear difference between trace and debug level and adding yet another trace level would not help in this situation. Adding methods for logging enter and exit events will make the set of tracing methods more complete and will bring more sense to using them. From my experience I can see that interface with debug, trace and enter/exit logging methods allows developers to produce more granular logging output which is easier to work with during problem determination. 4. The event of method entry or exit is a trace kind of event and should not be logged at different severity(should not have a method on the logging interface) but it should be encapsulated in the message that is being logged. Also, some enter/exit events might have more importance than others, therefore the fact that an event represents enter or exit point should be a state of the message not its severity. The proposed interface will allow us to make a logging call for method enter/exit event without having to create another object(message object) and set the enter/exit flag on it. If there is a logging implementation that allows the enter/exit be a flag on message object, the wrapper for this implementation can certainly have the enter/exit methods implemented that way. When enter/exit events need to be logged on different levels, we start talking about two dimensional space of logging events. Adding support for this into a thin wrapper that is designed to bridge many(all?) different APIs, will get too complicated and would loose the simplicity and ease of use. 5. The Log4J does not have methods for logging method entry/exit events. We should not add those only because Java Logging has added them. The JCL is a thin wrapper for many different logging implementations, not only Log4J. Java Logging has added methods for logging entry/exit events because they were identified as being useful for problem determination. Is there something wrong with following their lead on this ? I believe that by adding these methods to the interface will make the interface easier to use, because the users-developers will not need to write their own code constructing entry/exit messages, if they require those to look consistent within their application/component. 6. Adding more than one enter() method will make the interface too big. The current Log interface contains two methods for each level and based on situation (normal code path or exception code path) the developer can choose the proper one to use. The proposed interface also provides multiple methods for logging entry and exit events, each one for different situation. It seems to be following the same pattern. If we decide on keeping the interface small, then the enter() methods could be consolidated to one, with following signature: enter(Class clazz, String methodName, Object[] methodArgs, Object message); 7. Instead of obtaining class name from the Class object that is passed in, the class name could be obtained from current execution stack. This approach is expensive and inaccurate. In order to obtain the current stack trace, a Throwable object has to be created. Once the current stack trace has been obtained, the calling class has to be located in the stack and there is no way to identify which class is the real caller, because the developers might have implemented their own logging helper classes, which will show up in the stack
[Jakarta Commons Wiki] Updated: CodeConPresentation
Date: 2005-01-18T18:26:26 Editor: KevinBurton Wiki: Jakarta Commons Wiki Page: CodeConPresentation URL: http://wiki.apache.org/jakarta-commons/CodeConPresentation no comment Change Log: -- @@ -15,6 +15,7 @@ * Atom (0.3 and all draft specs) * OPML * FOAF +* Changes.xml * RDF * Modules (dc, aggregation, content, etc) @@ -57,3 +58,6 @@ * mod_bigcompany * BigCompanyEventListener * Totally isolated development. + + * FeedParserListener (rss, atom) + * FeedDirectoryParserListener (opml, foaf, changes.xml) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[all][poll] svn conversion
Alright folks, it looks like svn has stabilized. Let's have a poll here: any more opinions on the svn conversion? Has everyone had ample time to test? Tim O'Brien [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[GUMP@brutus]: Project commons-jelly-tags-email (in module commons-jelly) failed
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 issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-email : Commons Jelly Full details are available at: http://brutus.apache.org/gump/public/commons-jelly/commons-jelly-tags-email/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-email-18012005.jar] identifier set to project name -ERROR- Multiple outputs defined by project javamail; an id attribute is required to select the one you want -ERROR- Unhandled Property: maven.jar.mail on: Maven on Project:commons-jelly-tags-email -DEBUG- Dependency on jaf exists, no need to add for property maven.jar.activation. -DEBUG- Dependency on javamail exists, no need to add for property maven.jar.mail. -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/email/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/email/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/email/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/email/target/test-reports -WARNING- No directory [/usr/local/gump/public/workspace/commons-jelly/jelly-tags/email/target/test-reports] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/commons-jelly/commons-jelly-tags-email/gump_work/build_commons-jelly_commons-jelly-tags-email.html Work Name: build_commons-jelly_commons-jelly-tags-email (Type: Build) Work ended in a state of : Failed Elapsed: 2 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/email] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-18012005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-18012005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-18012005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaf-1.0.1/activation.jar:/usr/local/gump/packages/javamail-1.3.2/mail.jar:/usr/local/gump/packages/javamail-1.3.2/lib/mailapi.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-18012005.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 You are working offline so the build will continue, but commons-jelly-SNAPSHOT.jar may be out of date! The build cannot continue because of the following unsatisfied dependency: mail-1.2.jar (try downloading from http://java.sun.com/products/javamail/javamail-1_2.html) Total time: 2 seconds Finished at: Tue Jan 18 20:12:12 PST 2005 - To subscribe to this information via syndicated feeds: - RSS: http://brutus.apache.org/gump/public/commons-jelly/commons-jelly-tags-email/rss.xml - Atom: http://brutus.apache.org/gump/public/commons-jelly/commons-jelly-tags-email/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 17001818012005, brutus:brutus-public:17001818012005 Gump E-mail Identifier (unique within run) #2. --
Re: [JXPath] On contributing XOM-support
Dear Shirasu, Congratulations on this wonderful piece of work and thank you very much for your decision to contribute it to Apache! I will be happy to assist you with making this contribution happen. But first we need to resolve a couple of issues: 1. Will this be a separate module under commons or an integral part of JXPath? I recommend that we make it an integral part of JXPath 2. Do we have any licensing issues with XOM? I believe we can use it, it is covered by LGPL. Does anybody know of a reason we would not be able to use XOM in our build? Once again, thank you. - Dmitri - Original Message - From: shirasu hiroyuki [EMAIL PROTECTED] To: commons-dev@jakarta.apache.org Sent: Monday, January 17, 2005 10:55 PM Subject: [JXPath] On contributing XOM-support Dear Commons Developpers, I tried to implement custom Pointers and Iterators of the object model XOM for the Commons JXPath. So JXPath supports access to XOM nodes by using my work. I would like to contribute my code to the JXPath project. You can see the details at http://www.k2.dion.ne.jp/~hirsh/xpath/jxpathOverXOM-en.html Thanking you in advance, -- shirasu hiroyuki([EMAIL PROTECTED]) - 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]
[GUMP@brutus]: Project commons-jelly-tags-util (in module commons-jelly) failed
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 issue affects 7 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-ant : Commons Jelly - commons-jelly-tags-fmt : Commons Jelly - commons-jelly-tags-html : Commons Jelly - commons-jelly-tags-jsl : Commons Jelly - commons-jelly-tags-util : Commons Jelly - maven : Project Management Tools - maven-bootstrap : Project Management Tools Full details are available at: http://brutus.apache.org/gump/public/commons-jelly/commons-jelly-tags-util/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-util-18012005.jar] identifier set to project name -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/util/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/util/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/util/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/util/target/test-reports -WARNING- No directory [/usr/local/gump/public/workspace/commons-jelly/jelly-tags/util/target/test-reports] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/commons-jelly/commons-jelly-tags-util/gump_work/build_commons-jelly_commons-jelly-tags-util.html Work Name: build_commons-jelly_commons-jelly-tags-util (Type: Build) Work ended in a state of : Failed Elapsed: 6 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/util] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-18012005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-18012005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-18012005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-18012005.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-18012005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-18012005.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 You are working offline so the build will continue, but commons-jelly-SNAPSHOT.jar may be out of date! Plugin 'maven-deploy-plugin' in project 'commons-jelly-tags-util' is not available build:start: java:prepare-filesystem: [mkdir] Created dir: /home/gump/workspaces2/public/workspace/commons-jelly/jelly-tags/util/target/classes java:compile: [echo] Compiling to /home/gump/workspaces2/public/workspace/commons-jelly/jelly-tags/util/target/classes [javac] Compiling 9 source files to /home/gump/workspaces2/public/workspace/commons-jelly/jelly-tags/util/target/classes [javac] /home/gump/workspaces2/public/workspace/commons-jelly/jelly-tags/util/src/java/org/apache/commons/jelly/tags/util/SortTag.java:23: cannot resolve symbol [javac] symbol : class BeanComparator [javac] location: package beanutils [javac] import
[GUMP@brutus]: Project commons-jelly-tags-bsf (in module commons-jelly) failed
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-bsf has an issue affecting its community integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-bsf : Commons Jelly
Full details are available at:
http://brutus.apache.org/gump/public/commons-jelly/commons-jelly-tags-bsf/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-DEBUG- Sole output [commons-jelly-tags-bsf-18012005.jar] identifier set to
project name
-DEBUG- Dependency on xml-xerces exists, no need to add for property
maven.jar.xerces.
-DEBUG- (Gump generated) Maven Properties in:
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/bsf/build.properties
-INFO- Failed with reason build failed
-DEBUG- Maven POM in:
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/bsf/project.xml
-DEBUG- Maven project properties in:
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/bsf/project.properties
-INFO- Project Reports in:
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/bsf/target/test-reports
-WARNING- No directory
[/usr/local/gump/public/workspace/commons-jelly/jelly-tags/bsf/target/test-reports]
-INFO- Failed to extract fallback artifacts from Gump Repository
The following work was performed:
http://brutus.apache.org/gump/public/commons-jelly/commons-jelly-tags-bsf/gump_work/build_commons-jelly_commons-jelly-tags-bsf.html
Work Name: build_commons-jelly_commons-jelly-tags-bsf (Type: Build)
Work ended in a state of : Failed
Elapsed: 7 secs
Command Line: maven --offline jar
[Working Directory:
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/bsf]
CLASSPATH:
/opt/jdk1.4/lib/tools.jar:/usr/local/gump/packages/bsf-2_2/lib/bsf.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-18012005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-18012005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-18012005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-18012005.jar
-
[javac] symbol : class BSFEngine
[javac] location: class org.apache.commons.jelly.tags.bsf.ScriptTag
[javac] public BSFEngine getEngine() {
[javac]^
[javac]
/home/gump/workspaces2/public/workspace/commons-jelly/jelly-tags/bsf/src/java/org/apache/commons/jelly/tags/bsf/ScriptTag.java:141:
cannot resolve symbol
[javac] symbol : class BSFEngine
[javac] location: class org.apache.commons.jelly.tags.bsf.ScriptTag
[javac] public void setEngine(BSFEngine engine) {
[javac] ^
[javac]
/home/gump/workspaces2/public/workspace/commons-jelly/jelly-tags/bsf/src/java/org/apache/commons/jelly/tags/bsf/BSFExpressionFactory.java:88:
cannot resolve symbol
[javac] symbol : class BSFException
[javac] location: class
org.apache.commons.jelly.tags.bsf.BSFExpressionFactory
[javac] } catch (BSFException e) {
[javac] ^
[javac]
/home/gump/workspaces2/public/workspace/commons-jelly/jelly-tags/bsf/src/java/org/apache/commons/jelly/tags/bsf/BSFExpressionFactory.java:103:
cannot resolve symbol
[javac] symbol : class BSFManager
[javac] location: class
org.apache.commons.jelly.tags.bsf.BSFExpressionFactory
[javac] BSFManager answer = new BSFManager();
[javac] ^
[javac]
[GUMP@brutus]: Project commons-jelly-tags-jetty (in module commons-jelly) failed
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 issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-jetty : Commons Jelly Full details are available at: http://brutus.apache.org/gump/public/commons-jelly/commons-jelly-tags-jetty/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-jetty-18012005.jar] identifier set to project name -DEBUG- Dependency on jetty4 exists, no need to add for property maven.jar.jetty. -DEBUG- Dependency on jakarta-servletapi-5-servlet exists, no need to add for property maven.jar.servletapi. -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jetty/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jetty/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jetty/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jetty/target/test-reports -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/commons-jelly/commons-jelly-tags-jetty/gump_work/build_commons-jelly_commons-jelly-tags-jetty.html Work Name: build_commons-jelly_commons-jelly-tags-jetty (Type: Build) Work ended in a state of : Failed Elapsed: 10 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jetty] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-18012005.jar:/usr/local/gump/public/workspace/jakarta-commons/httpclient/dist/commons-httpclient.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-18012005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/http/target/commons-jelly-tags-http-18012005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-18012005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jakarta-servletapi-5/jsr154/dist/lib/servlet-api.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-18012005.jar:/usr/local/gump/packages/jetty-4.2.21/lib/org.mortbay.jetty.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 You are working offline so the build will continue, but commons-jelly-SNAPSHOT.jar may be out of date! [echo] Warning: This tag library requires JDK1.4 or JDK1.3 with JSSE installed to build. You are using version 1.4.2_05 Plugin 'maven-deploy-plugin' in project 'commons-jelly-tags-jetty' is not available build:start: java:prepare-filesystem: [mkdir] Created dir: /home/gump/workspaces2/public/workspace/commons-jelly/jelly-tags/jetty/target/classes java:compile: [echo] Compiling to /home/gump/workspaces2/public/workspace/commons-jelly/jelly-tags/jetty/target/classes [javac] Compiling 18 source files to /home/gump/workspaces2/public/workspace/commons-jelly/jelly-tags/jetty/target/classes java:jar-resources: test:prepare-filesystem: [mkdir] Created dir: /home/gump/workspaces2/public/workspace/commons-jelly/jelly-tags/jetty/target/test-classes [mkdir] Created dir:
[GUMP@brutus]: Project commons-jelly-tags-swing (in module commons-jelly) failed
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 issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-swing : Commons Jelly Full details are available at: http://brutus.apache.org/gump/public/commons-jelly/commons-jelly-tags-swing/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-swing-18012005.jar] identifier set to project name -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/target/test-reports -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/commons-jelly/commons-jelly-tags-swing/gump_work/build_commons-jelly_commons-jelly-tags-swing.html Work Name: build_commons-jelly_commons-jelly-tags-swing (Type: Build) Work ended in a state of : Failed Elapsed: 15 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-18012005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-18012005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-18012005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/target/commons-jelly-tags-define-18012005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/interaction/target/commons-jelly-tags-interaction-18012005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-18012005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-18012005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-18012005.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-18012005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-18012005.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 You are working offline so the build will continue, but commons-jelly-SNAPSHOT.jar may be out of date! Plugin 'maven-deploy-plugin' in project 'JellySwing' is not available build:start: java:prepare-filesystem: [mkdir] Created dir: /home/gump/workspaces2/public/workspace/commons-jelly/jelly-tags/swing/target/classes java:compile: [echo] Compiling to /home/gump/workspaces2/public/workspace/commons-jelly/jelly-tags/swing/target/classes [javac] Compiling 35 source files to /home/gump/workspaces2/public/workspace/commons-jelly/jelly-tags/swing/target/classes java:jar-resources: test:prepare-filesystem: [mkdir] Created dir: /home/gump/workspaces2/public/workspace/commons-jelly/jelly-tags/swing/target/test-classes [mkdir] Created dir:
Re: [all][poll] svn conversion
My opinion is that we should call a vote asap, and anyone who is -1's should use the test to prove their point. While we still have the test up. I'd suggest a 1 week vote. Any -1 with worthy reason is enough to stop it, but we would be aiming to come up with solutions to any -1's (in a different email thread). Hen On Tue, 18 Jan 2005 21:28:28 -0500, Tim O'Brien [EMAIL PROTECTED] wrote: Alright folks, it looks like svn has stabilized. Let's have a poll here: any more opinions on the svn conversion? Has everyone had ample time to test? Tim O'Brien [EMAIL PROTECTED] - 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]
Re: [all][poll] svn conversion
On Wed, 2005-01-19 at 00:21 -0500, Henri Yandell wrote: My opinion is that we should call a vote asap, and anyone who is -1's should use the test to prove their point. While we still have the test up. I'd suggest a 1 week vote. Any -1 with worthy reason is enough to stop it, but we would be aiming to come up with solutions to any -1's (in a different email thread). Sounds good to me - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all][poll] svn conversion
Go for it! Henri Yandell wrote: My opinion is that we should call a vote asap, and anyone who is -1's should use the test to prove their point. While we still have the test up. I'd suggest a 1 week vote. Any -1 with worthy reason is enough to stop it, but we would be aiming to come up with solutions to any -1's (in a different email thread). Hen On Tue, 18 Jan 2005 21:28:28 -0500, Tim O'Brien [EMAIL PROTECTED] wrote: Alright folks, it looks like svn has stabilized. Let's have a poll here: any more opinions on the svn conversion? Has everyone had ample time to test? Tim O'Brien [EMAIL PROTECTED] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-commons-sandbox/feedparser/src/java/org/apache/commons/feedparser/test TestAtom.java TestFeedFilter.java TestFeedLocator.java TestFeedParser.java TestFeedParserUTF8.java
burton 2005/01/18 22:01:41
Modified:feedparser/src/java/org/apache/commons/feedparser/locate
AnchorParser.java
feedparser/src/java/org/apache/commons/feedparser/test
TestAtom.java TestFeedFilter.java
TestFeedLocator.java TestFeedParser.java
TestFeedParserUTF8.java
Log:
updated anchor parser to support rel... updated tests to remove lucene build
dependency (extra imports removed)
Revision ChangesPath
1.7 +5 -5
jakarta-commons-sandbox/feedparser/src/java/org/apache/commons/feedparser/locate/AnchorParser.java
Index: AnchorParser.java
===
RCS file:
/home/cvs/jakarta-commons-sandbox/feedparser/src/java/org/apache/commons/feedparser/locate/AnchorParser.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- AnchorParser.java 18 Jan 2005 19:39:36 - 1.6
+++ AnchorParser.java 19 Jan 2005 06:01:41 - 1.7
@@ -52,6 +52,9 @@
int index = 0;
+//FIXME: what if there are HTML comments here? We would parse links
+//within comments which isn't what we want.
+
//FIXME: what if href isn't the first attribute? Will it fail
here???
//FIXME: how do we pass back the content of the href: a href=''
this
@@ -68,13 +71,11 @@
String title = (String)map.get( title );
-if ( title != null ) {
-title = title.trim();
+if ( title != null )
title = EntityDecoder.decode( title );
-}
String rel = (String)map.get( rel );
-
+
if ( resource == null || resource.equals( ) )
continue;
@@ -112,7 +113,6 @@
//parse( a title=\linux\ rel=\linux\
href=\http://peerfear.org\; adf/a, listener );
parse( a href='http://peerfear.org' rel='linux' title='linux'
adf/a, listener );
-
}
1.6 +1 -8
jakarta-commons-sandbox/feedparser/src/java/org/apache/commons/feedparser/test/TestAtom.java
Index: TestAtom.java
===
RCS file:
/home/cvs/jakarta-commons-sandbox/feedparser/src/java/org/apache/commons/feedparser/test/TestAtom.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- TestAtom.java 31 Aug 2004 21:00:32 - 1.5
+++ TestAtom.java 19 Jan 2005 06:01:41 - 1.6
@@ -22,13 +22,6 @@
import java.net.*;
import java.security.*;
-import org.apache.lucene.index.*;
-import org.apache.lucene.search.*;
-import org.apache.lucene.queryParser.*;
-import org.apache.lucene.analysis.*;
-import org.apache.lucene.analysis.standard.*;
-import org.apache.lucene.document.*;
-
import org.peerfear.newsmonster.tools.*;
import org.peerfear.newsmonster.network.*;
1.6 +1 -8
jakarta-commons-sandbox/feedparser/src/java/org/apache/commons/feedparser/test/TestFeedFilter.java
Index: TestFeedFilter.java
===
RCS file:
/home/cvs/jakarta-commons-sandbox/feedparser/src/java/org/apache/commons/feedparser/test/TestFeedFilter.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- TestFeedFilter.java 22 Oct 2004 00:37:08 - 1.5
+++ TestFeedFilter.java 19 Jan 2005 06:01:41 - 1.6
@@ -22,13 +22,6 @@
import java.net.*;
import java.security.*;
-import org.apache.lucene.index.*;
-import org.apache.lucene.search.*;
-import org.apache.lucene.queryParser.*;
-import org.apache.lucene.analysis.*;
-import org.apache.lucene.analysis.standard.*;
-import org.apache.lucene.document.*;
-
import org.peerfear.newsmonster.tools.*;
import org.peerfear.newsmonster.network.*;
1.7 +1 -8
jakarta-commons-sandbox/feedparser/src/java/org/apache/commons/feedparser/test/TestFeedLocator.java
Index: TestFeedLocator.java
===
RCS file:
/home/cvs/jakarta-commons-sandbox/feedparser/src/java/org/apache/commons/feedparser/test/TestFeedLocator.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- TestFeedLocator.java 22 Oct 2004 00:37:08 - 1.6
+++ TestFeedLocator.java 19 Jan 2005 06:01:41 - 1.7
@@ -22,13 +22,6 @@
import java.net.*;
import java.security.*;
-import org.apache.lucene.index.*;
-import org.apache.lucene.search.*;
-import org.apache.lucene.queryParser.*;
-import org.apache.lucene.analysis.*;
-import org.apache.lucene.analysis.standard.*;
-import org.apache.lucene.document.*;
-
cvs commit: jakarta-commons-sandbox/feedparser/src/java/org/apache/commons/feedparser AtomFeedParser.java
burton 2005/01/18 22:22:15 Modified:feedparser/src/java/org/apache/commons/feedparser AtomFeedParser.java Log: ... added latest spec... Revision ChangesPath 1.16 +5 -1 jakarta-commons-sandbox/feedparser/src/java/org/apache/commons/feedparser/AtomFeedParser.java Index: AtomFeedParser.java === RCS file: /home/cvs/jakarta-commons-sandbox/feedparser/src/java/org/apache/commons/feedparser/AtomFeedParser.java,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- AtomFeedParser.java 14 Jan 2005 19:06:26 - 1.15 +++ AtomFeedParser.java 19 Jan 2005 06:22:15 - 1.16 @@ -33,6 +33,10 @@ import org.jaxen.jdom.*; /** + * + * + * http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-04.txt + * * http://www.mnot.net/drafts/draft-nottingham-atom-format-02.html * * http://www.ietf.org/html.charters/atompub-charter.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Commons Wiki] Updated: FeedParser
Date: 2005-01-18T22:23:56 Editor: KevinBurton Wiki: Jakarta Commons Wiki Page: FeedParser URL: http://wiki.apache.org/jakarta-commons/FeedParser no comment Change Log: -- @@ -12,3 +12,4 @@ == Resources == CodeConPresentation +TagMetaDataEvents - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all][poll] svn conversion
From eclipse it's slower than using CVS. On Tue, 18 Jan 2005 21:28:28 -0500, Tim O'Brien [EMAIL PROTECTED] wrote: Alright folks, it looks like svn has stabilized. Let's have a poll here: any more opinions on the svn conversion? Has everyone had ample time to test? Tim O'Brien [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Commons Wiki] New: TagMetaDataEvents
Date: 2005-01-18T22:26:16
Editor: KevinBurton
Wiki: Jakarta Commons Wiki
Page: TagMetaDataEvents
URL: http://wiki.apache.org/jakarta-commons/TagMetaDataEvents
no comment
New Page:
There are a number of standards for supporting 'tags' in RSS including:
dc:subject
RSS 2.0 'category'
mod_taxonomy
How are we going to build a generic API that supports all systems currently in
use?
== Delicious ===
{{{
taxo:topics
rdf:Bag
rdf:li resource=http://del.icio.us/tag/programming/
/rdf:Bag
/taxo:topics
}}}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Commons Wiki] Updated: TagMetaDataEvents
Date: 2005-01-18T22:30:34
Editor: KevinBurton
Wiki: Jakarta Commons Wiki
Page: TagMetaDataEvents
URL: http://wiki.apache.org/jakarta-commons/TagMetaDataEvents
no comment
Change Log:
--
@@ -6,7 +6,7 @@
How are we going to build a generic API that supports all systems currently in
use?
-== Delicious ===
+== Delicious ==
{{{
@@ -17,3 +17,16 @@
/taxo:topics
}}}
+
+== Technorati ==
+
+Technorati tags seems totally proprietary:
+
+{{{
+To contribute to this tag, just make a post to your blog about met and include
a link to this page like so:
+
+a href=http://technorati.com/tag/met; rel=tagmet/a
+
+}}}
+
+Which is totally proprietary...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Commons Wiki] Updated: TagMetaDataEvents
Date: 2005-01-18T22:35:24 Editor: KevinBurton Wiki: Jakarta Commons Wiki Page: TagMetaDataEvents URL: http://wiki.apache.org/jakarta-commons/TagMetaDataEvents no comment Change Log: -- @@ -30,3 +30,7 @@ }}} Which is totally proprietary... + +== Interface == + +onTag( String tagname, String uri ) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [JXPath] On contributing XOM-support
Dear Dmitri, Thank you very much for your help. 1. Will this be a separate module under commons or an integral part of JXPath? I recommend that we make it an integral part of JXPath I hope that my code is acceptable as an integral part of JXPath. If so, what specific changes I need to make to the code? (license comments, etc.) Also we need to change the original JXPath code. For example, org.apache.commons.jxpath.ri.model.XMLModelTestCase Because XOM's namespace URI is a little more strict. For details, see http://www.xom.nu/tutorial.xhtml#d0e334 2. Do we have any licensing issues with XOM? I believe we can use it, it is covered by LGPL. I believe, too. Once again, thank you. -- shirasu hiroyuki([EMAIL PROTECTED]) - Original Message - From: Dmitri Plotnikov [EMAIL PROTECTED] Subject: Re: [JXPath] On contributing XOM-support Date: Tue, 18 Jan 2005 23:31:43 -0500 Dear Shirasu, Congratulations on this wonderful piece of work and thank you very much for your decision to contribute it to Apache! I will be happy to assist you with making this contribution happen. But first we need to resolve a couple of issues: 1. Will this be a separate module under commons or an integral part of JXPath? I recommend that we make it an integral part of JXPath 2. Do we have any licensing issues with XOM? I believe we can use it, it is covered by LGPL. Does anybody know of a reason we would not be able to use XOM in our build? Once again, thank you. - Dmitri - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all][poll] svn conversion
On Wed, 19 Jan 2005 17:24:05 +1100, Dion Gillard [EMAIL PROTECTED] wrote: From eclipse it's slower than using CVS. Even (whatever the Eclipse equivalent is for) 'svn status', which doesn't have to talk to the SVN server, while the CVS equivalent does?? -- Martin Cooper On Tue, 18 Jan 2005 21:28:28 -0500, Tim O'Brien [EMAIL PROTECTED] wrote: Alright folks, it looks like svn has stabilized. Let's have a poll here: any more opinions on the svn conversion? Has everyone had ample time to test? Tim O'Brien [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ - 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]
[Jakarta Commons Wiki] Updated: TagMetaDataEvents
Date: 2005-01-18T23:43:58 Editor: KevinBurton Wiki: Jakarta Commons Wiki Page: TagMetaDataEvents URL: http://wiki.apache.org/jakarta-commons/TagMetaDataEvents no comment Change Log: -- @@ -31,6 +31,10 @@ Which is totally proprietary... +== Ideal HTML specification == + +http://www.peerfear.org/rss/permalink/2005/01/18/TechnoratiTagAPIIsBroken/ + == Interface == onTag( String tagname, String uri ) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
