yeah, nice to hear: we added a lot of ITs to m-site-p to improve quality, and
this one surprised me a lot.
I'm glad I won't have to work once again on the topic :)
Regards,
Hervé
Le mardi 7 mai 2013 21:40:39 Andreas Gudian a écrit :
Ha, found it. The site plugin is working correctly, but I
-- Forwarded message --
From: agud...@apache.org
Date: 2013/4/28
Subject: svn commit: r860135 - in
/websites/production/maven/content/surefire: ./ css/ images/ js/
maven-failsafe-plugin/ maven-failsafe-plugin/apidocs/
maven-failsafe-plugin/apidocs/org/apache/maven
Date: 2013/4/28
Subject: svn commit: r860135 - in
/websites/production/maven/content/surefire: ./ css/ images/ js/
maven-failsafe-plugin/ maven-failsafe-plugin/apidocs/
maven-failsafe-plugin/apidocs/org/apache/maven/plugin/failsafe/
maven-failsafe-plugin/apidocs/org/apache/mav
: 2013/4/28
Subject: svn commit: r860135 - in
/websites/production/maven/content/surefire: ./ css/ images/ js/
maven-failsafe-plugin/ maven-failsafe-plugin/apidocs/
maven-failsafe-plugin/apidocs/org/apache/maven/plugin/failsafe/
maven-failsafe-plugin/apidocs/org/apache/mav
...@apache.org
Date: 2013/4/28
Subject: svn commit: r860135 - in
/websites/production/maven/content/surefire: ./ css/ images/ js/
maven-failsafe-plugin/ maven-failsafe-plugin/apidocs/
maven-failsafe-plugin/apidocs/org/apache/maven/plugin/failsafe/
maven-failsafe-plugin/apidocs/org
Published
text is now).
Any idea how we can get that back?
Thanks,
Andreas
-- Forwarded message --
From: agud...@apache.org
Date: 2013/4/28
Subject: svn commit: r860135 - in
/websites/production/maven/content/surefire: ./ css/ images/ js/
maven-failsafe-plugin/ maven-failsafe
is now).
Any idea how we can get that back?
Thanks,
Andreas
-- Forwarded message --
From: agud...@apache.org
Date: 2013/4/28
Subject: svn commit: r860135 - in
/websites/production/maven/content/surefire: ./ css/ images/ js/
maven-failsafe-plugin/ maven-failsafe-plugin/apidocs/
maven
2013/1/20 Hervé BOUTEMY herve.bout...@free.fr:
Le dimanche 20 janvier 2013 05:21:14 Hervé BOUTEMY a écrit :
So if we change our documentation release process to update a fixed
-latest place and svn copy on release, svnpubsub should be bearable IMHO
need to rephrase
if we change our
exactly
with or without Maven automation like the one Brett shown us
Regards,
Hervé
Le vendredi 25 janvier 2013 00:20:19 Olivier Lamy a écrit :
2013/1/20 Hervé BOUTEMY herve.bout...@free.fr:
Le dimanche 20 janvier 2013 05:21:14 Hervé BOUTEMY a écrit :
So if we change our documentation
Le dimanche 20 janvier 2013 05:21:14 Hervé BOUTEMY a écrit :
So if we change our documentation release process to update a fixed
-latest place and svn copy on release, svnpubsub should be bearable IMHO
need to rephrase
if we change our documentation release process to update a fixed
-latest
just for the record: I updated Maven 3.1-SNAPSHOT site, there were little
modifications in the code since last update (1 new package private class)
and here is the result:
[INFO] Publish files: 2 addition(s), 9373 update(s), 0 delete(s)
...
[INFO] Checked in 757 file(s) to revision: 847301
Objet : svn commit: r843406 - in
/websites/production/maven/content/surefire-archives/surefire-2.13: ./
maven-failsafe-plugin/ maven-failsafe-plugin/css/ maven-failsafe-plugin/images/
maven-failsafe-plugin/images/logos/ maven-failsafe-plugin/images/profiles/ m...
Date : lun., janv. 7, 2013 08:48
ok, thanks for the tips: will be useful to improve our configurations
FYI, I published latest Maven core 3.1-SNAPSHOT site as an update from
2012-12-16 state:
[INFO] Updating the pub tree from
scm:svn:https://svn.apache.org/repos/infra/websites/production/maven/content/ref/3.1-
SNAPSHOT ...
-Copyright #169; 2001-2012 a href=http://www.apache.org/;The Apache
Software Foundation/a. All Rights Reserved.
+Copyright #169; 2001-2013 a href=http://www.apache.org/;The Apache
Software Foundation/a. All Rights Reserved.
Looks like a once a year hit :)
- Brett
On 07/01/2013, at 5:25 PM,
we have aggregated javadoc.
Why generate one per module too ?
cpd/pmd/findbugs are already in sonar.
2013/1/7 Hervé BOUTEMY herve.bout...@free.fr:
ok, thanks for the tips: will be useful to improve our configurations
FYI, I published latest Maven core 3.1-SNAPSHOT site as an update from
Le mercredi 2 janvier 2013 23:43:52 Brett Porter a écrit :
On 02/01/2013, at 10:45 AM, Hervé BOUTEMY herve.bout...@free.fr wrote:
Le lundi 24 décembre 2012 14:17:02 Brett Porter a écrit :
I had the same feeling pushing up Continuum's Maven site recently...
On 23/12/2012, at 9:36 AM,
On 05/01/2013, at 10:57 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
ok, that was my first attempts back in july, not based on performance
expectations but simply logic
but the release procedure wasn't easy to automate in Maven: I don't see in
Continuum instrusction where the svn cp
On 02/01/2013, at 10:45 AM, Hervé BOUTEMY herve.bout...@free.fr wrote:
Le lundi 24 décembre 2012 14:17:02 Brett Porter a écrit :
I had the same feeling pushing up Continuum's Maven site recently...
On 23/12/2012, at 9:36 AM, Olivier Lamy ol...@apache.org wrote:
2012/12/22 Kristian
Le lundi 24 décembre 2012 14:17:02 Brett Porter a écrit :
I had the same feeling pushing up Continuum's Maven site recently...
On 23/12/2012, at 9:36 AM, Olivier Lamy ol...@apache.org wrote:
2012/12/22 Kristian Rosenvold kristian.rosenv...@zenior.no:
Svnsubpub is just ridiculously
Hi,
unfortunately i've found that the maven-failsafe-plugin web-page
http://maven.apache.org/surefire/maven-failsafe-plugin/index.html
does not contain a link to
Overview
in the top nav-bar
in contradiction to the maven-surefire-plugin web-page...
http://maven.apache.org/surefire/maven
2012/12/24 Brett Porter br...@apache.org:
I had the same feeling pushing up Continuum's Maven site recently...
On 23/12/2012, at 9:36 AM, Olivier Lamy ol...@apache.org wrote:
2012/12/22 Kristian Rosenvold kristian.rosenv...@zenior.no:
Svnsubpub is just ridiculously inefficient and we need to
I had the same feeling pushing up Continuum's Maven site recently...
On 23/12/2012, at 9:36 AM, Olivier Lamy ol...@apache.org wrote:
2012/12/22 Kristian Rosenvold kristian.rosenv...@zenior.no:
Svnsubpub is just ridiculously inefficient and we need to do something
about it...
That remember
:* *svn commit: r843406 - in
/websites/production/maven/content/surefire-archives/surefire-2.13: ./
maven-failsafe-plugin/ maven-failsafe-plugin/css/
maven-failsafe-plugin/images/ maven-failsafe-plugin/images/logos/
maven-failsafe-plugin/images/profiles/ m...*
*Svar til:* dev@maven.apache.org
??
Kristian
Videresendt melding:
*Fra:* krosenv...@apache.org
*Dato:* 22. desember 2012 02:18:53 GMT+07:00
*Til:* comm...@maven.apache.org
*Emne:* *svn commit: r843406 - in
/websites/production/maven/content/surefire-archives/surefire-2.13: ./
maven-failsafe-plugin/ maven-failsafe-plugin/css/
maven
/defaultConfiguration/SecondTest.java
(with props)
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/defaultConfiguration/ThirdTest.java
(with props)
Modified:
maven/surefire/trunk/maven-failsafe-plugin/src/main/java/org/apache/maven
/SecondTest.java
(with props)
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/defaultConfiguration/ThirdTest.java
(with props)
Modified:
maven/surefire/trunk/maven-failsafe-plugin/src/main/java/org/apache/maven/plugin
/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/defaultConfiguration/ThirdTest.java
(with props)
Modified:
maven/surefire/trunk/maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/IntegrationTestMojo.java
maven
-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/defaultConfiguration/ThirdTest.java
(with props)
Modified:
maven/surefire/trunk/maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/IntegrationTestMojo.java
maven/surefire/trunk/maven-surefire-common
Hi,
thanks for the answers...
Please file a ticket and I'm sure Kristian will update this for the next
release.
/Anders
Done.
http://jira.codehaus.org/browse/SUREFIRE-692
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH)
Hi,
just a question: If i open the maven-failsafe-plugin project page ( for
the link to the issue track it point to
http://jira.codehaus.org/browse/SUREFIRE ? Doesn't this project has it's
own project in JIRA ?
And one other point i found for the maven-failsafe-plugin
(http
just a question: If i open the maven-failsafe-plugin project page ( for the
link to the issue track it point to
http://jira.codehaus.org/browse/SUREFIRE ? Doesn't this project has it's
own project in JIRA ?
No, it shares the same JIRA project as the other surefire-related
components
http://maven.apache.org/plugins/maven-failsafe-plugin/) is that the link
to API (http://maven.apache.org/plugins/maven-failsafe-plugin/api.html)
produces a Page not found ?
Please file a ticket and I'm sure Kristian will update this for the next
release.
Yes, he will ;)
I talked
The way I understand you this is halfway a documentation issue; any
non-legal value including the string filesystem will actually give you
filesystem order.
So I could solve this by just adding filesystem to the list of legal
options, right ?
Another issue is that Dennis actually converted the
Kristian Rosenvold wrote:
The way I understand you this is halfway a documentation issue; any
non-legal value including the string filesystem will actually give you
filesystem order.
Oh I see, I didn't properly read the diff.
So I could solve this by just adding filesystem to the list of
On 2010-12-14 20:03, Kristian Rosenvold wrote:
The way I understand you this is halfway a documentation issue; any
non-legal value including the string filesystem will actually give you
filesystem order.
So I could solve this by just adding filesystem to the list of legal
options, right ?
ok, i'll back it out
On 5 August 2010 13:20, Benjamin Bentmann benjamin.bentm...@udo.edu wrote:
Stephen Connolly wrote:
I can roll it back out just wanted to ensure that because I was
specifying the requirements that they would be stated on the site
Well, the maven-plugin-plugin
:
maven/surefire/trunk/maven-failsafe-plugin/pom.xml
maven/surefire/trunk/maven-surefire-plugin/pom.xml
maven/surefire/trunk/maven-surefire-report-plugin/pom.xml
Modified: maven/surefire/trunk/maven-failsafe-plugin/pom.xml
URL:
http://svn.apache.org/viewvc/maven/surefire/trunk/maven
Yes, you fixed the issue. Cool !
;)
K
Den 5. aug. 2010 kl. 15:35 skrev Stephen Connolly
stephen.alan.conno...@gmail.com:
I'm fine with us dropping support for 1.3... people can still use surefire
2.2 if they need to run with jdk 1.3... or we can revisit surefire booter
but perhaps a vote.
:
[
http://jira.codehaus.org/browse/SUREFIRE-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly closed SUREFIRE-591.
-
Resolution: Fixed
Fix Version/s: 2.5
r897127.
Add maven-failsafe-plugin to surefire
: 2.5
r897127.
Add maven-failsafe-plugin to surefire project
-
Key: SUREFIRE-591
URL: http://jira.codehaus.org/browse/SUREFIRE-591
Project: Maven Surefire
Issue Type: New Feature
r897127.
Add maven-failsafe-plugin to surefire project
-
Key: SUREFIRE-591
URL: http://jira.codehaus.org/browse/SUREFIRE-591
Project: Maven Surefire
Issue Type: New Feature
Components
41 matches
Mail list logo
