self contained repositories

[Krzysztof Koźmic (2)]

Does anyone have any more remarks for project structure standards?
http://wiki.kozmic.pl/Dynamic%20Proxy%20Documentation.Castle-project-structure-standards.ashx?NoRedirect=1&NS=Dynamic%20Proxy%20Documentation

As we've discussed, NAnt and NUnit should be packaged with each
project to ensure build can succeed on any computer with just .NET
installed.

John, will you be interested in doing this change, or should I start?

[John Simons]

Krzysztof,

As I have mentioned before can we name the tools folder "tools", this would make the job of updating TC build configuration easier because we already call it "tools" on the checkout rules.

Also, can you as part of making these changes move /trunk/SharedLibs/build to /tools

I don't really see a benefit from referencing assemblies from both tools and lib, and if we do this it would require changes to the build script(where to copy reference assemblies from...), so I reckon we leave lib as it is and we only reference from the lib, thoughts?

I noticed you moved the solution file to the root, is that so it is at the same level as default.build?
I would instead have moved the default.build into src. Otherwise it becomes a non standard way from when you create a new project in VS.

Cheers
John

---

From: Krzysztof Koźmic (2) <krzy...@kozmic.pl>
To: Castle Project Development List <castle-pro...@googlegroups.com>
Sent: Mon, 14 December, 2009 7:24:15 PM
Subject: self contained repositories

--

You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-pro...@googlegroups.com.
To unsubscribe from this group, send email to castle-project-devel+unsub...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.

---

See what's on at the movies in your area. Find out now.

[G. Richard Bellamy]

Okay... now that I've released Validator and Binder, I'll make sure my stuff
is compliant.

-rb

-----Original Message-----
From: castle-pro...@googlegroups.com
[mailto:castle-pro...@googlegroups.com] On Behalf Of Krzysztof Kozmic
(2)
Sent: Monday, December 14, 2009 12:24 AM
To: Castle Project Development List

--

You received this message because you are subscribed to the Google Groups
"Castle Project Development List" group.
To post to this group, send email to castle-pro...@googlegroups.com.
To unsubscribe from this group, send email to

castle-project-d...@googlegroups.com.

[Jonathon Rossi]

Inline

2009/12/14 John Simons <johnsi...@yahoo.com.au>

Krzysztof,

As I have mentioned before can we name the tools folder "tools", this would make the job of updating TC build configuration easier because we already call it "tools" on the checkout rules.

I agree with naming it tools, this would also mean you wouldn't have to change the build scripts as you mentioned.

Also, can you as part of making these changes move /trunk/SharedLibs/build to /tools

I don't really see a benefit from referencing assemblies from both tools and lib, and if we do this it would require changes to the build script(where to copy reference assemblies from...), so I reckon we leave lib as it is and we only reference from the lib, thoughts?

I am pretty sure this is the way we ran the old trunk, we have nunit.framework.dll in both tools and lib because there were different ones for different platforms, but only one runner.

I noticed you moved the solution file to the root, is that so it is at the same level as default.build?
I would instead have moved the default.build into src. Otherwise it becomes a non standard way from when you create a new project in VS.

I also agree that the solution files (main and silverlight) should be inside src (as they are now) because they are only used for the source code, whereas default.build grabs things from tools, lib, src and maybe doc to build the packages.

Cheers
John

---

From: Krzysztof Koźmic (2) <krzy...@kozmic.pl>
To: Castle Project Development List <castle-pro...@googlegroups.com>
Sent: Mon, 14 December, 2009 7:24:15 PM
Subject: self contained repositories

Does anyone have any more remarks for project structure standards?
http://wiki.kozmic.pl/Dynamic%20Proxy%20Documentation.Castle-project-structure-standards.ashx?NoRedirect=1&NS=Dynamic%20Proxy%20Documentation

As we've discussed, NAnt and NUnit should be packaged with each
project to ensure build can succeed on any computer with just .NET
installed.

John, will you be interested in doing this change, or should I start?

--

You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-pro...@googlegroups.com.
To unsubscribe from this group, send email to castle-project-devel+unsub...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.

---

See what's on at the movies in your area. Find out now.

--

You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-pro...@googlegroups.com.

To unsubscribe from this group, send email to castle-project-d...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.

--
Jono