jamwiki-devel Mailing List for JAMWiki
Brought to you by:
wrh2
This list is closed, nobody may subscribe to it.
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(45) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2011 |
Jan
(53) |
Feb
(23) |
Mar
(6) |
Apr
(2) |
May
(5) |
Jun
(1) |
Jul
(2) |
Aug
(2) |
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
2012 |
Jan
(7) |
Feb
(2) |
Mar
(1) |
Apr
|
May
(7) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
(1) |
Feb
(5) |
Mar
(54) |
Apr
(7) |
May
(1) |
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Ryan H. <rya...@gm...> - 2015-07-13 04:38:50
|
Hi Audrius, It's been more than two years since the last JAMWiki release and I've been debating what to do with the project, so it's great that you're interested in it. One thing I've been thinking about is that, rather than continuing on with the project under the same name, it might make the most sense to continue the project by creating a fork of the existing code & documentation under a new name - call it JAMWiki2, JAMWikiNext, or start fresh with a name that doesn't include "JAMWiki" at all. That would allow you to push forward with whatever vision you have for the project and allow some freedom from supporting old code and requirements, and would also make it clear that the project is moving in a new direction. Would that make sense to you? I can make it clear on jamwiki.org and the JAMWiki Sourceforge page that your project is an "approved" and active fork, and eventually just redirect JAMWiki traffic to your project. I could also provide some assistance in the initial setup if desired. While I would love to personally continue developing JAMWiki, the balance between the amount of time required to produce a quality product and the benefit provided vs. other available solutions is something I can no longer justify, so if the project can continue in some way under another person or group's leadership I am excited to support that endeavor. Please let me know your thoughts. Ryan On 7/12/2015 10:00 AM, Audrius Meskauskas wrote: > Hello, Ryan, hello, list, > > You have asked, if anybody would like to take over JAMWiki development > and maintenance. Ok, me the great ... > > I am the initiator of Ultrastudio.org project which used a fork 0.8.4. I > have made many various changes in the code, including some security > hardening, but did not contribute back upstream at that time as most of > changes required were way too specific of my focused goals and I was not > paying attention to be generic enough (PostgreSQL only and so on). > Ultrastudio.org, if somebody is interested in, was a project to build a > Wikipedia-like encyclopedia with Java applets easily enabled, addressing > security through server side applet compilation after public code review > and automated security scan. We operated for a few years with some > limited success but have no technical possibility to continue after > Oracle just disabled unsigned applets. The server is still running in a > read only mode now. > > Successful or not, this project gave me significant experience with > JamWiki code, I am fully comfortable with the build system and project > layout, so probably could take over development and maintenance. My > primary focus would be keeping up with the newer technologies where > available (Java 8, Google Guava, we may later try something more > sophisticated like Cassandra for the storage) and further hardening > security, and also maybe some Selenium tests. Also, if it would be > enough interest from the side, in the future may be good to migrate the > code into GitHub, doing further development through pull requests and > code review. > > I will discuss my changes with you, as long a you may have time for > this, and will listen carefully if you oppose on serious grounds, but I > also would like to have certain freedoms as well. You have asked > somebody for taking over and I mean exactly this. To indicate the > possible major alterations, we may increment the major version number. > > I am Java developer with researcher background. I started to program in > this language when it first came long time ago, use Java heavily at work > and at some time have contributed over 100 000 LOC to GNU Classpath. I > plan to work on JAMWiki as on the hobby project without ambitions to > make business or fame out of it. I think it should be an "ecologic > niche" for a good and simple Java Wiki on the world as MediaWiki > basically dictates all your server architecture (must be LAMP) and > Confluence is horribly expensive to try anything more serious with it, > leave alone it is closed source. Also, I do not take removing from > Wikipedia into serious consideration as this was part of the some > strongly pushed process that also removed high quality commercial tools > like Magnolia or Jahia, probably just to show there is no any notable > Java wiki engine remaining. > > > With respect > Audrius > > > _______________________________________________ > Jamwiki-devel mailing list > Jam...@li... > https://lists.sourceforge.net/lists/listinfo/jamwiki-devel > |
From: Audrius M. <aud...@me...> - 2015-07-12 18:26:02
|
The proposed patch joins together edits by the same user and topic in the recent changes list, displaying them as one. Many people have difficulties in committing edits in one change. They make an edit, read for a few minutes, then apply one change, and after some time another one, and more. With more users and activity this quickly clutters the recent changes page. Usually moderators are not much interested in these intermediate edits and prefer to see the final difference made by the particular contributor. The proposed alteration of RecentChangesServlet shows different edits only as long as the topic or the user is different. Multiple continuos edits by the same user and topic are considered the same. To create this the patch, I have merged in the ServletUtil.buildVirtualWikiLinks call that is from the later versions than Ultrastudio.org has been forked and changed the visibility to of handleJamWikiRequest (kinda used to be protected?). This code initially belonged to Ultrastudio.org and worked fine there for a long time. For peace of mine I have made a test build and deployment of the modified version, seems working as expected. The patch is against the current trunk. Audrius |
From: Audrius M. <aud...@me...> - 2015-07-12 17:14:24
|
Hello, Ryan, hello, list, You have asked, if anybody would like to take over JAMWiki development and maintenance. Ok, me the great ... I am the initiator of Ultrastudio.org project which used a fork 0.8.4. I have made many various changes in the code, including some security hardening, but did not contribute back upstream at that time as most of changes required were way too specific of my focused goals and I was not paying attention to be generic enough (PostgreSQL only and so on). Ultrastudio.org, if somebody is interested in, was a project to build a Wikipedia-like encyclopedia with Java applets easily enabled, addressing security through server side applet compilation after public code review and automated security scan. We operated for a few years with some limited success but have no technical possibility to continue after Oracle just disabled unsigned applets. The server is still running in a read only mode now. Successful or not, this project gave me significant experience with JamWiki code, I am fully comfortable with the build system and project layout, so probably could take over development and maintenance. My primary focus would be keeping up with the newer technologies where available (Java 8, Google Guava, we may later try something more sophisticated like Cassandra for the storage) and further hardening security, and also maybe some Selenium tests. Also, if it would be enough interest from the side, in the future may be good to migrate the code into GitHub, doing further development through pull requests and code review. I will discuss my changes with you, as long a you may have time for this, and will listen carefully if you oppose on serious grounds, but I also would like to have certain freedoms as well. You have asked somebody for taking over and I mean exactly this. To indicate the possible major alterations, we may increment the major version number. I am Java developer with researcher background. I started to program in this language when it first came long time ago, use Java heavily at work and at some time have contributed over 100 000 LOC to GNU Classpath. I plan to work on JAMWiki as on the hobby project without ambitions to make business or fame out of it. I think it should be an "ecologic niche" for a good and simple Java Wiki on the world as MediaWiki basically dictates all your server architecture (must be LAMP) and Confluence is horribly expensive to try anything more serious with it, leave alone it is closed source. Also, I do not take removing from Wikipedia into serious consideration as this was part of the some strongly pushed process that also removed high quality commercial tools like Magnolia or Jahia, probably just to show there is no any notable Java wiki engine remaining. With respect Audrius |
From: 芮元生 <ys...@cf...> - 2015-04-03 03:19:55
|
Hello,I’m learning JAMWiki. I download the war file and source code of of JAMWiki1.2.4.but I found there are some difference between the war file and source code. As you can see in the pictue,I cannot find JAMWIKILexer.java in source code, so there are some errors in my project.but it have JAMWIKILexer.class in the war file As I download source code of other versions,they also have this question. Does I am wrong or it miss some classes actually? I will very happy to hearing from you,thank you for your excellent work. |
From: Ryan H. <rya...@gm...> - 2014-10-18 15:55:34
|
Hi Charles, Ideally JAMWiki would continue on as it has for the past eight years, but the reality is that I haven't pushed a release in more than a year, and it's both dangerous and unfair to keep software in the wild that isn't being properly maintained. I spent some time thinking about whether it made sense to focus significant effort on continuing the project, and while I would agree that there are advantages to having a Java wiki that is similar in features to Mediawiki, the truth is that Mediawiki has made great strides in ease-of-installation and other facets, and thus I think the future of JAMWiki would be limited at best. If I had more time and motivation I would probably continue the project solely because I enjoy the development, but given time constraints and other factors I'm simply not up to the task. As noted in the previous email, perhaps someone will choose to fork the code and continue the project, but for my part I think it's time to step away from what has been a very enjoyable and educational effort. Thanks for your kind words about the project - if you should ever decide you want to continue development please let me know how I could help. Ryan On 10/14/2014 1:07 AM, Charles Clavadetscher wrote: > Hello Ryan > > I guess that this was not an easy decision to take. I am still very fond > of the JAMWiki software and still use it for my homepage > (http://www.schmiedewerkstatt.ch). Unfortunately I am still not in the > position to contribute and even less to take over. Apart from the > contributions that I made my knowledge of the system as a whole is too > small. Of course, if there will be somebody taking ownership I would be > interested in keeping tuned. My situation may change in the future in > terms of contribution time. > > MediaWiki is PHP and although quite mature a bit a question of taste, if > one uses it or not. Confluence, as far as I could see in a quick search > is commercial software. So in my case, it would not even make it into > the narrow list of candidates for the choice of a Wiki software. > > I'd like to thank you anyway for all the effort that you have put into > the project and I hope that everything is ok. > I wish you a good time. > Bye > Charles > > ------------------------------------------------------- > Charles Clavadetscher > Motorenstrasse 18 > CH - 8005 Zurich > > http://www.schmiedewerkstatt.ch > ------------------------------------------------------- > > On 10/13/2014 06:01 PM, Ryan Holliday wrote: >> Hello, >> >> The last JAMWiki release occurred more than a year and a half ago (March >> 2013), and at this point I think it is appropriate to announce the >> end-of-life for the project. It isn't right to continue a project when >> updates and fixes aren't being released. Additionally, the primary >> purpose for JAMWiki when the project started nearly ten years ago was to >> provide a good Java wiki with many of the features of Mediawiki, but >> today Mediawiki is vastly easier to use and install, and Confluence >> provides a Java wiki meets the needs of those who want a Java wiki. >> >> The code remains open source (LGPL), and is available to anyone who >> wants to use it provided they follow the attribution requirements. If >> someone wants to take over ownership of the project we can discuss, >> although if that happens it would probably be better to fork and adopt a >> new name to avoid any confusion. I'll leave the source repository >> intact on Sourceforge, and will likely continue to host jamwiki.org for >> a while so that documentation remains available, but at this point I do >> not have any plans for future releases. >> >> Thank you to everyone who has used JAMWiki and helped with the project >> over the years - I've learned a lot and had a lot of fun developing it. >> >> Ryan Holliday >> >> ------------------------------------------------------------------------------ >> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports >> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper >> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer >> http://p.sf.net/sfu/Zoho >> _______________________________________________ >> Jamwiki-devel mailing list >> Jam...@li... >> https://lists.sourceforge.net/lists/listinfo/jamwiki-devel > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > Jamwiki-devel mailing list > Jam...@li... > https://lists.sourceforge.net/lists/listinfo/jamwiki-devel > |
From: Charles C. <cha...@bl...> - 2014-10-14 08:07:15
|
Hello Ryan I guess that this was not an easy decision to take. I am still very fond of the JAMWiki software and still use it for my homepage (http://www.schmiedewerkstatt.ch). Unfortunately I am still not in the position to contribute and even less to take over. Apart from the contributions that I made my knowledge of the system as a whole is too small. Of course, if there will be somebody taking ownership I would be interested in keeping tuned. My situation may change in the future in terms of contribution time. MediaWiki is PHP and although quite mature a bit a question of taste, if one uses it or not. Confluence, as far as I could see in a quick search is commercial software. So in my case, it would not even make it into the narrow list of candidates for the choice of a Wiki software. I'd like to thank you anyway for all the effort that you have put into the project and I hope that everything is ok. I wish you a good time. Bye Charles ------------------------------------------------------- Charles Clavadetscher Motorenstrasse 18 CH - 8005 Zurich http://www.schmiedewerkstatt.ch ------------------------------------------------------- On 10/13/2014 06:01 PM, Ryan Holliday wrote: > Hello, > > The last JAMWiki release occurred more than a year and a half ago (March > 2013), and at this point I think it is appropriate to announce the > end-of-life for the project. It isn't right to continue a project when > updates and fixes aren't being released. Additionally, the primary > purpose for JAMWiki when the project started nearly ten years ago was to > provide a good Java wiki with many of the features of Mediawiki, but > today Mediawiki is vastly easier to use and install, and Confluence > provides a Java wiki meets the needs of those who want a Java wiki. > > The code remains open source (LGPL), and is available to anyone who > wants to use it provided they follow the attribution requirements. If > someone wants to take over ownership of the project we can discuss, > although if that happens it would probably be better to fork and adopt a > new name to avoid any confusion. I'll leave the source repository > intact on Sourceforge, and will likely continue to host jamwiki.org for > a while so that documentation remains available, but at this point I do > not have any plans for future releases. > > Thank you to everyone who has used JAMWiki and helped with the project > over the years - I've learned a lot and had a lot of fun developing it. > > Ryan Holliday > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://p.sf.net/sfu/Zoho > _______________________________________________ > Jamwiki-devel mailing list > Jam...@li... > https://lists.sourceforge.net/lists/listinfo/jamwiki-devel |
From: Ryan H. <rya...@gm...> - 2014-10-13 16:01:10
|
Hello, The last JAMWiki release occurred more than a year and a half ago (March 2013), and at this point I think it is appropriate to announce the end-of-life for the project. It isn't right to continue a project when updates and fixes aren't being released. Additionally, the primary purpose for JAMWiki when the project started nearly ten years ago was to provide a good Java wiki with many of the features of Mediawiki, but today Mediawiki is vastly easier to use and install, and Confluence provides a Java wiki meets the needs of those who want a Java wiki. The code remains open source (LGPL), and is available to anyone who wants to use it provided they follow the attribution requirements. If someone wants to take over ownership of the project we can discuss, although if that happens it would probably be better to fork and adopt a new name to avoid any confusion. I'll leave the source repository intact on Sourceforge, and will likely continue to host jamwiki.org for a while so that documentation remains available, but at this point I do not have any plans for future releases. Thank you to everyone who has used JAMWiki and helped with the project over the years - I've learned a lot and had a lot of fun developing it. Ryan Holliday |
From: Keith F. <fog...@ya...> - 2014-05-14 10:21:59
|
Hi JAMWiki-developers, I was hoping you may be able to help. I'm working on a MSc. thesis and am looking to distinguish java Open Source Test-First/Test-Driven Development and Test-Last projects for a research experiment. To this end I was hoping that contributors to JAMWiki would consider filling out the short linked survey (12 questions) for this project (or any other open source java project you are involved in)? My research will look at and compare design pattern usage in Test-First and Test-Last projects in relation to effectiveness and design quality. If you would be interested in learning more about the project or its findings please enter your details in the comment box on the survey and I will contact you once the project is complete. I intend to use the results of the survey solely for the purposes of the dissertation. Individual contributors will not be named in any reporting of the project. If you do not wish your project to be identified you can indicate so in the survey and its name will be masked. Many thanks in advance; your help is very much appreciated. Keith Fogarty Link to survey: https://docs.google.com/a/mydit.ie/forms/d/160CG5J_LJM3cAbSUrtfzka55vTrAeUwL4o-PvsY8Wkw/viewform Open Source Software Project Survey Hi, I was hoping you may be able to help me. I'm currently working on an M.Sc. Thesis and require a number of Test-First and Test-Last subject projects as part o... View on docs.google.com Preview by Yahoo |
From: Ryan H. <rya...@gm...> - 2013-07-28 07:35:30
|
Is Tomcat 5.5 specified somewhere on the wiki or in the documentation included in the JAMWiki documentation? If so, requirements should instead be expressed in terms of the JSP/servlet specification required, currently servlet 2.5 and JSP 2.1 (see http://jamwiki.org/wiki/en/Installation#Prerequisites). If there is somewhere that specifies a specific Tomcat version then that should be updated. Ryan On 7/26/2013 11:51 PM, Thomas Koch wrote: > Hi Ryan, > > should JAMWiki also raise the minimum tomcat version at least to 6? > http://wiki.apache.org/tomcat/TomcatVersions > > Any updates (even security fixes) to tomcat 5.5 are "highly unlikely". > > Regards, > > Thomas Koch, http://www.koch.ro > |
From: Thomas K. <th...@ko...> - 2013-07-27 06:51:29
|
Hi Ryan, should JAMWiki also raise the minimum tomcat version at least to 6? http://wiki.apache.org/tomcat/TomcatVersions Any updates (even security fixes) to tomcat 5.5 are "highly unlikely". Regards, Thomas Koch, http://www.koch.ro |
From: Ryan H. <rya...@gm...> - 2013-07-26 21:17:25
|
Hi Thomas, The work-in-progress code for JAMWiki 2.0 already includes a move to Java 6, although I've sadly not had much time available for development work lately. The master branch has all changes that are planned for 2.0, and http://jamwiki.org/wiki/en/Tech:JAMWiki_2.0 has some details about features that may be included in the next major release. The next major release won't be ready for the September deadline in the document you've linked to, but if there is still a way to include JAMWiki please go ahead and do so. Ryan On 7/26/2013 1:50 PM, Thomas Koch wrote: > There's a collective effort of free software projects to move to java6: > > https://docs.google.com/document/d/1pi8OsiG-hPDjqSge4xqmpZTshryUkMdF4QLBeCf0GXo/edit?pli=1 > > Jamwiki could join? > > (I'm sorry that I did not have the time to start contributing to Jamwiki in > the last months as I intended. Especially since jamwiki finally moved to Git.) > > Regards, > > Thomas Koch, http://www.koch.ro > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Jamwiki-devel mailing list > Jam...@li... > https://lists.sourceforge.net/lists/listinfo/jamwiki-devel > |
From: Thomas K. <th...@ko...> - 2013-07-26 20:50:24
|
There's a collective effort of free software projects to move to java6: https://docs.google.com/document/d/1pi8OsiG-hPDjqSge4xqmpZTshryUkMdF4QLBeCf0GXo/edit?pli=1 Jamwiki could join? (I'm sorry that I did not have the time to start contributing to Jamwiki in the last months as I intended. Especially since jamwiki finally moved to Git.) Regards, Thomas Koch, http://www.koch.ro |
From: Ryan H. <rya...@gm...> - 2013-05-19 05:04:14
|
Hi All, The jamwiki.org server died tonight. Another machine is on order, but jamwiki.org will likely be unavailable until it arrives some time next week. Sorry for any inconvenience. Ryan |
From: Ryan H. <rya...@gm...> - 2013-04-24 03:38:06
|
I'm a bit late, but the plan is to release the next JAMWiki bugfix release in the coming week. If you've got a fix or translation update for this release please be sure to get it committed soon. This will be the first release since switching to Git, so if anyone is aware of any changes required to make the Maven release plugin work with Git please let me know - see http://jamwiki.org/wiki/en/User:wrh2/Notes for the process I usually use when pushing a new release. Ryan |
From: Thomas K. <th...@ko...> - 2013-04-07 19:45:17
|
Hi, I wanted to apply my HTML fixes to the 1.3.x branch (worked) and than merge it the 1.3.x brannch to master. The latter resulted in merge conflicts in all pom.xml files due to both branches having changed the version number. This is a very common problem with Maven and any VCS (not only Git). I've already sent a mail to the git mailing list to ask for best practice advice: http://comments.gmane.org/gmane.comp.version-control.git/220319 I naively thought, that I could find some way to declare the version only once in the parent pom. But I had to learn that I don't know too much about maven. It's not possible. This is a long standing, nagging bug of Maven: http://docs.codehaus.org/display/MAVENUSER/EasyVersionMaintenance Dealing with the pom.xml version changes actually isn't that hard in git. In merge commit bd649210896 I've merged two commits the only updated version information from the 1.3.x branch into the master branch. I used the "ours" strategy: "git merge -s ours 875d0". This essentially ignored the changes introduced by those two commits and only marked them as merged. Now I (we) have to figure out how to deal with the CHANGELOG.txt and UPGRADE.txt. It would have been easier, if the edit to UPGRADE.txt would have been in a separate commit. Just for my own reference (and your curiousity) I'm listing the interesting search results for the merge issue: others who have the same issue: http://stackoverflow.com/questions/6109814/when-should-mvn-release-be-used-in- the-project-lifecycle stackoverflow.com/questions/3555160/merging-changes-from-a-maven-relase- branch-yields-conflicts-due-to-changed-versiP https://github.com/SpringSource/spring-framework/pull/224 http://stackoverflow.com/questions/12197191/git-merge-conflict-only-on- version-tag-in-pom-xml http://ceki.blogspot.ch/2006/11/solution-to-maven2-version-number.html the same in mercurial and solution to use merge tool configuration http://stackoverflow.com/questions/10178733/mercurial-merge-auto-merging- certain-conflict-patterns perl script to solve version merge conflicts https://bitbucket.org/jwalton/git-scripts/src/06ced9820a91/resolve-maven- version-conflicts.pl maven plugin to deal with version conflicts on git-flow style workflows: https://github.com/lukepfarrar/gitflow-maven-plugin Thomas Koch, http://www.koch.ro |
From: Ryan H. <rya...@gm...> - 2013-04-06 19:36:33
|
Hi Thomas, In the past the process for release branches was to commit release code directly to the branch and then merge that branch back to master. In some cases changes were backported from master, but in general I've found that it's safer to commit the fix to the release branch and then merge. This is the process I've used at a number of jobs, and many open source projects use it as well, so it should be fairly robust. I haven't yet merged the latest 1.3.x changes to master, but aside from the category initialization fix most of them were just updating the version number to 1.3.2, something that will be irrelevant for a branch destined to become 2.0.0. And yes, I can switch to single line commit messages - the current format is a holdover from the Subversion days where the format was "area of commit" followed by a bullet list of changes. Updating progress on my own development work, I've been working on updates to the database code to simplify connection and transaction management by using the Spring JdbcTemplate and TransactionTemplate classes, and will hopefully have that code ready for review soon. The database code has always been a somewhat of a mess, so hopefully these changes will simplify things and fix some transaction issues in the process. Ryan |
From: Ryan H. <rya...@gm...> - 2013-04-06 19:28:26
|
Hi Thomas, These all look very straightforward - feel free to merge to master at your leisure, and also merge to 1.3.x as some of them fix potential HTML issues. The only very minor request I have is that if your edit can be set to trim trailing whitespace there are a few places where commits added extra tabs or space characters at the ends of lines. Ryan On 4/6/2013 6:40 AM, Thomas Koch wrote: > Mostly very small trivial cleanups. The last commit is a step towards changes > feed with diffs. > > 8b5b42d Extract feed entry description creation in separate function > e862900 use static helper methods url{En|De}codeUtf8 > 0072ee1 remove unused variable > 033bcf2 access static members statically, not with this. > dac898d remove some unused java imports > a3132fc remove unused variable > 7004e99 HTML fix: input tags were not closed > a552bec fix missing equals sign after html attribute > 46beec6 Fix invalid <p> in <span> tag > > Please be so kind and review and merge to master. > > Regards, > > Thomas Koch, http://www.koch.ro > > ------------------------------------------------------------------------------ > Minimize network downtime and maximize team effectiveness. > Reduce network management and security costs.Learn how to hire > the most talented Cisco Certified professionals. Visit the > Employer Resources Portal > http://www.cisco.com/web/learning/employer_resources/index.html > _______________________________________________ > Jamwiki-devel mailing list > Jam...@li... > https://lists.sourceforge.net/lists/listinfo/jamwiki-devel > |
From: Thomas K. <th...@ko...> - 2013-04-06 13:41:01
|
Mostly very small trivial cleanups. The last commit is a step towards changes feed with diffs. 8b5b42d Extract feed entry description creation in separate function e862900 use static helper methods url{En|De}codeUtf8 0072ee1 remove unused variable 033bcf2 access static members statically, not with this. dac898d remove some unused java imports a3132fc remove unused variable 7004e99 HTML fix: input tags were not closed a552bec fix missing equals sign after html attribute 46beec6 Fix invalid <p> in <span> tag Please be so kind and review and merge to master. Regards, Thomas Koch, http://www.koch.ro |
From: Thomas K. <th...@ko...> - 2013-04-06 09:53:17
|
Hi Ryan, I just saw 3 new commits on the 1.3.x branch and was a bit puzzled not to also see them in master. First I wanted to complain but then I first read the manpage on gitworkflows[1]. So you did it perfectly correct and I'm just used to a workflow that only applies for internal web projects without old versions that still need maintenance. [1] https://www.kernel.org/pub/software/scm/git/docs/gitworkflows.html Just one nit-picking: Could you please use the first line in commit messages for a short summary? That's a generally followed standard. Many tools only show the first commit message line for a quick overview and it's not that informative to just read "Bugfix:" there. A search for "commit message" reveals the guidelines of different projects. The linux kernel guidelines is found in [2] in section 15. [2] https://www.kernel.org/doc/Documentation/SubmittingPatches Two more often cited and good texts on git commit messages: https://wiki.openstack.org/wiki/GitCommitMessages http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html I'll review my own patches now for that and push them in a separate branch for review and merge. Regards, Thomas Koch, http://www.koch.ro |
From: Ryan H. <rya...@gm...> - 2013-04-02 02:46:23
|
I've pushed the release branches that were on Github to Sourceforge. Let me know if anything seems incorrect - I followed instructions from http://stackoverflow.com/questions/11266478/git-add-remote-branch I've had limited time available for JAMWiki development lately, although I'll be flying the next few days and tend to get things done when I'm stuck in airports. I've got a number of things I'd like to look into for 2.0, including simplifying upgrades and making it easier to use parts of the JAMWiki codebase (such as the parser) in other applications. Ryan On 3/24/2013 12:57 PM, Thomas Koch wrote: > Hi Ryan, Peter, > > I have pushed master and all tags now. |
From: Ryan H. <rya...@gm...> - 2013-03-27 03:16:28
|
Emails should be sent to jamwiki-commit again. For reference, here are the steps taken to get this working: Copy https://sourceforge.net/apps/trac/sourceforge/wiki/Git%20hook%20script%20example to /home/git/p/jamwiki/code.git/hooks/post-receive-user chmod a+x post-receive-user git config --add hooks.mailinglist jam...@li... Make the content of the /home/git/p/jamwiki/code.git/description file "JAMWiki". |
From: Ryan H. <rya...@gm...> - 2013-03-26 15:09:50
|
Hi, The /home/git/p/... directory is present this morning, so perhaps it just takes some time after the project is updated for it to appear. I'll get the email hook set up later tonight. For future reference, if I'm reading the docs correctly then everyone with the developer role should also have shell access - see https://sourceforge.net/p/forge/documentation/SSH/. Ryan |
From: Peter P. <pit...@us...> - 2013-03-26 07:05:32
|
Hi, Am 26.03.2013 um 05:41 schrieb Ryan Holliday <rya...@gm...>: > As Thomas noted, Sourceforge has been nagging me for some time to > upgrade the JAMWiki project on the Sourceforge site. That is done now, Thanks! I've pushed a commit to "pom.xml" to reflect the new URLs. -- Regards, Peter |
From: Peter P. <pit...@us...> - 2013-03-26 07:03:45
|
Hi Ryan, Am 26.03.2013 um 07:03 schrieb Ryan Holliday <rya...@gm...>: > Hi, > > On 3/25/2013 12:44 AM, Peter Palmreuther wrote: >> Did so, but I saw no commit message on jamwiki-commit. > > I spent some time tonight trying to setup the email hook as described at https://sourceforge.net/apps/trac/sourceforge/wiki/Git#Commitemailhooksetup and https://sourceforge.net/p/forge/documentation/Git/, but there isn't a /home/git directory on the shell. I'll need to revisit this at a later point, although if either of you have any suggestions I'd be grateful for the pointers. I don't have plain shell access on SF, but the first link you provide tells about "/home/scm_git" ... Maybe it's a typo in SF Git docs? If you can provide me temporary shell access to the project I can have a look for what's maybe "wrong" ... -- Regards, Peter |
From: Ryan H. <rya...@gm...> - 2013-03-26 06:03:30
|
Hi, On 3/25/2013 12:44 AM, Peter Palmreuther wrote: > Did so, but I saw no commit message on jamwiki-commit. I spent some time tonight trying to setup the email hook as described at https://sourceforge.net/apps/trac/sourceforge/wiki/Git#Commitemailhooksetup and https://sourceforge.net/p/forge/documentation/Git/, but there isn't a /home/git directory on the shell. I'll need to revisit this at a later point, although if either of you have any suggestions I'd be grateful for the pointers. Ryan |