gmane.text.xml.cocoon.devel

[jira] [Commented] (COCOON3-101) Keep archetype synced

Hudson (JIRA — 2012-05-23T16:10:42

    [ https://issues.apache.org/jira/browse/COCOON3-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281697#comment-13281697 ] 

Hudson commented on COCOON3-101:
--------------------------------

Integrated in Cocoon-trunk #179 (See [https://builds.apache.org/job/Cocoon-trunk/179/])
    COCOON3-101 refactoring cocoon-archetype-block to use the parent versions of the deps so we do not need to keep them in sync by hand. (Revision 1341870)

     Result = FAILURE
thorsten : http://svn.apache.org/viewvc/?view=rev&rev=1341870
Files : 
* /cocoon/cocoon3/trunk/cocoon-archetype-block
* /cocoon/cocoon3/trunk/cocoon-archetype-block/pom.xml
* /cocoon/cocoon3/trunk/cocoon-archetype-block/src/main/resources/archetype-resources/pom.xml
* /cocoon/cocoon3/trunk/cocoon-archetype-block/xsl
* /cocoon/cocoon3/trunk/cocoon-archetype-block/xsl/properties-to-pom.xsl

                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact

Re: Keep archetype synced

Thorsten Scherler — 2012-05-23T14:12:15

revision 1341870 I started with setup of the basic env that I was 
thinking about. It is still not 100% as I want and further ATM only in 
the block one.

salu2

[jira] [Created] (COCOON3-101) Keep archetype synced

Thorsten Scherler (JIRA — 2012-05-23T14:08:40

Thorsten Scherler created COCOON3-101:
-----------------------------------------

             Summary: Keep archetype synced
                 Key: COCOON3-101
                 URL: https://issues.apache.org/jira/browse/COCOON3-101
             Project: Cocoon 3
          Issue Type: New Feature
          Components: cocoon-archetype-X
            Reporter: Thorsten Scherler


http://cocoon.markmail.org/thread/f6hruvbn7h7orllp

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

RE: Keep archetype synced

Robby Pelssers — 2012-05-22T20:26:21

I find the documentation a bit scarce but at least it supports xslt2.0.  If you come to think of it, Cocoon would be a super maven plugin supporting zipping, transforming, file writing, ...   :-)

Robby 

-----Original Message-----
From: Robby Pelssers [mailto:Robby.Pelssers< at >nxp.com] 
Sent: Tuesday, May 22, 2012 5:22 PM
To: dev< at >cocoon.apache.org
Subject: RE: Keep archetype synced

Was also thinking about using some kind of xsl transform to generate the archetype pom.  I will take a look this evening how xml-maven-plugin works.

Robby

-----Original Message-----
From: Thorsten Scherler [mailto:scherler< at >gmail.com] 
Sent: Tuesday, May 22, 2012 5:02 PM
To: dev< at >cocoon.apache.org
Subject: Keep archetype synced

Hi all,

as mentioned in another thread we need to find a way to manage the deps 
of the archetype in a less time consuming manner. Somehow we need to get 
the parents versions in the deploy of the archetype.

We may want to look into doing some "magic" with

<groupId>org.codehaus.mojo</groupId>
<artifactId

RE: Keep archetype synced

Robby Pelssers — 2012-05-22T15:22:22

Was also thinking about using some kind of xsl transform to generate the archetype pom.  I will take a look this evening how xml-maven-plugin works.

Robby

-----Original Message-----
From: Thorsten Scherler [mailto:scherler< at >gmail.com] 
Sent: Tuesday, May 22, 2012 5:02 PM
To: dev< at >cocoon.apache.org
Subject: Keep archetype synced

Hi all,

as mentioned in another thread we need to find a way to manage the deps 
of the archetype in a less time consuming manner. Somehow we need to get 
the parents versions in the deploy of the archetype.

We may want to look into doing some "magic" with

<groupId>org.codehaus.mojo</groupId>
<artifactId>xml-maven-plugin</artifactId>

We used it in sobu to generate the i18n resource files based on xml, so 
we could use a archetype base.xml + xsl trans = final pom.xml

This way we only need to keep in sync which deps we need the version 
would be taken from the parent.pom.xml.

wdyt?

Keep archetype synced

Thorsten Scherler — 2012-05-22T15:02:19

Hi all,

as mentioned in another thread we need to find a way to manage the deps 
of the archetype in a less time consuming manner. Somehow we need to get 
the parents versions in the deploy of the archetype.

We may want to look into doing some "magic" with

<groupId>org.codehaus.mojo</groupId>
<artifactId>xml-maven-plugin</artifactId>

We used it in sobu to generate the i18n resource files based on xml, so 
we could use a archetype base.xml + xsl trans = final pom.xml

This way we only need to keep in sync which deps we need the version 
would be taken from the parent.pom.xml.

wdyt?

Re: svn commit: r1340124 - in /cocoon/trunk/site/cocoon-main-site/src/site: site.xml xdoc/live_sites_3.0.xml

Thorsten Scherler — 2012-05-22T14:51:19

Thanks for taking care!

salu2

On 05/18/2012 05:16 PM, ilgrosso< at >apache.org wrote:

RE: question related to using servlet: in < at >src

Robby Pelssers — 2012-05-22T13:49:02

I'm pretty sure it works.  Actually I lost a few hours without luck and as a quick fix I just copied the sample over and am modifying this to my needs as this evidently works.

Just as a side note.. I did not only create a new block based upon sample archetype. What I did was first create a parent project with parent archetype. I cd'ed into this folder and next created a sample block using the sample archetype.  I'm not sure if there's still something fishy with that approach.  I might give it a try again later but I'm under a bit of pressure to get some output now.

Robby

From: Francesco Chicchiriccò [mailto:ilgrosso< at >apache.org]
Sent: Tuesday, May 22, 2012 9:17 AM
To: dev< at >cocoon.apache.org
Subject: Re: question related to using servlet: in < at >src

On 22/05/2012 08:58, Robby Pelssers wrote:
Nope... still fails.  I will try to start in debug mode and see how far I get. Meanwhile I will also try the sample block again and see if that (still) works.   That one contains several similar use cases so they might be

Re: question related to using servlet: in < at >src

Francesco Chicchiriccò — 2012-05-22T09:29:43

Actually, yes, there are but this is an open point...
Anyway, this shouldn't affect too much your generated project: did you 
try to generate with samples archetype as per my mail below? I'd suggest 
to start comparing these two projects.


Just replace the version on the pom files of your generated project.

Regards.

RE: question related to using servlet: in < at >src

Robby Pelssers — 2012-05-22T09:16:29

Hi Francesco,

I am starting to get a suspicion I know the root cause.  I noticed that e.g. some artifacts use a different version.

If you compare for instance the version of parent/pom.xml
      <dependency>
        <groupId>org.apache.cocoon</groupId>
        <artifactId>cocoon-servlet-service-impl</artifactId>
        <version>1.3.1-SNAPSHOT</version>
      </dependency>

With the one generated by the archetype
            <dependency>
                <groupId>org.apache.cocoon</groupId>
                <artifactId>cocoon-servlet-service-impl</artifactId>
        <!-- After upgrading to 1.2.1 fix the TODO in ServiceServletMonitor -->
                <version>1.2.0</version>
            </dependency>

Isn't there some clever way to keep the archetype in sync with cocoon dependencies used by parent/pom.xml?

What is the best way on short notice for me to work around this discrepancy?

Robby
From: Robby Pelssers [mailto:Robby.Pelssers< at >nxp.com]
Sent: Tuesday, May 22, 2012 9:02 AM
To: dev< at >cocoon.apache.org
Su

Re: svn commit: r1340929 - /cocoon/cocoon3/trunk/cocoon-optional/src/main/java/org/apache/cocoon/optional/pipeline/components/sax/directory/DirectoryGenerator.java

Stavros Kounis — 2012-05-22T09:08:15

unsubscribe

On 21 May 2012 11:31, <ilgrosso< at >apache.org> wrote:

Re: question related to using servlet: in < at >src

Francesco Chicchiriccò — 2012-05-22T07:17:19

Robby,
I've just generated a new project from samples archetype and everything 
seems to work, servlet:/ protocol included.
Incidentally, I've also fixed a typo in pom.xml of the generated project.

Here's what I did:

1. 'mvn clean install' from cocoon-archetype-sample/ subdir in C3 
sources, or wait for next redeployment and use 'mvn -U' in the following

2. generate a new samples block:

mvn archetype:generate \
     -DarchetypeGroupId=org.apache.cocoon.archetype-sample \
     -DarchetypeArtifactId=cocoon-archetype-sample \
     -DarchetypeVersion=3.0.0-beta-1-SNAPSHOT \
     -DgroupId=com.mycompany \
     -DartifactId=mysample \
     -Dversion=1.0-SNAPSHOT \
     
-DarchetypeRepository=https://repository.apache.org/content/repositories/snapshots/ 


3. (IMPORTANT!) add ASF SNAPSHOT repository to pom.xml

<repository>
<id>apache.snapshots</id>
<name>Apache Snapshot Repository</name>
<url>http://repository.apache.org/snapshots</url>
<releases>
<enabled>false</enabled>
</releases>
</repository>

4. mvn jet

RE: question related to using servlet: in < at >src

Robby Pelssers — 2012-05-22T07:01:42

Yes... I understand.  But I guess the snapshot version still remains the same, right?  And I did still have prior versions of artifacts in my local repo. So I guess maven won't fetch them in this case?!

Robby

From: Francesco Chicchiriccò [mailto:ilgrosso< at >apache.org]
Sent: Tuesday, May 22, 2012 8:59 AM
To: dev< at >cocoon.apache.org
Subject: Re: question related to using servlet: in < at >src

On 22/05/2012 08:53, Robby Pelssers wrote:
I am reinstalling all artifacts now and see if that was the culprit. Forgot to do so yesterday evening probably because I followed your quick-start from latest mail discussion.  Will let you know if it still fails afterwards.

Since Jenkins is redeploying SNAPSHOT artifacts at every build, there shouldn't be any difference but the xercesImpl version correction that I've just committed.

Anyway..

From: Francesco Chicchiriccò [mailto:ilgrosso< at >apache.org]
Sent: Tuesday, May 22, 2012 8:50 AM
To: dev< at >cocoon.apache.org<mailto:dev< at >cocoon.apache.org>
Subject: Re: question related to using

Re: question related to using servlet: in < at >src

Francesco Chicchiriccò — 2012-05-22T06:59:22

Since Jenkins is redeploying SNAPSHOT artifacts at every build, there 
shouldn't be any difference but the xercesImpl version correction that 
I've just committed.

Anyway..

RE: question related to using servlet: in < at >src

Robby Pelssers — 2012-05-22T06:58:09

Nope... still fails.  I will try to start in debug mode and see how far I get. Meanwhile I will also try the sample block again and see if that (still) works.   That one contains several similar use cases so they might be broken as well.

Robby

From: Robby Pelssers [mailto:Robby.Pelssers< at >nxp.com]
Sent: Tuesday, May 22, 2012 8:54 AM
To: dev< at >cocoon.apache.org
Subject: RE: question related to using servlet: in < at >src

I am reinstalling all artifacts now and see if that was the culprit. Forgot to do so yesterday evening probably because I followed your quick-start from latest mail discussion.  Will let you know if it still fails afterwards.

From: Francesco Chicchiriccò [mailto:ilgrosso< at >apache.org]
Sent: Tuesday, May 22, 2012 8:50 AM
To: dev< at >cocoon.apache.org
Subject: Re: question related to using servlet: in < at >src

On 22/05/2012 08:42, Robby Pelssers wrote:
Hi Francesco,

My sitemap did declare the servlet namespace

<map:sitemap
        xmlns:map="http://apache.org/cocoon/sitemap"<http://apache.org/cocoon/sitem

RE: question related to using servlet: in < at >src

Robby Pelssers — 2012-05-22T06:53:39

I am reinstalling all artifacts now and see if that was the culprit. Forgot to do so yesterday evening probably because I followed your quick-start from latest mail discussion.  Will let you know if it still fails afterwards.

From: Francesco Chicchiriccò [mailto:ilgrosso< at >apache.org]
Sent: Tuesday, May 22, 2012 8:50 AM
To: dev< at >cocoon.apache.org
Subject: Re: question related to using servlet: in < at >src

On 22/05/2012 08:42, Robby Pelssers wrote:
Hi Francesco,

My sitemap did declare the servlet namespace

<map:sitemap
        xmlns:map="http://apache.org/cocoon/sitemap"<http://apache.org/cocoon/sitemap>
        xmlns:servlet="http://apache.org/cocoon/servlet"<http://apache.org/cocoon/servlet>
        xmlns:controller="http://apache.org/cocoon/controller"<http://apache.org/cocoon/controller>>

But if you look more carefully that shouldn't even matter as I'm not using it as a namespace prefix.  In the < at >src attribute I'm using it but there it's just a string.
<map:generate src="servlet:/testdata"/>

You only need

Re: question related to using servlet: in < at >src

Francesco Chicchiriccò — 2012-05-22T06:50:16

Ops, you are absolutely right :-)
It looks like the ServletURLStreamHandler does not get registered...

RE: question related to using servlet: in < at >src

Robby Pelssers — 2012-05-22T06:42:00

Hi Francesco,

My sitemap did declare the servlet namespace

<map:sitemap
        xmlns:map="http://apache.org/cocoon/sitemap"
        xmlns:servlet="http://apache.org/cocoon/servlet"
        xmlns:controller="http://apache.org/cocoon/controller">

But if you look more carefully that shouldn't even matter as I'm not using it as a namespace prefix.  In the < at >src attribute I'm using it but there it's just a string.
<map:generate src="servlet:/testdata"/>

You only need to declare it when you use a tag in the servlet namespace like e.g.
      <map:match equals="redirect/sax-pipeline/simple-xml">
        <servlet:redirect-to uri="servlet:/sax-pipeline/simple-xml"/>
      </map:match>

So this is not causing the issue.

Robby

From: Francesco Chicchiriccò [mailto:ilgrosso< at >apache.org]
Sent: Tuesday, May 22, 2012 8:34 AM
To: dev< at >cocoon.apache.org
Subject: Re: question related to using servlet: in < at >src

On 21/05/2012 23:49, Robby Pelssers wrote:
Hi all,

I noticed the cocoon protocol got ditched in favour of the ser

Re: question related to using servlet: in < at >src

Francesco Chicchiriccò — 2012-05-22T06:34:12

...did you declare xmlns:servlet="http://apache.org/cocoon/servlet"?

Re: could not download XercesImpl from maven repo

Francesco Chicchiriccò — 2012-05-22T06:32:27

Correct: just fixed this in r1341316: just a typo, since parent/pom.xml 
reports the right version.

Cheers.

Re: could not download XercesImpl from maven repo

Jasha Joachimsthal — 2012-05-22T06:13:04

It looks like 2.10.1 has never existed (or I am looking in the wrong
places). There's no svn tag [1] or binary download [2] for 2.10.1.

[1] https://svn.apache.org/repos/asf/xerces/java/tags/
[2] http://archive.apache.org/dist/xerces/j/binaries/

On 21 May 2012 23:46, Robby Pelssers <Robby.Pelssers< at >nxp.com> wrote: