-
Notifications
You must be signed in to change notification settings - Fork 17
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
Using com.ibm.wala.cast.python.ml as a library is problematic due to Maven Shade plug-in #28
Comments
khatchad
changed the title
Using com.ibm.wala.cast.python.ml as a library is problematic due to Maven shade plug-in
Using com.ibm.wala.cast.python.ml as a library is problematic due to Maven Shade plug-in
Apr 14, 2023
Sometimes this can be addressed by shifting classes from dependencies to a different (unlikely to conflict) package name. Is that possible with this plugin? |
Yes, it is. But, I am wondering whether just to use two JARs. The execution one would have some special name. The default JAR would be for library usage. |
PR welcome :-)
…On Apr 14, 2023 at 12:15:21, Raffi Khatchadourian ***@***.***> wrote:
See
https://maven.apache.org/plugins/maven-shade-plugin/examples/attached-artifact.html
—
Reply to this email directly, view it on GitHub
<#28 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABPEUMJBQA4LX46EK6OIWTXBGO4TANCNFSM6AAAAAAW6XWT5Q>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
khatchad
added a commit
to ponder-lab/ML
that referenced
this issue
Apr 15, 2023
msridhar
pushed a commit
that referenced
this issue
Apr 15, 2023
Should be solved by #29. |
khatchad
added a commit
to ponder-lab/ML
that referenced
this issue
May 23, 2023
* Address wala#28. (#29) See https://maven.apache.org/plugins/maven-shade-plugin/examples/attached-artifact.html for reference. * Remove unused footnote. (#31) Forgot to remove this one with the last update. * Lowercase parent pom artifact ID. (#32) Fixes wala#30. * Fix wala#33. (#34) Make consistent by using Jython 3 as a dependency. * Metadata, build script, and warnings (#35) * Remove obsolete bundles. These are being used as JARs now. * Export missing packages. Since wala/ML is now using JAR packaging, this probably doesn't matter. However, it fixes the warnings. And, if it ever gets OSGi component packaged again, we can use it. * Fix build.properities file. Source and data directiories don't exist for these subprojects. * Fix more warnings. * Use verify to run the tests. * Export more packages. * Fix generics hiding warning. * Fix Jython and Jython3 test directory metadata. * Add GH actions file (#40) * Add GH actions file. * Remove optional dependency analysis. Was failing. * Fix path. * Switch Jython repos. * Revert "Switch Jython repos." This reverts commit 20052de. * Print out the stack trace. * Switch to Jython3 for testing ML. * Revert "Print out the stack trace." This reverts commit 8fb7951. * Update run.sh Fix broken resolution. * Ignore failing test. Reinstate once wala#42 is fixed. * Revert "Work around https://github.com/ponder-lab/ML/issues/4." This reverts commit 0e5c334.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
com.ibm.wala.cast.python
currently uses the Maven Shade plug-in:ML/com.ibm.wala.cast.python.ml/pom.xml
Lines 65 to 100 in a8e1d8e
I believe it does this for two reasons:
MANIFEST.mf
file.However, this is problematic for using
com.ibm.wala.cast.python.ml
as a library:The text was updated successfully, but these errors were encountered: