Jean-Christophe Kermagoret wrote:
Hi,
I made the following :
> svn update (so I get the last svn from trunk - 22 version)
cd trunk
mvn -P allblocks -Dmaven.test.skip=true install
cd core/cocoon-webapp
mvn jetty:run
Everything went fine : I get the sample page
Then, I decided to create a new b
Grzegorz Kossakowski wrote:
Examples you provided do not apply to the situation I want to discuss.
In 2.1 times we were shipping all dependencies ourselves so there is
no problem of dependency resolution.
I was talking about the situation when we want to release some early
alpha that has _s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kossakowski wrote:
> [EMAIL PROTECTED] pisze:
>> Author: giacomo
>> Date: Tue Jun 5 05:04:42 2007
>> New Revision: 544460
>>
>> URL: http://svn.apache.org/viewvc?view=rev&rev=544460
>> Log:
>> attempt to fix wrong prefix for servlet-service
Hi,
I made the following :
> svn update (so I get the last svn from trunk - 22 version)
cd trunk
mvn -P allblocks -Dmaven.test.skip=true install
cd core/cocoon-webapp
mvn jetty:run
Everything went fine : I get the sample page
Then, I decided to create a new block with archetype in a test direct
Grzegorz Kossakowski (JIRA) pisze:
[
https://issues.apache.org/jira/browse/COCOON-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski closed COCOON-2073.
Resolution: Fixed
Thanks for report. I updated
[
https://issues.apache.org/jira/browse/COCOON-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski closed COCOON-2073.
Resolution: Fixed
Thanks for report. I updated please test and close the issue.
>
Vadim Gritsenko pisze:
I wanted to know what are our rules. Do we:
- want to have such a internal releases
I'd avoid using word "release" for this as it has some legal
implications and we would get chewed up for using it :)
Ah, I'm young committer so forgive me that I omit legal implications
Grzegorz Kossakowski wrote:
Vadim Gritsenko pisze:
Grzegorz Kossakowski wrote:
On the other hand, milestones are just our internal releases and I
think we can live with these gaps.
No, they are not internal:
http://cocoon.apache.org/2.1/changes.html
http://archive.apache.org/dist/cocoon/S
[
https://issues.apache.org/jira/browse/COCOON-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski updated COCOON-2073:
-
Assignee: Grzegorz Kossakowski
Description:
Current ajax block includes d
[EMAIL PROTECTED] pisze:
Author: giacomo
Date: Tue Jun 5 05:04:42 2007
New Revision: 544460
URL: http://svn.apache.org/viewvc?view=rev&rev=544460
Log:
attempt to fix wrong prefix for servlet-services
Hi Giacomo, thanks for taking care of it. However I would be grateful if you mention in log m
Vadim Gritsenko pisze:
Grzegorz Kossakowski wrote:
On the other hand, milestones are just our internal releases and I
think we can live with these gaps.
No, they are not internal:
http://cocoon.apache.org/2.1/changes.html
http://archive.apache.org/dist/cocoon/SOURCES/
http://repo1.maven.
Hi,
The follow instructions still points to the our old bugzilla tracking
system:
http://cocoon.apache.org/link/livesites-2.1.html#How+to+get+listed
Best Regards,
Antonio Gallardo.
[EMAIL PROTECTED] wrote:
Vadim Gritsenko <[EMAIL PROTECTED]> writes:
Thanks!
I got it going, but I needed to change a file within one of the jar
files:
META-INF/cocoon/avalon/cocoon-core-xslt-saxon.xconf
in
/maven-temp-repository/org/apache/cocoon/cocoon-pipeline-components/1.0.0-RC1/cocoon-pip
Vadim Gritsenko <[EMAIL PROTECTED]> writes:
Thanks!
I got it going, but I needed to change a file within one of the jar
files:
META-INF/cocoon/avalon/cocoon-core-xslt-saxon.xconf
in
/maven-temp-repository/org/apache/cocoon/cocoon-pipeline-components/1.0.0-RC1/cocoon-pipeline-components-1.0.0-RC1.
[EMAIL PROTECTED] wrote:
This recipy was used for cocoon 2.1:
http://wiki.apache.org/cocoon/Saxon
Does it still apply?
The page is incorrect in suggesting that there is a need to modify Saxon jar,
see [1]. But other than that, Cocoon 2.2 is mostly backward compatible with
Cocoon 2.1, and we
This recipy was used for cocoon 2.1:
http://wiki.apache.org/cocoon/Saxon
Does it still apply?
--
Joakim Verona
Grzegorz Kossakowski wrote:
On the other hand, milestones are just
our internal releases and I think we can live with these gaps.
No, they are not internal:
http://cocoon.apache.org/2.1/changes.html
http://archive.apache.org/dist/cocoon/SOURCES/
http://repo1.maven.org/maven2/org/apache/co
[
https://issues.apache.org/jira/browse/COCOON-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Trieloff closed COCOON-1941.
-
Resolution: Fixed
Fix Version/s: 2.2-dev (Current SVN)
2.1.11-dev (Curr
On 25 May 2007, at 16:07, Grzegorz Kossakowski wrote:
As for serializing to XHTML. First of all you must be aware that
browsers will not treat XHTML as XHTML pages because of content
type set to "text/html" instead of "text/xhtml". It is done so
because IE (sigh) does not understand "text/
[
https://issues.apache.org/jira/browse/COCOON-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated COCOON-1941:
--
Status: On Hold (was: Continued)
Ok, an endless loop of feedback ;-) Here is
[
https://issues.apache.org/jira/browse/COCOON-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated COCOON-1941:
--
Status: Continued (was: On Hold)
Hmm, let's look what happens after the feedb
[
https://issues.apache.org/jira/browse/COCOON-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated COCOON-1941:
--
Status: On Hold (was: Open)
This issues is already done, but I have no Jira k
Upgrade to dojo 0.4.3 (security fixes!)
---
Key: COCOON-2073
URL: https://issues.apache.org/jira/browse/COCOON-2073
Project: Cocoon
Issue Type: Improvement
Components: Blocks: Ajax
Affects Ve
23 matches
Mail list logo