aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Graham Charters <>
Subject Re: Start-order impl flawed for esa-maven-plugin
Date Fri, 13 Sep 2013 09:59:42 GMT
Hi Stephan,

I think it's good in general to avoid start-order, but some people need it.
 The contents are derived from the dependencies.  In the absence of any
other information source, the order they appear in the pom is all we have
to work with.  I wanted to be able to put an extra element in the
dependency information to be explicit about the order, but that doesn't
seem possible, and if we specify it anywhere else, then we're duplication
existing information.

Thanks for the getDenpendecies pointer.  I spotted that after I sent the
email.  I've not looked into how I can correlate those with the actual
artifacts yet, but if that's possible, then it might work.

Regards, Graham.

On 12 September 2013 07:29, Siano, Stephan <> wrote:

> Hi Graham,
> Maven uses some kind of ordering for dependencies to build the classpath.
> There is some project.getDependencies() call that returns a list, so this
> might be worth looking at. However I am not really sure how useful this
> startOrder feature in the current form is because usually in maven projects
> the order of dependencies is rather irrelevant, so putting some meaning
> into the order in which dependencies are defined for some plugin might be
> somewhat surprising (but that's my personal opinion and I also do not have
> a really good idea how to define a start-up order for bundles in a pom).
> Best regards
> Stephan
> -----Original Message-----
> From: Graham Charters []
> Sent: Mittwoch, 11. September 2013 17:49
> To:
> Subject: Start-order impl flawed for esa-maven-plugin
> The esa-maven-plugin purports to enable start-order to be determined by pom
> dependency order:
> *By default, the Subsystem runtime can start content bundles in any order.
> The OSGi start level service is not applicable to subsystems. You can
> therefore specify the start order of the bundles based on the order in
> which they're expressed as dependencies in the maven pom using the
> following:*
> *<configuration>
>   <startOrder>dependencies</startOrder></configuration>*
> Unfortunately, the MavenProject.getArtifactDependencies call that this
> uses returns a Set and therefore there are no dependency order
> guarantees.  I think we either need a way to specify an order element
> as part of a pom dependency or a way to get an ordered list of the
> dependencies, but I'm not aware of either of these facilities being
> available to maven plugins.  If nobody has any suggestions, then I'll
> need to pull this support for the existing esa-maven-plugin. :(
> Regards, Graham.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message