Am Do., 6. Sep. 2018 um 09:52 Uhr schrieb Benedikt Ritter <
brit...@apache.org>:
> I have created COMMONSSITE-124 [1] in order to fix this. Will implement a
> fix later today.
>
> Benedikt
>
> [1] https://issues.apache.org/jira/browse/COMMONSSITE-124
>
COMMONSSITE-124 has been resolved in
I have created COMMONSSITE-124 [1] in order to fix this. Will implement a
fix later today.
Benedikt
[1] https://issues.apache.org/jira/browse/COMMONSSITE-124
Am Fr., 31. Aug. 2018 um 13:24 Uhr schrieb Benedikt Ritter <
brit...@apache.org>:
>
>
> Am Fr., 31. Aug. 2018 um 11:38 Uhr schrieb sebb
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
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 Mi., 22. Aug. 2018 um 14:33 Uhr schrieb Gilles <
gil...@harfang.homelinux.org>:
> On Wed, 22 Aug 2018 08:11:03 -0400, Rob Tompkins wrote:
> >> On Aug 22, 2018, at 1:47 AM, Benedikt Ritter
> >> wrote:
> >>
> >> Hi,
> >>
> >> I don't understand this discussion. Changes in Commons Parent have
>
Am Mi., 22. Aug. 2018 um 16:55 Uhr schrieb Gilles <
gil...@harfang.homelinux.org>:
> On Wed, 22 Aug 2018 16:24:57 +0200, Stefan Bodewig wrote:
> > On 2018-08-22, Rob Tompkins wrote:
> >
> >>> On Aug 22, 2018, at 9:03 AM, Stefan Bodewig
> >>> wrote:
> >
> >>> On 2018-08-22, Rob Tompkins wrote:
>
On Wed, 22 Aug 2018 16:24:57 +0200, Stefan Bodewig wrote:
On 2018-08-22, Rob Tompkins wrote:
On Aug 22, 2018, at 9:03 AM, Stefan Bodewig
wrote:
On 2018-08-22, Rob Tompkins wrote:
On Aug 22, 2018, at 1:47 AM, Benedikt Ritter
wrote:
Hi,
I don't understand this discussion. Changes in
On 2018-08-22, Rob Tompkins wrote:
>> On Aug 22, 2018, at 9:03 AM, Stefan Bodewig wrote:
>> On 2018-08-22, Rob Tompkins wrote:
On Aug 22, 2018, at 1:47 AM, Benedikt Ritter wrote:
Hi,
I don't understand this discussion. Changes in Commons Parent have broken
the
> On Aug 22, 2018, at 9:03 AM, Stefan Bodewig wrote:
>
> On 2018-08-22, Rob Tompkins wrote:
>
>>> On Aug 22, 2018, at 1:47 AM, Benedikt Ritter wrote:
>
>>> Hi,
>
>>> I don't understand this discussion. Changes in Commons Parent have broken
>>> the commons-compress build. So we should
On 2018-08-22, Rob Tompkins wrote:
>> On Aug 22, 2018, at 1:47 AM, Benedikt Ritter wrote:
>> Hi,
>> I don't understand this discussion. Changes in Commons Parent have broken
>> the commons-compress build. So we should either roll this changes back or
>> those who need the changes in commons
> On Aug 22, 2018, at 8:32 AM, Gilles wrote:
>
> On Wed, 22 Aug 2018 08:11:03 -0400, Rob Tompkins wrote:
>>> On Aug 22, 2018, at 1:47 AM, Benedikt Ritter wrote:
>>>
>>> Hi,
>>>
>>> I don't understand this discussion. Changes in Commons Parent have broken
>>> the commons-compress build. So
On Wed, 22 Aug 2018 08:11:03 -0400, Rob Tompkins wrote:
On Aug 22, 2018, at 1:47 AM, Benedikt Ritter
wrote:
Hi,
I don't understand this discussion. Changes in Commons Parent have
broken
the commons-compress build. So we should either roll this changes
back or
those who need the changes in
> On Aug 22, 2018, at 1:47 AM, Benedikt Ritter wrote:
>
> Hi,
>
> I don't understand this discussion. Changes in Commons Parent have broken
> the commons-compress build. So we should either roll this changes back or
> those who need the changes in commons parent should fix the commons
>
On 2018-08-22, Benedikt Ritter wrote:
> I don't understand this discussion. Changes in Commons Parent have broken
> the commons-compress build. So we should either roll this changes back or
> those who need the changes in commons parent should fix the commons
> compress build.
I have already
Hi,
I don't understand this discussion. Changes in Commons Parent have broken
the commons-compress build. So we should either roll this changes back or
those who need the changes in commons parent should fix the commons
compress build.
Regards,
Benedikt
Am Do., 16. Aug. 2018 um 19:08 Uhr
On Thu, Aug 16, 2018 at 10:27 AM Stefan Bodewig wrote:
> On 2018-08-16, Gary Gregory wrote:
>
> > I've use the release plugin a bunch without trouble. You might want to
> see
> > how other POMs are configured, for example [dbcp].
>
> The same way as Compress (no commons- prefix), I've got no
On 2018-08-16, Gary Gregory wrote:
> I've use the release plugin a bunch without trouble. You might want to see
> how other POMs are configured, for example [dbcp].
The same way as Compress (no commons- prefix), I've got no idea why
running site-deploy should work for it.
You use the release
Hi Stefan,
I've use the release plugin a bunch without trouble. You might want to see
how other POMs are configured, for example [dbcp].
You have to keep in mind that components like Collections, Lang, Pool, and
DBCP, the folder name is different from the artifact id because the
artifact id
Hi all
with
http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?r1=1831599=1832339
a component's site is expected to be a in subdirectory named after
${commons.componentTd} - it used to be the artifactId.
A quick look at
20 matches
Mail list logo
