You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Nigel Magnay (JIRA)" <ji...@codehaus.org> on 2007/02/27 17:18:15 UTC
[jira] Created: (CONTINUUM-1188) JPox relies on java being on the
path, but maven does not, so fails with a file not found exception
JPox relies on java being on the path, but maven does not, so fails with a file not found exception
---------------------------------------------------------------------------------------------------
Key: CONTINUUM-1188
URL: http://jira.codehaus.org/browse/CONTINUUM-1188
Project: Continuum
Issue Type: Bug
Affects Versions: 1.1
Environment: ubuntu 6.10
Reporter: Nigel Magnay
Priority: Trivial
This may be a jpox bug (whatever jpox is), but you get a file not found exception if java isn't on your path.
"Error while executing the JPox tool 'org.jpox.enhancer.JPOXEnhancer'"
if build.sh checked that it was, it would avoid this failure case.
Also it relies on javax files being available, so the docs should probably tell you how to get these.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-1188) JPox relies on java being on the
path, but maven does not, so fails with a file not found exception
Posted by "Jesse McConnell (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse McConnell updated CONTINUUM-1188:
---------------------------------------
Fix Version/s: 1.1-alpha-#
> JPox relies on java being on the path, but maven does not, so fails with a file not found exception
> ---------------------------------------------------------------------------------------------------
>
> Key: CONTINUUM-1188
> URL: http://jira.codehaus.org/browse/CONTINUUM-1188
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.1-alpha-1
> Environment: ubuntu 6.10
> Reporter: Nigel Magnay
> Priority: Trivial
> Fix For: 1.1-alpha-#
>
>
> This may be a jpox bug (whatever jpox is), but you get a file not found exception if java isn't on your path.
> "Error while executing the JPox tool 'org.jpox.enhancer.JPOXEnhancer'"
> if build.sh checked that it was, it would avoid this failure case.
> Also it relies on javax files being available, so the docs should probably tell you how to get these.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-1188) JPox relies on java being on the
path, but maven does not, so fails with a file not found exception
Posted by "Andy Jefferson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97409 ]
Andy Jefferson commented on CONTINUUM-1188:
-------------------------------------------
FYI JPOX provides persistence of Java objects to datastores, used by Continuum. Obviously the JPOX enhancer requires Java to be able to run, just as it requires jdo2-api.jar to be in the CLASSPATH - all documented clearly in the JPOX docs. This issue is Continuum-specific
> JPox relies on java being on the path, but maven does not, so fails with a file not found exception
> ---------------------------------------------------------------------------------------------------
>
> Key: CONTINUUM-1188
> URL: http://jira.codehaus.org/browse/CONTINUUM-1188
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.1-alpha-1
> Environment: ubuntu 6.10
> Reporter: Nigel Magnay
> Priority: Trivial
> Fix For: 1.1-alpha-#
>
>
> This may be a jpox bug (whatever jpox is), but you get a file not found exception if java isn't on your path.
> "Error while executing the JPox tool 'org.jpox.enhancer.JPOXEnhancer'"
> if build.sh checked that it was, it would avoid this failure case.
> Also it relies on javax files being available, so the docs should probably tell you how to get these.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira