Since I am in a tag and therefore have no access to${plugin.in}, I had to call
<maven:get plugin="maven-my-plugin"
property="plugin"
var="plugin" />
this way I can use
> >> <ant:pathelement path="${plugin.getDependencyPath
Now it become cumbersome here, for every tag, I must define the classpath
(10 element). An now my plugin.jelly poluted with the same definitions.
-D
On Thu, 2 Sep 2004 13:37:53 -0500, Jefferson K. French
<[EMAIL PROTECTED]> wrote:
> Now that you mention it, it probably points to the one in your local
> repo, which means it may not be necessary to bundle the jars afterall.
> I may have added bundle the jars at the same time I added the
> getDependencyPath call, and assumed I needed both.
>
> On Thu, 02 Sep 2004, at 09:18:23 [GMT -0700] dan tran wrote:
>
> > Jeff,
>
> > I understand step 1 and 2. Please help me to understand step 3.
>
> > In step 3, your add more classpath to maven.dependency.classpath using
> > ${plugin.getDependencyPath('groupId:artifactId')
>
> > Does ${plugin.getDependencyPath('groupId:artifactId') point to the one
> > the jar you
> > bundle with the plugin? or it points to the one in ${maven.local.repo} directory
>
> > -D
>
> > On Thu, 2 Sep 2004 10:39:57 -0500, Jefferson K. French
> > <[EMAIL PROTECTED]> wrote:
> >> Dan,
> >>
> >> I added to maven.dependency.classpath. My plugin was using an Ant task
> >> that had external dependencies. What I did was:
> >>
> >> 1. Put the dependent jars in the plugin's project.xml, along with
> >> the line:
> >>
> >> <properties><plugin.bundle>true</plugin.bundle></properties>
> >>
> >> 2. Added a plugin:plugin postGoal that copied any dependency that
> >> has the plugin.bundle property to maven.build.dest. When I
> >> deployed the plugin, the dependent jars were deployed along with
> >> them.
> >>
> >> 3. In plugin.jelly, I setup the classpath like this:
> >>
> >> <ant:taskdef name="mytask"
> >> classname="com.mycompany.taskdefs.MyTask">
> >> <ant:classpath>
> >> <ant:pathelement
> >> path="${plugin.getDependencyPath('groupId:artifactId')}"/>
> >> <ant:pathelement
> >> path="${plugin.getDependencyPath('groupId:artifactId')}"/>
> >> <ant:path refid="maven.dependency.classpath"/>
> >> </ant:classpath>
> >> </ant:taskdef>
> >>
> >> Possibly the same classpath construction will work for your java task?
> >>
> >> Jeff
> >>
> >> On Thu, 02 Sep 2004, at 08:12:47 [GMT -0700] dan tran wrote:
> >>
> >> > Jeff, so I will need to setup the classpath my self rather then depending on
> >> > maven.dependcy.classpath right?
> >>
> >> > Thanks,
> >>
> >> > -D
> >>
> >> > On Thu, 2 Sep 2004 10:03:08 -0500, Jefferson K. French
> >> > <[EMAIL PROTECTED]> wrote:
> >> >> Dan,
> >> >>
> >> >> I had the same issue for a custom plugin. What I did was to include my
> >> >> plugin's dependencies in the plugin's project.xml, then make sure the
> >> >> dependent jars were bundled along with the plugin when it was
> >> >> deployed.
> >> >>
> >> >> Jeff
> >> >>
> >> >>
> >> >>
> >> >> On Thu, 02 Sep 2004, at 07:39:56 [GMT -0700] dan tran wrote:
> >> >>
> >> >> > Hello,
> >> >>
> >> >> > I have a custom plugin P which is called by a project A.
> >> >> > In plugin P, I have a tag which uses <ant:java> to invoke
> >> >> > a java class.
> >> >>
> >> >> > Calling plugin P's tag from project A results in a ClassNotFoundException,
> >> >> > unless I include plugin P's denpendencies in project A
> >> >>
> >> >> > In previous post, I have the similar problem when dealing with
> >> >> > plugin's properties not seeing by plugin's tag
> >> >>
> >> >> > http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=15788
> >> >>
> >> >> > Is there similar solution for this situtation. I just hate to include
> >> >> > my custom plugin's dependencies that every project that needs to
> >> >> > call the tag.
> >> >>
> >> >> > Big thanks
> >> >>
> >>
> >> --
> >> mailto:[EMAIL PROTECTED]
> >>
> >>
>
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
> --
> mailto:[EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
