Re: Netbeans plugin
On Feb 9, 2008 4:48 AM, Kevan Miller [EMAIL PROTECTED] wrote: Jacek had been most active with the Netbeans activities. I think he may have been distracted for a bit. I'm sure he'd love to hear that people are interested... ;-) I always am. People keep asking about it, but the truth is that it requires a lot of attention that I must admit publicly don't have much lately. Whenever I start working on the plugin something distracts me for a bit. Let's see how it's going to be this time. Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
[jira] Commented: (GERONIMO-2682) Sending a message throws a SendFailedException
[
https://issues.apache.org/jira/browse/GERONIMO-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12567414#action_12567414
]
Vamsavardhana Reddy commented on GERONIMO-2682:
---
Looks like the connection to smtp server could not be established. Are you
able to use the same smtp server to send mail from any other mail software?
Sending a message throws a SendFailedException
--
Key: GERONIMO-2682
URL: https://issues.apache.org/jira/browse/GERONIMO-2682
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: mail
Affects Versions: 2.0.x
Reporter: Geist Alexander
Fix For: 2.0.x
// Get system properties
Properties props = System.getProperties();
// Setup mail server
props.put(mail.smtp.host, Settings.smtpServer);
props.put(mail.imap.partialfetch, false);
props.put(mail.smtp.auth, true);
Authenticator auth = new Authenticator()
{
protected PasswordAuthentication getPasswordAuthentication()
{
return new PasswordAuthentication(Settings.user, Settings.key);
}
};
return Session.getDefaultInstance(props, auth);
The method was used to get the session. It works.
Next step is to build and to send the message.
// Define message
MimeMessage message = new MimeMessage(mailParam.getSession());
// Set the from address
message.setFrom(new InternetAddress(Settings.from));
// Empfänger
message.addRecipient(Message.RecipientType.TO, new
InternetAddress(mailParam.getMailAddress()));
// Set the subject
message.setSubject(Subject);
BodyPart messageBodyPart = new MimeBodyPart();
String text =
getEmailText(mailParam.getXmgKey(),mailParam.getXlgKey(),
mailParam.getDate());
messageBodyPart.setContent(text, text/html);
Multipart multipart = new MimeMultipart();
multipart.addBodyPart(messageBodyPart);
// Put parts in message
message.setContent(multipart);
// Send message
Transport.send(message);
Transport.send(message) is throwing this Exception
javax.mail.SendFailedException: Send failure (javax.mail.MessagingException:
Connection error (java.net.ConnectException: Connection refused: connect))
at javax.mail.Transport.send(Transport.java:163)
at javax.mail.Transport.send(Transport.java:48)
at keygen.main.MailSender.sendMail(MailSender.java:44)
at keygen.main.MailSender.main(MailSender.java:112)
Caused by: javax.mail.MessagingException: Connection error
(java.net.ConnectException: Connection refused: connect)
at
org.apache.geronimo.javamail.transport.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:403)
at javax.mail.Service.connect(Service.java:254)
at javax.mail.Service.connect(Service.java:85)
at javax.mail.Service.connect(Service.java:70)
at javax.mail.Transport.send(Transport.java:94)
... 3 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:519)
at java.net.Socket.connect(Socket.java:469)
at java.net.Socket.init(Socket.java:366)
at java.net.Socket.init(Socket.java:239)
at
org.apache.geronimo.javamail.transport.smtp.SMTPTransport.getConnectedSocket(SMTPTransport.java:1091)
at
org.apache.geronimo.javamail.transport.smtp.SMTPTransport.getConnection(SMTPTransport.java:851)
at
org.apache.geronimo.javamail.transport.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:380)
... 7 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[BUILD] 2.2: Failed for Revision: 620248
Geronimo Revision: 620248 built with tests included See the full build-0300.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080210/build-0300.log Download the binaries from http://geronimo.apache.org/maven/server/binaries/trunk/20080210 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 30 minutes 14 seconds [INFO] Finished at: Sun Feb 10 03:37:12 EST 2008 [INFO] Final Memory: 308M/675M [INFO] TESTSUITE RESULTS (Failures only) = See detailed results at http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html Assembly: tomcat = See the full test.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080210/logs-0300-tomcat/test.log Assembly: jetty = See the full test.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080210/logs-0300-jetty/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 73.306 sec FAILURE!
Re: Inclusion of MySQL in roller-mysql-database plugin
David Jencks wrote: On Feb 9, 2008, at 8:17 PM, Davanum Srinivas wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kevan, You are right. We have a new mechanism for triggering prohibited works. We need to get this to the attention of the legal-discuss folks so they cover that angle in addition to just the ship angle that they have looked at so far. Would specifying scopeprovided/scope provided in the pom.xml for mysql be enough to geronimo from downloading mysql when the plugin is installed? I am not that worried about pulling in that jar into our maven repo when we create/build our distribution, as long as we don't ship it. The scope won't have any effect. We do have the option of specifying the mysql jar as a prerequisite which will prevent installation of the plugin unless the mysql jar is already present, presumably because someone who is aware of the licensing concerns has explicitly installed it. I don't know if we've checked that this works properly with a jar rather than car (geronimo plugin) dependency but theoretically it would work. It works I will prepare a patch and put it in Kevan's JIRA https://issues.apache.org/jira/browse/GERONIMO-3816 for you to review. I don't think this a very elegant solution but it may be the best we can do in the near term. I guess I'm dreaming of a license filter that you can set up and then plugins can download dependencies consistent with the licenses you have allowed. To reiterate, we (asf) would never be shipping the mysql jar, but as currently set up, anyone installing the mysql roller plugin would be installing the mysql jar into their geronimo server. thanks david jencks thanks, dims Kevan Miller wrote: | | On Feb 9, 2008, at 2:01 PM, Davanum Srinivas wrote: | | -BEGIN PGP SIGNED MESSAGE- | Hash: SHA1 | | Kevan, | | I followed the discussion. You said that Yes. The automatic download | is the issue.. I don't think that is the case...I | believe the clear guidance kicks in when we *ship* a distribution | with some other license on that page. So i thought | we should get clarification on that point. | | related question, Are we at this point picking/shipping either the | plugin or the mysql jars into our distribution? | | | Hi Dims, | The roller plugins are not included in Geronimo 2.1. We will want to | release the roller plugin at some point. So, will need to clear up this | point before then. | | Thanks for the clarification. So, is this your question? | | | | Is it ok to release an Apache product which will automatically, without | user prompting, download a prohibited work? | | The product in question is the Apache Geronimo roller-mysql-database | plugin which has a dependency on a prohibited work (i.e. a MySQL jar | which is GPL with a FLOSS exception). The building of the plugin would | download a MySQL jar into a users maven repository. The MySQL jar would | *not* be included in the Geronimo roller-mysql-database plugin binary. | However, the subsequent installation of this plugin would cause the | Geronimo server to automatically download and install the MySQL jar, | without notifying the user. | | * | | IMO, the answer is no, you can't. Not by default and not without | notifying the user. Am happy to get clarification, if you (or anyone | else) think otherwise or aren't sure... | | I think the basic options are: | | 1. Don't make roller-mysql-database part of the standard build (and | don't release a roller-mysql-database binary). The user can use a | non-standard build option to create the plugin, as long as he/she is | notified. | 2. Make the roller-mysql-database part of the standard build, but remove | the MySQL dependency. This binary can be built and released by our | project. However, the MySQL jar must be installed -- either manually by | the user or by some tool which properly notifies the user. | | --kevan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) iD8DBQFHrnrmgNg6eWEDv1kRAvXxAKDLSlpx83vB5a2iEzskKIOt8iIP+wCfdqfn oUFOkxrqEIx5Yl+U2ao04vE= =oWpQ -END PGP SIGNATURE-
Re: Geronimo in year 2008
On Feb 9, 2008 12:02 PM, Jacek Laskowski [EMAIL PROTECTED] wrote: On Feb 7, 2008 6:58 AM, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: Geronimo had a great year 2007. I don't need to re-list all our achievements listed in Matt's mail from 31st Dec 2007 (http://www.mail-archive.com/dev@geronimo.apache.org/msg54994.html). Now that 2.1 is also rolling out, I think it is time we start discussing what we want to do in Geronimo in year 2008. Let us also discuss what we must do to make Geronimo an application server of choice. I would like all of us to use this mail thread to put forth our thoughts (and any action items some of us may have already come up with silently) so that the community can see what great heights Geronimo will scale in 2008. We certainly need more exposure in the tools area and having a Geronimo NetBeans plugin is a way to go. Eclipse one's fine, but we need to bring Geronimo to NetBeans masses and let them know there's another application server with a name that starts with G which is worth paying attention to as well. Documentation, documentation and no need to say more but documentation is an absolute must. In most cases, we have an associated JIRA for a new feature or a major bug fix. How about we designate the JIRA as resolved only after the related documentation is in place? Many a time we verify the code before closing the JIRA. It shouldn't be hard adding a wiki page with a small write up on how to use that feature or any work around provided. It can be a detailed document or an entry in an FAQ. This will also help in coming up with comprehensive docs after a release. Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: Geronimo in year 2008
I hope to summarize the input collected on this thread in a few days. Let us introduce some practices that we would love everybody to follow, but as always it is up to the individual. ++Vamsi On Feb 10, 2008 11:33 PM, Jacek Laskowski [EMAIL PROTECTED] wrote: On Feb 10, 2008 9:59 AM, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: In most cases, we have an associated JIRA for a new feature or a major bug fix. How about we designate the JIRA as resolved only after the related documentation is in place? Many a time we verify the code before closing the JIRA. It shouldn't be hard adding a wiki page with a small write up on how to use that feature or any work around provided. It can be a detailed document or an entry in an FAQ. This will also help in coming up with comprehensive docs after a release. +1. It's a rule to describe new stuff on the mailing list so it's easy to pick it up and put it on the Wiki. Will you document it somewhere? ;-) Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
[jira] Issue Comment Edited: (GERONIMO-3816) roller-mysql-database has mysql dependency
[ https://issues.apache.org/jira/browse/GERONIMO-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12567454#action_12567454 ] ppe edited comment on GERONIMO-3816 at 2/10/08 10:06 AM: - This patch (roller-mysql-database_lic_iss_res_080210.patch) intend to reinstate the roller-mysql-database module by resolving the licensing issue. To prevent automatic download of the mysql connector the mysql-connector-java dependency is disabled and the module is instead set up with a prerequisite on the connector. The prerequisite description contains information on the licensing issue and instructions on what is needed to be done by the user for the module to be used. was (Author: ppe): This patch intend to reinstate the roller-mysql-database module by resolving the licensing issue. To prevent automatic download of the mysql connector the mysql-connector-java dependency is disabled and the module is instead set up with a prerequisite on the connector. The prerequisite description contains information on the licensing issue and instructions on what is needed to be done by the user for the module to be used. roller-mysql-database has mysql dependency -- Key: GERONIMO-3816 URL: https://issues.apache.org/jira/browse/GERONIMO-3816 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Plugins Reporter: Kevan Miller Attachments: roller-mysql-database_lic_iss_res_080210.patch The roller-mysql-database plugin has a hard dependency on MySQL. We have to remove this for licensing reasons. See explanation below. I plan on disabling the building of the roller-mysql-database plugin as well as removing the mysql dependency. We'll need to reach a decision on how we want to handle this long term. Here's more licensing info... MySQL is Licensed under the GPL license: http://www.mysql.com/company/legal/licensing/ MySQL is also available under a FLOSS exception: http://www.mysql.com/company/legal/licensing/foss-exception.html. The FLOSS exception only be applied to MySQL when it is used under an OSI-approved license. Neither license is deemed suitable by the Apache Software Foundation in ASF distributions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3816) roller-mysql-database has mysql dependency
[ https://issues.apache.org/jira/browse/GERONIMO-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Petersson updated GERONIMO-3816: -- Attachment: roller-mysql-database_lic_iss_res_080210.patch This patch intend to reinstate the roller-mysql-database module by resolving the licensing issue. To prevent automatic download of the mysql connector the mysql-connector-java dependency is disabled and the module is instead set up with a prerequisite on the connector. The prerequisite description contains information on the licensing issue and instructions on what is needed to be done by the user for the module to be used. roller-mysql-database has mysql dependency -- Key: GERONIMO-3816 URL: https://issues.apache.org/jira/browse/GERONIMO-3816 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Plugins Reporter: Kevan Miller Attachments: roller-mysql-database_lic_iss_res_080210.patch The roller-mysql-database plugin has a hard dependency on MySQL. We have to remove this for licensing reasons. See explanation below. I plan on disabling the building of the roller-mysql-database plugin as well as removing the mysql dependency. We'll need to reach a decision on how we want to handle this long term. Here's more licensing info... MySQL is Licensed under the GPL license: http://www.mysql.com/company/legal/licensing/ MySQL is also available under a FLOSS exception: http://www.mysql.com/company/legal/licensing/foss-exception.html. The FLOSS exception only be applied to MySQL when it is used under an OSI-approved license. Neither license is deemed suitable by the Apache Software Foundation in ASF distributions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [Fwd: Geronimo Documentation - 5-minute Tutorial on Enterprise Application Development with Eclipse and Geronimo]
On Feb 5, 2008 2:55 PM, Hernan Cunico [EMAIL PROTECTED] wrote: solved, it was a refresh problem. restarting eclipse fixed it. Hi Hernan, I'm relieved. I've just read the email. Sorry for not responding earlier. Do you have any idea what I could write about Geronimo and Java EE 5? I'm going to write something today (Sunday!) and am looking for some interesting ideas ;-) Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: Geronimo in year 2008
On Feb 10, 2008 9:59 AM, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: In most cases, we have an associated JIRA for a new feature or a major bug fix. How about we designate the JIRA as resolved only after the related documentation is in place? Many a time we verify the code before closing the JIRA. It shouldn't be hard adding a wiki page with a small write up on how to use that feature or any work around provided. It can be a detailed document or an entry in an FAQ. This will also help in coming up with comprehensive docs after a release. +1. It's a rule to describe new stuff on the mailing list so it's easy to pick it up and put it on the Wiki. Will you document it somewhere? ;-) Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: Inclusion of MySQL in roller-mysql-database plugin
Kevan Miller wrote: All, I created a Jira to handle licensing issues involving the inclusion of MySQL in the roller-mysql-database plugin. See https://issues.apache.org/jira/browse/GERONIMO-3816 A patch that may resolve this issue have been posted to https://issues.apache.org/jira/browse/GERONIMO-3816 regards Peter P I've insured that we will no longer build the roller-mysql-database plugin in our source code. However, there are multiple ways of handling this problem. Would like to hear opinions from the project. Ultimately, it's the PMC's responsibility to oversee the licensing of our distributions and to oversee the way we handle dependencies on artifacts that are covered by excluded licenses. The ASF Licensing Policy (currently it's a draft policy, but I think we should be following the guidelines documented there) are located here -- http://www.apache.org/legal/3party.html Discussion of how to handle Prohibited Works is here -- http://people.apache.org/~rubys/3party.html#options Would be good for the project (in particular PMC) members to be familiar with these issues. Would like to hear how we think we should address this issue. As long as I feel the PMC is providing appropriate oversight, I'm happy with what ever decision we reach. --kevan
Re: Adding a page to a plugin
Thanks all for pointing out the documentation. Looks like its pretty detailed too. Will be very helpful. Will improve it if anything missing Regards Manu On Feb 9, 2008 1:11 AM, Joseph Leong [EMAIL PROTECTED] wrote: Just an update. I'm not sure exactly why the steps i took the first time didn't work... but it seems nothing was wrong with my procedure. I Re-downloaded trunk, re-implemented and everything worked just like a charm. The only difference between the two was the way i imported the projected into eclipse. The first method was unconventional and the second method was via mvn eclipse:eclipse Anyhow so for future reference, it is 1) Creating the handler page. 2) Creating the jsp page 3) Adding the addhelper in the ImportExport portlet. Now i can finally move along and finish this piece. Thanks again for everyone's input. Wishing everyone the best, -Joseph Leong On Feb 8, 2008 11:35 AM, Paul McMahan [EMAIL PROTECTED] wrote: Right, the doc in the wiki about the extensible admin console was really only helpful for Manu's followup to your question. The mutipage portlet code you referred to is internal to the admin console and afaik is not documented anywhere nor is it intended to be exposed as an externally supported api. Creating an admin console extension does not require you to implement your portlet this way. Paul On Feb 8, 2008, at 10:37 AM, Joseph Leong wrote: Thank you for all the responses! The piece i'm working on is the plugin installer in the console, but it seems to be built with some sort of multipage model framework. So this part of it is working a little differently than the documentation, but It just so happens that your wiki references on the extensible administration console will really help on the debug viewer plugin piece i'm working on. I'll post updates on what the missing piece was once i figure it out, feel it'll save someone down the road a good bit of time should they go down this route and find any other pieces of the console working on this multipage model framework. Wishing you all the best, Joseph Leong On Feb 7, 2008 4:50 PM, Joseph Leong [EMAIL PROTECTED] wrote: Hi everyone, I'm trying to add a page to a plugin. After tracing the code, it is running through the handler ie.. hitting the actionBeforeView and going into the renderView. However nothing of my jsp page is showing up. The steps i've taken are: 1) Create the handler page 2) create the jsp page 3) Add the addhelper in the ImportExportPortlet.java Is there anything blatantly obvious that I'm missing? Or i will continue to work with these 3 pieces. Thanks! -Joseph Leong
[jira] Created: (GERONIMO-3836) Deployment fails with FNFE due to missing jline_.dll on Cygwin
Deployment fails with FNFE due to missing jline_.dll on Cygwin -- Key: GERONIMO-3836 URL: https://issues.apache.org/jira/browse/GERONIMO-3836 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: deployment Affects Versions: 2.2 Reporter: Jacek Laskowski Meant to deploy a webapp from a directory outside Geronimo's installation dir. Deployer worked with -u and -p options although it spit FNFE exception, but it failed without them. [EMAIL PROTECTED] /cygdrive/c/apps/apache-wicket/src/jdk-1.5/wicket-examples/target $ c\:/geronimo/bin/deploy.sh -u system -p manager deploy wicket-examples.war Using GERONIMO_BASE: c:\geronimo Using GERONIMO_HOME: c:\geronimo Using GERONIMO_TMPDIR: c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp Using JRE_HOME:c:\apps\java5\jre java.io.FileNotFoundException: c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp\jline_.dll (The system cannot find the path specified) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.init(FileOutputStream.java:179) at java.io.FileOutputStream.init(FileOutputStream.java:131) at jline.WindowsTerminal.loadLibrary(WindowsTerminal.java:274) at jline.WindowsTerminal.initializeTerminal(WindowsTerminal.java:227) at jline.Terminal.setupTerminal(Terminal.java:77) at jline.Terminal.getTerminal(Terminal.java:28) at jline.ConsoleReader.init(ConsoleReader.java:167) at jline.ConsoleReader.init(ConsoleReader.java:162) at org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:164) at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45) at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67) at org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:31) Deployed default/wicket-examples/1202695110250/war @ /wicket-examples [EMAIL PROTECTED] /cygdrive/c/apps/apache-wicket/src/jdk-1.5/wicket-examples/target $ c\:/geronimo/bin/deploy.sh undeploy default/wicket-examples/1202695110250/war Using GERONIMO_BASE: c:\geronimo Using GERONIMO_HOME: c:\geronimo Using GERONIMO_TMPDIR: c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp Using JRE_HOME:c:\apps\java5\jre java.io.FileNotFoundException: c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp\jline_.dll (The system cannot find the path specified) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.init(FileOutputStream.java:179) at java.io.FileOutputStream.init(FileOutputStream.java:131) at jline.WindowsTerminal.loadLibrary(WindowsTerminal.java:274) at jline.WindowsTerminal.initializeTerminal(WindowsTerminal.java:227) at jline.Terminal.setupTerminal(Terminal.java:77) at jline.Terminal.getTerminal(Terminal.java:28) at jline.ConsoleReader.init(ConsoleReader.java:167) at jline.ConsoleReader.init(ConsoleReader.java:162) at org.apache.geronimo.deployment.cli.InputPrompt.init(InputPrompt.java:42) at org.apache.geronimo.deployment.cli.ServerConnection.doAuthPromptAndRetry(ServerConnection.java:230) at org.apache.geronimo.deployment.cli.ServerConnection.tryToConnect(ServerConnection.java:190) at org.apache.geronimo.deployment.cli.ServerConnection.init(ServerConnection.java:94) at org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:161) at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45) at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67) at org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:31) Username: system Password: Error: Login Failed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[VOTE] Geronimo Server 2.1 and Geronimo TxManager 2.1.1 Releases
All, I've prepared a 2.1 release candidate for your review and vote. I've also prepared a 2.1.1 TxManager release candidate for review and vote. For simplicity, I'm holding a single vote for both releases. The Geronimo server release is dependent upon the TxManager 2.1.1 release. The source for the Geronimo 2.1 release currently resides here: https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.0 When the release vote is approved, I will svn mv the code to https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.0 An archive of this source code can be found here: http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-2.1-src.tar.gz http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/ contains the 8 Java EE and Minimal server binary distributions to be released (tomcat/jetty, Java EE/Minimal, tar/zip) as well as the RELEASE_NOTES and source code archives for the release. For your convenience, here are pointers to the urls for the distributions in zip format: http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-jetty6-javaee5-2.1-bin.zip http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-jetty6-minimal-2.1-bin.zip http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-tomcat6-javaee5-2.1-bin.zip http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-tomcat6-minimal-2.1-bin.zip The maven artifacts for the release can be found here: http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1/ or in the following archive (warning, this file is 458 megs): http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist.tar.gz When the release vote is approved, these maven artifacts will be moved to the m2-ibiblio-rsync-repository at Apache. Due to the discovery of a bug in the Connector component of Geronimo TxManager, a new release of TxManager was needed. TxManager 2.1.1 is also part of this vote. The source code for the TxManager 2.1.1 release can be found here: https://svn.apache.org/repos/asf/geronimo/components/txmanager/tags/geronimo-txmanager-parent-2.1.1 The maven artifacts for TxManager 2.1.1 can be found here: http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-txmanager-2.1.1/ When the release vote is approved, these maven artifacts will be moved to the m2-ibiblio-rsync-repository at Apache. Please review these releases and register your vote. [ ] +1 Release Geronimo 2.1 and TxManager 2.1.1 [ ] 0 No opinion [ ] -1 Do not release Geronimo 2.1 and TxManager 2.1.1 (please provide rationale) I'll plan on calling this vote on Wednesday evening (11 PM EST). --kevan
[BUILD] 2.2: Failed for Revision: 620375
Geronimo Revision: 620375 built with tests included See the full build-2100.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080210/build-2100.log Download the binaries from http://geronimo.apache.org/maven/server/binaries/trunk/20080210 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 29 minutes 56 seconds [INFO] Finished at: Sun Feb 10 21:36:50 EST 2008 [INFO] Final Memory: 308M/992M [INFO] TESTSUITE RESULTS (Failures only) = See detailed results at http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html Assembly: tomcat = See the full test.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080210/logs-2100-tomcat/test.log Assembly: jetty = See the full test.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080210/logs-2100-jetty/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 74.257 sec FAILURE!
[jira] Commented: (GERONIMO-3816) roller-mysql-database has mysql dependency
[ https://issues.apache.org/jira/browse/GERONIMO-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12567534#action_12567534 ] David Jencks commented on GERONIMO-3816: I applied the patch in rev 620430 with some text changes in the poms and README. I tried to make the mysql dependency optional but maven tries to download it anyway. If we can make it optional then our build won't even need the jar: the only function is to get the dependency into the plugin dependency list. Although it would be better to get optional to work I think the current state is OK to release. roller-mysql-database has mysql dependency -- Key: GERONIMO-3816 URL: https://issues.apache.org/jira/browse/GERONIMO-3816 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Plugins Reporter: Kevan Miller Attachments: roller-mysql-database_lic_iss_res_080210.patch The roller-mysql-database plugin has a hard dependency on MySQL. We have to remove this for licensing reasons. See explanation below. I plan on disabling the building of the roller-mysql-database plugin as well as removing the mysql dependency. We'll need to reach a decision on how we want to handle this long term. Here's more licensing info... MySQL is Licensed under the GPL license: http://www.mysql.com/company/legal/licensing/ MySQL is also available under a FLOSS exception: http://www.mysql.com/company/legal/licensing/foss-exception.html. The FLOSS exception only be applied to MySQL when it is used under an OSI-approved license. Neither license is deemed suitable by the Apache Software Foundation in ASF distributions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-100) geronimo/stop-server dumps ConnectException: Connection refused: connect when server's stopped yet Shutdown request has been issued
geronimo/stop-server dumps ConnectException: Connection refused: connect when server's stopped yet Shutdown request has been issued --- Key: GSHELL-100 URL: https://issues.apache.org/jira/browse/GSHELL-100 Project: GShell Issue Type: Bug Security Level: public (Regular issues) Reporter: Jacek Laskowski Assignee: Jason Dillon The stack trace should not be printed out, but a error message. The Shutdown request has been issued message's a little misleading. [EMAIL PROTECTED] /cygdrive/c/geronimo-jetty6-javaee5-2.1 $ ./bin/gsh Apache Geronimo (2.1) Type 'help' for more information. [EMAIL PROTECTED]:/ geronimo/stop-server Stopping Geronimo server: localhost:1099 Username: systen Password: 23:22:20,156 WARN [ServerProxy] Unable to shutdown the server java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nes ted exception is: java.net.ConnectException: Connection refused: connect] at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:317) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) at org.apache.geronimo.commands.ServerProxy.getConnection(ServerProxy.java:102) at org.apache.geronimo.commands.ServerProxy.invoke(ServerProxy.java:219) at org.apache.geronimo.commands.ServerProxy.invoke(ServerProxy.java:230) at org.apache.geronimo.commands.ServerProxy.invoke(ServerProxy.java:234) at org.apache.geronimo.commands.ServerProxy.shutdown(ServerProxy.java:202) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.groovy.reflection.CachedMethod.invokeByReflection(CachedMethod.java:107) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:127) at org.codehaus.groovy.runtime.metaclass.StdMetaMethod.invoke(StdMetaMethod.java:18) at org.codehaus.groovy.runtime.MetaClassHelper.doMethodInvoke(MetaClassHelper.java:538) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:749) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:589) at org.codehaus.groovy.runtime.Invoker.invokePojoMethod(Invoker.java:87) at org.codehaus.groovy.runtime.Invoker.invokeMethod(Invoker.java:75) at org.codehaus.groovy.runtime.InvokerHelper.invokeMethod(InvokerHelper.java:74) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethodN(ScriptBytecodeAdapter.java:158) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethod0(ScriptBytecodeAdapter.java:201) at org.apache.geronimo.commands.StopServerCommand.doExecute(StopServerCommand.groovy:72) at org.apache.geronimo.gshell.command.CommandSupport.execute(CommandSupport.java:101) at org.apache.geronimo.gshell.plugin.PlexusCommandWrapper.execute(PlexusCommandWrapper.java:71) at org.apache.geronimo.gshell.DefaultCommandExecutor.execute(DefaultCommandExecutor.java:209) at org.apache.geronimo.gshell.ExecutingVisitor.visit(ExecutingVisitor.java:96) at org.apache.geronimo.gshell.parser.ASTExpression.jjtAccept(ASTExpression.java:17) at org.apache.geronimo.gshell.parser.SimpleNode.childrenAccept(SimpleNode.java:57) at org.apache.geronimo.gshell.ExecutingVisitor.visit(ExecutingVisitor.java:79) at org.apache.geronimo.gshell.parser.ASTCommandLine.jjtAccept(ASTCommandLine.java:17) at org.apache.geronimo.gshell.DefaultCommandLineBuilder$1.execute(DefaultCommandLineBuilder.java:95) at org.apache.geronimo.gshell.DefaultCommandExecutor.execute(DefaultCommandExecutor.java:86) at org.apache.geronimo.gshell.DefaultShell.execute(DefaultShell.java:123) at org.apache.geronimo.gshell.DefaultShell$1.execute(DefaultShell.java:155) at org.apache.geronimo.gshell.console.Console.work(Console.java:187) at org.apache.geronimo.gshell.console.Console.run(Console.java:128) at org.apache.geronimo.gshell.console.JLineConsole.run(JLineConsole.java:68) at org.apache.geronimo.gshell.DefaultShell.run(DefaultShell.java:202) at org.apache.geronimo.gshell.GShell.run(GShell.java:156) at
Re: Inclusion of MySQL in roller-mysql-database plugin
I applied this patch with some text changes and think the result is OK as far as legal issues. I tried to make the msyql-connector-java jar an optional dependency but maven insists on downloading it anyway. If we can prevent this I'd prefer it. The only reason for the dependency is so it gets copied into the plugin dependency list. The README now says: Roller with MySql Licensing: MySQL is Licensed under the GPL license: http://www.mysql.com/company/ legal/licensing/ and also under a FLOSS exception: http://www.mysql.com/company/legal/ licensing/foss-exception.html. Neither of these license terms are compatible with the goals of the ASF. The mysql-connector-java jar should not be needed to build the roller- mysql-database plugin (it is marked as an optional dependency) but for unknown reasons it is currently downloaded during the build. The only purpose of including the dependency in the pom is to get it into the geronimo plugin dependency list. The mysql-connector-java jar is listed as a prerequisite of the roller-mysql-database plugin. This has the effect of requiring the user to install the mysql jar themselves into their geronimo server before installing the roller-mysql-database plugin. The licensing issues are explained in text in the prerequisite specification. Roller with MySql Setup: At any time you can start using mysql as database back-end by installing the roller-mysql plugin module. Before installing the roller-mysql plugin create a empty mysql database called 'roller' with the user 'roller' and password 'roller'. After installing the roller-mysql plugin you may need to restart roller for the database change to take effect this can be done from Geronimos console via Application -- Web App WARs. The description of the prerequisite, which appears in the console when you try to install the plugin, reads: This module requires the mysql connector to be present in the Geronimo repository. MySQL is Licensed under the GPL license: http://www.mysql.com/company/legal/licensing/ MySQL is also available under a FLOSS exception: http://www.mysql.com/company/legal/licensing/foss- exception.html. The FLOSS exception only be applied to MySQL when it is used under an OSI-approved license. Neither of these licenses are compatible with the goals of the Apache Software Foundation. Thus, we cannot let the MySQL roller plugin automaticaly download the connector for you. How ever if either of the above license terms are acceptable to you, you may download the connector into the Geronimo repository yourself and re-select/install this module to enable roller with a mysql connector. I checked that the console plugin installer worked properly and it clearly prevents you from installing the plugin with mysql-connector- jar missing and you can see the prerequisite description. You also can't install it using the gshell list-plugins command but it is a lot harder to tell that it didn't install and the description is not presented. thanks david jencks On Feb 10, 2008, at 10:08 AM, Peter Petersson wrote: Kevan Miller wrote: All, I created a Jira to handle licensing issues involving the inclusion of MySQL in the roller-mysql-database plugin. See https://issues.apache.org/jira/browse/GERONIMO-3816 A patch that may resolve this issue have been posted to https:// issues.apache.org/jira/browse/GERONIMO-3816 regards Peter P I've insured that we will no longer build the roller-mysql- database plugin in our source code. However, there are multiple ways of handling this problem. Would like to hear opinions from the project. Ultimately, it's the PMC's responsibility to oversee the licensing of our distributions and to oversee the way we handle dependencies on artifacts that are covered by excluded licenses. The ASF Licensing Policy (currently it's a draft policy, but I think we should be following the guidelines documented there) are located here -- http://www.apache.org/legal/3party.html Discussion of how to handle Prohibited Works is here -- http:// people.apache.org/~rubys/3party.html#options Would be good for the project (in particular PMC) members to be familiar with these issues. Would like to hear how we think we should address this issue. As long as I feel the PMC is providing appropriate oversight, I'm happy with what ever decision we reach. --kevan
