portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Woonsan Ko <woon_...@yahoo.com>
Subject Re: Build error in trunk due to conflicting commons-beanutils depenencies
Date Tue, 08 Oct 2013 17:48:15 GMT







>________________________________
> From: Ate Douma <ate@douma.nu>
>To: jetspeed-dev@portals.apache.org 
>Sent: Tuesday, October 8, 2013 1:31 PM
>Subject: Re: Build error in trunk due to conflicting commons-beanutils depenencies
> 
>
>On 10/08/2013 05:43 PM, David Taylor wrote:
>> I just built with Maven 2.2.1, and no errors. I see the same problem you
>> are seeing with Maven 3.0.3. Lets try to see what it takes to get this
>> working with Maven-3...
>Then maybe transitive dependency resolution works a bit different between 
>Maven-2 and Maven-3?

I guess not.
The dependency tree shows the same thing with Maven-2.2.1 under jetspeed-portal module before
committing the fix:

[INFO] [dependency:tree {execution: default-cli}]
[INFO] org.apache.portals.jetspeed-2:jetspeed-portal:jar:2.2.3-SNAPSHOT
[INFO] +- org.apache.portals.jetspeed-2:jetspeed-registry:jar:2.2.3-SNAPSHOT:compile
[INFO] |  \- org.apache.portals.jetspeed-2:jetspeed-serializer:jar:2.2.3-SNAPSHOT:compile
[INFO] |     \- org.apache.ddlutils:ddlutils:jar:1.0:compile
[INFO] |        \- commons-betwixt:commons-betwixt:jar:0.8:compile
[INFO] |           \- commons-beanutils:commons-beanutils-core:jar:1.7.0:compile
[INFO] \- commons-beanutils:commons-beanutils:jar:1.8.0:compile

I was able to build it with Maven-3 for the Jetspeed-2.2.2 tag, but it failed to build with
maven 3 for the trunk since late July this year.
So, I assume something else affected the build somehow.
I noticed that the java compiler version has been changed to 1.6 recently in the trunk. Maybe
that affected the classpath resolution somehow?
Not sure, but anyway it's working fine now.

Regards,

Woonsan



>
>
>>
>>
>> On Mon, Oct 7, 2013 at 11:27 AM, Woonsan Ko <woon_san@yahoo.com> wrote:
>>
>>> Hi,
>>>
>>> I've met a weird build error from the fresh JS-2 trunk today
>>> (Maven3/JDK1.6):
>>>
>>> ...
>>>
>>> INFO] Jetspeed-2 Portal Site ............................ SUCCESS [0.973s]
>>> [INFO] Jetspeed-2 Portal Components ...................... FAILURE [2.046s]
>>> ...
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> ...
>>>
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
>>> (default-compile) on project jetspeed-portal: Compilation failure:
>>> Compilation failure:
>>> [ERROR]
>>> /Users/woonsan/workspace/portal/jetspeed-2-TRUNK/components/jetspeed-portal/src/main/java/org/apache/jetspeed/services/rest/JaxrsServiceValve.java:[55,23]
>>> cannot find symbol
>>> [ERROR] symbol  : method invokeStaticMethod(java.lang.Class<capture#657 of
>>> ?>,java.lang.String,java.lang.Object[])
>>> [ERROR] location: class org.apache.commons.beanutils.MethodUtils
>>>
>>> ...
>>>
>>>
>>> So, I ran `mvn dependency:tree -Dincludes=commons-beanutils' in the
>>> components/jetspeed-portal module folder:
>>>
>>>
>>> [INFO] org.apache.portals.jetspeed-2:jetspeed-portal:jar:2.2.3-SNAPSHOT
>>> [INFO] +-
>>> org.apache.portals.jetspeed-2:jetspeed-registry:jar:2.2.3-SNAPSHOT:compile
>>> [INFO] |  \-
>>> org.apache.portals.jetspeed-2:jetspeed-serializer:jar:2.2.3-SNAPSHOT:compile
>>> [INFO] |     \- org.apache.ddlutils:ddlutils:jar:1.0:compile
>>> [INFO] |        \- commons-betwixt:commons-betwixt:jar:0.8:compile
>>> [INFO] |           \-
>>> commons-beanutils:commons-beanutils-core:jar:1.7.0:compile
>>> [INFO] \- org.apache.velocity:velocity-tools:jar:1.3:compile
>>> [INFO]    \- commons-beanutils:commons-beanutils:jar:1.8.0:compile
>>>
>>>
>>>
>>> The above clearly shows it depends on two different versions of
>>> commons-beanutils. The API, MethodUtils#invokeStaticMethod() [1]
>>> has been introduced since 1.8.I don't know why/when this problem started
>>> staying here, but I think we should add the explicit dependencies in
>>> components/jetspeed-portal/pom.xml like the following:
>>>
>>>      <dependency>
>>>        <groupId>commons-beanutils</groupId>
>>>        <artifactId>commons-beanutils</artifactId>
>>>      </dependency>
>>>      <dependency>
>>>        <groupId>commons-beanutils</groupId>
>>>        <artifactId>commons-beanutils-core</artifactId>
>>>      </dependency>
>>>
>>>
>>> In my local testing, this solves the problem. So I'll add commit it soon.
>>> Please let me know if there's anything I missed.
>>>
>>>
>>> Thanks!
>>>
>>> Regards,
>>>
>>> Woonsan
>>>
>>>
>>> [1]
>>> http://commons.apache.org/proper/commons-beanutils/javadocs/v1.8.3/apidocs/org/apache/commons/beanutils/MethodUtils.html#invokeStaticMethod%28java.lang.Class,%20java.lang.String,%20java.lang.Object[]%29
>>>
>>
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
>For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message