[Keros-developers] Look at this bug created against Ant

[Scot P. F. <fl...@mi...>]

All:

Please check out this bug created against Ant.  This will make Keros 
much much more portable and as a project more easily supported by a tool 
like Ivy.

The crux of this bug/feature is that it allows one to import files from 
a classpath resource.  The neat thing is that Keros could conceivably be 
distributed as a whole in one jar file :)

Anyway, take a peak and give me your thoughts...

PS:  Phillip, sorry for duping this email to you...the developer list 
was bouncing back all my emails...

I did a cut and paste below...


This is really good progress. Is there any technical issue to enable remote
ant build file by http or whatever?
The goal is to enable to start writting a build just referencing a remote
build file (may be cached in a temp that would be used if remote
unavailable) and to share build among several project easily...



jonathan doklovic-2 wrote:

> > 
> > I added a bug to the bug database and attached a patch that adds the
> > same classpath functionality as taskdef to the import task.
> > 
> > http://issues.apache.org/bugzilla/show_bug.cgi?id=44214
> > 
> > - Jonathan
> > 
> > On Fri, 2008-01-11 at 09:40 -0800, kermitt wrote:
>   
>> >> In a previous post I suggest this:
>> >> 
>> >> I wish Ant import would support URL + jar like that :
>> >> 
>> >> <project ...>
>> >>    <import url="http://repo/build.jar!common-build.xml"/>
>> >> </project>
>> >> 
>> >> As ivy became a sub project, it would make sense to have a closer
>> >> integration like :
>> >> 
>> >> <project ...>
>> >>    <import url="ivy://settings.xml:org/module/artifact@MyResolver" />
>> >> <!--
>> >> would locate the settings.xml file and seek a build-common.xml file using
>> >> MyResolver resolver.
>> >> -->
>> >> </project>
>> >> 
>> >> we could imagine deeper integration :
>> >> 
>> >> <project ...>
>> >>    <import url="ivy://settings.xml:org/module/artifact@MyResolver"
>> >> ivyFile="${basedir]/ivy.xml"/>
>> >> <!--
>> >> configure ivy / read the ivy file
>> >> would map each ivy configuration to a path ( path could use a lazy
>> >> resolve
>> >> proxy: resolve only when it get used)
>> >> would import resolved artifcat as an ant build file
>> >> 
>> >> -->
>> >> </project> 
>> >> 
>> >> jonathan doklovic-2 wrote:
>>     
>>> >> > 
>>> >> > Hi,
>>> >> > 
>>> >> > I know there's not currently a way to do this, but I think it would be
>>> >> > very helpful to be able to use the import task to import a file from a
>>> >> > jar.
>>> >> > 
>>> >> > This way, when I have a handful of projects, all with common targets, I
>>> >> > can put the common.xml build file in a jar and have each project depend
>>> >> > on that jar.
>>> >> > 
>>> >> > Combined with something like ivy, I think this would be a pretty good
>>> >> > way to share common targets among multiple projects that may not have
>>> >> > anything to do with each other.
>>> >> > 
>>> >> > Any thoughts?
>>> >> > 
>>> >> > Any way to do this now?
>>> >> > 
>>> >> > - Jonathan

-- 
Scot P. Floess
27 Lake Royale
Louisburg, NC  27549

252-478-8087 (Home)
919-754-4592 (Work)

Chief Architect JPlate   http://sourceforge.net/projects/jplate
Chief Architect JavaPIM  http://sourceforge.net/projects/javapim

Architect Keros          http://sourceforge.net/projects/keros