continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dan tran <dant...@gmail.com>
Subject Re: Compile error doesn't cause build failure on M2
Date Fri, 02 Dec 2005 19:33:03 GMT
opps, sorry i posted onthe wrong topic

-Dan



On 12/2/05, dan tran <dantran@gmail.com> wrote:
>
> I think we should reverse the changes and put it back when  maven 2.0.1 is
> released.
>
> It is hard for me to ask my user to use 2.0.1 bootstrap, inorder to do
> release and maven:scm-bootstrap
>
> -Dan
>
>
>
> On 12/2/05, Emmanuel Venisse <emmanuel@venisse.net> wrote:
> >
> > comments below
> >
> > Eric Pugh (OSC2) a écrit :
> > > Hi all,
> > >
> > > I've seen in the archives some posts about Ant and M1 build failures
> > > not being propagated back properly.  However, I am noticing the same
> > > thing under M2.  I intentionally put in a compile error:
> > > Compiling 35 source files to C:\continuum-1.0.1\apps\continuum
> > > \working-directory\1\target\classes
> > > [INFO]
> > >
> > ------------------------------------------------------------------------
> > > ----
> > > [ERROR] BUILD FAILURE
> > > [INFO]
> > >
> > ------------------------------------------------------------------------
> > > ----
> > > [INFO] Compilation failure
> > >
> > > C:\continuum-1.0.1\apps\continuum\working-directory\1\src\main\java
> > > \com\ergito\search\SimpleTermHighlighter.java:[22,20] cannot find
> > symbol
> > > symbol  : variable sSuffix
> > > location: class com.ergito.search.SimpleTermHighlighter
> > >
> > > how ever my builds are considered successes:
> > > 2005-12-02 08:14:22,035 [Thread-1] WARN
> > ContinuumBuildExecutor:maven2
> > > - Execut
> > > able 'c:\maven-2.0\bin\mvn'.
> > > 2005-12-02 08:14:22,035 [Thread-1] INFO
> > ContinuumBuildExecutor:maven2
> > > - Argume
> > > nts: --batch-mode --non-recursive clean install
> > > 2005-12-02 08:14:22,035 [Thread-1] INFO
> > ContinuumBuildExecutor:maven2
> > > - Workin
> > > g directory: C:\continuum-1.0.1\bin\..\apps\continuum\working-directory\1
> > > 2005-12-02 08:14:35,629 [Thread-1] INFO
> > ContinuumBuildExecutor:maven2
> > > - Exit c
> > > ode: 0
> > > 2005-12-02 08:14:35,848 [Thread-1] INFO   Notifier:mail
> > > - Curren
> > > t build state: 2, previous build state: 2
> > >
> > > In the FAQ Entry: How does Continuum detect a successful build?
> > > It refers to maven or ant, but I'm not sure if that means "maven1 and
> > > maven2".
> >
> > I don't specify maven version because it's for several maven version (
> > 1.0.2 and 2.0, perhaps 1.1 too)
> > It's fixed in subversion for maven 1.1 and maven 2, so when they will be
> > release, this step won't be
> > necessary.
> >
> > > Also, the line about adding something to the beginning of
> > > run.bat:
> > > <quote>
> > > You must add too, at the begin of $CONTINUUM/bin/win32/run.bat, the
> > > following lines if you run Continuum from command line :
> > > </quote>
> > > seems to suggest you should use the wrapper run.bat versus the
> > > plexus.bat method?
> >
> > run.bat is the preferred method.
> > I'll in faqs run.bat or plexus.bat
> >
> > >
> > > Lastly, adding set.MAVEN_TERMINATE_CMD=0n to the wrapper.conf seems
> > > like to should come that way?
> >
> > wrapper.conf is use by run.bat and by InstallService.bat. It's better to
> > define thevalue in
> > wrapper.conf.
> >
> > In continuum 1.0.2, this step won't be necessary.
> >
> > If you think the faq isn't very understandable, you can create a patch.
> >
> > Emmanuel
> >
> >
>

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