+1
On 7 June 2015 at 20:15, Karl Heinz Marbaise wrote:
> Hi,
>
> We solved 14 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=12331393
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2
Hi there,
I've already filed a ticket [0] for this, but I realize the behavior I'm
seeing could be by design, so I thought I'd bring it up over here.
What are the intended semantics of these handlers? In particular, I'm
seeing a handler instance appears to be reused across modules in a
multi-modu
+1
On Wed, Jun 10, 2015 at 5:38 PM, Hervé BOUTEMY wrote:
> +1
>
> Regards,
>
> Hervé
>
> Le dimanche 7 juin 2015 12:15:06 Karl Heinz Marbaise a écrit :
>> Hi,
>>
>> We solved 14 issues:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&ve
>> rsion=12331393
>>
>> There a
+1
Regards,
Hervé
Le dimanche 7 juin 2015 12:15:06 Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 14 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&ve
> rsion=12331393
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/
Hi,
AFAIK it is Aether which is responsible for these messages.
If you use M3.1.1 or above, you can change the logging of
conf/logging/simplelogger.properties
Based on http://www.slf4j.org/api/org/slf4j/impl/SimpleLogger.html I would
expect this to work:
org.slf4j.simpleLogger.log.org.sona
Hi,
here my +1
Kind regards
Karl Heinz Marbaise
On 6/7/15 12:15 PM, Karl Heinz Marbaise wrote:
Hi,
We solved 14 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=12331393
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/i
ok, the maven-reporting-impl 2.4 still has MSHARED-381 unresolved.
--
View this message in context:
http://maven.40175.n5.nabble.com/Unable-to-Update-to-DOXIA-1-6-latest-tp5837197p5837335.html
Sent from the Maven Developers mailing list archive at Nabble.com.
--
:-) Maybe later.
Thx Stephen for the advice.
--
View this message in context:
http://maven.40175.n5.nabble.com/Unable-to-Update-to-DOXIA-1-6-latest-tp5837197p5837331.html
Sent from the Maven Developers mailing list archive at Nabble.com.
---
I generally try to avoid more than 2, but hey - time to break records !
Kristian
2015-06-10 13:02 GMT+02:00 Stephen Connolly :
> The only issue is if there is a problem in one of the projects then you may
> need to respin all four... if you frame your vote email so that you can
> release the ear
Hi Herve,
I have reworked the old code of surefire in .
Since now we will not print after every new line.
Just printing plain text as it is in .
I will push the fix in the evening.
Cheers
--
View this message in context:
http://maven.40175.n5.nabble.com/Doxia-does-not-generate-br-tp583711
The only issue is if there is a problem in one of the projects then you may
need to respin all four... if you frame your vote email so that you can
release the earlier components in the event of an unrelated problem with
downstream projects then you should at least be able to make progress if
thing
I have to already release three projects at once. So i will add reporting.
Finally calling VOTE for 4 projects would not be any problem?
IMHO this saves the time for everyone.
maven-reporting-impl
maven-shared-utils
maven-verifier
surefire
--
View this message in context:
http://maven.40175.
12 matches
Mail list logo