[jbpm-issues] [JBoss JIRA] Work logged: (JBPM-3033) jbpm3 build javadoc error

[Alejandro Guizar (JIRA)]

     [ https://issues.jboss.org/browse/JBPM-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel\#worklog-{worklog.getId()} ]

Alejandro Guizar logged work on JBPM-3033:
------------------------------------------

                Author: Alejandro Guizar
            Created on: 27/Jan/11 7:20 PM
            Start Date: 27/Jan/11 6:54 PM
    Worklog Time Spent: 2 hours, 17 minutes 
      Work Description: Upgrade to maven-javadoc-plugin 2.7.
Disable offline links detection.


Issue Time Tracking
-------------------

    Time Spent: 2 hours, 17 minutes
    Worklog Id:     (was: 12423695)


> jbpm3 build javadoc error
> -------------------------
>
>                 Key: JBPM-3033
>                 URL: https://issues.jboss.org/browse/JBPM-3033
>             Project: jBPM
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Runtime Engine
>    Affects Versions: jBPM 3.2.9
>            Reporter: Julian Coleman
>            Assignee: Alejandro Guizar
>              Labels: build, javadoc, jbpm3, maven, profile
>             Fix For: jBPM 3.2.x
>
>   Original Estimate: 0 minutes
>          Time Spent: 2 hours, 17 minutes
>  Remaining Estimate: 0 minutes
>
> I had a chance to look in more detail at the error that I was getting with the jBPM builds.  It only happens when running -Prelease (-Psoa, -Pdistro) and it only happens if this is the very first build for a version.
> To reproduce it, change -SNAPSHOT in the pom.xml files to something that does not exist, e.g. -FOO. Then run `mvn -Prelease -Dmaven.test.skip=true install`.  You will see that the javadoc phase in "jBPM3 - Core" tries to use modules that aren't yet available (it fails trying to find org.jbpm.jbpm3:jbpm-jpdl:pom:3.2.10-FOO).
> I noticed this because we want to change the SOA build in MEAD to just use the jBPM release, and then we can remove the SOA profile.  MEAD has its own repository, and has no access to any other repository.  So, whan I tried to build jBPM -Prelease in MEAD, it failed.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira