bzr-eclipse team mailing list archive

[Alexander Taler <dissent@xxxxxxxx>]

Thanks for your feedback Piotr, that made everything much
simpler.  I've deleted and recreated the branch and edited the
tutorial.  The basic steps are checkout in Eclipse, build in
Maven, refresh in Eclipse.

I modified the UI project to access bzr-java-lib as a dependency
in the same way as client and core.tests.  Both of those copy the
jar file during the Maven package command.  It's not perfect
because if you change bzr-java-lib the package needs to be copied
over twice.

  lp:~alex-idereal/bzr-eclipse/1.2.0-patches
  https://answers.launchpad.net/bzr-eclipse/+faq/2257

Unfortunately I couldn't get the build path variable you
suggested to work.  The client project complained, possibly
because it's exporting that functionality in the bundle.

I do want to add this to the wiki, but it was very slow last time
I tried to use it.  I also want to add more documentation about
how it's put together, and how to update bzr-java-lib.

What do you think?

Alex

> Hi,

> I checked the tutorial at
> https://answers.launchpad.net/bzr-eclipse/+faq/2257 and here are some
> ideas:
> 1) use "mvn install" instead of copying bzr-java-lib artifacts to
> repository manually
> 2) consider adding a minimalistic script to build the plugin (update
> site) for those who do not need the whole dev environment:
> bzr branch lp:bzr-java-lib
> cd bzr-java-lib
> mvn install
> cd ..
> bzr branch lp:bzr-eclipse
> cd bzr-eclipse
> mvn package
> 3) I think it's better not to copy the jar files to project folders,
> let's use a variable as mentioned before or something else to reduce
> the number of manual steps required to set up the IDE
> 4) there should be no need to modify any files that impact the build
> process (manifest, build.properties etc.), currently the project
> builds fine with maven and I am inclined to assume they're ok, but if
> for some reason they need to be changed, please make sure that 2)
> still works

> BTW, once the tutorial is finished you might consider adding it to
> http://wiki.bazaar.canonical.com/BzrEclipse#Hacking too.

> Thanks
> Piotr

> On Mon, Apr 22, 2013 at 11:23 AM, Piotr Piastucki <piastucki@xxxxxxxxx> wrote:
> > I would suggest introducing a new variable that points to a folder
> > with bzr-java-lib jars as follows:
> > lp:~piastucki/bzr-eclipse/classpath_fixes. This way the projects will
> > be automatically synchronized with any bzr-java-lib changes and there
> > is only 1 variable to configure after checking out the source code.
> >
> > Piotr

-- 
idereal | deliver                       http://idereal.co.nz/
Get your software to market sooner      022 659 0282