Byldan

Source code checked in

sisbell — Tue, 11 Dec 2007 08:49:58 GMT

Wsdl generation support.

Source code checked in

sisbell — Mon, 10 Dec 2007 04:47:11 GMT

Added Init method to build tasks as a way to pass in parameters. This is part of the config and should not be included within the execute method.

Source code checked in

sisbell — Mon, 10 Dec 2007 00:31:46 GMT

Fixed compile time build error.

Source code checked in

sisbell — Sun, 09 Dec 2007 21:09:15 GMT

Added provisioning packages.

Source code checked in

sisbell — Wed, 26 Sep 2007 07:06:25 GMT

Partial implementation of pre and post aggregate build tasks. Supports failing of build if cyclical dependency is found. Automatically orders the projects correctly for a build. Improved logging.

Source code checked in

sisbell — Sun, 23 Sep 2007 16:52:53 GMT

Missing class file causes VS project build to fail. Deleted this file from IDE project.

Source code checked in

sisbell — Sun, 23 Sep 2007 16:16:00 GMT

Restructured the repository to allow multiple projects within Byldan. Moving the Byldan.Build into its own project space and adding Byldan.Provisioning for server services related to build artifacts.

UPDATED WIKI: Home

sisbell — Sun, 23 Sep 2007 03:59:18 GMT

Project Description
Byldan is a framework for managing the build life-cycle of .NET applications. Its goal is to support multiple-platforms (Linux/Windows) and multiple compiler vendors (Novell/Microsoft).

Documentation

UPDATED WIKI: Documentation

sisbell — Sat, 22 Sep 2007 05:36:22 GMT

Documentation

Installing

Go to the releases section and download the latest binary version
Unzip into a directory
Place the directory location containing the bd.bat file within your path

Setting up and Building a Simple Project

To setup a single-module project:

Create the project directory
Go to the root of the project directory, at create a new file called project.xml. It should looks something like:

<Project>
  <GroupId>Byldan</GroupId>
  <ArtifactId>Byldan.Test</ArtifactId>
  <Version>1.1.0.3</Version>
  <Type>library</Type>
</Project>

In the Type tag, you can use the following value: library, winexe, exe, netmodule, project

Add your classes
Type bd install
Look under the target directory for the assembly file: it will be named <ArtifactId>.<Extension_Type>

To clean the directories, type "bd clean".

Using Dependencies

To use dependencies:

Create a new project and setup your project.xml similar to the following:

<Project>
  <GroupId>Byldan</GroupId>
  <ArtifactId>Byldan.Test.Dependency</ArtifactId>
  <Version>1.1.0.3</Version>
  <Type>exe</Type>
  <Dependencies>
    <Dependency>
      <GroupId>Byldan</GroupId>
      <ArtifactId>Byldan.Test</ArtifactId>
      <Version>1.1.0.3</Version>
      <Type>library</Type>
    </Dependency>
  </Dependencies>
</Project>

If the dependency has already been installed into the GAC, then the 'Type' field should specify 'gac' instead of 'library'.

Create your class files that use classes from the Byldan.Test assembly.
Type bd install
Look under the target directory for the assembly file: it will be named <ArtifactId>.<Extension_Type>

Multi-module Builds

To setup multi-module builds, go to the parent directory of your projects, and create another project.xml file:

<Project>
  <GroupId>Byldan</GroupId>
  <ArtifactId>Byldan.Test.Multimodule</ArtifactId>
  <Version>1.1.0.3</Version>
  <Type>project</Type>
  <Modules>
     <Module>simple-build</Module>
     <Module>simple-dependency</Module>
  </Modules>
</Project>

The module names should match the directories of your project. It is important that you put these in order of their dependencies. For example, simple-dependency depends on simple-build, so it should be included last.

Type bd install (This still needs to be added to distribution)
Look under the target directory of each project for the assembly file: it will be named <ArtifactId>.<Extension_Type>

Creating Custom Build Tasks

To create a custom build task, requires implementing the Byldan.Build.Framework.IBuildTask interface. Next add a Byldan.Build.Framework.GoalAttribute to the Execute method, specifying the goal attribute name as a parameter (in this case 'xsd').

    public class XsdClassGeneratorBuildTask : IBuildTask
    {
        
        [GoalAttribute(Name = "xsd")]
        public void Execute(Project project, ProjectInfo projectInfo)
        {
            Console.WriteLine("Executed the XSD Generator");
        }
    }

