Hi,
I've had a chance to look at the commons release plugin and daemon again
- primarily as a way of generating the text for the VOTE email.
The current Commons Daemon specific release guide is:
https://github.com/apache/commons-daemon/blob/master/HOWTO-RELEASE.txt
If, at the end of the Maven
We have fixed a few bugs including a regression since Apache Commons
Daemon 1.2.3 was released, so I would like to release Apache Commons
Daemon 1.2.4.
Apache Commons Daemon 1.2.4 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/daemon/1.2.4-RC1
(svn revision
AFAICT Commons no longer uses CMS to build, so nothing needs to be done.
Sebb.
On Wed, 6 Jan 2021 at 12:51, Andrew Wetmore wrote:
>
>
> Hi, and happy New Year.
>
> Checking in on the migration of your project website from the Apache CMS to a
> different tech. Has there been progress? Have you
Great! Good luck.
Gary
On Wed, Jan 6, 2021, 09:02 Mark Thomas wrote:
> FYI, I'm expecting to tag 1.2.4-RC1 and start the release process later
> today.
>
> Mark
>
>
> On 23/11/2020 12:45, Rob Tompkins wrote:
> > I see. Let me give that a whirl
> >
> >> On Nov 23, 2020, at 3:58 AM, Mark Thomas
Ah, yes, we do have some needed duplication, I never use the stock release
plugin. We have two custom plugins that are handy for releasing.
Gary
On Wed, Jan 6, 2021, 07:14 Henri Biestro wrote:
>
> Found the culprit; it seems 'site' plugin uses the report section to
> generate the javadoc
FYI, I'm expecting to tag 1.2.4-RC1 and start the release process later
today.
Mark
On 23/11/2020 12:45, Rob Tompkins wrote:
> I see. Let me give that a whirl
>
>> On Nov 23, 2020, at 3:58 AM, Mark Thomas wrote:
>>
>> Rob,
>>
>> You shouldn't need to install any version of Visual Studio. The
Hi, and happy New Year.
Checking in on the migration of your project website from the Apache CMS to a
different tech. Has there been progress? Have you opened a Jira ticket to track
it? Is there anything Infra can help with?
A
Andrew Wetmore
Technical Writer-Editor
Infra
*Apache Software
Found the culprit; it seems 'site' plugin uses the report section to generate
the javadoc whilst 'release' plugin uses the build section to do the same.
Fixed the issue by adding the same javadoc plugin configuration in build
section of the pom.xml.
On 2021/01/05 17:05:32, Henri Biestro
Thanks John, IntelliJ is indeed rich in its options.
I realise my question was badly phrased; my problem is really about 'mvn site'
vs 'mvn release:prepare'. The former works executed from a shell or IntelliJ,
the latter does not failing on javadoc for a package that it should ignore.
On
