Hi Karan

Thank you so much... that indeed fixed the build issue I have now.

I'm looking into how to hook up this code with the atinject tck...
i'll report back...

Lin

On Fri, Aug 13, 2010 at 12:38 PM, Karan Malhi <[email protected]> wrote:
> Hi Lin,
>
> I faced the same issue with compilation failures and had to checkout and
> build openwebbeans to ensure that openejb-jcdi compiles. Looks like the
> openwebbeans snapshot is not being updated in the maven repo or it could be
> something else -- not sure about this one.
>
> Yes, mvn clean install -DskipTests  is the correct way to do the build while
> skipping tests
>
> Regarding, some of the tests still running (MovieTest) and failing, that was
> an issue with the pom.xml. maven-surefire-plugin version was  set to 2.2 in
> our pom.xml and version 2.2 of that plugin does not recognize the skipTests
> property. I have updated our pom's to reflect the latest version of the
> surefire-plugin. You should now be able to update your working copy of
> openejb-jcdi and try to run the build again. It should build fine.
>
> On Fri, Aug 13, 2010 at 10:50 AM, Lin Sun <[email protected]> wrote:
>
>> Hi
>>
>> Thanks.  I didn't build openwebbeans first.
>>
>> So i went to build openwebbeans, then openejb-jcdi.
>>
>> I ran mvn clean install -DskipTests=true
>>
>> &
>>
>> mvn clean install -DskipTests=true -DskipiTests=true
>>
>> But still failed at a test error ( org.superbiz.moviefun.MoviesTest).
>> Is above the correct way to run build with test off?
>>
>> I did notice my openejb-core module builds fine.  Is this the only
>> project that uses openwebbean?
>>
>> Thanks
>>
>> Lin
>>
>>
>> On Thu, Aug 12, 2010 at 5:36 PM, David Blevins <[email protected]>
>> wrote:
>> >
>> > On Aug 12, 2010, at 1:35 PM, Lin Sun wrote:
>> >
>> >> Hi
>> >>
>> >> I am trying to build the new openejb-jcdi code.   Here is what I did
>> >> 1. check out code from
>> >> http://svn.apache.org/repos/asf/openejb/branches/openejb-jcdi/
>> >> 2. run mvn clean test, it failed at some junit failure
>> >> 3. run mvn clean test -DskipTests=true
>> >>
>> >> However, I am failing at many compilation errors like below -
>> >>
>> >> [INFO] Compiling 599 source files to
>> C:\openejb-jcdi\container\openejb-core\targ
>> >> et\classes
>> >> [INFO]
>> ------------------------------------------------------------------------
>> >> [ERROR] BUILD FAILURE
>> >> [INFO]
>> ------------------------------------------------------------------------
>> >> [INFO] Compilation failure
>> >>
>> >>
>> C:\openejb-jcdi\container\openejb-core\src\main\java\org\apache\openejb\util\Poj
>> >> oSerialization.java:[38,33] sun.misc.Unsafe is Sun proprietary API and
>> may be re
>> >> moved in a future release
>> >>
>> >>
>> C:\openejb-jcdi\container\openejb-core\src\main\java\org\apache\openejb\util\pro
>> >> xy\LocalBeanProxyGeneratorImpl.java:[30,33] sun.misc.Unsafe is Sun
>> proprietary A
>> >> PI and may be removed in a future release
>> >>
>> >> How can i get the openejb-jcdi project to build?   I am using sun jdk
>> >> 1.6.0_21 and maven 2.2.1
>> >
>> > The "sun.misc.Unsafe" lines are warnings and shouldn't cause any build
>> failures.  I don't know if the OpenWebBeans snapshots are current.
>> >
>> > I just checked out fresh copies of both[1][2] and built with tests off to
>> check for compilation errors and didn't have any compile issues.  You can
>> ignore or comment out any failed test cases.
>> >
>> > -David
>> >
>> >
>> >  [1] https://svn.apache.org/repos/asf/openwebbeans/trunk
>> >  [2] https://svn.apache.org/repos/asf/openejb/branches/openejb-jcdi
>> >
>> >
>>
>
>
>
> --
> Karan Singh Malhi
>

Reply via email to