Reinhard Poetz wrote:
The proposed modules have been accepted by 7 +1 votes and no negative
one. I'm going move the artifacts into the Apache Maven M2 sync
repository and also move the non-Maven artifacts to the Cocoon
distribution area.
When everything is available from the mirrors, I
It sounds like a good plan. Go ahead Carsten!
+1
Reinhard Poetz wrote:
Grzegorz Kossakowski wrote:
Carsten Ziegeler pisze:
We currently have the core xml module, separated into api, impl and a
special entity resolver. The dependencies of these modules are minimal
but unfortunately the impl
Hi,
as we plan to have independent releases of all the blocks, the core
modules etc. we should reduce the number of dependencies refering to
snapshots to a minimum.
Especially for the parent poms and references to apis - there is no need
to always release all parent poms, the api etc. just to
Hi,
I just came across the pipeline project in the commons sandbox.
http://commons.apache.org/sandbox/pipeline/
I didn't have a deeper look at it, but at least they are defining a
pipeline api. So it might be worth to have a look at it and see if we
could use that instead of defining or own.
Joerg Heinicke wrote:
On 02.04.2008 11:36, Reinhard Poetz wrote:
I've prepared the artifacts for the release of Cocoon 2.2 final.
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!
+1 Unfortunately
Additional components and features.
---
Key: COCOON-2195
URL: https://issues.apache.org/jira/browse/COCOON-2195
Project: Cocoon
Issue Type: Improvement
Components: Corona (experimental)
[
https://issues.apache.org/jira/browse/COCOON-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON-2195:
Attachment: patch.txt
Added patch.
Additional components and features.
I've just started to move the deployment of blocks into a ServletContextListener
and came across a (for me) unkown feature that gives access to the path of
blocks in Spring properties:
This feature was introduced by Carsten as part of this SVN commit
Reinhard Poetz wrote:
I've just started to move the deployment of blocks into a
ServletContextListener and came across a (for me) unkown feature that
gives access to the path of blocks in Spring properties:
This feature was introduced by Carsten as part of this SVN commit
Carsten Ziegeler pisze:
Hi,
as we plan to have independent releases of all the blocks, the core
modules etc. we should reduce the number of dependencies refering to
snapshots to a minimum.
Especially for the parent poms and references to apis - there is no need
to always release all parent
Joerg Heinicke pisze:
On 30.03.2008 20:08, Jörg Heinicke (JIRA) wrote:
[
https://issues.apache.org/jira/browse/COCOON-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Heinicke updated COCOON-2109:
--
Affects version
On Apr 10, 2008, at 3:31 AM, Carsten Ziegeler wrote:
Hi,
as we plan to have independent releases of all the blocks, the core
modules etc. we should reduce the number of dependencies refering to
snapshots to a minimum.
Especially for the parent poms and references to apis - there is no
Grzegorz Kossakowski pisze:
We should fix this link.
Done.
Does anyone has a good idea how to turn off our own Continuum instance completely so it does not
suck zone's resources?
--
Grzegorz
Vadim Gritsenko wrote:
On Apr 10, 2008, at 3:31 AM, Carsten Ziegeler wrote:
Hi,
as we plan to have independent releases of all the blocks, the core
modules etc. we should reduce the number of dependencies refering to
snapshots to a minimum.
Especially for the parent poms and references to
Grzegorz Kossakowski wrote:
Carsten Ziegeler pisze:
Hi,
as we plan to have independent releases of all the blocks, the core
modules etc. we should reduce the number of dependencies refering to
snapshots to a minimum.
Especially for the parent poms and references to apis - there is no
need
Carsten Ziegeler pisze:
The rule is easy: don't update if there is no reason to update. The only
module that might update to snapshost is the webapp that aggregates all
the various blocks as an example.
But for instance, if the api doesn't change, there is no need for anyone
using the api
[
https://issues.apache.org/jira/browse/COCOON-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587771#action_12587771
]
Grzegorz Kossakowski commented on COCOON-2195:
--
Thanks Steven for your work!
[
https://issues.apache.org/jira/browse/COCOON-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski reassigned COCOON-2195:
Assignee: Grzegorz Kossakowski
Additional components and features.
Grzegorz Kossakowski wrote:
Carsten Ziegeler pisze:
The rule is easy: don't update if there is no reason to update. The
only module that might update to snapshost is the webapp that
aggregates all the various blocks as an example.
But for instance, if the api doesn't change, there is no need
Carsten Ziegeler pisze:
Agreed. I would add one (quite obvious) rule: if some module gets
relesed and artifact is available at central other modules should
always update its dependencies ASAP. This applies to patch releases.
No, I don't think so :)
Example (it's fictional): we have the ajax
On Apr 10, 2008, at 4:01 PM, Carsten Ziegeler wrote:
Vadim Gritsenko wrote:
On Apr 10, 2008, at 3:31 AM, Carsten Ziegeler wrote:
Hi,
as we plan to have independent releases of all the blocks, the
core modules etc. we should reduce the number of dependencies
refering to snapshots to a
Reinhard Poetz wrote:
Reinhard Poetz wrote:
The proposed modules have been accepted by 7 +1 votes and no negative
one. I'm going move the artifacts into the Apache Maven M2 sync
repository and also move the non-Maven artifacts to the Cocoon
distribution area.
Should we also put the
[
https://issues.apache.org/jira/browse/COCOON-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587849#action_12587849
]
Steven Dolg commented on COCOON-2195:
-
Of course I can create smaller patches.
I'm
[
https://issues.apache.org/jira/browse/COCOON-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587850#action_12587850
]
Reinhard Poetz commented on COCOON-2195:
Grzegorz, if you don't mind I will take
Vadim Gritsenko wrote:
On Apr 10, 2008, at 4:01 PM, Carsten Ziegeler wrote:
Vadim Gritsenko wrote:
On Apr 10, 2008, at 3:31 AM, Carsten Ziegeler wrote:
Hi,
as we plan to have independent releases of all the blocks, the core
modules etc. we should reduce the number of dependencies refering
David Crossley wrote:
Reinhard Poetz wrote:
Reinhard Poetz wrote:
The proposed modules have been accepted by 7 +1 votes and no negative
one. I'm going move the artifacts into the Apache Maven M2 sync
repository and also move the non-Maven artifacts to the Cocoon
distribution area.
Should
26 matches
Mail list logo
