ok, it's here now
thank you
Hervé
Le mercredi 11 décembre 2013 13:11:01 Igor Fedorenko a écrit :
> I emailed vote results couple of days before. Not sure what happened.
> I just resent the email. Let me know if you still don't see it.
>
> --
> Regards,
> Igor
>
> On 12/11/2013, 12:06, Hervé BO
Thanks for the release... Android Maven Plugin is using it now in master ;-)
> I emailed vote results couple of days before. Not sure what happened.
> I just resent the email. Let me know if you still don't see it.
>
> --
> Regards,
> Igor
>
> On 12/11/2013, 12:06, Hervé BOUTEMY wrote:
>> the arti
I emailed vote results couple of days before. Not sure what happened.
I just resent the email. Let me know if you still don't see it.
--
Regards,
Igor
On 12/11/2013, 12:06, Hervé BOUTEMY wrote:
the artifacts seem to be published in central [1], but I didn't see vote
result: did I miss something
On 12/9/2013, 21:24, Igor Fedorenko wrote:
Hi,
The vote has passed with the following result:
+1 (binding): Jason, Hervé, Olivier
+1 (non binding):
I will promote the artifacts to the central repo.
-
To unsubscribe, e-mail
the artifacts seem to be published in central [1], but I didn't see vote
result: did I miss something?
Regards,
Hervé
[1]
http://central.maven.org/maven2/org/apache/maven/plugin-testing/maven-plugin-testing/3.0.0/
Le vendredi 6 décembre 2013 08:11:49 Igor Fedorenko a écrit :
> Hi,
>
> We so
+1
On 10 December 2013 02:55, Igor Fedorenko wrote:
> Can I get some votes here please?
>
> --
> Regards,
> Igor
>
> On 12/6/2013, 8:11, Igor Fedorenko wrote:
>>
>> Hi,
>>
>> We solved 6 issues:
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740&version=18839
>>
>>
>> There ar
+1
Regards,
Hervé
Le vendredi 6 décembre 2013 08:11:49 Igor Fedorenko a écrit :
> Hi,
>
> We solved 6 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740&version=188
> 39
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/issues/?jql=project%
There are two versions of maven involved during maven-plugin-testing
build -- the version of maven used to run the build and the version of
maven core artifacts maven-plugin-testing depends on. Maven core
dependency version is controlled by maven-plugin-testing pom.xml (see
${mavenVersion} propert
Igor,
so why did "mvn verify" work locally with Maven 3.0.5? Is there a test
case missing which triggers the bug?
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Mon, Dec 9, 2
+1
On Dec 9, 2013, at 10:55 AM, Igor Fedorenko wrote:
> Can I get some votes here please?
>
> --
> Regards,
> Igor
>
> On 12/6/2013, 8:11, Igor Fedorenko wrote:
>> Hi,
>>
>> We solved 6 issues:
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740&version=18839
>>
>>
>> There
Can I get some votes here please?
--
Regards,
Igor
On 12/6/2013, 8:11, Igor Fedorenko wrote:
Hi,
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740&version=18839
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20
This looks like a bug in maven, I don't think maven-plugin-testing can
do anything about it.
--
Regards,
Igor
On 12/7/2013, 6:49, Karl Heinz Marbaise wrote:
Hi,
> Can you explain what behaviour did you expect with maven 3.0.x and
earlier? Did you expect sources release not to build? Did you e
maven-plugin-testing will not work with maven 3.0.x. MavenSession
constructor had signature changed from Sonatype to Eclipse Aether.
--
Regards,
Igor
On 12/8/2013, 17:39, Hervé BOUTEMY wrote:
I must admit I don't actually really understand if Maven Plugin Testing 3.0.0
can be used with Maven 3.
I must admit I don't actually really understand if Maven Plugin Testing 3.0.0
can be used with Maven 3.0.x or not
is there some compatibility documentation somewhere?
(no need to respin a vote, we can improve release docs by hand)
Regards,
Hervé
Le vendredi 6 décembre 2013 18:15:00 Igor Fedore
good
notice that the actual convention says it should be at
http://maven.apache.org/plugins-archives/plugin-testing-archives/plugin-testing-LATEST
but you're right that for such a component,
http://maven.apache.org/plugins-archives/plugin-testing-archives/LATEST is
nicer: no need to repeat com
It appeared to have worked. Thank you again, Hervé.
The site is in place now, where it should be
http://maven.apache.org/plugins-archives/plugin-testing-archives/LATEST
--
Regards,
Igor
On 12/7/2013, 9:33, Hervé BOUTEMY wrote:
no, your changes were properly staged in r889475 (from websites r
no, your changes were properly staged in r889475 (from websites repository)
you can see the result at http://maven.staging.apache.org/extpaths.txt
and it will be published in production site as soon as you "CMS publish" the
site (see
[2])
notice that the publication may fail since extpaths.txt
How do I make changes to extpaths.txt? My changes to svn [1] got
overwritten during site deploy as far as I can tell.
[1] http://svn.apache.org/viewvc?view=revision&revision=r1548906
--
Regards,
Igor
On 12/7/2013, 1:10, Hervé BOUTEMY wrote:
plugin-testing-archives is not in extpaths.txt [1]
t
Hi,
> Can you explain what behaviour did you expect with maven 3.0.x and
earlier? Did you expect sources release not to build? Did you expect
tests using maven-plugin-testing-3.0.0 to fail? Or is it something else?
I expected that Maven (3.0.X and 3.1) refused to build the sources which
did no
plugin-testing-archives is not in extpaths.txt [1]
than any deployment of the main site will remove what you deployed
you need to add an entry, then either redeploy content or remember the
revision of the previous deployment to cp the revision to actual trunk
tell me if you need me to help (no
Can you explain what behaviour did you expect with maven 3.0.x and
earlier? Did you expect sources release not to build? Did you expect
tests using maven-plugin-testing-3.0.0 to fail? Or is it something else?
--
Regards,
Igor
On 12/6/2013, 17:25, Karl Heinz Marbaise wrote:
Hi,
Non binding...(-
What did you expect to happen with maven 3.0.x and earlier? Did you
expect maven-plugin-testing-3.0.0 build to fail? Did you expect tests
using maven-plugin-testing-3.0.0 to fail? Or is it something else?
--
Regards,
Igor
On 12/6/2013, 17:25, Karl Heinz Marbaise wrote:
Hi,
Non binding...(-1?).
I don't know what happened to the documentation site.
It worked earlier today. I still have
~/maven-sites/plugin-testing-archives/LATEST with svn info pointing at
https://svn.apache.org/repos/infra/websites/production/maven/content/plugin-testing-archives/LATEST
but that svn is not there any more
Hi,
Non binding...(-1?)...
* Checked SHA1 of maven-plugin-testing-3.0.0-source-release.zip
* Tested with Maven 3.0.3, 3.0.4, 3.0.5, 3.1 and 3.1.1
Java version: 1.7.0_21
OS name: "mac os x" version: "10.8.5" arch: "x86_64" Family: "mac"
BUT based on the pom it should had been working with 3.1.
+0.9 (non-binding). As before:
* Checked SHA1 of maven-plugin-testing-3.0.0-source-release.zip
* Ran "mvn -V verify" on Mac OS X 10.9:
* JDK 1.6.0_51, Maven 3.0.5 and Maven 3.1.1
* JDK 1.7.0_45, Maven 3.0.5 and Maven 3.1.1
* JDK 1.8.0-ea, Maven 3.0.5 and Maven 3.1.1
However, for me,
http://m
On 12/5/2013, 7:42, Igor Fedorenko wrote:
Speaking of restage. What do we do with git tags during restage? Do we
create new tags, maven-plugin-testing-3.0.0-take2, for example, or we go
through the hassle of retag explained in [2]?
I dropped the old tag and created new one with the same name (
Hi,
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740&version=18839
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20%3D%20MPLUGINTESTING%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC
Stagin
While testing staged 3.0.0 I ran into a MPLUGINTESTING-32 [1], which has
to do with incorrect mojo configuration merge order and results in test
pom.xml configuration ignored by tests. I pushed the fix and regression
tests to master and plan to restage 3.0.0 later today.
Speaking of restage. What
+1 (non-binding)
* downloaded source-release.zip
* checked SHA1
* unzipped and ran "mvn install" successfully on Mac OS X 10.9 with:
* Maven 3.1.1, JDK 1.7.0_45
* Maven 3.1.1, JDK 1.6.0_51
One note: probably you should state in the Release-Mail, that Maven
2.2.1 and JDK5 are *not* supported
Wow. That was fast! :-)
--
Regards,
Igor
On 12/4/2013, 12:51, Manfred Moser wrote:
+1 for me. Works with the android maven plugin build using Maven 3.1.1
Thanks
Manfred
Hi,
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740&version=18839
There are still a
+1 for me. Works with the android maven plugin build using Maven 3.1.1
Thanks
Manfred
> Hi,
>
> We solved 4 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740&version=18839
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/issues/?jql=project
Hi,
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740&version=18839
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20%3D%20MPLUGINTESTING%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC
Stagin
32 matches
Mail list logo
