Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maven enhance goal fails because of DataNucleus - "The command line is too long." #49

Open
GoogleCodeExporter opened this issue Aug 24, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

- What steps will reproduce the problem?
run mvn appengine:enhance on project with jars in class path long enough to 
exceed windows command line limit.

- What version of the product are you using? On what operating system?
appengine-maven-plugin v1.8.8.
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 
17:22:22+0200)
Java version: 1.7.0_25, vendor: Oracle Corporation
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"

- Please provide any additional information below.
This is actually problem with DataNucleus described here 
http://code.google.com/p/vosao/issues/detail?id=47 but making the long story 
short:
==============QUOTE==============
Problem

CreateProcess error=87 when running DataNucleus tools under Microsoft Windows 
OS.

Windows has a command line length limitation, between 8K and 64K characters 
depending
on the Windows version, that may be triggered when running tools such as the 
Enhancer
or the SchemaTool with too many arguments.

Solution

When running such tools from Maven or Ant, disable the fork mechanism by 
setting the
option fork="false". 
==============END==============

The solution is to set <fork>false</fork> in configuration section for 
datanucleus-maven-plugin, but since appengine-maven-plugin runs datanucleus on 
behalf, it would be good to have this fork setting covered by appengine plugin 
similar like for enhancerApi.

Just for the completes, this is not blocking problem. I've checked the 
datanucleus plugin source code and it's enough to set the following in pom to 
workaround this:

<properties>
    <fork>false</fork>
</properties>

However, settings may vary from datanucleus release to release. I think it 
would be good idea to update appengine plugin with something similar like 
attached code changes.

Original issue reported on code.google.com by rkrysin...@gmail.com on 4 Jan 2014 at 11:21

Attachments:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant