abdera-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Duncan Jr" <stephen.dun...@gmail.com>
Subject Re: problem building for Eclipse
Date Thu, 17 Apr 2008 12:21:52 GMT
The following should work:

mvn install
mvn eclipse:eclipse

-Stephen

On Thu, Apr 17, 2008 at 3:56 AM, David Calavera <david.calavera@gmail.com>
wrote:

> On Thu, Apr 17, 2008 at 8:34 AM, Dan Diephouse <
> dan.diephouse@mulesource.com>
> wrote:
>
> > As a Maven guy, might I suggest:
> >
> > $ cd abderatrunk
> > $ mvn eclipse:eclipse
> >
> > In eclipse:
> > File -> Import -> Existing Projects
> >
> > Enter the directory to the abdera source and hit OK.
> >
> > (thats off the top of my head, hopefully its right)
>
>
> This goal doesn't work. Maven can't resolve any artifacts:
>
> [INFO] Building Abdera Bundle Jar
> [INFO]    task-segment: [eclipse:eclipse]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Preparing eclipse:eclipse
> Downloading:
>
> http://people.apache.org/repo/m2-incubating-repository/org/apache/abdera/abdera-extensions-wsse/0.5.0-incubating-SNAPSHOT/abdera-extensions-wsse-0.5.0-incubating-SNAPSHOT.jar
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> I'm not a maven expert and I don't know how to tell this goal that it must
> compile and install the dependencies first.
>
>
> >
> > Dan
> >
> >
> > Jun Yang wrote:
> >
> > > Hi all,
> > >
> > > I am following the instructions in BUILD to build Abdera head for
> > > Eclipse:
> > >
> > > Without Maven:
> > >  From within eclipse, check out each of the following
> > >  as projects.  Do not worry about the project type for now:
> > >
> > >     * /java/trunk/build              project name: build
> > >     * /java/trunk/core               project name: core
> > >     * /java/trunk/dependencies       project name: dependencies
> > >     * /java/trunk/docs               project name: docs
> > >     * /java/trunk/examples           project name: examples
> > >     * /java/trunk/parser             project name: parser
> > >     * /java/trunk/server             project name: server
> > >     * /java/trunk/security           project name: security
> > >     * /java/trunk/spring             project name: spring
> > >     * /java/trunk/extensions         project name: eclipse
> > >
> > >    From the eclipse workspace root, invoke:
> > >      ant -f build/build.xml init
> > >
> > >    Then, from the eclipse workspace root, invoke
> > >      ant -f snell_sandbox/eclipse/setupeclipse.xml
> > >
> > >    This will copy all of the necessary eclipse project files over to
> > >    the appropriate projects in the eclipse workspace.  Restart your
> > >    eclipse workbench and all of your projects should be ready to go.
> > >
> > >    Note: the security module will contain compile errors due to
> missing
> > >    XML Security jars.  To build and use that module, you'll need to
> > >    download the Apache XML Security and the Bouncy Castle Crypto
> > >    implementation.
> > >
> > > Problem is there is no "snell_sandbox/eclipse/setupeclipse.xml".
> > >  "snell"
> > > doesn't appear in build/build.xml so it's probably not generated by
> that
> > > first command of "ant -f build/build.xml init".  Any pointers?
> > >
> > > BTW, why is the last project named "eclipse" not "extensions" like the
> > > others?
> > >
> > > Thanks!
> > >
> > > Jun
> > >
> > >
> > >
> >
> >
> > --
> > Dan Diephouse
> > MuleSource
> > http://mulesource.com | http://netzooid.com
> >
>
>
>
> --
> David Calavera
> http://www.thinkincode.net
>



-- 
Stephen Duncan Jr
www.stephenduncanjr.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message