cocoon-dev mailing list archives

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

Andreas Hochsteger commented on COCOON-1802:

Thanks, Daniel, for taking care of that.
Unfortunately I just implemented the automatic fixing of version numbers and groupIds.
But it's ok, I can remove this code again, since it might not have been 100% correct in every

I'll add a new version of the conversion script later today, which will takes care of the
poms and mocks too.
It's already implemented, but I want to do some tests before adding it to Jira.
It would be nice, if the Questions in the post above could be answered, so I can choose the
right solutions for the conversion.


> 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