The project.xml file for building the custom build task would look similar to:

<Project>
  <GroupId>Byldan.Build.BuildTasks</GroupId>
  <ArtifactId>Byldan.Build.BuildTask.Xsd</ArtifactId>
  <Version>0.4</Version>
  <Type>library</Type>
  <Dependencies>
    <Dependency>
      <GroupId>Byldan.Build</GroupId>
      <ArtifactId>Byldan.Build.Framework</ArtifactId>
      <Version>0.4</Version>
      <Type>exe</Type>
    </Dependency>
    <Dependency>
      <GroupId>Byldan.Build</GroupId>
      <ArtifactId>Byldan.Build.Model</ArtifactId>
      <Version>0.4</Version>
      <Type>library</Type>
    </Dependency>
  </Dependencies>
</Project>

Using Custom Build Tasks

To use the custom attribute defined above, add a build task to your project.xml file. The group id and artifact id must match those defined within the project.xml file of the project assembly containing the build task implementation.

<Project>
  <GroupId>Byldan.Build</GroupId>
  <ArtifactId>Byldan.Build.Test</ArtifactId>
  <Version>0.4</Version>
  <Type>library</Type>
  <BuildTasks>
    <BuildTask>
      <GroupId>Byldan.Build.BuildTasks</GroupId>
      <ArtifactId>Byldan.Build.BuildTask.Xsd</ArtifactId>
      <Version>0.4</Version>
      <Goals>
        <Goal>
          <Name>xsd</Name>
          <Phase>compile</Phase>
        </Goal>
      </Goals>
    </BuildTask>
  </BuildTasks>
</Project>

You can also execute the plugin directly without specifying it within the project.xml file.

 bd <group_id>:<artifact_id>:<version>:<goal>

For example:

 bd Byldan:Byldan.BuildTasks:0.2:xsd

Running FxCop

You will need to have FxCopCmd located within your path. From the directory containing the project.xml file, type:

  bd fxcop:fxcop

The target of the project will contain the FxCop output file.

Using NUnit

You will need nunit-console located within your path. Within your project directory, create a directory called 'Tests'. Place your NUnit tests in this directory. From the directory containing the project.xml file, type:

  bd install

Byldan will automatically compile and run the unit tests.

Signing Assemblies

Just place your snk file within the ~\.byldan directory (this directory also contains your build artifacts). Byldan will automatically pick it up and sign your project assemblies.

UPDATED WIKI: Documentation

sisbell — Sat, 22 Sep 2007 05:32:46 GMT

Documentation

Installing

Go to the releases section and download the latest binary version
Unzip into a directory
Place the directory location containing the bd.bat file within your path

Setting up and Building a Simple Project

To setup a single-module project:

Create the project directory
Go to the root of the project directory, at create a new file called project.xml. It should looks something like:

<Project>
  <GroupId>Byldan</GroupId>
  <ArtifactId>Byldan.Test</ArtifactId>
  <Version>1.1.0.3</Version>
  <Type>library</Type>
</Project>

In the Type tag, you can use the following value: library, winexe, exe, netmodule, project

Add your classes
Type bd install
Look under the target directory for the assembly file: it will be named <ArtifactId>.<Extension_Type>

To clean the directories, type "bd clean".

Using Dependencies

To use dependencies:

Create a new project and setup your project.xml similar to the following:

<Project>
  <GroupId>Byldan</GroupId>
  <ArtifactId>Byldan.Test.Dependency</ArtifactId>
  <Version>1.1.0.3</Version>
  <Type>exe</Type>
  <Dependencies>
    <Dependency>
      <GroupId>Byldan</GroupId>
      <ArtifactId>Byldan.Test</ArtifactId>
      <Version>1.1.0.3</Version>
      <Type>library</Type>
    </Dependency>
  </Dependencies>
</Project>

If the dependency has already been installed into the GAC, then the 'Type' field should specify 'gac' instead of 'library'.

Create your class files that use classes from the Byldan.Test assembly.
Type bd install
Look under the target directory for the assembly file: it will be named <ArtifactId>.<Extension_Type>

