[JBoss JIRA] Created: (JBPM-1687) fix build scripts for spaces
by Tom Baeyens (JIRA)
fix build scripts for spaces
----------------------------
Key: JBPM-1687
URL: https://jira.jboss.org/jira/browse/JBPM-1687
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Components: PVM
Reporter: Tom Baeyens
Priority: Critical
currently, the build doesn't work in case there are spaces in the project path. (e.g. when checking out in the "Documents and Settings" folder, as hudson does by default.
this can be easily tested by checking out the pvm in a directory called "pvm in space". Then the docbook generation fails like this:
[INFO] Processing master.xml
[INFO] Executing tasks
[copy] Copying 25 files to C:\wstempranillo\pvm in space\modules\core\target\manual\html\reference\images
[INFO] Executed tasks
[INFO] [docbkx:generate-pdf {execution: doc-reference pdf}]
[INFO] Processing master.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to open C:\wstempranillo\pvm in space\modules\core\target\manual\pdf\reference\master.fo for input.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 3 months
[JBoss JIRA] Commented: (JBPM-1403) jBPM3 module ownership
by Alejandro Guizar (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-1403?page=com.atlassian.jira.plug... ]
Alejandro Guizar commented on JBPM-1403:
----------------------------------------
I will take enterprise once you are done with JBPM-1287. I might as well take core, as I have been doing quite some work there.
> jBPM3 module ownership
> ----------------------
>
> Key: JBPM-1403
> URL: https://jira.jboss.org/jira/browse/JBPM-1403
> Project: JBoss jBPM
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Productization
> Reporter: Thomas Diesler
> Assignee: Tom Baeyens
> Fix For: jBPM 3.3.0 CR1
>
>
> I am in the search of component owners for these modules in jBPM3. Every component should be owned by a living soul that I can talk to if there is an issue with that module.
> console
> distribution (thomas)
> enterprise
> jbpm4jsf
> jpdl/core
> jpdl/db
> jpdl/examples
> jpdl/identity
> jpdl/simulation
> jpdl/userguide (tom)
> jpdl/ws (heiko)
> I filled in the owners for the modules that I know of. Please provide the missing information.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 4 months
[JBoss JIRA] Commented: (JBPM-1403) jBPM3 module ownership
by Thomas Diesler (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-1403?page=com.atlassian.jira.plug... ]
Thomas Diesler commented on JBPM-1403:
--------------------------------------
Current modules are
hudson (thomas)
console (heiko)
distribution (thomas)
enterprise
jbpm4jsf
jpdl/core
jpdl/db
jpdl/identity
jpdl/integration (thomas)
jpdl/simulation
jpdl/userguide (tom)
> jBPM3 module ownership
> ----------------------
>
> Key: JBPM-1403
> URL: https://jira.jboss.org/jira/browse/JBPM-1403
> Project: JBoss jBPM
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Productization
> Reporter: Thomas Diesler
> Assignee: Tom Baeyens
> Fix For: jBPM 3.3.0 CR1
>
>
> I am in the search of component owners for these modules in jBPM3. Every component should be owned by a living soul that I can talk to if there is an issue with that module.
> console
> distribution (thomas)
> enterprise
> jbpm4jsf
> jpdl/core
> jpdl/db
> jpdl/examples
> jpdl/identity
> jpdl/simulation
> jpdl/userguide (tom)
> jpdl/ws (heiko)
> I filled in the owners for the modules that I know of. Please provide the missing information.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 4 months