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 10:32:02 GMT
    [ 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


Mime
View raw message