Re: [m2] Timestamp plugin
Hi Jason,
Not much work has been done yet. I have created a really minimal version
of the plugin. Thats 7 lines of real code. Have a look at the plugin if
you want to, its attached to
https://issues.apache.org/jira/browse/GERONIMO-1659 . It may not be the
best way of doing it, but doubt there is any simpler way.
/Anders
Jason van Zyl wrote:
Anders Hessellund Jensen wrote:
I would like to be able to substitute timestamps with the build time
into a resource file. As I understand it, there is currently no plugin
to to this, so I consider writing one.
Sorry for not responding to this earlier, and I know that you've started
working on this plugin and I'd like to harness the work you've done but
I think what you are doing should be an extension to the resources
plugin. We should figure out how to augment filtering of resources. I
think the easiest way to do this is to filter the resources using Velocity.
This way additional tools can be created for swizzling resources and
this can all happen in one pass through velocity instead of having N
plugins which need to make N passes over the resources to filter them.
So I don't want to discourage you at all. Work on the plugin and I will
try to integrate your code into the resources plugin when you are done.
The other advantage of using Velocity in the resources plugin will allow
you to use Velocity directives in your resources so you can do any sort
of conditional logic you may want to have instead of simple
substitution. So I think we would benefit in two ways using Velocity
here: scalable addition of tools that can be used to swizzle resources
(a timestamp tool is a perfect example) and conditional logic which can
sometimes be useful like looking at a property introduced by a profile
and behave a certain way for example.
The plugin should leverage the existing resource filtering mechanism
of M2. The plugin would take a configuration like this:
build.date
.MM.dd
Running the plugin with this configuration would define the M2
property build.date, and any filtered resource file would get
${build.date} substituted with 2006.02.28 or whatever the date at
build time is.
WDYT?
Best regards,
Anders
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Timestamp plugin
The plugin is in progress. I'm aiming for functionality identical to
that of the TStamp Ant core task:
http://ant.apache.org/manual/CoreTasks/tstamp.html .
Anders Hessellund Jensen wrote:
I would like to be able to substitute timestamps with the build time
into a resource file. As I understand it, there is currently no plugin
to to this, so I consider writing one.
The plugin should leverage the existing resource filtering mechanism of
M2. The plugin would take a configuration like this:
build.date
.MM.dd
Running the plugin with this configuration would define the M2 property
build.date, and any filtered resource file would get ${build.date}
substituted with 2006.02.28 or whatever the date at build time is.
WDYT?
Best regards,
Anders
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Timestamp plugin
I would like to be able to substitute timestamps with the build time
into a resource file. As I understand it, there is currently no plugin
to to this, so I consider writing one.
The plugin should leverage the existing resource filtering mechanism of
M2. The plugin would take a configuration like this:
build.date
.MM.dd
Running the plugin with this configuration would define the M2 property
build.date, and any filtered resource file would get ${build.date}
substituted with 2006.02.28 or whatever the date at build time is.
WDYT?
Best regards,
Anders
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-670) JacORB IDL Compiler
JacORB IDL Compiler --- Key: MAVENUPLOAD-670 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-670 Project: maven-upload-requests Type: Task Reporter: Anders Hessellund Jensen Attachments: jacorb-idl-compiler-upload-bundle-2.2.3.jar This is the JacORB IDL compiler, part of the JacORB CORBA implementation. The JacORB developers has authorized me to upload this bundle, but I'm not a developer on the project, I am merely creating a upload bundle for the idl compiler. If you need to talk to one of the developers on the project, please talk to Andre Spiegel at [EMAIL PROTECTED] . He is listed as a developer on the page http://www.jacorb.org/authors.html . The JacORB IDL compiler is going to used in the IDL compiler plugin for maven. It is licensed under the LGPL. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugin development questions
Anders Hessellund Jensen wrote: I understand that the right way to scan for files to include for compilation is to use a org.codehaus.plexus.compiler.util.scan.StaleSourceScanner. This class uses a SourceMapping to specify which sources to include. There does not seem to be a mapping that can filter sources based some include and exclude patterns, however. Is anyone working on such a SourceMapping, or should I make up my own? After I took a closer look at StaleSourceScanner and SourceMapping, I understand that this does not make any sense, so please disregard this part of my mail. Best regards, Anders - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Plugin development questions
Hi all, I'm working on a maven 2 plugin to compile IDL files. Alan Cabrera created an initial plugin, and I am adding some additional features. I have a couple of questions I'd like to have some help with. I need to be specify various parameters to pass to the compiler backend. For each idl file to compile, the following needs to be specified: - Whether the compiler should emit stubs, skeletons or both - A list of package prefixes - A list of symbol definitions for preprocessing of the IDL files Obviously, these configurations would be the same for many .idl files, so the .idl files should be grouped together. I suppose an XML configuration of the plugin could look something like this: jacorb all **/*.idl **/CORBA_TypeCode.idl IIOP org.omg _PRE_3_0_COMPILER_ 1 . . . I think it would provide the neccessary flexibility. Does this configuration layout look OK to you guys? I understand that the right way to scan for files to include for compilation is to use a org.codehaus.plexus.compiler.util.scan.StaleSourceScanner. This class uses a SourceMapping to specify which sources to include. There does not seem to be a mapping that can filter sources based some include and exclude patterns, however. Is anyone working on such a SourceMapping, or should I make up my own? Best regards, Anders - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
