Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Process Manager (Stardust) » Build problems: time to update the project wiki?
Build problems: time to update the project wiki? [message #990464] Wed, 12 December 2012 15:38 Go to next message
Robert Brodt is currently offline Robert Brodt
Messages: 601
Registered: August 2010
Location: Colorado Springs, CO
Senior Member

Hi all,

I'm trying to build the project from source as described in the project wiki (http://wiki.eclipse.org/Stardust/Source_Code) and it looks like at least one new plugin has been added (deploy.jee) - maybe it's time to update the wiki page? Wink

After cloning deploy.jee.git to my local repo, I can get a little further in the build process, but it looks like there's a jar missing. I'm seeing the following error:

[WARNING] Missing POM for org.eclipse.stardust.engine:carnot-base:jar:9.9.9-SNAPSHOT
[ERROR] Internal error: java.lang.RuntimeException: Could not resolve project dependencies: Missing:
[ERROR] ----------
[ERROR] 1) org.eclipse.stardust.engine:carnot-base:jar:9.9.9-SNAPSHOT
[ERROR]
[ERROR] Try downloading the file manually from the project website.
[ERROR]
[ERROR] Then, install it using the command:
[ERROR] mvn install:install-file -DgroupId=org.eclipse.stardust.engine -DartifactId=carnot-base -Dversion=9.9.9-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
[ERROR]
[ERROR] Alternatively, if you host your own repository you can deploy the file there:
[ERROR] mvn deploy:deploy-file -DgroupId=org.eclipse.stardust.engine -DartifactId=carnot-base -Dversion=9.9.9-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[ERROR]
[ERROR] Path to dependency:
[ERROR] 1) org.eclipse.stardust.modeling.engine:org.eclipse.stardust.ide.engine.base:pom:9.9.9-SNAPSHOT
[ERROR] 2) org.eclipse.stardust.engine:carnot-base:jar:9.9.9-SNAPSHOT
[ERROR]
[ERROR] ----------
[ERROR] 1 required artifact is missing.
[ERROR]
[ERROR] for artifact:
[ERROR] org.eclipse.stardust.modeling.engine:org.eclipse.stardust.ide.engine.base:pom:9.9.9-SNAPSHOT
[ERROR]
[ERROR] from the specified remote repositories:
[ERROR] eclipse-main (http://download.eclipse.org/releases/helios/, releases=false, snapshots=false),
[ERROR] eclipse-wtp (http://download.eclipse.org/webtools/downloads/drops/R3.2.3/R-3.2.3-20110217214612/repository/, releases=false, snapshots=false),
[ERROR] build.tools-repo (file://localhost/c:/Users/bbrodt/git/stardust/build.tools/lib, releases=true, snapshots=false),
[ERROR] stardust-3rdparty-repo (https://infinity.sungard.com/repository/ipp-3rd-party, releases=true, snapshots=false),
[ERROR] central (http://repo1.maven.org/maven2, releases=true, snapshots=false)


Also, I would like to be able to import the projects into an eclipse workspace for debugging. I am using the "Import existing Maven Projects" wizard to do this, but can't get past an importer error "Artifact ID is null" Unfortunately, the wizard won't tell me which artifact is causing this problem.

Oh, one more thing: is it possible to build this project with Indigo instead of Helios? It looks like there aren't any specific dependencies on 3.6.2

Any help here would be appreciated.

Cheers,
Bob
Re: Build problems: time to update the project wiki? [message #991142 is a reply to message #990464] Mon, 17 December 2012 13:40 Go to previous message
Sven Rottstock is currently offline Sven Rottstock
Messages: 24
Registered: December 2012
Junior Member
Hi Robert,

many thanks for your hint. I've updated the Wiki as follows:


  • Mentioned the deploy.jee Git repository
  • Updated "Building Stardust" section to emphasize which tasks are needed if you want to use your own Maven settings file instead of the one in build.tools/conf/m2
  • Added the section "Importing projects into Eclipse"


The second item should help you to fix your build issue. But let me explain this in short: unfortunately we have two dependency management systems, namely Maven and Ivy. The build process is prepared to use the Maven settings file which is located at build.tools/conf/m2. If you want to use the user or the global Maven settings file then you have to provide this as a property in build.tools/etc/private.properties.

Sorry for the inconvenience and appreciate your patience.

Cheers,
Sven
Previous Topic:Starting process using JMS Trigger
Next Topic:Stardust execution issue in Linux
Goto Forum:
  


Current Time: Sat Sep 20 08:16:14 GMT 2014

Powered by FUDForum. Page generated in 0.08415 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software