- 14 Nov, 2017 3 commits
-
-
akrherz authored
command form this time was git ls-files '*.jsp' | while read f; do tail -n1 $f | read -r _ || echo >> $f; done
-
akrherz authored
the command line form was find . -name '*.jsp' ! -type d -exec bash -c 'expand -i -t 4 "$0" > /tmp/e && mv /tmp/e "$0"' {} \;
-
akrherz authored
all done via the magic of dos2unix
-
- 01 Oct, 2017 1 commit
-
-
Dele Olajide authored
* jmxweb plugin version 0.0.7 * jmxweb plugin - updated date
-
- 25 May, 2017 2 commits
-
-
Guus der Kinderen authored
This commit copies version number, author and description from plugin.xml to pom.xml. This makes the same information available as Maven metadata. When Ant support is dropped, the duplicate data in the plugin.xml should be replaced by a filter (which takes the data from the pom.xml).
-
Guus der Kinderen authored
I continue to be thoroughly confused by having two directories per plugin, one for the plugin sources, and one for the maven build. This commit merges both directories. As a side effect, various plugin unit tests are now executed by default. Some failed, for which I applied fixes. This commit also adds some plugins to the Maven structure that previously were not.
-
- 08 May, 2017 1 commit
-
-
Guus der Kinderen authored
The Openfire plugin developer guide states that 'additinal' files should be in /classes/. Apparently, the old Ant script also included any files in the /src/. The new Maven structure does not. To work around compatibility issues, code that was in /src/ is now moved to /classes/. This should work with both Ant, as well as Maven. Additionally, this plugin now makes use of the new HttpBindManager API for registering contexts with the BOSH context. I do wonder if this plugin has any reason to be here though. Can't it just run its own embedded Jetty server?
-
- 26 Apr, 2017 1 commit
-
-
Guus der Kinderen authored
Javadoc comment are dangling if they don't belong to any class, method or field. For example a Javadoc comment in between method declarations that have their own javadoc comments. These generate needless warnings, which are in most instances easily solved. By far most problems occur in the license block that's in most files.
-
- 04 Jan, 2017 1 commit
-
-
daryl herzmann authored
-
- 22 Jun, 2016 1 commit
-
-
deleolajide authored
-
- 21 Jun, 2016 1 commit
-
-
deleolajide authored
-
- 20 Jun, 2016 1 commit
-
-
Dele Olajide authored
-
- 10 May, 2016 1 commit
-
-
Dele Olajide authored
-
- 09 May, 2016 1 commit
-
-
Daniel Hams authored
Use the JasperInitializer in place of the JettyJasperInitializer across the code base (Http-bind and JMX web plugin).
-
- 29 Apr, 2016 1 commit
-
-
Dele Olajide authored
-
- 01 Dec, 2015 1 commit
-
-
Guus der Kinderen authored
-
- 21 Nov, 2015 1 commit
-
-
Christian Schudt authored
Old version 2.4 was J2EE 1.4 Also remove <taglib> from web.xml. This was required in JSP 1.2, but is no longer in JSP 2.0 (Servlet API 2.4) and gives warnings since it has been removed from the XSD. See http://wiki.metawerx.net/wiki/RemovingTaglibFromWeb.xml
-
- 01 Jul, 2015 1 commit
-
-
kurt authored
- src/plugins/userImportExport/classes/wildfire-user-schema.xsd.xml - src/plugins/jmxweb/src/hawtio/app/wiki/exemplar/camel-blueprint.xml (from http://www.w3.org/2001/XMLSchema to http://www.w3c.org/2001/XMLSchema)
-
- 12 Jan, 2015 1 commit
-
-
Dele Olajide authored
-
- 10 Jan, 2015 1 commit
-
-
Dele Olajide authored
-