Luca Morandini wrote:
Reinhard Poetz wrote:
I've prepared the artifacts for the release of Cocoon 2.2 final.
There is much room for improvement in the doc though: don't you think it
should be improved before release ?
It would be great to have better docs, but honestly who is going to
Carsten Ziegeler wrote:
Luca Morandini wrote:
Reinhard Poetz wrote:
I've prepared the artifacts for the release of Cocoon 2.2 final.
There is much room for improvement in the doc though: don't you think
it should be improved before release ?
It would be great to have better docs, but
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
Luca Morandini wrote:
Reinhard Poetz wrote:
I've prepared the artifacts for the release of Cocoon 2.2 final.
There is much room for improvement in the doc though: don't you
think it should be improved before release ?
It would be great to
Dev at weitling wrote:
Sorry, I can't agree. Cocoon still has the same fault as many
open-source products: A lack of documentation.
I don't know if GSoC is for docs, too, but it is really, really
necessary to improve docs.
It's still the same Catch-22: To write docs you need to understand the
Carsten Ziegeler wrote:
Dev at weitling wrote:
Sorry, I can't agree. Cocoon still has the same fault as many
open-source products: A lack of documentation.
I don't know if GSoC is for docs, too, but it is really, really
necessary to improve docs.
It's still the same Catch-22: To write docs
Carsten Ziegeler wrote:
It would be great to have better docs, but honestly who is going to
write them?
Some (most ?) of it has been already written, it's just a matter of
copying it from Javadoc (or 2.1 docs pages) to the 2.2 ones, and check
its currentness, of course.
We might not get
Hi,
(Changing subject, starting new thread. Please, when an email says
'this thread is for votes only', try to respect that!)
On 03/04/2008, Luca Morandini [EMAIL PROTECTED] wrote:
Carsten Ziegeler wrote:
We might not get some new users because of bad docs, but we might get
people really
Luca Morandini schrieb:
Carsten Ziegeler wrote:
It would be great to have better docs, but honestly who is going to
write them?
Some (most ?) of it has been already written, it's just a matter of
copying it from Javadoc (or 2.1 docs pages) to the 2.2 ones, and check
its currentness, of
Carsten Ziegeler wrote:
Dev at weitling wrote:
Sorry, I can't agree. Cocoon still has the same fault as many
open-source products: A lack of documentation.
I don't know if GSoC is for docs, too, but it is really, really
necessary to improve docs.
It's still the same Catch-22: To write docs
Hi
On 02/04/2008, Reinhard Poetz [EMAIL PROTECTED] wrote:
mvn
org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create
-DarchetypeGroupId=org.apache.cocoon
-DarchetypeArtifactId=cocoon-22-archetype-block
-DarchetypeVersion=1.0.0
-DgroupId=com.mycompany
Hi,
On 02/04/2008, Reinhard Poetz [EMAIL PROTECTED] wrote:
Find instructions about how you can test in a seperate mail. Report your
findings to that thread and use this one for voting only. Thanks!
This majority vote stays open for 72 hours.
+1
Andrew.
[
https://issues.apache.org/jira/browse/COCOON-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585165#action_12585165
]
Ellis Pritchard commented on COCOON-2063:
-
Anyone fancy applying the patches?
Grzegorz Kossakowski wrote:
Hello,
I've played with JNet for a while trying to integrate it with SSF and run
into many troubles.
First of all, I'm not sure if I understand whole concept correctly. Do I
understand correctly that JNet provides SourceURLStreamHandlerFactory class
that acts just
Reinhard Poetz pisze:
Grzegorz Kossakowski wrote:
Hello,
I've played with JNet for a while trying to integrate it with SSF and run
into many troubles.
First of all, I'm not sure if I understand whole concept correctly. Do I
understand correctly that JNet provides SourceURLStreamHandlerFactory
Reinhard Poetz pisze:
I've prepared the artifacts for the release of Cocoon 2.2 final. See the
list of
all proposed artifacts below.
You can find the staged files for all modules (sources, binaries, javadocs,
checksums, gpg signatures) at
- http://people.apache.org/builds/cocoon/
(Maven
Andreas Hartmann pisze:
Luca Morandini schrieb:
Carsten Ziegeler wrote:
It would be great to have better docs, but honestly who is going to
write them?
Some (most ?) of it has been already written, it's just a matter of
copying it from Javadoc (or 2.1 docs pages) to the 2.2 ones, and check
Dev at weitling pisze:
Despite my sometimes dumb question here on the list I know Cocoon is
really cool and still improving. But without good docs the developers
and the users separate more and more. There are many people who want to
contribute to Cocoon, but most of them do only have spare
Andrew Savory pisze:
Hi,
(Changing subject, starting new thread. Please, when an email says
'this thread is for votes only', try to respect that!)
On 03/04/2008, Luca Morandini [EMAIL PROTECTED] wrote:
Carsten Ziegeler wrote:
We might not get some new users because of bad docs, but we might
Reinhard Poetz pisze:
The proposed release artifacts of all the modules that we vote on (see the
seperate voting thread) are available at
http://people.apache.org/builds/cocoon/
The easiest way to test the artifacts is by adding a cocoon-staging
profile to
your ~/.m2/settings.xml:
On Apr 3, 2008, at 2:58 PM, Grzegorz Kossakowski wrote:
Reinhard Poetz pisze:
Why do we have to replace the blockcontext: protocol at all?
Take a look at its current source code. There is no such a thing
like blockcontext: protocol implementation at the moment.
In my [RT] mail I explained
[
https://issues.apache.org/jira/browse/COCOON-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Heinicke updated COCOON-2063:
--
Affects version (Component): Parent values: Blocks: HTML(10168). Level 1
values:
[
https://issues.apache.org/jira/browse/COCOON-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Heinicke updated COCOON-2063:
--
Affects Version/s: 2.2
NekoHTMLTransformer needs to set the default-encoding of the current
On 03.04.2008 23:33, Jörg Heinicke (JIRA) wrote:
With Mac OS X I also have no access to the source code of the JDK.
Which makes me wonder again how to do serious Java development with Mac
OS X. I know a few of you guys are using Mac OS X. How do you do it?
Whenever I start this I get
Grzegorz Kossakowski wrote:
[*] The 1.0.0 releases are still missing but provided for a version
that hasn't
been mirgrated to Spring. These artifacts will hopefully follow soon.
Any reason for such a weird practice marked with [*]? It's really
questionable to release 1.1.0 before 1.0.0...
Grzegorz Kossakowski wrote:
Why do we have to replace the blockcontext: protocol at all?
Take a look at its current source code. There is no such a thing like
blockcontext: protocol implementation at the moment.
Therefore I'm asking ...
In my [RT] mail I explained how we could possibly to
25 matches
Mail list logo
