I just re-enabled the samples build. When I refactored the build into
modules, I forgot to enable the samples. They are now enabled like any
other module. Also, the dist directory (<projectRoot>/jsecurity-{version}/
is cleaner now, with the 'full' jsecurity.jar in this directory and the
modules and samples .jars/wars in their respective subdirectories. This is
cleaner and easier to peruse.
Finally, although the samples builds are re-enabled and building/packaging
functions correctly, I'm fairly certain a few of them would fail at
runtime. I created an issue to track this:
https://issues.apache.org/jira/browse/JSEC-47
This would be a good issue for someone to work on that hasn't had much
runtime experience with JSecurity - they'll experience first hand how to
debug/set-up an application. Most of the samples already have a head-start
and wouldn't take much work to get one or more running again. Any takers?
;)
- Les
On Wed, Jan 21, 2009 at 3:45 PM, Les Hazlewood <[email protected]>wrote:
> Interesting - although again I can't test this out until tonight, it seems
> that a classes dir that is being referenced in the ant file does not exist
> on disk. Doesn't sound like an Ivy issue to me. I'll check it out when I
> get home. I'll prolly blast my local Ivy cache anyway just in case.
>
>
> On Wed, Jan 21, 2009 at 3:20 PM, Emmanuel Lecharny <[email protected]>wrote:
>
>> Jeremy Haile wrote:
>>
>>> I just built the samples successfully with no errors with the latest code
>>> from trunk. If you provide more information about how/why your targets
>>> failed, I'd be happy to help diagnose/correct the problem.
>>>
>>
>> I got the same errors than Alan. I just did a full build (ant), and then a
>> build samples :
>>
>> BUILD FAILED
>> /home/elecharny/apacheds/jsecurity/trunk/common.ant.xml:118:
>> /home/elecharny/apacheds/jsecurity/trunk/build/classes not found.
>>
>>
>> Java 1.6.0_10
>> Apache Ant version 1.7.0 compiled on December 13 2006
>>
>> http://repo1.maven.org/maven2/org/apache/ivy/ivy/2.0.0-beta2/ivy-2.0.0-beta2.jar
>> linux
>> fresh Jsecurity check out.
>>
>> I suggest you doom your ivy repo, and co jsecurity from scratch.
>>
>> --
>> --
>> cordialement, regards,
>> Emmanuel Lécharny
>> www.iktek.com
>> directory.apache.org
>>
>>
>>
>
