openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Albert Lee" <allee8...@gmail.com>
Subject Re: Maven build for Examples Integration Tests compile error
Date Thu, 01 Nov 2007 19:25:18 GMT
Once I get all the build steps sorted out for the Win32 platform, I'll
update the doc to reflect the required procedures.

Albert Lee.

On 11/1/07, Patrick Linskey <plinskey@gmail.com> wrote:
>
> That sounds like a good approach to me. Can you update the process
> docs accordingly?
>
> -Patrick
>
> On Oct 31, 2007 11:04 AM, Michael Dick <michael.d.dick@gmail.com> wrote:
> > Hi all,
> >
> > I think this should be a manual step whether you're working on a release
> > candidate or not. I've been trying to get this to work automatically via
> the
> > maven-antrun-plugin with limited success.
> >
> > The only reliable method that worked for me was to use the <exec> tag
> inside
> > ant to run another instance of ant.
> >
> > Besides being ugly this approach required me to have a standalone copy
> of
> > ant installed and on my path.
> >
> > It would be nice if we could automate running the samples through maven,
> but
> > since it's broken at the moment I think we should just manually run
> them.
> >
> > -Mike
> >
> >
> > On 10/30/07, Albert Lee <allee8285@gmail.com> wrote:
> > >
> > > We changed the inheritAll to "true" in
> > > openjpa-integration\examples\pom.xml,
> > > where it drilled down the test case tree's build.xml
> > >
> > >                         <subant inheritAll="true" failonerror="true">
> > >                             <fileset dir="${examples.base}"
> > >                                 includes="*/examples/*/build.xml"/>
> > >                         </subant>
> > >
> > > With this change, the compile target was successful but failed in the
> run
> > > target because the basedir was not the build.xml is expected. Hence we
> can
> > > either compile OR run but not both.
> > >
> > > How important is to exercise the examples-profile in preparation of
> the
> > > release candidate as documented in the "Making an OpenJPA Release"?
> Can
> > > this
> > > profile be run manually? What approach/strategy should it take to make
> > > sure
> > > we have a good release build?
> > >
> > > Advice is appreciated.
> > > Albert Lee.
> > >
> > > On 10/30/07, Patrick Linskey <plinskey@gmail.com> wrote:
> > > >
> > > > Yeah, I ran into this a while back. The automated build skips the
> > > > examples build for this reason.
> > > >
> > > > -Patrick
> > > >
> > > > On Oct 30, 2007 4:12 PM, Albert Lee <allee8285@gmail.com> wrote:
> > > > > I ran into the following compile errors in "Examples Integration
> > > Tests"
> > > > > module while doing the release build.
> > > > >
> > > > > I have the JAVA_HOME set to C:\Progra~1\IBM\Java50 but when the
> > > pom.xmlis
> > > > > run, the ${java.home} is changed to C:\Progra~1\IBM\Java50\jre.
> > > > >
> > > > > There are other modules compiling many Java files without any
> problem,
> > > > > except this module.
> > > > >
> > > > > Mike & I are trying to figure this out but have been scratching
> our
> > > > heads
> > > > > for a little while. Does anyone has any clue on what happens here?
> > > > >
> > > > > Thanks,
> > > > > Albert Lee.
> > > > >
> > > > > [INFO]
> > > > >
> > > >
> > >
> ----------------------------------------------------------------------------
> > > > > [INFO] Building OpenJPA Examples Integration Tests
> > > > > [INFO]    task-segment: [deploy, site]
> > > > > [INFO]
> > > > >
> > > >
> > >
> ----------------------------------------------------------------------------
> > > > > [INFO] Preparing javadoc:javadoc
> > > > > [WARNING] Removing: javadoc from forked lifecycle, to prevent
> > > recursive
> > > > > invocation.
> > > > > [INFO] No goals needed for project - skipping
> > > > > [INFO] [javadoc:javadoc {execution: default}]
> > > > > [INFO] [site:attach-descriptor]
> > > > > [INFO] [antrun:run {execution: run-examples}]
> > > > > [INFO] Executing tasks
> > > > >      [echo] Running OpenJPA Examples
> > > > >     [mkdir] Created dir:
> > > > >
> > > >
> > >
> C:\a.workspace\eclipse.workspace\ejb3.serv1\openjpa.101.cur\openjpa-integration\examples\target
> > > > > \examples
> > > > >     [unzip] Expanding:
> > > > >
> > > >
> > >
> C:\a.workspace\eclipse.workspace\ejb3.serv1\openjpa.101.cur\target\site\downloads\apache-openjpa-
> > > > > 1.0.1-binary.zip into
> > > > >
> > > >
> > >
> C:\a.workspace\eclipse.workspace\ejb3.serv1\openjpa.101.cur\openjpa-integration\examples\target\ex
> > > > > amples
> > > > >      [echo] ^^^11 ^^C:\Progra~1\IBM\Java50\jre
> > > > >
> > > > > pre-compile:
> > > > >
> > > > > compile:
> > > > >     [javac] Compiling 2 source files
> > > > > [INFO]
> > > > >
> > >
> ------------------------------------------------------------------------
> > > > > [ERROR] BUILD ERROR
> > > > > [INFO]
> > > > >
> > >
> ------------------------------------------------------------------------
> > > > > [INFO] Error executing ant tasks
> > > > >
> > > > > Embedded error: The following error occurred while executing this
> > > line:
> > > > >
> > > >
> > >
> C:\a.workspace\eclipse.workspace\ejb3.serv1\openjpa.101.cur\openjpa-integration\examples\target\examples\apache-openjpa-
> > > > > 1.0.1\examples\build.xml:73: Unable to find a javac compiler;
> > > > > com.sun.tools.javac.Main is not on the classpath.
> > > > > Perhaps JAVA_HOME does not point to the JDK
> > > > > [INFO]
> > > > >
> > >
> ------------------------------------------------------------------------
> > > > > [INFO] For more information, run Maven with the -e switch
> > > > > [INFO]
> > > > >
> > >
> ------------------------------------------------------------------------
> > > > > [INFO] Total time: 9 minutes 51 seconds
> > > > > [INFO] Finished at: Tue Oct 30 17:41:15 CDT 2007
> > > > > [INFO] Final Memory: 42M/177M
> > > > > [INFO]
> > > > >
> > >
> ------------------------------------------------------------------------
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Patrick Linskey
> > > > 202 669 5907
> > > >
> > >
> >
>
>
>
> --
> Patrick Linskey
> 202 669 5907
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message