[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [virgo-dev] Build System and .classpath files
- From: Patsy Phelan <pphelan@xxxxxxxx>
- Date: Thu, 15 Jul 2010 16:01:24 +0100
- Delivered-to: firstname.lastname@example.org
Yeap, I think that is it. I would have to dig into some our internal
documentation to have found the link :) Thanks for
Not sure on the current status of it, but we have been using it over a
year or more with no problems - from dm Server 1.0ish all the way
through to now with Virgo.
We still have to tweak other .settings files for eclipse and STS but
that is a story for another day :)
On Thu, 2010-07-15 at 10:53 -0400, Dmitry Sklyut wrote:
> I think this is the java code for the
> task: https://issues.apache.org/jira/browse/IVY-1016
> Not sure how current that is. This could be a very good compromise.
> On Thu, Jul 15, 2010 at 10:45 AM, Patsy Phelan <pphelan@xxxxxxxx>
> We had the same issues here but we modified the then
> "spring-build" to
> include a "eclipse" target which uses ant/ivy to resolve the
> dependencies and update the .classpath files for eclipse. At
> the our
> root level build (build-all) we can iterate all the
> sub-bundles and
> update the .classpath files.
> It did mean adding a new "task" into the ivy.jar that was
> present in the
> spring-build/lib directory. This was un-jar'd, goto the folder
> org/apache/ivy/ant, new class added, antlib.xml updated to
> reflect the
> new EclipseClasspath class, and re-jar'd again.
> I would have to look for the java file for the
> EclipseClasspath but in
> the meantime, I have attached the decompiled version of it.
> (EclipseClasspath.jad). It was build agains't the ivy jar we
> had so
> there was not much problems getting it to a class file.
> The antlib.xml file in the ivy.jar was updated to include
> this :
> <taskdef name="eclipse"
> Then some slight modification in the
> spring-build/common/common.xml to
> add a new target:
> <!-- Generate Eclipse .classpath file from ivy
> dependencies -->
> <target name="eclipse" description="Updates eclipse
> <ivy:resolve conf="test" />
> <ivy:eclipse conf="test" />
> At this point you can add this as a "depends" to other more
> targets. So for us this works quite well, the developers are
> used to
> "ant clean eclipse jar" and so into the GUIs they go. Of
> everywhere you see spring-build start to think virgo-build.
> Hope it helps,
> > It's even worse than that: we also index into the ivy cache
> in Eclipse
> > .classpath files and in some tests, for example
> > org.eclipse.virgo.web.test.SpringWebFlowWarTests in Virgo
> virgo-dev mailing list
> virgo-dev mailing list