I'm not sure to understand what is the BOM approach,
Doing the release of maven artifact the current way is just the easy way, it
cost only a bit of time to upload and sign
AFAIK, the plugin that populate is able to release per spec version. (Need to
be rechecked maybe). So maven side could be done. Unsure how external will be
versioned.
If we want to go to another system we will have more work to do in the IDE.
Issue 1,
Apache NetBeans IDE list platform according to maven version name RELEASE* of a
specific artefact. RELEASE120 or RELEASE120-1 is understandable by user in the
selection panel.
But changing to spec version, will present specification version and we will
need a mechanism for a mapping that for example
o.n.core version 3.57 is platform 12.0
o.n.core version 3.58 is platform 12.1
If update are created 12.0-u1 and nothing is changed on core, user will have
to clue that there is a 12.0-u1.
So all in one, we need a more complex mechanism to get the mapping
information.
Issue 2,
upgrade existing maven project to a specific release, or last release. As an
example, let's have a plugin with 20 artifacts of Apache NetBeans used
Upgrading a maven project in the current approach,
is only to rename all RELEASEoldversion entry to RELEASEversionyouwant
or a property to change (bulk change, 1 search and replace),
maybe check that module became api or vice versa
Upgrading with spec version,
you have to look each entry, map the spec version to the release you
want. (IDE tool needed) maven version plugin can help getting only last
version. (20 changes to do)
No easy to do,
Best Regards
Eric
-----Message d'origine-----
De : Neil C Smith <[email protected]>
Envoyé : lundi 13 juillet 2020 10:40
À : dev <[email protected]>
Objet : Re: Apache NetBeans 12.0-u1is available for testing.
On Mon, 13 Jul 2020 at 09:14, Eric Barboni <[email protected]> wrote:
> It's possible to get the maven bits alongside a patch release, we only
> need a version scheme like RELEASE120-u1 knowing that RELEASE120-1 is
> taken by eventually a republish (may happen in the future)
>
> https://github.com/apache/netbeans-jenkins-lib/edit/master/meta/netbeansrelease.json
> mavenversion for release120 need to be updated for version number
> RELEASE120-u1 and it should be ok to stage.
It would be great to look at a BOM approach to this for the future, with the
modules by spec version. Having to update every Maven module for each update
release doesn't seem sustainable if we start having more of them. And be good
if the implementation versions remained in sync with the UCs?
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
