[
https://issues.apache.org/cayenne/browse/CAY-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734#action_12734
]
Kevin Menard commented on CAY-985:
----------------------------------
I'm not a huge fan of splitting the modules myself, but there could be value in
doing so even for ant builds. On most of our internal apps, we've kicked maven
to the curb. But, we still use maven-ant-tasks for dependency management in an
ant environment. This allows us to scope dependencies appropriately and makes
it a bit easier in WAR packaging, as we don't need a bunch of delete lines.
The same would be true of ant + Ivy.
I agree with the notion that there's a better way of dealing with the problem
than adding more complexity to our artifact build process, however.
> Cayenne 3.0M3 cayenne-server maven artifact lacks VPP
> -----------------------------------------------------
>
> Key: CAY-985
> URL: https://issues.apache.org/cayenne/browse/CAY-985
> Project: Cayenne
> Issue Type: Bug
> Components: Cayenne Core Library
> Affects Versions: 3.0
> Reporter: Jon Sharp
> Assignee: Andrus Adamchik
>
> The published artifact for cayenne-server 3.0M3 on ibiblio appears to lack
> the necessary VPP dependency classes. This lack of VPP is evident in the
> failure of the cgen ant task:
> Embedded error: The following error occurred while executing this line:
> /home/.../build.xml:16: java.lang.NoClassDefFoundError:
> foundrylogic/vpp/VPPConfig
> foundrylogic.vpp.VPPConfig
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
