Bug 778702 (SOA-1166) - jBPM exmaples cannot be compiled
Summary: jBPM exmaples cannot be compiled
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1166
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBPM - within SOA, Build Process, Configuration, Deployment
Version: 4.3 CP01
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.3 CP01
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-12 12:32 UTC by Jiri Pechanec
Modified: 2009-12-02 00:22 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-20 08:10:54 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 778599 0 high CLOSED jBPM examples - example.base.build.xml was removed - corresponding pom.xml file was not added - how do users build/run t... 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-1166 0 None None None Never

Internal Links: 778599

Description Jiri Pechanec 2009-02-12 12:32:41 UTC
Date of First Response: 2009-02-17 05:39:59
project_key: SOA

If I try to compile jBPM exmaples in the directory jbpm-jpdl/examples the build process fails with message
org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.jbpm.jbpm3:jbpm for project: org.jbpm.jbpm3:jbpm-examples:jar:null for project org.jbpm.jbpm3:jbpm-examples:jar:null
        at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: org.jbpm.jbpm3:jbpm for project: org.jbpm.jbpm3:jbpm-examples:jar:null for project org.jbpm.jbpm3:jbpm-examples:jar:null
        at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1370)
        at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:821)
        at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
        at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198)
        at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
        at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
        at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)

The pom.xml contains the defintion of parent project
  <!-- Parent -->
  <parent>
    <groupId>org.jbpm.jbpm3</groupId>
    <artifactId>jbpm</artifactId>
    <version>3.2.5.SP1</version>
    <relativePath>../../pom.xml</relativePath>
  </parent>

But the file does not exist

Comment 1 Julian Coleman 2009-02-17 10:39:59 UTC
1) Compiling the examples on a machine where jBPM 3.2.5 has been built does not show the problem.
Presumably, the parent POM is already cached locally (~/.m2).

2) Compiling the examples on a fresh machine shows maven trying to fetch the parent POM and failing:

  [INFO] Scanning for projects...
  Downloading: http://repo1.maven.org/maven2/org/jbpm/jbpm3/jbpm/3.2.5.SP1/jbpm-3.2.5.SP1.pom
  [INFO] ------------------------------------------------------------------------
  [ERROR] FATAL ERROR
  [INFO] ------------------------------------------------------------------------
  [INFO] Failed to resolve artifact.
  
  GroupId: org.jbpm.jbpm3
  ArtifactId: jbpm
  Version: 3.2.5.SP1

  Reason: Unable to download the artifact from any repository

    org.jbpm.jbpm3:jbpm:pom:3.2.5.SP1

  from the specified remote repositories:
    central (http://repo1.maven.org/maven2)

So, it looks like we need to make the jBPM 3.2.5 SP1 POM available somewhere.

Comment 2 Thomas Diesler 2009-02-17 13:58:28 UTC
You need to run 

> mvn install

This copies the maven output artefacts to your local repo

Comment 3 Julian Coleman 2009-02-17 15:47:04 UTC
Any mvn command line (install, compile) will produce the error, as we have nowhere to fetch the
output artifacts from.  In the jBPM installation, we have the examples directory, which includes the
POM, but none of the other parts of the source, nor any hints as to where to get the jBPM artifacts.
So, maven looks for the artifacts in the default repository (repo1.maven.org).  For users who install
jBPM, there needs to be some way to build the examples.  Even better, a way to build the examples
with no Internet connection, i.e., we ship everything that they need.


Comment 4 Thomas Diesler 2009-02-19 10:03:31 UTC
Link: Added: This issue depends JBPM-2050


Comment 5 Julian Coleman 2009-02-24 15:08:15 UTC
The examples can now be compiled, as repository.jboss.org is looked at for the main artifact.
When we build the next CR, we will need to upload the jBPM main artifact to the repository.

It will not be possible to build the examples without first downloading the artifact to the
local repository (~/.m2).


Comment 6 Julian Coleman 2009-03-19 15:17:21 UTC
From Alejandro Guizar in SOA-647:
  jBPM 3.2.5.SP4 is tagged and published to the maven repo
(See also JBPM-2112)


Comment 7 Jiri Pechanec 2009-03-20 08:10:54 UTC
Verified in CR5

Comment 8 Alejandro Guizar 2009-12-02 00:22:02 UTC
Link: Added: This issue related SOA-1072



Note You need to log in before you can comment on or make changes to this bug.