Res Pons | 5 Mar 23:50
Picon

I need help with project concept

Sorry to post across the userlists.

I'm using Subversion, Ant, and Anthill OS to automate my projects.  We 
release many products in different projects.

Currently I have set up a property sheet in Anthill for each project's 
build.xml and everything works fine.  However, many of the projects create a 
.jar file which is used or needed by other projects.  I tell my build.xml 
file in each project where to get the compiled jar files.

With so many jar files being copied all over and our projects growing larger 
and larger daily, I was asked to create my own top parallel project and call 
all the build files from my master proj and make this project the exchange 
folder for all the jar files or any other artifact.  It's a cleaner way, of 
course and more contained but it entails more work on my part.

I've got my master build file to work, running at the cmnd prompt, however, 
Anthill does not like it when you tell a build file to check out other top 
level project files from the repo.  Should I create dummy project files in 
Anthill just to check out the other projects and then let my build file take 
control?

Somebody please give me guidance on the big picture.  Is this a good idea to 
have a master and separate build project aware of all the other projects and 
but the other projects not being aware of it? How do I bypass the Anthill's 
shortcoming? By switching to CruiseControl?  Are there or do you have any 
examples I could see please?

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! 
(Continue reading)

Res Pons | 5 Mar 23:51
Picon

I need help with project concept

Sorry to post across the userlists.

I'm using Subversion, Ant, and Anthill OS to automate my projects.  We 
release many products in different projects.

Currently I have set up a property sheet in Anthill for each project's 
build.xml and everything works fine.  However, many of the projects create a 
.jar file which is used or needed by other projects.  I tell my build.xml 
file in each project where to get the compiled jar files.

With so many jar files being copied all over and our projects growing larger 
and larger daily, I was asked to create my own top parallel project and call 
all the build files from my master proj and make this project the exchange 
folder for all the jar files or any other artifact.  It's a cleaner way, of 
course and more contained but it entails more work on my part.

I've got my master build file to work, running at the cmnd prompt, however, 
Anthill does not like it when you tell a build file to check out other top 
level project files from the repo.  Should I create dummy project files in 
Anthill just to check out the other projects and then let my build file take 
control?

Somebody please give me guidance on the big picture.  Is this a good idea to 
have a master and separate build project aware of all the other projects and 
but the other projects not being aware of it? How do I bypass the Anthill's 
shortcoming? By switching to CruiseControl?  Are there or do you have any 
examples I could see please?

_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar – get it now! 
(Continue reading)

Eric Minick | 6 Mar 06:24

Re: I need help with project concept

Res,

I believe this is a fairly classic dependency management question with 
several decent answers. The 'master build script' approach you have 
taken is somewhat similar to the approach some Maven projects take. 
Personally, I'm not a big fan of the approach, but it certainly works 
for a number of organizations.

Anthill does have a dependency support mechanism of its own. At a high 
level what it does is allow you to specify groups of projects that have 
dependency relationships. You would then build these groups of projects 
together and Anthill would tell your build scripts where to find the 
shared jars - and likewise where to deliver the jars. You would need to 
tweak your build scripts, but probably wouldn't need to overhaul them. 
If this sounds like a viable approach, let us know and we can talk about 
that in more depth. As a side note, Anthill Pro does something similar 
but uses a different model to manage the dependencies. If the Anthill OS 
model doesn't work for you, it might be worth a look.

If you are really serious about dependencies and don't really want your 
build system managing them, I would use Ivy. The tool has been out for 
about a year and while young is really nice. Instead of copying jar 
files around, you use ivy to 'publish' them to a repository. Each 
project will also have a file where you list out the jars (and versions 
of jars) it is dependent on. When you start a build, you run an Ant task 
to retrieve the dependencies first thing. The repository is usually just 
files copied to the file system, but I believe there are extensions 
available to back it to Subversion.

The nice thing about Ivy is that dependencies are handled the same way 
(Continue reading)

Varban | 9 Mar 14:54

ClearCase UCM build/release process input needed

Hello,

