Re: how to apply message filters in STOMP
On 9/8/06, Dhawan, Vikram (LNG-DAY) [EMAIL PROTECTED] wrote: Hi, In a STOMP client what is the way to apply a message filter. In my Consumer code I want to accept only those messages who has a particular header value in one of the message header field. See the stomp documentation... http://incubator.apache.org/activemq/stomp.html which details all the various Stomp headers you can use. In this case add a 'selector' header (using the same syntax as JMS's SQL 92 syntax) on the SUBSCRIBE command -- James --- http://radio.weblogs.com/0112098/
Re: SSL authentication/authorization patch
starting to look into it now. thx for the patch! On 9/5/06, Sepand M [EMAIL PROTECTED] wrote: Hey guys, The patch is done. It's here: https://issues.apache.org/activemq/browse/AMQ-912 Hope you like it. It would be really great if you could give an estimate of when you will decide if it goes in or not (although I doubt you can =) ). Regards, Sepand -- Regards, Hiram Blog: http://hiramchirino.com
[jira] Work stopped: (AMQ-912) ActiveMQ support for SSL authentication and authorization
[ https://issues.apache.org/activemq/browse/AMQ-912?page=all ] Work on AMQ-912 stopped by Hiram Chirino. ActiveMQ support for SSL authentication and authorization - Key: AMQ-912 URL: https://issues.apache.org/activemq/browse/AMQ-912 Project: ActiveMQ Issue Type: Improvement Components: Test Cases, Transport Reporter: Sepand Mavandadi Assigned To: Hiram Chirino Attachments: ssl_certifiacte_auth_patch.txt, svn_diff.txt Original Estimate: 0 minutes Remaining Estimate: 0 minutes This patch adds new Transports, Brokers, and Plugins needed for authentication and authorization based on SSL certificates. It also adds a few unit tests for the mentioned classes. The new (or heavily modified) SslTransport, SslTransportServer, and SslTransportFactory classes allow for access to the underlying socket's need and want client auth settings. If a certificate is found, it is set as the transportContext of the created connection. The JaasCertificateAuthenticationBroker uses the new CertificateLoginModule to authenticate certificates (this class is abstract to allow for different backends for certificate authentication, a concrete class is TextFileCertificateLoginModule). JaasCertificateAuthenticationBroker also sets the security context's user name to that provided for the certificate by the login module. This allows for authorization using the existing authorization broker. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
RE: Issues found when load tested servicemix
Thank you Guillaume. Servicemix is working perfectly now. Regards, Ujval -Original Message- From: Guillaume Nodet [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 9:14 PM To: servicemix-dev@geronimo.apache.org Subject: Re: Issues found when load tested servicemix Note that for an InOnly exchange, the exchange should be queued twice, because the provider component has to send back a DONE status. Also, the destinationService will never change for a given exchange as it is the provider address. So in the JmsIn - JmsOut, the same exchange should be enqueued first in the queue for the provider (JmsOut), and then in the queue for the consumer (JmsIn). For the JmsIn - WSIF - JmsOut, you should see 4 calls to enqueue an exchange: 2 for the first exchange (JmsIn - WSIF) and 2 for the last one (WSIF - JmsOut). The size of the internal queue for the delivery channel (not the seda queue) is 1024, so it may be related to the behavior you experience. This would block if one of the component does not accept messages from its delivery channel or does not implement MessageExchangeListener. It seems that you are using your own components for JMS so i would suggest that you check your InJms component and make sure you inherit the MessageExchangeListener (with an empty implementation in this case, as shown in [1]. [1] http://svn.apache.org/viewvc/incubator/servicemix/trunk/servicemix-compo nents/src/main/java/org/apache/servicemix/components/jms/JmsInBinding.ja va?view=markup On 9/8/06, Ujval Mysore [EMAIL PROTECTED] wrote: I have upgraded to Servicemix 3.0 and load tested it again by deploying Servicemix on Weblogic 8.1 and Geronimo 1.0 app servers. The situation seems to be improved but the overall problem still persists. For #4 in my mail below, servicemix 2.0.2 used to get stuck for around 30 transactions. But now for Servicemix 3.0 this runs well for around 1000 transactions. I have debugged the code and found that the messages are being put in the BoundedLinkedQueue but, the work is not getting scheduled in the run() method of SedaQueue.java after around 1000 transactions. For the flow JmsIn -- JmsOut, the put() method is called only once, which is perfect, as the message exchange needs to flow thru the NMR only once from JmsIn to JmsOut. But, for the flow JmsIn -- WSIF -- JmsOut, ideally speaking the put() method has to be invoked only twice. But, the method is invoked 4 times. I checked the destination service from the message exchange in the put() method of BoundedLinkedQueue.java and run() method of 'new Work()' inner class. In both the methods, the destination service for the first two times was as expected i.e. WSIF and the JmsOut. The flow should stop here. But, put() method is called twice more, the destination service being WSIF. And run() method called once more and the destionation service being WSIF again. I think because of excessive puts in the BoundedLinkedQueue, the scheduling of the work is getting affected. The servicemix.xml being: sm:container spring:id=jbi useMBeanServer=false createMBeanServer=false dumpStats=true statsInterval=10 sm:activationSpecs !-- Subscribe to a JMS destination -- sm:activationSpec componentName=inputReceiver service=my:inputReceiver destinationService=my:Inventory_EJBService sm:component bean xmlns=http://xbean.org/schemas/spring/1.0; class=com.infosys.servicemix.components.jms.JmsInWLBinding property name=queueConnFactory value=java:comp/env/infosysServicemixQCF/ property name=qu value=java:comp/env/Queue1/ /bean /sm:component /sm:activationSpec sm:activationSpec componentName=Inventory_EJBService service=my:Inventory_EJBService destinationService=my:outputSender sm:component bean xmlns=http://xbean.org/schemas/spring/1.0; class=org.apache.servicemix.components.wsif.WSIFBinding property name=definitionResource value=MultiAddition.wsdl/ /bean /sm:component /sm:activationSpec sm:activationSpec componentName=outputSender service=my:outputSender sm:component bean xmlns=http://xbean.org/schemas/spring/1.0; class=com.infosys.servicemix.components.jms.JmsOutWLBinding property name=queueConnFactory value=java:comp/env/infosysServicemixQCF/ property name=qu value=java:comp/env/Queue2/ /bean /sm:component /sm:activationSpec Thanks n Regards, Ujval Mysore -Original Message- From: Guillaume Nodet [mailto:[EMAIL PROTECTED] Sent: Monday, August 28, 2006 6:26 PM To: servicemix-dev@geronimo.apache.org Subject: Re: Issues found when load tested servicemix 30
Re: Release 3.0
On 9/7/06, Guillaume Nodet [EMAIL PROTECTED] wrote: I'd like to cut branch and start the release process for ServiceMix 3.0 tomorrow. Any objections ? None from me. Bruce -- perl -e 'print unpack(u30,D0G)[EMAIL PROTECTED]5R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' Apache Geronimo - http://geronimo.apache.org/ Apache ActiveMQ - http://incubator.apache.org/activemq/ Apache ServiceMix - http://incubator.apache.org/servicemix/ Castor - http://castor.org/
Re: [VOTE] ServiceMix 3.0-incubating
I have just fixed these missing headers. I will recut a release and start another vote. Consider this vote canceled. On 9/8/06, Hiram Chirino [EMAIL PROTECTED] wrote: It looks good but there are a few files that don't have a license header on them.. Most of them don't need a header but there are a few .java files that do seem like they need it. Here's all the files without a header: ./apache-servicemix/src/main/release/conf/keystore.jks ./apache-servicemix/src/main/release/examples/file-binding/outbox/holder.txt ./apache-servicemix/src/main/release/examples/loan-broker/build.xml ./apache-servicemix/src/main/release/examples/loan-broker/README.txt ./apache-servicemix/src/main/release/examples/loan-broker/servicemix.xml ./apache-servicemix/src/main/release/examples/loan-broker/src/sa/META-INF/DISCLAIMER.txt ./apache-servicemix/src/main/release/examples/loan-broker/src/sa/META-INF/jbi.xml ./apache-servicemix/src/main/release/examples/loan-broker/src/su/servicemix.xml ./apache-servicemix/src/main/release/examples/wsn-http-binding/src/sa/META-INF/DISCLAIMER.txt ./build/src/main/resources/META-INF/DISCLAIMER ./DISCLAIMER ./geronimo/deployer/src/resources/META-INF/DISCLAIMER ./geronimo/deployer-service/src/main/resources/META-INF/DISCLAIMER ./geronimo/servicemix/src/resources/META-INF/DISCLAIMER ./geronimo/servicemix-service/src/main/resources/META-INF/DISCLAIMER ./KEYS ./samples/servicemix-web/src/webapp/blank.html ./samples/servicemix-web/src/webapp/bullet.gif ./samples/servicemix-web/src/webapp/index.html ./samples/servicemix-web/src/webapp/mbeanDetail.jsp ./samples/servicemix-web/src/webapp/mbeans.jsp ./samples/servicemix-web/src/webapp/minus.gif ./samples/servicemix-web/src/webapp/mktree.css ./samples/servicemix-web/src/webapp/mktree.js ./samples/servicemix-web/src/webapp/plus.gif ./samples/servicemix-web/src/webapp/search.html ./samples/servicemix-web/src/webapp/style.css ./samples/ws-sec/client-basic.html ./samples/ws-sec/client-ws-sec.html ./samples/ws-sec/src/main/resources/groups.properties ./samples/ws-sec/src/main/resources/login.properties ./samples/ws-sec/src/main/resources/users.properties ./samples/wsdl-first/src/main/assembly/src.xml ./servicemix-beanflow/README.txt ./servicemix-beanflow/src/main/java/org/apache/servicemix/beanflow/annotations/package.html ./servicemix-beanflow/src/main/java/org/apache/servicemix/beanflow/package.html ./servicemix-beanflow/src/main/java/org/apache/servicemix/beanflow/support/package.html ./servicemix-beanflow/src/main/java/org/apache/servicemix/beanflow/util/package.html ./servicemix-beanflow/src/main/resources/META-INF/DISCLAIMER ./servicemix-beanflow/src/test/resources/log4j.properties ./servicemix-bpe/src/main/jbi/META-INF/DISCLAIMER ./servicemix-bpe/src/main/resources/bpeEngine.properties ./servicemix-bpe/src/main/resources/META-INF/DISCLAIMER ./servicemix-bpe/src/test/java/org/apache/servicemix/bpe/BPESpringComponentTest.java ./servicemix-bpe/src/test/resources/loanbroker/bank.wsdl ./servicemix-bpe/src/test/resources/loanbroker/creditagency.wsdl ./servicemix-bpe/src/test/resources/loanbroker/loanbroker.bpel ./servicemix-bpe/src/test/resources/loanbroker/loanbroker.wsdl ./servicemix-bpe/src/test/resources/log4j-tests.properties ./servicemix-bpe/src/test/resources/log4j.properties ./servicemix-common/src/main/java/org/apache/servicemix/common/package.html ./servicemix-common/src/main/resources/META-INF/DISCLAIMER ./servicemix-common/src/test/java/org/apache/servicemix/common/xbean/XBeanEndpoint.java ./servicemix-common/src/test/resources/log4j-tests.properties ./servicemix-common/src/test/resources/log4j.properties ./servicemix-common/src/test/resources/wsn/b-2.xsd ./servicemix-common/src/test/resources/wsn/bf-2.xsd ./servicemix-common/src/test/resources/wsn/br-2.xsd ./servicemix-common/src/test/resources/wsn/brw-2.wsdl ./servicemix-common/src/test/resources/wsn/bw-2.wsdl ./servicemix-common/src/test/resources/wsn/r-2.xsd ./servicemix-common/src/test/resources/wsn/rw-2.wsdl ./servicemix-common/src/test/resources/wsn/t-1.xsd ./servicemix-common/src/test/resources/wsn/wsn.wsdl ./servicemix-common/src/test/resources/wsn/xml.xsd ./servicemix-common/src/test/resources/xbean/xbean.properties ./servicemix-components/src/main/java/org/apache/servicemix/components/activesoap/package.html ./servicemix-components/src/main/java/org/apache/servicemix/components/cache/package.html ./servicemix-components/src/main/java/org/apache/servicemix/components/drools/package.html ./servicemix-components/src/main/java/org/apache/servicemix/components/email/package.html ./servicemix-components/src/main/java/org/apache/servicemix/components/file/package.html ./servicemix-components/src/main/java/org/apache/servicemix/components/groovy/package.html ./servicemix-components/src/main/java/org/apache/servicemix/components/http/package.html ./servicemix-components/src/main/java/org/apache/servicemix/components/jabber/package.html
[jira] Created: (SM-573) LoanBroker example occasionnally hangs
LoanBroker example occasionnally hangs -- Key: SM-573 URL: https://issues.apache.org/activemq/browse/SM-573 Project: ServiceMix Issue Type: Bug Affects Versions: 3.0-M2 Environment: Linux Reporter: Alain Knaff Often, the loan-broker example hangs. When that happens, the client (launched with ant) hangs for a while at [java] Sending request and eventually gets a javax.jms.JMSException: EDU.oswego.cs.dl.util.concurrent.TimeoutException When that happens, nothing at all is logged on the server (launched with servicemix.xml). Once in that state, it stays like that (until restarted). If the server is good at first, it often gets into that state at the second request. Occasionnally, 1 request in 2 succeed (i.e. first succeeds, second hangs, third succeeds, fourth hangs...) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Changing the name of the ServiceMix project at the Codehaus
On 9/6/06, Dain Sundstrom [EMAIL PROTECTED] wrote: If that is a problem, maybe we can just use Mixins or Smixins. How about choosing a name that completely separates the two project? How about Riviera? Bruce -- perl -e 'print unpack(u30,D0G)[EMAIL PROTECTED]5R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' Apache Geronimo - http://geronimo.apache.org/ Apache ActiveMQ - http://incubator.apache.org/activemq/ Apache ServiceMix - http://incubator.apache.org/servicemix/ Castor - http://castor.org/
Re: Missing heqders (Was: [VOTE] ServiceMix 3.0-incubating)
cd to the root of the source folder you want to search.
put the following into a findunlicensed.pl file, chmod a+x it and then run:
find . -name .svn -prune -o -type f -print0 | xargs -0 ./findunlicensed.pl
#!/usr/bin/perl
#
# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements. See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the License); you may not use this file except in compliance with
# the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an AS IS BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
#===
# Change the old license header to remove the copyright ASF line
# and replace it with the new Licensed under the ... text.
# Note that this should not be applied to the collective copyright
# in, for example, a README file that describes the work as a whole.
#===
#
# Usage: copy2license.pl *.java
#or
# find . -name .svn -prune -o -type f -print0 | xargs -0 findunlicensed.pl
#
sub ShowUsage {
print qq!
Usage: $0 file [ file ... ]
where:
file = a file in which to substitute license text
!;
}
#===
# ensure proper usage
if (scalar @ARGV 1) {
ShowUsage();
exit;
}
undef $/; # slurp the whole file
# process each filename that was supplied
while ($filename = shift) {
open(INFILE, $filename) || die (Cannot read from $filename, $!\n);
$wholething = INFILE;
close INFILE;
if (! ($wholething =~ /License/m) ) {
print $filename\n;
}
}
$/ = \n; # reset the input record separator
exit 0;
On 9/9/06, Guillaume Nodet [EMAIL PROTECTED] wrote:
What' s your magic command ?
On 9/8/06, Hiram Chirino [EMAIL PROTECTED] wrote:
It looks good but there are a few files that don't have a license
header on them.. Most of them don't need a header but there are a few
.java files that do seem like they need it. Here's all the files
without a header:
./apache-servicemix/src/main/release/conf/keystore.jks
./apache-servicemix/src/main/release/examples/file-binding/outbox/holder.txt
./apache-servicemix/src/main/release/examples/loan-broker/build.xml
./apache-servicemix/src/main/release/examples/loan-broker/README.txt
./apache-servicemix/src/main/release/examples/loan-broker/servicemix.xml
./apache-servicemix/src/main/release/examples/loan-broker/src/sa/META-INF/DISCLAIMER.txt
./apache-servicemix/src/main/release/examples/loan-broker/src/sa/META-INF/jbi.xml
./apache-servicemix/src/main/release/examples/loan-broker/src/su/servicemix.xml
./apache-servicemix/src/main/release/examples/wsn-http-binding/src/sa/META-INF/DISCLAIMER.txt
./build/src/main/resources/META-INF/DISCLAIMER
./DISCLAIMER
./geronimo/deployer/src/resources/META-INF/DISCLAIMER
./geronimo/deployer-service/src/main/resources/META-INF/DISCLAIMER
./geronimo/servicemix/src/resources/META-INF/DISCLAIMER
./geronimo/servicemix-service/src/main/resources/META-INF/DISCLAIMER
./KEYS
./samples/servicemix-web/src/webapp/blank.html
./samples/servicemix-web/src/webapp/bullet.gif
./samples/servicemix-web/src/webapp/index.html
./samples/servicemix-web/src/webapp/mbeanDetail.jsp
./samples/servicemix-web/src/webapp/mbeans.jsp
./samples/servicemix-web/src/webapp/minus.gif
./samples/servicemix-web/src/webapp/mktree.css
./samples/servicemix-web/src/webapp/mktree.js
./samples/servicemix-web/src/webapp/plus.gif
./samples/servicemix-web/src/webapp/search.html
./samples/servicemix-web/src/webapp/style.css
./samples/ws-sec/client-basic.html
./samples/ws-sec/client-ws-sec.html
./samples/ws-sec/src/main/resources/groups.properties
./samples/ws-sec/src/main/resources/login.properties
./samples/ws-sec/src/main/resources/users.properties
./samples/wsdl-first/src/main/assembly/src.xml
./servicemix-beanflow/README.txt
./servicemix-beanflow/src/main/java/org/apache/servicemix/beanflow/annotations/package.html
./servicemix-beanflow/src/main/java/org/apache/servicemix/beanflow/package.html
./servicemix-beanflow/src/main/java/org/apache/servicemix/beanflow/support/package.html
./servicemix-beanflow/src/main/java/org/apache/servicemix/beanflow/util/package.html
./servicemix-beanflow/src/main/resources/META-INF/DISCLAIMER
./servicemix-beanflow/src/test/resources/log4j.properties
./servicemix-bpe/src/main/jbi/META-INF/DISCLAIMER
./servicemix-bpe/src/main/resources/bpeEngine.properties
Re: Changing the name of the ServiceMix project at the Codehaus
I would prefer something more google friendly ... I like smixins which keep a light tie to ServiceMix. On 9/11/06, Bruce Snyder [EMAIL PROTECTED] wrote: On 9/6/06, Dain Sundstrom [EMAIL PROTECTED] wrote: If that is a problem, maybe we can just use Mixins or Smixins. How about choosing a name that completely separates the two project? How about Riviera? Bruce -- perl -e 'print unpack(u30,D0G)[EMAIL PROTECTED]5R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' Apache Geronimo - http://geronimo.apache.org/ Apache ActiveMQ - http://incubator.apache.org/activemq/ Apache ServiceMix - http://incubator.apache.org/servicemix/ Castor - http://castor.org/ -- Cheers, Guillaume Nodet
[jira] Commented: (SM-573) LoanBroker example occasionnally hangs
[ https://issues.apache.org/activemq/browse/SM-573?page=comments#action_36933 ] Guillaume Nodet commented on SM-573: This has been fixed quite recently. Could you try with the 3.0 release being currently voted (unofficial release) ? Also the No Source available is due to the fact that this example does not make use of the xml payload, only properties which is a bit in contradiction with the JBI spec, though supported somehow by Servicemix. LoanBroker example occasionnally hangs -- Key: SM-573 URL: https://issues.apache.org/activemq/browse/SM-573 Project: ServiceMix Issue Type: Bug Affects Versions: 3.0-M2 Environment: Linux Reporter: Alain Knaff Often, the loan-broker example hangs. When that happens, the client (launched with ant) hangs for a while at [java] Sending request and eventually gets a javax.jms.JMSException: EDU.oswego.cs.dl.util.concurrent.TimeoutException When that happens, nothing at all is logged on the server (launched with servicemix.xml). Once in that state, it stays like that (until restarted). If the server is good at first, it often gets into that state at the second request. Occasionnally, 1 request in 2 succeed (i.e. first succeeds, second hangs, third succeeds, fourth hangs...) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Changing the name of the ServiceMix project at the Codehaus
On 9/11/06, Guillaume Nodet [EMAIL PROTECTED] wrote: I would prefer something more google friendly ... I like smixins which keep a light tie to ServiceMix. I tend to agree with Terry that the name should be more professional, but I'm not going to get in the way if others like it. Think of Maven/Mojo combination - there's a clear separation (for legal purposes) and Mojo passes as a professional enough name. But I'd really like to just choose something and move on. Bruce -- perl -e 'print unpack(u30,D0G)[EMAIL PROTECTED]5R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' Apache Geronimo - http://geronimo.apache.org/ Apache ActiveMQ - http://incubator.apache.org/activemq/ Apache ServiceMix - http://incubator.apache.org/servicemix/ Castor - http://castor.org/
[jira] Closed: (SM-574) JBoss Deployer fails to deploy ServiceMix properly on startup of JBoss
[ https://issues.apache.org/activemq/browse/SM-574?page=all ]
Bruce Snyder closed SM-574.
---
Resolution: Fixed
JBoss Deployer fails to deploy ServiceMix properly on startup of JBoss
--
Key: SM-574
URL: https://issues.apache.org/activemq/browse/SM-574
Project: ServiceMix
Issue Type: Bug
Affects Versions: 3.0
Reporter: Bruce Snyder
Fix For: 3.0
Attachments: JBIService.java.diff.txt
Here are the JBoss logs that are output on startup:
{panel}
07:26:15,622 INFO [JBIContainer] ServiceMix 3.0-incubating-SNAPSHOT JBI
Container (ServiceMix) is starting
07:26:15,624 INFO [JBIContainer] For help or more informations please see:
http://incubator.apache.org/servicemix/
07:26:15,707 WARN [ManagementContext] Failed to start rmi registry: Port
already in use: 1099; nested exception is:
java.net.BindException: Address already in use
07:26:15,798 WARN [ManagementContext] Failed to start jmx connector: Cannot
bind to URL [rmi://localhost:1099/jmxrmi]:
javax.naming.CommunicationException [Root exception is
java.rmi.ConnectIOException: non-JRMP server at remote endpoint]
07:26:16,014 INFO [ComponentMBeanImpl] Initializing component:
#SubscriptionManager#
07:26:16,155 INFO [DeploymentService] Restoring service assemblies
07:26:16,270 ERROR [ClientFactory] Cound not start ClientFactory:
javax.naming.CommunicationException [Root exception is
java.io.NotSerializableException:
org.apache.servicemix.jbi.framework.ClientFactory]
07:26:16,275 INFO [JBIContainer] ServiceMix JBI Container (ServiceMix)
started
{panel}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Changing the name of the ServiceMix project at the Codehaus
I agree on the professional side, tough I' m not a native english speaker and I think I may miss lots of subtilities when choosing a name (unless one point them explicitely). On a side note, Mojo = M(aven) (P)ojo, so there is still a link to maven ... I think Riviera is a nice name, but very google unfriendly: more than 49.000.000 hits :( On 9/11/06, Bruce Snyder [EMAIL PROTECTED] wrote: On 9/11/06, Guillaume Nodet [EMAIL PROTECTED] wrote: I would prefer something more google friendly ... I like smixins which keep a light tie to ServiceMix. I tend to agree with Terry that the name should be more professional, but I'm not going to get in the way if others like it. Think of Maven/Mojo combination - there's a clear separation (for legal purposes) and Mojo passes as a professional enough name. But I'd really like to just choose something and move on. Bruce -- perl -e 'print unpack(u30,D0G)[EMAIL PROTECTED]5R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' Apache Geronimo - http://geronimo.apache.org/ Apache ActiveMQ - http://incubator.apache.org/activemq/ Apache ServiceMix - http://incubator.apache.org/servicemix/ Castor - http://castor.org/ -- Cheers, Guillaume Nodet
Re: OpenEJB 2 build failures (was Re: openejb-builder test failure) - FIXED
On 9/8/06, Jacek Laskowski [EMAIL PROTECTED] wrote: I'll give it a try and close the issue(s) as resolved with a comment how to work it out. Thanks Joe! I've been pulling my hair out wondering how to crack it. These two aforementioned issue reports pertaining to the Geronimo build on MS Windows have just been closed with 'Won't Fix' as it's not something OpenEJB (or Geronimo) can fix. o http://jira.codehaus.org/browse/OPENEJB-263 - Tests fail with 'java.net.MalformedURLException: no protocol: and' o http://jira.codehaus.org/browse/OPENEJB-262 - Tests fail with 'java.lang.NoSuchMethodException: org.openejb.deployment.DeploymentTestSuite.getName()' OpenEJB and Geronimo build just fineat last! Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Build failure on trunk. Plese help resolve this.
Hi,
I am getting a build failure on trunk. Build is failing with
compilation errors in geronimo-console-standard. If I run the
build from applications directory, all applications are building
without any problem. The failure is occurring when I run the
build from root directory. The following is the console output.
[INFO] -
---
[INFO] Building Geronimo Applications, Console :: Standard Portlets
[INFO] task-segment: [install]
[INFO] -
---
[INFO] [tools:require-java-version {execution: validate-java-version}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[WARNING] POM for 'org.apache.pluto:pluto:pom:1.0.1:compile' is invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[WARNING] POM for 'tranql:tranql:pom:1.4-SNAPSHOT:provided' is invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[WARNING] POM for 'org.apache.pluto:pluto:pom:1.0.1:compile' is invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[WARNING] POM for 'tranql:tranql:pom:1.4-SNAPSHOT:provided' is invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[INFO] [jspc:compile {execution: jspc}]
[INFO] Built File: \WEB-INF\view\welcome\welcomeHelp.jsp
[INFO] Built File: \WEB-INF\view\welcome\welcomeMaximized.jsp
[INFO] Built File: \WEB-INF\view\welcome\welcomeNormal.jsp
[INFO] Built File: \WEB-INF\view\webmanager\help.jsp
[INFO] Built File: \WEB-INF\view\webmanager\maximized.jsp
[INFO] Built File: \WEB-INF\view\webmanager\normal.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\editHTTP.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\editHTTPS.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\help.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\maximized.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\normal.jsp
[INFO] Built File: \WEB-INF\view\webaccesslogmanager\help.jsp
[INFO] Built File: \WEB-INF\view\webaccesslogmanager\view.jsp
[INFO] Built File: \WEB-INF\view\threads\list.jsp
[INFO] Built File: \WEB-INF\view\threads\monitor.jsp
[INFO] Built File: \WEB-INF\view\servermanager\help.jsp
[INFO] Built File: \WEB-INF\view\servermanager\normal.jsp
[INFO] Built File: \WEB-INF\view\servermanager\shutdown.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\addmaximized.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\addnormal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\help.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\maximized.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\normal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\addmaximized.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\addnormal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\help.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\maximized.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\normal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\addmaximized.j
sp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\addnormal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\help.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\maximized.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\normal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\addmaximized.
jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\addnormal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\help.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\maximized.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\normal.jsp
[INFO] Built File: \WEB-INF\view\repository\help.jsp
[INFO] Built File: \WEB-INF\view\repository\normal.jsp
[INFO] Built File: \WEB-INF\view\realmwizard\advanced.jsp
[INFO] Built File: \WEB-INF\view\realmwizard\configure.jsp
[INFO] Built File: \WEB-INF\view\realmwizard\edit.jsp
[INFO] Built File: \WEB-INF\view\realmwizard\list.jsp
[INFO] Built File: \WEB-INF\view\realmwizard\selectType.jsp
[INFO] Built File: \WEB-INF\view\realmwizard\showPlan.jsp
[INFO] Built File: \WEB-INF\view\realmwizard\testLogin.jsp
[INFO] Built File:
Re: [VOTE] Geronimo Development Process
[ +1] CTR with documentation guidelines Kevan Miller wrote: This is a vote to determine the development process the Geronimo community wishes to use for trunk development. If any modifications are needed for a branch development process, then a separate vote will be held. All votes are important. This is a community-wide issue. Please let your voice be heard... Choose the development process which you think will best serve the Geronimo community. I'd like to limit voting to a single process, rather than using a poll/ranking system (i.e. 1,2,3). If a clear consensus does not emerge, then we'll need to refine and hold another vote. [ ] +1 Relaxed RTC [ ] +1 RTC with Lazy Consensus [ ] +1 CTR with documentation guidelines These development processes are summarized below: 1. Relaxed RTC Geronimo follows a Review-Then-Commit (RTC) model. Patches for new function are provided by developers for review and comment by their peers. Feedback is conducted through JIRA comments. The goal of this interaction is to solicit suggestions from the community and incorporate their feedback as appropriate. In order for a patch to be accepted it requires the following: * Needs to be reviewed by committers on the project. Others may comment but their comments are not binding. The review may, but does not have to, include application and testing. The goal of the review is to understand the technical attributes of the change as well as the assess other impacts to the project as a whole. * 3 +1 votes from committers on the project with no outstanding -1 votes. * Any -1 votes need to be accompanied by a reason (the parties should then attempt to reach a mutually agreed upon solution to the issue raised). * If the issues can't be resolved then the PMC can be called upon to settle the dispute and make a recommendation. * Issues are generally of a technical nature. However, issues may include other items like usability, project cohesiveness or other issues that impact the project as a whole. The goal of these guidelines is to facilitate timely communication as well as the fostering of ideas and collaboration as well as innovation. 2. RTC with Lazy Consensus Geronimo follows a Review-Then-Commit model with Lazy consensus. Patches for new function are provided by developers for review and comment by their peers. Feedback is conducted through JIRA comments. The goal of this interaction is to solicit suggestions from the community and incorporate their feedback as appropriate. A patch is accepted if: * 3 +1 votes from committers on the project with no outstanding -1 votes and no significant, ongoing discussion * 72 hours pass with no outstanding -1 votes and no significant, ongoing discussion. A 24 hour warning should be sent to the dev list. 3. CTR with documentation guidelines Geronimo follows a Commit-Then-Review model. There should be an emphasis of community communication. Community-based policing and persuasion will be used to remedy any problem areas. Guidelines are not strict dogma -- common sense should prevail. Community communication is the key, not a process. General guidelines are: * Non-trivial changes (and certainly potentially controversial changes) should be announced on the dev list. This announcement should be well in advance of the change being committed. The community should be given the opportunity to understand and discuss the proposal. * Concurrent with the commit of a significant change, the committer should document the change on the dev list. You should describe what you are doing, describe why you are doing it, and provide an overview of how you implemented it. --kevan
Re: Build failure on trunk. Plese help resolve this.
Hi Vamsi,
I am getting the same error. Scenario is same here.
Thanks,
Lasantha Ranaweera
Vamsavardhana Reddy wrote:
Hi,
I am getting a build failure on trunk. Build is failing with
compilation errors in geronimo-console-standard. If I run the build
from applications directory, all applications are building without any
problem. The failure is occurring when I run the build from root
directory. The following is the console output.
[INFO]
-
---
[INFO] Building Geronimo Applications, Console :: Standard Portlets
[INFO]task-segment: [install]
[INFO]
-
---
[INFO] [tools:require-java-version {execution: validate-java-version}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[WARNING] POM for 'org.apache.pluto:pluto:pom:1.0.1:compile' is
invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[WARNING] POM for 'tranql:tranql:pom:1.4-SNAPSHOT:provided' is
invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[WARNING] POM for 'org.apache.pluto:pluto:pom:1.0.1:compile' is
invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[WARNING] POM for 'tranql:tranql:pom:1.4-SNAPSHOT:provided' is
invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[INFO] [jspc:compile {execution: jspc}]
[INFO] Built File: \WEB-INF\view\welcome\welcomeHelp.jsp
[INFO] Built File: \WEB-INF\view\welcome\welcomeMaximized.jsp
[INFO] Built File: \WEB-INF\view\welcome\welcomeNormal.jsp
[INFO] Built File: \WEB-INF\view\webmanager\help.jsp
[INFO] Built File: \WEB-INF\view\webmanager\maximized.jsp
[INFO] Built File: \WEB-INF\view\webmanager\normal.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\editHTTP.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\editHTTPS.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\help.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\maximized.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\normal.jsp
[INFO] Built File: \WEB-INF\view\webaccesslogmanager\help.jsp
[INFO] Built File: \WEB-INF\view\webaccesslogmanager\view.jsp
[INFO] Built File: \WEB-INF\view\threads\list.jsp
[INFO] Built File: \WEB-INF\view\threads\monitor.jsp
[INFO] Built File: \WEB-INF\view\servermanager\help.jsp
[INFO] Built File: \WEB-INF\view\servermanager\normal.jsp
[INFO] Built File: \WEB-INF\view\servermanager\shutdown.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\users\addmaximized.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\users\addnormal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\help.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\users\maximized.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\normal.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\groups\addmaximized.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\groups\addnormal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\help.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\groups\maximized.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\normal.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\addmaximized.j
sp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\addnormal.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\help.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\maximized.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\normal.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\groups\addmaximized.
jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\groups\addnormal.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\groups\error.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\groups\help.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\groups\maximized.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\groups\normal.jsp
[INFO] Built File: \WEB-INF\view\repository\help.jsp
[INFO] Built File: \WEB-INF\view\repository\normal.jsp
[INFO] Built File: \WEB-INF\view\realmwizard\advanced.jsp
[INFO] Built File: \WEB-INF\view\realmwizard\configure.jsp
[INFO] Built File: \WEB-INF\view\realmwizard\edit.jsp
[INFO] Built File: \WEB-INF\view\realmwizard\list.jsp
[INFO] Built File:
Re: Build failure on trunk. Plese help resolve this.
I started to hit this same error as I was setting up my OSX late last
week. Strangely enough, it doesn't happen on Windows!?!?
Joe
Vamsavardhana Reddy wrote:
Hi,
I am getting a build failure on trunk. Build is failing with
compilation errors in geronimo-console-standard. If I run the build
from applications directory, all applications are building without any
problem. The failure is occurring when I run the build from root
directory. The following is the console output.
[INFO]
-
---
[INFO] Building Geronimo Applications, Console :: Standard Portlets
[INFO]task-segment: [install]
[INFO]
-
---
[INFO] [tools:require-java-version {execution: validate-java-version}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[WARNING] POM for 'org.apache.pluto:pluto:pom:1.0.1:compile' is invalid.
It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[WARNING] POM for 'tranql:tranql:pom:1.4-SNAPSHOT:provided' is invalid.
It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[WARNING] POM for 'org.apache.pluto:pluto:pom:1.0.1:compile' is invalid.
It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[WARNING] POM for 'tranql:tranql:pom:1.4-SNAPSHOT:provided' is invalid.
It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[INFO] [jspc:compile {execution: jspc}]
[INFO] Built File: \WEB-INF\view\welcome\welcomeHelp.jsp
[INFO] Built File: \WEB-INF\view\welcome\welcomeMaximized.jsp
[INFO] Built File: \WEB-INF\view\welcome\welcomeNormal.jsp
[INFO] Built File: \WEB-INF\view\webmanager\help.jsp
[INFO] Built File: \WEB-INF\view\webmanager\maximized.jsp
[INFO] Built File: \WEB-INF\view\webmanager\normal.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\editHTTP.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\editHTTPS.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\help.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\maximized.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\normal.jsp
[INFO] Built File: \WEB-INF\view\webaccesslogmanager\help.jsp
[INFO] Built File: \WEB-INF\view\webaccesslogmanager\view.jsp
[INFO] Built File: \WEB-INF\view\threads\list.jsp
[INFO] Built File: \WEB-INF\view\threads\monitor.jsp
[INFO] Built File: \WEB-INF\view\servermanager\help.jsp
[INFO] Built File: \WEB-INF\view\servermanager\normal.jsp
[INFO] Built File: \WEB-INF\view\servermanager\shutdown.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\users\addmaximized.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\addnormal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\help.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\maximized.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\normal.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\groups\addmaximized.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\groups\addnormal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\help.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\groups\maximized.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\normal.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\addmaximized.j
sp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\addnormal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\help.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\maximized.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\normal.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\groups\addmaximized.
jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\groups\addnormal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\help.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\groups\maximized.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\groups\normal.jsp
[INFO] Built File: \WEB-INF\view\repository\help.jsp
[INFO] Built File: \WEB-INF\view\repository\normal.jsp
[INFO] Built File: \WEB-INF\view\realmwizard\advanced.jsp
[INFO] Built File: \WEB-INF\view\realmwizard\configure.jsp
[INFO] Built File: \WEB-INF\view\realmwizard\edit.jsp
[INFO] Built File: \WEB-INF\view\realmwizard\list.jsp
[INFO]
Re: Build failure on trunk. Plese help resolve this.
On 9/11/06, Joe Bohn [EMAIL PROTECTED] wrote:
I started to hit this same error as I was setting up my OSX late lastweek.Strangely enough, it doesn't happen on Windows!?!?
I am using Windows XP.
Vamsi
JoeVamsavardhana Reddy wrote: Hi, I am getting a build failure on trunk.Build is failing with
compilation errors in geronimo-console-standard.If I run the build from applications directory, all applications are building without any problem.The failure is occurring when I run the build from root
directory.The following is the console output. [INFO] - --- [INFO] Building Geronimo Applications, Console :: Standard Portlets
[INFO]task-segment: [install] [INFO] - --- [INFO] [tools:require-java-version {execution: validate-java-version}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [WARNING] POM for 'org.apache.pluto:pluto:pom:1.0.1:compile
' is invalid. It willbe ignored for artifact resolution. Reason: Not a v4.0.0 POM. [WARNING] POM for 'tranql:tranql:pom:1.4-SNAPSHOT:provided' is invalid. It will be ignored for artifact resolution. Reason: Not a
v4.0.0 POM. [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [WARNING] POM for 'org.apache.pluto:pluto:pom:1.0.1:compile' is invalid. It willbe ignored for artifact resolution. Reason: Not a
v4.0.0 POM. [WARNING] POM for 'tranql:tranql:pom:1.4-SNAPSHOT:provided' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. [INFO] [jspc:compile {execution: jspc}]
[INFO] Built File: \WEB-INF\view\welcome\welcomeHelp.jsp [INFO] Built File: \WEB-INF\view\welcome\welcomeMaximized.jsp [INFO] Built File: \WEB-INF\view\welcome\welcomeNormal.jsp [INFO] Built File: \WEB-INF\view\webmanager\help.jsp
[INFO] Built File: \WEB-INF\view\webmanager\maximized.jsp [INFO] Built File: \WEB-INF\view\webmanager\normal.jsp [INFO] Built File: \WEB-INF\view\webmanager\connector\editHTTP.jsp [INFO] Built File: \WEB-INF\view\webmanager\connector\editHTTPS.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\help.jsp [INFO] Built File: \WEB-INF\view\webmanager\connector\maximized.jsp [INFO] Built File: \WEB-INF\view\webmanager\connector\normal.jsp
[INFO] Built File: \WEB-INF\view\webaccesslogmanager\help.jsp [INFO] Built File: \WEB-INF\view\webaccesslogmanager\view.jsp [INFO] Built File: \WEB-INF\view\threads\list.jsp [INFO] Built File: \WEB-INF\view\threads\monitor.jsp
[INFO] Built File: \WEB-INF\view\servermanager\help.jsp [INFO] Built File: \WEB-INF\view\servermanager\normal.jsp [INFO] Built File: \WEB-INF\view\servermanager\shutdown.jsp [INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\users\addmaximized.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\addnormal.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\help.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\maximized.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\normal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\addmaximized.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\addnormal.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\help.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\maximized.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\normal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\addmaximized.j sp [INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\addnormal.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\help.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\maximized.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\normal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\addmaximized. jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\addnormal.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\help.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\maximized.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\normal.jsp
[INFO] Built File: \WEB-INF\view\repository\help.jsp [INFO] Built File: \WEB-INF\view\repository\normal.jsp [INFO] Built File: \WEB-INF\view\realmwizard\advanced.jsp [INFO] Built File: \WEB-INF\view\realmwizard\configure.jsp
[INFO] Built File: \WEB-INF\view\realmwizard\edit.jsp [INFO] Built File:
[VOTE] ServiceMix-3.0-M2-incubating (second try)
I've fixed the missing headers files that Hiram pointed out, so I'm starting a new vote. I have uploaded the 3.0-incubating release at http://people.apache.org/repo/m2-incubating-repository Distributions are available at http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/apache-servicemix/3.0-incubating/apache-servicemix-3.0-incubating.tar.gz http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/apache-servicemix/3.0-incubating/apache-servicemix-3.0-incubating.zip Please, take some time to download and review ... and vote :) -- Cheers, Guillaume Nodet
[jira] Created: (SM-571) Memory leak in DeliveryChannelImpl
Memory leak in DeliveryChannelImpl -- Key: SM-571 URL: https://issues.apache.org/activemq/browse/SM-571 Project: ServiceMix Issue Type: Bug Components: servicemix-core Affects Versions: 3.0 Reporter: Marc Tremblay Priority: Critical Attachments: patch.txt In sendSync(MessageExchange messageExchange, long timeout), MessageExchanges are put into the exchangesById Map using one key, but removal in the finally block is using a different key. I have attached a patch that I have verified to eliminate the memory leak described above. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
magicGBall app plans
I'm trying to use the MagicGBall sample app running to test the Yoko CORBA support, and I'm a bit confused by what I'm seeing in the trunk source tree. In the 1.1.1 tree, the magicGBall sample was a single module, and it also included a pair of plan files in the source tree for deploying this app with or without transport-level security. In the 1.2 tree, the m2 build has split this into 4 modules, and the plan files don't seem to exist any more. Are the missing plan files just an omission from the restructure, or has some other mechanism replaced these plans? Other samples (e.g. the welcome app) seem to have plans that have gone missing in action. Rick
Long path problem on windows
I have a quick question. We have seen build failures on windows due to long path problem. Has anyone come across problems at runtime due to long path? Thanks, Vamsi
Re: Build failure on trunk. Plese help resolve this.
On 9/11/06, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: Hi, I am getting a build failure on trunk. Build is failing with compilation errors in geronimo-console-standard. If I run the build from applications directory, all applications are building without any problem. The failure is occurring when I run the build from root directory. The following is the console output. Can't be! Today is my first day when I could happily build OpenEJB 2.2-SNAPSHOT and Geronimo 1.2-SNAPSHOT and everything went so smooth. I work with Cygwin on MS Windows (had to uninstall TortoiseSVN as it gave me a lot of troubles with bizzare permission-related problems - I'm saying this to exclude issues with your build environment). How did you build Geronimo? Did you try with an empty m2 repo? What's the path of the repo? I can see from the above console output that you run mvn install. Could you run the build again with a clean m2 repo (no spaces and short path, e.g. c:\.m2, please) and svn up and mvn clean install afterwards. It must^H^H^H^Hshould work. Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: Build failure on trunk. Plese help resolve this.
Hi Jacek, To avoid the problems due to long paths, I have shared my trunk dir and m2 repo dir so that I can map these on a network drive and use. After this, my maven.repo.local woule be M:/. and the build root will be G:\ Another thing... when I ran bootstrap, I have not used any drive mapping as mentioned above. How is it that the build is successful if I run the build from applications dir? When I run the build from root, it is failing due to applications/geronimo-console-standard. VamsiOn 9/11/06, Jacek Laskowski [EMAIL PROTECTED] wrote: On 9/11/06, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: Hi,I am getting a build failure on trunk.Build is failing with compilation errors in geronimo-console-standard.If I run the build from applications directory, all applications are building without any problem.The failure is occurring when I run the build from root directory.The following is the console output.Can't be! Today is my first day when I could happily build OpenEJB 2.2-SNAPSHOT and Geronimo 1.2-SNAPSHOT and everything went so smooth.I work with Cygwin on MS Windows (had to uninstall TortoiseSVN as itgave me a lot of troubles with bizzare permission-related problems - I'm saying this to exclude issues with your build environment).How did you build Geronimo? Did you try with an empty m2 repo? What'sthe path of the repo?I can see from the above console output that you run mvn install. Could you run the build again with a clean m2 repo (no spaces andshort path, e.g. c:\.m2, please) and svn up and mvn clean installafterwards. It must^H^H^H^Hshould work.Jacek--Jacek Laskowski http://www.laskowski.net.pl
Re: Long path problem on windows
To reproduce long path error during runtime unzip geronimo-tomcat-j2ee-1.2-SNAPSHOT-bin.zip in assemblies/target directory. Thanks Anita --- Vamsavardhana Reddy [EMAIL PROTECTED] wrote: I have a quick question. We have seen build failures on windows due to long path problem. Has anyone come across problems at runtime due to long path? Thanks, Vamsi __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: [VOTE] Geronimo Development Process
[X] +1 CTR with documentation guidelines Jacek On 9/11/06, Kevan Miller [EMAIL PROTECTED] wrote: This is a vote to determine the development process the Geronimo community wishes to use for trunk development. If any modifications are needed for a branch development process, then a separate vote will be held. All votes are important. This is a community-wide issue. Please let your voice be heard... Choose the development process which you think will best serve the Geronimo community. I'd like to limit voting to a single process, rather than using a poll/ranking system (i.e. 1,2,3). If a clear consensus does not emerge, then we'll need to refine and hold another vote. [ ] +1 Relaxed RTC [ ] +1 RTC with Lazy Consensus [ ] +1 CTR with documentation guidelines These development processes are summarized below: 1. Relaxed RTC Geronimo follows a Review-Then-Commit (RTC) model. Patches for new function are provided by developers for review and comment by their peers. Feedback is conducted through JIRA comments. The goal of this interaction is to solicit suggestions from the community and incorporate their feedback as appropriate. In order for a patch to be accepted it requires the following: * Needs to be reviewed by committers on the project. Others may comment but their comments are not binding. The review may, but does not have to, include application and testing. The goal of the review is to understand the technical attributes of the change as well as the assess other impacts to the project as a whole. * 3 +1 votes from committers on the project with no outstanding -1 votes. * Any -1 votes need to be accompanied by a reason (the parties should then attempt to reach a mutually agreed upon solution to the issue raised). * If the issues can't be resolved then the PMC can be called upon to settle the dispute and make a recommendation. * Issues are generally of a technical nature. However, issues may include other items like usability, project cohesiveness or other issues that impact the project as a whole. The goal of these guidelines is to facilitate timely communication as well as the fostering of ideas and collaboration as well as innovation. 2. RTC with Lazy Consensus Geronimo follows a Review-Then-Commit model with Lazy consensus. Patches for new function are provided by developers for review and comment by their peers. Feedback is conducted through JIRA comments. The goal of this interaction is to solicit suggestions from the community and incorporate their feedback as appropriate. A patch is accepted if: * 3 +1 votes from committers on the project with no outstanding -1 votes and no significant, ongoing discussion * 72 hours pass with no outstanding -1 votes and no significant, ongoing discussion. A 24 hour warning should be sent to the dev list. 3. CTR with documentation guidelines Geronimo follows a Commit-Then-Review model. There should be an emphasis of community communication. Community-based policing and persuasion will be used to remedy any problem areas. Guidelines are not strict dogma -- common sense should prevail. Community communication is the key, not a process. General guidelines are: * Non-trivial changes (and certainly potentially controversial changes) should be announced on the dev list. This announcement should be well in advance of the change being committed. The community should be given the opportunity to understand and discuss the proposal. * Concurrent with the commit of a significant change, the committer should document the change on the dev list. You should describe what you are doing, describe why you are doing it, and provide an overview of how you implemented it. --kevan -- Jacek Laskowski http://www.laskowski.net.pl
Re: [WELCOME] Please welcome Joe Bohn as the newest member of the Geronimo PMC
Congratulations Joe! Anita On Sep 8, 2006, at 10:51 AM, Sachin Patel wrote: The Apache Geronimo PMC would like to announce that Joe Bohn has accepted the invitation to join the Geronimo PMC. In addition to his technical contributions to Geronimo, we are extremely excited to have Joe assisting with project oversight. Please congratulate Joe! The Apache Geronimo PMC -sachin __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Long path problem on windows
On 9/11/06, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: I have a quick question. We have seen build failures on windows due to long path problem. Has anyone come across problems at runtime due to long path? Never heard of any. BTW, that'd be interesting to find out how JVM handles the long paths to load classes. Jacek -- Jacek Laskowski http://www.laskowski.net.pl
[jira] Commented: (SM-571) Memory leak in DeliveryChannelImpl
[ https://issues.apache.org/activemq/browse/SM-571?page=comments#action_36929 ] Marc Tremblay commented on SM-571: -- The code in question is on the servicemix-3.0 branch, although I have no reason to suspect that this isn't also an issue with trunk. Memory leak in DeliveryChannelImpl -- Key: SM-571 URL: https://issues.apache.org/activemq/browse/SM-571 Project: ServiceMix Issue Type: Bug Components: servicemix-core Affects Versions: 3.0 Reporter: Marc Tremblay Priority: Critical Attachments: patch.txt In sendSync(MessageExchange messageExchange, long timeout), MessageExchanges are put into the exchangesById Map using one key, but removal in the finally block is using a different key. I have attached a patch that I have verified to eliminate the memory leak described above. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SM-572) servicemix-wsn2005 always use the anonymous publisher
servicemix-wsn2005 always use the anonymous publisher - Key: SM-572 URL: https://issues.apache.org/activemq/browse/SM-572 Project: ServiceMix Issue Type: Bug Components: servicemix-wsn2005 Affects Versions: 3.0-M2 Reporter: Guillaume Nodet Assigned To: Guillaume Nodet -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] 1.1.1-rc3 (incorporates all recent comments and issues, you need to vote again)
+1 -- all looks good to me --kevan
Re: Long path problem on windows
I haven't had a problem running recently on windows due to the long path name problem (although I did in the past). However, I tend not to use very long names anyway. I know this question is about running and not building ... but I'll take the opportunity to point out one other new bit of news on the building front. I was under the impression that we couldn't exceed something in the realm of 14-15 chars before we started to hit the problem building. However, that was with the M1 build on 1.1.1 (where attempting to use a root of c:\geronimo1.1.1 was hitting the problem). With trunk and the current M2 build I can go longer that that (provided I keep the M2 repo root location fairly short and w/o spaces). I was just able to successfully build with a root of 25 chars and do not yet know what the actual limit is. Joe Vamsavardhana Reddy wrote: I have a quick question. We have seen build failures on windows due to long path problem. Has anyone come across problems at runtime due to long path? Thanks, Vamsi
[jira] Closed: (GERONIMODEVTOOLS-108) Build Error - Rev441511 - Cannot download org.apache.geronimo.st.jmxagent-1.0.0.jar
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-108?page=all ] Sachin Patel closed GERONIMODEVTOOLS-108. - Resolution: Fixed Thanks, I just fixed it before I saw this. Build Error - Rev441511 - Cannot download org.apache.geronimo.st.jmxagent-1.0.0.jar --- Key: GERONIMODEVTOOLS-108 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-108 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 1.x Environment: Clean chekout and clean .m2 repo Reporter: Donald Woods Assigned To: Sachin Patel Priority: Blocker Fix For: 1.x Attachments: Devtools-108.patch Getting download failure for dependency org.apache.geronimo.st.jmxagent-1.0.0.jar, which has been deleted from the source tree (no longer built) nut is still listed in 3 pom.xml files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMODEVTOOLS-105) Build Error - Rev441511 - Cannot download eclipse-support-1.0-SNAPSHOT.jar
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-105?page=all ]
Sachin Patel closed GERONIMODEVTOOLS-105.
-
Resolution: Fixed
fixed
Build Error - Rev441511 - Cannot download eclipse-support-1.0-SNAPSHOT.jar
--
Key: GERONIMODEVTOOLS-105
URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-105
Project: Geronimo-Devtools
Issue Type: Bug
Components: eclipse-plugin
Affects Versions: 1.x
Environment: Clean checkout and .m2 repo on SLES10 x86_64
Reporter: Donald Woods
Assigned To: Sachin Patel
Priority: Blocker
Fix For: 1.x
Attachments: Devtools-105.patch
Clean checkout of
https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/trunk
Clean .m2 repo
Building on SLES10 x86_64 w/ 1.5.0 JDK
[INFO]
[INFO] Building org.apache.geronimo.st.core
[INFO]task-segment: [install]
[INFO]
. . .
[INFO] [dependency:copy {execution: copy}]
[INFO] Configured Artifact:
org.apache.geronimo.devtools:eclipse-support:null:1.0-SNAPSHOT:jar
[DEBUG] Skipping disabled repository maven1-ibiblio
[DEBUG] Skipping disabled repository maven2-ibiblio
[DEBUG] Skipping disabled repository maven1-sppatel
[DEBUG] Skipping disabled repository central
[DEBUG] eclipse-support: using locally installed snapshot
[DEBUG] Trying repository maven2-snapshot-apache
Downloading:
http://people.apache.org/maven-snapshot-repository/org/apache/geronimo/devtools/eclipse-support/1.0-SNAPSHOT/eclipse-support-1.0-SNAPSHOT.jar
[WARNING] Unable to get resource from repository maven2-snapshot-apache
(http://people.apache.org/maven-snapshot-repository)
[DEBUG] Trying repository maven2-snapshot-codehaus
Downloading:
http://snapshots.maven.codehaus.org/maven2/org/apache/geronimo/devtools/eclipse-support/1.0-SNAPSHOT/eclipse-support-1.0-SNAPSHOT.jar
[WARNING] Unable to get resource from repository maven2-snapshot-codehaus
(http://snapshots.maven.codehaus.org/maven2)
[DEBUG] Skipping disabled repository maven1-ibiblio
[DEBUG] Skipping disabled repository maven2-ibiblio
[DEBUG] Trying repository maven1-codehaus
Downloading:
http://dist.codehaus.org//org.apache.geronimo.devtools/jars/eclipse-support-1.0-SNAPSHOT.jar
[WARNING] Unable to get resource from repository maven1-codehaus
(http://dist.codehaus.org/)
[DEBUG] Trying repository maven1-apache
Downloading:
http://people.apache.org/repository/org.apache.geronimo.devtools/jars/eclipse-support-1.0-SNAPSHOT.jar
[WARNING] Unable to get resource from repository maven1-apache
(http://people.apache.org/repository)
[DEBUG] Skipping disabled repository maven1-sppatel
[DEBUG] Skipping disabled repository central
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
GroupId: org.apache.geronimo.devtools
ArtifactId: eclipse-support
Version: 1.0-SNAPSHOT
Reason: Unable to download the artifact from any repository
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.geronimo.devtools
-DartifactId=eclipse-support \
-Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
org.apache.geronimo.devtools:eclipse-support:jar:1.0-SNAPSHOT
from the specified remote repositories:
maven1-apache (http://people.apache.org/repository),
central (http://repo1.maven.org/maven2),
maven2-snapshot-apache (http://people.apache.org/maven-snapshot-repository),
maven1-sppatel (http://people.apache.org/~sppatel/repository),
maven1-codehaus (http://dist.codehaus.org/),
maven2-snapshot-codehaus (http://snapshots.maven.codehaus.org/maven2),
maven1-ibiblio (http://people.apache.org/repo/m1-ibiblio-rsync-repository/),
maven2-ibiblio (http://people.apache.org/repo/m2-ibiblio-rsync-repository)
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to find
artifact.
. . .
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (SM-572) servicemix-wsn2005 always use the anonymous publisher
[ https://issues.apache.org/activemq/browse/SM-572?page=all ] Guillaume Nodet resolved SM-572. Fix Version/s: 3.1 3.0 Resolution: Fixed Author: gnodet Date: Mon Sep 11 05:54:00 2006 New Revision: 442200 URL: http://svn.apache.org/viewvc?view=revrev=442200 Log: SM-572: servicemix-wsn2005 always use the anonymous publisher Modified: incubator/servicemix/branches/servicemix-3.0/servicemix-wsn2005/src/main/java/org/apache/servicemix/wsn/AbstractNotificationBroker.java Author: gnodet Date: Mon Sep 11 05:56:48 2006 New Revision: 442203 URL: http://svn.apache.org/viewvc?view=revrev=442203 Log: SM-572: servicemix-wsn2005 always use the anonymous publisher Modified: incubator/servicemix/trunk/servicemix-wsn2005/src/main/java/org/apache/servicemix/wsn/AbstractNotificationBroker.java servicemix-wsn2005 always use the anonymous publisher - Key: SM-572 URL: https://issues.apache.org/activemq/browse/SM-572 Project: ServiceMix Issue Type: Bug Components: servicemix-wsn2005 Affects Versions: 3.0-M2 Reporter: Guillaume Nodet Assigned To: Guillaume Nodet Fix For: 3.1, 3.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMODEVTOOLS-106) Build Error - Rev441511 - Cannot download xmlbeans-maven-plugin-2.0.1-SNAPSHOT.jar
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-106?page=all ] Sachin Patel closed GERONIMODEVTOOLS-106. - Resolution: Fixed patch applied. Build Error - Rev441511 - Cannot download xmlbeans-maven-plugin-2.0.1-SNAPSHOT.jar -- Key: GERONIMODEVTOOLS-106 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-106 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 1.x Environment: Clean checkout and clean .m2 repo on SLES10 x86_64 Reporter: Donald Woods Assigned To: Sachin Patel Priority: Blocker Fix For: 1.x Attachments: Devtools-106.patch Eclipse-support build cannot find its specified dependency of xmlbeans-maven-plugin-2.0.1-SNAPSHOT.jar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Build failure on trunk. Plese help resolve this.
My problem has gone after I ran the bootstrap command again.
Joe Bohn wrote:
I started to hit this same error as I was setting up my OSX late last
week. Strangely enough, it doesn't happen on Windows!?!?
Joe
Vamsavardhana Reddy wrote:
Hi,
I am getting a build failure on trunk. Build is failing with
compilation errors in geronimo-console-standard. If I run the build
from applications directory, all applications are building without
any problem. The failure is occurring when I run the build from root
directory. The following is the console output.
[INFO]
-
---
[INFO] Building Geronimo Applications, Console :: Standard Portlets
[INFO]task-segment: [install]
[INFO]
-
---
[INFO] [tools:require-java-version {execution: validate-java-version}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[WARNING] POM for 'org.apache.pluto:pluto:pom:1.0.1:compile' is
invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[WARNING] POM for 'tranql:tranql:pom:1.4-SNAPSHOT:provided' is
invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[WARNING] POM for 'org.apache.pluto:pluto:pom:1.0.1:compile' is
invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[WARNING] POM for 'tranql:tranql:pom:1.4-SNAPSHOT:provided' is
invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[INFO] [jspc:compile {execution: jspc}]
[INFO] Built File: \WEB-INF\view\welcome\welcomeHelp.jsp
[INFO] Built File: \WEB-INF\view\welcome\welcomeMaximized.jsp
[INFO] Built File: \WEB-INF\view\welcome\welcomeNormal.jsp
[INFO] Built File: \WEB-INF\view\webmanager\help.jsp
[INFO] Built File: \WEB-INF\view\webmanager\maximized.jsp
[INFO] Built File: \WEB-INF\view\webmanager\normal.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\editHTTP.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\editHTTPS.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\help.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\maximized.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\normal.jsp
[INFO] Built File: \WEB-INF\view\webaccesslogmanager\help.jsp
[INFO] Built File: \WEB-INF\view\webaccesslogmanager\view.jsp
[INFO] Built File: \WEB-INF\view\threads\list.jsp
[INFO] Built File: \WEB-INF\view\threads\monitor.jsp
[INFO] Built File: \WEB-INF\view\servermanager\help.jsp
[INFO] Built File: \WEB-INF\view\servermanager\normal.jsp
[INFO] Built File: \WEB-INF\view\servermanager\shutdown.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\users\addmaximized.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\users\addnormal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\help.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\users\maximized.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\users\normal.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\groups\addmaximized.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\groups\addnormal.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\groups\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\help.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\groups\maximized.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\groups\normal.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\addmaximized.j
sp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\addnormal.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\error.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\help.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\maximized.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\normal.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\groups\addmaximized.
jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\groups\addnormal.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\groups\error.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\groups\help.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\groups\maximized.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\groups\normal.jsp
[INFO] Built File: \WEB-INF\view\repository\help.jsp
[INFO] Built File: \WEB-INF\view\repository\normal.jsp
[INFO] Built File: \WEB-INF\view\realmwizard\advanced.jsp
[INFO] Built File: \WEB-INF\view\realmwizard\configure.jsp
[INFO] Built File:
Re: [VOTE] Geronimo Development Process
On 9/11/06, Kevan Miller [EMAIL PROTECTED] wrote: [ ] +1 Relaxed RTC[ ] +1 RTC with Lazy Consensus[X] +1 CTR with documentation guidelines-- Cheers,Guillaume Nodet
Re: [VOTE] 1.1.1-rc3 (incorporates all recent comments and issues, you need to vote again)
It looks like the problem is worse than I thought with the zero length DTDs. They are also still present in the binary images. Looks like I have to change my vote to -1. The truly evil could construe this as Not only did you ship the Sun DTD, but you altered the content and removed the copyright. :-) Joe Joe Bohn wrote: Looks good to me. +1. I did notice that there are still the 0 length DTDs (and some other 0 length items) in the full source distribution. I'm not sure if this is something that we need to be concerned about or not. They have been removed from the schema src. Joe Matt Hogstrom wrote: I have incorporated the latest feedback on 1.1.1-rc2. Items that were identified as issues included: * 0 length files in the modules/j2ee-schema/src/j2ee*schema directories. I have removed the those directories. The remaining directories are still intact. * Updated the RELEASE-NOTES-1.1.1.txt file to clarify the installation of the console for J2EE certified versions of the server. * Released Open EJB 2.1.1 so it is available online for normal builds. These binaries are not included in this rc3 for that reason. * Changed the Specs and Schema to use -rc3 in their suffix to ensure that the correct files are available. SVN has been updated with this version number for the specs and schema so you can checkout and build for yourself. Otherwise, one can download the appropriate files and place them in their local repository (do not rename these files...use them as is). There have been no other comments on the RC2 thread so I am resetting the vote and will ask for your input for hopefully the last time. This vote will conclude at 0600 ET on Tuesday September 12th. This vote supersedes the previous RC1 and RC2 votes; you need to vote again. Please remember that only PMC votes are binding but we need all feedback we can get to ensure there are no significant unknowns. Here is the list of artifacts: *Schemas* http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-schema- j2ee_1.4-1.0-rc3-src.jar http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-schema- j2ee_1.4-1.0-rc3.jar *Specifications* http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-j2ee- jacc_1.0_spec-1.1.1-rc3.jar *Source* http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-1.1.1-rc3- src.tar.gz http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-1.1.1-rc3-src.zip *Distributions* http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-jetty- j2ee-1.1.1-rc3.tar.gz http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-jetty- j2ee-1.1.1-rc3.zip http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-jetty- minimal-1.1.1-rc3.tar.gz http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-jetty- minimal-1.1.1-rc3.zip http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-tomcat- j2ee-1.1.1-rc3.tar.gz http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-tomcat- j2ee-1.1.1-rc3.zip http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-tomcat- minimal-1.1.1-rc3.tar.gz http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-tomcat- minimal-1.1.1-rc3.zip Note: These artifacts are uploading at the time I am sending this e- mail. They may not be available for a few hours depending on the upload speed.
[jira] Closed: (GERONIMODEVTOOLS-108) Build Error - Rev441511 - Cannot download org.apache.geronimo.st.jmxagent-1.0.0.jar
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-108?page=all ] Sachin Patel closed GERONIMODEVTOOLS-108. - Build Error - Rev441511 - Cannot download org.apache.geronimo.st.jmxagent-1.0.0.jar --- Key: GERONIMODEVTOOLS-108 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-108 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 1.x Environment: Clean chekout and clean .m2 repo Reporter: Donald Woods Assigned To: Sachin Patel Priority: Blocker Fix For: 1.x Attachments: Devtools-108.patch Getting download failure for dependency org.apache.geronimo.st.jmxagent-1.0.0.jar, which has been deleted from the source tree (no longer built) nut is still listed in 3 pom.xml files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMODEVTOOLS-107) Invalid file name of the deployment plan for a Connector
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-107?page=all ] Sachin Patel closed GERONIMODEVTOOLS-107. - Fix Version/s: 1.x Resolution: Fixed fixed in trunk Invalid file name of the deployment plan for a Connector Key: GERONIMODEVTOOLS-107 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-107 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 1.1.0 Environment: Windows XP SP2, Sun J2RE SE 1.5.0._08, Eclipse SDK 3.2.0, Geronimo Eeclipse Plugin 1.1.x (11-Aug-2006) Reporter: Ilya Kanonirov Fix For: 1.x After creating a new connector using the Connector Project wizard, the name of module's deployment plan is geronimo-connector.xml instead of expected geronimo-ra.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Build failure on trunk. Plese help resolve this.
I have created a mavenrc_pre.bat as given in
http://cwiki.apache.org/GMOxDEV/building-apache-geronimo-with-maven-2.html
and added maven.repo.local option inside that file. I do not know
why it has not taken effect. I set maven.repo.local to M:/.
explicitly and then ran bootstrap openejb2 (do not know if this step
was required). After that a build from root was successful.
PROBLEM SOLVED :o))
Thanks,
VamsiOn 9/11/06, Lasantha Ranaweera [EMAIL PROTECTED] wrote:
My problem has gone after I ran the bootstrap command again.Joe Bohn wrote: I started to hit this same error as I was setting up my OSX late last week.Strangely enough, it doesn't happen on Windows!?!?
Joe Vamsavardhana Reddy wrote: Hi, I am getting a build failure on trunk.Build is failing with compilation errors in geronimo-console-standard.If I run the build
from applications directory, all applications are building without any problem.The failure is occurring when I run the build from root directory.The following is the console output.
[INFO] - --- [INFO] Building Geronimo Applications, Console :: Standard Portlets
[INFO]task-segment: [install] [INFO] - --- [INFO] [tools:require-java-version {execution: validate-java-version}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [WARNING] POM for 'org.apache.pluto:pluto:pom:1.0.1:compile
' is invalid. It willbe ignored for artifact resolution. Reason: Not a v4.0.0 POM. [WARNING] POM for 'tranql:tranql:pom:1.4-SNAPSHOT:provided' is invalid. It will be ignored for artifact resolution. Reason: Not a
v4.0.0 POM. [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [WARNING] POM for 'org.apache.pluto:pluto:pom:1.0.1:compile' is invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM. [WARNING] POM for 'tranql:tranql:pom:1.4-SNAPSHOT:provided' is invalid. It will be ignored for artifact resolution. Reason: Not a
v4.0.0 POM. [INFO] [jspc:compile {execution: jspc}] [INFO] Built File: \WEB-INF\view\welcome\welcomeHelp.jsp [INFO] Built File: \WEB-INF\view\welcome\welcomeMaximized.jsp [INFO] Built File: \WEB-INF\view\welcome\welcomeNormal.jsp
[INFO] Built File: \WEB-INF\view\webmanager\help.jsp [INFO] Built File: \WEB-INF\view\webmanager\maximized.jsp [INFO] Built File: \WEB-INF\view\webmanager\normal.jsp [INFO] Built File: \WEB-INF\view\webmanager\connector\editHTTP.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\editHTTPS.jsp [INFO] Built File: \WEB-INF\view\webmanager\connector\help.jsp [INFO] Built File: \WEB-INF\view\webmanager\connector\maximized.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\normal.jsp [INFO] Built File: \WEB-INF\view\webaccesslogmanager\help.jsp [INFO] Built File: \WEB-INF\view\webaccesslogmanager\view.jsp
[INFO] Built File: \WEB-INF\view\threads\list.jsp [INFO] Built File: \WEB-INF\view\threads\monitor.jsp [INFO] Built File: \WEB-INF\view\servermanager\help.jsp [INFO] Built File: \WEB-INF\view\servermanager\normal.jsp
[INFO] Built File: \WEB-INF\view\servermanager\shutdown.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\addmaximized.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\addnormal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\error.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\help.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\maximized.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\normal.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\addmaximized.jsp [INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\groups\addnormal.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\error.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\help.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\maximized.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\normal.jsp [INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\addmaximized.j sp [INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\addnormal.jsp [INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\error.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\help.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\maximized.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\normal.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\addmaximized. jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\addnormal.jsp [INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\help.jsp
Re: [VOTE] Geronimo Development Process
[ ] +1 Relaxed RTC [ ] +1 RTC with Lazy Consensus [X ] +1 CTR with documentation guidelines TTFN, -bd-
Re: [VOTE] Geronimo Development Process
[X] +1 CTR with documentation guidelines
Re: Build failure on trunk. Plese help resolve this.
Hit a new error running mvn eclipse:eclipse :o(((
[INFO] Searching repository for plugin with prefix: 'eclipse'.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] The plugin 'org.apache.maven.plugins:maven-eclipse-plugin' does not exist
or no valid version could be found
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.m
aven.plugins:maven-eclipse-plugin' does not exist or no valid version could be f
ound
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Defa
ultLifecycleExecutor.java:1281)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor
(DefaultLifecycleExecutor.java:1517)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListBy
AggregationNeeds(DefaultLifecycleExecutor.java:381)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:135)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: The p
lugin 'org.apache.maven.plugins:maven-eclipse-plugin' does not exist or no valid
version could be found
at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePl
uginVersion(DefaultPluginVersionManager.java:225)
at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePl
uginVersion(DefaultPluginVersionManager.java:87)
at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPlug
inManager.java:158)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Defa
ultLifecycleExecutor.java:1252)
... 14 more
[INFO]
[INFO] Total time: 22 seconds
[INFO] Finished at: Mon Sep 11 19:05:38 IST 2006
[INFO] Final Memory: 25M/45M
[INFO]
On 9/11/06, Lasantha Ranaweera [EMAIL PROTECTED] wrote:
My problem has gone after I ran the bootstrap command again.Joe Bohn wrote: I started to hit this same error as I was setting up my OSX late last week.Strangely enough, it doesn't happen on Windows!?!?
Joe Vamsavardhana Reddy wrote: Hi, I am getting a build failure on trunk.Build is failing with compilation errors in geronimo-console-standard.If I run the build
from applications directory, all applications are building without any problem.The failure is occurring when I run the build from root directory.The following is the console output.
[INFO] - --- [INFO] Building Geronimo Applications, Console :: Standard Portlets
[INFO]task-segment: [install] [INFO] - --- [INFO] [tools:require-java-version {execution: validate-java-version}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [WARNING] POM for 'org.apache.pluto:pluto:pom:1.0.1:compile
' is invalid. It willbe ignored for artifact resolution. Reason: Not a v4.0.0 POM. [WARNING] POM for 'tranql:tranql:pom:1.4-SNAPSHOT:provided' is invalid. It will be ignored for artifact resolution. Reason: Not a
v4.0.0 POM. [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [WARNING] POM for 'org.apache.pluto:pluto:pom:1.0.1:compile' is invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM. [WARNING] POM for 'tranql:tranql:pom:1.4-SNAPSHOT:provided' is invalid. It will be ignored for artifact resolution. Reason: Not a
v4.0.0 POM. [INFO] [jspc:compile {execution: jspc}] [INFO] Built File: \WEB-INF\view\welcome\welcomeHelp.jsp [INFO] Built File: \WEB-INF\view\welcome\welcomeMaximized.jsp [INFO] Built File: \WEB-INF\view\welcome\welcomeNormal.jsp
[INFO] Built File: \WEB-INF\view\webmanager\help.jsp [INFO] Built File: \WEB-INF\view\webmanager\maximized.jsp [INFO] Built File: \WEB-INF\view\webmanager\normal.jsp [INFO] Built File: \WEB-INF\view\webmanager\connector\editHTTP.jsp
[INFO] Built
Re: [VOTE] 1.1.1-rc3 (incorporates all recent comments and issues, you need to vote again)
Hi Matt, I was able to deploy a datasource and the testsupport/1.3 ear file. +1 -bd- On Sep 9, 2006, at 2:58 AM, Matt Hogstrom wrote: I have incorporated the latest feedback on 1.1.1-rc2. Items that were identified as issues included: * 0 length files in the modules/j2ee-schema/src/j2ee*schema directories. I have removed the those directories. The remaining directories are still intact. * Updated the RELEASE-NOTES-1.1.1.txt file to clarify the installation of the console for J2EE certified versions of the server. * Released Open EJB 2.1.1 so it is available online for normal builds. These binaries are not included in this rc3 for that reason. * Changed the Specs and Schema to use -rc3 in their suffix to ensure that the correct files are available. SVN has been updated with this version number for the specs and schema so you can checkout and build for yourself. Otherwise, one can download the appropriate files and place them in their local repository (do not rename these files...use them as is). There have been no other comments on the RC2 thread so I am resetting the vote and will ask for your input for hopefully the last time. This vote will conclude at 0600 ET on Tuesday September 12th. This vote supersedes the previous RC1 and RC2 votes; you need to vote again. Please remember that only PMC votes are binding but we need all feedback we can get to ensure there are no significant unknowns. Here is the list of artifacts: *Schemas* http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-schema- j2ee_1.4-1.0-rc3-src.jar http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-schema- j2ee_1.4-1.0-rc3.jar *Specifications* http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-j2ee- jacc_1.0_spec-1.1.1-rc3.jar *Source* http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-1.1.1-rc3- src.tar.gz http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-1.1.1-rc3- src.zip *Distributions* http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-jetty- j2ee-1.1.1-rc3.tar.gz http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-jetty- j2ee-1.1.1-rc3.zip http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-jetty- minimal-1.1.1-rc3.tar.gz http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-jetty- minimal-1.1.1-rc3.zip http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-tomcat- j2ee-1.1.1-rc3.tar.gz http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-tomcat- j2ee-1.1.1-rc3.zip http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-tomcat- minimal-1.1.1-rc3.tar.gz http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-tomcat- minimal-1.1.1-rc3.zip Note: These artifacts are uploading at the time I am sending this e- mail. They may not be available for a few hours depending on the upload speed.
Re: [VOTE] 1.1.1-rc3 (incorporates all recent comments and issues, you need to vote again)
I think I'm having a John Kerry moment. :-) On further reflection, I'd like to change my vote back to a +1. My rationale earlier was that if it stopped us on rc2 then it should also stop us on rc3. However, I don't believe that this issue alone would have held up rc2 and it should not hold up rc3. We have removed the copyright protected Sun content from distribution. IANAL, but I would assume simply shipping the empty named files is not an exposure. Joe Joe Bohn wrote: It looks like the problem is worse than I thought with the zero length DTDs. They are also still present in the binary images. Looks like I have to change my vote to -1. The truly evil could construe this as Not only did you ship the Sun DTD, but you altered the content and removed the copyright. :-) Joe Joe Bohn wrote: Looks good to me. +1. I did notice that there are still the 0 length DTDs (and some other 0 length items) in the full source distribution. I'm not sure if this is something that we need to be concerned about or not. They have been removed from the schema src. Joe Matt Hogstrom wrote: I have incorporated the latest feedback on 1.1.1-rc2. Items that were identified as issues included: * 0 length files in the modules/j2ee-schema/src/j2ee*schema directories. I have removed the those directories. The remaining directories are still intact. * Updated the RELEASE-NOTES-1.1.1.txt file to clarify the installation of the console for J2EE certified versions of the server. * Released Open EJB 2.1.1 so it is available online for normal builds. These binaries are not included in this rc3 for that reason. * Changed the Specs and Schema to use -rc3 in their suffix to ensure that the correct files are available. SVN has been updated with this version number for the specs and schema so you can checkout and build for yourself. Otherwise, one can download the appropriate files and place them in their local repository (do not rename these files...use them as is). There have been no other comments on the RC2 thread so I am resetting the vote and will ask for your input for hopefully the last time. This vote will conclude at 0600 ET on Tuesday September 12th. This vote supersedes the previous RC1 and RC2 votes; you need to vote again. Please remember that only PMC votes are binding but we need all feedback we can get to ensure there are no significant unknowns. Here is the list of artifacts: *Schemas* http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-schema- j2ee_1.4-1.0-rc3-src.jar http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-schema- j2ee_1.4-1.0-rc3.jar *Specifications* http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-j2ee- jacc_1.0_spec-1.1.1-rc3.jar *Source* http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-1.1.1-rc3- src.tar.gz http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-1.1.1-rc3-src.zip *Distributions* http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-jetty- j2ee-1.1.1-rc3.tar.gz http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-jetty- j2ee-1.1.1-rc3.zip http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-jetty- minimal-1.1.1-rc3.tar.gz http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-jetty- minimal-1.1.1-rc3.zip http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-tomcat- j2ee-1.1.1-rc3.tar.gz http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-tomcat- j2ee-1.1.1-rc3.zip http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-tomcat- minimal-1.1.1-rc3.tar.gz http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-tomcat- minimal-1.1.1-rc3.zip Note: These artifacts are uploading at the time I am sending this e- mail. They may not be available for a few hours depending on the upload speed.
Re: [VOTE] Geronimo Development Process
[ X ] +1 CTR with documentation guidelines
[jira] Commented: (GERONIMO-2380) Keystores portlet - Form field validation using javascript
[ http://issues.apache.org/jira/browse/GERONIMO-2380?page=comments#action_12433858 ] Paul McMahan commented on GERONIMO-2380: Vamsi, thanks for responding to my comments. Despite my concerns I think the patch is progress so +1 Keystores portlet - Form field validation using javascript -- Key: GERONIMO-2380 URL: http://issues.apache.org/jira/browse/GERONIMO-2380 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 1.1.1 Environment: Win XP, G 1.1.1-rc1 Reporter: Vamsavardhana Reddy Fix For: 1.2, 1.1.x, 1.1.2 Attachments: GERONIMO-2380.patch Forms in Keystores portlet could use field validation using javascript to check for empty strings and non numerical values before posting the data to the server. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Geronimo Development Process
[X] +1 CTR with documentation guidelines We'll have to work extra hard to ensure that we hold each other to the communication standard ... but I think if we are diligent then this makes the most sense. If the change is approved, I also recommend that we hold a public review of how we feel it is working after some reasonable amount of time (perhaps 2-3 months) to ensure that we're not drifting back into old habits. Joe Kevan Miller wrote: This is a vote to determine the development process the Geronimo community wishes to use for trunk development. If any modifications are needed for a branch development process, then a separate vote will be held. All votes are important. This is a community-wide issue. Please let your voice be heard... Choose the development process which you think will best serve the Geronimo community. I'd like to limit voting to a single process, rather than using a poll/ranking system (i.e. 1,2,3). If a clear consensus does not emerge, then we'll need to refine and hold another vote. [ ] +1 Relaxed RTC [ ] +1 RTC with Lazy Consensus [ ] +1 CTR with documentation guidelines These development processes are summarized below: 1. Relaxed RTC Geronimo follows a Review-Then-Commit (RTC) model. Patches for new function are provided by developers for review and comment by their peers. Feedback is conducted through JIRA comments. The goal of this interaction is to solicit suggestions from the community and incorporate their feedback as appropriate. In order for a patch to be accepted it requires the following: * Needs to be reviewed by committers on the project. Others may comment but their comments are not binding. The review may, but does not have to, include application and testing. The goal of the review is to understand the technical attributes of the change as well as the assess other impacts to the project as a whole. * 3 +1 votes from committers on the project with no outstanding -1 votes. * Any -1 votes need to be accompanied by a reason (the parties should then attempt to reach a mutually agreed upon solution to the issue raised). * If the issues can't be resolved then the PMC can be called upon to settle the dispute and make a recommendation. * Issues are generally of a technical nature. However, issues may include other items like usability, project cohesiveness or other issues that impact the project as a whole. The goal of these guidelines is to facilitate timely communication as well as the fostering of ideas and collaboration as well as innovation. 2. RTC with Lazy Consensus Geronimo follows a Review-Then-Commit model with Lazy consensus. Patches for new function are provided by developers for review and comment by their peers. Feedback is conducted through JIRA comments. The goal of this interaction is to solicit suggestions from the community and incorporate their feedback as appropriate. A patch is accepted if: * 3 +1 votes from committers on the project with no outstanding -1 votes and no significant, ongoing discussion * 72 hours pass with no outstanding -1 votes and no significant, ongoing discussion. A 24 hour warning should be sent to the dev list. 3. CTR with documentation guidelines Geronimo follows a Commit-Then-Review model. There should be an emphasis of community communication. Community-based policing and persuasion will be used to remedy any problem areas. Guidelines are not strict dogma -- common sense should prevail. Community communication is the key, not a process. General guidelines are: * Non-trivial changes (and certainly potentially controversial changes) should be announced on the dev list. This announcement should be well in advance of the change being committed. The community should be given the opportunity to understand and discuss the proposal. * Concurrent with the commit of a significant change, the committer should document the change on the dev list. You should describe what you are doing, describe why you are doing it, and provide an overview of how you implemented it. --kevan
[ANNOUNCE] Welcome Hernan Cunico as the newest member of the Geronimo PMC
All, The Geronimo PMC is pleased to welcome Hernan Cunico as the newest member of the Geronimo PMC. We're very happy to have Hernan joining us to help with the oversight of the Geronimo project. Well done, Hernan! The Apache Geronimo PMC --kevan
Re: [VOTE] 1.1.1-rc3 (incorporates all recent comments and issues, you need to vote again)
Joe, et al, I have to respin to create the final binaries. I will ensure that the 0 length files are gone. I'd rather not do an rc4 for this issue. If anyone feels that we must please speak up. Otherwise, I'll fix this cosmetic problem during the final build. Thanks Matt On Sep 11, 2006, at 9:55 AM, Joe Bohn wrote: I think I'm having a John Kerry moment. :-) On further reflection, I'd like to change my vote back to a +1. My rationale earlier was that if it stopped us on rc2 then it should also stop us on rc3. However, I don't believe that this issue alone would have held up rc2 and it should not hold up rc3. We have removed the copyright protected Sun content from distribution. IANAL, but I would assume simply shipping the empty named files is not an exposure. Joe Joe Bohn wrote: It looks like the problem is worse than I thought with the zero length DTDs. They are also still present in the binary images. Looks like I have to change my vote to -1. The truly evil could construe this as Not only did you ship the Sun DTD, but you altered the content and removed the copyright. :-) Joe Joe Bohn wrote: Looks good to me. +1. I did notice that there are still the 0 length DTDs (and some other 0 length items) in the full source distribution. I'm not sure if this is something that we need to be concerned about or not. They have been removed from the schema src. Joe Matt Hogstrom wrote: I have incorporated the latest feedback on 1.1.1-rc2. Items that were identified as issues included: * 0 length files in the modules/j2ee-schema/src/j2ee*schema directories. I have removed the those directories. The remaining directories are still intact. * Updated the RELEASE-NOTES-1.1.1.txt file to clarify the installation of the console for J2EE certified versions of the server. * Released Open EJB 2.1.1 so it is available online for normal builds. These binaries are not included in this rc3 for that reason. * Changed the Specs and Schema to use -rc3 in their suffix to ensure that the correct files are available. SVN has been updated with this version number for the specs and schema so you can checkout and build for yourself. Otherwise, one can download the appropriate files and place them in their local repository (do not rename these files...use them as is). There have been no other comments on the RC2 thread so I am resetting the vote and will ask for your input for hopefully the last time. This vote will conclude at 0600 ET on Tuesday September 12th. This vote supersedes the previous RC1 and RC2 votes; you need to vote again. Please remember that only PMC votes are binding but we need all feedback we can get to ensure there are no significant unknowns. Here is the list of artifacts: *Schemas* http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-schema- j2ee_1.4-1.0-rc3-src.jar http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-schema- j2ee_1.4-1.0-rc3.jar *Specifications* http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-j2ee- jacc_1.0_spec-1.1.1-rc3.jar *Source* http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-1.1.1-rc3- src.tar.gz http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-1.1.1-rc3- src.zip *Distributions* http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-jetty- j2ee-1.1.1-rc3.tar.gz http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-jetty- j2ee-1.1.1-rc3.zip http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-jetty- minimal-1.1.1-rc3.tar.gz http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-jetty- minimal-1.1.1-rc3.zip http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-tomcat- j2ee-1.1.1-rc3.tar.gz http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-tomcat- j2ee-1.1.1-rc3.zip http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-tomcat- minimal-1.1.1-rc3.tar.gz http://people.apache.org/~hogstrom/1.1.1-rc3/geronimo-tomcat- minimal-1.1.1-rc3.zip Note: These artifacts are uploading at the time I am sending this e- mail. They may not be available for a few hours depending on the upload speed. Matt Hogstrom [EMAIL PROTECTED]
[jira] Closed: (GERONIMODEVTOOLS-103) not able to get geronimo plan editor recognize openejb-jar.xml or geronimo-application.xml
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-103?page=all ] Sachin Patel closed GERONIMODEVTOOLS-103. - Fix Version/s: 1.x Resolution: Fixed Assignee: Sachin Patel not able to get geronimo plan editor recognize openejb-jar.xml or geronimo-application.xml -- Key: GERONIMODEVTOOLS-103 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-103 Project: Geronimo-Devtools Issue Type: Bug Affects Versions: 1.1.0 Environment: Eclipse 3.2 and WTP 1.5 windows XP Reporter: Lin Sun Assigned To: Sachin Patel Fix For: 1.x Attachments: devtools103.patch I still have similar prob. The MDB openejb-jar.xml plan actually contains the fully qualified tags but it cannot be opened with the geornimo plan editor. Similar with a new openejb-jar.xml file created by default using the create new ejb project wizard. Is this also some code missed from 1.0? This was working in 1.0 from what I remember. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [ANNOUNCE] Welcome Hernan Cunico as the newest member of the Geronimo PMC
Congrats Hernan. VamsiOn 9/11/06, Kevan Miller [EMAIL PROTECTED] wrote: All,The Geronimo PMC is pleased to welcome Hernan Cunico as the newestmember of the Geronimo PMC. We're very happy to have Hernan joiningus to help with the oversight of the Geronimo project.Well done, Hernan! The Apache Geronimo PMC--kevan
Re: [VOTE] 1.1.1-rc3 (incorporates all recent comments and issues, you need to vote again)
On Sep 11, 2006, at 9:55 AM, Joe Bohn wrote: I think I'm having a John Kerry moment. :-) Better than a Bush moment... :-P On further reflection, I'd like to change my vote back to a +1. My rationale earlier was that if it stopped us on rc2 then it should also stop us on rc3. However, I don't believe that this issue alone would have held up rc2 and it should not hold up rc3. We have removed the copyright protected Sun content from distribution. IANAL, but I would assume simply shipping the empty named files is not an exposure. Agreed. I saw them there, also. I'd be happy to see them go, but I don't think they're doing any harm... --kevan
Re: [ANNOUNCE] Welcome Hernan Cunico as the newest member of the Geronimo PMC
Congrats Hernan!! Paul On 9/11/06, Kevan Miller [EMAIL PROTECTED] wrote: All, The Geronimo PMC is pleased to welcome Hernan Cunico as the newest member of the Geronimo PMC. We're very happy to have Hernan joining us to help with the oversight of the Geronimo project. Well done, Hernan! The Apache Geronimo PMC --kevan
Re: Build failure on trunk. Plese help resolve this.
On 9/11/06, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: Hit a new error running mvn eclipse:eclipse :o((( Welcome to the wonderful world of MS Windows annoyances ;-) I remember it once happened to me and I sorted it out deleting some dirs in m2 repo. Although I once blamed bootstrap for this I don't remember what it ended up with exactly, but I do remember we agreed it was not bootstrap. Anyway, delete m2 plugins (C:\.m2\org\apache\maven\plugins) from your local m2 repo and give it a shot again. It should work. Search the archives for some explanations and let us know how it gets sorted out. Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: [ANNOUNCE] Welcome Hernan Cunico as the newest member of the Geronimo PMC
Well done, indeed! Congratulations. Kevan Miller wrote: All, The Geronimo PMC is pleased to welcome Hernan Cunico as the newest member of the Geronimo PMC. We're very happy to have Hernan joining us to help with the oversight of the Geronimo project. Well done, Hernan! The Apache Geronimo PMC --kevan
[ANNOUNCE] Welcome Rick McGuire as the newest member of the Geronimo PMC
All, The Geronimo PMC is pleased to welcome Rick McGuire as the newest member of the Geronimo PMC. We're very happy to have Rick joining us to help with the oversight of the Geronimo project. Lets give a round of applause for Rick. Well done, Rick! The Apache Geronimo PMC Jeff
Re: [ANNOUNCE] Welcome Rick McGuire as the newest member of the Geronimo PMC
Lots of good news today. Congrats Rick! Paul On 9/11/06, Jeff Genender [EMAIL PROTECTED] wrote: All, The Geronimo PMC is pleased to welcome Rick McGuire as the newest member of the Geronimo PMC. We're very happy to have Rick joining us to help with the oversight of the Geronimo project. Lets give a round of applause for Rick. Well done, Rick! The Apache Geronimo PMC Jeff
[DISCUSS] 1.2 Release Manager
Folks, Dain has volunteered to be the 1.2 release manager and Alan has also volunteered to be the co-pilot. I have not seen a formal discussion or vote on this. I don't know that we have a policy on this so I'm starting the discuss thread. At some point in the past Aaron volunteered to do 1.2 as well but I don't recall closure on his volunteering. Also, note that only PMC members have binding votes on the release of Apache software. Matt Hogstrom [EMAIL PROTECTED]
Re: [ANNOUNCE] Welcome Hernan Cunico as the newest member of the Geronimo PMC
Congrats Hernan! Kevan Miller wrote: All, The Geronimo PMC is pleased to welcome Hernan Cunico as the newest member of the Geronimo PMC. We're very happy to have Hernan joining us to help with the oversight of the Geronimo project. Well done, Hernan! The Apache Geronimo PMC --kevan
Re: [DISCUSS] 1.2 Release Manager
I think it's important that we agree on the release manager. Dain and Alan are more than welcome to take this on as far as I'm concerned. Thanks, Aaron On 9/11/06, Matt Hogstrom [EMAIL PROTECTED] wrote: Folks, Dain has volunteered to be the 1.2 release manager and Alan has also volunteered to be the co-pilot. I have not seen a formal discussion or vote on this. I don't know that we have a policy on this so I'm starting the discuss thread. At some point in the past Aaron volunteered to do 1.2 as well but I don't recall closure on his volunteering. Also, note that only PMC members have binding votes on the release of Apache software. Matt Hogstrom [EMAIL PROTECTED]
Re: [ANNOUNCE] Welcome Rick McGuire as the newest member of the Geronimo PMC
Congrats Rick. VamsiOn 9/11/06, Jeff Genender [EMAIL PROTECTED] wrote: All,The Geronimo PMC is pleased to welcome Rick McGuire as the newest memberof the Geronimo PMC. We're very happy to have Rick joining us to helpwith the oversight of the Geronimo project.Lets give a round of applause for Rick.Well done, Rick!The Apache Geronimo PMCJeff
Re: [ANNOUNCE] Welcome Rick McGuire as the newest member of the Geronimo PMC
Congrats Rick! Jeff Genender wrote: All, The Geronimo PMC is pleased to welcome Rick McGuire as the newest member of the Geronimo PMC. We're very happy to have Rick joining us to help with the oversight of the Geronimo project. Lets give a round of applause for Rick. Well done, Rick! The Apache Geronimo PMC Jeff
Re: [Poll] Next release?
I'm gonna cheat a bit as I think that both release date and feature set are equally important and one affects the other. Certification however is a strong 1 What do you mean by release name, _numbering_ ? [2] Release Date [2] Feature Set [3] Release Name [1] Certification Cheers! Hernan Dain Sundstrom wrote: In an attempt to quantify our expectation about the next release from trunk, please rank the following items in importance to you: [ ] Release Date [ ] Feature Set [ ] Release Name [ ] Certification
Re: [DISCUSS] 1.2 Release Manager
Dain and Alan would be great. Jeff Matt Hogstrom wrote: Folks, Dain has volunteered to be the 1.2 release manager and Alan has also volunteered to be the co-pilot. I have not seen a formal discussion or vote on this. I don't know that we have a policy on this so I'm starting the discuss thread. At some point in the past Aaron volunteered to do 1.2 as well but I don't recall closure on his volunteering. Also, note that only PMC members have binding votes on the release of Apache software. Matt Hogstrom [EMAIL PROTECTED]
Re: [DISCUSS] 1.2 Release Manager
Yup, Dain and Alan would be great. Do you guys know what are you actually getting into !? ;-) Cheers! Hernan Matt Hogstrom wrote: Folks, Dain has volunteered to be the 1.2 release manager and Alan has also volunteered to be the co-pilot. I have not seen a formal discussion or vote on this. I don't know that we have a policy on this so I'm starting the discuss thread. At some point in the past Aaron volunteered to do 1.2 as well but I don't recall closure on his volunteering. Also, note that only PMC members have binding votes on the release of Apache software. Matt Hogstrom [EMAIL PROTECTED]
Re: Build failure on trunk. Plese help resolve this.
Jacek, I have deleted the plugins directory and reran mvn eclipse:eclipse . Looks like it is working. Will update if it fails. Thanks, VamsiOn 9/11/06, Jacek Laskowski [EMAIL PROTECTED] wrote: On 9/11/06, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: Hit a new error running mvn eclipse:eclipse :o(((Welcome to the wonderful world of MS Windows annoyances ;-) I remember it once happened to me and I sorted it out deleting somedirs in m2 repo. Although I once blamed bootstrap for this I don'tremember what it ended up with exactly, but I do remember we agreed it was not bootstrap.Anyway, delete m2 plugins (C:\.m2\org\apache\maven\plugins) from yourlocal m2 repo and give it a shot again. It should work. Search thearchives for some explanations and let us know how it gets sorted out. Jacek--Jacek Laskowskihttp://www.laskowski.net.pl
Re: [ANNOUNCE] Welcome Hernan Cunico as the newest member of the Geronimo PMC
Congratulations !On 9/11/06, Kevan Miller [EMAIL PROTECTED] wrote: All,The Geronimo PMC is pleased to welcome Hernan Cunico as the newestmember of the Geronimo PMC. We're very happy to have Hernan joiningus to help with the oversight of the Geronimo project.Well done, Hernan! The Apache Geronimo PMC--kevan-- Cheers,Guillaume Nodet
Re: [VOTE] Geronimo Development Process
[ ] +1 Relaxed RTC [ ] +1 RTC with Lazy Consensus [X] +1 CTR with documentation guidelines Cheers! Hernan Kevan Miller wrote: This is a vote to determine the development process the Geronimo community wishes to use for trunk development. If any modifications are needed for a branch development process, then a separate vote will be held. All votes are important. This is a community-wide issue. Please let your voice be heard... Choose the development process which you think will best serve the Geronimo community. I'd like to limit voting to a single process, rather than using a poll/ranking system (i.e. 1,2,3). If a clear consensus does not emerge, then we'll need to refine and hold another vote. [ ] +1 Relaxed RTC [ ] +1 RTC with Lazy Consensus [ ] +1 CTR with documentation guidelines These development processes are summarized below: 1. Relaxed RTC Geronimo follows a Review-Then-Commit (RTC) model. Patches for new function are provided by developers for review and comment by their peers. Feedback is conducted through JIRA comments. The goal of this interaction is to solicit suggestions from the community and incorporate their feedback as appropriate. In order for a patch to be accepted it requires the following: * Needs to be reviewed by committers on the project. Others may comment but their comments are not binding. The review may, but does not have to, include application and testing. The goal of the review is to understand the technical attributes of the change as well as the assess other impacts to the project as a whole. * 3 +1 votes from committers on the project with no outstanding -1 votes. * Any -1 votes need to be accompanied by a reason (the parties should then attempt to reach a mutually agreed upon solution to the issue raised). * If the issues can't be resolved then the PMC can be called upon to settle the dispute and make a recommendation. * Issues are generally of a technical nature. However, issues may include other items like usability, project cohesiveness or other issues that impact the project as a whole. The goal of these guidelines is to facilitate timely communication as well as the fostering of ideas and collaboration as well as innovation. 2. RTC with Lazy Consensus Geronimo follows a Review-Then-Commit model with Lazy consensus. Patches for new function are provided by developers for review and comment by their peers. Feedback is conducted through JIRA comments. The goal of this interaction is to solicit suggestions from the community and incorporate their feedback as appropriate. A patch is accepted if: * 3 +1 votes from committers on the project with no outstanding -1 votes and no significant, ongoing discussion * 72 hours pass with no outstanding -1 votes and no significant, ongoing discussion. A 24 hour warning should be sent to the dev list. 3. CTR with documentation guidelines Geronimo follows a Commit-Then-Review model. There should be an emphasis of community communication. Community-based policing and persuasion will be used to remedy any problem areas. Guidelines are not strict dogma -- common sense should prevail. Community communication is the key, not a process. General guidelines are: * Non-trivial changes (and certainly potentially controversial changes) should be announced on the dev list. This announcement should be well in advance of the change being committed. The community should be given the opportunity to understand and discuss the proposal. * Concurrent with the commit of a significant change, the committer should document the change on the dev list. You should describe what you are doing, describe why you are doing it, and provide an overview of how you implemented it. --kevan
Re: [ANNOUNCE] Welcome Rick McGuire as the newest member of the Geronimo PMC
Congratulations Rick !On 9/11/06, Jeff Genender [EMAIL PROTECTED] wrote: All,The Geronimo PMC is pleased to welcome Rick McGuire as the newest memberof the Geronimo PMC. We're very happy to have Rick joining us to helpwith the oversight of the Geronimo project.Lets give a round of applause for Rick.Well done, Rick!The Apache Geronimo PMCJeff-- Cheers,Guillaume Nodet
Re: [DISCUSS] 1.2 Release Manager
Slet's not discuss responsibility until we have their buy in :) On Sep 11, 2006, at 10:36 AM, Hernan Cunico wrote: Yup, Dain and Alan would be great. Do you guys know what are you actually getting into !? ;-) Cheers! Hernan Matt Hogstrom wrote: Folks, Dain has volunteered to be the 1.2 release manager and Alan has also volunteered to be the co-pilot. I have not seen a formal discussion or vote on this. I don't know that we have a policy on this so I'm starting the discuss thread. At some point in the past Aaron volunteered to do 1.2 as well but I don't recall closure on his volunteering. Also, note that only PMC members have binding votes on the release of Apache software. Matt Hogstrom [EMAIL PROTECTED] Matt Hogstrom [EMAIL PROTECTED]
Some JIRA's with patches waiting for review
The following are some of the JIRA's that have patches waiting for review. I am sending this mail because these will never make into the Patches in RTC mail since it seems to pickup only those JIRA's that are categorized as Improvement. GERONIMO-2341 EditableConfigurationManager problems!!??? GERONIMO-2280 FileKeystoreInstance.getKeyManager() fails when there is more than one privatekey in the store GERONIMO-2279 FileKeyStoreInstance: Does not save keyPasswords after removing an entry GERONIMO-2278 Problems in editing Jetty SSL Connector and the edit page in Geronimo Console GERONIMO-2274 realm-principal does not work in web app security GERONIMO-2271 Security Realm deployed as part of a web app listed as Serverwide GERONIMO-2294 In security realm with multiple login modules, anything after the first is ignored Thanks, Vamsi
Re: Build failure on trunk. Plese help resolve this.
On 9/11/06, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: Jacek, I have deleted the plugins directory and reran mvn eclipse:eclipse . Looks like it is working. Will update if it fails. Let's hunt down the bug and fix it. We, Windowsian, need to help each other before these MS Windows annoyances spread around and won't let us build the server(s) anymore. If you find some time, could you please rerun what you've done so far when you run across the build failures and verify it was (or was not) bootstrap who messed up the m2 plugins? I'd like some more evidence before drawing conclusions. I'm building Geronimo, Geronimo specs and OpenEJB manually (it's the second or third time today), so I can only confirm the respective builds work fine. Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: [ANNOUNCE] Welcome Hernan Cunico as the newest member of the Geronimo PMC
welcome!On Sep 11, 2006, at 10:08 AM, Kevan Miller wrote:All,The Geronimo PMC is pleased to welcome Hernan Cunico as the newest member of the Geronimo PMC. We're very happy to have Hernan joining us to help with the oversight of the Geronimo project.Well done, Hernan!The Apache Geronimo PMC--kevan -sachin
Re: [VOTE] Geronimo Development Process
[X] +1 CTR with documentation guidelines Kevan Miller wrote: This is a vote to determine the development process the Geronimo community wishes to use for trunk development. If any modifications are needed for a branch development process, then a separate vote will be held. All votes are important. This is a community-wide issue. Please let your voice be heard... Choose the development process which you think will best serve the Geronimo community. I'd like to limit voting to a single process, rather than using a poll/ranking system (i.e. 1,2,3). If a clear consensus does not emerge, then we'll need to refine and hold another vote. [ ] +1 Relaxed RTC [ ] +1 RTC with Lazy Consensus [ ] +1 CTR with documentation guidelines These development processes are summarized below: 1. Relaxed RTC Geronimo follows a Review-Then-Commit (RTC) model. Patches for new function are provided by developers for review and comment by their peers. Feedback is conducted through JIRA comments. The goal of this interaction is to solicit suggestions from the community and incorporate their feedback as appropriate. In order for a patch to be accepted it requires the following: * Needs to be reviewed by committers on the project. Others may comment but their comments are not binding. The review may, but does not have to, include application and testing. The goal of the review is to understand the technical attributes of the change as well as the assess other impacts to the project as a whole. * 3 +1 votes from committers on the project with no outstanding -1 votes. * Any -1 votes need to be accompanied by a reason (the parties should then attempt to reach a mutually agreed upon solution to the issue raised). * If the issues can't be resolved then the PMC can be called upon to settle the dispute and make a recommendation. * Issues are generally of a technical nature. However, issues may include other items like usability, project cohesiveness or other issues that impact the project as a whole. The goal of these guidelines is to facilitate timely communication as well as the fostering of ideas and collaboration as well as innovation. 2. RTC with Lazy Consensus Geronimo follows a Review-Then-Commit model with Lazy consensus. Patches for new function are provided by developers for review and comment by their peers. Feedback is conducted through JIRA comments. The goal of this interaction is to solicit suggestions from the community and incorporate their feedback as appropriate. A patch is accepted if: * 3 +1 votes from committers on the project with no outstanding -1 votes and no significant, ongoing discussion * 72 hours pass with no outstanding -1 votes and no significant, ongoing discussion. A 24 hour warning should be sent to the dev list. 3. CTR with documentation guidelines Geronimo follows a Commit-Then-Review model. There should be an emphasis of community communication. Community-based policing and persuasion will be used to remedy any problem areas. Guidelines are not strict dogma -- common sense should prevail. Community communication is the key, not a process. General guidelines are: * Non-trivial changes (and certainly potentially controversial changes) should be announced on the dev list. This announcement should be well in advance of the change being committed. The community should be given the opportunity to understand and discuss the proposal. * Concurrent with the commit of a significant change, the committer should document the change on the dev list. You should describe what you are doing, describe why you are doing it, and provide an overview of how you implemented it. --kevan
Re: [ANNOUNCE] Welcome Rick McGuire as the newest member of the Geronimo PMC
congratulations!On Sep 11, 2006, at 10:17 AM, Jeff Genender wrote:All,The Geronimo PMC is pleased to welcome Rick McGuire as the newest memberof the Geronimo PMC. We're very happy to have Rick joining us to helpwith the oversight of the Geronimo project. Lets give a round ofapplause for Rick.Well done, Rick!The Apache Geronimo PMCJeff -sachin
Re: [ANNOUNCE] Welcome Hernan Cunico as the newest member of the Geronimo PMC
Congratulations Hernan! Anita --- Kevan Miller [EMAIL PROTECTED] wrote: All, The Geronimo PMC is pleased to welcome Hernan Cunico as the newest member of the Geronimo PMC. We're very happy to have Hernan joining us to help with the oversight of the Geronimo project. Well done, Hernan! The Apache Geronimo PMC --kevan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: [ANNOUNCE] Welcome Rick McGuire as the newest member of the Geronimo PMC
Congratulations Rick! Anita --- Jeff Genender [EMAIL PROTECTED] wrote: All, The Geronimo PMC is pleased to welcome Rick McGuire as the newest member of the Geronimo PMC. We're very happy to have Rick joining us to help with the oversight of the Geronimo project. Lets give a round of applause for Rick. Well done, Rick! The Apache Geronimo PMC Jeff __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
[jira] Created: (GERONIMO-2393) Maven plugin is generating invalid classpath entries in classpath
Maven plugin is generating invalid classpath entries in classpath - Key: GERONIMO-2393 URL: http://issues.apache.org/jira/browse/GERONIMO-2393 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: buildsystem Affects Versions: 1.2 Environment: WinXP, G TRUNK Reporter: Vamsavardhana Reddy Fix For: 1.2 I have run mvn eclipse:eclipse. Upon importing the projects into eclipse, I am noticing the the classpath entries generated have the first letter missing. Here is an example of some classpath entries in .classpath file. classpathentry kind=var path=M2_REPO/ommons-cli/commons-cli/1.0/commons-cli-1.0.jar/ classpathentry kind=var path=M2_REPO/tax/stax-api/1.0/stax-api-1.0.jar/ classpathentry kind=var path=M2_REPO/lassworlds/classworlds/1.1-alpha-2/classworlds-1.1-alpha-2.jar/ classpathentry kind=var path=M2_REPO/rg/apache/maven/maven-repository-metadata/2.0.4/maven-repository-metadata-2.0.4.jar/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2393) Maven plugin is generating invalid classpath entries in .classpath
[ http://issues.apache.org/jira/browse/GERONIMO-2393?page=all ] Vamsavardhana Reddy updated GERONIMO-2393: -- Summary: Maven plugin is generating invalid classpath entries in .classpath (was: Maven plugin is generating invalid classpath entries in classpath) Maven plugin is generating invalid classpath entries in .classpath -- Key: GERONIMO-2393 URL: http://issues.apache.org/jira/browse/GERONIMO-2393 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: buildsystem Affects Versions: 1.2 Environment: WinXP, G TRUNK Reporter: Vamsavardhana Reddy Fix For: 1.2 I have run mvn eclipse:eclipse. Upon importing the projects into eclipse, I am noticing the the classpath entries generated have the first letter missing. Here is an example of some classpath entries in .classpath file. classpathentry kind=var path=M2_REPO/ommons-cli/commons-cli/1.0/commons-cli-1.0.jar/ classpathentry kind=var path=M2_REPO/tax/stax-api/1.0/stax-api-1.0.jar/ classpathentry kind=var path=M2_REPO/lassworlds/classworlds/1.1-alpha-2/classworlds-1.1-alpha-2.jar/ classpathentry kind=var path=M2_REPO/rg/apache/maven/maven-repository-metadata/2.0.4/maven-repository-metadata-2.0.4.jar/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Patches in RTC (Geronimo - 2006-09-11)
Geronimo - Monday, September 11, 2006 14 Patches in RTC [GERONIMO-2382] Webservers portlet - Form field validation using javascript - Assignee: Unassigned - Reporter: Vamsavardhana Reddy - Created: Tue Sep 05 10:28:15 PDT 2006 - Updated: Fri Sep 08 23:17:14 PDT 2006 - Votes: 3 1 David Jencks 2 Gianny Damour 3 Paul McMahan - http://issues.apache.org/jira/browse/GERONIMO-2382 [GERONIMO-2383] Replace ENCConfigBuilder with a pluggable set of NamingBuilders - Assignee: David Jencks - Reporter: David Jencks - Created: Tue Sep 05 11:20:28 PDT 2006 - Updated: Sun Sep 10 10:55:40 PDT 2006 - Votes: 1 1 Gianny Damour - http://issues.apache.org/jira/browse/GERONIMO-2383 [GERONIMO-2388] JMS Server portlet improvement - field validation, reset button and show current task - Assignee: Unassigned - Reporter: Vamsavardhana Reddy - Created: Fri Sep 08 05:52:57 PDT 2006 - Updated: Sun Sep 10 11:50:12 PDT 2006 - Votes: 2 1 David Jencks 2 Gianny Damour - http://issues.apache.org/jira/browse/GERONIMO-2388 [GERONIMO-2349] jta 1.1 support with container manager jpa support in transaction module - Assignee: David Jencks - Reporter: David Jencks - Created: Wed Aug 23 13:22:37 PDT 2006 - Updated: Fri Sep 08 23:54:52 PDT 2006 - Votes: 2 1 David Blevins 2 Gianny Damour - http://issues.apache.org/jira/browse/GERONIMO-2349 [GERONIMO-2248] Applications portlets: List Parent and Child components against each component - Assignee: Unassigned - Reporter: Vamsavardhana Reddy - Created: Sun Jul 30 08:15:34 PDT 2006 - Updated: Sun Sep 10 11:05:40 PDT 2006 - Votes: 2 1 David Jencks 2 Donald Woods - http://issues.apache.org/jira/browse/GERONIMO-2248 [GERONIMO-2354] Replace concurrent with backport-concurrent-util - Assignee: Unassigned - Reporter: Jason Dillon - Created: Sun Aug 27 21:53:39 PDT 2006 - Updated: Thu Sep 07 12:14:27 PDT 2006 - Votes: 3 1 Dain Sundstrom 2 David Jencks 3 Guillaume Nodet - http://issues.apache.org/jira/browse/GERONIMO-2354 [GERONIMO-2379] Security Realms portlet - form field validation using javascript - Assignee: Unassigned - Reporter: Vamsavardhana Reddy - Created: Tue Sep 05 00:36:42 PDT 2006 - Updated: Sun Sep 10 11:12:56 PDT 2006 - Votes: 3 1 David Jencks 2 Gianny Damour 3 Paul McMahan - http://issues.apache.org/jira/browse/GERONIMO-2379 [GERONIMO-903] Update Log4J usage from 1.2.8 to latest maintenance version of 1.2.13 - Assignee: Jason Dillon - Reporter: Donald Woods - Created: Tue Aug 23 16:02:38 PDT 2005 - Updated: Sat Sep 09 11:17:42 PDT 2006 - Votes: 1 1 David Jencks - http://issues.apache.org/jira/browse/GERONIMO-903 [GERONIMO-2381] DB Manager portlet - Form field validation using javascript - Assignee: Unassigned - Reporter: Vamsavardhana Reddy - Created: Tue Sep 05 07:53:28 PDT 2006 - Updated: Mon Sep 11 07:02:56 PDT 2006 - Votes: 2 1 Gianny Damour 2 Paul McMahan - http://issues.apache.org/jira/browse/GERONIMO-2381 [GERONIMO-2365] Upgrade Derby to 10.1.3.1 - Assignee: Jason Dillon - Reporter: Jason Dillon - Created: Wed Aug 30 17:10:25 PDT 2006 - Updated: Sat Sep 09 11:11:06 PDT 2006 - Votes: 1 1 David Jencks - http://issues.apache.org/jira/browse/GERONIMO-2365 [GERONIMO-2015] Let's replace JKS to PKCS12 key store type - Assignee: Unassigned - Reporter: Nikolay Chugunov - Created: Fri May 12 14:54:17 PDT 2006 - Updated: Sun Sep 10 11:08:59 PDT 2006 - Votes: 0 - http://issues.apache.org/jira/browse/GERONIMO-2015 [GERONIMO-2163] WADI Integration for Jetty - Assignee: Gianny Damour - Reporter: Gianny Damour - Created: Sun Jul 02 14:16:35 PDT 2006 - Updated: Fri Sep 01 08:33:50 PDT 2006 - Votes: 1 1 David Jencks - http://issues.apache.org/jira/browse/GERONIMO-2163 [GERONIMO-2380] Keystores portlet - Form field validation using javascript - Assignee: Unassigned - Reporter: Vamsavardhana Reddy - Created: Tue Sep 05 06:40:58 PDT 2006 - Updated: Mon Sep 11 06:57:18 PDT 2006 - Votes: 3 1 David Jencks 2 Gianny Damour 3 Paul McMahan - http://issues.apache.org/jira/browse/GERONIMO-2380 [GERONIMO-2358] Move java ee 5 specs into specs trunk - Assignee: David Blevins - Reporter: David Blevins - Created: Mon Aug 28 17:21:48 PDT 2006 - Updated: Sat Sep 09 13:59:17 PDT 2006
[jira] Assigned: (AMQ-912) ActiveMQ support for SSL authentication and authorization
[ https://issues.apache.org/activemq/browse/AMQ-912?page=all ] Hiram Chirino reassigned AMQ-912: - Assignee: Hiram Chirino ActiveMQ support for SSL authentication and authorization - Key: AMQ-912 URL: https://issues.apache.org/activemq/browse/AMQ-912 Project: ActiveMQ Issue Type: Improvement Components: Test Cases, Transport Reporter: Sepand Mavandadi Assigned To: Hiram Chirino Attachments: ssl_certifiacte_auth_patch.txt, svn_diff.txt Original Estimate: 0 minutes Remaining Estimate: 0 minutes This patch adds new Transports, Brokers, and Plugins needed for authentication and authorization based on SSL certificates. It also adds a few unit tests for the mentioned classes. The new (or heavily modified) SslTransport, SslTransportServer, and SslTransportFactory classes allow for access to the underlying socket's need and want client auth settings. If a certificate is found, it is set as the transportContext of the created connection. The JaasCertificateAuthenticationBroker uses the new CertificateLoginModule to authenticate certificates (this class is abstract to allow for different backends for certificate authentication, a concrete class is TextFileCertificateLoginModule). JaasCertificateAuthenticationBroker also sets the security context's user name to that provided for the certificate by the login module. This allows for authorization using the existing authorization broker. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (AMQ-912) ActiveMQ support for SSL authentication and authorization
[ https://issues.apache.org/activemq/browse/AMQ-912?page=all ] Work on AMQ-912 started by Hiram Chirino. ActiveMQ support for SSL authentication and authorization - Key: AMQ-912 URL: https://issues.apache.org/activemq/browse/AMQ-912 Project: ActiveMQ Issue Type: Improvement Components: Test Cases, Transport Reporter: Sepand Mavandadi Assigned To: Hiram Chirino Attachments: ssl_certifiacte_auth_patch.txt, svn_diff.txt Original Estimate: 0 minutes Remaining Estimate: 0 minutes This patch adds new Transports, Brokers, and Plugins needed for authentication and authorization based on SSL certificates. It also adds a few unit tests for the mentioned classes. The new (or heavily modified) SslTransport, SslTransportServer, and SslTransportFactory classes allow for access to the underlying socket's need and want client auth settings. If a certificate is found, it is set as the transportContext of the created connection. The JaasCertificateAuthenticationBroker uses the new CertificateLoginModule to authenticate certificates (this class is abstract to allow for different backends for certificate authentication, a concrete class is TextFileCertificateLoginModule). JaasCertificateAuthenticationBroker also sets the security context's user name to that provided for the certificate by the login module. This allows for authorization using the existing authorization broker. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [ANNOUNCE] Welcome Hernan Cunico as the newest member of the Geronimo PMC
On 9/11/06, Kevan Miller [EMAIL PROTECTED] wrote: All, The Geronimo PMC is pleased to welcome Hernan Cunico as the newest member of the Geronimo PMC. We're very happy to have Hernan joining us to help with the oversight of the Geronimo project. Hurray! Our documenation's saved ;-P Congrats, Hernan! Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: [DISCUSS] 1.2 Release Manager
I'm +1 for Dain and Alan taking the lead on this release. Joe Matt Hogstrom wrote: Folks, Dain has volunteered to be the 1.2 release manager and Alan has also volunteered to be the co-pilot. I have not seen a formal discussion or vote on this. I don't know that we have a policy on this so I'm starting the discuss thread. At some point in the past Aaron volunteered to do 1.2 as well but I don't recall closure on his volunteering. Also, note that only PMC members have binding votes on the release of Apache software. Matt Hogstrom [EMAIL PROTECTED]
Re: [ANNOUNCE] Welcome Rick McGuire as the newest member of the Geronimo PMC
On 9/11/06, Jeff Genender [EMAIL PROTECTED] wrote: All, The Geronimo PMC is pleased to welcome Rick McGuire as the newest member of the Geronimo PMC. We're very happy to have Rick joining us to help with the oversight of the Geronimo project. Lets give a round of applause for Rick. Yoko-related patches will get another binding +1 when voted;-) Rick, welcome aboard! Jacek -- Jacek Laskowski http://www.laskowski.net.pl
[jira] Commented: (GERONIMO-2383) Replace ENCConfigBuilder with a pluggable set of NamingBuilders
[ http://issues.apache.org/jira/browse/GERONIMO-2383?page=comments#action_12433879 ] Jeff Genender commented on GERONIMO-2383: - +1. Replace ENCConfigBuilder with a pluggable set of NamingBuilders --- Key: GERONIMO-2383 URL: http://issues.apache.org/jira/browse/GERONIMO-2383 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Affects Versions: 1.2 Reporter: David Jencks Assigned To: David Jencks Fix For: 1.2 Attachments: GERONIMO-2383-openejb-v2.patch, GERONIMO-2383-v2.patch (Previously part of GERONIMO-2349) The ENCConfigBuilder is way too hardcoded into what it accepts and how. It won't let you add things like a persistence-ref builder very easily. We can replace it with a set of NamingBuilders somewhat similar to NamespaceDrivenBuilders. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2388) JMS Server portlet improvement - field validation, reset button and show current task
[ http://issues.apache.org/jira/browse/GERONIMO-2388?page=comments#action_12433880 ] Jeff Genender commented on GERONIMO-2388: - +1 JMS Server portlet improvement - field validation, reset button and show current task - Key: GERONIMO-2388 URL: http://issues.apache.org/jira/browse/GERONIMO-2388 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 1.1.1 Environment: Win XP, G 1.1.1-rc2 Reporter: Vamsavardhana Reddy Fix For: 1.1.2, 1.1.x, 1.2 Attachments: GERONIMO-2388.patch JMS Server portlet improvements: 1. Add new listener/edit listener page does not show any information on what listener is being added or edited. If the use is in doubt, he/she will have to go back to the previous page and start a fresh which might result in generating the page if the user chooses to click on List JMS Connectors link instead of the back button. This can be avoided by showing the current task in the edit page. 2. Form field validation using javascript for name, host (check for empty string) and port (check for numeric value). 3. Reset button. One useful little button will not do any harm. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2365) Upgrade Derby to 10.1.3.1
[ http://issues.apache.org/jira/browse/GERONIMO-2365?page=comments#action_12433881 ] Jeff Genender commented on GERONIMO-2365: - This doesn't seem to need RTC, but I will +1 it anyways. Upgrade Derby to 10.1.3.1 - Key: GERONIMO-2365 URL: http://issues.apache.org/jira/browse/GERONIMO-2365 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Affects Versions: 1.2 Reporter: Jason Dillon Assigned To: Jason Dillon Priority: Minor Fix For: 1.2 Attachments: GERONIMO-2365-testsupport-bdudney.patch, GERONIMO-2365.diff The latest release appears to run fine. We should upgrade our dependencies to use 10.1.3.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2381) DB Manager portlet - Form field validation using javascript
[ http://issues.apache.org/jira/browse/GERONIMO-2381?page=comments#action_12433882 ] Jeff Genender commented on GERONIMO-2381: - +1 DB Manager portlet - Form field validation using javascript --- Key: GERONIMO-2381 URL: http://issues.apache.org/jira/browse/GERONIMO-2381 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 1.1.1 Environment: WinXP, G 1.1.1-rc1 Reporter: Vamsavardhana Reddy Fix For: 1.2, 1.1.x, 1.1.2 Attachments: GERONIMO-2381.patch Form field validation in DB Manager portlet using javascript. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Build failure on trunk. Plese help resolve this.
On 9/11/06, Jacek Laskowski [EMAIL PROTECTED] wrote: I'm building Geronimo, Geronimo specs and OpenEJB manually (it's the second or third time today), so I can only confirm the respective builds work fine. Another shot and it went smoothly. After I changed the m2 local repository to c:\.m2 the builds are all fine. The first build is for Geronimo Specs, then OpenEJB 2 and Geronimo itself afterwards. All, with some network-related problems downloading jars, went fine. Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: [ANNOUNCE] Welcome Rick McGuire as the newest member of the Geronimo PMC
Congrats Rick ! Jeff Genender wrote: All, The Geronimo PMC is pleased to welcome Rick McGuire as the newest member of the Geronimo PMC. We're very happy to have Rick joining us to help with the oversight of the Geronimo project. Lets give a round of applause for Rick. Well done, Rick! The Apache Geronimo PMC Jeff
[jira] Commented: (GERONIMO-2365) Upgrade Derby to 10.1.3.1
[ http://issues.apache.org/jira/browse/GERONIMO-2365?page=comments#action_12433883 ] Jacek Laskowski commented on GERONIMO-2365: --- Where should these patches be applied to? What module are they for? Upgrade Derby to 10.1.3.1 - Key: GERONIMO-2365 URL: http://issues.apache.org/jira/browse/GERONIMO-2365 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Affects Versions: 1.2 Reporter: Jason Dillon Assigned To: Jason Dillon Priority: Minor Fix For: 1.2 Attachments: GERONIMO-2365-testsupport-bdudney.patch, GERONIMO-2365.diff The latest release appears to run fine. We should upgrade our dependencies to use 10.1.3.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [ANNOUNCE] Welcome Hernan Cunico as the newest member of the Geronimo PMC
Congrats Hernan ! chris Kevan Miller wrote: All, The Geronimo PMC is pleased to welcome Hernan Cunico as the newest member of the Geronimo PMC. We're very happy to have Hernan joining us to help with the oversight of the Geronimo project. Well done, Hernan! The Apache Geronimo PMC --kevan
lifecycle logging from server
Hi All, With my recent poking around in the startup and shutdown code for https://issues.apache.org/jira/browse/GERONIMO-2385 I figure I might be the guy to fix; http://issues.apache.org/jira/browse/GERONIMO-2387 but I can't assign it to myself. Could some one give me that permission in JIRA (user name bdudney)? Thanks, -bd-
Re: [ANNOUNCE] Welcome Rick McGuire as the newest member of the Geronimo PMC
Congratulations Rick! -dain On Sep 11, 2006, at 7:17 AM, Jeff Genender wrote: All, The Geronimo PMC is pleased to welcome Rick McGuire as the newest member of the Geronimo PMC. We're very happy to have Rick joining us to help with the oversight of the Geronimo project. Lets give a round of applause for Rick. Well done, Rick! The Apache Geronimo PMC Jeff