Multi-module Builds

To setup multi-module builds, go to the parent directory of your projects, and create another project.xml file:

<Project>
  <GroupId>Byldan</GroupId>
  <ArtifactId>Byldan.Test.Multimodule</ArtifactId>
  <Version>1.1.0.3</Version>
  <Type>project</Type>
  <Modules>
     <Module>simple-build</Module>
     <Module>simple-dependency</Module>
  </Modules>
</Project>

Type bd install (This still needs to be added to distribution)
Look under the target directory of each project for the assembly file: it will be named <ArtifactId>.<Extension_Type>

Creating Custom Build Tasks

    public class XsdClassGeneratorBuildTask : IBuildTask
    {
        
        [GoalAttribute(Name = "xsd")]
        public void Execute(Project project, ProjectInfo projectInfo)
        {
            Console.WriteLine("Executed the XSD Generator");
        }
    }

The project.xml file for building the custom build task would look similar to:

<Project>
  <GroupId>Byldan.Build.BuildTasks</GroupId>
  <ArtifactId>Byldan.Build.BuildTask.Xsd</ArtifactId>
  <Version>0.4</Version>
  <Type>library</Type>
  <Dependencies>
    <Dependency>
      <GroupId>Byldan.Build</GroupId>
      <ArtifactId>Byldan.Build.Framework</ArtifactId>
      <Version>0.4</Version>
      <Type>exe</Type>
    </Dependency>
    <Dependency>
      <GroupId>Byldan.Build</GroupId>
      <ArtifactId>Byldan.Build.Model</ArtifactId>
      <Version>0.4</Version>
      <Type>library</Type>
    </Dependency>
  </Dependencies>
</Project>

Using Custom Build Tasks

<Project>
  <GroupId>Byldan.Build</GroupId>
  <ArtifactId>Byldan.Build.Test</ArtifactId>
  <Version>0.4</Version>
  <Type>library</Type>
  <BuildTasks>
    <BuildTask>
      <GroupId>Byldan.Build.BuildTasks</GroupId>
      <ArtifactId>Byldan.Build.BuildTask.Xsd</ArtifactId>
      <Version>0.4</Version>
      <Goals>
        <Goal>
          <Name>xsd</Name>
          <Phase>compile</Phase>
        </Goal>
      </Goals>
    </BuildTask>
  </BuildTasks>
</Project>

You can also execute the plugin directly without specifying it within the project.xml file.

 bd <group_id>:<artifact_id>:<version>:<goal>

For example:

 bd Byldan:Byldan.BuildTasks:0.2:xsd

Running FxCop

You will need to have FxCopCmd located within your path. From the directory containing the project.xml file, type:

  bd fxcop:fxcop

The target of the project will contain the FxCop output file.

Using NUnit

  bd install

Byldan will automatically compile and run the unit tests.

UPDATED WIKI: Documentation

sisbell — Sat, 22 Sep 2007 05:28:57 GMT

Documentation

Installing

Go to the releases section and download the latest binary version
Unzip into a directory
Place the directory location containing the bd.bat file within your path

Setting up and Building a Simple Project

To setup a single-module project:

Create the project directory
Go to the root of the project directory, at create a new file called project.xml. It should looks something like:

<Project>
  <GroupId>Byldan</GroupId>
  <ArtifactId>Byldan.Test</ArtifactId>
  <Version>1.1.0.3</Version>
  <Type>library</Type>
</Project>

In the Type tag, you can use the following value: library, winexe, exe, netmodule, project

Add your classes
Type bd install
Look under the target directory for the assembly file: it will be named <ArtifactId>.<Extension_Type>

Using Dependencies

To use dependencies:

Create a new project and setup your project.xml similar to the following:

<Project>
  <GroupId>Byldan</GroupId>
  <ArtifactId>Byldan.Test.Dependency</ArtifactId>
  <Version>1.1.0.3</Version>
  <Type>exe</Type>
  <Dependencies>
    <Dependency>
      <GroupId>Byldan</GroupId>
      <ArtifactId>Byldan.Test</ArtifactId>
      <Version>1.1.0.3</Version>
      <Type>library</Type>
    </Dependency>
  </Dependencies>
</Project>

If the dependency has already been installed into the GAC, then the 'Type' field should specify 'gac' instead of 'library'.

