]-
[WARNING] *
[WARNING] * Your build is requesting parallel execution, but project *
[WARNING] * contains the following plugin(s) that have goals not marked *
[WARNING] * as @threadSafe to support
See
https://cwiki.apache.org/confluence/display/MAVEN/Parallel+builds+in+Maven+3
On Fri, 12 Jan 2018 08:31:43 +0100, Anders Hammar
wrote:
mvn -T 2C ... IIRC.
/Anders
On Fri, Jan 12, 2018 at 12:02 AM, Tibor Digana
wrote:
What was initially intended with Mojo#threadSafe ?
Was it the
mvn -T 2C ... IIRC.
/Anders
On Fri, Jan 12, 2018 at 12:02 AM, Tibor Digana
wrote:
> What was initially intended with Mojo#threadSafe ?
> Was it the use case mvn -T 2C ...?
> Or it was parallel processes execution from the project root?
> For instance report-plugin which generates H
What was initially intended with Mojo#threadSafe ?
Was it the use case mvn -T 2C ...?
Or it was parallel processes execution from the project root?
For instance report-plugin which generates HTML files is threadsafe?
Cheers
Tibor
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
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:2
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
Excellent!
Thanks!
-Chris
On Fri, Jul 27, 2012 at 8:43 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> per goal
>
> On 27 July 2012 11:27, Chris Graham wrote:
>
> > Hi All.
> >
> > Do we mark an entire plugin as @threadSafe or each goal
per goal
On 27 July 2012 11:27, Chris Graham wrote:
> Hi All.
>
> Do we mark an entire plugin as @threadSafe or each goal specifically? I can
> easily see that some goals within a single plugin could be threadsafe,
> whilst others in the same plugin not threadsafe.
>
> So,
Hi All.
Do we mark an entire plugin as @threadSafe or each goal specifically? I can
easily see that some goals within a single plugin could be threadsafe,
whilst others in the same plugin not threadsafe.
So, what is the level of granularity of this?
-Chris
52 skrev Chris Graham :
>
> > :-)
> >
> > Ta much.
> >
> > -Chris
> >
> > On Thu, May 17, 2012 at 2:27 PM, Kristian Rosenvold <
> > kristian.rosenv...@zenior.no> wrote:
> >
> >> yes
> >>
> >> Den 17. mai 2012 kl. 06:18 skrev Ch
>>
>> Den 17. mai 2012 kl. 06:18 skrev Chris Graham :
>>
>>> Hi All.
>>>
>>> Can we mark a plugin as threadSafe AND still have it work under JRE 1.4
>> and
>>> Maven 2.0.9?
>>>
>>> Obviously, it's ability to run in par
:-)
Ta much.
-Chris
On Thu, May 17, 2012 at 2:27 PM, Kristian Rosenvold <
kristian.rosenv...@zenior.no> wrote:
> yes
>
> Den 17. mai 2012 kl. 06:18 skrev Chris Graham :
>
> > Hi All.
> >
> > Can we mark a plugin as threadSafe AND still have it work
yes
Den 17. mai 2012 kl. 06:18 skrev Chris Graham :
> Hi All.
>
> Can we mark a plugin as threadSafe AND still have it work under JRE 1.4 and
> Maven 2.0.9?
>
> Obviously, it's ability to run in parallel mode would require Maven 3.
>
> So, if I mark a plugin as bei
Hi All.
Can we mark a plugin as threadSafe AND still have it work under JRE 1.4 and
Maven 2.0.9?
Obviously, it's ability to run in parallel mode would require Maven 3.
So, if I mark a plugin as being @threadSafe, will it still be able to be
run under the older JRE's and Maven's?
-Chris
maven-3.html says the
maven-remote-resources-plugin 1.2 is threadsafe. However...
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.2:process (default) on
project assemblies: Error rendering velocity resource.
t; intermittent error. I've never gotten this error bulding single threaded.
>>
>> https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html says the
>> maven-remote-resources-plugin 1.2 is threadsafe. However...
>>
>> [ERROR] Failed to execute goal
>&g
his intermittent
error. I've never gotten this error bulding single threaded.
https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html says the
maven-remote-resources-plugin 1.2 is threadsafe. However...
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resour
Rosenvold
> > Subject: Re: really threadsafe?
> > To: "Maven Developers List"
> > Date: Sunday, March 27, 2011, 7:48 PM
> > The problem seems to be within
> > velocity, or at least within the ancient
> > version of velocity that's being used by the r
http://svn.codehaus.org/plexus/tags/plexus-velocity-1.1.3/
LieGrue,
strub
--- On Sun, 3/27/11, Kristian Rosenvold wrote:
> From: Kristian Rosenvold
> Subject: Re: really threadsafe?
> To: "Maven Developers List"
> Date: Sunday, March 27, 2011, 7:48 PM
> The p
ache.org/MAVEN/parallel-builds-in-maven-3.html says the
> maven-remote-resources-plugin 1.2 is threadsafe. However...
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-remote-resources-plugin:1.2:process (default)
> on project assemblies:
en-3.html says the
maven-remote-resources-plugin 1.2 is threadsafe. However...
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.2:process (default) on
project assemblies: Error rendering velocity resource. NullPoi
Hi all,
I see that m-deploy-p isn't marked as threadSafe yet. As I don't remember
having seen any threads about it, isn't there any technical reason for this?
I mean, though I'm no concurrency expert, I'm wondering if I could try and
have a look at the code to help. B
On 2011-02-08 21:41, Dennis Lundberg wrote:
> I think it would be a useful service to our users to list which plugins
> and components are @threadSafe, and also in which version it was first
> marked as @threadSafe.
A list of released plugins is now in place, as well as some that a
t;> their own plugins.
>>>
>>
>> Same plugin could be run on the Apache Nexus instance. They have to mark the
>> mojos as theadsafe, but you could easily generate the list so people would
>> know, or could even be metadata IDEs could consume to guide users if the
the list so people would
> know, or could even be metadata IDEs could consume to guide users if they are
> to find @threadsafe plugins.
>
>> On 2011-02-08 22:36, Jason van Zyl wrote:
>>> Write a Nexus plugin that walks a repository looking for Maven plugins,
>>> c
have to mark the
mojos as theadsafe, but you could easily generate the list so people would
know, or could even be metadata IDEs could consume to guide users if they are
to find @threadsafe plugins.
> On 2011-02-08 22:36, Jason van Zyl wrote:
>> Write a Nexus plugin that walks a repository
it would be a useful service to our users to list which plugins
>> and components are @threadSafe, and also in which version it was first
>> marked as @threadSafe.
>>
>> We can start writing things down on the wiki page you mentioned. I'll
>> add a new heading and sta
, at 3:41 PM, Dennis Lundberg wrote:
> I think it would be a useful service to our users to list which plugins
> and components are @threadSafe, and also in which version it was first
> marked as @threadSafe.
>
> We can start writing things down on the wiki page you mentioned. I
t would be a useful service to our users to list which plugins
>> and components are @threadSafe, and also in which version it was first
>> marked as @threadSafe.
>>
>> We can start writing things down on the wiki page you mentioned. I'll
>> add a new heading and
as thread safe.
/Anders
[1] http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html
On Tue, Feb 8, 2011 at 21:41, Dennis Lundberg wrote:
> I think it would be a useful service to our users to list which plugins
> and components are @threadSafe, and also in which vers
I think it would be a useful service to our users to list which plugins
and components are @threadSafe, and also in which version it was first
marked as @threadSafe.
We can start writing things down on the wiki page you mentioned. I'll
add a new heading and start to accumulate the info. W
find . -name *Mojo.java | xargs grep threadSafe
I suppose that may not be good enough ;) I was hoping to get all the
non-deprecated
core plugins @threadSafe, and by the looks of it it's not that far off.
If I subtract the retirement-candidates there only seem to be a few left.
I&
Hi
I'd like to start a list of which versions of plugins and components are
@threadSafe. Where should we have such a list?
--
Dennis Lundberg
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional com
Thanks Kristian!
On 2011-01-09 20:41, Kristian Rosenvold wrote:
> Done.
>
> Kristian
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
Done.
Kristian
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
I'll do it tonight
Den 9. jan. 2011 kl. 19:11 skrev Dennis Lundberg :
> Hi
>
> I've gone through the issues for the Remote Resources Plugin and now
> there is only one left:
>
> "Add @threadSafe support for maven3"
> http://jira.codehaus.org/browse/MRRESO
Hi
I've gone through the issues for the Remote Resources Plugin and now
there is only one left:
"Add @threadSafe support for maven3"
http://jira.codehaus.org/browse/MRRESOURCES-50
Can someone help to get this fixed before I make the 1.2 release?
Threads are not my cup of tea..
Hi,
Thanks for your answer.
So, done :
http://jira.codehaus.org/browse/MENFORCER-106
http://jira.codehaus.org/browse/MRRESOURCES-50
And by the way:
Buildnumber-m-p : http://jira.codehaus.org/browse/MOJO-1567 (not mvn core).
Cheers
2010/9/9 Kristian Rosenvold
> You should create issues. I sup
You should create issues. I suppose posting a little email here or on
users-list might bring attention to the issue, like you just did :)
krist...@javazone
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional
Hi all,
While playing with parallel build on my project, I noticed some warnings and
tried upgrading plugins.
Two main maven plugins (remote-resources and enforcer) have not been
released with the @threadsafe annotation.
I crawled the JIRA and didn't find an issue filed about it. I was wond
On Tuesday 08 June 2010 5:51:09 am Olivier Lamy wrote:
> done too (and snapshot deployed).
> Can you test this with cxf build
Looks good. :-)
Dan
>
> 2010/6/8 Olivier Lamy :
> > we probably need to add @threadSafe in PMD too.
> > I have created MPMD-122 (and
done too (and snapshot deployed).
Can you test this with cxf build
2010/6/8 Olivier Lamy :
> we probably need to add @threadSafe in PMD too.
> I have created MPMD-122 (and will try to do it today)
>
> 2010/6/8 Daniel Kulp :
>> On Monday 07 June 2010 7:03:49 pm Olivier Lamy wrote
we probably need to add @threadSafe in PMD too.
I have created MPMD-122 (and will try to do it today)
2010/6/8 Daniel Kulp :
> On Monday 07 June 2010 7:03:49 pm Olivier Lamy wrote:
>> Hi,
>> So I have fixed all dependencies issues and deploy a snapshot.
>> Can you test on
eSource
> >> >
> >> > There is probably a harness update or something else required to get
> >> > it to use the new package, but I've tried updating a bunch of things
> >> > without success.
> >> >
> >> > Dan
> >> >
without success.
>> >
>> > Dan
>> >
>> >> On 6/3/10 12:02 PM, Daniel Kulp wrote:
>> >>> I've been working on getting the CXF builds to at least build (not run
>> >>> the tests yet) with the Maven 3 // mode. With the updates
Before having looked at the source code in question, I could only
recommend plexus-utils 2.0.5 (on a general basis), because all of the
executeCommandLine methods are deadlock prone prior to that version.
I find it quite hard to evaluate if any of the transitive dependencies
included in the plugi
el Kulp wrote:
> >>> I've been working on getting the CXF builds to at least build (not run
> >>> the tests yet) with the Maven 3 // mode. With the updates to the
> >>> checkstyle plugin, I've now done about a dozen or so builds with
> &g
ds to at least build (not run
the tests yet) with the Maven 3 // mode.With the updates to the
checkstyle plugin, I've now done about a dozen or so builds with various
-T settings without any failures.I'm not quite ready to declare an
@threadSafe victory for the PMD and Checkstyle
arious
> > -T settings without any failures.I'm not quite ready to declare an
> > @threadSafe victory for the PMD and Checkstyle plugins (will probably
> > loop it overnight), but it's definitely looking promising now.
> >
> > HOWEVER, according to Kr
in, I've now done about a dozen or so builds with various -T settings
> without any failures. I'm not quite ready to declare an @threadSafe victory
> for the PMD and Checkstyle plugins (will probably loop it overnight), but it's
> definitely looking promising now.
>
With the updates to the checkstyle
plugin, I've now done about a dozen or so builds with various -T settings
without any failures.I'm not quite ready to declare an @threadSafe victory
for the PMD and Checkstyle plugins (will probably loop it overnight), but it's
definitely l
I've been working on getting the CXF builds to at least build (not run the
tests yet) with the Maven 3 // mode.With the updates to the checkstyle
plugin, I've now done about a dozen or so builds with various -T settings
without any failures.I'm not quite ready to declare
53 matches
Mail list logo
