I see this has been fixed now. Merci!
/Anders
On Thu, Dec 20, 2012 at 10:32 PM, Anders Hammar wrote:
> Thanks Olivier!
>
> /Anders
>
>
>
> On Thu, Dec 20, 2012 at 10:02 PM, Olivier Lamy wrote:
>
>> oh ok
>> Apologize my bad I read too fast the acronym from Anders :-)
>> I will fix that.
>>
>>
You're looking at the wrong place. The xml stuff is listed early in the
build output (before any plugin execution), but what you're looking for is
listed in the beginning of the execution of the plugin in question.
/Anders
On Fri, Dec 21, 2012 at 2:21 AM, Benson Margulies wrote:
> I expect that
ok
can you explain the ant/ivy build pipeline implementing promotion you did with
the help of my team mates?
(notice I won't be here for 1 week, so won't be able to continue the
discussion for the moment, but the topic is worth more discussion)
Regards,
Hervé
Le jeudi 20 décembre 2012 12:12:2
No, "license.excludedGroups" is the java system property you specify on
command-line to configure. The name of the parameter itself is what you
configure in the pom.
/Anders
On Fri, Dec 21, 2012 at 2:16 AM, Benson Margulies wrote:
> @Parameter( property = "license.excludedGroups", defaultValue
The Maven team is pleased to announce the release of
maven-shared-utils, version 0.2
This project aims to be a functional replacement for
{{{http://plexus.codehaus.org/plexus-utils}plexus-utils}} in Maven.
It is not a 100% API compatible replacement though but a replacement
:
lots of methods got
I expect that when I run mvn -X (3.0.4), I'll see the actual
configuration values in use in the mojo.
With the license-maven-plugin, whatever I do, I see just XML templates like:
${license.useMissingFile}
Any value I actually configure is not shown.
Did I hallucinate the previous useful output
I suppose it logically must be so that a typo points to missing test
coverage Well not this typo - any more!
Thanks,
Kristian
Den 21. des. 2012 kl. 00:58 skrev Robert Scholte :
> Looks like a typo: 'p' too much...
>
> Op Thu, 20 Dec 2012 15:54:07 +0100 schreef :
>
>> else if ( "junit.framew
Hi,
The vote has passed with the following result :
+1 (binding): Olivier, Robert, Hervé, Kristian
I will promote the artifacts to the central repo.
(I will complete the "release paperwork" for verifier and m-s-u later tonight)
Kristian
Thanks Olivier!
/Anders
On Thu, Dec 20, 2012 at 10:02 PM, Olivier Lamy wrote:
> oh ok
> Apologize my bad I read too fast the acronym from Anders :-)
> I will fix that.
>
> 2012/12/20 Robert Scholte :
> > Let me try to clarify:
> >
> > The site shows the wrong version of the maven-plugin-plugin
oh ok
Apologize my bad I read too fast the acronym from Anders :-)
I will fix that.
2012/12/20 Robert Scholte :
> Let me try to clarify:
>
> The site shows the wrong version of the maven-plugin-plugin.
> Actually, everything under http://maven.apache.org/plugin-tools/ refers to
> 3.1 instead of 3.
+1
Regards,
Hervé
Le lundi 17 décembre 2012 16:33:25 Kristian Rosenvold a écrit :
> Hi,
>
> We solved 3 issues
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=174
> 32
>
> There are 2 issues left in jira;
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=tr
Let me try to clarify:
The site shows the wrong version of the maven-plugin-plugin.
Actually, everything under http://maven.apache.org/plugin-tools/ refers to
3.1 instead of 3.2
Robert
Op Thu, 20 Dec 2012 17:31:35 +0100 schreef Olivier Lamy :
2012/12/20 Anders Hammar :
euh I just checked
+1
Robert
Op Thu, 20 Dec 2012 12:17:24 +0100 schreef Kristian Rosenvold
:
+1
Need one more PMC vote ;)
Kristian
2012/12/17 Kristian Rosenvold :
Hi,
We solved 3 issues
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=17432
There are 2 issues left in jira;
http:
Looks like a typo: 'p' too much...
Op Thu, 20 Dec 2012 15:54:07 +0100 schreef :
else if ( "junit.framework.AssertiponFailedError".equals(
target.getClass().getName() )
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.o
2012/12/20 Anders Hammar :
>> euh I just checked
>>
>> http://svn.apache.org/viewvc/maven/site/trunk/pom.xml?revision=1419847&view=markup
>> and it's 3.2 :-)
>>
>> see
>> http://svn.apache.org/viewvc/maven/site/trunk/pom.xml?r1=1408002&r2=1410738&diff_format=h
>>
>
> maven-site-plugin? I don't foll
> euh I just checked
>
> http://svn.apache.org/viewvc/maven/site/trunk/pom.xml?revision=1419847&view=markup
> and it's 3.2 :-)
>
> see
> http://svn.apache.org/viewvc/maven/site/trunk/pom.xml?r1=1408002&r2=1410738&diff_format=h
>
maven-site-plugin? I don't follow.
/Anders
>
> 2012/12/20 Olivier
euh I just checked
http://svn.apache.org/viewvc/maven/site/trunk/pom.xml?revision=1419847&view=markup
and it's 3.2 :-)
see
http://svn.apache.org/viewvc/maven/site/trunk/pom.xml?r1=1408002&r2=1410738&diff_format=h
2012/12/20 Olivier Lamy :
> 2012/12/20 Anders Hammar :
>> Would be happy to do it,
2012/12/20 Anders Hammar :
> Would be happy to do it, but I have to admit that I'm not sure of the
> process now. Is the docs [1] correct?
> So "mvn site-deploy -Preporting" on the right version should do it?
I started a bit of documentation here
http://maven.apache.org/developers/website/deploy-m
Would be happy to do it, but I have to admit that I'm not sure of the
process now. Is the docs [1] correct?
So "mvn site-deploy -Preporting" on the right version should do it?
/Anders
[1] http://maven.apache.org/developers/release/maven-plugin-release.html
On Thu, Dec 20, 2012 at 12:01 PM, Oliv
I'm quite sure I deployed that, but that's a bit of a worthless point
in these days ;)
K
Den 20. des. 2012 kl. 18:01 skrev Olivier Lamy :
> 2012/12/20 Anders Hammar :
>> The site for m-plugin-p is for 3.1, not the latest 3.2 version. Did
>> something go wrong in the latest release, or did this h
+1
Need one more PMC vote ;)
Kristian
2012/12/17 Kristian Rosenvold :
> Hi,
>
> We solved 3 issues
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=17432
>
> There are 2 issues left in jira;
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=proj
Yes, I want to start the build of other projects if new version of the
promoted artifact is available.
Imagine a larger project in which 15-50 modules exists. Top level
module build is triggered by the available new modules with a specific
status i.e. performance tests run when new version of the
2012/12/20 Anders Hammar :
> The site for m-plugin-p is for 3.1, not the latest 3.2 version. Did
> something go wrong in the latest release, or did this happen in the cms
> switch?
must work.
Nobody upgraded that.
So feel free to test it and do the upgrade.
>
> /Anders
--
Olivier Lamy
Talend: h
The site for m-plugin-p is for 3.1, not the latest 3.2 version. Did
something go wrong in the latest release, or did this happen in the cms
switch?
/Anders
GitHub user Tibor17 opened a pull request:
https://github.com/apache/maven-surefire/pull/17
Proposed use of New JUnit ParallelComputer in Surefire
I agreed with @krosenvold to push the first changes on the use of
ParallelComputer in Surefire.
We have to decide whether we ke
25 matches
Mail list logo