[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Newsgroup Home]
|
[news.eclipse.technology.ajdt] Re: Dev vs Prod aspects?
|
- From: Andrew Eisenberg <andrew.eisenberg@xxxxxxxxxxxxxxxx>
- Date: Mon, 10 Aug 2009 20:35:29 -0700
- Newsgroups: eclipse.technology.ajdt
- Organization: EclipseCorner
- Thread-index: AcoaNMWkau9un22tB06J6U01dnxj1A==
- Thread-topic: Dev vs Prod aspects?
- User-agent: Microsoft-Entourage/12.20.0.090605
There's no specific documentation on this. However, you may want to take a
look at Ramnivas Laddad's AspectJ in Action (I think 2nd edition is already
out, or will be soon).
I does seem to me that if you keep your aspects in their own directory, it
is simple to include the directory in compilation in test builds, but not in
production builds.
Or, a simpler way would be to use the Java compiler for prod builds and AJC
for test builds.
On 10/08/09 2:53 PM, in article
c694788cf98e41da85df886347f4aebe$1@xxxxxxxxxxxxxxx, "Michael Giroux"
<michael_giroux@xxxxxxxxxxxxxxxx> wrote:
> Can someone point me to documentation that describes how to enable aspects
> for different types of build? For example, I need to apply an aspect to a
> method in development mode, but for production, we cannot have the aspect
> applied.
>
> Is there a convenient way to do this?
>
> BTW, our production build is accomplished using standalone ANT if this
> helps.
>
> Thanks
> Michael
>