You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by Woonsan Ko <wo...@yahoo.com> on 2013/10/07 20:27:26 UTC
Build error in trunk due to conflicting commons-beanutils depenencies
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
Re: Build error in trunk due to conflicting commons-beanutils depenencies
Posted by Woonsan Ko <wo...@yahoo.com>.
Hi Ate,
Thanks for the suggestion. That makes sense.
So, I think I should do the following:
- Add exclusion(s) on commons-beanutils-core after looking into all transitive dependencies.
- Add commons-beanutils dependency explicitly wherever used.
- Check all for any problematic transitive dependencies.
I'll create an issue for this and fix it soon.
Cheers,
Woonsan
>________________________________
> From: Ate Douma <at...@douma.nu>
>To: Jetspeed Developers List <je...@portals.apache.org>
>Sent: Tuesday, October 8, 2013 3:55 AM
>Subject: Re: Build error in trunk due to conflicting commons-beanutils depenencies
>
>
>On 10/07/2013 08:27 PM, Woonsan Ko 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.
>>
>We should only need/depend on commons-beanutils artifact, not ALSO on
>commons-beanutils-core. The first already contains 'everything' while the second
>one is a trimmed down version excluding commons-beanutils-bean-collections [1].
>So I would suggest that the transitive dependency on commons-beanutils-core
>should be excluded from ddlutils in jetspeed-serializer (and the
>commons-beanutils then should be explicitly added as an dependency there as well).
>
>I also would run a full mvn:dependency:tree on the whole of modules, to make
>sure no other component is (transitively) depending on commons-beanutils-core
>either.
>
>Ate
>
>[1]
>http://commons.apache.org/proper/commons-beanutils/index.html#BeanUtils_Core_And_Modules
>
>
>>
>> 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
>
>
>
>
>
Re: Build error in trunk due to conflicting commons-beanutils depenencies
Posted by Ate Douma <at...@douma.nu>.
On 10/07/2013 08:27 PM, Woonsan Ko 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.
>
We should only need/depend on commons-beanutils artifact, not ALSO on
commons-beanutils-core. The first already contains 'everything' while the second
one is a trimmed down version excluding commons-beanutils-bean-collections [1].
So I would suggest that the transitive dependency on commons-beanutils-core
should be excluded from ddlutils in jetspeed-serializer (and the
commons-beanutils then should be explicitly added as an dependency there as well).
I also would run a full mvn:dependency:tree on the whole of modules, to make
sure no other component is (transitively) depending on commons-beanutils-core
either.
Ate
[1]
http://commons.apache.org/proper/commons-beanutils/index.html#BeanUtils_Core_And_Modules
>
> 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
Re: Build error in trunk due to conflicting commons-beanutils depenencies
Posted by David Taylor <da...@gmail.com>.
> We are running Jetspeed 2.2.2 on Tomcat7.
With the 2.2.2 release, we did some work to make Jetspeed run on Tomcat7.
We got pretty close. However, there are still issues outline here. :
https://issues.apache.org/jira/browse/JS2-1274
https://issues.apache.org/jira/browse/JS2-1255
If you have addressed the problems, it would be great if you could share
solutions with the community
> Java 6 was released in 2006 and Java 7 in 2011.
We will support building on Java 7 with the next major upgrade, not 2.2.3,
but 2.3. But yes, you can run on Java7
On Tue, Oct 8, 2013 at 11:22 AM, Ron Wheeler <rwheeler@artifact-software.com
> wrote:
> Maven 3.1.1 is the current Maven.
> We are running Jetspeed 2.2.2 on Tomcat7.
> We using Spring 3.2.4 and compiling with Java 7.
> Java 6 was released in 2006 and Java 7 in 2011.
>
> Ron
>
>
> On 08/10/2013 1:35 PM, David Taylor wrote:
>
>> Great. So you build with this command?
>>
>> mvn clean install
>>
>> What about these commands, do they now work with Maven-3 ...
>>
>> mvn jetspeed:mvn -Dtarget=testdb
>> mvn test -P test
>>
>> mvn jetspeed:mvn -Dtarget=min
>> mvn jetspeed:mvn -Dtarget=demo
>>
>>
>> On Tue, Oct 8, 2013 at 10:31 AM, Woonsan Ko <wo...@yahoo.com> wrote:
>>
>> Hi David,
>>>
>>> I've just fixed the issue by excluding commons-beanutils-core from the
>>> ddlutils dependency definition and adding explicit dependencies wherever
>>> (jetspeed-portal and jetspeed-serializer) used:
>>> - https://issues.apache.org/**jira/browse/JS2-1288<https://issues.apache.org/jira/browse/JS2-1288>
>>>
>>> Now, it seems the build works fine even with Maven 3.0.3 (Java 1.6) from
>>> here.
>>>
>>>
>>> Cheers,
>>>
>>> Woonsan
>>>
>>>
>>>
>>>
>>> ______________________________**__
>>>> From: David Taylor <da...@gmail.com>
>>>> To: Jetspeed Developers List <je...@portals.apache.org>>;
>>>> Woonsan
>>>>
>>> Ko <wo...@yahoo.com>
>>>
>>>> Sent: Tuesday, October 8, 2013 11:43 AM
>>>> Subject: Re: Build error in trunk due to conflicting commons-beanutils
>>>>
>>> depenencies
>>>
>>>>
>>>> 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...
>>>>
>>>>
>>>>
>>>> On Mon, Oct 7, 2013 at 11:27 AM, Woonsan Ko <wo...@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<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>
>>>
>>>>
>>>>
>>>> --
>>>> David
>>>>
>>>>
>>>>
>>>>
>>>>
>>
>>
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwheeler@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@**portals.apache.org<je...@portals.apache.org>
> For additional commands, e-mail: jetspeed-dev-help@portals.**apache.org<je...@portals.apache.org>
>
>
--
David
Re: Build error in trunk due to conflicting commons-beanutils depenencies
Posted by Ron Wheeler <rw...@artifact-software.com>.
Maven 3.1.1 is the current Maven.
We are running Jetspeed 2.2.2 on Tomcat7.
We using Spring 3.2.4 and compiling with Java 7.
Java 6 was released in 2006 and Java 7 in 2011.
Ron
On 08/10/2013 1:35 PM, David Taylor wrote:
> Great. So you build with this command?
>
> mvn clean install
>
> What about these commands, do they now work with Maven-3 ...
>
> mvn jetspeed:mvn -Dtarget=testdb
> mvn test -P test
>
> mvn jetspeed:mvn -Dtarget=min
> mvn jetspeed:mvn -Dtarget=demo
>
>
> On Tue, Oct 8, 2013 at 10:31 AM, Woonsan Ko <wo...@yahoo.com> wrote:
>
>> Hi David,
>>
>> I've just fixed the issue by excluding commons-beanutils-core from the
>> ddlutils dependency definition and adding explicit dependencies wherever
>> (jetspeed-portal and jetspeed-serializer) used:
>> - https://issues.apache.org/jira/browse/JS2-1288
>>
>> Now, it seems the build works fine even with Maven 3.0.3 (Java 1.6) from
>> here.
>>
>>
>> Cheers,
>>
>> Woonsan
>>
>>
>>
>>
>>> ________________________________
>>> From: David Taylor <da...@gmail.com>
>>> To: Jetspeed Developers List <je...@portals.apache.org>; Woonsan
>> Ko <wo...@yahoo.com>
>>> Sent: Tuesday, October 8, 2013 11:43 AM
>>> Subject: Re: Build error in trunk due to conflicting commons-beanutils
>> depenencies
>>>
>>> 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...
>>>
>>>
>>>
>>> On Mon, Oct 7, 2013 at 11:27 AM, Woonsan Ko <wo...@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
>>>
>>>
>>> --
>>> David
>>>
>>>
>>>
>>>
>
>
--
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Build error in trunk due to conflicting commons-beanutils depenencies
Posted by David Taylor <da...@gmail.com>.
The tests almost pass for me with 3.0.3, everything passes except this:
mvn test -P test
....
[INFO] Jetspeed-2 Demo Portal Application ................ FAILURE [0.615s]
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1:59.705s
[INFO] Finished at: Tue Oct 08 11:23:13 PDT 2013
[INFO] Final Memory: 97M/210M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.portals.jetspeed-2:jetspeed-deploy-maven-plugin:2.2.3-SNAPSHOT:deploy
(deploy-jetspeed-layouts) on project jetspeed-demo: Failed to copy
/Users/dtaylor/apache/jetspeed-2/applications/jetspeed-layouts/target/classes
to
/Users/dtaylor/apache/jetspeed-2/applications/jetspeed-demo/target/jetspeed-demo-2.2.3-SNAPSHOT/WEB-INF/deploy/local/jetspeed-layouts.war:
/Users/dtaylor/apache/jetspeed-2/applications/jetspeed-layouts/target/classes
(No such file or directory) -> [Help 1]
mvn jetspeed:mvn -Dtarget=min
and
mvn jetspeed:mvn -Dtarget=demo
now passes!
On Tue, Oct 8, 2013 at 11:10 AM, Woonsan Ko <wo...@yahoo.com> wrote:
> Hi David,
>
> The following commands work fine now with Maven 3.0.3:
>
>
> $ mvn clean install
>
> $ mvn jetspeed:mvn -Dtarget=min
> $ mvn jetspeed:mvn -Dtarget=demo
> However, when I run tests by the following commands, I noticed unit test
> errors/failures:
>
> $ export MAVEN_OPTS="-Xmx256m -XX:MaxPermSize=256m"
> $ mvn jetspeed:mvn -Dtarget=testdb
> $ mvn jetspeed:mvn -Dtarget=test
>
> The errors come out first in the jetspeed-security component:
>
>
> -------------------------------------------------------------------------------
> Test set: org.apache.jetspeed.security.mapping.ldap.setup1.TestLDAP1
>
> -------------------------------------------------------------------------------
> Tests run: 7, Failures: 0, Errors: 6, Skipped: 0, Time elapsed: 2.425 sec
> <<< FAILURE!
> ldapTestSetup(org.apache.jetspeed.security.mapping.ldap.setup1.TestLDAP1)
> Time elapsed: 2.329 sec <<< ERROR!
> org.apache.directory.shared.ldap.exception.LdapConfigurationException:
> Failed to bind an LDAP service (10389) to the service registry. [Root
> exception is java.net.BindException: Address already in use]
> at
> org.apache.directory.server.ldap.LdapServer.startNetwork(LdapServer.java:528)
> at
> org.apache.directory.server.ldap.LdapServer.start(LdapServer.java:394)
> at
> org.apache.jetspeed.security.EmbeddedApacheDSTestService.start(EmbeddedApacheDSTestService.java:82)
> at
> org.apache.jetspeed.security.mapping.ldap.AbstractLDAPTest.ldapTestSetup(AbstractLDAPTest.java:77)
> ...
>
> It looks like TestLDAP1 opening an LDAP server..
> Anyway, it doesn't look related to Maven-3 issue to me, but the LDAP
> related unit tests have failed in the trunk..
>
> Regards,
>
> Woonsan
>
>
>
>
> ----- Original Message -----
> > From: David Taylor <da...@gmail.com>
> > To: Jetspeed Developers List <je...@portals.apache.org>; Woonsan
> Ko <wo...@yahoo.com>
> > Cc:
> > Sent: Tuesday, October 8, 2013 1:35 PM
> > Subject: Re: Build error in trunk due to conflicting commons-beanutils
> depenencies
> >
> >G reat. So you build with this command?
> >
> > mvn clean install
> >
> > What about these commands, do they now work with Maven-3 ...
> >
> > mvn jetspeed:mvn -Dtarget=testdb
> > mvn test -P test
> >
> > mvn jetspeed:mvn -Dtarget=min
> > mvn jetspeed:mvn -Dtarget=demo
> >
> >
> >
> > On Tue, Oct 8, 2013 at 10:31 AM, Woonsan Ko <wo...@yahoo.com> wrote:
> >
> >> Hi David,
> >>
> >> I've just fixed the issue by excluding commons-beanutils-core from the
> >> ddlutils dependency definition and adding explicit dependencies
> wherever
> >> (jetspeed-portal and jetspeed-serializer) used:
> >> - https://issues.apache.org/jira/browse/JS2-1288
> >>
> >> Now, it seems the build works fine even with Maven 3.0.3 (Java 1.6)
> from
> >> here.
> >>
> >>
> >> Cheers,
> >>
> >> Woonsan
> >>
> >>
> >>
> >>
> >> >________________________________
> >> > From: David Taylor <da...@gmail.com>
> >> >To: Jetspeed Developers List <je...@portals.apache.org>;
> > Woonsan
> >> Ko <wo...@yahoo.com>
> >> >Sent: Tuesday, October 8, 2013 11:43 AM
> >> >Subject: Re: Build error in trunk due to conflicting commons-beanutils
> >> depenencies
> >> >
> >> >
> >> >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...
> >> >
> >> >
> >> >
> >> >On Mon, Oct 7, 2013 at 11:27 AM, Woonsan Ko <wo...@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
> >> >>
> >> >
> >> >
> >> >
> >> >--
> >> >David
> >> >
> >> >
> >> >
> >> >
> >>
> >
> >
> >
> > --
> > David
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
--
David
Re: Build error in trunk due to conflicting commons-beanutils depenencies
Posted by Woonsan Ko <wo...@yahoo.com>.
Hi David,
The following commands work fine now with Maven 3.0.3:
$ mvn clean install
$ mvn jetspeed:mvn -Dtarget=min
$ mvn jetspeed:mvn -Dtarget=demo
However, when I run tests by the following commands, I noticed unit test errors/failures:
$ export MAVEN_OPTS="-Xmx256m -XX:MaxPermSize=256m"
$ mvn jetspeed:mvn -Dtarget=testdb
$ mvn jetspeed:mvn -Dtarget=test
The errors come out first in the jetspeed-security component:
-------------------------------------------------------------------------------
Test set: org.apache.jetspeed.security.mapping.ldap.setup1.TestLDAP1
-------------------------------------------------------------------------------
Tests run: 7, Failures: 0, Errors: 6, Skipped: 0, Time elapsed: 2.425 sec <<< FAILURE!
ldapTestSetup(org.apache.jetspeed.security.mapping.ldap.setup1.TestLDAP1) Time elapsed: 2.329 sec <<< ERROR!
org.apache.directory.shared.ldap.exception.LdapConfigurationException: Failed to bind an LDAP service (10389) to the service registry. [Root exception is java.net.BindException: Address already in use]
at org.apache.directory.server.ldap.LdapServer.startNetwork(LdapServer.java:528)
at org.apache.directory.server.ldap.LdapServer.start(LdapServer.java:394)
at org.apache.jetspeed.security.EmbeddedApacheDSTestService.start(EmbeddedApacheDSTestService.java:82)
at org.apache.jetspeed.security.mapping.ldap.AbstractLDAPTest.ldapTestSetup(AbstractLDAPTest.java:77)
...
It looks like TestLDAP1 opening an LDAP server..
Anyway, it doesn't look related to Maven-3 issue to me, but the LDAP related unit tests have failed in the trunk..
Regards,
Woonsan
----- Original Message -----
> From: David Taylor <da...@gmail.com>
> To: Jetspeed Developers List <je...@portals.apache.org>; Woonsan Ko <wo...@yahoo.com>
> Cc:
> Sent: Tuesday, October 8, 2013 1:35 PM
> Subject: Re: Build error in trunk due to conflicting commons-beanutils depenencies
>
>G reat. So you build with this command?
>
> mvn clean install
>
> What about these commands, do they now work with Maven-3 ...
>
> mvn jetspeed:mvn -Dtarget=testdb
> mvn test -P test
>
> mvn jetspeed:mvn -Dtarget=min
> mvn jetspeed:mvn -Dtarget=demo
>
>
>
> On Tue, Oct 8, 2013 at 10:31 AM, Woonsan Ko <wo...@yahoo.com> wrote:
>
>> Hi David,
>>
>> I've just fixed the issue by excluding commons-beanutils-core from the
>> ddlutils dependency definition and adding explicit dependencies wherever
>> (jetspeed-portal and jetspeed-serializer) used:
>> - https://issues.apache.org/jira/browse/JS2-1288
>>
>> Now, it seems the build works fine even with Maven 3.0.3 (Java 1.6) from
>> here.
>>
>>
>> Cheers,
>>
>> Woonsan
>>
>>
>>
>>
>> >________________________________
>> > From: David Taylor <da...@gmail.com>
>> >To: Jetspeed Developers List <je...@portals.apache.org>;
> Woonsan
>> Ko <wo...@yahoo.com>
>> >Sent: Tuesday, October 8, 2013 11:43 AM
>> >Subject: Re: Build error in trunk due to conflicting commons-beanutils
>> depenencies
>> >
>> >
>> >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...
>> >
>> >
>> >
>> >On Mon, Oct 7, 2013 at 11:27 AM, Woonsan Ko <wo...@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
>> >>
>> >
>> >
>> >
>> >--
>> >David
>> >
>> >
>> >
>> >
>>
>
>
>
> --
> David
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Build error in trunk due to conflicting commons-beanutils depenencies
Posted by David Taylor <da...@gmail.com>.
Great. So you build with this command?
mvn clean install
What about these commands, do they now work with Maven-3 ...
mvn jetspeed:mvn -Dtarget=testdb
mvn test -P test
mvn jetspeed:mvn -Dtarget=min
mvn jetspeed:mvn -Dtarget=demo
On Tue, Oct 8, 2013 at 10:31 AM, Woonsan Ko <wo...@yahoo.com> wrote:
> Hi David,
>
> I've just fixed the issue by excluding commons-beanutils-core from the
> ddlutils dependency definition and adding explicit dependencies wherever
> (jetspeed-portal and jetspeed-serializer) used:
> - https://issues.apache.org/jira/browse/JS2-1288
>
> Now, it seems the build works fine even with Maven 3.0.3 (Java 1.6) from
> here.
>
>
> Cheers,
>
> Woonsan
>
>
>
>
> >________________________________
> > From: David Taylor <da...@gmail.com>
> >To: Jetspeed Developers List <je...@portals.apache.org>; Woonsan
> Ko <wo...@yahoo.com>
> >Sent: Tuesday, October 8, 2013 11:43 AM
> >Subject: Re: Build error in trunk due to conflicting commons-beanutils
> depenencies
> >
> >
> >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...
> >
> >
> >
> >On Mon, Oct 7, 2013 at 11:27 AM, Woonsan Ko <wo...@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
> >>
> >
> >
> >
> >--
> >David
> >
> >
> >
> >
>
--
David
Re: Build error in trunk due to conflicting commons-beanutils depenencies
Posted by Woonsan Ko <wo...@yahoo.com>.
Hi David,
I've just fixed the issue by excluding commons-beanutils-core from the ddlutils dependency definition and adding explicit dependencies wherever (jetspeed-portal and jetspeed-serializer) used:
- https://issues.apache.org/jira/browse/JS2-1288
Now, it seems the build works fine even with Maven 3.0.3 (Java 1.6) from here.
Cheers,
Woonsan
>________________________________
> From: David Taylor <da...@gmail.com>
>To: Jetspeed Developers List <je...@portals.apache.org>; Woonsan Ko <wo...@yahoo.com>
>Sent: Tuesday, October 8, 2013 11:43 AM
>Subject: Re: Build error in trunk due to conflicting commons-beanutils depenencies
>
>
>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...
>
>
>
>On Mon, Oct 7, 2013 at 11:27 AM, Woonsan Ko <wo...@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
>>
>
>
>
>--
>David
>
>
>
>
Re: Build error in trunk due to conflicting commons-beanutils depenencies
Posted by Woonsan Ko <wo...@yahoo.com>.
>________________________________
> From: Ate Douma <at...@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 <wo...@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
Re: Build error in trunk due to conflicting commons-beanutils depenencies
Posted by Ate Douma <at...@douma.nu>.
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?
>
>
> On Mon, Oct 7, 2013 at 11:27 AM, Woonsan Ko <wo...@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
Re: Build error in trunk due to conflicting commons-beanutils depenencies
Posted by David Taylor <da...@gmail.com>.
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...
On Mon, Oct 7, 2013 at 11:27 AM, Woonsan Ko <wo...@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
>
--
David