forked from sarnowski/maven-php-plugin
-
Notifications
You must be signed in to change notification settings - Fork 29
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-php-dependency include behavior #19
Comments
Hi, you should use for your purpose the maven-assembly plugin to build a tar.gz (for exemple) from tous source, and inject dependencies in your tar.gz (do not put extract action for your .phar deps, it will fail otherwise). For our project, here is our 'webappassembly descriptor' 👍
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I would like to create project with following structure:
/lib/somelibrary-1.phar
/lib/somelibrary-2.phar
...
index.php
somepage.php
I created 3 projects.
In website/pom.xml I added somelibrary-1 and somelibrary-2 as dependencies.
As result they are unpacked to target/php-deps
This is not what I want. So, following this tutorial:
http://www.php-maven.org/tags/2.0.2/tut-dependencymanagement.html
Which states:
"The include action tells maven to not extract the phar file but instead put it on php include path."
I added to website/pom.xml
Unfortunately it doesn't work as I expected.
As result dependency is not visible in target/php-deps and is not available anwyhere in target dir!
Info says that "will be added on include path".
But what does it mean?
Is there any way to bundle unextracted phar with webapplication?
The text was updated successfully, but these errors were encountered: