cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Hochsteger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COCOON-1802) Script for m10n of old blocks
Date Sun, 19 Mar 2006 22:00:59 GMT
    [ 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


Mime
View raw message