Skip navigation
471 Views 5 Replies Latest reply: Jan 26, 2012 1:34 AM by Nathan Sowatskey RSS
Nathan Sowatskey Bronze 37 posts since
Nov 2, 2011
Currently Being Moderated

Jan 23, 2012 2:51 AM

Where is the code being maintained?

Hi

 

I just went to check the diffs between my local Subversion copy of the code and the repot at http://svn.igniterealtime.org/svn/repos/smack.

 

There are no incoming changes, which seems odd to me as the code is being maintained, and I haven't updated my copy of the code since before Christmas.

 

So, where is the latest code, if it is not at the repo link above, please?

 

Many thanks

 

Nathan

  • Flow Silver 97 posts since
    Jan 11, 2007
    Currently Being Moderated
    Jan 25, 2012 9:04 AM (in response to Nathan Sowatskey)
    Where is the code being maintained?

    I'm only aware of http://fisheye.igniterealtime.org/browse/smack

     

    Maybe one of the offical dev's could bring some light into this.

  • rcollier KeyContributor 600 posts since
    Mar 4, 2009
    Currently Being Moderated
    Jan 25, 2012 10:14 AM (in response to Nathan Sowatskey)
    Where is the code being maintained?

    You aren't seeing any updates since the most active development is for 3.2.2, which is happening on a branch. 

     

    You will see an update when that is merged into trunk, or other changes that are already occuring on trunk are committed.

      • rcollier KeyContributor 600 posts since
        Mar 4, 2009
        Currently Being Moderated
        Jan 25, 2012 12:37 PM (in response to Nathan Sowatskey)
        Where is the code being maintained?

        No further development should be done on 3.2.2.  It would be released already if there weren't a few test cases failing

         

        Once those are fixed, that branch will be effectively closed.  I want new development to occur on trunk towards 3.3.  I am not sure you should try the maven route yet though, I already have it pretty much mavenized in a workspace at home (from last year).  Problem is that the current build actually includes the classes from some other jars as part of the deployment, which in a maven world should be a dependency.  This is not a major issue, but in addition to that I have been thinking about some changes to the artifacts that are being produced.  This is something that I would only want to do in a 4.0 release. 

         

        I have been putting off converting to Maven while I think about a road map for the future.

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points