Hi,
I'm working on the Cobertura Maven Plugin over at Mojo, and have run
into a problem that I cannot solve.
This plugin wraps an external tool, Cobertura, which logs stuff either
by System.out.println() or by using Java Util Logging (JUL). The
printing to standard out/err is not a problem and th
Hello Hervé, thanks for the writeup. One question:
* is there anything wrong with using a plugin as an extension should
more than one plugin use the provided toolchain, i.e. is it worth to
split early?
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (ht
Hi,
I would like to start with releasing the asf pom version 16,
maven-parent version 26 and
maven-plugins version 27...
So i would go with first asf, second maven-parent and third maven-plugins ?
Any objections or issues which should go into ?
If no objections i would go to start with it to
Hi,
checked with Maven 2.2.1, 3.0.5,3.1.1, 3.2.1, 3.2.2, 3.2.3 without any
issue.
so +1 from me.
On 11/10/14 9:39 PM, Kristian Rosenvold wrote:
We solved 4 issues, including an enourmously irritating stacktrace
this component has been logging with -X.
http://jira.codehaus.org/secure/Releas
Hi Kristian,
On 11/10/14 9:27 PM, Kristian Rosenvold wrote:
No. Threadsafe annotation does not affect execution. It only affects nagging :)
Absolutely true... ;-)
But it's actually a quite good idea; we could probably synchronize
execution inside core for non-threadsafe mojos.
(Synchronizin
We solved 4 issues, including an enourmously irritating stacktrace
this component has been logging with -X.
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=17140
There are no issues left in JIRA.
http://repository.apache.org/content/repositories/maven-1095/org/apache/mav
No. Threadsafe annotation does not affect execution. It only affects nagging :)
But it's actually a quite good idea; we could probably synchronize
execution inside core for non-threadsafe mojos.
(Synchronizing inside the actual mojo is only moderately reliable...)
Kristian
2014-11-10 9:24 GMT+0
Hi,
based on a discussion i would like to know the following:
If a mojo is marked as threadsafe = true mean that two instances of the
mojo could be created and ran in parallel...if threadsafe = false this
will not happen so they will always run sequentiel...?
Is my assumption correct ? I ass
It's been a while since I look into this, but if I recall correctly my idea
was to add new component that would handle server credentials. If fronted
by a generic interface, it should be possible to plug in a different impl
possible using something else than settings.xml as the storage. The default
Well, see https://github.com/benson-basis/github-release-note-maven-plugin
for the code I have. Is this the sort of thing you're talking about?
On Mon, Nov 10, 2014 at 2:57 PM, Anders Hammar wrote:
>> I've been working with/on a plugin for talking to github, and I'm
>> staring at some fairly com
> I've been working with/on a plugin for talking to github, and I'm
> staring at some fairly complex code for processing proxy information
> from settings.xml, and some slightly less complex code for obtaining
> and decrypting credentials from servers.
>
> Is there a shared component in which I put
Hi Hervé,
So it sounds we need a new release of the parent pom's to get the new
information from the parent pom...
On 11/9/14 10:40 PM, Hervé BOUTEMY wrote:
cause of this strange "Default target for maven-compiler-plugin version
3.1"JDK requirement found:
http://jira.codehaus.org/browse/MPLUG
Github user asfgit closed the pull request at:
https://github.com/apache/maven-surefire/pull/67
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
13 matches
Mail list logo
