Hi, an update on this thread. After a long mail chain on maven dev list, the solution for the problem we have at the moment is that we need to keep the eclipse plugins in local repository. http://www.mail-archive.com/[email protected]/msg62938.html
I will say there are two options to run it on different platforms 1- having eclipse RCP delta pack in our repository and then using it for packaging the RCP for all platforms. RCP delta pack contains all required plugins,platform dependent eclipse launcher etc. 2- building the RCP as it is being built right now and getting appropriate platform specific runtime binary from eclipse website, unzipping those in a directory and running. I prefer option 2, because we don't have to put the RCP delta pack in our repository and we don't have to worry about updating it manually for newer versions. If we want to provide users everything at one place then may be we can provide those runtime binaries along with our binaries in distribution directory. Regards, Bhupendra On 12/18/06, Bhupendra Bhardwaj <[EMAIL PROTECTED]> wrote:
On 12/15/06, Daniel Kulp <[EMAIL PROTECTED]> wrote: > > > Bhupendra, > > There are two parts to this... > > 1) Building and running tests in management/eclipse-plugin: > (BTW: is the "plugins" dir in there needed? It looks like everything > is > being downloaded OK. Maybe use the dependency plugin to build the > plugins > dir if needed? Having all those jars there sucks from a "size of the > source > distribution" standpoint) Those jars are now deleted. Earlier in this mail chain I mentioned that those jars will be removed. Is this needed? It seems to build fine on Linux with the win32 bundle? > I > guess tests might not run? I'm not sure. > > In anycase, if you needed to, you would definitely use profiles for > this. > You can add a dependency in the profile for a platform. Thus, you can > create a "windows" profile that adds the windows version, a Linux one, > etc... > > In all cases, the artifacts would need to be put in the maven > repositories. > You may need to follow the instructions at: > http://maven.apache.org/guides/mini/guide-central-repository-upload.html > > to create some packages and create a JIRA item and work with the maven > folks > to get the other packages available. I had posted mail to maven dev list (see link below) and they are currently working on providing a feature in maven to download jars from eclipse repo. http://www.mail-archive.com/[email protected]/msg62815.html Regards, Bhupendra Dan > > > On Friday 15 December 2006 07:00, Bhupendra Bhardwaj wrote: > > Hi, > > > > The SWT DSOs are available in platform specific jars. You are right. > > So RCP delta pack is what we need to package RCP to run as standalone > > application for different platforms. But I don't know how it can be > > downloaded and packaged for each platform using maven. > > > > Regards, > > Bhupendra > > > > On 12/14/06, Andrew Overholt <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > * Bhupendra Bhardwaj < [EMAIL PROTECTED]> [2006-12-14 18:41]: > > > > 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. > > > > > > The SWT DSOs are *in* the SWT fragment (platform-specific part of > the > > > plugin ... the org.eclipse.swt.gtk.linux.x86_<blah>.jar) and will be > > > extracted at run-time. If you're going to package this up as an RPM > for > > > your Fedora/RHEL users, you'll want to depend upon eclipse-rcp > instead > > > of bundling the runtime. Look at the RSSOwl or Azureus specfiles in > > > Fedora Extras CVS [1] for examples. Those aren't strict RCP apps, > but > > > they're close and will give you something to work from. > > > > > > Andrew > > > > > > [1] > > > http://cvs.fedora.redhat.com > > -- > J. Daniel Kulp > Principal Engineer > IONA > P: 781-902-8727 C: 508-380-7194 > [EMAIL PROTECTED] >
