this
statement, and the result would no longer be Cocoon. This does not
imply that any architecture improvements are unimportant, just that
the primary purpose must be honored. Some suggestions (e.g. changing
the programming language) should require creating a new project.
solprovider
Where is the current development work? (Research favors Canada.)
Would you prefer someone local?
Are you expecting 100% telecommuting?
What currency is the pay?
Cocoon (and most Apache projects) are used in many countries. The
best candidate might be distant; avoiding the hassle of
on 1.2 incompatible with 1.4 was named 1.3.
solprovider
On 8/4/08, Carsten Ziegeler [EMAIL PROTECTED] wrote:
Reinhard Pötz wrote:
Cocoon 2.2 already uses cocoon-pipeline-api-1.0.0,
cocoon-sitemap-api-1.0.0., etc.
Yes, I know - this complicates things a little bit.
What concrete name
[
https://issues.apache.org/jira/browse/COCOON-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12570795#action_12570795
]
solprovider commented on COCOON-1529:
-
The i18n transformer requires users to add
with decision-making closer to the effect. The differentiation
only exists due to Cocoon storing the PipelineEvents for the second
phase of processing.
Solprovider and I already discussed this on the users mailing list [1] -
though it seems he does not agree to my reasoning. My main point
child nodes before passing
control to the PipelineEvent nodes.
This affects Cocoon-2.1 through Cocoon-2.1.11. Has this been fixed in
Cocoon-2.2?
Thoughts?
solprovider
to 2.2? Why? What is required
for the question to be removed?
solprovider
not be considered a blocker
since the the formatting has been wrong in every release of Cocoon
that I have seen.
I did not check the tar.gz. Anybody understanding tar.gz files is
also likely to know the dos2unix command.
solprovider
[
https://issues.apache.org/jira/browse/COCOON-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
solprovider closed COCOON-2074.
---
Resolution: Fixed
Fix Version/s: (was: 2.1.11)
2.1.12-dev (Current SVN
found a problem.
f) Thank you for your work.
Thank you for your time and patience with me,
solprovider
[
https://issues.apache.org/jira/browse/COCOON-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12555064
]
solprovider commented on COCOON-2074:
-
This version excludes the filtered files from the unfiltered copy
[
https://issues.apache.org/jira/browse/COCOON-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
solprovider reopened COCOON-2074:
-
The commit was reverted due to concerns about filtering damaging binary files.
Build ignores
[
https://issues.apache.org/jira/browse/COCOON-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554955
]
solprovider commented on COCOON-2074:
-
This version copies the directory with filtering=off, then overwrites
version dies from lack of use. A
demonstration is in progress.
solprovider
[
https://issues.apache.org/jira/browse/COCOON-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554964
]
solprovider commented on COCOON-2074:
-
Vadim Gritsenko suggested on the Dev ML to use excludes in the copy all
where the application creation instructions
belong. Should this discussion continue?
solprovider
as soon as I learned a Cocoon
release was planned. This may be the final release of Cocoon-2.1 so
every change must be committed or discarded.
solprovider
[
https://issues.apache.org/jira/browse/COCOON-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
solprovider closed COCOON-2074.
---
Resolution: Fixed
Fix Version/s: 2.1.11-dev (Current SVN
[
https://issues.apache.org/jira/browse/COCOON-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
solprovider closed COCOON-2067.
---
Resolution: Fixed
Fix Version/s: 2.1.11-dev (Current SVN
to apply the patch?
Someone should check if this bug affects Cocoon-2.2,
Thank you,
solprovider
[
https://issues.apache.org/jira/browse/COCOON-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
solprovider updated COCOON-1354:
Priority: Critical (was: Minor)
Urgency: Urgent
Affects Version/s
[
https://issues.apache.org/jira/browse/COCOON-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535819
]
solprovider edited comment on COCOON-1354 at 10/17/07 8:11 PM:
---
This is critical
component. Where do these suggestions
belong?
solprovider
[
https://issues.apache.org/jira/browse/COCOON-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502099
]
solprovider commented on COCOON-2068:
-
Changing this would cause more problems that fixing the environment. My
[
https://issues.apache.org/jira/browse/COCOON-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
solprovider closed COCOON-2068.
---
Resolution: Invalid
This would cause more problems than it might solve.
Add failover for loading
Versions: 2.1.10
Reporter: solprovider
Priority: Minor
The build process carefully adds each of the standard files in the webapp
directory. New applications are not included in the build process. The
improvement copies the entire directory. I did not notice any files needing
[
https://issues.apache.org/jira/browse/COCOON-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499904
]
solprovider commented on COCOON-2068:
-
I found many other issues trying to create a Cocoon PAR for SAP Portal
: 2.1.10
Reporter: solprovider
Priority: Minor
The ClassLoader from currentThread.getContextClassLoader() was unable to
retrieve classes in my environment. Add fallback to standard Java class
loading.
NOTE: The two set lines work in either order. I prefer trying standard
[
https://issues.apache.org/jira/browse/COCOON-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
solprovider updated COCOON-2068:
Description:
The ClassLoader from currentThread.getContextClassLoader() was unable to
retrieve
[
https://issues.apache.org/jira/browse/COCOON-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498669
]
solprovider commented on COCOON-2068:
-
Hi Carlsten,
I changed the code and comment for this entry after
Components: * Cocoon Core
Affects Versions: 2.1.10
Reporter: solprovider
Priority: Trivial
The error message in the last line of the code below misnames the parameter as
'configuration' instead of 'configurations'.
The easy fix is to add an 's'.
A better fix
31 matches
Mail list logo