+1 for all that improve our horrible website.Your proposal is good, giving a
better management of // branches, thus +1
Cheers,
Arnaud
# Arnaud Héritier
# Software Factory Manager
# eXo Platform
# http://www.exoplatform.com
# http://blog.aheritier.net
On Fri, Jul 10, 2009 at 7:48 AM, Brett
baerrach wrote:
On Fri, Jul 10, 2009 at 6:19 AM, J. den Boerjdb...@diversit.eu wrote:
I'm trying to find the problem why no Eclipse project files can be
generated
of an Ear project without installing the required dependencies first.
I've seen that it's caused by the
+1 for all
Emmanuel
On Fri, Jul 10, 2009 at 7:48 AM, Brett Porter br...@apache.org wrote:
Hi,
I've committed some changes that I'd like reviewed to go forward with which
makes Maven releases easier.
1) see http://maven.apache.org/docs/2.0.11-RC1-SNAPSHOT/release-notes.html
(may
not be
Hi,
The main reason for this release is to get the current trunk out to our
users. This will be the last release that will work with Java 1.4. The
next release after this one will be upgraded to Checkstyle 5.0 and will
therefor require Java 5.
We solved 5 issues:
Hi,
The main reason for this release is to get the current trunk out to our
users. This will be the last release using Doxia 1.0. The next release
after this one will use Doxia 1.1.x.
We solved 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146styleName=Htmlversion=15076
Hi,
It has been well over two years since the last release, so it's about
time...
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11134styleName=Htmlversion=13201
There are still a couple of issues left in JIRA:
Hi,
I'd like to release this to help projects that hasn't switched over to
using Nexus yet.
We solved 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11695styleName=Htmlversion=13937
There are still a couple of issues left in JIRA:
On 10-Jul-09, at 1:48 AM, Brett Porter wrote:
Hi,
I've committed some changes that I'd like reviewed to go forward
with which makes Maven releases easier.
1) see http://maven.apache.org/docs/2.0.11-RC1-SNAPSHOT/release-notes.html
(may not be present yet due to proxying), and relevant
Hi Brett,
my responses are inline:
Brett Porter wrote:
+
+private String getWagonHint( String protocol, String repositoryId )
+{
+// TODO: Implement a better way to get the hint, via
settings.xml or something.
While this effectively is the same, I think it could be
2) see commits in site branch.
The basic approach is this:
* push all release notes into docs/$version/release-notes.html instead of
the consolidated older format and add a page to list them in order
So if someone wants to see the historical list of changes they will need to
look at N
I think jira should remain the consolidated list of bugs fixed during
a release. Having it on the site is important, but specifically I
don't want to have yet another file to update each time i fix a bug.
Grabbing the release notes from jira and updating the site is nice and
efficient and pretty
sorry, these changes should have been on a branch. I'll move that
across now so that trunk is still deployable. I'm heading out now but
I can respond to these issues later.
On 11/07/2009, at 12:27 AM, Jason van Zyl wrote:
On 10-Jul-09, at 1:48 AM, Brett Porter wrote:
Hi,
I've committed
On Fri, Jul 10, 2009 at 6:17 PM, jdboerjdb...@diversit.eu wrote:
I know about the lifecycle and I've seen the ear lifecycle.
Because the ear:generateApplicationXml goal is causing the problem
(probably) I created a custom Ear plugin with version 2.3.2-TEST in which I
removed the
13 matches
Mail list logo
