Problems analysing MANIFEST

[Niklaus Giger]

Hi

While trying to get buildr working for the Eclipse RCP application
http://elexis.hg.sourceforge.net/hgweb/elexis/elexis-base
I wrote a small script (see attachement) to generate a buildfile (also
attached)

After running buildr osgi:resolve:dependencies I get a dependencies.yml which
looks quite good and which allows me to compile a few java files.

Elexis developers put a few *.jar files into lib subdirectories. These jarfiles
do not show up in the dependencies.yml. Therefore I added them directly into
the buildfile using
compile.dependencies << '#{jar}'
This trick allows me already to compile a few hundred java files.

Is this the correct way to do it or is this an error with buildr4osgi?

Also I think that in lib/buildr4osgi/osgi/packaging.rb "Bundle-Classpath" is
miss-capitalized and that it should be "Bundle-ClassPath".

I am unable to "rake install" for jruby as I cannot install the doc:setup
which requires mkmf. (I am running GNU/Debian/Linux squeeze).

Which platform can I use to develop and test?

There is one MANIFEST.MF (see attachment) which puzzles me most, as in the
dependencies.yml it shows up only as:

> elexisAll:elexis-utilities:
> dependencies: []
> projects:
> - elexisAll:h2-adapter
> - elexisAll:hsql-adapter
> - elexisAll:mysql-adapter
> - elexisAll:postgresql-adapter

Best regards

--
Niklaus Giger

[Antoine Toulme]

Hi Niklaus, please see my answers inline:

On Thu, Jun 24, 2010 at 16:30, Niklaus Giger <niklau...@member.fsf.org> wrote:

Hi

While trying to get buildr working for the Eclipse RCP application
http://elexis.hg.sourceforge.net/hgweb/elexis/elexis-base
I wrote a small script (see attachement) to generate a buildfile (also
attached)

After running buildr  osgi:resolve:dependencies I get a dependencies.yml which
looks quite good and which allows me to compile a few java files.

Elexis developers put a few *.jar files into lib subdirectories. These jarfiles
do not show up in the dependencies.yml. Therefore  I added them directly into
the buildfile using
 compile.dependencies << '#{jar}'

That's almost it.

First off, if you have bundle dependencies that are not OSGi, they will never show up in the dependencies.yml file.

Second, you can and you should always rely on saying:

compile.with dependencies, LOG4J, XMPP, whatever_jar_I_have_that's_not_osgi 

This trick allows me already to compile a few hundred java files.

Is this the correct way to do it or is this an error with buildr4osgi?

Also I think that in lib/buildr4osgi/osgi/packaging.rb "Bundle-Classpath" is
miss-capitalized and that it should be "Bundle-ClassPath".

OK. Please file a bug at jira.intalio.org about that. 

I am unable to "rake install" for jruby as I cannot install the doc:setup
which requires mkmf. (I am running GNU/Debian/Linux squeeze).

You're using the master branch ? Do gem build buildr4osgi.gemspec

Then you can install it on jruby with:

jruby -S gem install buildr4osgi-0.9.4.gem 

rake install is actualling calling the Buildr install script.

 

Which platform can I use to develop and test?

MRI and JRuby are supported. 

There is one MANIFEST.MF (see attachment) which puzzles me most, as in the
dependencies.yml it shows up only as:

> elexisAll:elexis-utilities:
>   dependencies: []
>   projects:
>     - elexisAll:h2-adapter
>     - elexisAll:hsql-adapter
>     - elexisAll:mysql-adapter
>     - elexisAll:postgresql-adapter

What's puzzling there ? It looks ok to me, maybe you can emphasize what you think looks wrong ?