[jbosstools-dev] Locus Repository Usage

[Rob Cernich]

> Hi Rob,
> 
> From a maintenance point-of-view, it would certainly improve matters for
> Teiid Designer since I have
> to update Designer's clone of the integration-stack-base.target every time a
> new build of locus is made.
> 
> However, there is a strong possibility in the future that locus will carry
> multiple versions of the
> same plugins, eg. saxon 9.2.1 (current in locus) and 9.4 (current released
> stable). In that
> scenario, JBT-IS will have to specify both versions if some projects use one
> version and some
> projects use another version. How likely this is remains a good question!

Isn't part of the goal of Locus to align the dependencies used by various components?  Hypothetically, what would happen if those two projects, using different versions of saxon, were installed in the same instance of Eclipse?  Unless the plugin depending on v. 9.2.1 were configured to only use versions 9.2.x or exactly 9.2.1, I'm guessing both projects would resolve the 9.4 version of saxon.

Personally, I think Locus, just like the TP's should be used for coordinating these dependencies.  (Just my opinion, as I haven't been involved with any of the activity surrounding Locus.  I'm sure there's a good pun in there somewhere;))

> 
> Regards
> 
> PGR
> 
> On 07/31/2013 06:00 PM, Rob Cernich wrote:
> > Hey all,
> > 
> > Recently, the JBTIS builds were broken and after a little analysis it
> > appears the culprit is Locus.  After looking at how JBTIS is using Locus,
> > I'm wondering if the target files for JBTIS are incorrect.
> > 
> > Currently, the target files declare specific artifact versions, but specify
> > the root locus repository URL.  Besides the fact that the JBTIS TP is
> > pointing to the "integration" repository for Locus, I'm wondering if it
> > would be better if we pointed at a specific version of Locus and simply
> > specified the artifacts without version.  This would require less
> > maintenance of the TP and should make the build more stable.  That said,
> > the solution would only work if it is acceptable to version the
> > dependencies based on a specific version of Locus.  Is this acceptable?
> > 
> > Reference:
> > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/target-platform/integration-stack-base.target#L10-34
> > Specific plugin versions would go to 0.0.0, while the repository URL would
> > go to .../stable/locus/<some-version>.
> > 
> > Thanks in advance,
> > Rob
> > _______________________________________________
> > jbosstools-dev mailing list
> > jbosstools-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> > 
> 
> --
> Paul Richardson
> 
>   * p.g.richardson at phantomjinx.co.uk
>   * p.g.richardson at redhat.com
>   * pgrichardson at linux.com
> 
> "I know exactly who reads the papers ...
> 
>   * The Daily Mirror is read by people who think they run the country.
>   * The Guardian is read by people who think they ought to run the country.
>   * The Times is read by people who do actually run the country.
>   * The Daily Mail is read by the wives of the people who run the country.
>   * The Financial Times is read by the people who own the country.
>   * The Morning Star is read by the people who think the country ought to be
>   run by another country.
>   * The Daily Telegraph is read by the people who think it is."
> 
> Jim Hacker, Yes Minister
> 
>