I'm doing some work on some of the JIRA issues assigned to me (finally
getting a chance) and I checked out the project and noticed that the
.classpath was referring to Spring 1.2.9 while the pom refers to 2.0.6.
Anyone have any issues if I update the .classpath file to reflect the
latest
I think the .classpath files should be removed. They are doomed to be stale.
The project is now built with maven2 completely. Maven can create the
.classpath files as needed.
Executing mvn eclipse:eclipse from the project root will create
everything needed.
On 9/10/07, Scott Battaglia [EMAIL
Executing mvn eclipse:eclipse creates projects for each of the modules,
which is probably not what we want.
-Scott
Ray Krueger wrote:
I think the .classpath files should be removed. They are doomed to be stale.
The project is now built with maven2 completely. Maven can create the
.classpath
Why isn't it?
If you're only interested in working on core then...
cd core
mvn eclipse:eclipse
On 9/10/07, Scott Battaglia [EMAIL PROTECTED] wrote:
Executing mvn eclipse:eclipse creates projects for each of the modules,
which is probably not what we want.
-Scott
Ray Krueger wrote:
I
I'm not trying to get into a discussion on how one should use Eclipse
(if I was working with a multi-module project I'd actually use IDEA).
My point was that this behavior and Eclipse project structure would be
different then what it is now by using mvn eclipse:eclipse.
My immediate need is
Ray Krueger wrote:
Ooh, here's an idea!
Have Maven generate a new .classpath file and check that in.
The plugin nicely doesn't generate one for the parent POM. Otherwise we
wouldn't still be having this discussion ;-)
The way to handle the flat structure is extremely kludgy:
Luke,
You've assigned JIRA issue SEC-516 to me (maybe believing that it was
specifically CAS-related). Its not CAS related so its not clear to me
whether I should be handling it or not.
-Scott
-
This SF.net email is
I've been using Intellij 7's maven support to generate the project files
then switching back to Intellij 6 to actually use them (still too many
bugs in 7). Don't mind what happens with the eclipse files as I'm barely
aware they exist :).
On the commons logging front, we should probably stick with
It was probably assigned because we saw the mention of Cas in there
somewhere. Feel free to mark it as unassigned :).
Scott Battaglia wrote:
Luke,
You've assigned JIRA issue SEC-516 to me (maybe believing that it was
specifically CAS-related). Its not CAS related so its not clear to me
BTW there is a new Eclipse plugin for Maven that can import maven
projects directly and keep the classpath synced from the pom
http://code.google.com/p/q4e/
Disclaimer: I work on the project
On 9/10/07, Ray Krueger [EMAIL PROTECTED] wrote:
Why isn't it?
If you're only interested in working on
Hi Shi,
I am *very* interested in finding out how I can set up Acegi Security to
support a role hierarchy. You mentioned in #1 below that Acegi Security
can be configured to do that. Could you point me in the right direction
by letting me know which documentation I can read to configure my
hi, Pat
That's my fault. What I mean is that you can define specific roles to you
application.
But take a looke at this,
http://opensource.atlassian.com/projects/spring/browse/SEC-232
I believe someone has already done lot of work in this field.
Regards,
Shi
On 9/11/07, [EMAIL PROTECTED]
12 matches
Mail list logo
