Geronimo Revision: 706543 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081021/build-0300.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081021/unit-test
[
https://issues.apache.org/jira/browse/GERONIMO-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Charles updated GERONIMO-4337:
---
Attachment: geronimo-plugins.xml
svn.diff
I have built the activemq5
Hmmm ... good point. I was just setting it in maven opts (xMx). I'll
try setting it on the plugin config also and see if that helps.
Thanks,
Joe
Jason Dillon wrote:
Are you setting the plugin's maxmemory or just mvn's max?
--jason
On Oct 21, 2008, at 3:30 AM, Joe Bohn wrote:
I think it
The m-javadoc-plugin spawns a javadoc process, so the heap settings
for mvn aren't going to get used at all there. You must configure the
heap size in the plugins configuration.
--jason
On Oct 21, 2008, at 6:33 PM, Joe Bohn wrote:
Hmmm ... good point. I was just setting it in maven opts
Yep, that was the problem. I got it to work specifying maxmemory of
2048m (just started at the top) and then I decided to see if I could
make it work with something smaller and discovered something funny. In
genesis we specify 512 (not 512m). When I initially saw this I thought
it must
Geronimo Revision: 706618 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081021/build-0900.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081021/unit-test
Must be a change in the newer plugin, cause it used to work.
--jason
On Oct 21, 2008, at 8:13 PM, Joe Bohn wrote:
Yep, that was the problem. I got it to work specifying maxmemory of
2048m (just started at the top) and then I decided to see if I could
make it work with something smaller
I built and checked in the server 2.1.3 javadocs. This seemed to be the
most expedient thing to do but there are some concerns:
#1 This is a huge amount of content to include in svn. I think infra
will not be happy with us.
#2 Given #1, I debated deleting the 2.0.1 javadoc. However, this
Continuing the dialog with myself :-) ... I decided to cancel this
release candidate as well. I discovered a problem with the
maven-javadoc-plugin configuration that I'd like to correct in this
release of Genesis since it might be the last 1.x release. I'll have
another candidate available
Thanks Joe!
I'm not sure why the javadoc is checked in into svn in the first
place. Seems to me like that's unnecessary since we should always be
able to regenerate the javadoc from source. So, I'm ok with removing
any javadoc from svn but we should keep the javadoc for any major
Geronimo version
This is a vote for Genesis 1.5.
Take 3:
In addition to take 1 take 2 this includes a more appropriate javadoc
max memory setting.
Take 2:
Same as take 1 except for replacing the hard-coded dependency on
geronimo-skin from 1.5-SNAPSHOT with 1.5 (this release).
Take 1:
While trying to get
[
https://issues.apache.org/jira/browse/GERONIMO-4368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12641431#action_12641431
]
Jay D. McHugh commented on GERONIMO-4368:
-
I believe that what Donald meant when
I'm not really sure why the javadoc is checked into svn. I was just
following the same process used for 2.0.1. I suppose there is nothing
to prevent us from directly copying the content somewhere under
/www/geronimo.apache.org as we do for the maven generated sites. That
certainly sounds
Geronimo Revision: 706684 built with tests included
See the full build-1400.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.1/20081021/build-1400.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/2.1/20081021/unit-test-reports
[
https://issues.apache.org/jira/browse/GERONIMO-4368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12641496#action_12641496
]
Michał Kudła commented on GERONIMO-4368:
Strange. I installed again 2.1.3 and
[
https://issues.apache.org/jira/browse/GERONIMO-4368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michał Kudła closed GERONIMO-4368.
--
Resolution: Fixed
Fix Version/s: 2.1.3
2.1.4
strange, but now its
Geronimo Revision: 706723 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081021/build-1500.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081021/unit-test
Here's my +1
Joe
Joe Bohn wrote:
This is a vote for Genesis 1.5.
Take 3:
In addition to take 1 take 2 this includes a more appropriate javadoc
max memory setting.
Take 2:
Same as take 1 except for replacing the hard-coded dependency on
geronimo-skin from 1.5-SNAPSHOT with 1.5 (this
Wrong DEFAULT_IMAP_PORT in the Geronimo JavaMail 1.4 provider
-
Key: GERONIMO-4372
URL: https://issues.apache.org/jira/browse/GERONIMO-4372
Project: Geronimo
Issue Type: Bug
+1
-Donald
Joe Bohn wrote:
This is a vote for Genesis 1.5.
Take 3:
In addition to take 1 take 2 this includes a more appropriate javadoc
max memory setting.
Take 2:
Same as take 1 except for replacing the hard-coded dependency on
geronimo-skin from 1.5-SNAPSHOT with 1.5 (this release).
All,
Please join us in congratulating Jason Warner as the newest member of
the Geronimo PMC. It's been great to have Jason working with us as a
committer on Geronimo. Even better to have him join us in providing
oversight of the Geronimo project.
Way to go Jason!!!
The Apache Geronimo
Congrats and welcome Jason!!!
Joe
Kevan Miller wrote:
All,
Please join us in congratulating Jason Warner as the newest member of
the Geronimo PMC. It's been great to have Jason working with us as a
committer on Geronimo. Even better to have him join us in providing
oversight of the
+1
Reviewed source, generated artifacts, and maven site.
--kevan
On Oct 21, 2008, at 12:01 PM, Joe Bohn wrote:
This is a vote for Genesis 1.5.
Take 3:
In addition to take 1 take 2 this includes a more appropriate
javadoc max memory setting.
Take 2:
Same as take 1 except for replacing
Congrats Jason!
Jarek
On Tue, Oct 21, 2008 at 4:29 PM, Kevan Miller [EMAIL PROTECTED] wrote:
All,
Please join us in congratulating Jason Warner as the newest member of the
Geronimo PMC. It's been great to have Jason working with us as a committer
on Geronimo. Even better to have him join us
Congratulations Jason!
Jay
Kevan Miller wrote:
All,
Please join us in congratulating Jason Warner as the newest member of
the Geronimo PMC. It's been great to have Jason working with us as a
committer on Geronimo. Even better to have him join us in providing
oversight of the Geronimo
Kevan Miller wrote:
Please join us in congratulating Jason Warner as the newest member of
the Geronimo PMC. It's been great to have Jason working with us as a
committer on Geronimo. Even better to have him join us in providing
oversight of the Geronimo project.
Excellent! Congratulations
Congrats Jason!
-Donald
Kevan Miller wrote:
All,
Please join us in congratulating Jason Warner as the newest member of
the Geronimo PMC. It's been great to have Jason working with us as a
committer on Geronimo. Even better to have him join us in providing
oversight of the Geronimo
Congratulations from me too, Jason!
- Jack
2008/10/22 Donald Woods [EMAIL PROTECTED]
Congrats Jason!
-Donald
Kevan Miller wrote:
All,
Please join us in congratulating Jason Warner as the newest member of the
Geronimo PMC. It's been great to have Jason working with us as a committer
28 matches
Mail list logo
