> So in our case we are trying to manage the Websphere runtime classpath > as a single set of dependencies. The case for doing this is pretty > strong and we've been using it to aggregate the container library into a > single dependency in our projects for while. I was hoping the import > scope would make this a first class pattern and relieve my future > proofing concern with it.
Tim, I totally get where you're coming from, and I understand why you might be a little bit confused about the import scope. I agree that your use case makes a lot of sense and would help management of artifact bundles across projects -- perhaps it can be incorporated into this "import" scope at some time in the future. Unless of course the current way works with no issues -- as you said, you are already doing it. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