we are currently working on the development of Anthill3 and in an effort to 
make the new version as flexible and adaptive as possible we need input from 
ClearCase UCM users about their standard process of build and release. 
We are interested to know what features you need for your regular process 
(update, rebase, baseline, promotion...), how/when/where the builds are done 
(building from integration/development stream, using a new/existing view for 
the builds, snapshot or dynamic views, separate streams for builds and 
development/release), how is branching handled (using streams or baselines 
or...), how are rebuilds of previous releases done and anything that you 
think is important for your build process.

Any input will be greatly appreciated and will contribute to making Anthill3 
an even better and more flexible product.

Thanks!
The Urbancode team
Res Pons | 9 Mar 19:43
Picon

Preventing Anthill OS to check out

I need your feedback please.

Is it a good or bad idea to fool AH-os to check out my master build project 
and from there starts calling other projects ( already checked out) to build 
and at the beging of this master build file make a system exec call to 
update these working folder before doing the build.  This will shave off so 
much time off my build times.  Especailly since AH would like to clean 
entire working folder and do a fresh complete check out of the repo.  Right 
now my buidls start @12:30 am and end around 5am with so many projects being 
built and growing...

I know Anthill pretty much doesn't like it when within your ant file you 
make it do repository check outs/ins across projects and AH would prefer 
that you set separate property sheets or AH-projects for each development 
proj.

Now on page 35 of the manual I sse that I could set log4j.rootCategory=DEBUG 
to prevent check outs...but I couldn't get it to work and AH still continued 
to delete and do fresh check out.

Thanks.

_________________________________________________________________
Don’t just search. Find. Check out the new MSN Search! 
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
Varban | 9 Mar 20:44

Re: Preventing Anthill OS to check out

Hi Res,

you can use the file system driver and have your build scripts do the 
repository work any way you want. This way Anthill will do nothing but run 
your build scripts and post the results. This however means that you need to 
write the repository tasks and include them in your build script (or a 
separate build script that you can call if the build is done via AnthillOS).
I believe there are many AnthillOS users that have taken this approach when 
the driver implementations do not suit their needs. 

Regards,
Varban

On Thursday 09 March 2006 13:43, Res Pons wrote:
> I need your feedback please.
>
> Is it a good or bad idea to fool AH-os to check out my master build project
> and from there starts calling other projects ( already checked out) to
> build and at the beging of this master build file make a system exec call
> to update these working folder before doing the build.  This will shave off
> so much time off my build times.  Especailly since AH would like to clean
> entire working folder and do a fresh complete check out of the repo.  Right
> now my buidls start @12:30 am and end around 5am with so many projects
> being built and growing...
>
> I know Anthill pretty much doesn't like it when within your ant file you
> make it do repository check outs/ins across projects and AH would prefer
> that you set separate property sheets or AH-projects for each development
> proj.
>
(Continue reading)

Res Pons | 10 Mar 00:09
Picon

Re: Preventing Anthill OS to check out

By system driver do you mean to make a system exec call using svn.exe? Thank 
you.

----Original Message Follows----
From: Varban <vvv@...>
Reply-To: vvv@..., Anthill user list <anthill@...>
To: Anthill user list <anthill@...>
Subject: Re: [Anthill] Preventing Anthill OS to check out
Date: Thu, 9 Mar 2006 14:44:57 -0500
MIME-Version: 1.0
Received: from lists.urbancode.com ([64.34.169.154]) by 
bay0-mc8-f19.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 9 
Mar 2006 11:52:27 -0800
Received: (qmail 3100 invoked by uid 510); 9 Mar 2006 19:46:16 -0000
Received: from anthill-bounces@... by
caladin.urbancode.com 
by uid 504 with qmail-scanner-1.20  (spamassassin: 2.61.  
Clear:RC:1(127.0.0.1):.  Processed in 0.036871 secs); 09 Mar 2006 19:46:16 
-0000
Received: from localhost (HELO caladin.urbancode.com) (127.0.0.1)  by 
lists.urbancode.com with SMTP; 9 Mar 2006 19:46:16 -0000
Received: (qmail 3066 invoked by uid 510); 9 Mar 2006 19:46:12 -0000
Received: from vvv@... by caladin.urbancode.com by uid 504 
withqmail-scanner-1.20 (spamassassin: 2.61.  
Clear:RC:0(207.99.47.54):SA:0(0.0/5.0):. Processed in 1.237877 secs); 09 Mar 
2006 19:46:12 -0000
Received: from host54a.simplicato.com (207.99.47.54)by lists.urbancode.com 
with SMTP; 9 Mar 2006 19:46:11 -0000
Received: from localhost (localhost.simplicato.com [127.0.0.1])by 
host54a.simplicato.com (Postfix) with ESMTP id 07FDF6C07BAfor 
(Continue reading)

