Re: [Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC1
Hi Jarek, You are right. I use mvn release:prepare -Pallsubproject and mvn release:perform -Pallsubproject but there is no allsubproject profile... Thank you for pointing it out. I will re-release it. On Mon, Jul 16, 2012 at 11:23 PM, Jarek Gawor jga...@gmail.com wrote: John, Looks like the testsuite pom files still use SNAPSHOT versions. Jarek On Mon, Jul 16, 2012 at 5:23 AM, Yi Xiao xiaoyijhondeve...@gmail.com wrote: Hi devs, Please help to review and vote on the release of Geronimo Eclipse Plugin (GEP) 3.0.0 RC1. GEP 3.0.0 supports Geronimo server 3.0.0, 2.2.1, 2.1.7 and Eclipse 3.7, 3.8, 4.2. [Known issue] 1. GEP 3.0.0 uses maven-eclipsepde-plugin v1.1, which means it can not be built successfully on 64bit win7 and 64bit macos. See following JIRAs for details. - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-737 Could not build GEP3.0 under win7-64bit - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Could not build GEP3.0 under macos-64bit 2. Also, please use maven v2.2.1 to build GEP 3.0.0 as following JIRA is still open. - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-694 Can not build GEP with maven 3.0 3. The plugins/org.apache.geronimo.st.v11.schemas/v11/xml.xsd uses W3C license and plugins/org.apache.geronimo.st.schemas/v30/persistence_2_0.xsd uses Eclipse Public License, so the rat check on them are failed. The source code zip is here: https://repository.apache.org/content/repositories/orgapachegeronimo-053/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.zip https://repository.apache.org/content/repositories/orgapachegeronimo-053/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.tar.gz The tag is here: http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0.0/ The deployable zip file is here: http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-deployable.zip The p2 repo zip file is here: http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-p2repo.zip Notice: As update site format is not recommend in eclipse, now only provide the p2 format. If you would like to review and/or comment on the release notes, you can find it here: http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.0.txt Finally, I've created a Staging Site that can be used to test the update manager functions of Eclipse (Indigo SR2 and Juno): http://people.apache.org/builds/geronimo/eclipse/updates/ The vote will be open for the 72-hour minimum. [ ] +1 about time to push this out the door [ ] 0 no opinion [ ] -1 not this one (please explain why) -- Best regards! John Xiao -- Best regards! John Xiao
Re: [Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC1
Hi Kevan, I think you use maven3 to execute mvn :) now, GEP only support maven2, you could refer to [Known issue] 2 And also, if you use MAC-64bit, will still get some error infos for [Known issue] 1. On Tue, Jul 17, 2012 at 12:32 AM, Kevan Miller kevan.mil...@gmail.comwrote: Anybody building successfully on a Mac? I'm getting errors like: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile) on project org.apache.geronimo.runtime.common: Compilation failure: Compilation failure: [ERROR] /Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.0/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[21,31] package org.eclipse.core.runtime does not exist [ERROR] [ERROR] /Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.0/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[22,31] package org.eclipse.core.runtime does not exist [ERROR] [ERROR] /Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.0/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[23,31] package org.eclipse.core.runtime does not exist [ERROR] --kevan On Jul 16, 2012, at 5:23 AM, Yi Xiao wrote: Hi devs, Please help to review and vote on the release of Geronimo Eclipse Plugin (GEP) 3.0.0 RC1. GEP 3.0.0 supports Geronimo server 3.0.0, 2.2.1, 2.1.7 and Eclipse 3.7, 3.8, 4.2. [Known issue] 1. GEP 3.0.0 uses maven-eclipsepde-plugin v1.1, which means it can not be built successfully on 64bit win7 and 64bit macos. See following JIRAs for details. - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-737 Could not build GEP3.0 under win7-64bit - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Could not build GEP3.0 under macos-64bit 2. Also, please use maven v2.2.1 to build GEP 3.0.0 as following JIRA is still open. - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-694 Can not build GEP with maven 3.0 3. The plugins/org.apache.geronimo.st.v11.schemas/v11/xml.xsd uses W3C license and plugins/org.apache.geronimo.st.schemas/v30/persistence_2_0.xsd uses Eclipse Public License, so the rat check on them are failed. The source code zip is here: https://repository.apache.org/content/repositories/orgapachegeronimo-053/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.zip https://repository.apache.org/content/repositories/orgapachegeronimo-053/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.tar.gz The tag is here: http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0.0/ The deployable zip file is here: http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-deployable.zip The p2 repo zip file is here: http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-p2repo.zip Notice: As update site format is not recommend in eclipse, now only provide the p2 format. If you would like to review and/or comment on the release notes, you can find it here: http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.0.txt Finally, I've created a Staging Site that can be used to test the update manager functions of Eclipse (Indigo SR2 and Juno): http://people.apache.org/builds/geronimo/eclipse/updates/ The vote will be open for the 72-hour minimum. [ ] +1 about time to push this out the door [ ] 0 no opinion [ ] -1 not this one (please explain why) -- Best regards! John Xiao -- Best regards! John Xiao
Re: [Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC1
On Jul 17, 2012, at 2:29 AM, Yi Xiao wrote: Hi Kevan, I think you use maven3 to execute mvn :) now, GEP only support maven2, you could refer to [Known issue] 2 And also, if you use MAC-64bit, will still get some error infos for [Known issue] 1. Thanks for the reminders John. I forget everytime… ;-) Everything looks pretty good, except it seems we're missing the slf4j license (we're redistributing slffj-api and slf4j-simple in org.apache.geronimo.runtime.v30_3.0.0.jar Here's my -1, until we address that… As long as we have people validating the build, I'll be +1 once the licensing issue is resolved. Thanks! --kevan
[jira] [Created] (GERONIMO-6373) Expose HOWL flushPartialBuffer config via HOWLLog - useful under low concurrency
Gary Tully created GERONIMO-6373:
Summary: Expose HOWL flushPartialBuffer config via HOWLLog -
useful under low concurrency
Key: GERONIMO-6373
URL: https://issues.apache.org/jira/browse/GERONIMO-6373
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: transaction manager
Affects Versions: 2.2.1
Reporter: Gary Tully
HOWL XALogger supports flushPartialBuffers which is not configurable via
Geronimo HOWLLog. It is useful in the case of low concurrency.
It would be great to have this exposed in the HOWLLog constructor so that it be
be configured.
{code} /**
* Indicates whether LogBufferManager should flush buffers
* before they are full.
*
* pNormally, buffers are flushed to disk only when
* they become full. In lightly loaded situations,
* one or more threads may have to wait until the
* flushSleepTime expires before the buffer is written.
* In the worst case, a single thread is using the
* log, and every put() with sync requested will
* be delayed flushSleepTime ms before the buffer is
* written.
*
* pSetting flushPartialBuffers true will allow
* the LogBufferManager to flush buffers to disk
* any time the channel is not busy. This improves
* throughput in single threaded and lightly loaded
* environments.
*
* pBy default, this feature is disabled (false) to
* provide compatability with earlier versions of
* this library.
*/
private boolean flushPartialBuffers = false;{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6373) Expose HOWL flushPartialBuffer config via HOWLLog - useful under low concurrency
[
https://issues.apache.org/jira/browse/GERONIMO-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated GERONIMO-6373:
-
Attachment: GERONIMO-6372.patch
Patch that adds boolean flushPartialBuffers to the constructor
Expose HOWL flushPartialBuffer config via HOWLLog - useful under low
concurrency
Key: GERONIMO-6373
URL: https://issues.apache.org/jira/browse/GERONIMO-6373
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: transaction manager
Affects Versions: 2.2.1
Reporter: Gary Tully
Attachments: GERONIMO-6372.patch
HOWL XALogger supports flushPartialBuffers which is not configurable via
Geronimo HOWLLog. It is useful in the case of low concurrency.
It would be great to have this exposed in the HOWLLog constructor so that it
be be configured.
{code} /**
* Indicates whether LogBufferManager should flush buffers
* before they are full.
*
* pNormally, buffers are flushed to disk only when
* they become full. In lightly loaded situations,
* one or more threads may have to wait until the
* flushSleepTime expires before the buffer is written.
* In the worst case, a single thread is using the
* log, and every put() with sync requested will
* be delayed flushSleepTime ms before the buffer is
* written.
*
* pSetting flushPartialBuffers true will allow
* the LogBufferManager to flush buffers to disk
* any time the channel is not busy. This improves
* throughput in single threaded and lightly loaded
* environments.
*
* pBy default, this feature is disabled (false) to
* provide compatability with earlier versions of
* this library.
*/
private boolean flushPartialBuffers = false;{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6373) Expose HOWL flushPartialBuffer config via HOWLLog - useful under low concurrency
[
https://issues.apache.org/jira/browse/GERONIMO-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated GERONIMO-6373:
-
Attachment: GERONIMO-6372.patch
Patch that adds new constructor that takes additional flushPartialBuffers arg.
Expose HOWL flushPartialBuffer config via HOWLLog - useful under low
concurrency
Key: GERONIMO-6373
URL: https://issues.apache.org/jira/browse/GERONIMO-6373
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: transaction manager
Affects Versions: 2.2.1
Reporter: Gary Tully
Attachments: GERONIMO-6372.patch
HOWL XALogger supports flushPartialBuffers which is not configurable via
Geronimo HOWLLog. It is useful in the case of low concurrency.
It would be great to have this exposed in the HOWLLog constructor so that it
be be configured.
{code} /**
* Indicates whether LogBufferManager should flush buffers
* before they are full.
*
* pNormally, buffers are flushed to disk only when
* they become full. In lightly loaded situations,
* one or more threads may have to wait until the
* flushSleepTime expires before the buffer is written.
* In the worst case, a single thread is using the
* log, and every put() with sync requested will
* be delayed flushSleepTime ms before the buffer is
* written.
*
* pSetting flushPartialBuffers true will allow
* the LogBufferManager to flush buffers to disk
* any time the channel is not busy. This improves
* throughput in single threaded and lightly loaded
* environments.
*
* pBy default, this feature is disabled (false) to
* provide compatability with earlier versions of
* this library.
*/
private boolean flushPartialBuffers = false;{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6373) Expose HOWL flushPartialBuffer config via HOWLLog - useful under low concurrency
[
https://issues.apache.org/jira/browse/GERONIMO-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated GERONIMO-6373:
-
Attachment: (was: GERONIMO-6372.patch)
Expose HOWL flushPartialBuffer config via HOWLLog - useful under low
concurrency
Key: GERONIMO-6373
URL: https://issues.apache.org/jira/browse/GERONIMO-6373
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: transaction manager
Affects Versions: 2.2.1
Reporter: Gary Tully
Attachments: GERONIMO-6372.patch
HOWL XALogger supports flushPartialBuffers which is not configurable via
Geronimo HOWLLog. It is useful in the case of low concurrency.
It would be great to have this exposed in the HOWLLog constructor so that it
be be configured.
{code} /**
* Indicates whether LogBufferManager should flush buffers
* before they are full.
*
* pNormally, buffers are flushed to disk only when
* they become full. In lightly loaded situations,
* one or more threads may have to wait until the
* flushSleepTime expires before the buffer is written.
* In the worst case, a single thread is using the
* log, and every put() with sync requested will
* be delayed flushSleepTime ms before the buffer is
* written.
*
* pSetting flushPartialBuffers true will allow
* the LogBufferManager to flush buffers to disk
* any time the channel is not busy. This improves
* throughput in single threaded and lightly loaded
* environments.
*
* pBy default, this feature is disabled (false) to
* provide compatability with earlier versions of
* this library.
*/
private boolean flushPartialBuffers = false;{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6373) Expose HOWL flushPartialBuffer config via HOWLLog - useful under low concurrency
[
https://issues.apache.org/jira/browse/GERONIMO-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated GERONIMO-6373:
-
Comment: was deleted
(was: Patch that adds boolean flushPartialBuffers to the constructor)
Expose HOWL flushPartialBuffer config via HOWLLog - useful under low
concurrency
Key: GERONIMO-6373
URL: https://issues.apache.org/jira/browse/GERONIMO-6373
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: transaction manager
Affects Versions: 2.2.1
Reporter: Gary Tully
Attachments: GERONIMO-6372.patch
HOWL XALogger supports flushPartialBuffers which is not configurable via
Geronimo HOWLLog. It is useful in the case of low concurrency.
It would be great to have this exposed in the HOWLLog constructor so that it
be be configured.
{code} /**
* Indicates whether LogBufferManager should flush buffers
* before they are full.
*
* pNormally, buffers are flushed to disk only when
* they become full. In lightly loaded situations,
* one or more threads may have to wait until the
* flushSleepTime expires before the buffer is written.
* In the worst case, a single thread is using the
* log, and every put() with sync requested will
* be delayed flushSleepTime ms before the buffer is
* written.
*
* pSetting flushPartialBuffers true will allow
* the LogBufferManager to flush buffers to disk
* any time the channel is not busy. This improves
* throughput in single threaded and lightly loaded
* environments.
*
* pBy default, this feature is disabled (false) to
* provide compatability with earlier versions of
* this library.
*/
private boolean flushPartialBuffers = false;{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMO-6373) Expose HOWL flushPartialBuffer config via HOWLLog - useful under low concurrency
[
https://issues.apache.org/jira/browse/GERONIMO-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks reassigned GERONIMO-6373:
--
Assignee: David Jencks
Expose HOWL flushPartialBuffer config via HOWLLog - useful under low
concurrency
Key: GERONIMO-6373
URL: https://issues.apache.org/jira/browse/GERONIMO-6373
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: transaction manager
Affects Versions: 2.2.1
Reporter: Gary Tully
Assignee: David Jencks
Attachments: GERONIMO-6372.patch
HOWL XALogger supports flushPartialBuffers which is not configurable via
Geronimo HOWLLog. It is useful in the case of low concurrency.
It would be great to have this exposed in the HOWLLog constructor so that it
be be configured.
{code} /**
* Indicates whether LogBufferManager should flush buffers
* before they are full.
*
* pNormally, buffers are flushed to disk only when
* they become full. In lightly loaded situations,
* one or more threads may have to wait until the
* flushSleepTime expires before the buffer is written.
* In the worst case, a single thread is using the
* log, and every put() with sync requested will
* be delayed flushSleepTime ms before the buffer is
* written.
*
* pSetting flushPartialBuffers true will allow
* the LogBufferManager to flush buffers to disk
* any time the channel is not busy. This improves
* throughput in single threaded and lightly loaded
* environments.
*
* pBy default, this feature is disabled (false) to
* provide compatability with earlier versions of
* this library.
*/
private boolean flushPartialBuffers = false;{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
