From 345c0d8f7738aab20d2b45fd6c5ebf911b75e2fa Mon Sep 17 00:00:00 2001
From: Trygve Laugstøl <trygvis@inamo.no>
Date: Fri, 2 May 2014 18:26:50 +0200
Subject: o Initial import of ActiveMQ plugin for Jenkins.

---
 .../plugins/activemq/ActiveMqPlugin/global.jelly    | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 src/main/resources/org/jenkinsci/plugins/activemq/ActiveMqPlugin/global.jelly

(limited to 'src/main/resources/org/jenkinsci/plugins/activemq/ActiveMqPlugin/global.jelly')

diff --git a/src/main/resources/org/jenkinsci/plugins/activemq/ActiveMqPlugin/global.jelly b/src/main/resources/org/jenkinsci/plugins/activemq/ActiveMqPlugin/global.jelly
new file mode 100644
index 0000000..6da81e0
--- /dev/null
+++ b/src/main/resources/org/jenkinsci/plugins/activemq/ActiveMqPlugin/global.jelly
@@ -0,0 +1,21 @@
+<j:jelly xmlns:j="jelly:core" xmlns:st="jelly:stapler" xmlns:d="jelly:define" xmlns:l="/lib/layout" xmlns:t="/lib/hudson" xmlns:f="/lib/form">
+  <!--
+    This Jelly script is used to produce the global configuration option.
+
+    Jenkins uses a set of tag libraries to provide uniformity in forms.
+    To determine where this tag is defined, first check the namespace URI,
+    and then look under $JENKINS/views/. For example, <f:section> is defined
+    in $JENKINS/views/lib/form/section.jelly.
+
+    It's also often useful to just check other similar scripts to see what
+    tags they use. Views are always organized according to its owner class,
+    so it should be straightforward to find them.
+  -->
+<!--
+  <f:section title="ActiveMQ Plugin">
+    <f:entry title="ActiveMq URL" field="brokerUrl" description="yeah yeah">
+      <f:textbox/>
+    </f:entry>
+  </f:section>
+-->
+</j:jelly>
-- 
cgit v1.2.3