I apologize for not R'ing the F'ing Site, but I really don't have time to delve too deeply into maven2 since I'm in midstream of making my current maven1 projects work the way my manager wants them to.
A couple of members of my dev team have asked me a quesiton that I can't easily answer. In maven2, is it possible to specify a compile-time dependecy on a source distribution for integration into a source debugger? If that wasn't a good question, let me place it in terms of how we work now: 1. Our main (web) project depends on a jar built internally. We primarly use a SNAPSHOT of that jar since it's very volatile. 2. We use the mavenide and Eclipse, so we have the ability to attach sources to our synchronized dependent jars for source debugging. 3. The dependent jar developer does a source distro when he does a snapshot deploy. 4. During debug, the developer is forced to download (manually) a snapshot source so that he's source debugging the same code that he's running. 5. IF the source was listed as a dependecy, then it could automagically appear in the repository, we could point a path variable to it, and the mavenide code could be updated to preserve that link for snapshots on a pom synchronize. Will this be a possibility/reality with maven2 or am I asking too much? It doesn't seem like an edge case at all, since this question has been asked by essentially every developer and technical manager at every job I've worked where I've promoted maven. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
