Re: Avalon conflict?

Hello,

>>>I've just tried running the new MavenTool on keel-core (my intention was
>>>to run it on all modules). It came up with a conflict that appears to be
>>>in the underlying Avalon dependencies, unfortunately.
>>>
>>>There's also a reference to "mockobjects" and "geronimo" that are a bit
>>>odd - I'm beginning to wonder if they're all truly required...
>>>
In the current program.xml, there is still avalon framework version 
4.1.3: I think it's a maven keel:maven that put it here, as it's a 
commons-logging dependancy.

mockobjects is asked by avalon-logkit, via geronimo-spec-jms

See below the project.xml I used to rebuild keel.core.

I did all the changes to rebuild quite a lot of modules of  keel. There 
are many conflicts between libraries (mainly with common-logging and 
avalon-logkit)

I avoid to do any maven keel:maven from keel modules. I did it only in 
the program.xml of a final projects. I iterated until I got no more 
conflict in it.

But something came wrong as I can no more run persistence (see my 
previous messages). I must have remove something required but which 
doesn't create any error at building time.

May be it would be best to change project.xml for one keel module at a 
time, until to get no conflict with maven keel:maven?

>>I can't help much.  mockobjects is almost certainly a test-time 
>>dependency, and nopt required for runtime/build.
>>I have seen references to geronimo, where the equivalent Sun JAR (like 
>>servlet API, etc) cannot be downloaded from a Maven repo because of 
>>Sun's license policy.
>>    
>>
What about the new license used by SUN for J2EE? 
http://www.eweek.com/article2/0,1895,1831435,00.asp.
May it change the rule on this point?

Pierre

<?xml version="1.0" encoding="UTF-8"?>
<project>
  <pomVersion>3</pomVersion>
  <name>Keel Core</name>
  <artifactId>keel-core</artifactId>
  <groupId>keel</groupId>
  <type>jar</type>
  <currentVersion>5.0</currentVersion>
  <shortDescription>Keel Core Interfaces</shortDescription>
  <description>
This project contains "core" Keel classes and interfaces,
but none of the actual implementations.
  </description>
  <shortDescription>Keel Core Interfaces</shortDescription>
  <reports>
    <!-- <report>maven-clover-plugin</report> -->
    <!-- Metrics
Checkstyle
Changes
Change Log
Developer Activity
File Activity
Project License
JavaDocs
JavaDoc Report
JavaDoc Warnings Report
Source Xref
Test Xref
Unit Tests
Link Check Report
Task List -->
    <report>maven-dashboard-plugin</report>
    <report>maven-checkstyle-plugin</report>
    <report>maven-pmd-plugin</report>
    <report>maven-simian-plugin</report>
    <report>maven-jxr-plugin</report>
    <report>maven-jcoverage-plugin</report>
    <report>maven-tasklist-plugin</report>
    <report>maven-changes-plugin</report>
    <report>maven-changelog-plugin</report>
    <report>maven-developer-activity-plugin</report>
    <report>maven-file-activity-plugin</report>
    <report>maven-linkcheck-plugin</report>
    <report>maven-tasklist-plugin</report>
    <report>maven-javadoc-plugin</report>
    <!-- metrics
test xref
unit tests
task list -->
  </reports>
  <dependencies>
    <dependency>
      <groupId>avalon-framework</groupId>
      <artifactId>avalon-framework-api</artifactId>
      <version>4.3</version>
      <type>jar</type>
    </dependency>
    <dependency>
      <groupId>avalon-framework</groupId>
      <artifactId>avalon-framework-impl</artifactId>
      <version>4.3</version>
      <type>jar</type>
    </dependency>
    <dependency>
      <groupId>junit</groupId>
      <artifactId>junit</artifactId>
      <version>3.8.1</version>
      <type>jar</type>
      <properties>
        <build>true</build>
        <scope>test</scope>
      </properties>
    </dependency>
  </dependencies>
  <build>
    <sourceDirectory>${basedir}/src/java</sourceDirectory>
    <unitTestSourceDirectory>${basedir}/src/test</unitTestSourceDirectory>
    <resources>
      <resource>
        <directory>${basedir}</directory>
        <filtering>false</filtering>
        <targetpath>/</targetpath>
        <includes>
          <include>conf/**/*</include>
          <include>README*</include>
          <include>LICENSE*</include>
        </includes>
      </resource>
      <resource>
        <directory>${basedir}/src</directory>
        <filtering>false</filtering>
        <targetpath>src</targetpath>
        <includes>
          <include>jsp/**/*</include>
          <include>ui/**/*</include>
          <include>vm/**/*</include>
          <include>webapp/**/*</include>
          <include>xsl/**/*</include>
          <include>xml/**/*</include>
        </includes>
      </resource>
      <resource>
        <directory>${basedir}/resources/server</directory>
        <filtering>false</filtering>
        <targetpath>/</targetpath>
        <includes>
          <include>**/*</include>
        </includes>
      </resource>
    </resources>
  </build>
  <properties>
    <keel.server>true</keel.server>
  </properties>
</project>



http://keelframework.org/documentation.shtml
Keelgroup mailing list
[email protected]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com