Isn't that what the Build Fresh option on the build definition is for?
Doesn't it delete the working directory and re-checkout from scm?
http://jira.codehaus.org/browse/CONTINUUM-1312
vote for it
--tom
In the instructions for upgrading from beta2 to beta3 at
http://maven.apache.org/continuum/guides/mini/guide-data-management.html
the last line reads:
NEXT_VAL values in SEQUENCE_TABLE must be checked before restarting continuum
What does that mean, how do we check it and how do we know if it is
This started happening after upgrading from maven 2.0.6.
Has anybody else experienced this?
--
tom
It doesn't sound like the build is still running. It sounds like the
project still looks like it's building because of the icon. I've had
this happen several times.
I clear it up by adding a build definition to the project and specify
the goal as -v (which just gives the maven version) then I r
Will there be a way to force the build even though there were no scm changes?
I have projects that generate code from database metadata. If a
database change occurs I would need the forced build (scheduled
nightly) to still occur so that database changes are pick up and the
system is rebuilt. Cu
Yes, it's 1 level under the root. I could move it up to the root but
there are far too many reletive references in it that would have to
change.
On 11/29/05, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
> your file is in a sub-directory?
>
> Emmanuel
>
> Tomislav Sto
Added http://jira.codehaus.org/browse/CONTINUUM-459
On 11/18/05, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
> I'll check it. File a jira issue, so i wouldn't lose it.
>
> Emmanuel
>
> Tomislav Stojcevich a écrit :
> > The same thing happens to me. I did sel
