[forge-issues] [JBoss JIRA] (FORGE-1031) Synchronize repository.yaml model with Forge's plugin installation model
[
https://issues.jboss.org/browse/FORGE-1031?page=com.atlassian.jira.plugin...
]
Lincoln Baxter III commented on FORGE-1031:
-------------------------------------------
Actually this isn't the case. Though looking at our docs, it's also not very
clear.
The Maven Version is actually completely irrelevant, and is only used in creating the
directory structure within forge itself. You do not need to do any maven release of your
plugin, since Forge builds it all locally anyway, thus, whether you release or not, it
doesn't make a difference. You can leave your plugin as 0.0.1-SNAPSHOT for as long as
you like, and as long as you keep updating the branch/tag names to match the version of
Forge that that particular branch/tag supports, you'll be fine.
To summarize. Releasing your plugin has zero effect.
Sorry again for the confusion. And THANK YOU for raising these issues formally so that we
can make sure they get addressed.
~Lincoln
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