[jira] Created: (DIRSTUDIO-63) Should not package ui-forms in org.apache.directory.ldapstudio.schemas_0.6.0jar
Should not package ui-forms in org.apache.directory.ldapstudio.schemas_0.6.0jar --- Key: DIRSTUDIO-63 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-63 Project: Directory LDAP Studio Issue Type: Bug Components: ldapstudio-schemas Affects Versions: 0.6.0 Reporter: Alex Blewitt You shouldn't bundle ui-forms-3.2.0 in the org.apache.directory.ldapstudio.schemas_0.6.0 bundle; otherwise, you'll get different classes loaded than the forms that are being used in the current Eclipse runtime. Instead, there should be a bundle dependency on the org.eclipse.ui.forms bundle (like you've got for org.eclipse.ui) instead. I guess this is probably just an oversight in putting it together... Alex. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[ApacheDS] Preparing installers for testing 1.0.1 release
Hi all, I will prepare for the 1.0.1 release now that MINA 1.0.2 is out and have some installers ready for testing. I will also try to provide some zip/tar balls for the sources. Would be nice to have a couple people kick the tires before we release. Stefan Zoerner, once I have some of these ready could you just double check your favorite distribution with VSLDAP and confirm compliance? Unfortunately my VSLDAP setup is not available. Thanks, Alex
Re: [ApacheDS] Preparing installers for testing 1.0.1 release
Hi Alex! Alex Karasulu wrote: Stefan Zoerner, once I have some of these ready could you just double check your favorite distribution with VSLDAP and confirm compliance? Unfortunately my VSLDAP setup is not available. Just drop a mail, if installers are available, and I'll perform the compliance tests immediately. I need at least a version for W32 (preferred) or Sun (SPARC platform). By the way: We can use the brand new VSLDAP 2.3 final release, it is out since February 12. Greetings from Hamburg, Stefan ---8--- Stefan Zoerner ([EMAIL PROTECTED]) Committer :: PMC Member Apache Directory Project http://directory.apache.org
Re: [ApacheDS] Preparing installers for testing 1.0.1 release
Excellent! Thank you Stefan. Alex On 2/21/07, Stefan Zoerner [EMAIL PROTECTED] wrote: Hi Alex! Alex Karasulu wrote: Stefan Zoerner, once I have some of these ready could you just double check your favorite distribution with VSLDAP and confirm compliance? Unfortunately my VSLDAP setup is not available. Just drop a mail, if installers are available, and I'll perform the compliance tests immediately. I need at least a version for W32 (preferred) or Sun (SPARC platform). By the way: We can use the brand new VSLDAP 2.3 final release, it is out since February 12. Greetings from Hamburg, Stefan ---8--- Stefan Zoerner ([EMAIL PROTECTED]) Committer :: PMC Member Apache Directory Project http://directory.apache.org
[Release] Approx. Timeline for ApacheDS 1.5
My customer is excited about using ApacheDS as their directory server, but they want to deploy only an official build with replication capabilities. Since this functionality is planned for ApacheDS 1.5, I have been asked to understand the timeline for 1.5. I understand with ApacheDS being open source that any estimate will not be entirely accurate, but could someone give me a best guess as to when ApacheDS 1.5 will be available for official download? A few weeks, a few months? Thank you for any help you can provide. Chad Zezula Iditarod Systems
Re: [Release] Approx. Timeline for ApacheDS 1.5
Hi Chad, On 2/21/07, Chad Zezula [EMAIL PROTECTED] wrote: My customer is excited about using ApacheDS as their directory server, but they want to deploy only an official build with replication capabilities. Please be informed that although the 1.5.x branch will produce official releases the branch is intended for feature releases where we introduce new features. Although the quality of the releases will be significant since we merge bug fixes from 1.0.x into this branch it is primarily for testing new features. These features will be stabilized in the 1.6.x branch. The rule of thumb to follow with ADS releases is that even minor numbers are stable releases with bug fixes only and odd minor numbers are feature introduction releases. Since this functionality is planned for ApacheDS 1.5, I have been asked to understand the timeline for 1.5. 1.5.0 will be released soon after 1.0.1: we're talking a matter of a week or two. I understand with ApacheDS being open source that any estimate will not be entirely accurate, but could someone give me a best guess as to when ApacheDS 1.5 will be available for official download? A few weeks, a few months? Thank you for any help you can provide. Weeks is a good guess yeah. BTW thanks for responding to the dev list after contacting me personally. Alex
[ApacheDS] In preparation for 1.0.1 release: candidates available
Hi, I have the following izpack installer based jars available for testing: http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-linux-i386-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-linux-ppc-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-macosx-i386-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-macosx-ppc-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-solaris-i386-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-solaris-sparc-setup.jar Note that these installers don't have the sources and the documentation packaged into them. I will do that for the final artifacts before releasing them. More installers will follow soon: rpm and windows installers. Thanks, Alex
Re: [ApacheDS] In preparation for 1.0.1 release: candidates available
Alex Karasulu wrote: http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-solaris-i386-setup.jar Is there a workaround for this: bash-3.00# java -jar apacheds-1.0.1-solaris-i386-setup.jar Java Accessibility Bridge for GNOME loaded. - Error - java.awt.HeadlessException: No X11 DISPLAY variable was set, but this program performed an operation which requires it. java.awt.HeadlessException: No X11 DISPLAY variable was set, but this program performed an operation which requires it. at java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:159) at java.awt.Window.init(Window.java:317) at java.awt.Frame.init(Frame.java:419) at net.sourceforge.mlf.metouia.borders.MetouiaDotsBuffer.init(MetouiaDotsBuffer.java:105) at net.sourceforge.mlf.metouia.borders.MetouiaDots.init(MetouiaDots.java:66) at net.sourceforge.mlf.metouia.borders.MetouiaToolBarBorder.init(MetouiaToolBarBorder.java:49) at net.sourceforge.mlf.metouia.MetouiaLookAndFeel.initComponentDefaults(MetouiaLookAndFeel.java:241) at javax.swing.plaf.basic.BasicLookAndFeel.getDefaults(BasicLookAndFeel.java:107) at javax.swing.plaf.metal.MetalLookAndFeel.getDefaults(MetalLookAndFeel.java:1392) at javax.swing.UIManager.setLookAndFeel(UIManager.java:441) at javax.swing.UIManager.setLookAndFeel(UIManager.java:481) at com.izforge.izpack.installer.GUIInstaller.loadLookAndFeel(GUIInstaller.java:346) at com.izforge.izpack.installer.GUIInstaller.init(GUIInstaller.java:111) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at java.lang.Class.newInstance0(Class.java:350) at java.lang.Class.newInstance(Class.java:303) at com.izforge.izpack.installer.Installer.main(Installer.java:62) Regards, Graham -- smime.p7s Description: S/MIME Cryptographic Signature
Re: [ApacheDS] In preparation for 1.0.1 release: candidates available
Yeah but you need a solaris machine with a display to generate the installer script. Basically go through an install on that machine then at the end of the install there is a screen with a button that asks you if you want to create a unmanned installation file. Hit that button and generate the script. Then scp that script to the target headless machine. Then install using the following command: java -jar apacheds-1.0.1-solaris-i386-setup.jar path/to/theinstaller-file-you-created Sorry this issue is still around. I was hoping to have a solaris package available but I have not had time to whip one together. HTH, Alex On 2/21/07, Graham Leggett [EMAIL PROTECTED] wrote: Alex Karasulu wrote: http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-solaris-i386-setup.jar Is there a workaround for this: bash-3.00# java -jar apacheds-1.0.1-solaris-i386-setup.jar Java Accessibility Bridge for GNOME loaded. - Error - java.awt.HeadlessException: No X11 DISPLAY variable was set, but this program performed an operation which requires it. java.awt.HeadlessException: No X11 DISPLAY variable was set, but this program performed an operation which requires it. at java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:159) at java.awt.Window.init(Window.java:317) at java.awt.Frame.init(Frame.java:419) at net.sourceforge.mlf.metouia.borders.MetouiaDotsBuffer.init( MetouiaDotsBuffer.java:105) at net.sourceforge.mlf.metouia.borders.MetouiaDots.init(MetouiaDots.java :66) at net.sourceforge.mlf.metouia.borders.MetouiaToolBarBorder.init( MetouiaToolBarBorder.java:49) at net.sourceforge.mlf.metouia.MetouiaLookAndFeel.initComponentDefaults( MetouiaLookAndFeel.java:241) at javax.swing.plaf.basic.BasicLookAndFeel.getDefaults(BasicLookAndFeel.java :107) at javax.swing.plaf.metal.MetalLookAndFeel.getDefaults(MetalLookAndFeel.java :1392) at javax.swing.UIManager.setLookAndFeel(UIManager.java:441) at javax.swing.UIManager.setLookAndFeel(UIManager.java:481) at com.izforge.izpack.installer.GUIInstaller.loadLookAndFeel( GUIInstaller.java:346) at com.izforge.izpack.installer.GUIInstaller.init(GUIInstaller.java:111) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance( NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance( DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java :494) at java.lang.Class.newInstance0(Class.java:350) at java.lang.Class.newInstance(Class.java:303) at com.izforge.izpack.installer.Installer.main(Installer.java:62) Regards, Graham --
Re: [ApacheDS] In preparation for 1.0.1 release: candidates available
The Mac Intel (i386) installer works very well. I can now run ADS on my Mac! Thanks Alex. Regards, P-A On 2/21/07, Alex Karasulu [EMAIL PROTECTED] wrote: Hi, I have the following izpack installer based jars available for testing: http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-linux-i386-setup.jar http://people.apache.org/%7Eakarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-linux-i386-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-linux-ppc-setup.jarhttp://people.apache.org/%7Eakarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-linux-ppc-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-macosx-i386-setup.jarhttp://people.apache.org/%7Eakarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-macosx-i386-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-macosx-ppc-setup.jarhttp://people.apache.org/%7Eakarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-macosx-ppc-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-solaris-i386-setup.jar http://people.apache.org/%7Eakarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-solaris-i386-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-solaris-sparc-setup.jarhttp://people.apache.org/%7Eakarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-solaris-sparc-setup.jar Note that these installers don't have the sources and the documentation packaged into them. I will do that for the final artifacts before releasing them. More installers will follow soon: rpm and windows installers. Thanks, Alex
[jira] Created: (DIRSERVER-857) Support for MacOSX Intel
Support for MacOSX Intel Key: DIRSERVER-857 URL: https://issues.apache.org/jira/browse/DIRSERVER-857 Project: Directory ApacheDS Issue Type: Improvement Affects Versions: 1.0 Reporter: Alex Karasulu Fix For: 1.0.1 Added support with compiled jsvc on intel mac. Thanks to PAM for this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DIRSERVER-857) Support for MacOSX Intel
[ https://issues.apache.org/jira/browse/DIRSERVER-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Karasulu reassigned DIRSERVER-857: --- Assignee: Alex Karasulu Support for MacOSX Intel Key: DIRSERVER-857 URL: https://issues.apache.org/jira/browse/DIRSERVER-857 Project: Directory ApacheDS Issue Type: Improvement Affects Versions: 1.0 Reporter: Alex Karasulu Assigned To: Alex Karasulu Fix For: 1.0.1 Added support with compiled jsvc on intel mac. Thanks to PAM for this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (DIRSERVER-857) Support for MacOSX Intel
[ https://issues.apache.org/jira/browse/DIRSERVER-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Karasulu closed DIRSERVER-857. --- Resolution: Fixed Already added. Support for MacOSX Intel Key: DIRSERVER-857 URL: https://issues.apache.org/jira/browse/DIRSERVER-857 Project: Directory ApacheDS Issue Type: Improvement Affects Versions: 1.0 Reporter: Alex Karasulu Assigned To: Alex Karasulu Fix For: 1.0.1 Added support with compiled jsvc on intel mac. Thanks to PAM for this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [ApacheDS] In preparation for 1.0.1 release: candidates available
Hi Alex! I have installed the Windows version (apacheds-1.0.1-win32-setup.exe) in my environment and performed the conformance tests provided by the Open Group for LDAP certification (VSLDAP-2.3-GA, BASE profile). All tests passed. Congratulation! Greetings from Hamburg, Stefan ---8--- Stefan Zoerner ([EMAIL PROTECTED]) Committer :: PMC Member Apache Directory Project http://directory.apache.org
Re: [ApacheDS] In preparation for 1.0.1 release: candidates available
Hi Alex! Installation of ApacheDS with your candidate on Solaris 10 (SPARC) was successful. I was able to start the server vie /etc/init.d-script afterwards, connecting to the server, browsing the data, adding and manipulating data, everything looks just fine. Greetings from Hamburg, Stefan B.t.w.: Lucky me, X11 enabled :-) ---8--- Stefan Zoerner ([EMAIL PROTECTED]) Committer :: PMC Member Apache Directory Project http://directory.apache.org
Re: [ApacheDS] In preparation for 1.0.1 release: candidates available
Excellent I think we're ready. I just added a release-notes.txt into the root of the installation folders. I will just enable doc generation and the packaging of sources into the distros now then tag and release. Thanks all for making this process easier. Alex On 2/21/07, Stefan Zoerner [EMAIL PROTECTED] wrote: Hi Alex! Installation of ApacheDS with your candidate on Solaris 10 (SPARC) was successful. I was able to start the server vie /etc/init.d-script afterwards, connecting to the server, browsing the data, adding and manipulating data, everything looks just fine. Greetings from Hamburg, Stefan B.t.w.: Lucky me, X11 enabled :-) ---8--- Stefan Zoerner ([EMAIL PROTECTED]) Committer :: PMC Member Apache Directory Project http://directory.apache.org
Re: [ApacheDS] In preparation for 1.0.1 release: candidates available
The linux i386 jar installer works fine here on ubuntu 6.06 regards, Stefan Alex Karasulu schrieb: Hi, I have the following izpack installer based jars available for testing: http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-linux-i386-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-linux-i386-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-linux-ppc-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-macosx-i386-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-macosx-ppc-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-solaris-i386-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-solaris-i386-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-solaris-sparc-setup.jar Note that these installers don't have the sources and the documentation packaged into them. I will do that for the final artifacts before releasing them. More installers will follow soon: rpm and windows installers. Thanks, Alex
triplesec Javadoc broken
As documented in http://issues.apache.org/jira/browse/DIRSERVER-748 a while back, the javadoc utility has a fatal problem with the string a in a javadoc comment (an extremely annoying bug that sun hasn't bother to fix for a number of years). I was generating javadoc for a fairly out of date v 1.5 build directory and noticed a single new problem string had crept into triplesec and i'm including a patch. It's completely stupid how such a minor oversight can have such a major impact due to such an old bug! fix_javadoc.patch Description: Binary data
Re: triplesec Javadoc broken
Could you just commit the fix? Thanks, Alex On 2/21/07, Norval Hope [EMAIL PROTECTED] wrote: As documented in http://issues.apache.org/jira/browse/DIRSERVER-748 a while back, the javadoc utility has a fatal problem with the string a in a javadoc comment (an extremely annoying bug that sun hasn't bother to fix for a number of years). I was generating javadoc for a fairly out of date v 1.5 build directory and noticed a single new problem string had crept into triplesec and i'm including a patch. It's completely stupid how such a minor oversight can have such a major impact due to such an old bug!
Re: [ApacheDS] In preparation for 1.0.1 release: candidates available
Great! I just completed the deployment now. All deployables should be signed and checksummed. There should be a little delay until jars are synced up to the repo and the distros are synched to mirrors. Tomorrow we can just announce this on some MLs. Alex On 2/21/07, Stefan Seelmann [EMAIL PROTECTED] wrote: The linux i386 jar installer works fine here on ubuntu 6.06 regards, Stefan Alex Karasulu schrieb: Hi, I have the following izpack installer based jars available for testing: http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-linux-i386-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-linux-i386-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-linux-ppc-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-macosx-i386-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-macosx-ppc-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-solaris-i386-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-solaris-i386-setup.jar http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-solaris-sparc-setup.jar Note that these installers don't have the sources and the documentation packaged into them. I will do that for the final artifacts before releasing them. More installers will follow soon: rpm and windows installers. Thanks, Alex
[documentation] Mojo for Generating Checklist Guides
Hi Guys, I checked in the plugin for generating Checklist Guides and corresponding recipes. It's here. https://svn.apache.org/repos/asf/directory/sandbox/oersoy/documentation.checklist.parent There's a README.txt that explains how to use it in the parent project root directory. I had to slap the README together fast, because I'm going to be sweating in Miami and then the Caribbean for 9 days (It's going to be rough, might not make it back), starting tomorrow, and I wanted to check this in, in case some of us wanted to explore it. Anyways if you run the archetype it will generate a project containing a source directory. In the source directory are 2 files checklists.xml recipes.xml The mojo reads these and generates rest of the content for the eclipse documentation plugin created by the archetype. There is other content in the ApacheDS Contributor Guide that I created earlier, beside the checklists and the recipes. My next task is to break that guide into 2 projects. One that holds the Hand created content, along with a Master TOC (Table of Contents) and another that has the generated content. Then suck the generated content into the hand written content, using the Eclipse TOC xml structure (The master TOC). This way the generated content can evolve on it's own. Cheers, - Ole Looking for earth-friendly autos? Browse Top Cars by Green Rating at Yahoo! Autos' Green Center. http://autos.yahoo.com/green_center/
Re: [OSGi] Implementing OSGi for 1.5
On 2/9/07, Alex Karasulu [EMAIL PROTECTED] wrote: John, Doing this means committing to OSGi and I'm not going to be too comfortable with doing this until I see: ... To tell you the truth we have big concerns that overshadow the container effort right now. First on that list is multi master replication so we can make the directory and all that rests upon it fault tolerant. That does not mean I am not interested in OSGi or getting this stuff working and integrated into the main trunk. I'm sure we're going to see several benefits from using a container again. My thoughts on moving ApacheDS to OSGi: 1) I am in agreement with the priorities and timeline mentioned by Alex and Emmanuel. There are some key enterprise features the server needs first and I have a lot of clean-up, doco, and enhancements to make to the protocols myself. I think we can target June and work to get the ApacheDS house in order by then. 2) A lot has improved in OSGi-land since we first started making ApacheDS bundles with Maven 1.0. OSGi support on jcp-open was encouraging as well as support we've seen from members of the JBoss, Geronimo, Spring, and Maven communities. We'll see a lot of activity this year, making OSGi even easier to move to: 3rd-party library support, Spring support, and drastic improvements to Maven bundle plugin technology. To be honest, moving a year ago to OSGi would have been a lot of effort and I think the 3 months asked for here will allow us to get some groundwork laid in the Felix community to make this an even easier transition. 3) I think the next step is to get all of the great thinking that was in this thread into a Confluence page. Is this still the best location?: http://docs.safehaus.org/display/APACHEDS/OSGi+and+ApacheDS We can move that page over by itself, but there was some indication that the entire site was moving? Enrique
Re: [OSGi] Implementing OSGi for 1.5
Enrique, On 2/21/07, Enrique Rodriguez [EMAIL PROTECTED] wrote: On 2/9/07, Alex Karasulu [EMAIL PROTECTED] wrote: John, Doing this means committing to OSGi and I'm not going to be too comfortable with doing this until I see: ... To tell you the truth we have big concerns that overshadow the container effort right now. First on that list is multi master replication so we can make the directory and all that rests upon it fault tolerant. That does not mean I am not interested in OSGi or getting this stuff working and integrated into the main trunk. I'm sure we're going to see several benefits from using a container again. My thoughts on moving ApacheDS to OSGi: 1) I am in agreement with the priorities and timeline mentioned by Alex and Emmanuel. There are some key enterprise features the server needs first and I have a lot of clean-up, doco, and enhancements to make to the protocols myself. I think we can target June and work to get the ApacheDS house in order by then. 2) A lot has improved in OSGi-land since we first started making ApacheDS bundles with Maven 1.0. OSGi support on jcp-open was encouraging as well as support we've seen from members of the JBoss, Geronimo, Spring, and Maven communities. We'll see a lot of activity this year, making OSGi even easier to move to: 3rd-party library support, Spring support, and drastic improvements to Maven bundle plugin technology. To be honest, moving a year ago to OSGi would have been a lot of effort and I think the 3 months asked for here will allow us to get some groundwork laid in the Felix community to make this an even easier transition. 3) I think the next step is to get all of the great thinking that was in this thread into a Confluence page. Is this still the best location?: http://docs.safehaus.org/display/APACHEDS/OSGi+and+ApacheDS We can move that page over by itself, but there was some indication that the entire site was moving? It should all move but feel free to move this page into the dev section of the 1.5 space. Alex
Re: triplesec Javadoc broken
Committed single file fix and also fixed about 25% of the javadoc warnings in ApacheDS proper (sorry can't afford more time just at the moment). Note that: 1. Javadoc in JDK1.6 (finally) has the fatal error on encountering a malformed a link within a javadoc comment fixed, so it's worth using it when debugging javadoc problems 2. Two errors are still reported at the end of the javadoc run, but it's impossible to tell which of the 350 odd remaining warnings they relate too. I was building the javadoc via my IDE so I'm not sure whether Maven will be upset by whatever is causing these errors or not.
