Hey Folks,
Any tips / pointers for calling Java code from Jelly / Maven's maven.xml?
I'm having classpath issues and don't want to expose it as a plugin, rather
just call it from maven.xml...
ta
diyfiesta wrote:
Hi Folks,
I've writen a POJO to do something useful and wanted to use
yep, ${root.maven} and just root.maven in the jellybean classLoader
attribute gave the same results :(
Arnaud HERITIER wrote:
You can try the classloader named root.maven
Arnaud
diyfiesta wrote:
hmmm,
in the partial listing below, for namespaces I have;
xmlns:j=jelly:core
goal for example).
I think that your classes are defined in the default classloader.
Arnaud
diyfiesta wrote:
Hey Folks,
Any tips / pointers for calling Java code from Jelly / Maven's maven.xml?
I'm having classpath issues and don't want to expose it as a plugin,
rather just call
in
that...
:-).
-Original Message-
From: diyfiesta [mailto:[EMAIL PROTECTED]
Sent: Monday, November 13, 2006 9:53 AM
To: users@maven.apache.org
Subject: Re: [M1] AspectJ with two source trees (main/src main/test)
So, looking into this more (and having created a simple example project
to have a property that says to run
AspectJ on the tests compilation too?
-Original Message-
From: diyfiesta [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 14, 2006 3:01 AM
To: users@maven.apache.org
Subject: RE: [M1] AspectJ with two source trees (main/src main/test)
Hi
Hi,
I'm using M1 so can't comment direclty on M2 stuff, but thought I'd
chip in with some thoughts on source file placement.
I've tried a few different approaches and have settled on putting the
aspects in with the java source as I view them as java-like if not
strict java (after all AJDT lets
posted incase its useful or intersting to anyone :)
diyfiesta wrote:
Thanks Jeff,
hmmm, I kind of thought that this wouldn't be too far off the beaten track
but perhaps it is!
I managed to change most of my aspects to use execution instead of call
(which in my case makes more sense, I just
/classes/...
but the tests run from a folder called
target/test-classes/...
which has the compiled test code, but not the aspectj compiled code. So, if
a test is affected by an aspect, it isn't in this folder.
diyfiesta wrote:
Hi,
Thanks for the note, I tried this but still don't have
Hi,
Thanks for the note, I tried this but still don't have any luck, for
example, I'm using the convention main/src/java and main/src/test for my
source trees, so adding an src/aspectj folder doesn't really fit in, if I
add it to main/src/aspectj, I get the same problem (and just for
Hi Folks,
Was hoping someone could give me a pointer with a problem I'm having with
the aspectj plugin...
I've got my source code under main/src and the unit tests under main/test,
however I can't get aspectj compiling both. I added this to my project.xml
hoping it would pick up both, but it
as an
absolute path : c:/target/test-classes/testing.policy
Did you try ? : -Djava.security.policy=target/test-classes/testing.policy
Arnaud
On 9/22/06, diyfiesta [EMAIL PROTECTED] wrote:
Hi Folks,
Bit stuck on trying to run my tests with a security manager enabled and a
specific policy file
Hi Folks,
Bit stuck on trying to run my tests with a security manager enabled and a
specific policy file. I added the security manager system property and
policy setting using the following in the properties file
(project.properties) and have the policy file set as a resource under for
the unit
12 matches
Mail list logo