Permalink
Browse files

- Commited initial CAF version

- Added netbeans stucture
  • Loading branch information...
Pedro Alves
Pedro Alves committed Feb 26, 2012
1 parent dbfd3a9 commit 9300cfd78d30bb216a7cadad504fc6292f138cfb
View
@@ -2,7 +2,8 @@
####################
bin
dist
-lib
+/lib
test-lib
dev-lib
override.properties
+/nbproject/private
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<availablePlugins>
+ <plugin id="cde">
+ <img>wt_transparent.png</img>
+ <name>Community Dashboard Editor</name>
+ <learnMoreUrl>http://cde.webdetails.org</learnMoreUrl>
+ <downloadUrl>http://www.webdetails.pt/ficheiros/CDE-bundle-1.0-RC3.tar.bz2</downloadUrl>
+ <availableVersion>1.0-RC3</availableVersion>
+ <description>The Community Dashboard Editor (CDE) is the outcome of real-world needs: It was born to greatly simplify the creation, edition and rendering of dashboards.
+
+CDE and the technology underneath (CDF, CDA and CCC) allows to develop and deploy dashboards in the Pentaho platform in a fast and effective way.
+ </description>
+ <company>WebDetails</company>
+ <companyUrl>http://webdetails.pt</companyUrl>
+ </plugin>
+ <plugin id="cda">
+ <img>wt_transparent.png</img>
+ <name>Community Data Access</name>
+ <learnMoreUrl>http://cda.webdetails.org</learnMoreUrl>
+ <downloadUrl>http://localhost:8080/cda-1.0.zip</downloadUrl>
+ <downloadUrl2>http://www.webdetails.pt/ficheiros/cda-installer-v1.0.jar</downloadUrl2>
+ <availableVersion>1.0</availableVersion>
+ <description>Community Data Access (CDA) is a Pentaho plugin designed for accessing data with great flexibility. Born for overcoming some cons of the older implementation, CDA allows you to access any of the various Pentaho data sources. </description>
+ <company>WebDetails</company>
+ <companyUrl>http://webdetails.pt</companyUrl>
+ </plugin>
+
+ <plugin id="cdf">
+ <img>wt_transparent.png</img>
+ <name>Community Dashboards Framework</name>
+ <learnMoreUrl>http://cdf.webdetails.org</learnMoreUrl>
+ <downloadUrl>http://localhost:8080/cdf-1.0.zip</downloadUrl>
+ <downloadUrl2>http://www.webdetails.pt/ficheiros/cdf-installer-v1.0.jar</downloadUrl2>
+ <samplesDownloadUrl>http://localhost:8080/cdf-1.0.samples.zip</samplesDownloadUrl>
+ <availableVersion>1.0</availableVersion>
+ <changelog>Changelog</changelog>
+ <installationNotes>Notes after install</installationNotes>
+ <description>Community Dashboards Framework (CDF) is a Pentaho plugin designed for drawing dashboards.</description>
+ <company>WebDetails</company>
+ <companyUrl>http://webdetails.pt</companyUrl>
+ </plugin>
+
+
+</availablePlugins>
View
@@ -9,33 +9,41 @@
============================================================================-->
<project name="Pentaho Marketplace" basedir="." default="resolve-and-dist" xmlns:ivy="antlib:org.apache.ivy.ant">
- <description>
+ <description>
This build file is used to create the Pentaho Marketplace Plugin
and works with the common_build.xml file.
- </description>
+ </description>
<!-- Import the subfloor-pkg.xml file which contains all the default tasks -->
- <import file="build-res/subfloor-pkg.xml" />
+ <import file="build-res/subfloor-pkg.xml" />
<!-- override copying of libs, no need for plugin -->
- <target name="assemble.copy-libs">
- <copy todir="${approot.stage.dir}/lib">
- <fileset file="${dist.dir}/${ivy.artifact.id}-${project.revision}.jar" />
- </copy>
- <copy todir="${approot.stage.dir}/lib">
- <fileset file="${lib.dir}/flexjson-*.jar" />
- </copy>
- </target>
+ <target name="assemble.copy-libs">
+ <copy todir="${approot.stage.dir}/lib">
+ <fileset file="${dist.dir}/${ivy.artifact.id}-${project.revision}.jar" />
+ </copy>
+ <copy todir="${approot.stage.dir}/lib">
+ <fileset file="${lib.dir}/flexjson-*.jar" />
+ </copy>
+ </target>
- <target name="assemble" depends="subfloor-pkg.assemble">
+ <target name="assemble" depends="subfloor-pkg.assemble">
<!-- Update the version.xml with the current version of this plugin -->
- <replace file="${approot.stage.dir}/version.xml" token="TRUNK" value="${project.revision}"/>
- </target>
+ <replace file="${approot.stage.dir}/version.xml" token="TRUNK" value="${project.revision}"/>
+ </target>
- <target name="resolve-and-dist" depends="resolve, dist"/>
+ <target name="resolve-and-dist" depends="resolve, dist"/>
- <target name="install" depends="resolve-and-dist">
- <delete dir="${biserver.dir}/pentaho-solutions/system/${ivy.artifact.id}"/>
- <unzip src="dist/${package.id}-${project.revision}.zip" dest="${biserver.dir}/pentaho-solutions/system"/>
- </target>
+ <target name="install" depends="resolve-and-dist" description="Installs the plugin in the specified directory (${plugin.local.install.solutions.dir})">
+ <delete dir="${plugin.local.install.solutions.dir}/system/${ivy.artifact.id}"/>
+ <unzip src="dist/${package.id}-${project.revision}.zip" dest="${plugin.local.install.solutions.dir}/system"/>
+ </target>
+
+
+ <target name="install-plugin" depends="install" description="Installs the plugin in the specified directory (${biserver.dir}) and signals the server to initialize it">
+
+ <get src="http://127.0.0.1:8080/pentaho/Publish?publish=now&amp;class=org.pentaho.platform.plugin.services.pluginmgr.PluginAdapter&amp;userid=${plugin.local.install.user}&amp;password=${plugin.local.install.pass}" dest="${stage.dir}/blah.html"/>
+ </target>
+
+
</project>
View
@@ -0,0 +1,3 @@
+Manifest-Version: 1.0
+X-COMMENT: Main-Class will be added automatically by build
+
View
@@ -0,0 +1,74 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- You may freely edit this file. See commented blocks below for -->
+<!-- some examples of how to customize the build. -->
+<!-- (If you delete it and reopen the project it will be recreated.) -->
+<!-- By default, only the Clean and Build commands use this build script. -->
+<!-- Commands such as Run, Debug, and Test only use this build script if -->
+<!-- the Compile on Save feature is turned off for the project. -->
+<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
+<!-- in the project's Project Properties dialog box.-->
+<project name="Pentaho_Marketplace" default="default" basedir=".">
+ <description>Builds, tests, and runs the project Pentaho Marketplace.</description>
+ <import file="nbproject/build-impl.xml"/>
+ <!--
+
+ There exist several targets which are by default empty and which can be
+ used for execution of your tasks. These targets are usually executed
+ before and after some main targets. They are:
+
+ -pre-init: called before initialization of project properties
+ -post-init: called after initialization of project properties
+ -pre-compile: called before javac compilation
+ -post-compile: called after javac compilation
+ -pre-compile-single: called before javac compilation of single file
+ -post-compile-single: called after javac compilation of single file
+ -pre-compile-test: called before javac compilation of JUnit tests
+ -post-compile-test: called after javac compilation of JUnit tests
+ -pre-compile-test-single: called before javac compilation of single JUnit test
+ -post-compile-test-single: called after javac compilation of single JUunit test
+ -pre-jar: called before JAR building
+ -post-jar: called after JAR building
+ -post-clean: called after cleaning build products
+
+ (Targets beginning with '-' are not intended to be called on their own.)
+
+ Example of inserting an obfuscator after compilation could look like this:
+
+ <target name="-post-compile">
+ <obfuscate>
+ <fileset dir="${build.classes.dir}"/>
+ </obfuscate>
+ </target>
+
+ For list of available properties check the imported
+ nbproject/build-impl.xml file.
+
+
+ Another way to customize the build is by overriding existing main targets.
+ The targets of interest are:
+
+ -init-macrodef-javac: defines macro for javac compilation
+ -init-macrodef-junit: defines macro for junit execution
+ -init-macrodef-debug: defines macro for class debugging
+ -init-macrodef-java: defines macro for class execution
+ -do-jar-with-manifest: JAR building (if you are using a manifest)
+ -do-jar-without-manifest: JAR building (if you are not using a manifest)
+ run: execution of project
+ -javadoc-build: Javadoc generation
+ test-report: JUnit report generation
+
+ An example of overriding the target for project execution could look like this:
+
+ <target name="run" depends="Pentaho_Marketplace-impl.jar">
+ <exec dir="bin" executable="launcher.exe">
+ <arg file="${dist.jar}"/>
+ </exec>
+ </target>
+
+ Notice that the overridden target depends on the jar target and not only on
+ the compile target as the regular run target does. Again, for a list of available
+ properties which you can use, check the target you are overriding in the
+ nbproject/build-impl.xml file.
+
+ -->
+</project>
Oops, something went wrong.

0 comments on commit 9300cfd

Please sign in to comment.