Hi Jim,
Actually, I was working on the dependency problem last yesterday /
last night. I went with the solution that has been working for us
very well in the Java space. And that's using a maven style remote
repository to store deployed artifacts.
I've updated the nant builds so that they auto
Just remembered.. I need to check to see if I can update the VS
project files to refer to dependencies from the local repo...
Otherwise I think I'm gonna have to copy them into the $project/lib
folder as part of the build process.
On 11/1/07, Hiram Chirino [EMAIL PROTECTED] wrote:
Hi Jim,
Yay.. your able to use environment variables in the VS project files.
I've now updated them to also refer to the nant repo to look for
dependencies.
On 11/1/07, Hiram Chirino [EMAIL PROTECTED] wrote:
Just remembered.. I need to check to see if I can update the VS
project files to refer to
And yes nant was a sort of requirement before.. It's the only build
system that works across frameworks and we do want to support mono
too. It also will detect and compile against all available frameworks
on your machine. So we will use it at least when we are doing release
builds.
On 11/1/07,
Ok.. I got it setup for the NMS.ActiveMQ module. Easy enough.
Please let me know if that's what you were requesting.. I'll
replicated that to the other modules if it's what you were looking
for.
On 11/1/07, Hiram Chirino [EMAIL PROTECTED] wrote:
Ok.. I'll try out setting up the extenal vendor
Yes, that is what I was going for. I originally had not placed the
Apache.NMS in a vendor sub-directory, but I'm OK with that. I really like
the external repository reference when doing a checkout.
The other projects are easy to change as well, except for MSMQ. It still
had a dependency on the
Sorry, I meant the patch I posted to [AMQNET-72]. Reference the
Apache.NMS.MSMQ-VendorSolution.patch file.
On 11/1/07, Jim Gomes [EMAIL PROTECTED] wrote:
Yes, that is what I was going for. I originally had not placed the
Apache.NMS in a vendor sub-directory, but I'm OK with that. I really
Hi Hiram,
It looks like we are missing the vs2005-stomp-tests.csproj in the new
organization. This should be included as part of the
Apache.NMS.ActiveMQproject and added to the
vs2005-activemq.sln file.
Thanks,
Jim
On 11/1/07, Hiram Chirino [EMAIL PROTECTED] wrote:
Ok.. I got it setup for
[Subject was: NMS Tibco Code Drop is In!]
I have downloaded the latest code (Revision 590826) and have begun playing
with it. There are some definite advantages and disadvantages to this new
structure. The new structure breaks out the provider implementations into
independent projects. The
