You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by Neon <tr...@gmail.com> on 2010/04/14 19:05:08 UTC
Adding a Shell Project also adds a Maven 2 build definition
I am using Continuum 1.3.6 in stand-alone mode under RHEL 5.
When I add a new shell project using the "Default Shell Project", It
also adds the "Default Maven 2 Build Definition"
Goals Arguments Build
File Schedule Build Environment From
Build Fresh Default Description
Type
clean install --batch-mode --non-recursive pom.xml
DEFAULT_SCHEDULE GROUP false
false Default Maven 2 Build Definition maven2
mytest.csh NIGHTLY_3AM Java5
PROJECT false true Default Shell Build
Definition shell
Then for some reason, continuum tries to build the "Default Maven 2
Build Definition" even though that is NOT the default which then fails
(since my project does not use Maven).
Is this a bug in Continuum 1.3.6? I did not have this problem under
Continuum 1.3.4.
I am running Continuum 1.3.6 in standalone mode vs under Tomcat 5.5.28
for my Continuum 1.3.4 setup.
Regards,
Neon
Re: Adding a Shell Project also adds a Maven 2 build definition
Posted by Brett Porter <br...@apache.org>.
I haven't confirmed, but you can certainly file a bug report (when JIRA is back up) at http://jira.codehaus.org/browse/CONTINUUM and we'll look into it.
Thanks,
Brett
On 15/04/2010, at 3:05 AM, Neon wrote:
> I am using Continuum 1.3.6 in stand-alone mode under RHEL 5.
>
> When I add a new shell project using the "Default Shell Project", It
> also adds the "Default Maven 2 Build Definition"
> Goals Arguments Build
> File Schedule Build Environment From
> Build Fresh Default Description
> Type
> clean install --batch-mode --non-recursive pom.xml
> DEFAULT_SCHEDULE GROUP false
> false Default Maven 2 Build Definition maven2
>
> mytest.csh NIGHTLY_3AM Java5
> PROJECT false true Default Shell Build
> Definition shell
>
> Then for some reason, continuum tries to build the "Default Maven 2
> Build Definition" even though that is NOT the default which then fails
> (since my project does not use Maven).
>
> Is this a bug in Continuum 1.3.6? I did not have this problem under
> Continuum 1.3.4.
>
> I am running Continuum 1.3.6 in standalone mode vs under Tomcat 5.5.28
> for my Continuum 1.3.4 setup.
>
> Regards,
>
> Neon
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/