[forge-issues] [JBoss JIRA] (FORGE-1031) Synchronize repository.yaml model with Forge's plugin installation model

[Lennart Jörelid (JIRA)]

Lennart Jörelid created FORGE-1031:
--------------------------------------

             Summary: Synchronize repository.yaml model with Forge's plugin installation model
                 Key: FORGE-1031
                 URL: https://issues.jboss.org/browse/FORGE-1031
             Project: Forge
          Issue Type: Enhancement
          Components: Documentation, Plugin API, Plugin Repository
    Affects Versions: 1.3.3.Final
            Reporter: Lennart Jörelid
            Priority: Minor


The repository.yaml file holds a Maven GAV to each Forge Plugin.
However, Forge's resolution only retrieves the latest/HEAD revision of a particular Git Branch, ignoring the Maven GAV given in the repository.yaml.

Thus, one *must* release SNAPSHOT plugin versions in order to be able to bugfix Forge plugins. This is quite contrary to a normal Maven release, where SNAPSHOT versions are not permitted (for example by the release plugin).

So ...

# Forge only uses HEAD of a branch to find a plugin source code revision
# Repository.yaml indicates that a particular Maven GAV for a project should be used for the plugin
# During resolution, Forge ignores the Maven GAV in repository.yaml
# Maven releases are normally not permitted to contain SNAPSHOTs, but the two facts above *requires* Forge plugins to be Maven SNAPSHOTs.

It seems that two different (and not particularly coherent) models are used to define Forge's resolution here.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira