cocoon-dev mailing list archives

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

Daniel Fagerstrom commented on COCOON-1802:

I have fixed the simple build problems related to artifactIds and version numbers in SVN:

Added the suffix -impl to some block dependencies to reflect the standard structure. Also
changed version 2.2-SNAPSHOT to 1.0-SNAPSHOT for block dependencies, only cocoon-core has
version 2.2. Removed dependencies on cocoon-test-core, that don't exists anymore, the test
is part of the cocoon-core following standard Maven idiom. I am not sure if the cocoon-core
test classes are available for other modules however, have not tested.

As long as we have connection problems with some of the involved Maven repositories, I suggest
that we not move all of the blocks to trunk. That will make the first build (and artifact
download) even more painful than today. We could move some important remaining but not all
of them.

> 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