Hi,
We solved some more issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=14952
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1
Staging repo:
+1
On 2009-11-23, at 11:33 AM, Benjamin Bentmann wrote:
Hi,
We solved some more issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=14952
There are still a couple of issues left in JIRA:
+1
Arnaud Héritier
Software Factory Manager
eXo platform - http://www.exoplatform.com
---
http://www.aheritier.net
On Mon, Nov 23, 2009 at 5:38 PM, Jason van Zyl ja...@maven.org wrote:
+1
On 2009-11-23, at 11:33 AM, Benjamin Bentmann wrote:
Hi,
We solved some more issues:
+1
2009/11/23 Arnaud HERITIER aherit...@gmail.com
+1
Arnaud Héritier
Software Factory Manager
eXo platform - http://www.exoplatform.com
---
http://www.aheritier.net
On Mon, Nov 23, 2009 at 5:38 PM, Jason van Zyl ja...@maven.org wrote:
+1
On 2009-11-23, at 11:33 AM, Benjamin
+1
2009/11/23 nicolas de loof nicolas.del...@gmail.com:
+1
2009/11/23 Arnaud HERITIER aherit...@gmail.com
+1
Arnaud Héritier
Software Factory Manager
eXo platform - http://www.exoplatform.com
---
http://www.aheritier.net
On Mon, Nov 23, 2009 at 5:38 PM, Jason van Zyl ja...@maven.org
I wonder if we really need a full vote for every alpha. Especially if this is
going to happen every two weeks. Why not just vote for a 2 week alpha release
schedule and then don't do another vote until it's time for beta 1?
Benjamin Bentmann wrote:
Hi,
We solved some more issues:
I have tried to summarize the discussion/results of this topic so far. I
was not able to write to the wiki (user krosenvold), but if someone with
permissions would consider uploading this http://gist.github.com/241344
to the wiki (it's confluence format), It'd bring the process one step
forward.
Hi
It seems that someone has problems with their local
environment/repository. For the second time in a week the Maven site has
been published with maven-default-skin instead of maven-stylus-skin that
is specified in maven-parent.
I'm not sure why this is happening, but we need to get to the
Hi,
This is probably me. Can someone fix it? I deployed it today after
adding my book on the list. I did it several days ago after updating
the plugins list to add versions and animal sniffer from mojo.
Is there someone who can help me to analyze the problem ? I'm not
sure to have many times
What version of Maven are you building it with?
I suggest always doing a sanity check with mvn site before deploying
something.
- Brett
On 24/11/2009, at 8:16 AM, Arnaud HERITIER wrote:
Hi,
This is probably me. Can someone fix it? I deployed it today after
adding my book on the list. I
See below...
br...@apache.org wrote:
Author: brett
Date: Tue Nov 17 04:46:15 2009
New Revision: 881151
URL: http://svn.apache.org/viewvc?rev=881151view=rev
Log:
merge changes from branch and make minor improvements - now have aggregated
3.x-dev notes and aggregated 2.x notes
Added:
+1
--
Regards,
Igor
Benjamin Bentmann wrote:
Hi,
We solved some more issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=14952
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1
On 24/11/2009, at 8:53 AM, Dennis Lundberg wrote:
See below...
@@ -281,6 +287,14 @@
artifactIdmaven-site-plugin/artifactId
version2.0.1/version
!-- version2.1-SNAPSHOT/version --
+ dependencies
+!-- remove once we use a site-plugin
Dennis Lundberg wrote:
Hi,
We solved 18 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212version=14696
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11212status=1
Staging repo:
Hi,
The vote has passed with the following result :
+1 (binding): Arnaud Héritier, Benjamin Bentmann, Olivier Lamy, Hervé
Boutemy, Vincent Siveton, Dennis Lundberg
+1 (non binding): Michael
I will promote the artifacts to the central repo.
Dennis Lundberg wrote:
Hi,
We solved 18 issues:
Le Fri, 20 Nov 2009 23:15:41 +0100,
Dennis Lundberg denn...@apache.org a écrit :
Hi,
We solved 18 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212version=14696
There are still a couple of issues left in JIRA:
On Mon, Nov 23, 2009 at 10:39 PM, Brett Porter br...@apache.org wrote:
What version of Maven are you building it with?
I suppose/hope I did it with 2.2.1 before the trying 3.0
I suggest always doing a sanity check with mvn site before deploying
something.
I did it, but I focused only on
On 24/11/2009, at 10:12 AM, Arnaud HERITIER wrote:
I updated my /pom dir in our svn (I don't know why it wasn't up to date) and
... it works
I don't know what I had in my maven/asf pom to have this behavior.
Sorry for the annoyance. I'll be more conscientious the next time (I'm too
used
Hmm, I updated the site not to add the skin since it is inherited from the
parent. Maybe it's not actually being read from the repository?
It's sure because I just updated parent poms. I didn't install them.
Arnaud
Kristian Rosenvold wrote:
Ever since my git-fu got sufficiently strong I get this allergic rash
every time someone says subversion. Anyone wishing to join can just
fork and we'll have some git-fun ;)
I'm on Windows; the best Windows git client (msysgit) is covered in poison
oak. ;-)
-Dan
Someone'll probably have to get some antihistamines ;)
Seriously though, we're 20 people using git in my daily job, and we're
stuck on windows. Most of us are using cygwin (and that git is just like
a slower version of linux git). Eclipse has it's own java-based git
implementation (which lacks
21 matches
Mail list logo