Create your class files that use classes from the Byldan.Test assembly.
Type bd install
Look under the target directory for the assembly file: it will be named <ArtifactId>.<Extension_Type>

Multi-module Builds

To setup multi-module builds, go to the parent directory of your projects, and create another project.xml file:

<Project>
  <GroupId>Byldan</GroupId>
  <ArtifactId>Byldan.Test.Multimodule</ArtifactId>
  <Version>1.1.0.3</Version>
  <Type>project</Type>
  <Modules>
     <Module>simple-build</Module>
     <Module>simple-dependency</Module>
  </Modules>
</Project>

Type bd install (This still needs to be added to distribution)
Look under the target directory of each project for the assembly file: it will be named <ArtifactId>.<Extension_Type>

Creating Custom Build Tasks

    public class XsdClassGeneratorBuildTask : IBuildTask
    {
        
        [GoalAttribute(Name = "xsd")]
        public void Execute(Project project, ProjectInfo projectInfo)
        {
            Console.WriteLine("Executed the XSD Generator");
        }
    }

The project.xml file for building the custom build task would look similar to:

<Project>
  <GroupId>Byldan.Build.BuildTasks</GroupId>
  <ArtifactId>Byldan.Build.BuildTask.Xsd</ArtifactId>
  <Version>0.4</Version>
  <Type>library</Type>
  <Dependencies>
    <Dependency>
      <GroupId>Byldan.Build</GroupId>
      <ArtifactId>Byldan.Build.Framework</ArtifactId>
      <Version>0.4</Version>
      <Type>exe</Type>
    </Dependency>
    <Dependency>
      <GroupId>Byldan.Build</GroupId>
      <ArtifactId>Byldan.Build.Model</ArtifactId>
      <Version>0.4</Version>
      <Type>library</Type>
    </Dependency>
  </Dependencies>
</Project>

Using Custom Build Tasks

<Project>
  <GroupId>Byldan</GroupId>
  <ArtifactId>Byldan.Test.BuildTask</ArtifactId>
  <Version>0.2</Version>
  <Type>library</Type>
  <BuildTasks>
    <BuildTask>
      <GroupId>Byldan</GroupId>
      <ArtifactId>Byldan.BuildTasks</ArtifactId>
      <Version>0.2</Version>
      <Goals>
        <Goal>
          <Name>xsd</Name>
          <Phase>compile</Phase>
        </Goal>
      </Goals>
    </BuildTask>
  </BuildTasks>
</Project>

You can also execute the plugin directly without specifying it within the project.xml file.

 bd <group_id>:<artifact_id>:<version>:<goal>

For example:

 bd Byldan:Byldan.BuildTasks:0.2:xsd

Running FxCop

You will need to have FxCopCmd located within your path. From the directory containing the project.xml file, type:

  bd fxcop:fxcop

The target of the project will contain the FxCop output file.

Using NUnit

  bd install

Byldan will automatically compile and run the unit tests.

UPDATED WIKI: Documentation

sisbell — Sat, 22 Sep 2007 05:22:59 GMT

Documentation

Installing

Go to the releases section and download the latest binary version
Unzip into a directory
Place the directory location containing the bd.bat file within your path

Setting up and Building a Simple Project

To setup a single-module project:

Create the project directory
Go to the root of the project directory, at create a new file called project.xml. It should looks something like:

<Project>
  <GroupId>Byldan</GroupId>
  <ArtifactId>Byldan.Test</ArtifactId>
  <Version>1.1.0.3</Version>
  <Type>library</Type>
</Project>

In the Type tag, you can use the following value: library, winexe, exe, netmodule, project

Add your classes
Type bd install
Look under the target directory for the assembly file: it will be named <ArtifactId>.<Extension_Type>

Using Dependencies

To use dependencies:

Create a new project and setup your project.xml similar to the following:

<Project>
  <GroupId>Byldan</GroupId>
  <ArtifactId>Byldan.Test.Dependency</ArtifactId>
  <Version>1.1.0.3</Version>
  <Type>exe</Type>
  <Dependencies>
    <Dependency>
      <GroupId>Byldan</GroupId>
      <ArtifactId>Byldan.Test</ArtifactId>
      <Version>1.1.0.3</Version>
      <Type>library</Type>
    </Dependency>
  </Dependencies>
