On 1/2/06, Martin Marinschek <
[EMAIL PROTECTED]> wrote:
The plugin that creates the tlds should also ensure that the output directory exists. This is good practice for Maven2 plugins in general.
In addition, that plugin should be running during the generate-resources phase, the output directory should be target/[plugin-name]/src/main/resources (or similar), and the output directory should be added as a dynamic resource root on the MavenProject object.
Kind Regards,
John Fallows.
The build doesn't run on my machine anymore - ok, it runs, but the tld
files are not created anymore.
The tld's cannot be created, as the target/classes/META-INF directory
doesn't exist.
Solution anyone?
The plugin that creates the tlds should also ensure that the output directory exists. This is good practice for Maven2 plugins in general.
In addition, that plugin should be running during the generate-resources phase, the output directory should be target/[plugin-name]/src/main/resources (or similar), and the output directory should be added as a dynamic resource root on the MavenProject object.
Kind Regards,
John Fallows.
On 1/2/06, John Fallows < [EMAIL PROTECTED]> wrote:
> Devs,
>
> On 1/1/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote:
> > Changes to the TLD files don't seem to be being picked up at build time;
> this was a problem in the Ant build as well but 'ant clean' fixed it there,
> but 'mvn clean' doesn't here.
> >
> > My situation: I editied
> tomahawk/src/main/tld/tomahawk-entities/tomahawk_validate_equal_attributes.xml
> and ran 'mvn install'. My changes didn't take, so I did a 'mvn clean' then
> a 'mvn install'. Changes still aren't picked up.
> >
> > I suspect it's the cached intermediate file at
> tomahawk\src\main\resources\META-INF\tomahawk.tld that's
> causing the problem. It isn't deleted by a clean.
> >
> > [INFO]
> ----------------------------------------------------------------------------
> > [INFO] Building Tomahawk
> > [INFO] task-segment: [install]
> > [INFO]
> ----------------------------------------------------------------------------
> > [INFO] [xslt:transform {execution: default}]
> > [INFO] # of XML files: 1
> > [INFO] file up-to-date:
> C:\work\workspace\myfaces-current-postreorg\build\..\tomahawk\src\main\resources\META-INF\tomahawk.tld
> >
> >
>
> All generated files should live in the target subdirectory, including
> generated resources such as .tld files.
>
> In ADF Faces we merge together a base .tld from
> src/main/conf/META-INF/xxx-base.tld with other metadata to generate
> target/[plugin-name]/src/main/resources/META-INF/xxx.tld,
> and the plugin automatically adds
> target/[plugin-name]src/main/resources to the resource root
> set (similar to java source path for javac).
>
> When the IDE projects are generated - we use JDeveloper :-) - both the
> xxx-base.tld and the xxx.tld files are visible in the merged resources tree
> view. When either the xxx-base.tld file or other relevant metadata is
> changed, we re-run mvn generate-resources to regenerate
> target/[plugin-name]/src/main/resources/META-INF/xxx.tld,
> without needing to do a clean build.
>
> Since src/main/resources and
> target/[plugin-name]/src/main/resources are both registered
> as resource roots, but src/main/conf is not, then the xxx-base.tld is not
> included in the JAR, but xxx.tld is included, as desired.
>
> Kind Regards,
> John Fallows.
>
> --
> Author Pro JSF and Ajax: Building Rich Internet Components
> http://www.apress.com/book/bookDisplay.html?bID=10044
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
--
Author Pro JSF and Ajax: Building Rich Internet Components
http://www.apress.com/book/bookDisplay.html?bID=10044
