I am going to paraphrase a conversation that i heard
recently on IRC, discussing the usability of the
current Forrest website.
can't even view it with FireFox ... more-or-less works
in FF for me ... perhaps designed for IE ... the search box
is all over the place ... fonts are unreadable ... the
Ron Blaschke wrote:
David Crossley wrote:
Ron Blaschke wrote:
If not, can anybody recommend a DTD parser that is available under the
Apache License? jpod uses it to resolve Eentity formatting codes,
which are akin to entity; in XML.
Forrest has its internal Catalog Entity Resolver
Why would this suddenly be needed for gump? It was okay
without this until recently. I am wondering if it was
a symptom of some other recent change in forrest.
--David
Author: cheche
Date: Sun Jan 23 08:00:24 2005
New Revision: 126215
URL: http://svn.apache.org/viewcvs?view=revrev=126215
I suddenly realised the issue with cocoon-trunk. It needs
to run its 'build docs' before running 'forrest'. It generates
some extra source documentation before forrest starts.
There is a global parameter forrest-exec which can call
a shell script to do other things, then call forrest.
I have the
Here is my +1
--David
Dave Brondsema wrote:
David Crossley wrote:
Dave Brondsema wrote:
David Crossley wrote:
I suddenly realised the issue with cocoon-trunk. It needs
to run its 'build docs' before running 'forrest'. It generates
some extra source documentation before forrest starts.
There is a global
I asked about this on [EMAIL PROTECTED]
http://marc.theaimsgroup.com/?t=11079957123
and a kind soul provided the solution.
No time left for me today.
--David
Gump wrote:
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information
I just re-generated the site and published it.
While doing so, i realised that i made a major stuff-up
the last time that i did it ... clobbered some of 0.6 docs
with the 0.7-dev stuff. I hope that i have fixed it now.
Here are some notes:
1) build the forrest_06_branch docs and copy them to
Bowe, Bastian wrote:
after opening http://forrest.apache.org/docs/dev/ and clicking on the
Project tab I get a 404
Ah thanks, i see that the Welcome tab is the same. I will investigate.
They need to point up one directory.
--David
Gregor J. Rothfuss wrote:
hey,
the lenya site contains a changes.html created out of the SVN changelog [1]
forrest takes over 5 minutes to create that page, which makes it a pita
to wait for when running forrest site. from what i can tell, forrest
spends a lot of time pondering the
Ross Gardler wrote:
David Crossley wrote:
Dave Brondsema wrote:
Because 0.6 docs are not split, things are pretty confusing. I
speculate it might be worth it to get a 0.7 release out the door
primarily so our online docs make sense. 0.7-dev has been pretty stable
for a while and it has
I solved some of the remaining failures with the forrestbot.
Both forrest-site and forrest-docs-dev needed to have a full
'svn checkout' done before the forrestbot starts. Forrestbot
only does 'svn co' of part of the source tree and so it misses
the conf directory for forrest-site. Dunno what the
Jason End wrote:
I was wondering if anyone would object to me rewriting
the Plugin documentation. My understanding is that the
0.7 documentation isn't finished and hence I find some
of the topics slightly confusing.
Please do. Documentation is never finished :-) and
there is always room for
This changes causes breakages when doing 'forrest' in docs-author.
Every document gets errors like the following. Do we need an upgraded
Cocoon 2.2?
X [0] libre-intro.html BROKEN:
org.apache.cocoon.environment.commandline.CommandLineRequest.getLocales()
method not yet implemented!
--David
Juan Jose Pablos wrote:
David Crossley wrote:
This changes causes breakages when doing 'forrest' in docs-author.
Every document gets errors like the following. Do we need an upgraded
Cocoon 2.2?
X [0] libre-intro.html BROKEN
Ross Gardler wrote:
David Crossley wrote:
Ross Gardler wrote:
Since I am not very clued in with catalogs and their use I have no
opinion on this thread, but I do need to implement something. So, if
someone has the time (and the wine) to design a solution for *exactly*
the problem
Arik Kfir wrote:
Thorsten Scherler wrote:
Arik Kfir wrote:
We are thinking about embedding Forrest as a content generation engine
in our software.
Apache lenya is trying to do the same thing. :)
I changed the response address to the dev list because we discuss such
things in the dev
Reinhard Poetz wrote:
David Crossley wrote:
This was deliberate. We will eventually need to find a better way
to link separate sets of documentation. Apache Cocoon has this
same issue.
Yes, this is a maintenance nightmare ATM. Any improvment here would be
hightly appreciated!
So would
release plan.
--David
David Crossley wrote:
Dave Brondsema wrote:
David Crossley wrote:
Ross Gardler wrote:
David Crossley wrote:
Should we aim for a release date of Friday 2005-03-25?
SInce it's Nicola's birthday I think that is a must - two excuses for a
beer in the evening
Ross Gardler wrote:
Author: crossley
Date: Wed Mar 16 21:06:16 2005
New Revision: 157895
URL: http://svn.apache.org/viewcvs?view=revrev=157895
Log:
Add the missing entry for pod-output plugin.
Sorry - in my rush to do this the other day I forgot to commit to the
main SVN server.
Just a quick note, gotta rush out now. Yes there was stacks of discussion
on this topic, but its good to be sure that we all understand, and maybe
there is a flaw.
The docs that are currently at docs/dev/ are 0.7-dev
They will move to /docs/ when the next release happens.
Then /docs/dev/ will
The ASF infrastructure is doing work on the servers over this
extended weekend. So you may find that some services are not
available. The websites will automatically fail-over to another
server. The mail is the priority, and they will try to have
it up again ASAP. The SVN and ViewCVS will probably
Cyriaque Dupoirieux wrote:
Ok, Ross,
I was wrong once again, I was not looking in the good direction...
In fact, my status.xml declared a section before the changes tag.
(I use this section to describe - in my history of modification -
the rules I apply to choose the next version
Ross Gardler wrote:
David Crossley wrote:
We need to be continually cleaning up our Jira issue tracker.
There is a lot of clutter and it means that we cannot have a
good view of our situation.
We recently defined a stack categories. That helps to provide
other ways to browse
Ross Gardler wrote:
David Crossley wrote:
What i am proposing now is an extra step. Remove the option
HEAD version entirely from Jira. I think it is superfluous.
Sorry - I'm reading too fast this morning.
If a bug is introduced into head (i.e. wasn't in the previous release)
where would
Ross Gardler wrote:
David Crossley wrote:
Ross, during the move of the status/changes/todo processing
into the projectInfo plugin, the status.xml file was removed
at main/fresh-site/status.xml ... Was that deliberate?
http://svn.apache.org/viewcvs?view=revrev=156244
Ahhh... hmmm... yes
Ross Gardler wrote:
David Crossley wrote:
Just a quick note, gotta rush out now. Yes there was stacks of discussion
on this topic, but its good to be sure that we all understand, and maybe
there is a flaw.
The docs that are currently at docs/dev/ are 0.7-dev
They will move to /docs/ when
Done. That clarifies the Roadmap.
Do any people out in the Forrest dev community
know other things that we can do to improve our use
of Jira? Or point to projects that use it well.
--David
David Crossley wrote:
The missing piece is that we need to clearly denote the version number
on all docs. We should be able to do something rough-and-ready
to get us by.
I have been experimenting with ways to do this.
Even if just a quick fix, it needs to be configurable.
I am calling
Dave Brondsema wrote:
Quoting Ross Gardler [EMAIL PROTECTED]:
Dave Brondsema wrote:
Quoting David Crossley [EMAIL PROTECTED]:
Done. That clarifies the Roadmap.
Do any people out in the Forrest dev community
know other things that we can do to improve our use
of Jira
David Crossley wrote:
Dave Brondsema wrote:
/docs/dev/ nested below /docs/ seems weird. I think it would be better
to host the current stable release at a url like: /docs/0.7/. This
would also permit us to keep documentation for all old releases
(although we would probably want
http://issues.cocoondev.org//browse/FOR-446
The following comment has been added to this issue:
Author: Ferdinand Soethe
Created: Thu, 24 Mar 2005 1:38 AM
Body:
Thanks for the feedback.
Re splitting
The reason I did not split them after some consideration,
is that
Some discussion from http://issues.cocoondev.org/browse/FOR-446
Dunno what the answer is yet ...
David Crossley wrote:
I am concerned about the annotated sitemaps in howto/*.xmap.html
as it will be difficult to keep these synchronised as the Forrest core
sitemaps change over time. Perhaps we
Due to all these fancy filename extensions for text files,
committers are going to need to configure their SVN clients accordingly.
Someone recently committed an SVN configuration file to
an ASF repository - i thought that it was committers but
i cannot now find it to add these new ones. Does
Thorsten Scherler wrote:
David Crossley wrote:
Due to all these fancy filename extensions for text files,
committers are going to need to configure their SVN clients accordingly.
http://issues.cocoondev.org//browse/FOR-124
Thanks but that is not the one that i meant. I think
Ferdinand Soethe wrote:
David Crossley wrote:
DC They are really separate issues:
DC 1) understanding the sitemap
DC 2) customising the particular pipeline that processes html sources.
They could be if the text about the site maps was a general explanation
(which it isn't - yet?). Though
Dave Brondsema wrote:
motd-page-url/docs//motd-page-url doesn't work if these docs are
standalone (e.g on my machine).
Yeah, sorry. I knew it would make a broken link for local docs,
but thought that it was more important to get the website happening
at this stage.
Would it help to use a
David Crossley wrote:
There are two plugins org.apache.forrest.plugin.view
and org.apache.forrest.plugin.views.
Argh, sorry, i should read all the day's mail first.
Thorsten has fixed that.
--David
I see that many of our plugins, even new ones, are not using
the naming convention.
... snipped from plugins/pluginInfrastructure.html
-
org.apache.forrest.plugin.PLUGINNAME
net.sf.forrestPlugins.PLUGINNAME
In addition the name of the plugin should indicate the type of plugin it is:
Thorsten Scherler wrote:
Hello devs,
trying to deploy the view and leather plugin I found a weird thing
happening:
Doing 'forrest run' brings the site rendered by the plugins, but doing
'forrest' will use the normal skin.
How come? How can I fix that?
Any ideas?
What do i need to
Thorsten Scherler wrote:
David Crossley wrote:
Thorsten Scherler wrote:
Hello devs,
trying to deploy the view and leather plugin I found a weird thing
happening:
Doing 'forrest run' brings the site rendered by the plugins, but doing
'forrest' will use the normal skin
Ross Gardler wrote:
David Crossley wrote:
I see that many of our plugins, even new ones, are not using
the naming convention.
... snipped from plugins/pluginInfrastructure.html
-
org.apache.forrest.plugin.PLUGINNAME
net.sf.forrestPlugins.PLUGINNAME
In addition the name
Ross Gardler wrote:
David Crossley wrote:
For various reasons, the ASF Board suggested to all projects
to remove authors from sources.
Apache Forrest follows that recommendation. Prior to each
release we scan the code to detect any license issues
and any author tags.
Om that case how
Ross Gardler wrote:
Thorsten Scherler wrote:
Ross Gardler wrote:
Thorsten Scherler wrote:
If somebody have some spare time and want to help us with the 2nd
generation skinning you can:
I will certainly be helping out, but not until 0.7 is released. Once
that is done this is right at
Dave Brondsema wrote:
[snip]
Furthering this idea, if we are versioning and storing docs-author and
site-author, do we really need to store them seperately? As you said,
this method would mean we won't have to restructure the
forrest_06_branch docs into two parts.
Good point. This
Ross Gardler wrote:
David Crossley wrote:
I started going through the plugins to fix any major issues
before the release.
The /plugins/ area of the website has some old *.zip for the
plugins that have been renamed ...
OpenOffice.org.zip
feeder.zip
htmlArea.zip
text-output.zip
Should
Ross Gardler wrote:
Author: rgardler
Date: Mon Apr 4 15:13:48 2005
New Revision: 160109
URL: http://svn.apache.org/viewcvs?view=revrev=160109
Log:
Deployment of org.apache.forrest.plugin.OpenOffice.org plugin (deployed by
'deploy' target of plugin build script)
Added:
Thorsten Scherler wrote:
Ross Gardler wrote:
Thorsten Scherler wrote:
If somebody have some spare time and want to help us with the 2nd
generation skinning you can:
I will certainly be helping out, but not until 0.7 is released. Once
that is done this is right at the top of my
Ross Gardler wrote:
David Crossley wrote:
Ross Gardler wrote:
How do people suggest I integrate the plugin docs with the main website
docs?
If they went under docs/plugins/$plugin-name/
then they will fit better with the versioning system
described above.
OK, that's where I'll put them
I have gone through our sources and removed the
few remaining author tags.
There are still some in some Cocoon sources that
have been imported at:
whiteboard/plugins/org.apache.forrest.plugin.Database/**/*.java
etc.
... not worried about those author tags, that is a Cocoon issue.
There are
Thorsten Scherler wrote:
David Crossley wrote:
Thorsten Scherler wrote:
David Crossley wrote:
You will see the plugin get rendered by 'forrest' with the pelt skin
in
build/site. If you now turn to 'forrest run' instance you find a
complete different skin.
I
Thorsten Scherler wrote:
Author: crossley
Date: Sun Apr 10 07:06:29 2005
New Revision: 160775
URL: http://svn.apache.org/viewcvs?view=revrev=160775
Log:
Enable changes.html and todo.html to also be in subdirectories.
Use relative location of images directory obtained via dotdots
Author: thorsten
Date: Fri Apr 8 19:24:54 2005
New Revision: 160651
URL: http://svn.apache.org/viewcvs?view=revrev=160651
Log:
Renamed leather to viewHelper. Cleaned the view plugin from not needed code.
added documentation to both plugins.
Added:
David Crossley wrote:
Ross Gardler wrote:
How do we link from the main docs-author (or site-author?) part of the site?
If we use docs/plugins/ then it will intergrate easily.
With the final scheme, we now need to put the generated
plugins docs in the forrest/site repository under
the /0.7
Sorry everyone. That was me again. I was tweaking
the .htaccess on the server to experiment, rather than
via SVN. Normally i would see my mistakes immediately
but due to the rsync delay to ajax, i didn't. Then i
forgot to check. Thanks to Joshua.
--David
Ross Gardler wrote:
As has been agreed all plugins are to be renamed so that they conform
with our naming convention. However, is the naming convention right?
Currently we say:
org.apache.forrest.plugin.NAME-input
org.apache.forrest.plugin.NAME-output
Juan Jose Pablos wrote:
Hi,
On http://forrest.apache.org/forrest-issues.html. I think that anoter
words for describe open issues for upcomming release would make more
sence.
What about Release issues?
Yes, i agree.
This document is an anomaly. It is currently at the top-level,
yet it
Author: rgardler
Date: Tue Apr 12 04:07:29 2005
New Revision: 161039
URL: http://svn.apache.org/viewcvs?view=revrev=161039
Log:
create a plugins index page
Modified:
forrest/trunk/site-author/content/xdocs/docs/plugins/pluginInfrastructure.xml
Arik Kfir wrote:
Should I file a JIRA on this (RFE)?
Yes please.
--David
Mark Eggers wrote:
After being away from using Forrest for a while, I decided to give it
another shot.
I am working on creating a large How To site, and hence my interest in
the How To DTD.
I noticed that the FAQ section of the How To V 2.0 DTD wasn't getting
translated using the seeded
Mark Eggers wrote:
After being away from using Forrest for a while, I decided to give it
another shot.
I am working on creating a large How To site, and hence my interest in
the How To DTD.
I noticed that the FAQ section of the How To V 2.0 DTD wasn't getting
translated using the seeded
Mark Eggers wrote:
David Crossley wrote:
Hey, that was a clever way to demonstrate a fix,
to tweak the sitemap to call a copy of the xsl.
Thanks, I was just following the pattern that's being used.
However, if you are using svn, then you could just change
the actual file and send
Mark Eggers wrote:
David Crossley wrote:
I'll try svn diff for my next submission (making faqs v2.0 consistent
with document v2.0 and howto v2.0 I think).
Hmm, i am not clear what you mean by that.
I noticed that there are only head definitions for howto and document
DTDs. When
A while ago we discussed our description of Forrest
and concluded that it was a bit limiting.
Actually trying to concisely summarise Forrest
is a very difficult task.
Here is what is was ...
Apache Forrest is an XML standards-oriented documentation framework
based upon Apache
Thorsten Scherler wrote:
Seems to be that I am the first one in trying to do it.
I just did some testing, but I actually I get
Message: null
Description: No details available.
Sender: org.apache.cocoon.servlet.CocoonServlet
Source: Cocoon Servlet
Request URI
Ross Gardler wrote:
David Crossley wrote:
A while ago we discussed our description of Forrest
and concluded that it was a bit limiting.
Actually trying to concisely summarise Forrest
is a very difficult task.
[ snip ]
Two points, one a possible addition, the other a possible red herring
Brett Presnell wrote:
Ross Gardler [EMAIL PROTECTED] writes:
Brett Presnell wrote:
[ snip ]
Getting better, but I don't like the last sentence because it sounds
like a document collection generated from the command line would be
deployed with an automated robot, and I think you mean this
Taking the comments into account, we now have this ...
Apache Forrest is a standards-based documentation framework
which uses Apache Cocoon. Forrest emphasises separation of
presentation and content, using a plugin architecture to
transform and aggregate various input sources into
Ferdinand Soethe wrote:
I know this has come up before, but I'm not sure which of the info in
old threads is still relevant today so I'll ask again:
If you remind us what came up before, then we might be able
to tell you if still relevant.
Why does Forrest expect unique element names in
Ross Gardler wrote:
I'm no expert when it comes to catalogs and it's late so I am not going
to try and fix this now. Perhaps someone can point me at the right docs
somewhere on the web to tell me how to do this when I return to it
tomorrow afternoon (GMT).
My question is simple how do I
Ross Gardler wrote:
From my blog
(http://www.jroller.com/page/rgardler/20050421#commercial_appreciation_of_open_source
)
Matthew Langham often posts on the relationships between Open Source
projects and commercial organisations profiting from those projects.
Usually I find myself
Ross Gardler wrote:
David Crossley wrote:
Ferdinand Soethe wrote:
I know this has come up before, but I'm not sure which of the info in
old threads is still relevant today so I'll ask again:
If you remind us what came up before, then we might be able
to tell you if still relevant.
Any
I don't understand what you mean Ross. It already works for me,
the catalog entity resolver finds the local status DTD.
That can be proved that by changing the publicIdentifier
in status.xml to be deliberately broken, then it fails
as it should,
e.g. ... PUBLIC -//APACHE//DTD Status Foo-Bust
Ferdinand Soethe wrote:
David Crossley wrote:
I know this has come up before, but I'm not sure which of the info in
old threads is still relevant today so I'll ask again:
If you remind us what came up before, then we might be able
to tell you if still relevant.
DC Any answer
Ross Gardler wrote:
David Crossley wrote:
Ross Gardler wrote:
[ snip ]
I just verified I was at the latest release of Forrest, and did a clean
build (somehow I always forget to do that). But no change.
I double-checked again :-) that i have no un-committed files.
Perhaps you should try
I noticed on yesterday's 'svn update' that the
file webapp/WEB-INF/jtidy.properties was removed.
Yet i did see any commit message for that.
Now i am getting broken build in site-author
where it complains abou missing jtidy.properties
Any clues anyone?
--David
Ross Gardler wrote:
David Crossley wrote:
Recently i upgraded the entity resolver jar to a new
pre-release. Today i reverted that, so lets see if that
helps you.
Bingo!!! That does the trick.
For reference I am using Windows XP SP2 + Cygwin
Thanks for your help.
Oh, a bug. Sorry
Ferdinand Soethe wrote:
Sorry to join in so late. I was busy writing a paper describing Forrest
in German so in a way warming up for this :-)
I commend all of you for the progress visible when following this
thread. Most changes seemed to make the message clearer for ordinary
users.
Ferdinand Soethe wrote:
David Crossley wrote:
DC I think that it confuses people. Forrest can have multiple
DC source input formats, so this description conflicts with that.
I changed that back an forth a couple of times and finally took
'formats' out. Not just because the repetition
Ross Gardler wrote:
In that case I may have liked it because of the work Ferdinand and I are
doing on the ApacheCon presentation. I'm used to his words etc.
Stick to the original if this new one is confusing.
We can enhance the original. Ferdinand, i don't mean
to dismiss any of your
Ferdinand Soethe wrote:
Ross Gardler wrote:
RG I'd say stick with what we had
I agree. No point in having a lengthy discussion. To a large extent it
depends on the perspective you have and the background you come from.
So if you feel happier with it, just ignore my proposal and
stick
The Project Management Committee (PMC) for Apache Forrest
has asked Johannes Schaefer to become a committer and a
member of the PMC and he has accepted.
Johannes has obviously been using Forrest in a demanding
environment and is uncovering a number of important bugs,
documenting them in the issue
Cyriaque Dupoirieux wrote:
http://forrest.apache.org/0.7/docs/plugins/index.html
description of org.apache.forrest.plugin.input.dtdx Plugin :
... generate automa*g*ically some ...
The original author perhaps intended it as a joke.
http://forrest.apache.org/0.7/docs/dtd-docs.html
Cyriaque Dupoirieux wrote:
David Crossley a ?crit :
It also led to a brilliant idea about a regular bug day
which we should instigate soon.
When will we decide the regular bug day ?
How about we decide now.
I reckon once per month. Perhaps we can do it
more often if it works.
Which day
Ross, would you please take this up on [EMAIL PROTECTED]
This is the first time that i have heard discussion of
this SISSL license.
The difficulty that i see is how to add their Exhibit A.
For each file that you add, is that file to be standalone
or is each file a mixture of other work plus our
Ferdinand Soethe wrote:
Ross Gardler wrote:
RG This only affects sites when generated from the command line interface
RG (i.e. not when doing 'forrest run' or running as a webapp). To change it
RG in non command line you need to override the sitemap redirects.
RG I haven't read all your
Ross Gardler wrote:
Dave Brondsema wrote:
I'd say we should find out why the HTML is generated with inconsistent
line endings in the first place.
True.
I did a little testing, here's what I have discovered so far:
- any file that is processed by XSLT has the line endings problem
-
Torsten Schlabach wrote:
Nicola,
My goal is to put a live Forrest on ASF infrastructure instead of the
bot and have that serve all Forrest-based sites in Apache, comprising
Lenya.
Sounds good. Let me know if you need any help or input from us.
Are you subsribed to [EMAIL PROTECTED]
Ross Gardler wrote:
Ferdinand Soethe wrote:
David Crossley wrote:
DC If people want to do many whitespace changes, then please
DC try to keep them as separate commits to real content changes.
DC Committers have a duty to monitor the commits. When the
DC changes are mixed with whitespace
Ferdinand Soethe wrote:
David Crossley wrote:
DC It seemed to also do other reformatting. Be sure to do 'svn diff'
DC before committing.
Should I revert it back to the original whitespaceing and insert my
changes again?
No. I was just making sure that people knew the problems
Nicola Ken Barozzi wrote:
One thing I like about Forrest is that it's not only a static site
generation engine, but it's capable of serving the site live. Changes
are instantaneous, bandwith is perserved, and dynamic content can be
employed.
IMHO every Apache project that produces
Ross Gardler wrote:
David Crossley wrote:
Ross Gardler wrote:
David Crossley wrote:
I presume that this does not happen when you do 'forrest' to
build the plugin's docs, rather than doing 'ant docs'.
I had also assumed that, however it turns our to be incorrect.
In fact doing forrest
Diwaker Gupta wrote:
David Crossley wrote:
Are there any others from our development community that can
be added?
Well, my homepage is forrest generated
(http://resolute.ucsd.edu/diwaker) -- but its a personal/academic web
site, so I'm not sure if it qualifies for listing. If it does, do
Ross Gardler wrote:
David Crossley wrote:
Ross Gardler wrote:
I think we need to change the website so that we have an index.html page
that is consitent through all releases. However, I do not claim to fully
understand the Google ranking algorithm, so please correct me if I am
wrong
Ferdinand Soethe wrote:
Whenever I start explaining Forrest, I stumble into the problem of
crossing terminology borders, using terms like 'build', 'compile',
'run' for the Forrest program and at the same time applying them to
Forrest projects.
If this is not just my ignorance about the
scott hutinger wrote:
If a newer version of xerces were in place, I would say yes. But that
is not the case, as xerces has not released anything as of yet.
That isn't truly Ant related, but just one point of view.
We can use pre-releases of these supporting products, we don't
need to wait
Antonio Gallardo wrote:
David Crossley dijo:
scott hutinger wrote:
If a newer version of xerces were in place, I would say yes. But that
is not the case, as xerces has not released anything as of yet.
That isn't truly Ant related, but just one point of view.
We can use pre-releases
Nicola Ken Barozzi wrote:
Antonio Gallardo wrote:
David Crossley dijo:
Antonio Gallardo wrote:
...
I suggest to add ant 2.6.3. It brings better java 1.5 support and lot of
fixes:
http://cvs.apache.org/viewcvs.cgi/ant/WHATSNEW?only_with_tag=ANT_163view=markup
Okay, i for one, am happy
Antonio Gallardo wrote:
David Crossley dijo:
Nicola Ken Barozzi wrote:
Antonio Gallardo wrote:
David Crossley dijo:
Antonio Gallardo wrote:
...
I suggest to add ant 2.6.3. It brings better java 1.5 support and lot
of
fixes:
http://cvs.apache.org/viewcvs.cgi/ant/WHATSNEW
Juan Jose Pablos wrote:
Hi,
I am cleaning up the libraries for the next release, and I would like to
know if we need these libraries:
castor-0.9.5.3-xml.jar
Castor is for xsp maybe?, I thought that we did not want to put xsp
support on forrest. Do we need it?
nekodtd-0.1.11.jar
1 - 100 of 3078 matches
Mail list logo