</Project>

If the dependency has already been installed into the GAC, then the 'Type' field should specify 'gac' instead of 'library'.

Create your class files that use classes from the Byldan.Test assembly.
Type bd install
Look under the target directory for the assembly file: it will be named <ArtifactId>.<Extension_Type>

Multi-module Builds

To setup multi-module builds, go to the parent directory of your projects, and create another project.xml file:

<Project>
  <GroupId>Byldan</GroupId>
  <ArtifactId>Byldan.Test.Multimodule</ArtifactId>
  <Version>1.1.0.3</Version>
  <Type>project</Type>
  <Modules>
     <Module>simple-build</Module>
     <Module>simple-dependency</Module>
  </Modules>
</Project>

Type bd install (This still needs to be added to distribution)
Look under the target directory of each project for the assembly file: it will be named <ArtifactId>.<Extension_Type>

Creating Custom Build Tasks

    public class XsdClassGeneratorBuildTask : IBuildTask
    {
        
        [GoalAttribute(Name = "xsd")]
        public void Execute(Project project, ProjectInfo projectInfo)
        {
            Console.WriteLine("Executed the XSD Generator");
        }
    }

The project.xml file for building the custom build task would look similar to:

<Project>
  <GroupId>Byldan.Build.BuildTasks</GroupId>
  <ArtifactId>Byldan.Build.BuildTask.Xsd</ArtifactId>
  <Version>0.4</Version>
  <Type>library</Type>
  <Dependencies>
    <Dependency>
      <GroupId>Byldan.Build</GroupId>
      <ArtifactId>Byldan.Build.Framework</ArtifactId>
      <Version>0.4</Version>
      <Type>exe</Type>
    </Dependency>
    <Dependency>
      <GroupId>Byldan.Build</GroupId>
      <ArtifactId>Byldan.Build.Model</ArtifactId>
      <Version>0.4</Version>
      <Type>library</Type>
    </Dependency>
  </Dependencies>
</Project>

Using Custom Build Tasks

<Project>
  <GroupId>Byldan</GroupId>
  <ArtifactId>Byldan.Test.BuildTask</ArtifactId>
  <Version>0.2</Version>
  <Type>library</Type>
  <BuildTasks>
    <BuildTask>
      <GroupId>Byldan</GroupId>
      <ArtifactId>Byldan.BuildTasks</ArtifactId>
      <Version>0.2</Version>
      <Goals>
        <Goal>
          <Name>xsd</Name>
          <Phase>compile</Phase>
        </Goal>
      </Goals>
    </BuildTask>
  </BuildTasks>
</Project>

You can also execute the plugin directly without specifying it within the project.xml file.

 bd <group_id>:<artifact_id>:<version>:<goal>

For example:

 bd Byldan:Byldan.BuildTasks:0.2:xsd

UPDATED RELEASE: Byldan 0.4 (Sep 21, 2007)

Sat, 22 Sep 2007 05:13:52 GMT

Byldan is a framework for managing the build life-cycle of .NET applications. Its goal is to support multiple-platforms (Linux/Windows) and multiple compiler vendors (Novell/Microsoft). This minor release of Byldan adds support for unit testing with NUnit and for signing of assemblies. Go here for [Documentation]

RELEASED: Byldan 0.4 (Sep 21, 2007)

Sat, 22 Sep 2007 05:13:52 GMT

Source code checked in

sisbell — Sat, 22 Sep 2007 04:47:52 GMT

Updated to version 0.4

Source code checked in

sisbell — Sat, 22 Sep 2007 04:29:10 GMT

Cleaned up logging. Fixed bug in multimodule fxcop task.

Source code checked in

sisbell — Thu, 20 Sep 2007 05:30:09 GMT

Add project file for nunit.

Source code checked in

sisbell — Thu, 20 Sep 2007 05:29:28 GMT

Fixed a bug where the build failed when byldan attempted to update it's cache. Improved logging.

Source code checked in

sisbell — Thu, 20 Sep 2007 04:28:17 GMT

Build fails if process return code not 1. Improved API docs.

Source code checked in

sisbell — Wed, 19 Sep 2007 06:43:51 GMT

Improved exception handling and added API docs. Feature: Picks up key for signing.