Hola Mau,
On Tue, Oct 25, 2011 at 10:31 AM, Maurizio Cucchiara
wrote:
> Hi Simo,
> IMHO it's a JB bug, we should take into consideration to file an issue
> on JIRA JB [1]
ack. I configured the plugin indeed to write the XML log directly to
${project.build.directory}
> The customkey is very usef
Hi Simo,
IMHO it's a JB bug, we should take into consideration to file an issue
on JIRA JB [1]
The customkey is very useful when you want compare the outcomes of
different tests: I chose the CHM label for the ConcurrentHashMap, HM
for the HashMap impl and so on.
I could be wrong, but we can omit th
Hi Izio,
I hoped the plugin generated the necessary directories, this would
make the build less portable, I'll study a solution.
Ah, I have yet another question for you: I noticed that in the old
bash scripts you required the jub.customkey system property as input
parameter, so I deduced you neede
try this
mkdir /Users/simonetripodi/Documents/workspace/commons-ognl/target/logs
Twitter :http://www.twitter.com/m_cucchiara
G+ :https://plus.google.com/107903711540963855921
Linkedin :http://www.linkedin.com/in/mauriziocucchiara
Maurizio Cucchiara
On 24 October 2011 22:25, Sim
Hi all guys,
I merged the work that Mau did in a separate branch, in the current
trunk. I got unfortunately some issues:
1) I don't know which values the `jub.customkey` property should take
2) tests produce errors: running `mvn clean test -P benchmarks` I get
the output below - system propertie
