From a testing perspective I find this discussion interesting; failsafe
has *minute* amounts of code which is distinct from surefire, and most
of this
is just the boilerplate stuff needed because reusing mojos is hard.
Most of the current IT coverage in surefire only runs with the surefire
Hi
**shameless self-advertisement, sorry**
You can try my com.google.code.maven-svn-wagon: maven-svn-wagon (dev site at
http://code.google.com/p/maven-svn-wagon/, the artifact is available from
the Central). In general it works just as the Kohsuke's
org.jvnet.wagon-svn:wagon-svn, and it
On Tue, 17 Jan 2012 15:18:46 -0500
John Casey jdca...@commonjava.org wrote:
+1 (non-binding)
Works fine to me.
Tony.
Hi,
We solved 8 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11138version=17354
There are still plenty of issues left in JIRA:
If it depends on svnkit, apache projects _may_ have issues using it due to
tge svnkit license.
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On Jan 19, 2012 8:13 a.m., Oleg
+1
Kristian
Den 17.01.2012 21:18, skrev John Casey:
Hi,
We solved 8 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11138version=17354
There are still plenty of issues left in JIRA:
+1
Kristian
Den 17.01.2012 11:14, skrev Olivier Lamy:
Hello,
After some RCs, it's now time to cut the release. So I start the vote
for Apache Maven 3.0.4.
The release notes is available here:
http://maven.apache.org/docs/3.0.4/release-notes.html
The staging repo:
Hi Oleg!!!
On the other hand - I remember trying to push the generated site directly to
the svn using both wagon-svn and maven-svn-wagon and in the end I decided to
generate the new site on the local filesystem instead and then manually
checkout old site, overwrite it with the generated files
+1
Emmanuel
On Tue, Jan 17, 2012 at 9:18 PM, John Casey jdca...@commonjava.org wrote:
Hi,
We solved 8 issues:
http://jira.codehaus.org/**secure/ReleaseNote.jspa?**
projectId=11138version=17354http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11138version=17354
There are still
hi,
+1 non-binding from me...
Tested with different of my projects no problems at all...
Kind regards
Karl Heinz Marbaise
-
Kind regards
Karl Heinz Marbaise
http://www.soebes.de
http://www.skmwiki.de
http://supose.org/wiki/supose
--
View this message in context:
I caused the Surefire build to fail, but I'll be damned if I can figure
out how.
https://builds.apache.org/job/maven-surefire/193/consoleFull
Anyone have any insight into how I can see the failures?
Thanks,
-john
--
John Casey
Developer, PMC Chair - Apache Maven (http://maven.apache.org)
Greetings,
On Thu, Jan 19, 2012 at 1:16 PM, John Casey jdca...@commonjava.org wrote:
I caused the Surefire build to fail, but I'll be damned if I can figure out
how.
https://builds.apache.org/job/maven-surefire/193/consoleFull
Anyone have any insight into how I can see the failures?
If you
This error:
Jan 19, 2012 6:02:51 PM hudson.remoting.Channel$ReaderThread run
SEVERE: I/O error in channel channel
java.io.StreamCorruptedException
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1332)
at
I'm going to need more +1 to push this through.
From the other threads it looks like mostly everyone else is using intellij.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
On 19/01/2012, at 7:40 PM, Stephen Connolly wrote:
If it depends on svnkit, apache projects _may_ have issues using it due to
tge svnkit license.
It's not a problem to use it for deploying our site, it'd be a problem if we
wanted to distribute it as part of a release. How we deploy our site
On 18/01/2012, at 7:59 PM, Arnaud Héritier wrote:
Perhaps if the SCM was GIT instead of SVN it could be faster ?
It's not a short term solution but it can be another reason to use Git ASAP.
I think you misinterpreted a typo in Simone's email - it's the CMS, not the SCM.
This isn't
Hi all guys,
just to let you know that today I moved the Apache Any23[1] site
deploying to local FS directory and then manual commit.
It took *more than two hours*, with the good business ADSL upload band
at office ... :(
Whatever solution we can adopt to deploy the site on svn, it takes too
+1
On Jan 19, 2012, at 3:55 PM, Barrie Treloar baerr...@gmail.com wrote:
I'm going to need more +1 to push this through.
From the other threads it looks like mostly everyone else is using intellij.
-
To unsubscribe, e-mail:
+1
2012/1/19 Barrie Treloar baerr...@gmail.com:
I'm going to need more +1 to push this through.
From the other threads it looks like mostly everyone else is using intellij.
-
To unsubscribe, e-mail:
+1, release it! (I know some guys who can't wait ;) )
We might need to update several skin-sites later, because some of them are
still using the previous stylus-skin.
For instance, IE9 shows a scrollbar in the menu, long menu items don't use
text-indent
So for your vote please verify the
+1
Hervé
Le mardi 17 janvier 2012 15:18:46 John Casey a écrit :
Hi,
We solved 8 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11138version=173
54
There are still plenty of issues left in JIRA:
+1
Hervé
Le vendredi 13 janvier 2012 09:52:34 Barrie Treloar a écrit :
Hi,
We solved 25 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11133version=162
40
There are still a large backlog of issues left in JIRA: (extra support
would be appreciated)
+1
Hervé
Le mercredi 18 janvier 2012 21:54:23 Simone Tripodi a écrit :
Hi all guys,
I am here to propose the RC2 Maven Skins version 6, that includes
* Maven Application Skin 1.0
* Maven Default Skin 1.1
* Maven Classic Skin 1.1
* Maven Stylus Skin 1.4
* Maven Fluido Skin 1.1
We
+1
On 17 January 2012 20:18, John Casey jdca...@commonjava.org wrote:
Hi,
We solved 8 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11138version=17354
There are still plenty of issues left in JIRA:
+1
On 18 January 2012 20:54, Simone Tripodi simonetrip...@apache.org wrote:
Hi all guys,
I am here to propose the RC2 Maven Skins version 6, that includes
* Maven Application Skin 1.0
* Maven Default Skin 1.1
* Maven Classic Skin 1.1
* Maven Stylus Skin 1.4
* Maven Fluido Skin 1.1
Issue Subscription
Filter: Design Best Practices (24 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
https://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
On Wed, 18 Jan 2012 21:54:23 +0100
Simone Tripodi simonetrip...@apache.org wrote:
+1 (non-binding)
Oh yeah :)
Thanks,
Tony.
Hi all guys,
I am here to propose the RC2 Maven Skins version 6, that includes
* Maven Application Skin 1.0
* Maven Default Skin 1.1
* Maven Classic Skin 1.1
+1
Kristian
2012/1/18 Simone Tripodi simonetrip...@apache.org:
Hi all guys,
I am here to propose the RC2 Maven Skins version 6, that includes
* Maven Application Skin 1.0
* Maven Default Skin 1.1
* Maven Classic Skin 1.1
* Maven Stylus Skin 1.4
* Maven Fluido Skin 1.1
We solved
27 matches
Mail list logo
