I am somehow successfull at building our PDE application Elexis. See
http://ngiger.dyndns.org/jenkins/view/buildr/job/elexis-2.2.dev_jpa-Buildr/18/
It was quite easy to use the IzPack installer to use the same artefacts to
generate an installer for various platforms.
But I still have problems to overcome, e.g. I have not yet found an easy way
to import an eclipse target definition as maven artefacts. Therefore I use for
this step still buckminster, where it is a no-brainer.
Currently I am stuck that I have a situation where I have to manually change
the generated dependencies.yml as the order of dependents projects decides
whether files compile or not.
Eg. the project at.medevit.elexis.jpapoadapter compiles fine when I have in
dependencies.yml the lines
> projects:
> - elexis:ch.elexis
> - elexis:at.medevit.elexis.model
> - elexis:ch.elexis.core
but fails with the sorted (default)
> projects:
> - elexis:at.medevit.elexis.model
> - elexis:ch.elexis
> - elexis:ch.elexis.core
Why? Both at.medevit.elexis.model and ch.elexis define Kontakt inside the
package ch.elexis.data. ch.elexis defines it as
public class Kontakt extends PersistentObject
Therefore compiling jpapoadapter fails, as it does not see the methods coming
from PersistentObject.
Do you see any easy solution to it? And as far as I understood buildr4osgi one
cannot easily get an unsorted array of dependencies as its structure depend on
a SortedHash.
Is there a way to override the order of dependencies from inside a project? I
didn't spot any easy method and used a simple script to patch the order inside
the dependencies.yml.
Thanks a lot for you attention.
Best regards
--
Niklaus Giger