cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Reinhard Poetz (JIRA)" <>
Subject [jira] Commented: (COCOON-1802) Script for m10n of old blocks
Date Sun, 19 Mar 2006 13:41:03 GMT
    [ ] 

Reinhard Poetz commented on COCOON-1802:

> How should the 'mocks' directory be mapped to the new directory structure? 

In the case of mocks that are only needed for testing, they can go to ./src/test/java. If
the case of mocks that are necessary to build the code because we can't use the library for
this or that reason, I'd go for a separate M2 module.

BTW, the web3 block can be removed from trunk and deprecated in 2.1.x. The main author, Michael
Gerzabek, doesn't do any programming work any more and also doesn't have access to SAP systems.

> Script for m10n of old blocks
> -----------------------------
>          Key: COCOON-1802
>          URL:
>      Project: Cocoon
>         Type: New Feature
>   Components: - Build System: Maven
>     Versions: 2.2-dev (Current SVN)
>     Reporter: Andreas Hochsteger
>  Attachments:,
> See thread starting with
for discussion details.
> Here's the info from the file README.txt:
> What is it?
> -----------
> is a script which automates parts of the conversion from the
> "old" blocks to the "new" mavenized ones.
> Configuration
> -------------
> Only 2 variables have to be adjusted:
> blksrc:
> Local directory where is checked out
> blkdest:
> Local directory where is checked out
> Usage
> -----
> # ./ <blockname>...
> Example:
> # ./ asciiart faces
> Conventions
> -----------
> The script assumes, that every block will consist of a parent block
> (cocoon-<blockname>), an implementation block (cocoon-<blockname>-impl)
> and a sample block (cocoon-<blockname>-sample).
> -----
> The subversion commands are currently untested and commented-out.
> The implementation pom has to be manually merged with the original pom of the
> "old" block. In many cases it is enough to add the dependencies.
> The build section should not be merged, since the new directory structure uses
> maven defaults and thus doesn't need a special configuration.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message