Hi Alexis,

On 26/10/2010, at 09:31, Alexis Tual wrote:

> 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 ?
> 

Sure. It's certainly a bug.

I can take a look on this problem during the weekend.

Cheers,

Henrique

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to