On 13/02/2008, Marshall Schor <[EMAIL PROTECTED]> wrote: > > Just an interesting note: > > pax:eclipse needs the scope to be "provided|test" in order to add the > dependency to the classpath. > > eclipse:eclipse needs the scope to be "compile" in order to add the > dependency to the classpath.
yes, because in Pax-Construct we use "compile" dependencies when embedding classes, and these embedded jars/directories are added separately to the classpath, so there's no need to add the original dependency that supplied the classes. but we could add them in case people use "compile" dependencies for OSGi bundles that won't be embedded (although that's not our recommended practice) fyi, eclipse:eclipse won't add "compile" dependencies that are OSGi bundles (it assumes PDE will infer they are Plug-in Dependencies) and it assumes any "provided" dependencies will be OSGi bundles and therefore also won't require a classpath entry. HTH -Marshall > btw, pax:eclipse will revert to eclipse:eclipse behaviour when used with a project that doesn't have "bundle" packaging - the special handling is only used for OSGi projects. -- Cheers, Stuart
