#7 Split out jazzy from SpellChecker

Other (7)
Rob Manning

I am working on getting your latest (1.4.1) artifacts up on Maven Central. The classes com.swabunga.* contained in the SpellChecker project are essentially jazzy-0.5.2 + bug-fixes and enhancements. While hosting them in the same project with the SpellChecker source code is fine from an open source point of view, it's not so great for Maven. It would be nice if you created a separate top-level project in subversion for jazzy enhancements. Currently, I am listing the browse-able scm repo as: http://svn.fifesoft.com/viewvc-1.0.5/bin/cgi/viewvc.cgi/SpellChecker/trunk/src/com/?root=RSyntaxTextArea
and the url for checking out the source code as: http://svn.fifesoft.com/svn/RSyntaxTextArea/SpellChecker/trunk/src/com/. I was thinking something more along the lines of:




  • Robert Futrell

    Robert Futrell - 2010-05-07

    Hi Rob,

    Thanks for looking into this! I was curious about adding RSTA to Maven, but I've never used it before and can't find the time to really look into it.

    About splitting the SpellChecker into two projects - can you explain why this is beneficial for Maven? I can certainly look into it, but I must admit I like the simplicity of having the modified Jazzy included in the SpellChecker project proper, especially since SpellChecker isn't really "pluggable" and will currently only work with Jazzy. If it could work with other spelling engines I'd be (slightly :) ) more motivated to do the splitting up.

    Is it possible, in the meantime, to get the main RSyntaxTextArea project by itself into Maven? And possibly AutoComplete as well? Not to sound bossy, I'm super grateful you're looking into this on your own. Let me know if there's anything I can do on the project end to get these two into Maven, just to get the ball rolling, and then we can look into SpellChecker after that?


  • Rob Manning

    Rob Manning - 2010-05-07


    "About splitting the SpellChecker into two projects - can you explain why
    this is beneficial for Maven?"

    I have already split up your jazzy enhancements into a separate Maven artifact (http://repo2.maven.org/maven2/net/sf/jazzy/jazzy/0.5.2-rtext-1.4.1/). The change that I requested for the subversion repository is a metatdata consistency fix for the pom file. Notice that the version indicates that this isn't an "official" jazzy release, but one that was done specifically for the RText project.

    The reason that it is important to make distinct artifacts is that if this is done correctly, Maven can then tell you when your transitive dependencies are in conflict (Suppose your project depends on artifacts A and B. Further suppose A depends on artifact X version 1 and B depends on artifact X version 2, and these are all runtime dependencies. Maven can tell you when this type of conflict occurs. Your CLASSPATH can only ever contain one version of each class file, so obviously it's a problem; without Maven, you just may never realize the problem until you run into classloader issues.) If not done correctly, and instead you bundle Artifact A with your artifact, then a project that depends on your artifact will "get" artifact A, and Maven doesn't know it, and cannot properly analyze the dependencies, and so cannot spot this kind of problem.

    I have already uploaded your latest releases and your December releases of all of your projects (http://repo2.maven.org/maven2/com/fifesoft/). Let me know when you make a new release and I'd be happy to work with you to get the new artifacts uploaded.



  • Robert Futrell

    Robert Futrell - 2010-05-13

    Thanks for clearing that up for me. I see now that Maven is trying to prevent transitive dependency problems, and me using Jazzy in the way I am isn't helping. :)

    Also, thanks for adding the other RSTA projects to Maven! It's something I wanted to do myself for awhile now. I'll contact you when there are new releases. Let me know if there's anything else I can do to facilitate RSTA's use in Maven.

  • Rob Manning

    Rob Manning - 2010-11-24

    Hello again,

    I am trying to get RText version 1.3.0 into Maven Central and I noticed a new dependency on org.fife.rsta.ac.LanguageSupport (and others) which I did not find in the RText source archive, but managed to track down here: http://svn.fifesoft.com/viewvc-1.0.5/bin/cgi/viewvc.cgi/RSTALanguageSupport/?root=RSyntaxTextArea. It's unfortunate that there are no tags for this new project, so I am left to conclude that svn revision 239 was the last checkin before 10/21/10 when the RText source archive was created (or at least uploaded to SourceForge). Can you tell me if this "release" of org.fife.rsta.ac.* has a version number associated with it other than revision 239 ?


  • Robert Futrell

    Robert Futrell - 2010-12-01

    Just a note that I contacted Rob via email to try to hash out the version numbers used by RText 1.3.0 (and 1.3.1). It should be revision 239 for the RSTA projects for RText 1.3.0, and revision 241 for RText 1.3.1.

  • Rob Manning

    Rob Manning - 2010-12-01

    I'll be sure to use the revisions you have specified to checkout the source. I'll also use those revision numbers as the version for the artifacts that get pushed to Maven Central. Thanks for clarifying this info.


  • Robert Futrell

    Robert Futrell - 2011-08-28
    • status: open --> closed-fixed
  • Robert Futrell

    Robert Futrell - 2011-08-28

    Closing since I've moved the com.swabunga.* classes in the spellchecker project into a new package, org.fife.com.swabunga.*. This should prevent clashes if any project is using both RSTA and the original Jazzy.


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks