[dojo-contributors] Eclipse RCP Dojo builder

[Shane O'Sullivan]

Hi all,

I'm currently working on the Eclipse RCP based build tool, and am seeing
some strange Ant/Python behaviour that I'm hoping one of you Ant & Build
gurus has seen before.  I'm calling Ant programatically from within Eclipse,
using the AntRunner class from the org.eclipse.tools.ant package.  This is
running directly against a build.xml file in a Dojo SVN checkout, so all the
paths should be correctly set up.  All the required Jars, python files,
pyLib.zip are all in their usual places.

However, when I run the ant build, I get the following exception:
File "popen2.py", line 27, in ?
ImportError: No module named python
    at org.python.core.Py.ImportError(Py.java:193)
    at org.python.core.imp.import_logic(imp.java:547)
    at org.python.core.imp.import_name(imp.java:597)
    at org.python.core.imp.importName(imp.java:625)
    at org.python.core.ImportFunction.load(__builtin__.java:1006)
    at org.python.core.ImportFunction.__call__(__builtin__.java:999)
    at org.python.core.PyObject.__call__(PyObject.java:572)
    ......
The strange thing about this is that it is failing on this line in
popen2.py(in the
pyLib.zip archive):
    from org.python.core import PyFile
So it basically seems to be saying that it can't find the org.python java
package, stored in the jython.jar file.  However, this is definitely on the
classpath correctly, since, when the exception is throw, it's already many
layers deep in the Jython code.

This code is running on a machine that is otherwise set up to work with
building Dojo, so Ant etc are installed, so there should be not problem with
environment variables etc (even though with this Eclipse set up these
dependencies should not be needed)

Has anyone ever seen a similar error?  Google has been no help with it.

Thanks

Shane


On 19/12/06, Shane O'Sullivan <shaneosullivan1 at gmail.com> wrote:
>
> Hi Chris,
>
> That sounds cool, I'd be glad to take a look at it.  However, I think the
> SVN route should still be the primary focus for this application, but also
> offering to pull down pre-built versions of Dojo from an update site would
> be useful too.  I should be able to make it also that anyone who installs
> this tool in Eclipse be given the option to also download the Dojo docs in
> Eclipse format.  This could also work on the standalone version.
>
> The SVN code is now finished on the app, moving on to Ant building issues
> and GUI-based user customisation next.
>
> Shane
>
> On 19/12/06, Chris Mitchell <ccmitchellusa at gmail.com> wrote:
> >
> > Hi Shane,
> >
> > We have some ant tasks that can package dojo profiles as eclipse
> > features on an eclipse update site, and could check these into the
> > build system, so that an eclipse update site is published to a url off
> > of dojotoolkit.org.  One of the features that gets included is the
> > Dojo book (in eclipse help format).
> >
> > Let me know if you want to check out what they look like.
> > --Chris
> >
> > On 12/19/06, Shane O'Sullivan <shaneosullivan1 at gmail.com> wrote:
> > > > can it be used from the command-line?
> > > There's no reason that command line arguments can't be enabled.  We'd
> > just
> > > have to decide what to include.  Then again, if we are to use
> > extensive
> > > command line arguments, we might just as well stick with the current
> > build
> > > system.
> > >
> > > >things that scare me a little bit is 15-20MB download
> > > Fair enough, that is a pretty big download.  However, for people who
> > already
> > > have Eclipse, it should be much smaller. Also, it's a one-off download
> > and
> > > most people have broadband these days, so for the added convenience it
> >
> > > brings, hopefully people will put up with the d/l time.
> > >
> > > >We get a couple emails every month about build issues...No dependency
> > on
> > > Ant for the core build stuff....either not having a complete Ant
> > > installation or issues with classpaths associated with Ant
> > >
> > > With this application, these classpath and build issues should
> > (should!!)
> > > disappear, as it will be entirely managed by the Eclipse plugin system
> > and
> > > classloaders.
> > >
> > > >Source in the snapshots...could also help your tool, since it means
> > you
> > > would not have to bundle SubEclipse
> > >
> > > This is definitely true, but I would also like to support downloading
> > the
> > > nightly build, which would still require SVN.  I wouldn't like the
> > user to
> > > have to download the entire tree each time they wanted to update their
> > > nightly snapshot.  But for releases, yes, this would be useful.
> > >
> > > > JavaScript for the build process means more committers can actually
> > help
> > > with the build process
> > >
> > > True, we're a javascript community, not necessarily full of people
> > with
> > > knowledge of Ant.
> > >
> > > > There has to be a command-line tool, and I don't think we can have
> > > dependencies on the base Eclipse packages in our main toolset. Shane,
> > does
> > > that agree with what you're proposing?
> > >
> > > Yes, this tool would not be the only build method available.  It will
> > have
> > > dependancies on Eclipse, obviously enough, and there will be some
> > people who
> > > don't need the functionality that it provides, and simply have one or
> > two
> > > profiles that they always use, and like to run Ant builds directly
> > from the
> > > command line.  The primary goal for this tool is to put a (hopefully)
> > > intuitive UI on top of the main Dojo build process to make it easier
> > for
> > > users to get the source code, and build different profiles without
> > having to
> > > touch the command line, Ant or Subversion.  However, it is not meant
> > to
> > > replace these mechanisms, merely enhance them.
> > >
> > > Shane
> > >
> > >
> > >
> > >
> > > On 19/12/06, Adam L. Peller <adam at peller.org> wrote:
> > > > The way I was reading it, Shane's Eclipse tool would be a useful
> > > > addition for anyone who wants to use Eclipse, but not the exclusive
> > > > way to do Dojo builds.  There has to be a command-line tool, and I
> > > > don't think we can have dependencies on the base Eclipse packages in
> >
> > > > our main toolset.  Shane, does that agree with what you're
> > proposing?
> > > >
> > > > I'm looking at this much the same way that Chris has contributed an
> > > > enhanced Eclipse-based view of dojo.book, which I hope we package
> > and
> > > > distribute in a way that's intuitive for the Eclipse community and
> > > > anyone who chooses to read it off an Eclipse-hosted server.  There
> > are
> > > > no plans to make it the primary server distribution for dojo.book.
> > > >
> > > > -Adam
> > > > _______________________________________________
> > > > dojo-contributors mailing list
> > > > dojo-contributors at dojotoolkit.org
> > > > http://dojotoolkit.org/mailman/listinfo/dojo-contributors
> > > >
> > >
> > >
> > > _______________________________________________
> > > dojo-contributors mailing list
> > > dojo-contributors at dojotoolkit.org
> > > http://dojotoolkit.org/mailman/listinfo/dojo-contributors
> > >
> > >
> > >
> > _______________________________________________
> > dojo-contributors mailing list
> > dojo-contributors at dojotoolkit.org
> > http://dojotoolkit.org/mailman/listinfo/dojo-contributors
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.dojotoolkit.org/pipermail/dojo-contributors/attachments/20061220/3a1a4cf0/attachment.htm