I've done a lot of release today for use the same groupId in plexus deps
(org.codehaus.plexus). This strategy avoided me managing a great number of exclusions in
continuum dependencies. I thought one of these depdencency wasn't release since the
groupId change in all plexus components.
Perhaps we can integrate a scm diff in the release plugin between the current code and the
latest tag for check if we have some modifications in code and in pom.xml
Emmanuel
Brett Porter a écrit :
Hi,
I was looking over Emmanuel's Continuum release marathon today and
wondered if there were a couple of things we could do to improve the
process.
Two things stood out for me - maybe Emmanuel can highlight the reasons
they were necessary and we can come up with some solutions.
1) It appeared that a component was released even though it hadn't
changed, possibly misled by the fact that the version is bumped
immediately after the last release. If it had changed, there was no easy
way for me to tell.
- solution here is really the maintenance of a changelog or changes
file, but I'd like to discuss what options we have here a little more
2) It seemed some releases were needed just to bump a dependency
version. This really shouldn't be necessary as the end application
should be able to select the appropriate versions it wants as long as
they are compatible (though in some cases they may not use that
dependency themselves - so do we need a new construct for that, or
should it simply be included as runtime, or something else?) I think
here we'd benefit from hearing the reasons it was necessary in continuum
or any other examples others can come up with. One that springs to mind
for me is releasing plexus-site-renderer to get a new doxia for the site
plugin.
Looking forward to hearing your thoughts on these.
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
