On 25 Nov 07, at 2:23 PM 25 Nov 07, Shane Isbell wrote:
Okay, so it sounds as though if someone wants a remote assembly
resource,
they can just add a remote resource plugin to the pom; which, during
build,
will copy the resource to the appropriate directory on the local file
system. So unless someone comes up with a compelling reason, I'm
going to
leave the NetCompilerContext method signature with the File types.
I think if that's what you're dealing with in the day-to-day case
leave it as that. People are dealing with Files and so says the
signature.
So, yes in Maven folks just configure the remote-resources-plugin to
nab stuff and place it into an assembly.
Thanks,
Shane
On Nov 25, 2007 11:41 AM, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 25 Nov 07, at 1:37 PM 25 Nov 07, Shane Isbell wrote:
I'm tightening up the compiler interfaces and have been thinking
about the
NetCompilerContext methods:
List<File> getLinkedResources()
List<File> getEmbeddedResources(),
File getWin32Icon(),
and so on, using File. What do people think about using URI instead?
This
would allow the build to pull the resources from either a web server
or a
file system but it could break the build if any remote resources are
not
available. Thoughts?
In Maven we actually have a resources plugin and a remote resources
plugin for these different purposes. Deal with files where they are
files, URIs where they are remote resources. Not sure the abstraction
buys you much in practice.
Shane
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
