You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Andreas Hochsteger (JIRA)" <ji...@apache.org> on 2006/03/18 11:32:58 UTC
[jira] Created: (COCOON-1802) Script for m10n of old blocks
Script for m10n of old blocks
-----------------------------
Key: COCOON-1802
URL: http://issues.apache.org/jira/browse/COCOON-1802
Project: Cocoon
Type: New Feature
Components: - Build System: Maven
Versions: 2.2-dev (Current SVN)
Reporter: Andreas Hochsteger
Attachments: m10n-blocks.zip
See thread starting with http://www.mail-archive.com/dev@cocoon.apache.org/msg42233.html for discussion details.
Here's the info from the file README.txt:
What is it?
-----------
m10n-blocks.sh 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 https://svn.apache.org/repos/asf/cocoon/blocks is checked out
blkdest:
Local directory where https://svn.apache.org/repos/asf/cocoon/trunk is checked out
Usage
-----
# ./m10n-blocks.sh <blockname>...
Example:
# ./m10n-blocks.sh 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).
TODOs
-----
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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (COCOON-1802) Script for m10n of old blocks
Posted by "Andreas Hochsteger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1802?page=all ]
Andreas Hochsteger updated COCOON-1802:
---------------------------------------
Attachment: m10n-blocks.zip
This update includes handling of pom files (including merging of impl dependencies) and handling of mocks using solution 1 as described in README.txt.
Please have a look at README.txt for answering open questions.
> Script for m10n of old blocks
> -----------------------------
>
> Key: COCOON-1802
> URL: http://issues.apache.org/jira/browse/COCOON-1802
> Project: Cocoon
> Type: New Feature
> Components: - Build System: Maven
> Versions: 2.2-dev (Current SVN)
> Reporter: Andreas Hochsteger
> Attachments: m10n-blocks.zip, m10n-blocks.zip
>
> See thread starting with http://www.mail-archive.com/dev@cocoon.apache.org/msg42233.html for discussion details.
> Here's the info from the file README.txt:
> What is it?
> -----------
> m10n-blocks.sh 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 https://svn.apache.org/repos/asf/cocoon/blocks is checked out
> blkdest:
> Local directory where https://svn.apache.org/repos/asf/cocoon/trunk is checked out
> Usage
> -----
> # ./m10n-blocks.sh <blockname>...
> Example:
> # ./m10n-blocks.sh 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).
> TODOs
> -----
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (COCOON-1802) Script for m10n of old blocks
Posted by "Reinhard Poetz (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1802?page=all ]
Reinhard Poetz closed COCOON-1802:
----------------------------------
Resolution: Fixed
Thanks, your script helped a lot!
> Script for m10n of old blocks
> -----------------------------
>
> Key: COCOON-1802
> URL: http://issues.apache.org/jira/browse/COCOON-1802
> Project: Cocoon
> Type: New Feature
> Components: - Build System: Maven
> Versions: 2.2-dev (Current SVN)
> Reporter: Andreas Hochsteger
> Assignee: Reinhard Poetz
> Attachments: m10n-blocks.zip, m10n-blocks.zip, m10n-blocks.zip, m10n-blocks.zip, svn-reorganize.zip, svn-reorganize.zip, svn-reorganize.zip
>
> See thread starting with http://www.mail-archive.com/dev@cocoon.apache.org/msg42233.html for discussion details.
> Here's the info from the file README.txt:
> What is it?
> -----------
> m10n-blocks.sh 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 https://svn.apache.org/repos/asf/cocoon/blocks is checked out
> blkdest:
> Local directory where https://svn.apache.org/repos/asf/cocoon/trunk is checked out
> Usage
> -----
> # ./m10n-blocks.sh <blockname>...
> Example:
> # ./m10n-blocks.sh 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).
> TODOs
> -----
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (COCOON-1802) Script for m10n of old blocks
Posted by "Andreas Hochsteger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1802?page=comments#action_12370978 ]
Andreas Hochsteger commented on COCOON-1802:
--------------------------------------------
Successful Builds
-----------------
The following old blocks were successfully built using 'mvn install' after
automatic conversion and installing the existing new blocks:
asciiart
axis (after manual installation of javax.mail and javax.activation as suggested by http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html)
batik
bsf
core-samples-additional
core-samples-main
deli
fop
hsqldb
html
itext
jfor
jsp
linkrewriter
lucene
mail
naming
paranoid
petstore
poi
profiler
proxy
qdox
serializers
slop
stx
tour
velocity
web3 (after fixing missing </project> of generated POM - bug in script!)
Build Problems
--------------
apples (wrong version for cocoon-forms-impl: 2.2.0-SNAPSHOT -> 1.0-SNAPSHOT; compilation error)
chaperon (missing dependency to cocoon-test-core)
eventcache (missing dependency to cocoon-template and cocoon-jms)
faces (missing dependencies to cocoon-portal and cocoon-taglib)
javaflow (missing dependency to cocoon-forms-impl)
jms (wrong version for cocoon-cron: 2.2.0-SNAPSHOT -> 1.0-SNAPSHOT; still not found after fixing it)
midi (missing dependency to cocoon-test-core)
ojb (manually fix missing </project> of generated POM - bug in script!; missing dependency d-haven-managed-pool:d-haven-managed-pool:jar:1.0)
python (manually fix missing </project> of generated POM - bug in script!; missing dependency to org.apache.cocoon:cocoon-xsp:jar:2.2.0-SNAPSHOT)
querybean (missing dependency to org.apache.cocoon:cocoon-lucene:jar:2.2.0-SNAPSHOT - wrong version!)
repository (missing dependency to org.apache.cocoon:cocoon-eventcache:jar:2.2.0-SNAPSHOT)
scratchpad (missing dependency to org.apache.cocoon:cocoon-forms:jar:2.2.0-SNAPSHOT)
slide (missing dependencies to org.apache.cocoon:cocoon-jms:jar:2.2.0-SNAPSHOT and org.apache.cocoon:cocoon-repository:jar:2.2.0-SNAPSHOT)
taglib (compilation failure)
webdav (missing dependency to org.apache.cocoon:cocoon-repository:jar:2.2.0-SNAPSHOT)
xsp (missing dependencies to org.apache.cocoon:cocoon-session-fw:jar:2.2.0-SNAPSHOT and d-haven-managed-pool:d-haven-managed-pool:jar:1.0)
Questions and TODOs
-------------------
* Merge old POM with block implementation POM (esp. dependencies) - could be automated using the ant xmltask
- In most cases it is enough to just add the dependencies
- The dependency to apache-cocoon:cocoon-core:2.2-SNAPSHOT from the old POM will be replaced by org.apache.cocoon:cocoon-default:1.0-SNAPSHOT for the new POM - is this correct?
- groupId (and perhaps artifactId) have to be manually fixed
- Fixing the groupId from apache-cocoon to org.apache.cocoon could be automated
- The build section of the POM is now obsolete by using the maven default directory structure for the new blocks.
* Move resources (others than *.java) from the old java directory to cocoon-<block>-impl/src/main/resources/...
- Can somebody please confirm the concrete directory?
* How should the 'mocks' directory be mapped to the new directory structure?
- Solution 1: Map to cocoon-<block>-mocks/src/main/java (separate artifact)
- Solution 2: Map to cocoon-<block>-impl/src/mock/java (not a standard Maven way I think - currently used for the JSP block)
- Solution 3: Include them in cocoon-mocks/src/mock/java (possibly prefered, since it already exists?)
- Solution 4: ? Is there another solution?
* The subversion commands are currently untested and commented-out.
- They should be activated finally if the script supports everyting that can be automated.
* Add 'name' tag to each POM in a consistent way:
- parent POM: <name>
- impl POM: <name> Implementation
- sample POM: <name> Samples
- mock POM: <name> Mocks
* Insert all converted blocks into master cocoon POM modules
* Copy/move status.xml
- There are some inconsistencies for the current new blocks
- Some are located in the parent block, some in the impl block
- Where should they be located?
* What is cocoon-test-core? Some blocks are depending on this (e.g. chaperon, midi)
> Script for m10n of old blocks
> -----------------------------
>
> Key: COCOON-1802
> URL: http://issues.apache.org/jira/browse/COCOON-1802
> Project: Cocoon
> Type: New Feature
> Components: - Build System: Maven
> Versions: 2.2-dev (Current SVN)
> Reporter: Andreas Hochsteger
> Attachments: m10n-blocks.zip, m10n-blocks.zip
>
> See thread starting with http://www.mail-archive.com/dev@cocoon.apache.org/msg42233.html for discussion details.
> Here's the info from the file README.txt:
> What is it?
> -----------
> m10n-blocks.sh 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 https://svn.apache.org/repos/asf/cocoon/blocks is checked out
> blkdest:
> Local directory where https://svn.apache.org/repos/asf/cocoon/trunk is checked out
> Usage
> -----
> # ./m10n-blocks.sh <blockname>...
> Example:
> # ./m10n-blocks.sh 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).
> TODOs
> -----
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (COCOON-1802) Script for m10n of old blocks
Posted by "Andreas Hochsteger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1802?page=comments#action_12370939 ]
Andreas Hochsteger commented on COCOON-1802:
--------------------------------------------
Because the files were created with Windows XP they might not work for Unix/Linux OOTB.
You may need to convert them into Unix format using 'recode ibmpc..latin1 <filename>'.
Cygwin should work without recoding though.
It would be great, if someone could provide me some feedback about the current functionality and possible improvements!
Thanks,
Andreas
> Script for m10n of old blocks
> -----------------------------
>
> Key: COCOON-1802
> URL: http://issues.apache.org/jira/browse/COCOON-1802
> Project: Cocoon
> Type: New Feature
> Components: - Build System: Maven
> Versions: 2.2-dev (Current SVN)
> Reporter: Andreas Hochsteger
> Attachments: m10n-blocks.zip
>
> See thread starting with http://www.mail-archive.com/dev@cocoon.apache.org/msg42233.html for discussion details.
> Here's the info from the file README.txt:
> What is it?
> -----------
> m10n-blocks.sh 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 https://svn.apache.org/repos/asf/cocoon/blocks is checked out
> blkdest:
> Local directory where https://svn.apache.org/repos/asf/cocoon/trunk is checked out
> Usage
> -----
> # ./m10n-blocks.sh <blockname>...
> Example:
> # ./m10n-blocks.sh 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).
> TODOs
> -----
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (COCOON-1802) Script for m10n of old blocks
Posted by "Daniel Fagerstrom (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1802?page=comments#action_12370979 ]
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: http://issues.apache.org/jira/browse/COCOON-1802
> Project: Cocoon
> Type: New Feature
> Components: - Build System: Maven
> Versions: 2.2-dev (Current SVN)
> Reporter: Andreas Hochsteger
> Attachments: m10n-blocks.zip, m10n-blocks.zip
>
> See thread starting with http://www.mail-archive.com/dev@cocoon.apache.org/msg42233.html for discussion details.
> Here's the info from the file README.txt:
> What is it?
> -----------
> m10n-blocks.sh 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 https://svn.apache.org/repos/asf/cocoon/blocks is checked out
> blkdest:
> Local directory where https://svn.apache.org/repos/asf/cocoon/trunk is checked out
> Usage
> -----
> # ./m10n-blocks.sh <blockname>...
> Example:
> # ./m10n-blocks.sh 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).
> TODOs
> -----
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (COCOON-1802) Script for m10n of old blocks
Posted by "Andreas Hochsteger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1802?page=all ]
Andreas Hochsteger updated COCOON-1802:
---------------------------------------
Attachment: svn-reorganize.zip
Changes:
* Fixed resource handling in Java source path
* Prepared configuration for svn commands
* Fixed some version numbers (1.0-SNAPSHOT -> 1.0.0-SNAPSHOT)
NOTE: Still not fully tested, since the cocoon archetype creation does not work for me ...
> Script for m10n of old blocks
> -----------------------------
>
> Key: COCOON-1802
> URL: http://issues.apache.org/jira/browse/COCOON-1802
> Project: Cocoon
> Type: New Feature
> Components: - Build System: Maven
> Versions: 2.2-dev (Current SVN)
> Reporter: Andreas Hochsteger
> Assignee: Reinhard Poetz
> Attachments: m10n-blocks.zip, m10n-blocks.zip, m10n-blocks.zip, m10n-blocks.zip, svn-reorganize.zip, svn-reorganize.zip, svn-reorganize.zip
>
> See thread starting with http://www.mail-archive.com/dev@cocoon.apache.org/msg42233.html for discussion details.
> Here's the info from the file README.txt:
> What is it?
> -----------
> m10n-blocks.sh 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 https://svn.apache.org/repos/asf/cocoon/blocks is checked out
> blkdest:
> Local directory where https://svn.apache.org/repos/asf/cocoon/trunk is checked out
> Usage
> -----
> # ./m10n-blocks.sh <blockname>...
> Example:
> # ./m10n-blocks.sh 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).
> TODOs
> -----
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (COCOON-1802) Script for m10n of old blocks
Posted by "Reinhard Poetz (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1802?page=all ]
Reinhard Poetz reassigned COCOON-1802:
--------------------------------------
Assign To: Reinhard Poetz
> Script for m10n of old blocks
> -----------------------------
>
> Key: COCOON-1802
> URL: http://issues.apache.org/jira/browse/COCOON-1802
> Project: Cocoon
> Type: New Feature
> Components: - Build System: Maven
> Versions: 2.2-dev (Current SVN)
> Reporter: Andreas Hochsteger
> Assignee: Reinhard Poetz
> Attachments: m10n-blocks.zip, m10n-blocks.zip, m10n-blocks.zip, m10n-blocks.zip
>
> See thread starting with http://www.mail-archive.com/dev@cocoon.apache.org/msg42233.html for discussion details.
> Here's the info from the file README.txt:
> What is it?
> -----------
> m10n-blocks.sh 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 https://svn.apache.org/repos/asf/cocoon/blocks is checked out
> blkdest:
> Local directory where https://svn.apache.org/repos/asf/cocoon/trunk is checked out
> Usage
> -----
> # ./m10n-blocks.sh <blockname>...
> Example:
> # ./m10n-blocks.sh 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).
> TODOs
> -----
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (COCOON-1802) Script for m10n of old blocks
Posted by "Andreas Hochsteger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1802?page=all ]
Andreas Hochsteger updated COCOON-1802:
---------------------------------------
Attachment: svn-reorganize.zip
This update contains the following changes:
* Renamed ZIP file to svn-reorganize.zip since it better says what it does
* Renamed conversion script from m10n-blocks.sh to convert-blocks.sh
* Added new script svn-reorganize-trunk.sh which generates the svn commands for the moves using a config file
* Adapted to new repository layout suggested by Reinhard
* Create new POM in directory 'blocks' which contains all converted blocks as Maven modules
* Updated sections Questions and TODOs in README.txt (Please check these - I need some help here!)
> Script for m10n of old blocks
> -----------------------------
>
> Key: COCOON-1802
> URL: http://issues.apache.org/jira/browse/COCOON-1802
> Project: Cocoon
> Type: New Feature
> Components: - Build System: Maven
> Versions: 2.2-dev (Current SVN)
> Reporter: Andreas Hochsteger
> Assignee: Reinhard Poetz
> Attachments: m10n-blocks.zip, m10n-blocks.zip, m10n-blocks.zip, m10n-blocks.zip, svn-reorganize.zip
>
> See thread starting with http://www.mail-archive.com/dev@cocoon.apache.org/msg42233.html for discussion details.
> Here's the info from the file README.txt:
> What is it?
> -----------
> m10n-blocks.sh 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 https://svn.apache.org/repos/asf/cocoon/blocks is checked out
> blkdest:
> Local directory where https://svn.apache.org/repos/asf/cocoon/trunk is checked out
> Usage
> -----
> # ./m10n-blocks.sh <blockname>...
> Example:
> # ./m10n-blocks.sh 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).
> TODOs
> -----
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (COCOON-1802) Script for m10n of old blocks
Posted by "Andreas Hochsteger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1802?page=comments#action_12371015 ]
Andreas Hochsteger commented on COCOON-1802:
--------------------------------------------
I just tested the builds with the latest version of the conversion script: 35 out of 45 blocks compile successfully!
Some blocks needed minor manual tweaks of their POMs or needed to have some jars installed manually in the local repository.
Note, that the latest version (from 1:58 PM of today) still has the automatic changing of dependency version numbers active and may wrongly set the version to 1.0-SNAPSHOT (e.g. for cocoon-mocks).
The summary follows ...
Successful Builds
-----------------
The following old blocks were successfully built using 'mvn install' after
automatic conversion and installing the existing new blocks (manual installation
of javax.mail and javax.activation as suggested by
http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html may be needed):
asciiart
axis
batik
bsf
core-samples-additional
core-samples-main
deli
eventcache
fop
hsqldb
html
itext
javaflow
jfor
jms
jsp
linkrewriter
lucene
mail
naming
paranoid
petstore
poi
profiler
proxy
qdox
querybean
repository (after manually installing missing (wrong) dependency d-haven-managed-pool:d-haven-managed-pool:jar:1.0 from http://keelframework.org/maven/d-haven-managed-pool/jars/ - should be d-haven-mpool:managed-pool:jar:1.0)
serializers
slide
slop
stx
tour
velocity
web3
Build Problems
--------------
apples (compilation failure: cannot find symbol: method setupComponent(...))
chaperon (compilation failure: cannot find symbols)
faces (missing dependency to org.apache.cocoon:cocoon-taglib-impl:jar:1.0-SNAPSHOT)
midi (compilation failure: cannot find symbols)
ojb (compilation failure: cannot find symbols)
python (missing dependency to org.apache.cocoon:cocoon-xsp:jar:2.2.0-SNAPSHOT)
scratchpad (missing dependency to org.apache.cocoon:cocoon-forms:jar:2.2.0-SNAPSHOT -> cocoon-forms-impl)
taglib (compilation failure: org.apache.cocoon.jxpath.JXPathCocoonContexts.ContextProxy is not abstract and does not override abstract method log(java.lang.String,java.lang.Throwable) in javax.servlet.ServletContext)
webdav (compilation failure: package org.apache.cocoon.core.container does not exist)
xsp (after manually fixing versions of dependencies: compilation failure: cannot find symbols)
> Script for m10n of old blocks
> -----------------------------
>
> Key: COCOON-1802
> URL: http://issues.apache.org/jira/browse/COCOON-1802
> Project: Cocoon
> Type: New Feature
> Components: - Build System: Maven
> Versions: 2.2-dev (Current SVN)
> Reporter: Andreas Hochsteger
> Attachments: m10n-blocks.zip, m10n-blocks.zip, m10n-blocks.zip
>
> See thread starting with http://www.mail-archive.com/dev@cocoon.apache.org/msg42233.html for discussion details.
> Here's the info from the file README.txt:
> What is it?
> -----------
> m10n-blocks.sh 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 https://svn.apache.org/repos/asf/cocoon/blocks is checked out
> blkdest:
> Local directory where https://svn.apache.org/repos/asf/cocoon/trunk is checked out
> Usage
> -----
> # ./m10n-blocks.sh <blockname>...
> Example:
> # ./m10n-blocks.sh 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).
> TODOs
> -----
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (COCOON-1802) Script for m10n of old blocks
Posted by "Jorg Heymans (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1802?page=comments#action_12370995 ]
Jorg Heymans commented on COCOON-1802:
--------------------------------------
cocoon-core test classes are now available for other modules.
See cocoon-template-impl/pom.xml for an example.
> Script for m10n of old blocks
> -----------------------------
>
> Key: COCOON-1802
> URL: http://issues.apache.org/jira/browse/COCOON-1802
> Project: Cocoon
> Type: New Feature
> Components: - Build System: Maven
> Versions: 2.2-dev (Current SVN)
> Reporter: Andreas Hochsteger
> Attachments: m10n-blocks.zip, m10n-blocks.zip, m10n-blocks.zip
>
> See thread starting with http://www.mail-archive.com/dev@cocoon.apache.org/msg42233.html for discussion details.
> Here's the info from the file README.txt:
> What is it?
> -----------
> m10n-blocks.sh 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 https://svn.apache.org/repos/asf/cocoon/blocks is checked out
> blkdest:
> Local directory where https://svn.apache.org/repos/asf/cocoon/trunk is checked out
> Usage
> -----
> # ./m10n-blocks.sh <blockname>...
> Example:
> # ./m10n-blocks.sh 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).
> TODOs
> -----
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (COCOON-1802) Script for m10n of old blocks
Posted by "Andreas Hochsteger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1802?page=comments#action_12370981 ]
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 case.
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.
Andreas.
> Script for m10n of old blocks
> -----------------------------
>
> Key: COCOON-1802
> URL: http://issues.apache.org/jira/browse/COCOON-1802
> Project: Cocoon
> Type: New Feature
> Components: - Build System: Maven
> Versions: 2.2-dev (Current SVN)
> Reporter: Andreas Hochsteger
> Attachments: m10n-blocks.zip, m10n-blocks.zip
>
> See thread starting with http://www.mail-archive.com/dev@cocoon.apache.org/msg42233.html for discussion details.
> Here's the info from the file README.txt:
> What is it?
> -----------
> m10n-blocks.sh 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 https://svn.apache.org/repos/asf/cocoon/blocks is checked out
> blkdest:
> Local directory where https://svn.apache.org/repos/asf/cocoon/trunk is checked out
> Usage
> -----
> # ./m10n-blocks.sh <blockname>...
> Example:
> # ./m10n-blocks.sh 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).
> TODOs
> -----
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (COCOON-1802) Script for m10n of old blocks
Posted by "Reinhard Poetz (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1802?page=comments#action_12371192 ]
Reinhard Poetz commented on COCOON-1802:
----------------------------------------
I will work on the scripts together with Andreas next week (29.3.).
> Script for m10n of old blocks
> -----------------------------
>
> Key: COCOON-1802
> URL: http://issues.apache.org/jira/browse/COCOON-1802
> Project: Cocoon
> Type: New Feature
> Components: - Build System: Maven
> Versions: 2.2-dev (Current SVN)
> Reporter: Andreas Hochsteger
> Assignee: Reinhard Poetz
> Attachments: m10n-blocks.zip, m10n-blocks.zip, m10n-blocks.zip, m10n-blocks.zip
>
> See thread starting with http://www.mail-archive.com/dev@cocoon.apache.org/msg42233.html for discussion details.
> Here's the info from the file README.txt:
> What is it?
> -----------
> m10n-blocks.sh 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 https://svn.apache.org/repos/asf/cocoon/blocks is checked out
> blkdest:
> Local directory where https://svn.apache.org/repos/asf/cocoon/trunk is checked out
> Usage
> -----
> # ./m10n-blocks.sh <blockname>...
> Example:
> # ./m10n-blocks.sh 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).
> TODOs
> -----
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (COCOON-1802) Script for m10n of old blocks
Posted by "Andreas Hochsteger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1802?page=all ]
Andreas Hochsteger updated COCOON-1802:
---------------------------------------
Attachment: svn-reorganize.zip
Changes:
* Some fixes to the directory structure as suggested by Reinhard
* First steps for automatic handling of resources in the java directories
* Some optimization of the POM XML code (including XSL)
NOTE: Changes are still untested!
> Script for m10n of old blocks
> -----------------------------
>
> Key: COCOON-1802
> URL: http://issues.apache.org/jira/browse/COCOON-1802
> Project: Cocoon
> Type: New Feature
> Components: - Build System: Maven
> Versions: 2.2-dev (Current SVN)
> Reporter: Andreas Hochsteger
> Assignee: Reinhard Poetz
> Attachments: m10n-blocks.zip, m10n-blocks.zip, m10n-blocks.zip, m10n-blocks.zip, svn-reorganize.zip, svn-reorganize.zip
>
> See thread starting with http://www.mail-archive.com/dev@cocoon.apache.org/msg42233.html for discussion details.
> Here's the info from the file README.txt:
> What is it?
> -----------
> m10n-blocks.sh 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 https://svn.apache.org/repos/asf/cocoon/blocks is checked out
> blkdest:
> Local directory where https://svn.apache.org/repos/asf/cocoon/trunk is checked out
> Usage
> -----
> # ./m10n-blocks.sh <blockname>...
> Example:
> # ./m10n-blocks.sh 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).
> TODOs
> -----
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (COCOON-1802) Script for m10n of old blocks
Posted by "Reinhard Poetz (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1802?page=comments#action_12370983 ]
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: http://issues.apache.org/jira/browse/COCOON-1802
> Project: Cocoon
> Type: New Feature
> Components: - Build System: Maven
> Versions: 2.2-dev (Current SVN)
> Reporter: Andreas Hochsteger
> Attachments: m10n-blocks.zip, m10n-blocks.zip
>
> See thread starting with http://www.mail-archive.com/dev@cocoon.apache.org/msg42233.html for discussion details.
> Here's the info from the file README.txt:
> What is it?
> -----------
> m10n-blocks.sh 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 https://svn.apache.org/repos/asf/cocoon/blocks is checked out
> blkdest:
> Local directory where https://svn.apache.org/repos/asf/cocoon/trunk is checked out
> Usage
> -----
> # ./m10n-blocks.sh <blockname>...
> Example:
> # ./m10n-blocks.sh 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).
> TODOs
> -----
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (COCOON-1802) Script for m10n of old blocks
Posted by "Andreas Hochsteger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1802?page=all ]
Andreas Hochsteger updated COCOON-1802:
---------------------------------------
Attachment: m10n-blocks.zip
New version with handling of POM files and mocks.
> Script for m10n of old blocks
> -----------------------------
>
> Key: COCOON-1802
> URL: http://issues.apache.org/jira/browse/COCOON-1802
> Project: Cocoon
> Type: New Feature
> Components: - Build System: Maven
> Versions: 2.2-dev (Current SVN)
> Reporter: Andreas Hochsteger
> Attachments: m10n-blocks.zip, m10n-blocks.zip, m10n-blocks.zip
>
> See thread starting with http://www.mail-archive.com/dev@cocoon.apache.org/msg42233.html for discussion details.
> Here's the info from the file README.txt:
> What is it?
> -----------
> m10n-blocks.sh 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 https://svn.apache.org/repos/asf/cocoon/blocks is checked out
> blkdest:
> Local directory where https://svn.apache.org/repos/asf/cocoon/trunk is checked out
> Usage
> -----
> # ./m10n-blocks.sh <blockname>...
> Example:
> # ./m10n-blocks.sh 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).
> TODOs
> -----
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (COCOON-1802) Script for m10n of old blocks
Posted by "Andreas Hochsteger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1802?page=comments#action_12370955 ]
Andreas Hochsteger commented on COCOON-1802:
--------------------------------------------
I'll try to submit a report tomorrow that shows which blocks can already be built using 'mvn package' after converting with this script.
For the failed blocks I'll give a description of the type of failure.
> Script for m10n of old blocks
> -----------------------------
>
> Key: COCOON-1802
> URL: http://issues.apache.org/jira/browse/COCOON-1802
> Project: Cocoon
> Type: New Feature
> Components: - Build System: Maven
> Versions: 2.2-dev (Current SVN)
> Reporter: Andreas Hochsteger
> Attachments: m10n-blocks.zip, m10n-blocks.zip
>
> See thread starting with http://www.mail-archive.com/dev@cocoon.apache.org/msg42233.html for discussion details.
> Here's the info from the file README.txt:
> What is it?
> -----------
> m10n-blocks.sh 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 https://svn.apache.org/repos/asf/cocoon/blocks is checked out
> blkdest:
> Local directory where https://svn.apache.org/repos/asf/cocoon/trunk is checked out
> Usage
> -----
> # ./m10n-blocks.sh <blockname>...
> Example:
> # ./m10n-blocks.sh 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).
> TODOs
> -----
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (COCOON-1802) Script for m10n of old blocks
Posted by "Andreas Hochsteger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1802?page=all ]
Andreas Hochsteger updated COCOON-1802:
---------------------------------------
Attachment: m10n-blocks.zip
This update removes the automatic handling of dependency versions (set version to 1.0-SNAPSHOT) since it also "fixes" correct version numbers. It is better to fix them manually directly in the POMs.
> Script for m10n of old blocks
> -----------------------------
>
> Key: COCOON-1802
> URL: http://issues.apache.org/jira/browse/COCOON-1802
> Project: Cocoon
> Type: New Feature
> Components: - Build System: Maven
> Versions: 2.2-dev (Current SVN)
> Reporter: Andreas Hochsteger
> Attachments: m10n-blocks.zip, m10n-blocks.zip, m10n-blocks.zip, m10n-blocks.zip
>
> See thread starting with http://www.mail-archive.com/dev@cocoon.apache.org/msg42233.html for discussion details.
> Here's the info from the file README.txt:
> What is it?
> -----------
> m10n-blocks.sh 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 https://svn.apache.org/repos/asf/cocoon/blocks is checked out
> blkdest:
> Local directory where https://svn.apache.org/repos/asf/cocoon/trunk is checked out
> Usage
> -----
> # ./m10n-blocks.sh <blockname>...
> Example:
> # ./m10n-blocks.sh 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).
> TODOs
> -----
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira