Maven build and stdFrameworks = true
Maven build and stdFrameworks = true
- Subject: Maven build and stdFrameworks = true
- From: Alexis Tual <email@hidden>
- Date: Tue, 26 Oct 2010 13:31:22 +0200
| Hi list and fellow maven users,
the deployment guys want to have woa's without standard webobjects frameworks embedded. This can be done with the skipAppleProvidedFrameworks param but unfortunately the generated Classpath*.txt do not contain the lines :
WOROOT/Library/Frameworks/JavaFoundation.framework/Resources/Java/javafoundation.jar
WOROOT/Library/Frameworks/JavaWebObjects.framework/Resources/Java/javawebobjects.jar
WOROOT/Library/Frameworks/JavaEOControl.framework/Resources/Java/javaeocontrol.jar
WOROOT/Library/Frameworks/JavaEOAccess.framework/Resources/Java/javaeoaccess.jar
WOROOT/Library/Frameworks/JavaXML.framework/Resources/Java/javaxml.jar
WOROOT/Library/Frameworks/JavaJDBCAdaptor.framework/Resources/Java/javajdbcadaptor.jar
WOROOT/Library/Frameworks/JavaEODistribution.framework/Resources/Java/javaeodistribution.jar
WOROOT/Library/Frameworks/JavaEOApplication.framework/Resources/Java/javaeoapplication.jar
I tried to correct this by setting the stdFrameworks="true" in wolifecycle.build.xml but that fails :
[INFO] Failed to execute: Executing Ant script: wolifecycle.build.xml [build-woapplication]: Failed to execute. /Users/roger/Documents/Dev/workspaceMyApp/bar/Library/Frameworks not found.
I understand that this requirement is a deviation of maven main usage : verify and include all dependencies at build time. But as webobjects jars will not change for another decade (at least :)), that's an acceptable behavior, what do you think ? Should i fill a jira issue for this ?
Thanks for your answers
Cheers,
Alex
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden