Hi,
On 12/14/06, Andrew Overholt <[EMAIL PROTECTED]> wrote:
Hi, On Thu, 2006-12-14 at 18:32 +0000, Bhupendra Bhardwaj wrote: > The eclipse plugins in maven repository are available for win32 only. This seems like the root of your current problem. If you are using maven to build and it pulls its deps from some repo somewhere, then your dependencies need to be in that repo, right? However, later on you say:
Yes, the dependencies need to be in the repo somewhere(local or remote) for compiling.
The downloading of required runtime binary from eclipse is required > because the platform specific eclipse plugins are not available in > maven repository, so we can't pachage everything together for all > platforms using maven. So what if they *were* in the maven repo? Would it be able to do per-arch/os/ws builds? SWT -- and by extension RCP -- is platform-dependent. How does maven handle this situation?
As much as I know about maven, depending on that what I can say is that Maven has a feature of using profiles, which are or can be activated based on env(os/arch etc). So if there are those dependencies available then using the profile those can be downloaded and then packaged or assembled for distribution. Other than the jar files(compilation dependencies), the platform specific files for runtime (dll, so etc) will be required. Those runtime bundles should also be available to download, if we want to package everything together. Regards, Bhupendra
