RE: aspectj error

2007-09-10 Thread Michal Palička
Hello,

to get rid of the "bad version number found" warning, try to add the correct 
aspectjtools dependency
to the aspectj-maven-plugin:


org.codehaus.mojo
aspectj-maven-plugin

...


...



aspectj
aspectjtools
1.5.3
compile




Hope this helps
Michal Palicka


-Original Message-
From: Alessandro Di Bella [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 10, 2007 02:26 AM
To: Maven Users List
Subject: aspectj error

Hi,
I'm trying to compile using aspectj and I keep getting the following error:

the parameter thisJoinPoint is not bound in [all branches of] pointcut
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

The plugin is configured as follow:

org.codehaus.mojo
aspectj-maven-plugin



compile
test-compile




1.5
1.5



and during the build I get this warning:
[WARNING] bad version number found in 
/home/amabboni/.m2/repository/aspectj/aspectjrt/1.5.3/aspectjrt-1.5.3.jar 
expected 1.5.2a found 1.5.3

I tried with the 1.5.2a version but no luck neither.

Any help would be greatly appreciated.

Thanks

Alessandro


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Assembly: snapshot archive name with timestamp

2007-08-07 Thread Michal Palička
Hello,

is it possible to set up the assembly plugin, so that the name of the resulting 
snapshot archive contains the timestamp?

Example:
current name: myproject-1.0-SNAPSHOT-bin.zip
desired name: myproject-1.0-20070807.140024-bin.zip

Thank you in advance

Michal Palicka


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Local modules

2007-03-08 Thread Michal Palička
Hello all,

is there a way to specify a module as "local", so that the module could not be 
deployed 
to shared repository? The module should be able to install to my local 
repository though.

Perhaps I should describe our use case:

In our project, we use a separate module that contains configuration files for 
the whole application.
The configuration files are stored in a version control system and they are 
modified during the build 
process using profiles and settings.xml.

Each member of the team can build a specific variant of the web application,
that contains the desired configuration (development, test, production, etc).

The problem is, that the "configuration module" should not be deployed to the 
shared
repository, because it would then break configurations of other team members.

We need some way to include the "configuration module" to the final application 
(war),
but at the same time the "configuration artifact" must be disallowed to "deploy"
(it must remain local).



Does Maven support the described use-case?
Is there any "official" method for solving such scenario?

Thank you in advance
Michal Palicka


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: hibernate3 plugin

2006-02-13 Thread Michal Palička

Hello,

the Hibernate3 plugin can be found at the "mojo-sandbox".

http://mojo.codehaus.org/faq.html#what-is-the-sandbox

I am not sure whether it supports Maven 1.x.
You'll have to build it from the source.
The source can be downloaded from a public SVN repository.

Regards
Michal Palicka


-Original Message-
From: Marco Mistroni [mailto:[EMAIL PROTECTED] 
Sent: Saturday, February 11, 2006 2:17 PM
To: Maven Users List
Subject: hibernate3 plugin

hello all,
 i m currently using Maven 1.1, and i need to download hibernate3-maven-plugin

can anyone tell me where i can downlod it, and which version?

thanks in advance and regards
 marco

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]