maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lukas Theussl (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MAVEN-1656) Doco that explains the protocols required to allow maven.xml or any plugin.jelly to inject values into or retrieve values from another plugin
Date Sun, 11 Mar 2007 19:49:34 GMT

     [ http://jira.codehaus.org/browse/MAVEN-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lukas Theussl updated MAVEN-1656:
---------------------------------

    Fix Version/s:     (was: 1.1-rc1)

> Doco that explains the protocols required to allow maven.xml or any plugin.jelly to inject
values into or retrieve values from another plugin
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAVEN-1656
>                 URL: http://jira.codehaus.org/browse/MAVEN-1656
>             Project: Maven 1.x
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 1.1-beta-1
>         Environment: All
>            Reporter: Andy Glick
>
> Brett recently posted a suggestion to someone who asked how to access the contents of
"plugin a" from the context of "plugin b" or from maven.xml. Brett stated that "plugin a"
would have to be initialized before it could be accessed, and that from what I could understand
he recommended 1 or 2 ways to do that:
> 1) reference the artifact plugin's namespace in the project tag 
> 2) specify <j:set target="plugin-name" scope="parent" var="some.plugin.var" value="some.value"/>
 (I think that this is the proper syntax, but I'm not sure :-).
> Thierry Lach, who asked the question this time around, reported that using the artifact
namespace didn't work in his instance, but that setting the scope to parent did. I'm hoping
that we can put together a fairly comprehensive explanation about what is going on here, and
if that means explaining why the project gave up on Jelly and switched to M2, then so be it.
> See http://news.gmane.org/gmane.comp.jakarta.turbine.maven.user for the postings
> Given that during the last couple of months Vincent Massol recommended that people use
the now deprecated <dependency-handle> mechanism on the mavenbook.org site (see Tip
#2), I should think that there ought to be a priority on documenting this issue in an obvious
place, probably the FAQ, but also on the Maven Jelly tags get and set entries. 
> If this is actually explicitly documented somewhere, I'm sorry to have wasted anyone's
time. I have seen several plugins that have successfully used the artifact namespace tag,
so there must be some way that people have learned this. I simply wish that I knew how they
had done so. ;-) 
> I'm willing to write the doco if someone would explain the details.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message