On 09/11/2012 11:19 AM, Francesco Chicchiriccò wrote:
On 10/09/2012 20:30, Thorsten Scherler wrote:
[...]
This breaks jetty:run and I am ATM not sure why. It fails like:
...
Any ideas very welcome!

Hi Thorsten,
this is happening because the generated project is using the latest version of the cocoon-maven-plugin (1.0.2) which in turn is enforcing the latest versions of cocoon-rcl-webapp-wrapper (1.0.2) and cocoon-rcl-spring-reloader (1.0.2); these are in turn dependent on Spring 3.1.

Following the procedure reported above, I've changed (in the generated pom.xml):

<plugin>
        <groupId>org.apache.cocoon</groupId>
        <artifactId>cocoon-maven-plugin</artifactId>
        <version>1.0.2</version>
        <executions>
          <execution>
            <id>prepare</id>
            <phase>compile</phase>
            <goals>
              <goal>prepare</goal>
            </goals>
          </execution>
        </executions>
      </plugin>

into

<plugin>
        <groupId>org.apache.cocoon</groupId>
        <artifactId>cocoon-maven-plugin</artifactId>
        <version>1.0.0</version>
<dependencies>
    <!-- RCL -->
    <dependency>
      <groupId>org.apache.cocoon</groupId>
<artifactId>cocoon-rcl-spring-reloader</artifactId>
      <version>1.0.0</version>
    </dependency>
    <dependency>
      <groupId>org.apache.cocoon</groupId>
<artifactId>cocoon-rcl-webapp-wrapper</artifactId>
      <version>1.0.0</version>
    </dependency>
</dependencies>
        <executions>
          <execution>
            <id>prepare</id>
            <phase>compile</phase>
            <goals>
              <goal>prepare</goal>
            </goals>
          </execution>
        </executions>
      </plugin>

and now it works.

I'd suggest to make this changes to archetype resources's pom.xml.

Done and committed. Thanks for the finding.


Moreover, consider that when issuing 'mvn clean deploy' instead of 'mvn clean install', you will also upload the SNAPSHOT artifacts to ASF maven repository (Nexus): since 2.2.X does not have a configured Jenkins instance for this (like as C3), you still need to do this manually when you want to publish updated SNAPSHOT artifacts.


Trying to fix that ATM but since I switch my box a while ago I never came to setup the deploy to ASF preconditions. I am working on it now. I get ATM for the "deploy"

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project cocoon-22-archetype-block: Failed to deploy artifacts: Could not transfer artifact org.apache.cocoon:cocoon-22-archetype-block:jar:1.1.0-20120911.095051-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots): Failed to transfer file: https://repository.apache.org/content/repositories/snapshots/org/apache/cocoon/cocoon-22-archetype-block/1.1.0-SNAPSHOT/cocoon-22-archetype-block-1.1.0-20120911.095051-2.jar. Return code is: 401 -> [Help 1]

Must be something with the credential setup.

salu2

--
Thorsten Scherler <scherler.at.gmail.com>
codeBusters S.L. - web based systems
<consulting, training and solutions>

http://www.codebusters.es/

Reply via email to