Bommels05/maven-plugins
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Try and have some kind of "standard" for the hacks that allow the plugins to be reliably loaded

Browse Source 
from another plugin
PR: MAVEN-372


git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@113480 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
bwalding 2003-06-10 10:17:26 +00:00
parent 2932b1be0a
commit acec98fc28
2 changed files with 7 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
eclipse/plugin.jelly
View File

@ -5,7 +5,7 @@
xmlns:ant="jelly:ant"
xmlns:test="test">
<test:eclipse/>
<test:dependency-handle/>
<!--==================================================================-->
<!-- Generate Eclipse .project and .classpath files -->

15
test/plugin.jelly
View File

@ -5,15 +5,6 @@
xmlns:resources="resources"
xmlns:define="jelly:define">
<define:taglib uri="test">
<define:tag name="eclipse">
<!-- The eclipse plugin requires access to the test plugin.
Using this tag forces the test plugin to be loaded into the
eclipse plugin -->
</define:tag>
</define:taglib>
<goal name="test"
description="Test the application"
prereqs="test:test"/>
@ -309,4 +300,10 @@
</j:if>
</j:if>
</goal>
<define:taglib uri="test">
<define:tag name="dependency-handle">
<!-- XXX Use this tag to allow this plugin to be loaded into another -->
</define:tag>
</define:taglib>
</project>