Res Pons | 10 Mar 00:12
Picon

Reserved Words

Hello

I have another question. Does Anthill have a list of reserved words that 
should be use carefully?  I recently discovered that Anthill OS does not 
like the word "version" by itself as a property name.  Ant wasn't 
complaining and it's not a reserved word in Ant.  As soon I renamed that 
property from version to something else, Anthill started to work.

Thanks,

_________________________________________________________________
Don’t just search. Find. Check out the new MSN Search! 
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
Eric Minick | 10 Mar 00:40

Re: Reserved Words

I'm curious what the error was when you passed in 'version'? I can 
imagine that there might be a problem there since Anthill will want to 
set version itself as per the versioning strategy you've selected. It 
looks like it passes two other properties the same way. The first is 
'kit' which is also the version. Frankly, I'm not sure what the history 
is behind that. Anthill also passes 'deployDir' which is the location 
where build artifacts can be published. Other ant parameters reserved by 
Anthill are the -buildfile and -logfile params.

Res Pons wrote:

> Hello
>
> I have another question. Does Anthill have a list of reserved words 
> that should be use carefully? I recently discovered that Anthill OS 
> does not like the word "version" by itself as a property name. Ant 
> wasn't complaining and it's not a reserved word in Ant. As soon I 
> renamed that property from version to something else, Anthill started 
> to work.
>
> Thanks,
>
> _________________________________________________________________
> Don’t just search. Find. Check out the new MSN Search! 
> http://search.msn.click-url.com/go/onm00200636ave/direct/01/
>
> _______________________________________________
> Anthill mailing list
> Anthill@...
> http://lists.urbancode.com/mailman/listinfo/anthill
(Continue reading)

Res Pons | 10 Mar 00:59
Picon

Re: Reserved Words

Thanks for the list.  It's good to know.  I was basically trying to pass the 
version number declared as property to a jar file, like so:

<property name="version" value="5.0" />
and in a copy task I was copying & renaming the file to tools.${version}.jar 
and Anthill didn't like it.  I forget the specific message.  But as soon as 
I changed version to ${product.version}.

<property name="product.version" value="5.0" /> everything was fine.

----Original Message Follows----
From: Eric Minick <etm@...>
Reply-To: Anthill user list <anthill@...>
To: Anthill user list <anthill@...>
Subject: Re: [Anthill] Reserved Words
Date: Thu, 09 Mar 2006 16:40:35 -0700
MIME-Version: 1.0
Received: from lists.urbancode.com ([64.34.169.154]) by 
bay0-mc1-f18.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 9 
Mar 2006 15:40:49 -0800
Received: (qmail 15499 invoked by uid 510); 9 Mar 2006 23:42:00 -0000
Received: from anthill-bounces@... by
caladin.urbancode.com 
by uid 504 with qmail-scanner-1.20  (spamassassin: 2.61.  
Clear:RC:1(127.0.0.1):.  Processed in 0.018568 secs); 09 Mar 2006 23:42:00 
-0000
Received: from localhost (HELO caladin.urbancode.com) (127.0.0.1)  by 
lists.urbancode.com with SMTP; 9 Mar 2006 23:42:00 -0000
Received: (qmail 15469 invoked by uid 510); 9 Mar 2006 23:41:56 -0000
Received: from etm@... by caladin.urbancode.com by uid 504 
(Continue reading)


Gmane