Hi Ben,
Ok I can refactor the Commons MethodDefinitionAttributes to SecurityCommonsAttributes
and remove the subproject from the project.properties.
Cheers,
Mark
On 9/8/05, Ben Alex <[EMAIL PROTECTED]> wrote:
Mark St.Godard wrote:
> Ben et al,
>
> I have checked in the first Annotations sample... basically a
> straightforward port of the "samples/attributes" -->
> "samples/annotations".
> Note: This sample project requires the
> acegi-security-tiger-0.9.0-SNAPSHOT.jar, so please ensure its built to
> your local maven repo.
> See core-tiger/
>
> Ben have a quick look, and let me know if you have any problems with
> your build, etc.
> Mine runs through fine, compiles, tests pass, etc..
>
Good work Mark. I would suggest that we move MethodDefinitionAttributes
to the net.sf.acegisecurity.annotation package, and rename the class to
SecurityCommonsAtributes.
> Next I will look at the actual Contacts sample... I think the last we
> talked on this we were possibly going to deprecate the Commons
> Attributes / plugin, etc. ? (i.e. let the commons-attributes folk
> build by hand ?)
>
> I think you mentioned it causes problems with Java 5 sources and the
> attributes plugin.
>
Yes, the commons-attributes-plugin in Maven does not work if you're
running Java 5 source compatibility. This only impacts the ability to
run the /samples/attributes/project.xml. I would suggest we remove this
subproject from the /project.properties' maven.multiproject.includes.
Cheers
Ben
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Home: http://acegisecurity.sourceforge.net
Acegisecurity-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
