Thanks for this James. I have some questions...
On 24/09/2008, at 2:19 AM, James Carpenter wrote:
c) Ensure the pdb files are properly processed to include the
necessary source stream during or before the deploy phase. It is
important SNAPSHOT artifacts include this information so one can't
wait for the release plugin to do the job.
--------------
Option 2:
a) Same as Option 1.a
b) Process the pdb files during/before the deploy phase to include
the information necessary to extract a single source file. Under
the covers the command line call formed when VS processed the source
stream from the pdb file will need to resolve the relevant source
archive and extract the relevant file from the source archive. The
best way to do this is likely to work out a one line mvn call which
will return the relevant source file, creating a plugin or two as
necessary. The command line call formed when processing the source
stream in the pdb file will therefore simply be a call into maven.
Does option 2 (b) result in a larger PDB file than 1 (c)? IIUC, you
are basically including the entire source in there, vs a reference to
a source which would be stored elsewhere.
If so, option 1 seems slightly more efficient from the repository's
perspective (as having a source archive could make sense regardless).
But it depends on how much complexity this adds on the client side.
Would the client end of this be easier to achieve if it were managed
from Visual Studio integration itself?
Thanks,
Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
