vigoo / bari Goto Github PK

View Code? Open in Web Editor NEW

11.0 11.0 6.0 3.09 MB

Bari is an advanced build management tool for .NET projects.

Home Page: http://vigoo.github.io/bari/

License: Apache License 2.0

PowerShell 0.58% XSLT 0.29% C# 98.28% C++ 0.49% C 0.27% Python 0.08% F# 0.01%

bari's People

Contributors

Stargazers

Watchers

Forkers

benkop zvrana p5ych08illy tib888 gavrail supremegenius

bari's Issues

Ability to build and run unit tests

With http://www.gallio.org/

Better names for generated solution files

Add an option to vs command that automatically starts vs

Default namespace property to c# projects

Generated solutions cannot be built from VS

Create git implementation of the version control system

I want a system testing plugin which is capable of running several tests using the fully built product. In bari's case this would be a large set of suites, running bari on them and verifying the generated output/built software.

Problems with project reference without solution item

If a csproj refers to another one using ProjectReference, and the solution file does not have any solution configuration specified for it, then msbuild does not use the solution dependent build output etc.

Possible solutions:

Duplicate the configuration specific block without condition for msbuild (must have conditioned block for VS as well)
Do not use csproj reference in these cases (but then what about caching?)

Reference alias support

A reference alias is a set of references addressed by a single name:

Definition:

aliases:
    ninject:      
      - nuget://Ninject
      - nuget://Ninject.Extensions.Factory
      - nuget://Castle.Core/3.0.0.4001

Then it can be used in reference lists with a simple reference URI:
alias://ninject

Add a scripted builder type

A project builder which can be implemented by the user as simple scripts.
Add access to the external tool acquiring system of bari from the scripts.

Example script in pseudocode:

 localizer = get_tool("localizer-tool")
 for each (file in sourceset("loc"):
     run(localizer, file, targetdir)

Embedded resource support for C# projects

Suite definition containing tabs cannot be read

Initial F# support

Common platform for finding and/or downloading external tools

And use it for NuGet, MSBuild, Gallio, etc.

Ability to compile registration-free C++ COM DLLs

Binary repository resolver

A configurable resolver which copies dependencies from a shared network location based on name and version number.

More detailed requirements:

A top level configuration section to define where the binary repo is, using a pattern
Ability to use environment variables in the pattern
The pattern must refer separately to dependency name, the file name, the version and the file extension
Ability to define separate locations for 32 and 64bit dependencies, but handle cases when there isn't a difference
Ability to define multiple binary repos with different name

The URI syntax would look something like this:

fsrepo://dependency/version/something.dll
fsrepo://binreponame/dependency/version/something.dll

the first syntax is for cases when there is only one repo (probably the common case).

Initial C++ support

Global copyright property

DotNetZip nuget package does not work as reference

Tests referencing to other modules does not work

Better error message in clean command when directories are locked

Give a more user friendly message, make suggestions etc.

Ability to add post processors to projects

Post processors are executed on the output of the project.

Support referencing additional native binaries in C# projects

These dependencies are not referenced by the target assembly but must be copied to the target directory using the same dependency resolver as .NET dependencies.

help command won't work unless valid goal is specified

this does not work:

E:\Workspace>d:\bari\target\full\bari.exe help
bari version 0.8.0.0

Goal 'debug' is invalid. Available goals: debug-x86, debug-x64, release-x86, release-x64

this does:

E:\Workspace>d:\bari\target\full\bari.exe --target debug-x86 help
bari version 0.8.0.0

The following commands can be used for this suite:
    build - builds a project, module or product
    clean - cleans that target dir and the bari cache
    help - displays the available commands and their usage
    info - shows all known information about the current suite
    test - builds and runs the unit tests in the suite
    vs - generates visual studio solution and projects for a module

When printing msbuild errors, the project name should be displayed also

Try to skip non-C++ files in vcxproj source files section

For example

app.ico
X.vcxproj.filters

app.config and manifest support for C# projects

Suite/module references should be able to refer to postprocessor-generated files

Add support to project and module parameters to the build command

Assembly version info injection to C# projects

Nuget plugin does not handle the case when not the latest version is required by another module

Example:
Successfully installed 'Castle.Core 3.1.0'.
Successfully installed 'Ninject 3.0.1.10'.
Attempting to resolve dependency 'Ninject (? 3.0.0.0 && < 3.1.0.0)'.
Attempting to resolve dependency 'Castle.Core (? 3.0.0.4001 && < 3.1.0.0)'.
Successfully installed 'Ninject 3.0.1.10'.
Successfully installed 'Castle.Core 3.0.0.4001'.
Successfully installed 'Ninject.Extensions.Factory 3.0.1.0'.

But only Castle 3.1.0 is really deployed

projects
modules
products

and they should be executed after the given build entity is built, similarly how runtime references are deployed.

Ability to compile mixed mode C++/CLI DLLs

`bari test` doesn't work on bari

Unexpected CopyLocal flag errors.

To reproduce:

bari clean
bari test

Workaround:

bari clean
bari vs full
bari test
runs the tests, but there are other (runtime) problems