Comments on: Getting Started with Bundlor

By: Ben Hale

Ben Hale — Fri, 12 Jun 2009 18:06:50 +0000

@Sam

Actually, we don't follow import links at this time. If you want to open a jira at http://issuetracker.springsource.com/browse/BUNDLR we'll schedule it in.

By: Sam

Sam — Fri, 12 Jun 2009 17:12:20 +0000

If the Spring Context configuration contains imports, does the plugin detect packages/classes defined in the imported context files?

By: SpringSource Team Blog » SpringSource Tool Suite now free

SpringSource Team Blog » SpringSource Tool Suite now free — Thu, 07 May 2009 16:01:44 +0000

[...] Getting Started with Bundlor [...]

By: Ben Hale

Ben Hale — Wed, 29 Apr 2009 06:37:06 +0000

@Pascal

It's been an issue that's been talked about, but at present there is no JIRA issue to do the work. Please open a Bundlor story at http://issuetracker.springsource.com with details of how you'd like this to work and it'll be put on our product backlog.

By: Pascal Nueesch

Pascal Nueesch — Mon, 27 Apr 2009 11:59:32 +0000

Hi Ben

I've tried the Bundlor as maven plugin with a small sample project and it works fine, but I've one question. Is it possible, that the version of the imported packages in the manifest is the same as the version which is defined in the dependencies section of the pom.xml? So I haven't to repeat all packages with their version in the import-template section.

By: Vorstellung des SpringSource dm Server | Von Tino Schmidt | Beitrag | Communardo Techblog

Thu, 09 Apr 2009 22:36:47 +0000

[...] Abhängigkeiten möglich wird. Eberhard Wolff regte auch am Beispiel des Werkzeuges Bundlor, dass für das Management der Abhängigkeiten und die Erzeugung von OSGI Manifesten genutzt [...]

By: SpringSource Team Blog » SpringSource dm Server Roadmap

SpringSource Team Blog » SpringSource dm Server Roadmap — Wed, 01 Apr 2009 13:13:43 +0000

[...] recently announced our Bundlor tool that simplifies the creation of OSGi manifests in Maven, Ant and Eclipse. We'll be releasing a [...]

By: SpringSource Team Blog » Using Bundlor in Eclipse

SpringSource Team Blog » Using Bundlor in Eclipse — Thu, 26 Mar 2009 05:58:48 +0000

[...] on March 26th, 2009 by Christian Dupuis in OSGi, Tools, dm Server. In an earlier blog, Ben introduced Bundlor, the concepts behind it and how to use it from the command line as well as [...]

By: Ben Hale

Ben Hale — Wed, 25 Mar 2009 09:30:23 +0000

@Matthew

That'll teach me to copy an exiting template without looking it over closely. You're right that you shouldn't need those duplicate entries, and in fact you don't. I've updated the example to be more correct.

As to the JDO metadata files, please open a story on the JIRA (https://issuetracker.springsource.com/browse/BNDLR) with the request.

By: Matthew Adams

Matthew Adams — Tue, 24 Mar 2009 18:48:00 +0000

Hi Ben,

I noticed one possible bit of redundancy in the information within the manifest template. It seems to me that if the user includes an entry in the Import-Package directive, then he shouldn't have to repeat those entries in the Import-Template directive, so as not to violate the DRY principle. Your example,

Import-Package:
ognl;version="[2.6.9, 3.0.0)";resolution:=optional,
org.jboss.el;version="[2.0.0, 3.0.0)";resolution:=optional
Import-Template:
org.springframework.*;version="[2.5.4.A, 3.0.0)",
org.apache.commons.logging;version="[1.1.1, 2.0.0)",
javax.el;version="[2.1.0, 3.0.0)";resolution:=optional,
ognl;version="[2.6.9, 3.0.0)";resolution:=optional,
org.jboss.el;version="[2.0.0, 3.0.0)";resolution:=optional

imports the packages ognl and org.jboss.el twice. Shouldn't it be sufficient to specify it in the Import-Package directive, which would imply its entry in Import-Template, or am I missing something? Would these entries ever be different in the Bundlor's manifest template?

BTW, nice addition to include the other supported files (JPA, Hibernate & properties). Can we add JDO metadata files to the list as well (META-INF/jdoconfig.xml, **/*.jdo, **/*.orm)?

-matthew