GitHub user wilx opened a pull request:
https://github.com/apache/commons-io/pull/64
Two small tweaks.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/wilx/commons-io master-tweaks
Alternatively you can review and apply these
> On Aug 31, 2018, at 4:46 AM, Benedikt Ritter wrote:
>
> Am Do., 30. Aug. 2018 um 13:45 Uhr schrieb sebb :
>
>> On 30 August 2018 at 11:19, Thomas Vandahl wrote:
>>> On 28.08.18 12:03, sebb wrote:
On 28 August 2018 at 09:25, Mark Struberg
>> wrote:
>> This is unlikely to happen
On 30.08.18 13:45, sebb wrote:
>> You are free to choose whatever developmentVersion should be recorded.
>
> It should not be necessary to downdate the new version.
It isn't. You can configure that.
> Huh?
>
> If a local workspace contains spurious files, by definition it is
> inconsistent.
On 31.08.18 10:46, Benedikt Ritter wrote:
> Our release process is cumbersome and fragile leading to all release
> looking a little different from each other, depending on who is RM.
> The pain that our release process causes has been brought up again and
> again since I started here at commons
Am Fr., 31. Aug. 2018 um 11:38 Uhr schrieb sebb :
> On 31 August 2018 at 10:16, Benedikt Ritter wrote:
> > Hello,
> >
> > I upgraded commons-csv from parent v43 to parent v47. Now the site build
> > doesn't work anymore (see below). I think we should roll back said
> chance,
> > since it broke
On 31 August 2018 at 10:16, Benedikt Ritter wrote:
> Hello,
>
> I upgraded commons-csv from parent v43 to parent v47. Now the site build
> doesn't work anymore (see below). I think we should roll back said chance,
> since it broke multiple working component builds.
Which change are you talking
On Fri, 31 Aug 2018 10:35:32 +0200, Benedikt Ritter wrote:
This discussion keeps popping up every few month. At the end we alway
conclude that we don't want to publish anything that's binary
incompatible
under the same coordinates.
There was no such conclusion, as Gary's answer shows:
Hello,
I upgraded commons-csv from parent v43 to parent v47. Now the site build
doesn't work anymore (see below). I think we should roll back said chance,
since it broke multiple working component builds.
Benedikt
commons-csv build log:
~/w/a/c/commons-csv git:(master) 1M > mvn site
[INFO]
Am Do., 30. Aug. 2018 um 13:45 Uhr schrieb sebb :
> On 30 August 2018 at 11:19, Thomas Vandahl wrote:
> > On 28.08.18 12:03, sebb wrote:
> >> On 28 August 2018 at 09:25, Mark Struberg
> wrote:
> This is unlikely to happen as long as it does not cover multi-module
> builds
> >>>
> >>> The
This discussion keeps popping up every few month. At the end we alway
conclude that we don't want to publish anything that's binary incompatible
under the same coordinates. So way are we discussing this again? Appending
"beta" to a release version will not stop people from using it. So why not
10 matches
Mail list logo
