Vikas,
please repost with the [vfs] prefix in the subject so that people can
receive your mail easily.
thanks
paul
Le 4 juil. 07 à 13:14, Vikas Kumar a écrit :
Hi
I am getting this problem as per issue 113(fixed bug).
Please help me to solve this problem.
Thanks regards
Vikas Kumar
On 28.06.2007, at 00:31, Paul Libbrecht wrote:
if I dare request, I would prefer to keep committership even
though my activities haven't been greatly active in jelly.
Similarly, I think, for Peter Royal.
paul
Le 27 juin 07 à 17:52, Torsten Curdt a écrit :
I've prepared the TODO
[
https://issues.apache.org/jira/browse/JELLY-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486524
]
Paul Libbrecht commented on JELLY-275:
--
Andre,
this really looks like a bug.
I believe that on should rather
is something I just managed and it is real easy, to my surprise it
even works with ant.
Now that there's java web start 1.5 (and JNLP 1.5), it might be useful
to make:
- a command-line generic jelly that starts in the current directory and
runs run.jelly or another one given as
for enlightening me.
paul
Dion Gillard wrote:
On 7/25/06, Paul Libbrecht [EMAIL PROTECTED] wrote:
Dion Gillard wrote:
The idea with the tag reference was to have a one stop place for all
the documentation.
I thought this was what libs/index.html does.
It's generated before xdoc:transform
Not very well
I just wanted to make sure that Commons-FileUpload's project's members
are aware of this ongoing specification.
paul
Original Message
Subject:REX and File Upload published
Resent-Date:Sun, 22 Oct 2006 17:03:41 +
Resent-From:public-webapi@w3.org
Date:
Hello,
since a while I'm considering the implementation of a reader for
log-like file formats, that is, for files that are xml up to a header
and footer. We use these in our ActiveMath system, typically, as log
files, where each new log entry is output as a new element.
loglike:parse
Just my 2p: if I remember well, there's a way checkstyle errors can
produce a text-like report with filename:line-number:message which is
exactly what most compilers would output to make errors clickable in,
say, jEdit and Emacs to name a few... That helped me every time i was
haunted by the
It isn't easy as that, building the site does take a huge time because
of the very many tag-libs depending on the maven version this may
even turn out to impossible.
This tag-reference page makes double usage with:
http://jakarta.apache.org/commons/jelly/libs/index.html
whose links are
, we need to
make them correct, I think the jellydoc takes precedence of javadoc... or ?
b) It doesn't provide examples and usage info.
how would you document examples except with unit-tests ??
paul
On 7/25/06, Paul Libbrecht [EMAIL PROTECTED] wrote:
It isn't easy as that, building the site
hello jellyers,
the jelly faq would love to be enriched by the many questions asked on
the list(s) but it is still a manually authored xdoc. Anything against
me moving it to using the maven-1.1 faq plugin ?
thanks
paul
smime.p7s
Description: S/MIME Cryptographic Signature
)
Reporter: Paul Libbrecht
Assigned to: Paul Libbrecht
When setting the debug mode, a lot of the creation of the ant tags are reported
about and this invokes the toString method of the tags.
This fails for some objects such as the fileset tag... a method to call
toString safely is needed
[ http://issues.apache.org/jira/browse/JELLY-228?page=all ]
Paul Libbrecht resolved JELLY-228:
--
Resolution: Fixed
Have applied the patch.
Please check and reopen if need be.
paul
AntTag.createDataType() throws ClassCastException
[ http://issues.apache.org/jira/browse/JELLY-232?page=all ]
Paul Libbrecht closed JELLY-232:
Resolution: Fixed
Fixed with AntTag and AntJellyContext.
paul
Some ant objects throw NPE at toString
before tagging it would only affect,
probably, the maven.xml in jelly/jelly-tags.
paul
Dion Gillard wrote:
Paul can we post the source/binary distribution release after getting
the jar out?
On 6/20/06, Paul Libbrecht [EMAIL PROTECTED] wrote:
Rahul Akolkar wrote:
Regardless of what Jelly
things up for a proper signing and hashing then will
achieve the jar-oriented tasks of the release guide. And send an
announcement here and on commons-users.
paul
Paul Libbrecht wrote:
I hereby request to vote about the release of the jelly subproject
interaction tag library.
The details
Dion Gillard wrote:
Don't we have tags at the taglib level for Jelly?
Nope... but that's quite ok or ?
That seems a whole lot of stuff for a single taglib.
What do you mean ?
svn cp is the only way to tag so I cp the whole project. It only
consumes my (temp) directory space, not even the
thanks, fixed!
paul
Lukas Theussl wrote:
Another remark: is the SNAPSHOT dependency on commons-jexl necessary?
-Lukas
Paul Libbrecht wrote:
Dion Gillard wrote:
Don't we have tags at the taglib level for Jelly?
Nope... but that's quite ok or ?
That seems a whole lot of stuff
-INTERACTION-1_1/
Enjoy!
paul libbrecht
smime.p7s
Description: S/MIME Cryptographic Signature
[ ] don't do it because...
thank you in advance.
paul
Paul Libbrecht wrote:
Here's the plan:
- all issues with this tag-libs are cleared
- no further changes are needed for the release... and almost no risk
of concurrent change exist (hence no branch is needed).
- the release shall, as with most
you in advance.
paul
Paul Libbrecht wrote:
Here's the plan:
- all issues with this tag-libs are cleared
- no further changes are needed for the release... and almost no risk
of concurrent change exist (hence no branch is needed).
- the release shall, as with most jelly-tag-libraries, only
Dion Gillard wrote:
I have assembled the following release candidates...
- a site with RC1 version tag:
http://people.apache.org/~polx/tmp/jelly-tags-interaction-rc1/
- a jar which is the sole outcome of this subproject:
?
thanks
paul
Sandy McArthur wrote:
On 3/3/06, Paul Libbrecht [EMAIL PROTECTED] wrote:
As far as I could see such a thing... jar signing would need to happen
on Apache server... using some Apache private key... right ?
Maybe this is a first issue ?
How would you go to ensure that such a private
robert burrell donkin wrote:
On Tue, 2006-05-09 at 23:07 +0200, Paul Libbrecht wrote:
The story seems quite simple so I thought I'd just ask for a vote sorry if too
stressed.
The interaction jelly tag-library is now ready for release 1.1.
It has been recently boosted with a finer control
[
http://issues.apache.org/jira/browse/JELLY-230?page=comments#action_12416139 ]
Paul Libbrecht commented on JELLY-230:
--
Lukas... replacenamespace is working fine for me.
The following:
?xml version=1.0 encoding=UTF-8?
j:jelly xmlns:j=jelly:core
[
http://issues.apache.org/jira/browse/JELLY-226?page=comments#action_12415443 ]
Paul Libbrecht commented on JELLY-226:
--
Is now committed... looks like i need to wait to see gump take it up.
Upgrade dom4j and jaxen
x:foreach's sort option breaks if empty result
--
Key: JELLY-231
URL: http://issues.apache.org/jira/browse/JELLY-231
Project: Commons Jelly
Type: Bug
Components: taglib.xml
Versions: 1.1
Reporter: Paul
Gump experts,
Failures in these three tests are due, I think, to old jaxen, indeed
jaxen 1.1-beta-4 is referenced in many places in
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-html/index.html
and the other failing gump reports. Explanation for this is the gump
Would that run visual unit tests ??
paul
Brett Porter wrote:
Hi,
Berin has setup a VMWare machine for general build stuff. I have setup
httpd, java, continuum and maven 2 on there.
Who was interested on working on nightly builds/CI for commons-*?
- Brett
Well,
Lukas who requested this indicated that anyways he wanted some other
releases (including the core).
There was one request to get a packed version to chew at before
voting... which I did not have the time to do. Votes were, otherwise,
positive.
So, it's not done yet and I'll need till
I please beg another round of review... or I'll interprete the silence
as no bother and will do...
paul
Hans Gilde wrote:
+0
If the unit tests pass, I'm inclined to say that the latest version should
be used. But I have not tried it.
-Original Message-
From: Paul Libbrecht [mailto
Henri Yandell wrote:
Migration is complete; Commons has successfully invaded
issues.apache.org/jira.
Next up - reflect the change on the website.
Just for your information, it is possible to have readable URLs to Jira
even though Jira itself doesn't give them.
Among others, a project page
thing would be to keep it for archive purposes in Bugzilla, I
think.
paul
Paul Libbrecht wrote:
Henri Yandell wrote:
There are now two projects in Jira, Jelly and Commons JellyImported.
If someone has a moment, it'd be a real help if they could take a look
at the two of these and let me know
[
http://issues.apache.org/jira/browse/JELLY-230?page=comments#action_12402290 ]
Paul Libbrecht commented on JELLY-230:
--
I fear that the problem is considered to be backwards compatibility even
though a normal perspective would be call to it a bug-fix
It's a nice question, I don't think it really is and it may be we need a
layer between Jaxen expressions in jelly and other objects in the context.
Jexl's new version now does more integer types (right?) which happened
to break a jexl comparison which could not happen against an integer.
Adding
Henri Yandell wrote:
There are now two projects in Jira, Jelly and Commons JellyImported.
If someone has a moment, it'd be a real help if they could take a look
at the two of these and let me know if JellyImported can be deleted or
if it should have its issues moved into Jelly.
I just didn't
[
http://issues.apache.org/jira/browse/JELLY-230?page=comments#action_12402265 ]
Paul Libbrecht commented on JELLY-230:
--
Gee!! I certainly hope that Jelly acts like this as this is normal XML!
What I realize is that this dummy namespace has had
Hello Jellyers,
After my two test fixes, which had almost nothing to do with dom4j...
I seem to be happily running everything with dom4j 1.6.1.
Can anyone confirm me this ? It's quite radical but it'd help in many
other places.
paul
[
http://issues.apache.org/jira/browse/JELLY-187?page=comments#action_12383406 ]
Paul Libbrecht commented on JELLY-187:
--
I have an issue with this patch... Namely the undocumented following usage:
$${a.b.c} does output ${a.b.c}
at least I use
[ http://issues.apache.org/jira/browse/JELLY-218?page=all ]
Paul Libbrecht resolved JELLY-218:
--
Fix Version: 1.1
Resolution: Fixed
Assign To: Paul Libbrecht
Fixed in subversion, please test.
If you have some time for a contribution
Hi,
in the efforts of upgrading to dom4j-1.6, I've bumped into the following
weird behaviour which may be my too small knowledge of JSL:
TestJSL.testExample1 tests the output of the jelly file:
src/test/org/apache/commons/jelly/jsl/example.jelly
and then tries to assert that the first
definitely in favor of cleaning up the Jira
assignments. If you'd like to assign me some stuff, I'll fix it. But I'm not in
a position to really lead anything at the moment.
-Original Message-
From: Paul Libbrecht [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 10, 2006 4:17 AM
To: Jakarta
[
http://issues.apache.org/jira/browse/JELLY-226?page=comments#action_12379153 ]
Paul Libbrecht commented on JELLY-226:
--
Well... I have now made a few tests and, up to two lines of fixes in
jelly-tags-jsl, I seem to be running fine all tag-libs
[ http://issues.apache.org/jira/browse/JELLY-175?page=all ]
Paul Libbrecht updated JELLY-175:
-
Component: taglib.interaction
Fix Version: 1.1
Version: 1.0
Assign To: Paul Libbrecht
Fixed versions component.
patch for jelly-tags
[ http://issues.apache.org/jira/browse/JELLY-229?page=all ]
Paul Libbrecht updated JELLY-229:
-
Component: taglib.interaction
Fix Version: 1.1
(was: 1.1-beta-1)
Version: 1.0
Fixed components and versions.
Add list
[ http://issues.apache.org/jira/browse/JELLY-175?page=all ]
Paul Libbrecht resolved JELLY-175:
--
Resolution: Fixed
This in the current version about to be released (I think).
paul
patch for jelly-tags-interaction
[
http://issues.apache.org/jira/browse/JELLY-229?page=comments#action_12378850 ]
Paul Libbrecht commented on JELLY-229:
--
I changed the question to born before the 20th century ;-).
For release to happen is just to get a vote on commons-dev which I
[
http://issues.apache.org/jira/browse/JELLY-226?page=comments#action_12378851 ]
Paul Libbrecht commented on JELLY-226:
--
The current dependency is jaxen 1.1-beta8 and dom4j 1.5.
Is that sufficient for you ?
Do you need 1.5.2 or 1.6 ?
paul
Upgrade
Hi,
I was fiddling with Jira jelly project administration because
interaction didn't have a component and realized that some components
have been assigned to dion... which is good.
I'd like it if we could distribute the lead of all components, also so
that James Strachan is not anymore the
[ http://issues.apache.org/jira/browse/JELLY-229?page=all ]
Paul Libbrecht resolved JELLY-229:
--
Fix Version: 1.1-beta-1
Resolution: Fixed
Assign To: Paul Libbrecht (was: james strachan)
Applying patch and successfully run the described
The story seems quite simple so I thought I'd just ask for a vote sorry
if too stressed.
The interaction jelly tag-library is now ready for release 1.1.
It has been recently boosted with a finer control on auto-completion,
and maven console plugin is using it successfully.
Thanks to give it a
[
http://issues.apache.org/jira/browse/JELLY-175?page=comments#action_12378439 ]
Paul Libbrecht commented on JELLY-175:
--
I suppose I was too tired...
I did it again... indeed saw that the patch was not needed... and that I got it
working on my Mac
[
http://issues.apache.org/jira/browse/JELLY-175?page=comments#action_12378292 ]
Paul Libbrecht commented on JELLY-175:
--
Please be more precise as to how this works great for you (platform, how
built-in, example code, etc...).
Last I tried, precisely
[
http://issues.apache.org/jira/browse/JELLY-175?page=comments#action_12378339 ]
Paul Libbrecht commented on JELLY-175:
--
Very weird, I did the same (you should have also indicated you applied the
patch).
And... well... I get a very bad result, namely
[ http://issues.apache.org/jira/browse/JELLY-203?page=all ]
Paul Libbrecht closed JELLY-203:
Resolution: Fixed
Tastes fixed.
paul
[Util] [PATCH] Test cases for jelly-tags-util has wrong package
[
http://issues.apache.org/jira/browse/JELLY-205?page=comments#action_12373358 ]
Paul Libbrecht commented on JELLY-205:
--
Do I understand that you consider it fixed but have not unit-test for it ?
paul
util:loadText adds a new line to files that does
[ http://issues.apache.org/jira/browse/JELLY-205?page=all ]
Paul Libbrecht closed JELLY-205:
Resolution: Fixed
Sorry, dumb of me... sure... clearly fixed... I don't think a unit-test is
necessary.
paul
util:loadText adds a new line to files
[
http://issues.apache.org/jira/browse/JELLY-173?page=comments#action_12373368 ]
Paul Libbrecht commented on JELLY-173:
--
Felipe, Jelly is not dead but several committers are a bit... busy or tired...
I am currently giving a few cycles to polish things
don't need to bloat it for now, having this server at hand... so I
thought that a temporary space as such is better
On 4/4/06, *Paul Libbrecht* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hello,
Since ages, the jelly-site is output wrong where, in particular, the
project
Now... this area piques me as it's getting so old and it looks like the
site not being updated is half a consequence of the failing tests.
So I tried it a bit more and got surprised to not reproduce this error
with jaxen b8 or b7 but to be able to reproduce this with b4.
I tried it with both
Hello,
Since ages, the jelly-site is output wrong where, in particular, the
project info, project reports, and downloads are missing from the
navigation.
Can folks please check
http://klein.activemath.org/~paul/JellyDoc/
before I can upload it ?
thanks
paul
PS: this was built with
Phil Steitz wrote:
On 3/11/06, Paul Libbrecht [EMAIL PROTECTED] wrote:
I would fear of a library providing such functionality be enormous...
any modularity in commons-math planned ?
Good question, which comes up over and over again in [math]. That's
why I suggested that we focus
if all
external dependencies are signed by the creator, you need to create a
seperate jnlp (include like) file per unique cert, which can kind of
suck from a release manager perspective.
So my preferred way is to just (re) sign everything with the same cert..
Mvgr,
Martin
Paul Libbrecht wrote
I would fear of a library providing such functionality be enormous...
any modularity in commons-math planned ?
paul
Sharon Lourduraj wrote:
Prime Number Theory is a huge subject. To start of with we can focus
on implementing prime finding methods, such as divide by odd numbers
up to the
As far as I could see such a thing... jar signing would need to happen
on Apache server... using some Apache private key... right ?
Maybe this is a first issue ?
How would you go to ensure that such a private key is not hacked or copied ?
Let infrastructure team do the signing ?
I suppose that,
Paul Libbrecht wrote:
I suppose that, with Java Web Start, the jar-signing mechanism may
request at least one authorization for each signing key...
Has anyone tested a java-web-start application where jars are from
different originators?
If, indeed as I fear, there are several requests
or that the resource be loaded from a remote
URL, which would make offline builds fail. Could be there is a simple
trick to make this work?
Phil
On 2/28/06, Paul Libbrecht [EMAIL PROTECTED] wrote:
You wouldn't need to read Xerces in any line... you just need to use an
org.xml.sax.InputSource which has
You wouldn't need to read Xerces in any line... you just need to use an
org.xml.sax.InputSource which has a properly set system-id.
new InputSource(URL) or new InputSource(File) does make it for you.
Generally such resolution error happen to be when an
InputSource(InputStream) is used for
At least I can confirm this on my local machine...
paul
Dion Gillard wrote:
Looks like my recent changes to JEXL have fixed this one. The others
appear to be jaxen related.
On 2/14/06, commons-jelly development commons-dev@jakarta.apache.org wrote:
To whom it may engage...
This is an
But remember this is only part of the problem.
The jelly-test failure is related to expression-equality in jexl where:
[junit] Expected expression: ${singleSize*2}
[junit] Actual expression: ${doubleSize} File:
fails because, I think so said Dion, of primitive-types incorrect
comparison
My +171717 to bundle Xerces back! (if I dare)
paul
Brett Porter wrote:
Maven 1.1 uses your built in XML parser. Problem is, the two JDKs behave
completely differently. I think we need to go back to bundling xerces.
-
To
-Original Message-
From: Paul Libbrecht [mailto:[EMAIL PROTECTED]
Sent: Monday, December 19, 2005 2:10 PM
To: Jakarta Commons Developers List
Subject: Re: [jelly][vote] APT tag library
Ryan,
The idea of making it a jira issue is that it's a place you
can post
, unfortunately, delayed to or 2.0...
paul
Diogo Quintela (EF) wrote:
I back you up Greg.
Indeed, we are only using those because of core/xml related changes (xml
pipeline / xml namespace) introduced to support those xsd declarations
(but are by far more than that)
Paul Libbrecht has worked
because of core/xml related changes (xml
pipeline / xml namespace) introduced to support those xsd declarations
(but are by far more than that)
Paul Libbrecht has worked on those
http://issues.apache.org/jira/browse/JELLY-214
http://issues.apache.org/jira/browse/JELLY-213
Regarding releasing as RC
Damian Hamill wrote:
I await your advice on the issue of patents (Martin van den Bemt)
however should the possibility of patent issues stop us ? I mean
there is a patent for MP3 but the folks at javazoom have released an
MP3 decoder. Isn't it OK to release in source form ?
If you read a bit
You definitely need to send such a wish to the general xml list at least.
Note also much w3c interaction can be done without membership...
paul
Rahul Akolkar wrote:
On 1/16/06, Tim OBrien [EMAIL PROTECTED] wrote:
snip/
...this brings up another issue, I think it would be beneficial for the
That seems annoying to insert yet another dependence, or ?
Services for the test ? Would that run with gump ?
paul
Benoit Callebaut wrote:
Hello James,
Thanks for highlighting some mistakes.
project.xml has a new dependency on vfs.
I am actually rewritting the whole stuff to make the
robert burrell donkin wrote:
not sure whether additional karma is required to add a component
Oh well, you need to be a committer if you want to maintain such in svn.
I think I'd summarize the things as follows:
- Ryan indicated he had this tag-library and would like to propose it
- Dion
Ryan Heaton wrote:
That sounds great. How do I get a jira account so I can add a component?
-Original Message-
From: Paul Libbrecht [mailto:[EMAIL PROTECTED]
Sent: Monday, December 19, 2005 2:10 PM
To: Jakarta Commons Developers List
Subject: Re: [jelly][vote] APT tag library
Dear Benoit,
I second James comments posted earlier.
I'd also like to request the following:
- the VFS embedding sounds relatively smooth to me, I'd easily consider
including it into Jelly... it's a hard one though since it's about
jelly-core.
- the properties enrichment is quite a radical
library, if it
gets accepted.
So far, I have recorded three people voting positive for both proposals:
Dion Gillard
Hans Gilde
Paul Libbrecht
hi ryan
(sorry to have to start being a little legalistic...)
i know that this can be a little confusing but there are votes and
VOTEs...
both
-Original Message-
From: Paul Libbrecht [mailto:[EMAIL PROTECTED]
Sent: Monday, December 19, 2005 2:17 AM
To: Jakarta Commons Developers List
Subject: Re: [jelly][vote] APT tag library
I'm slowly catching up on this.
Maybe we need to have life with Ryan a bit longer before becoming
what libraries are actually in use.
- Brett
Paul Libbrecht wrote:
I'm trying hard to fail and fail to fail...
As I understand it would be enough to change
${JELLY_HOME}/parent-project.xml to refer jaxen 1.1-beta-6, 1.1-beta-8
or 1.1-beta-5... but maven clean jar still succeeds with me.
Can
I am sorry to answer only now... I'd put my vote as well...
paul
Ryan Heaton wrote:
It has been awhile now since I've seen any activity on this thread. I've only
seen one person vote.
So how does this work? Is one vote adequate for approval? Do we need to
encourage more votes?
I'm trying hard to fail and fail to fail...
As I understand it would be enough to change
${JELLY_HOME}/parent-project.xml to refer jaxen 1.1-beta-6, 1.1-beta-8
or 1.1-beta-5... but maven clean jar still succeeds with me.
Can it be this is related to the maven classpath ??
Am I
Brett Porter wrote:
It was intentionally breaking, I think. I was told that it tightening
up conformance. Others are welcome to pursue it further, this isn't
really my realm of expertise.
Brett, would you have a copy of the mails ?
Such a strengthening would be related to a reported
Do i not understand Gump or the fact that we stick Jaxen head is
something that could be changed ?
Indeed, no-one really wishes to work with the latest jaxen currently.
thanks
paul
Dion Gillard wrote:
It's a break in how Jaxen works.
Unless we upgrade all of Jelly to work with the code
[ http://issues.apache.org/jira/browse/JELLY-224?page=all ]
Paul Libbrecht resolved JELLY-224:
--
Resolution: Invalid
This has nothing to do with Jelly...
All XML parsers have to load the DTD when it's referenced since a DTD can
indicate default
[
http://issues.apache.org/jira/browse/JELLY-224?page=comments#action_12359148 ]
Paul Libbrecht commented on JELLY-224:
--
You mean like a catalog based on public-identifiers, right ?
That could be considered, indeed, within the core tags... but we need
Hans,
I've seen your bug-report about keeping this reference.
At least if one wished something like reload my parent component with
this jelly such a reference would have been needed and I was preparing
for such. Hence these changes.
Now that, for one, I did not find time to finalize this,
[X] +1, let him commit!
[ ] +0
[ ] -0
[ ] -1, no, because
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Le 8 sept. 05, à 14:19, peter royal a écrit :
Since it sounds like this is a larger contribution, it might be
necessary for a CLA or a Software Grant to be filled out,
http://apache.org/licenses/#clas, but someone with more knowledge
can clarify that..
I would also find it good and I believe
Just for me to be sure to understand... this is definitely a change
compared to pre-1.0, or ?
Can you maybe update the javadoc of setCacheTags/getCacheTags or should
we work on a page lifecycle of a tag ?
paul
Le 16 août 05, à 03:56, peter royal a écrit :
On Aug 15, 2005, at 3:22 AM, Paul
Goodness... this didn't reach commons-dev. It must!
paul
Début du message réexpédié :
De: Paul Libbrecht [EMAIL PROTECTED]
Date: 15 août 2005 23:01:31 GMT+02:00
À: Henk P. Penning [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], repository@apache.org
Objet: Rép : SNAPSHOTs in java-repository
Le 14
Brett,
Le 16 août 05, à 09:16, Brett Porter a écrit :
The SNAPSHOT releases of Jelly have been removed from ibiblio. They
were way out of date and confusing. If you need to track a development
version, they are published to http://cvs.apache.org/repository. The
default Maven settings used for
I have just added this little point in the shall not section... have
a bit of time in order to merge docs in further.
paul
Le 16 août 05, à 11:38, Brett Porter a écrit :
The important thing to remember is not to put anything in
/www/www.apache.org/dist that is not a sanctioned release.
.
-Original Message-
From: Paul Libbrecht [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 13, 2005 6:31 PM
To: Jakarta Commons Developers List
Subject: Re: [jelly] 1.0-final problem wrt tag caching
Indeed... it is running by me as well but I am fully puzzled.
I had added, after your commit, in my
royal a écrit :
On Aug 10, 2005, at 6:14 PM, Paul Libbrecht wrote:
I'm annoyed... I don't obtain the same results as you do.
With the default cacheTags value as false, I obtain only your test
failing.
With the default cacheTags value as true, I obtain many failed tests.
Did you not say
: (+351) 217 827 830
Email: [EMAIL PROTECTED]
PGP: 0xF51A5AB9
| -Original Message-
| From: Paul Libbrecht [mailto:[EMAIL PROTECTED]
| Sent: quarta-feira, 10 de Agosto de 2005 23:49
| To: Jakarta Commons Developers List
| Subject: Re: [jelly] Jelly Builds
|
|
| Le 4 août 05, à 12:56, Paul
de Informação, Lda.
Av. António Serpa, 26 - 4º Dto.
1050-027 Lisboa, Portugal
Tel: (+351) 217 827 800
Fax: (+351) 217 827 830
Email: [EMAIL PROTECTED]
PGP: 0xF51A5AB9
-Original Message-
From: Paul Libbrecht [mailto:[EMAIL PROTECTED]
Sent: quinta-feira, 11 de Agosto de 2005 12:44
To: Jakarta
1 - 100 of 354 matches
Mail list logo
