On Dec 30, 2007 5:35 PM, Reinhard Poetz [EMAIL PROTECTED] wrote:
... o make Cocoon pipelines/sitemaps ready for the usage in OSGi
environments...
The Sling project would very probably be interested in this. We're not
there yet, but once we start working on different output renderings in
Carsten Ziegeler pisze:
Hi,
i've put up the 2.1.11 release at:
http://people.apache.org/~cziegeler/releases/cocoon/
please check, verify and cast your votes.
Works fine on openSUSE 10.3 with Java 1.6.0_03.
Here's my late:
+1!
--
Grzegorz Kossakowski
Committer and PMC Member of Apache
On Jan 8, 2008, at 1:34 AM, Ralph Goers wrote:
How hard would it be to create an archetype to create the pom
automatically? Users would then either just build and run it or edit
it first to remove stuff they don't care about.
Telling them to create pom.xml inheriting from
Vadim Gritsenko pisze:
On Jan 8, 2008, at 1:34 AM, Ralph Goers wrote:
How hard would it be to create an archetype to create the pom
automatically? Users would then either just build and run it or edit
it first to remove stuff they don't care about.
Telling them to create pom.xml inheriting
Hi,
where has our mirror.html aka the download page gone? I want to add our
latest release. It would also be great to directly have a download link
on our top page at cocoon.apache.org.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
We did it again :)
Many thanks for all your help to get another release out of the door!
There were some issues raised in this thread and I think we should try
to fix them for the next release.
It would be great, if those of you who found the problems could open a
jira issue.
Thanks
Carsten
The vote for releasing 2.1.11 as assembled here
http://people.apache.org/~cziegeler/releases/cocoon/
past successfully with
7 +1 votes from Grzegorz Kossakowski, Jeroen Reijn, Bertrand Delacretaz,
David Crossley, Felix Knecht, Joerg Heinicke, and
Carsten Ziegeler
No other votes were cast.
Carsten Ziegeler pisze:
We did it again :)
Yes, yes! :)
Next step should be Cocoon 2.2. :)
Many thanks for all your help to get another release out of the door!
Carsten, many thanks for taking care of release process.
There were some issues raised in this thread and I think we should try
Carsten Ziegeler pisze:
Hi,
where has our mirror.html aka the download page gone? I want to add our
latest release. It would also be great to directly have a download link
on our top page at cocoon.apache.org.
If you give me a link I can add it to the main page. Or if you want to do it
[EMAIL PROTECTED] pisze:
Author: rgoers Date: Sun Jan 6 01:35:48 2008 New Revision: 609282
URL: http://svn.apache.org/viewvc?rev=609282view=rev Log: Created
XPathXMLFileModule to fix
problems with XMLFileModule. Added getAttributeValue to JXPathHelper and
changed all references
to
Rats. Sorry. I was trying to squeeze that in when I had free time and I
just get so used to skipping the tests since every time I've tried to
run them my build has failed. I shouldn't have assumed they were still
not working.
To be honest when I was working on this I was just very frustrated
Come to think of it, although it is a pretty lame excuse, the reason I
ran with tests disabled is I just cut and pasted the command line from
the README - I can never remember the format since -P allblocks isn't
something you normally do with maven. Perhaps the README should be
changed? It
Carsten Ziegeler wrote:
Hi,
where has our mirror.html aka the download page gone? I want to add our
latest release.
Yeah i wondered that too. When testing the 2.1.11 release i went
there to find the instructions about verify checksums and signatures.
Because the mirror.html is missing, the
OK. So using PreparedVariableResolver fixes the problems with the
dependencies. I've committed the change. But I am still getting 1 unit
test failure in cocoon core - CachingSourceTestCase is failing on line
88. How could this possibly have anything to do with what I changed?
Ralph Goers
On 08.01.2008 22:59, Ralph Goers wrote:
But I am still getting 1 unit
test failure in cocoon core - CachingSourceTestCase is failing on line
88. How could this possibly have anything to do with what I changed?
Since our Continuum build now runs successful it seems to be an issue
with your
Well, that just means I'm going to be up a while trying to figure out
why. But thanks. It's good to know that it is working again. I also
verified that the XPathXMLFileModule sample still works, so that is good.
Then I just need to write some unit tests for it. I modified my own
copy of
On 08.01.2008 23:23, Joerg Heinicke wrote:
But I am still getting 1 unit test failure in cocoon core -
CachingSourceTestCase is failing on line 88. How could this possibly
have anything to do with what I changed?
Since our Continuum build now runs successful it seems to be an issue
with
On 08.01.2008 16:07, Carsten Ziegeler wrote:
The vote for releasing 2.1.11 as assembled here
http://people.apache.org/~cziegeler/releases/cocoon/
past successfully with
7 +1 votes from Grzegorz Kossakowski, Jeroen Reijn, Bertrand Delacretaz,
David Crossley, Felix Knecht, Joerg Heinicke, and
On 08.01.2008 14:45, Grzegorz Kossakowski wrote:
We were not shipping samples because samples should depend on released
artifacts, only. Anyway, I
agree that we need to find a way for distribution of our samples.
However, I wonder how we will treat them? As official released packages with
I put slashdot.org in my browser on that machine and it took quite a
while to display but it did. I notice that the unit tests pause for
quite a while on that test. I'm not sure why.
Anyway, I changed the 5 to 30 and it still fails. Should unit tests
really be going to external resources?
Maybe we are on the same page, but I'm unclear what you mean by
include. A cocoon release should consist of nothing more than
deploying artifacts to the maven repository. End users should be getting
the release by specifying the version number of the release in the
archetypeVersion. To create
On 09.01.2008 00:11, Ralph Goers wrote:
Maybe we are on the same page, but I'm unclear what you mean by
include. A cocoon release should consist of nothing more than
deploying artifacts to the maven repository. End users should be getting
the release by specifying the version number of the
No. We could take advantage of http://maven.apache.org/ant-tasks.html to
create various ant scripts to do that. However, since I'm still not
sure what this supposed support for non-maven builds really looks like
it is hard to have a good answer to the question.
Ralph
Joerg Heinicke wrote:
Joerg Heinicke wrote:
On 08.01.2008 16:07, Carsten Ziegeler wrote:
The vote for releasing 2.1.11 as assembled here
http://people.apache.org/~cziegeler/releases/cocoon/
past successfully with
7 +1 votes from Grzegorz Kossakowski, Jeroen Reijn, Bertrand
Delacretaz, David Crossley, Felix
David Crossley wrote:
Carsten Ziegeler wrote:
Hi,
where has our mirror.html aka the download page gone? I want to add our
latest release.
Yeah i wondered that too. When testing the 2.1.11 release i went
there to find the instructions about verify checksums and signatures.
Because the
I changed the expire time from 5 to 10 and then changed the sleep time
to 11000. That got the unit test to pass.
I'm not sure what to do about this. Having a unit test rely on an
external resource is very bad practice just for this reason. Worse, if I
didn't have an active internet connection
26 matches
Mail list logo
