You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Emmanuel Lécharny <el...@gmail.com> on 2016/07/05 13:12:49 UTC
ApacheDS-2.0.0-M22 : pb with the installers
Hi guys,
I just tested some of the linux installers, as 2 useras are complaining.
There is an issue with a bad declaration in the wrapper.conf file.
The workaround is to remove line 38 in the wrapper.conf file :
...
# Java Additional Parameters
wrapper.java.additional.1=-Dlog4j.configuration=${double.quote}file:///%INSTANCE_DIRECTORY%/conf/log4j.properties${double.quote}
wrapper.java.additional.2=-Dapacheds.var.dir=${double.quote}%INSTANCE_DIRECTORY%${double.quote}
wrapper.java.additional.3=-Dapacheds.log.dir=${double.quote}%INSTANCE_DIRECTORY%/log${double.quote}
wrapper.java.additional.4=-Dapacheds.run.dir=${double.quote}%INSTANCE_DIRECTORY%/run${double.quote}
wrapper.java.additional.5=-Dapacheds.instance=${double.quote}%INSTANCE%${double.quote}
wrapper.java.additional.6=%REPAIR_COMMAND%
<------------------------------------------------------------- This line
is wrong
Now, the pb is that it's just a workaround, and we should fix the
problem in the sources. I wan do that, and produce new installers.
Here is what I suggest : once this fix is applied, I can produce the
installers for a new version (2.0.0-M23) that will be voted in less than
72 hours (let's say 24h), just because teh server's code itself won't be
changed.
Wdyt ?
Re: ApacheDS-2.0.0-M22 : pb with the installers
Posted by Emmanuel Lécharny <el...@gmail.com>.
Le 05/07/16 � 19:49, Stefan Seelmann a �crit :
> On 07/05/2016 03:12 PM, Emmanuel L�charny wrote:
>> Hi guys,
>>
>>
>> I just tested some of the linux installers, as 2 useras are complaining.
>> There is an issue with a bad declaration in the wrapper.conf file.
>>
>>
>> The workaround is to remove line 38 in the wrapper.conf file :
>>
>> ...
>>
>> # Java Additional Parameters
>> wrapper.java.additional.1=-Dlog4j.configuration=${double.quote}file:///%INSTANCE_DIRECTORY%/conf/log4j.properties${double.quote}
>> wrapper.java.additional.2=-Dapacheds.var.dir=${double.quote}%INSTANCE_DIRECTORY%${double.quote}
>> wrapper.java.additional.3=-Dapacheds.log.dir=${double.quote}%INSTANCE_DIRECTORY%/log${double.quote}
>> wrapper.java.additional.4=-Dapacheds.run.dir=${double.quote}%INSTANCE_DIRECTORY%/run${double.quote}
>> wrapper.java.additional.5=-Dapacheds.instance=${double.quote}%INSTANCE%${double.quote}
>> wrapper.java.additional.6=%REPAIR_COMMAND%
>> <------------------------------------------------------------- This line
>> is wrong
>>
>>
>> Now, the pb is that it's just a workaround, and we should fix the
>> problem in the sources. I wan do that, and produce new installers.
>>
>>
>> Here is what I suggest : once this fix is applied, I can produce the
>> installers for a new version (2.0.0-M23) that will be voted in less than
>> 72 hours (let's say 24h), just because teh server's code itself won't be
>> changed.
>>
>>
>> Wdyt ?
> That's ok for me, but not only create the installers, but do a full
> release, right?
Right.
>
> However the fact that this happend worries me. I created the Jenkins job
> to test the installers [1] on purpose. However it only runs once a week
> and the vote was exactly in between. Now it fails. I need to remember to
> run it during the vote and for the release version too.
I also need to remember to test all the installers before starting a
vote. Just because I can start the server on my machine does not mean it
works well on linux :/
My bad.
Re: ApacheDS-2.0.0-M22 : pb with the installers
Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
On 07/05/2016 03:12 PM, Emmanuel L�charny wrote:
> Hi guys,
>
>
> I just tested some of the linux installers, as 2 useras are complaining.
> There is an issue with a bad declaration in the wrapper.conf file.
>
>
> The workaround is to remove line 38 in the wrapper.conf file :
>
> ...
>
> # Java Additional Parameters
> wrapper.java.additional.1=-Dlog4j.configuration=${double.quote}file:///%INSTANCE_DIRECTORY%/conf/log4j.properties${double.quote}
> wrapper.java.additional.2=-Dapacheds.var.dir=${double.quote}%INSTANCE_DIRECTORY%${double.quote}
> wrapper.java.additional.3=-Dapacheds.log.dir=${double.quote}%INSTANCE_DIRECTORY%/log${double.quote}
> wrapper.java.additional.4=-Dapacheds.run.dir=${double.quote}%INSTANCE_DIRECTORY%/run${double.quote}
> wrapper.java.additional.5=-Dapacheds.instance=${double.quote}%INSTANCE%${double.quote}
> wrapper.java.additional.6=%REPAIR_COMMAND%
> <------------------------------------------------------------- This line
> is wrong
>
>
> Now, the pb is that it's just a workaround, and we should fix the
> problem in the sources. I wan do that, and produce new installers.
>
>
> Here is what I suggest : once this fix is applied, I can produce the
> installers for a new version (2.0.0-M23) that will be voted in less than
> 72 hours (let's say 24h), just because teh server's code itself won't be
> changed.
>
>
> Wdyt ?
That's ok for me, but not only create the installers, but do a full
release, right?
However the fact that this happend worries me. I created the Jenkins job
to test the installers [1] on purpose. However it only runs once a week
and the vote was exactly in between. Now it fails. I need to remember to
run it during the vote and for the release version too.
Kind Regards,
Stefan
[1]
https://builds.apache.org/view/A-D/view/Directory/job/dir-apacheds-docker-installers/