Re: Eclipse plugin development with Maven 2
Hi, there is some docs on codehaus about it : http://docs.codehaus.org/display/MAVEN/Maven+and+Eclipse http://docs.codehaus.org/display/MAVENUSER/Eclipse+Plugin http://docs.codehaus.org/display/MAVEN/Barriers+to+Building+Eclipse+with+Maven Cheers, Stéphane Sebastien Pennec a écrit : Hi there, Anybody in the list has used Maven 2 to develop plugins for Eclipse? Is there any best practice related to this kind of project that I should know about before I start? Any advice appreciated :) Sébastien - 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]
Re: [M1][ANN] Maven Cobertura Plugin 1.3 Released
Hi, no, this plugin is for Maven2 ( see the subject ;) Chees, Stéphane [EMAIL PROTECTED] a écrit : Is this for Maven2? If I try and run it I get: [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginMana ger.java:292) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(Defau ltPluginManager.java:198) at org.apache.maven.plugin.DefaultPluginManager.verifyReportPlugin(DefaultP luginManager.java:487) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyReportPlugin(D efaultLifecycleExecutor.java:1292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLi fecycleExecutor.java:657) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLi fecycleExecutor.java:637) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:512) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.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) If I try and install it manually I get: C:\work\pe-sms\trunk\Maven\pe-sms\coremvn plugin:download -Dmaven.repo.remote=http://maven-plugins.sourceforge.net/repository -DgroupId=maven-plugins -DartifactId=maven-cobertura-plugin -Dversion=1.3 [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'plugin'. [INFO] org.apache.maven.plugins: checking for updates from codehaus [INFO] org.codehaus.mojo: checking for updates from codehaus [INFO] artifact org.apache.maven.plugins:maven-plugin-plugin: checking for updates from codehaus [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Required goal not found: plugin:download [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 4 seconds [INFO] Finished at: Mon Jan 29 08:55:44 GMT 2007 [INFO] Final Memory: 1M/3M [INFO] -Original Message- From: Jeff Jensen [mailto:[EMAIL PROTECTED] Sent: 28 January 2007 14:49 To: [EMAIL PROTECTED]; 'Maven Users List' Subject: [M1][ANN] Maven Cobertura Plugin 1.3 Released We are pleased to announce the Maven Cobertura Plug-in 1.3 release! http://maven-plugins.sourceforge.net/maven-cobertura-plugin Cobertura is a free Java tool that calculates the percentage of code accessed by tests. It can be used to identify which parts of your Java program are lacking test coverage. It is based on jcoverage. === Changes in this version include: Fixed bugs: o Allow running against project with no test src. Fixes 1618999. Thanks to Jon Christiansen. o java.lang.NoClassDefFoundError for custom log4j Appender. Fixes 1639236. o Using aspectj maven plugin confuses cobertura. Fixes 1387499. Thanks to psylence. === To automatically install the plugin, type the following on a single line: maven plugin:download
Re: [M1][ANN] Maven Cobertura Plugin 1.3 Released
OOoops O_o My Apologies, lukas is right, this is a Maven 1 plugin. Stéphane. Lukas Theussl a écrit : no, this plugin is for Maven 1 (see the subject ;) ) :) -Lukas Stéphane Bouchet wrote: Hi, no, this plugin is for Maven2 ( see the subject ;) Chees, Stéphane [EMAIL PROTECTED] a écrit : Is this for Maven2? If I try and run it I get: [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginMana ger.java:292) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(Defau ltPluginManager.java:198) at org.apache.maven.plugin.DefaultPluginManager.verifyReportPlugin(DefaultP luginManager.java:487) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyReportPlugin(D efaultLifecycleExecutor.java:1292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLi fecycleExecutor.java:657) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLi fecycleExecutor.java:637) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:512) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.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) If I try and install it manually I get: C:\work\pe-sms\trunk\Maven\pe-sms\coremvn plugin:download -Dmaven.repo.remote=http://maven-plugins.sourceforge.net/repository -DgroupId=maven-plugins -DartifactId=maven-cobertura-plugin -Dversion=1.3 [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'plugin'. [INFO] org.apache.maven.plugins: checking for updates from codehaus [INFO] org.codehaus.mojo: checking for updates from codehaus [INFO] artifact org.apache.maven.plugins:maven-plugin-plugin: checking for updates from codehaus [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Required goal not found: plugin:download [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 4 seconds [INFO] Finished at: Mon Jan 29 08:55:44 GMT 2007 [INFO] Final Memory: 1M/3M [INFO] -Original Message- From: Jeff Jensen [mailto:[EMAIL PROTECTED] Sent: 28 January 2007 14:49 To: [EMAIL PROTECTED]; 'Maven Users List' Subject: [M1][ANN] Maven Cobertura Plugin 1.3 Released We are pleased to announce the Maven Cobertura Plug-in 1.3 release! http://maven-plugins.sourceforge.net/maven-cobertura-plugin Cobertura is a free Java tool that calculates the percentage of code accessed by tests. It can be used to identify which parts of your Java program are lacking test coverage. It is based on jcoverage. === Changes in this version include: Fixed bugs: o Allow running against project with no test src. Fixes 1618999. Thanks to Jon Christiansen. o java.lang.NoClassDefFoundError for custom log4j Appender. Fixes 1639236. o Using aspectj maven plugin confuses
Re: HOW TO - Use maven-eclipse-plugin to build a RCP Target Platform and an internal repository from an Eclipse installation
Hi, see my comments inline : Steinar Bang a écrit : (Note: I'm aware that to actually create a target platform separate from the eclipse installation, the plugins have to be copied to a location separate from the eclipse installation, and that installation be set as the PDE target platform. I do this already to be able to use other OSGi bundles from inside an eclipse RCP app. The parts I'm asking about, are the steps that deploy into the maven repo) Barrie Treloar [EMAIL PROTECTED]: To be specific, if my eclipse install dir is /usr/local/eclipse-32/, does the eclipse:make-artifacts goal deploy everything under /usr/local/eclipse-32/plugins/? Or does it copy just the eclipse runtime? (if so, how does it know what to take?) If it copies just the runtime, I understand why the RCP must be deployed in addition. If it copies everything, then deploying the RCP may not be neccessary, if RCP has been installed in the eclipse installation first...? The make-artifacts goal only copies the plugins. It does nothing with the runtime. What I meant to ask was: Does make-artifacts only deploy those plugins from /usr/local/eclipse-32/plugins that are known parts of the eclipse runtime to the repository? Or does it deploy _all_ plugins it finds at that location? (when you install an eclipse plugin, if you don't do anything special, it's just installed over the installation) the make-artifacts goal deploy everything it found under the feature and plugin directory to the repository, with any third party plugins founded. (see doc : http://maven.apache.org/plugins/maven-eclipse-plugin/make-artifacts-mojo.html) Cheers, Stéphane To build your RCP application you need an Eclipse Target Platform, which is best created separately from your Eclipse Install. This allows you to be using Eclipse 3.2 for the build process but Eclipse RCP 3.1 for the application you are building. Hm... I see, I think. Doing both these steps will create two sets of the runtime in the eclipse repo. One for 3.2 taken from the installation, and one for 3.1 taken from the zip file? So if you want 3.2 for both the installation, and for the application, installing the RCP isn't neccessary? Or am I misunderstanding? - 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]
Re: [m2] eclipse:make-artifacts does not exists?!
Hi, you need the 2-3-SNAPSHOT version of the eclipse plugin . http://www.nabble.com/forum/ViewPost.jtp?post=7317502framed=yskin=177 Cheers, Stéphane Adrian Herscu a écrit : Hi all, I am trying to use Eclipse jars in my M2 project. The mvn eclipse:make-artifacts (http://maven.apache.org/plugins/maven-eclipse-plugin/make-artifacts-mojo.html) returns: [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'eclipse'. [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Required goal not found: eclipse:make-artifacts [INFO] Any suggestion? Adrian. - 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]
Re: Unsupported WTP version: 1.5
You may use the 2.3-SNAPSHOT version of the eclipse plugin to have it to
work.
Cheers,
Stéphane.
Minto van der Sluis a écrit :
Hi all,
I try to use the maven eclipse plugin for WTP 1.5. But it tells me it does
not know WTP 1.5. What am I doing wrong?
My pom looks like this:
properties
ejbversion2.0/ejbversion
java13_home/opt/java/ibm-jdk-131//java13_home
/properties
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.0/version
configuration
forktrue/fork
compilerVersion1.3/compilerVersion
executable${java13_home}/bin/javac/executable
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.2/version
configuration
wtpversion1.5/wtpversion
/configuration
/plugin
/plugins
/build
Here is the message I get:
[INFO] Preparing eclipse:eclipse
[INFO] No goals needed for project - skipping
[INFO] [eclipse:eclipse]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Unsupported WTP version: 1.5. This plugin currently supports only the
following versions: 1.0 R7 none.
[INFO]
[INFO] For more information, run Maven with the -e switch
Any clues? Am I missing dependancies? Even removing the eclipse version from
the pom does not help.
Kind regards,
Minto van der Sluis
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unsupported WTP version: 1.5
the eclipse plugin snapshot is hosted on apache. add these to your
settings :
repositories
repository
idapache.snapshots/id
urlhttp://people.apache.org/maven-snapshot-repository//url
/repository
/repositories
pluginRepositories
pluginRepository
idapache.snapshots/id
urlhttp://people.apache.org/maven-snapshot-repository//url
/pluginRepository
/pluginRepositories
Cheers,
Stéphane.
Minto van der Sluis a écrit :
Hi,
Thanks for the answers. I not have the following in my pom:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.3-SNAPSHOT/version
configuration
wtpversion1.5/wtpversion
/configuration
/plugin
But it seems like maven is not able to find it in any of the following
repositories:
repositories
repository
snapshots
enabledtrue/enabled
updatePolicydaily/updatePolicy
/snapshots
idmaven2-snapshot-apache/id
namemaven2-snapshot-apache/name
urlhttp://people.apache.org/maven-snapshot-repository/url
/repository
repository
snapshots
enabledtrue/enabled
updatePolicydaily/updatePolicy
/snapshots
idmaven2-snapshot-codehaus/id
namemaven2-snapshot-codehaus/name
urlhttp://snapshots.maven.codehaus.org/maven2/url
/repository
/repositories
I even tried building it from trunk, but then I get complaints about other
plugins (maven-plugin-test-harness) it is not able to find.
Can anyone tell me where I can find a precompiled snapshot? Or maybe I have
done something wrong.
Regards,
Minto
Stéphane Bouchet-3 wrote:
You may use the 2.3-SNAPSHOT version of the eclipse plugin to have it to
work.
Cheers,
Stéphane.
Minto van der Sluis a écrit :
Hi all,
I try to use the maven eclipse plugin for WTP 1.5. But it tells me it
does
not know WTP 1.5. What am I doing wrong?
My pom looks like this:
properties
ejbversion2.0/ejbversion
java13_home/opt/java/ibm-jdk-131//java13_home
/properties
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.0/version
configuration
forktrue/fork
compilerVersion1.3/compilerVersion
executable${java13_home}/bin/javac/executable
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.2/version
configuration
wtpversion1.5/wtpversion
/configuration
/plugin
/plugins
/build
Here is the message I get:
[INFO] Preparing eclipse:eclipse
[INFO] No goals needed for project - skipping
[INFO] [eclipse:eclipse]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Unsupported WTP version: 1.5. This plugin currently supports only
the
following versions: 1.0 R7 none.
[INFO]
[INFO] For more information, run Maven with the -e switch
Any clues? Am I missing dependancies? Even removing the eclipse version
from
the pom does not help.
Kind regards,
Minto van der Sluis
-
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]
Re: [m1/2] org.eclipse.ui and org.eclipse.core.runtime on iBiblio?
Hi, There is a 2.3-SNAPSHOT that provide a new goal : eclipse:make-artifacts . that goal scan your eclipse plugin directory and copy all the artifact in your local repo. Cheers, Stéphane Jörg Schaible a écrit : Benoit Xhenseval wrote on Wednesday, October 18, 2006 12:46 AM: Hi Anyone seen the jar from Eclipse: org.eclipse.ui and org.eclipse.core.runtime In any maven central repository? http://www.mavenregistry.com/search/group/6193 Do you have to install them manually in your own? Is it some kind of license limitation? They might not be up-to-date ... your turn :) - 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]
Re: Confused about Maven 2 Eclipse plugin
hi, There is a bug with Maven Embedder, see : http://jira.codehaus.org/browse/MNGECLIPSE-71 ther is also a mailing list for this plugin that could help you : http://m2eclipse.codehaus.org/mail-lists.html Cheers, Stéphane Los Morales a écrit : Hi, Thanks for the tip. Now I tried the lifecycle clean, compile and package on my base project, but it doesn't recurse down to my sub projects. For example, I have this setup: --Main Project --- Project 1 --- pom.xml --- Project 2 --- pom.xml --- pom.xml Now when I run the Maven 2 plugin phase clean from the base directory-- Main Project, I get this: Deleting directory c:\workspaces\test\Main Project\target Deleting directory c:\workspaces\test\Main Project\target\classes Deleting directory c:\workspaces\test\Main Project\target\test-classes ... However, it does not clean up Project 1 and 2's target directories. I know my pom.xml's are good since the command line (mvn clean) works like a charm. Am I'm missing a step or 2? Thanks in advance. -los From: Manuel Ledesma [EMAIL PROTECTED] Reply-To: Maven Users List users@maven.apache.org To: Maven Users List users@maven.apache.org Subject: Re: Confused about Maven 2 Eclipse plugin Date: Thu, 12 Oct 2006 23:12:28 -0400 Look at external tools. You can launch lifecycle and goals from there. Los Morales wrote: I'm currently using Eclipse 3.2 and Maven 2 plugin version 0.0.9. When I enable Maven 2 and right-click on my main project, there are only 2 options for me in the popup menu: 1) Update Source Folders and 2) Add Dependency... Where are the lifecycle phases or custom goals? Seems like the NetBeans plugin works fine but I'm totally frustrated for the one with Eclipse. Everytime I need to clean/compile/package my Eclipse project, I got to do it via the command line. Am I missing something here? Thanks in advance. -los _ Express yourself - download free Windows Live Messenger themes! http://clk.atdmt.com/MSN/go/msnnkwme002001msn/direct/01/?href=http://imagine-msn.com/themes/vibe/default.aspx?locale=en-ussource=hmtagline - 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] _ Add fun gadgets and colorful themes to express yourself on Windows Live Spaces http://clk.atdmt.com/MSN/go/msnnkwsp007001msn/direct/01/?href=http://www.get.live.com/spaces/features - 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]
Re: JPOX and Maven2
As I can see (1) , the last maven plugin is using jpox 1.1.1 . Stéphane. (1) *http://mojo.codehaus.org/jpox-maven-plugin/dependencies.html * Aleksei Valikov a écrit : Hi folks, Does anyone use JPOX with Maven2? Which enhancer plugin do you use? Bye. /lexi - 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]
Re: Have Maven Eclipse Plugin specify Eclipse file encoding
Ralph Pöllath a écrit : Hi, My work environment requires that all source files are encoded as UFT-8. Since we're using Eclipse, this means we have to change the file encoding to UTF-8 whenever we create a new workspace, which is inconvenient and error-prone. Since all of our Eclipse config is generated by the Maven Eclipse Plugin already, having it set the file encoding on a per-project basis would be a great solution (looks like you just have to add encoding/project=UTF-8 to .settings/org.eclipse.core.resources.prefs). Should I post a feature request to JIRA? yes, fill a new issue here : http://jira.codehaus.org/browse/MECLIPSE Stéphane. Thanks, -Ralph. - 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]
Re: executing after being built with Maven2
Take a look to the last maven-jar-plugin : http://maven.apache.org/plugins/maven-jar-plugin/examples/executable-jar.html Cheers, Stéphane berndq a écrit : Stephen More wrote: I guess you are looking for the assembly plugin Here is the docu: http://maven.apache.org/plugins/maven-assembly-plugin/howto.html But I do not know how up to date this is. Recently on the dev list a staging version of new docu was presented for review (this was helpfull for me) A staging site is currently available at http://people.apache.org/~epunzalan/maven-assembly-plugin. Thank you for taking some time to review it. Bernd I am fairly new to maven2. Once the dependecies are listed, I see how maven automagically figures out what are the needed jars and downloads them. I can compile, test and jar my maven2 project just fine. My problem is that when I try to run from the SNAPSHOT, I can no longer find all the jars that were used during the compilation process. After a package I would like to: java -jar SNAPSHOT.jar and have it work. - Should I include all the needed jars in my SNAPSHOT.jar ? If so how. or - Can maven echo out the classpath used during compile and test so I can set my classpath to the same so it will execute ? -Thanks Steve More - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: NullPointerException in maven-eclipse-plugin while executing mak e-artifacts goal
Sharma, Jaikumar a écrit : Thanks Stephane, I installed eclipse in a fresh way (only SDK -- no other plugins in IDE), and run make-artifacts and it installed all the required artifacts in local repository. I am still not sure why JBoss IDE artifact caused NPE. Thanks again for your help! You're Welcome :) The best thing to do is to fill a new JIRA issue with your stacktrace in MECLIPSE ( http://jira.codehaus.org/browse/MECLIPSE ) and we will try to track this problem with this particular plugin. Stéphane. Regards, snip - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: NullPointerException in maven-eclipse-plugin while executing mak e-artifacts goal
Hi,
this new functionnality is still under dev.
It seems you have installed a plugin (org.jbpm.core ) taht is not
delivered with the basic eclipse install. the maven plugin tries to
create for each eclipse plugin an artifact and install it in our repo.
So there is an error with that particular eclipse plugin
Do you need this plugin into your App ? if not, try to remove it, then
try again .
Stéphane
Sharma, Jaikumar a écrit :
Dear Maven users,
Did someone tried maven-eclipse-plugin : version 2.3-SNAPSHOT to build
eclipse plugins ? When I run mvn clean make-artifacts it is coming out
with NullPointeException as appended at the end of the mail.
Plugin configuration in my pom.xml is :
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.3-SNAPSHOT/version
configuration
eclipseDir${ECLIPSE_HOME}/eclipseDir
buildOutputDirectory${basedir}/target/buildOutputDirectory
!-- downloadSourcestrue/downloadSources --
eclipseProjectDir${basedir}/eclipseProjectDir
manifestplugin.xml/manifest
pdetrue/pde
executions
execution
goals
goalmake-artifacts/goal
/goals
/execution
/executions
/configuration
/plugin
Does some has any idea or pointers on this or I am doing something wrong ?
Thanks for your help!
[INFO] Processing file
C:\Lang\eclipse\plugins\org.eclipse.xsd.edit_2.1.0.jar
[WARNING] Missing version for artifact org.eclipse.core.runtime, skipping
[WARNING] Missing version for artifact org.eclipse.emf.edit, skipping
[WARNING] Missing version for artifact org.eclipse.xsd, skipping
[INFO] Installing C:\DOCUME~1\JKS\LOCALS~1\Temp\pom36712.xml to
C:\Lang\maven-2.0.4\Repository\org\eclipse\org.eclipse.xsd.edit\2.1.0\org.ec
lipse.xsd.edit-2.1.0.pom
[INFO] Installing C:\Lang\eclipse\plugins\org.eclipse.xsd.edit_2.1.0.jar to
C:\Lang\maven-2.0.4\Repository\org\eclipse\org.eclipse.xsd.edit\2.1.0\org.ec
lipse.xsd.edit-2.1.0.jar
[INFO] Processing file C:\Lang\eclipse\plugins\org.eclipse.xsd_2.1.1.jar
[WARNING] Missing version for artifact org.eclipse.core.runtime, skipping
[WARNING] Missing version for artifact org.eclipse.emf.ecore, skipping
[INFO] Installing C:\DOCUME~1\JKS\LOCALS~1\Temp\pom36713.xml to
C:\Lang\maven-2.0.4\Repository\org\eclipse\org.eclipse.xsd\2.1.1\org.eclipse
.xsd-2.1.1.pom
[INFO] Installing C:\Lang\eclipse\plugins\org.eclipse.xsd_2.1.1.jar to
C:\Lang\maven-2.0.4\Repository\org\eclipse\org.eclipse.xsd\2.1.1\org.eclipse
.xsd-2.1.1.jar
[INFO] Processing file C:\Lang\eclipse\plugins\org.jbpm.core_3.0.9.jar
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.plugin.eclipse.MakeArtifactsMojo.execute(MakeArtifactsMojo.
java:166)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManage
r.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife
cycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(De
faultLifecycleExecutor.java:488)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifec
ycleExecutor.java:458)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail
ures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Defa
ultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle
Executor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
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)
[INFO]
[INFO] Total time: 13 seconds
[INFO]
Re: NullPointerException in maven-eclipse-plugin while executing mak e-artifacts goal
Sharma, Jaikumar a écrit :
Thanks Stephane, Please see below.
-Original Message-
From: Stéphane Bouchet [mailto:[EMAIL PROTECTED]
Sent: Monday, August 28, 2006 6:33 PM
To: Maven Users List
Subject: Re: NullPointerException in maven-eclipse-plugin while executing
mak e-artifacts goal
Hi,
this new functionnality is still under dev.
It seems you have installed a plugin (org.jbpm.core ) taht is not
delivered with the basic eclipse install. the maven plugin tries to
create for each eclipse plugin an artifact and install it in our repo.
So there is an error with that particular eclipse plugin
Do you need this plugin into your App ? if not, try to remove it, then
try again .
[Sharma, Jaikumar]
I did not install (org.jbpm.core) into my repository and it does not exist
in local repository. When I run the mvn make-artifacts, then a lot of
plugins from local eclipse installation gets processed and installed into
local repository based on plugin manifest.
I am not sure, what is the reason, it gets stuck on this plugin, while
processing and gives NullPointerException.
That is what i am saying.
You have installed JBOSS IDE and not just Eclipse IDE, and tha
org.jbpm.core plugin for eclipse gives you the NPE.
i don't know either the reason why it gave you this.
the solution i gave you is that you could install a fresh Eclipse in
another directory, run mvn make-artifacts into, and see if you could
use the installed artifact with your app and maven..
The make-artifacts goals need to be call just the first time, after
that, you will have all the necessary artifact in your repo.
Stéphane
Jaikumar
Stéphane
Sharma, Jaikumar a écrit :
Dear Maven users,
Did someone tried maven-eclipse-plugin : version 2.3-SNAPSHOT to build
eclipse plugins ? When I run mvn clean make-artifacts it is coming out
with NullPointeException as appended at the end of the mail.
Plugin configuration in my pom.xml is :
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.3-SNAPSHOT/version
configuration
eclipseDir${ECLIPSE_HOME}/eclipseDir
buildOutputDirectory${basedir}/target/buildOutputDirectory
!-- downloadSourcestrue/downloadSources --
eclipseProjectDir${basedir}/eclipseProjectDir
manifestplugin.xml/manifest
pdetrue/pde
executions
execution
goals
goalmake-artifacts/goal
/goals
/execution
/executions
/configuration
/plugin
Does some has any idea or pointers on this or I am doing something wrong ?
Thanks for your help!
[INFO] Processing file
C:\Lang\eclipse\plugins\org.eclipse.xsd.edit_2.1.0.jar
[WARNING] Missing version for artifact org.eclipse.core.runtime, skipping
[WARNING] Missing version for artifact org.eclipse.emf.edit, skipping
[WARNING] Missing version for artifact org.eclipse.xsd, skipping
[INFO] Installing C:\DOCUME~1\JKS\LOCALS~1\Temp\pom36712.xml to
C:\Lang\maven-2.0.4\Repository\org\eclipse\org.eclipse.xsd.edit\2.1.0\org.ec
lipse.xsd.edit-2.1.0.pom
[INFO] Installing C:\Lang\eclipse\plugins\org.eclipse.xsd.edit_2.1.0.jar
to
C:\Lang\maven-2.0.4\Repository\org\eclipse\org.eclipse.xsd.edit\2.1.0\org.ec
lipse.xsd.edit-2.1.0.jar
[INFO] Processing file C:\Lang\eclipse\plugins\org.eclipse.xsd_2.1.1.jar
[WARNING] Missing version for artifact org.eclipse.core.runtime, skipping
[WARNING] Missing version for artifact org.eclipse.emf.ecore, skipping
[INFO] Installing C:\DOCUME~1\JKS\LOCALS~1\Temp\pom36713.xml to
C:\Lang\maven-2.0.4\Repository\org\eclipse\org.eclipse.xsd\2.1.1\org.eclipse
.xsd-2.1.1.pom
[INFO] Installing C:\Lang\eclipse\plugins\org.eclipse.xsd_2.1.1.jar to
C:\Lang\maven-2.0.4\Repository\org\eclipse\org.eclipse.xsd\2.1.1\org.eclipse
.xsd-2.1.1.jar
[INFO] Processing file C:\Lang\eclipse\plugins\org.jbpm.core_3.0.9.jar
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.plugin.eclipse.MakeArtifactsMojo.execute(MakeArtifactsMojo.
java:166)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManage
r.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife
cycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(De
Re: Multi-project site generation
Arnaud Bailly a écrit : Hi, I am trying to create site and deploy it for a multi-project package. In the coo (parent) pom, I define various reports to generate. The root also contains src/site/... tree with documentation. The site.xml does not contains reports sections. The pom is: reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdsurefire-report-maven-plugin/artifactId /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdcobertura-maven-plugin/artifactId /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdjxr-maven-plugin/artifactId /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdchanges-maven-plugin/artifactId /plugin /plugins /reporting The modules each contain src/site/site.xml descriptor and POMs inherit from parent without any additional reports. Here is a sample site descriptor: ?xml version=1.0 encoding=ISO-8859-1? project name=JAutomata Core skin groupIdorg.apache.maven.skins/groupId artifactIdmaven-stylus-skin/artifactId version1.0/version /skin poweredBy logo name=Hosted on SourceForge.net href=http://sourceforge.net; img=http://sflogo.sourceforge.net/sflogo.php?group_id=170468amp;type=1/ logo name=Build with Maven 2 href=http://maven.apache.org; img=images/logos/maven-feather.png/ /poweredBy body links item name=Maven 2 href=http://maven.apache.org/maven2// /links menu name=JAuto ref=parent / menu name=Standard reports ref=reports / /body /project What happens is that 'mvn site' fails in parent site generation with: [INFO] Generate Project Team report. [INFO] Generate Maven Surefire Report report. [INFO] Generate Cobertura Test Coverage report. [INFO] Cobertura 1.7 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file [ERROR] Error: data file /home/nono/projets/jautomata/jautomata-2.0/cobertura.ser does not exist [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error during page generation Embedded error: Error rendering Maven report: Error in Cobertura Report generation: Unable to generate Cobertura Report for project. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 25 seconds [INFO] Finished at: Fri Aug 25 10:19:56 CEST 2006 [INFO] Final Memory: 21M/38M This is normal as the parent does not contains any code. What puzzles me is that this generation process used to work when child did not have descriptors !? Help would be of course appreciated. Hi, there is an issue with cobertura-report. See : http://jira.codehaus.org/browse/MCOBERTURA-38 It seems it is fixed in trunk, so try to build it from it. Cheers, Stéphane - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is it possible to build Eclipse 3.1 plugins using M2 ?
It's on apache SNAPSHOT repo . http://people.apache.org/maven-snapshot-repository/org/apache/maven/plugins/maven-eclipse-plugin/2.3-SNAPSHOT/ add the following in your $HOME/.m2/settings.xml : pluginRepositories .. pluginRepository idapache-snapshot/id nameApache Snapshots repository/name url http://people.apache.org/maven-snapshot-repository /url snapshots enabledtrue/enabled /snapshots releases enabledfalse/enabled /releases /pluginRepository /pluginRepositories Stéphane Sharma, Jaikumar a écrit : Thanks Stephane. I am not able to locate this plugin version in M2 repo. Regards -Original Message- From: Stéphane Bouchet [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 23, 2006 1:50 PM To: Maven Users List Subject: Re: Is it possible to build Eclipse 3.1 plugins using M2 ? There is also a thread about building eclipse RCP apps but i believe this is for eclipse 3.2 : http://www.nabble.com/Eclipse-bundle-howto-tf2065506.html#a5690799 Stéphane. Valerio Schiavoni a écrit : after a quick search, i found it my self. adding these lines to your pom: plugin artifactIdmaven-eclipse-plugin/artifactId version2.3-SNAPSHOT/version configuration pdetrue/pde /configuration /plugin you should be able at least to compile an eclipse plugin. On 8/23/06, Valerio Schiavoni [EMAIL PROTECTED] wrote: improvements in the maven-eclipse-plugin - 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]
Re: Is it possible to build Eclipse 3.1 plugins using M2 ?
There is also a thread about building eclipse RCP apps but i believe this is for eclipse 3.2 : http://www.nabble.com/Eclipse-bundle-howto-tf2065506.html#a5690799 Stéphane. Valerio Schiavoni a écrit : after a quick search, i found it my self. adding these lines to your pom: plugin artifactIdmaven-eclipse-plugin/artifactId version2.3-SNAPSHOT/version configuration pdetrue/pde /configuration /plugin you should be able at least to compile an eclipse plugin. On 8/23/06, Valerio Schiavoni [EMAIL PROTECTED] wrote: improvements in the maven-eclipse-plugin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse bundle howto
Hi, i take a look to your How-To. it looks very promising for building Eclipse RCP apps. But did you take a look to the last snapshot of eclipse-plugin ?? there is some neww feature very nice being developped by fabrizio : http://jira.codehaus.org/browse/MECLIPSE-92 Cheers, Stéphane. Martin Vysny a écrit : Hi all, I finally managed to create working maven2 build that builds eclipse plugins (bundles). A simple howto is located at http://vyzivus.host.sk/maven2-build-plugin-howto.html, the build system itself is demonstrated in EuroMath2 eclipse plugin (just download src distribution at http://sourceforge.net/project/showfiles.php?group_id=117196package_id=127532). Hope that helps, sincerely, Martin - 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]
Re: Eclipse Plugins
Barrie Treloar a écrit : On 7/18/06, Scott Goldstein [EMAIL PROTECTED] wrote: 1. How do you write a pom to build and release an Eclipse RCP application, including using an Eclipse Product Configuration to build the final package? 2. How do you then create the Eclipse project from the pom? As Fabrizio has indicated, PDE support is limited at best. Here are some other links I have found. http://m2eclipse.codehaus.org/ The M2 Eclipse Plugin might have some stuff in it of use. I've yet to check. (The website is out of date and the source repository is not where the link indicates) http://cwiki.apache.org/confluence/display/FELIX/OSGi+plugin+for+maven+2 An OSGi plugin which is not quite the same but probably close enough. http://cwiki.apache.org/GMOxDOC11/geronimo-eclipse-plugin-faq.html Some stuff in Geronimo for building their Eclipse plugin. http://vyzivus.host.sk/maven2-build-plugin-howto.html http://euromath2.sourceforge.net/eplugin/team-list.html http://dev.eclipse.org/mhonarc/lists/pde-build-dev/msg00075.html http://mavenosgiplugin.berlios.de/ - A Maven 1.0 plugin http://mevenide.codehaus.org/maven-eclipse-plugin-plugin/ Looks like a Maven 1.0 plugin http://jira.codehaus.org/browse/MECLIPSE-92 And maybe support for basic stuff in the eclipse plugin. I've seen a number of requests for this functionality fly past on the list. If effort is going to be spent addding these features then it would be good to pool the effort. The maven eclipse plugin feels like the correct spot. Hi, The current maven-eclipse-plugin is definitively the more accurate plugin to begin with. The current SNAPSHOT could generate the MANIFEST.MF file needed by any eclipse plugin, but it would not generate plugin.xml. there is some work in progress by somebody here in the list to make an archetype for eclipse plugin. So for compiling eclipse plugin, the work is almost done ( for me, it is working ) . What is missing today is : - packaging eclipse plugin ( could be done with assembly ) - support for RCP packaging ( currently you cannot build eclipse RCP app like eclipse does with its own process ) - a plugin to test eclipse plugin the two last thing are done with eclipse's own stuff ( ant + headless eclipse). Stéphane. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse Plugins
1. You can always develop with IDE other than Eclipse, notepad for example ! But for plugins, Eclipse provide some very useful editors and tools. With maven-eclipse-plugin, you can mix maven's concept of dependency managment and eclipse tools without effort. You could create an eclipse plugin without eclipse using maven assembly. 2. the main interrest to have it as maven project is continious integration and nightly builds. the eclipse'w way is complex and you can just build plugins, and tests them. you cannot generate site like maven does. Stéphane. Milos Kleint a écrit : I don't completely get the use the maven-eclipse-plugin to build eclipse plugins in maven. that raises a few questions. 1. you cannot develop the plugin in any other IDE, only in eclipse itself? 2. why even bother having it as maven project? do I miss something obvious? Milos On 8/4/06, Stéphane Bouchet [EMAIL PROTECTED] wrote: Barrie Treloar a écrit : On 7/18/06, Scott Goldstein [EMAIL PROTECTED] wrote: 1. How do you write a pom to build and release an Eclipse RCP application, including using an Eclipse Product Configuration to build the final package? 2. How do you then create the Eclipse project from the pom? As Fabrizio has indicated, PDE support is limited at best. Here are some other links I have found. http://m2eclipse.codehaus.org/ The M2 Eclipse Plugin might have some stuff in it of use. I've yet to check. (The website is out of date and the source repository is not where the link indicates) http://cwiki.apache.org/confluence/display/FELIX/OSGi+plugin+for+maven+2 An OSGi plugin which is not quite the same but probably close enough. http://cwiki.apache.org/GMOxDOC11/geronimo-eclipse-plugin-faq.html Some stuff in Geronimo for building their Eclipse plugin. http://vyzivus.host.sk/maven2-build-plugin-howto.html http://euromath2.sourceforge.net/eplugin/team-list.html http://dev.eclipse.org/mhonarc/lists/pde-build-dev/msg00075.html http://mavenosgiplugin.berlios.de/ - A Maven 1.0 plugin http://mevenide.codehaus.org/maven-eclipse-plugin-plugin/ Looks like a Maven 1.0 plugin http://jira.codehaus.org/browse/MECLIPSE-92 And maybe support for basic stuff in the eclipse plugin. I've seen a number of requests for this functionality fly past on the list. If effort is going to be spent addding these features then it would be good to pool the effort. The maven eclipse plugin feels like the correct spot. Hi, The current maven-eclipse-plugin is definitively the more accurate plugin to begin with. The current SNAPSHOT could generate the MANIFEST.MF file needed by any eclipse plugin, but it would not generate plugin.xml. there is some work in progress by somebody here in the list to make an archetype for eclipse plugin. So for compiling eclipse plugin, the work is almost done ( for me, it is working ) . What is missing today is : - packaging eclipse plugin ( could be done with assembly ) - support for RCP packaging ( currently you cannot build eclipse RCP app like eclipse does with its own process ) - a plugin to test eclipse plugin the two last thing are done with eclipse's own stuff ( ant + headless eclipse). Stéphane. - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: eclipse plugin archetype?
Hi, there is some improvement to the maven-eclipse-plugin to adress this. If you set these lines in your POM, you could be able to compile and debug an eclipse plugin : plugin artifactIdmaven-eclipse-plugin/artifactId version2.3-SNAPSHOT/version configuration pdetrue/pde /configuration /plugin But there is no archetype to create an eclipse plugin skeleton for the moment. Cheers, Stéphane Valerio Schiavoni a écrit : i did. this is not what i was referring to. the use case for me is that i want to develop an ecplise plugin, and i wonder if it's possible to develop it using maven as build tool. what you suggested is usefull to use eclipse as the development environment for my project: whic is good for sure, but not what i was referring to :) thanks anyway, valerio On 7/26/06, Thierry Barnier [EMAIL PROTECTED] wrote: have you tried mvn eclipse:eclipse ? Thierry 2006/7/26, Valerio Schiavoni [EMAIL PROTECTED]: hello everyone, i was wondering if there's an eclipse plugin archetype... any idea ? thanks, valerio -- http://valerioschiavoni.blogspot.com http://jroller.com/page/vschiavoni - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: eclipse plugin archetype?
Valerio Schiavoni a écrit : Hello Stéphane, maybe i can contribute some code with the proposed archetype. what do you think? Sure ! but i am not familiar with archetype creations :( I'm quite new to eclipse plugin development, so i don't know either if there's a common/best practice way to organize a project structure. Eclipse plugin is like a java project, but there is 3 files that are mandatory : plugin.xml, build.properties and META-INF/MANIFEST.MF . the rest of the project can follow the maven directory structure ( src/main/java , src/test/java).. Stéphane. On 7/26/06, Stéphane Bouchet [EMAIL PROTECTED] wrote: But there is no archetype to create an eclipse plugin skeleton for the moment. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: eclipse plugin archetype?
Valerio Schiavoni a écrit : Hello Stèphane, On 7/26/06, Stéphane Bouchet [EMAIL PROTECTED] wrote: Eclipse plugin is like a java project, but there is 3 files that are mandatory : plugin.xml, build.properties and META-INF/MANIFEST.MF . how much different are those files from plugin to plugin ? i know that when you start the development of an eclipse plugin, the wizard proposes you a certain number of prepackaged templates. maybe there' can be a 1:1 mapping between those templates and the files you suggested. These files are always differents but i think to map one of the proposed PDE project is a good idea If you try to create a new project with these templates, you can see the contents of the files. the rest of the project can follow the maven directory structure ( src/main/java , src/test/java).. one more thing maybe is needed: what kind of dependencies an ecplise plugin would typically depend on ? i guess some of the eclipse apis are needed.. the actual maven-eclipse-plugin handle the required dependencies very well, so you need to use it ( i think) . Stéphane. thanks, valerio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2]assembly plugin: finalName issue
hi, if src is the id specified in your assembly XML file, try add appendAssemblyIdfalse/appendAssemblyId in your assembly configuration's section in your pom.xml. Stéphane. Sebastien Pennec a écrit : Hello, I've set, in the configuration of the assembly plugin, the finalName property. Unfortunately, the plugin keeps appending in the file name -src between the finalName value and the extension (.zip, .tar.gz) specified in the assembly config file. Does anybody know if it's possible to get rid of this -src thing? Thanks, Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Please review maven-eclipse-plugin
Hi, I don't have any problem to download it from snapshot repo. Testing the maven-eclipse-snapshot right now. Stéphane. Edwin Punzalan a écrit : Its in SVN: http://svn.apache.org/repos/asf/maven/plugins/trunk/pom.xml Brett said he'd deploy it... not sure if its done already or not yet. But it should be in apache snapshots repo when deployed: http://snapshots.maven.codehaus.org/maven2 MacHershell wrote: Where can I get the org.apache.maven.plugins:maven-plugins:2-SNAPSHOT (on which maven-eclipse-plugin depends)? - 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]
Re: maven 1.x plugin for aspectj 1.5
Hi, Testing since yesterday, and working fine for me. But not tested the report. Lukas Theussl a écrit : Stephane or anybody who is interested, I have deployed a new snapshot for the aspectj-4.0 plugin where all the outstanding JIRAs have been fixed [1,2]. It'd be nice if somebody could test and give some feedback, in particular for issues MPASPECTJ-14, 15 and 23. If nothing big comes up then we could release it soon. Thanks, -Lukas [1] http://jira.codehaus.org/browse/MPASPECTJ?report=com.atlassian.jira.plugin.system.project:roadmap-panel [2] http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/plugins/aspectj/ stéphane bouchet wrote: I am testing it right now :) Carlos Sanchez a écrit : It wasn't release because there were not enough testers. If several people agree that 4.0-SNAPSHOT is good and deserve to be released I'm ok with it. On 3/27/06, Arnaud HERITIER [EMAIL PROTECTED] wrote: Finally we'll not release the 3.3 It will be the 4.0 because we upgraded to aspectj 1.5 http://maven.apache.org/maven-1.x/plugins/aspectj/changes-report.html A snapshot is available if you want to test it : maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-aspectj-plugin -Dversion=4.0-SNAPSHOT Arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stéphane Bouchet http://sbouchet.blogspot.com Architecte Logiciel du projet CASTORE http://www.castore.org EMN - CRITE La chantrerie 4, rue Alfred Kastler 44300 NANTES 02.51.85.82.29 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mvn eclipse:eclipse -- requires install first -- bug/oversight?
Hi, i got the same 'problem' with Maven 1.X. I need to install all my local
projects before generating .project and .classpath files.
It is really annoying because the generated files does not refers to the libs in
my repo.
It looks like even if the property eclipse.dependency is set or not, the
eclipse plugin will try to find it in the repo, but after that it will write the
correct entry in the .classpath and .project files.
In my case, I don't commit these files, and tell to my dev squad to do maven
install before use Eclipse...
Cheers,
Gordon Henriksen a écrit :
Hi everyone,
Bit of a problem. There's a workaround, but the workaround is precisely
the problem. Here goes…
mvn eclipse:eclipse requires that I install my local projects before it
will generate the .project and .classpath files for Eclipse. This makes
total sense for external dependencies; the .classpath needs to reference
an .jar file somewhere, so putting them in ~/.m2/repository makes a lot
of sense. Fine and dandy. But for a project like such:
my-root-project/ { packaging: pom }
my-lib/ { packaging: jar }
my-webapp/ { packaging: war, dependencies: { my-lib } }
When I run mvn eclipse:eclipse, the Eclipse .classpath file references
the adjacent my-lib project, not my-lib that resides in the
~/.m2/repository. Therefore, the install doesn't seem as if it should be
necessary for the local projects. Yet the Eclipse plugin insists upon
it. Further, it is damaging to our workflow, since we have to make sure
our code compiles before we can add a dependency to pom.xml and
successfully push those to Eclipse. Besides that, forcing the install of
a project before we can even get our IDE set up seems very backwards; by
definition, the projects in question are under development, so
publishing them to even the per-user repository is premature.
In fact, since I prefer not to have the possibility of out-of-sync
.classpath and .project files, I've prohibited checking these files in.
So our checkout directions look like this:
mkdir my-enterprise
cd my-enterprise
svn co svn+ssh://my.host/my-enterprise/trunk .
mvn install # --
mvn eclipse:eclipse
Is there a reason this is the case? Or should I file an RFE and look
into making a patch?
Other Eclipse+Maven users:
Should I allow checkin of .classpath and .project, even at the risk of
them falling out of sync with pom.xml?
Does it sound like I'm missing the zen of making these tools cooperate?
— G
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Stéphane Bouchet
http://sbouchet.blogspot.com
Architecte Logiciel du projet CASTORE
http://www.castore.org
EMN - CRITE
La chantrerie
4, rue Alfred Kastler
44300 NANTES
02.51.85.82.29
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven 1.x plugin for aspectj 1.5
in fr.emn.castor.groupes.aspects.GestionGroupesAspect
has not been applied [Xlint:adviceDidNotMatch]
[iajc]
[iajc]
C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\collections\aspects\GestionCollectionsAspect.aj:124
[warning] advice defined in
fr.emn.castor.collections.aspects.GestionCollectionsAspect has not been applied
[Xlint:adviceDidNotMatch]
[iajc]
[iajc]
C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\collections\aspects\GestionCollectionsAspect.aj:116
[warning] advice defined in
fr.emn.castor.collections.aspects.GestionCollectionsAspect has not been applied
[Xlint:adviceDidNotMatch]
[iajc]
[iajc]
C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\collections\aspects\GestionCollectionsAspect.aj:108
[warning] advice defined in
fr.emn.castor.collections.aspects.GestionCollectionsAspect has not been applied
[Xlint:adviceDidNotMatch]
[iajc]
[iajc]
C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\groupes\aspects\GestionGroupesAspect.aj:107
[warning] advice defined in fr.emn.castor.groupes.aspects.GestionGroupesAspect
has not been applied [Xlint:adviceDidNotMatch]
[iajc]
[iajc]
C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\collections\aspects\GestionCollectionsAspect.aj:100
[warning] advice defined in
fr.emn.castor.collections.aspects.GestionCollectionsAspect has not been applied
[Xlint:adviceDidNotMatch]
[iajc]
[iajc]
C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\collections\aspects\GestionCollectionsAspect.aj:92
[warning] advice defined in
fr.emn.castor.collections.aspects.GestionCollectionsAspect has not been applied
[Xlint:adviceDidNotMatch]
[iajc]
[iajc]
C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\groupes\aspects\GestionGroupesAspect.aj:86
[warning] advice defined in fr.emn.castor.groupes.aspects.GestionGroupesAspect
has not been applied [Xlint:adviceDidNotMatch]
[iajc]
[iajc]
C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\documents\aspects\ConsultationDocumentAspect.aj:63
[warning] advice defined in
fr.emn.castor.documents.aspects.ConsultationDocumentAspect has not been applied
[Xlint:adviceDidNotMatch]
[iajc]
[iajc]
C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\recherche\aspects\RechercheAspect.aj:65
[warning] advice defined in fr.emn.castor.recherche.aspects.RechercheAspect has
not been applied [Xlint:adviceDidNotMatch]
[iajc]
[iajc]
C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\collections\aspects\ConsultationCollectionAspect.aj:63
[warning] advice defined in
fr.emn.castor.collections.aspects.ConsultationCollectionAspect has not been
applied [Xlint:adviceDidNotMatch]
[iajc]
[iajc]
[iajc] 26 warnings
[iajc]
C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\users\authentification\aspects\ConnexionAspect.aj:60
[warning] advice defined in
fr.emn.castor.users.authentification.aspects.ConnexionAspect has not been
applied [Xlint:adviceDidNotMatch]
[iajc] after(String loginUser, String motPasse) :
seConnecter(loginUser,motPasse) {
[iajc] ^
[iajc] Copying 1 file to
C:\eclipse\workspace\castore-core\target\test-classes
aspectj:
[echo] Compiling to C:\eclipse\workspace\castore-core/target/classes
Lukas Theussl a écrit :
Sorry, I can't give you a release date. All I can say is that I have
recently cleaned up a few trivial issues, but the plugin has been
unmaintained for a while and I have never used it myself, so it is
difficult to judge how much work it still needs.
If you'd like to help, it would be good to have some feedback about the
issues that are still open and scheduled [1], most of them have patches
attached that only need testing.
Cheers,
-Lukas
[1]
http://jira.codehaus.org/browse/MPASPECTJ?report=com.atlassian.jira.plugin.system.project:roadmap-panel
David Fladung wrote:
I see that work is currently being done to upgrade the maven 1.x aspectj
plugin for the latest release of aspectj (4.0-snapshot). Is there any
estimate on when this plugin might be released?
-
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]
--
Stéphane Bouchet
http://sbouchet.blogspot.com
Architecte Logiciel du projet CASTORE
http://www.castore.org
EMN - CRITE
La chantrerie
4, rue Alfred Kastler
44300 NANTES
02.51.85.82.29
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven 1.x plugin for aspectj 1.5
I am testing it right now :) Carlos Sanchez a écrit : It wasn't release because there were not enough testers. If several people agree that 4.0-SNAPSHOT is good and deserve to be released I'm ok with it. On 3/27/06, Arnaud HERITIER [EMAIL PROTECTED] wrote: Finally we'll not release the 3.3 It will be the 4.0 because we upgraded to aspectj 1.5 http://maven.apache.org/maven-1.x/plugins/aspectj/changes-report.html A snapshot is available if you want to test it : maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-aspectj-plugin -Dversion=4.0-SNAPSHOT Arnaud On 3/27/06, stéphane bouchet [EMAIL PROTECTED] wrote: Hi, I am currently using 3.3-SNAPSHOT and everything works fine. it supports java 1.5, and latest aspectj 1.5 too. The only weird thing is when the aspect:test goal is called, i got lots of warnings... see the console output below : java:compile: aspectj:init: aspectj:compile: [iajc] C:\eclipse\workspace\castore-core\src\java\fr\emn\castor\groupes\GroupeProxy.java:150 [warning] can not implement lazyTjp on this joinpoint method-execution(void fr.emn.castor.groupes.GroupeProxy.setUsersToGroupe(java.lang.String, java.util.Iterator)) because around advice is used [Xlint:canNotImplementLazyTjp] [iajc] public void setUsersToGroupe(String id, Iterator userList) [iajc] ^^ [iajc] see also: C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\groupes\aspects\GestionGroupesAspect.aj:148::0 [iajc] [iajc] 1 warning [iajc] Copying 9 files to C:\eclipse\workspace\castore-core\target\classes aspectj:test-compile: [iajc] C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\documents\aspects\GestionDocumentsAspect.aj:320 [warning] advice defined in fr.emn.castor.documents.aspects.GestionDocumentsAspect has not been applied [Xlint:adviceDidNotMatch] [iajc] [iajc] C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\documents\aspects\GestionDocumentsAspect.aj:296 [warning] advice defined in fr.emn.castor.documents.aspects.GestionDocumentsAspect has not been applied [Xlint:adviceDidNotMatch] [iajc] [iajc] C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\documents\aspects\GestionDocumentsAspect.aj:278 [warning] advice defined in fr.emn.castor.documents.aspects.GestionDocumentsAspect has not been applied [Xlint:adviceDidNotMatch] [iajc] [iajc] C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\documents\aspects\GestionDocumentsAspect.aj:248 [warning] advice defined in fr.emn.castor.documents.aspects.GestionDocumentsAspect has not been applied [Xlint:adviceDidNotMatch] [iajc] [iajc] C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\documents\aspects\GestionDocumentsAspect.aj:240 [warning] advice defined in fr.emn.castor.documents.aspects.GestionDocumentsAspect has not been applied [Xlint:adviceDidNotMatch] [iajc] [iajc] C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\documents\aspects\GestionDocumentsAspect.aj:216 [warning] advice defined in fr.emn.castor.documents.aspects.GestionDocumentsAspect has not been applied [Xlint:adviceDidNotMatch] [iajc] [iajc] C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\documents\aspects\GestionDocumentsAspect.aj:191 [warning] advice defined in fr.emn.castor.documents.aspects.GestionDocumentsAspect has not been applied [Xlint:adviceDidNotMatch] [iajc] [iajc] C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\documents\aspects\GestionDocumentsAspect.aj:169 [warning] advice defined in fr.emn.castor.documents.aspects.GestionDocumentsAspect has not been applied [Xlint:adviceDidNotMatch] [iajc] [iajc] C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\collections\aspects\GestionCollectionsAspect.aj:148 [warning] advice defined in fr.emn.castor.collections.aspects.GestionCollectionsAspect has not been applied [Xlint:adviceDidNotMatch] [iajc] [iajc] C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\groupes\aspects\GestionGroupesAspect.aj:148 [warning] advice defined in fr.emn.castor.groupes.aspects.GestionGroupesAspect has not been applied [Xlint:adviceDidNotMatch] [iajc] [iajc] C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\documents\aspects\GestionDocumentsAspect.aj:148 [warning] advice defined in fr.emn.castor.documents.aspects.GestionDocumentsAspect has not been applied [Xlint:adviceDidNotMatch] [iajc] [iajc] C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\collections\aspects\GestionCollectionsAspect.aj:140 [warning] advice defined in fr.emn.castor.collections.aspects.GestionCollectionsAspect has not been applied [Xlint:adviceDidNotMatch] [iajc] [iajc] C:\eclipse\workspace\castore-core\src\aspects\fr\emn\castor\collections
Re: ZoneInfo warning!
i think you are using Mevenide. If so, in Windows/preferences/Maven/locations, change the java_home location to point to a jre and not the jdk_home . raja bangaru a écrit : getting the Following warnings when i run maven goal thru Eclipse IDE ZoneInfo: C:\j2sdk1.4.2_10\lib\zi\ZoneInfoMappings (The system cannot find the path specified) can't open C:\j2sdk1.4.2_10\lib\tzmappings. any help please? -- Stéphane Bouchet http://sbouchet.blogspot.com Architecte Logiciel du projet CASTORE http://www.castore.org EMN - CRITE La chantrerie 4, rue Alfred Kastler 44300 NANTES 02.51.85.82.29 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mevenide and Eclipse 3.1
Hi, What you need is a xerces parser for maven. Create a new directory under %MAVEN_HOME%/lib, called endorsed Copy into it the last version of XercesImpl . Enjoy ! Blaise Gosselin a écrit : Hello, I'm working under Eclipse 3.1.0 and Maven 1.1-beta-2. When I install the mevenide plugin for Eclipse, and that I try to launch a maven goal, I have the following exception : javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:93) at org.apache.maven.jelly.JellyUtils.compileScript(JellyUtils.java:202) at org.apache.maven.jelly.JellyUtils.compileScript(JellyUtils.java:162) at org.apache.maven.plugin.PluginManager.createJellyScriptHousing(PluginManager.java:395) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:589) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263) at org.apache.maven.cli.App.doMain(App.java:511) at org.apache.maven.cli.App.main(App.java:1258) 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:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) I suppose this error is due to the package xerces that can't be found by Maven. Where can I put it so it works ? Thanks in advance. __ _ _ _ bgOnline -- Stéphane Bouchet http://sbouchet.blogspot.com Architecte Logiciel du projet CASTORE http://www.castore.org EMN - CRITE La chantrerie 4, rue Alfred Kastler 44300 NANTES 02.51.85.82.29 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven kodo plugin
Henry S. Isidro a écrit : [EMAIL PROTECTED] wrote: Dear Henry, I have got org.codehaus.mojo:mojo-sandbox:pom:2-SNAPSHOT. However, I can't get com.solarmetric:kodo-jdo:jar:3.0 I don't think it's in the repositories. Have you tried their website -- http://www.solarmetric.com/ Henry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Hi, All the jars from kodo can't be in remote repo, due to licence limitations. Kodo is a commercial implementation of JDO, so you must download a version from their website, and put manually the Jars to your local repo. -- Stéphane Bouchet http://sbouchet.blogspot.com Architecte Logiciel du projet CASTORE http://www.castore.org EMN - CRITE La chantrerie 4, rue Alfred Kastler 44300 NANTES 02.51.85.82.29 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven kodo plugin
[EMAIL PROTECTED] a écrit : Dear Stephane, You mean that kodo-jdo-runtime.jar? thanks. Tel: (020)36315358-328 Fax: (020)36315170 stéphane bouchet Stephane.BouchetTo: Maven Users List users@maven.apache.org @emn.fr cc: Subject: Re: maven kodo plugin 08/02/2006 16:36 Please respond to Maven Users List Henry S. Isidro a écrit : [EMAIL PROTECTED] wrote: Dear Henry, I have got org.codehaus.mojo:mojo-sandbox:pom:2-SNAPSHOT. However, I can't get com.solarmetric:kodo-jdo:jar:3.0 I don't think it's in the repositories. Have you tried their website -- http://www.solarmetric.com/ Henry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Hi, All the jars from kodo can't be in remote repo, due to licence limitations. Kodo is a commercial implementation of JDO, so you must download a version from their website, and put manually the Jars to your local repo. -- Stéphane Bouchet http://sbouchet.blogspot.com Architecte Logiciel du projet CASTORE http://www.castore.org EMN - CRITE La chantrerie 4, rue Alfred Kastler 44300 NANTES 02.51.85.82.29 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ 2006 sees Hactl's 30 years of commitment to Hong Kong and our customers. On this occasion we extend our thanks to all of you for your loyalty and trust. You have contributed to our success. Visit us at our website at www.hactl.com DISCLAIMER :- The information contained in this message, including any attachment, is confidential and may also be privileged. The information is intended only for the person or entity to which it is addressed. Any review, re-transmission, copying, storage, distribution or other use or disclosure of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please contact the sender immediately by return email and delete this message from your system. Thank you. __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] yes, and also kodo.jar that contains the enhancer. there is also some other jars ( jta, jca ) that are not in remote repos, too ! ( due to licence terms, too ) -- Stéphane Bouchet http://sbouchet.blogspot.com Architecte Logiciel du projet CASTORE http://www.castore.org EMN - CRITE La chantrerie 4, rue Alfred Kastler 44300 NANTES 02.51.85.82.29 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven kodo plugin
java.lang.NullPointerException at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:292) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:198) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:163) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1095) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1060) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java: 869) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav a:301) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) 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) [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Wed Feb 08 17:39:29 CST 2006 [INFO] Final Memory: 3M/9M [INFO] thanks. Tel: (020)36315358-328 Fax: (020)36315170 stéphane bouchet Stephane.BouchetTo: Maven Users List users@maven.apache.org @emn.fr cc: Subject: Re: maven kodo plugin 08/02/2006 17:16 Please respond to Maven Users List [EMAIL PROTECTED] a écrit : Dear Stephane, You mean that kodo-jdo-runtime.jar? thanks. Tel: (020)36315358-328 Fax: (020)36315170 stéphane bouchet Stephane.BouchetTo: Maven Users List users@maven.apache.org @emn.fr cc: Subject: Re: maven kodo plugin 08/02/2006 16:36 Please respond to Maven Users List Henry S. Isidro a écrit : [EMAIL PROTECTED] wrote: Dear Henry, I have got org.codehaus.mojo:mojo-sandbox:pom:2-SNAPSHOT. However, I can't get com.solarmetric:kodo-jdo:jar:3.0 I don't think it's in the repositories. Have you tried their website -- http://www.solarmetric.com/ Henry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Hi, All the jars from kodo can't be in remote repo, due to licence limitations. Kodo is a commercial implementation of JDO, so you must download a version from
Re: [M1.1b2] problem with site generation : missing dependency
Hi,
the jar is here : http://www.ibiblio.org/maven/batik/jars/
it seems your ${maven.repo.remote} property is missing or not configured,
because maven is trying to download that jar from the URL you specified in your
project.xml ...
Stéphane
Hervé BOUTEMY a écrit :
Maven site generation has been working well for a long time.
But lately, I deleted my local repository, and now I can't generate my site
any more : a dependency is missing :
$ maven site:site
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.1-beta-2
Attempting to download batik-1.5-fop-0.20-5.jar.
WARNING: Failed to download batik-1.5-fop-0.20-5.jar.
The build cannot continue because of the following unsatisfied dependency:
batik-1.5-fop-0.20-5.jar (try downloading from http://xml.apache.org/batik/)
Total time : 3 seconds
Finished at : Friday, January 20, 2006 8:32:09 AM CET
Is anybody facing the same problem ?
Hervé
-
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]
Re: [M1.1b2] problem with site generation : missing dependency
Arnaud HERITIER a écrit :
Hi,
the jar is here : http://www.ibiblio.org/maven/batik/jars/
The link is broken.
Since we use rewritting rules over the m2 repository to create the m1 one,
these directories listings are outdated.
Right !
I found the jar (working) on a mirror :
http://mirrors.sunsite.dk/maven/batik/jars/
this one is in my build.properties ..
Stéphane
arnaud
it seems your ${maven.repo.remote} property is missing or not
configured, because maven is trying to download that jar from
the URL you specified in your project.xml ...
Stéphane
Hervé BOUTEMY a écrit :
Maven site generation has been working well for a long time.
But lately, I deleted my local repository, and now I can't
generate my
site any more : a dependency is missing :
$ maven site:site
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.1-beta-2
Attempting to download batik-1.5-fop-0.20-5.jar.
WARNING: Failed to download batik-1.5-fop-0.20-5.jar.
The build cannot continue because of the following
unsatisfied dependency:
batik-1.5-fop-0.20-5.jar (try downloading from
http://xml.apache.org/batik/)
Total time : 3 seconds
Finished at : Friday, January 20, 2006 8:32:09 AM CET
Is anybody facing the same problem ?
Hervé
-
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]
-
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]
Re: [M1] Specifying Module build order
It depends on your dependencies you specify in your differents project.xml. In fact, if one project depends on another one, the second will be build before the first one. Personnaly i used maven 1.1beta2 witch is better than maven 1.0. Stéphane Afkham Azeez a écrit : Hi Folks, I have a project with multiple modules and I have got all my project.xml files and maven.xml files in place. But I do not know how to specify the order in which the modules are to be built. How is this achieved? -- Thanks Afkham Azeez - 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]
Re: M2 Kodo Plugin
Hi, I actually manage this plugin , and it is hosted on sourceforge. I am not currently working with M2, so feel free to take the m1 code and modify it to do a M2 plugin ! Stéphane Brian E. Fox a écrit : Anyone have an M2 Kodo plugin? We currently use Ant to do it, but I was thinking about making a plugin. Didn't want to reinvent the wheel... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2 Kodo Plugin
Yes, the m1 plugin is only written in jelly.But I am not a devlopper of Kodo, so i cannot have access to the source code of the ant task... I only use the java code to enhance and create the schema. Look at the solarmatric's docs . Stéphane Brian E. Fox a écrit : I took at quick look the other day. Isn't most of the M1 plugin in Jelly? I was thinking of looking at the ant plugin to get some java code. -Original Message- From: stéphane bouchet [mailto:[EMAIL PROTECTED] Sent: Monday, December 05, 2005 6:15 AM To: Maven Users List Subject: Re: M2 Kodo Plugin Hi, I actually manage this plugin , and it is hosted on sourceforge. I am not currently working with M2, so feel free to take the m1 code and modify it to do a M2 plugin ! Stéphane Brian E. Fox a écrit : Anyone have an M2 Kodo plugin? We currently use Ant to do it, but I was thinking about making a plugin. Didn't want to reinvent the wheel... - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven kodo plugin 4.0.0 EA3 released
The maven-kodo-plugin team is pleased to announce the Kodo Plugin 4.0.0-EA3 release! http://maven-plugins.sourceforge.net/maven-kodo-plugin Maven plugin for Solarmetric's Kodo JDO implementation Changes in this version include: New Features: o This version requires Kodo 4.0.0EA3 jars. Please note that this version is in an early stage. Add a new property maven.kodo.properties.filename if the property file used is not kodo.properties. Thanks to Mark Slater. For a manual installation, you can download the plugin here: https://sourceforge.net/project/showfiles.php?group_id=61626package_id=93912release_id=371112 Have fun! -The maven-kodo-plugin team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JCOVERAGE for MAVEN 2
Sorry for confusion, according to the maven 2 plugin matrix, (http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Matrix) the cobertura plugin is in dev for maven2. Stéphane David Sag a écrit : There is no maven 2 plugin for cobertura according to the developers. dave REBOISSON Eric [EMAIL PROTECTED] wrote on 08-11-2005 09:46:48: I tried to use Cobertura but this error appears , why ? How to resolve it ? : D:\Documents and Settings\reboisse\workspace\DataModelmvn cobertura:report [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'cobertura'. Downloading: http://repo1.maven.org/maven2/cobertura/cobertura/1.4/cobertura-1.4.pom 150b downloaded Downloading: http://repo1.maven.org/maven2/cobertura/cobertura/1.4/cobertura-1.4.jar 80K downloaded [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager. java:292) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPl uginManager.java:198) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManag er.java:163) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLife cycleExecutor.java:1095) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(Defaul tLifecycleExecutor.java:1305) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggrega tionNeeds(DefaultLifecycleExecutor.java:376) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle Executor.java:132) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) 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) [INFO] [INFO] Total time: 8 seconds [INFO] Finished at: Tue Nov 08 09:45:42 CET 2005 [INFO] Final Memory: 1M/3M [INFO] D:\Documents and Settings\reboisse\workspace\DataModel -Message d'origine- De : stéphane bouchet [mailto:[EMAIL PROTECTED] Envoyé : lundi 7 novembre 2005 17:28 À : Maven Users List Objet : Re: JCOVERAGE for MAVEN 2 Jcoverage is a commercial tool, prefer cobertura. the plugin for maven2 is still in dev. http://maven-plugins.sourceforge.net/maven-cobertura-plugin/ STéphane REBOISSON Eric a écrit : Is there a JCOVERAGE plugins for maven 2 ? How to install it if it exists ? Thanks Eric __ Ce message (et toutes ses pièces jointes éventuelles) est confidentiel et établi à l'intention exclusive de ses destinataires. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'IFP décline toute responsabilité au titre de ce message. This message and any attachments (the message) are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. IFP should not be liable for this message. Visitez notre site Web / Visit our web site : http://www.ifp.fr __ - 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] - 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]
Re: JCOVERAGE for MAVEN 2
Try clover, but it's a commercial tool. http://maven.apache.org/maven2/plugins/maven-clover-plugin/ REBOISSON Eric a écrit : Ok. But is there a coverage plugin whitch run whith M2 ? Thanks -Message d'origine- De : David Sag [mailto:[EMAIL PROTECTED] Envoyé : mardi 8 novembre 2005 10:03 À : Maven Users List Cc : 'Maven Users List' Objet : RE: JCOVERAGE for MAVEN 2 There is no maven 2 plugin for cobertura according to the developers. dave REBOISSON Eric [EMAIL PROTECTED] wrote on 08-11-2005 09:46:48: I tried to use Cobertura but this error appears , why ? How to resolve it ? : D:\Documents and Settings\reboisse\workspace\DataModelmvn cobertura:report [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'cobertura'. Downloading: http://repo1.maven.org/maven2/cobertura/cobertura/1.4/cobertura-1.4.pom 150b downloaded Downloading: http://repo1.maven.org/maven2/cobertura/cobertura/1.4/cobertura-1.4.jar 80K downloaded [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager. java:292) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPl uginManager.java:198) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManag er.java:163) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLife cycleExecutor.java:1095) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(Defaul tLifecycleExecutor.java:1305) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggrega tionNeeds(DefaultLifecycleExecutor.java:376) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle Executor.java:132) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) 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) [INFO] [INFO] Total time: 8 seconds [INFO] Finished at: Tue Nov 08 09:45:42 CET 2005 [INFO] Final Memory: 1M/3M [INFO] D:\Documents and Settings\reboisse\workspace\DataModel -Message d'origine- De : stéphane bouchet [mailto:[EMAIL PROTECTED] Envoyé : lundi 7 novembre 2005 17:28 À : Maven Users List Objet : Re: JCOVERAGE for MAVEN 2 Jcoverage is a commercial tool, prefer cobertura. the plugin for maven2 is still in dev. http://maven-plugins.sourceforge.net/maven-cobertura-plugin/ STéphane REBOISSON Eric a écrit : Is there a JCOVERAGE plugins for maven 2 ? How to install it if it exists ? Thanks Eric __ Ce message (et toutes ses pièces jointes éventuelles) est confidentiel et établi à l'intention exclusive de ses destinataires. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'IFP décline toute responsabilité au titre de ce message. This message and any attachments (the message) are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. IFP should not be liable for this message. Visitez notre site Web / Visit our web site : http://www.ifp.fr __ - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED
Re: [m2] aspectj
Hi, In my case, i will not upgrade to maven2 unless an aspectj plugin. I am like the majority of users, because my project uses java 1.4 and i cannot change that prereq. So for the moment I will wait for a plugin before migrate to maven2. And if there wil not be a plugin, i will try to write one ;) Regards, Stéphane Kaare Nilsen a écrit : You should not rely on the number of people that asks for priority. The persons that asks are the one who already have a motivation of using maven, the wast majority i would suspect checks if maven have a plugin for it, if not they would use something else. I for sure would not use maven if i was not on a java 1.5 project due to the fact of the missing aspectJ plugin. But luckily using aspectJ 5 and java 1.5 i don't need a special compiler. With all that said. Maven2 really has made my building way more easy, and if you could use java 1.5 and aspectJ 5 that is a working combination /Kaare Nilsen On 07/11/05, Brett Porter [EMAIL PROTECTED] wrote: I don't believe this is currently working. You're probably the 3rd person that has asked all year - so that probably justifies the priority :) That's possibly just a matter of it not being there though - I'm sure if it was started more would come out of the woodwork. There has been some discussion on this list in the past about possible ways to implement it - if you are interested in searching for that, revieweing, and reviving the discussion, we'd really appreciate anything you are able to contribute. For myself, I'm not an aspectj user. Cheers, Brett On 11/5/05, Eduardo Rocha [EMAIL PROTECTED] wrote: I have seen in Maven Plugin Matrix that AspectJ Plugin for Maven 2 is considered Low Priority (!) and it is yet to be done. However, I was googling around and found some Maven2 compilers besides javac (eclipse, aspectj), called plexus-SOMENAME-compiler. I saw in this mail list as well someone trying to use csharp compiler as well. Does anyone already has AspectJ + Maven 2 working? Does anyone know how to properly use these plexus compilers? - 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] - 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]
Re: JCOVERAGE for MAVEN 2
Jcoverage is a commercial tool, prefer cobertura. the plugin for maven2 is still in dev. http://maven-plugins.sourceforge.net/maven-cobertura-plugin/ STéphane REBOISSON Eric a écrit : Is there a JCOVERAGE plugins for maven 2 ? How to install it if it exists ? Thanks Eric __ Ce message (et toutes ses pièces jointes éventuelles) est confidentiel et établi à l'intention exclusive de ses destinataires. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'IFP décline toute responsabilité au titre de ce message. This message and any attachments (the message) are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. IFP should not be liable for this message. Visitez notre site Web / Visit our web site : http://www.ifp.fr __ - 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]
[ANN] Maven kodo plugin 4.0.0 released
The maven-kodo-plugin team is pleased to announce the Kodo Plugin 4.0.0-EA2 release! http://maven-plugins.sourceforge.net/maven-kodo-plugin/ Maven plugin for Solarmetric's Kodo JDO implementation Changes in this version include: New Features: o This version requires Kodo 4.0.0-EA2 jars. Please note that this version is in an early stage. To automatically install the plugin, type the following on a single line: maven plugin:download -DgroupId=maven-kodo-plugin -DartifactId=maven-kodo-plugin -Dversion=4.0.0-EA2 For a manual installation, you can download the plugin here: http://www.ibiblio.org/maven,http://maven-plugins.sourceforge.net/repository/maven-kodo-plugin/plugins/maven-kodo-plugin-4.0.0-EA2.jar Have fun! -The maven-kodo-plugin team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m1] multiproject dependency problem
sorry for long delay ... see below . Jörg Schaible a écrit : stéphane bouchet wrote on Friday, August 26, 2005 3:44 PM: Jörg Schaible a écrit : stéphane bouchet wrote on Friday, August 26, 2005 11:54 AM: OK, more infos : 1/ Using the multiproject 1.4.1 plugin 2/ Using Eclipse 3.1 with Mevenide 3/ in Fact, i have a project that manage the two others, called 'maven'. it is in its project.properties that the props maven.multiproject.includes and maven.multiproject.basedirare sets. in its project.xml, there is no dependency att all (just reports), and this project is excluded when i launch 'multiproject:install' . Can you call pom:validate ? - Jörg Wow. got lots of errors :) the problem is that the pom:validate don't work with extended descriptors. and my 'applets' and 'core' projects extends this one. Oh, they normally do. They just don't like an inherited build section. ok, understood. Anyway i corrected some errors in 'maven' and still not working . Originally I thought your using pre 1.0.2, since there was an error, where the reactor ignored the deps because of an exception. SOmething strange too is that the docs in the maven site about the project descriptor does not match my acual (and corrected) pom ?? Maybe i could try Maven 1.1beta ? Can't say. I use 1.0.2 without this problems and I have some multiprojects. Is your dependency section really in side the dependencies tags? Or do you have two depednencies sections (had any of this already)? I still believe it's something in your POMs. HUm. i tried Maven 1.1 Beta and still no luck :( Anyway i think there is some problem in my deps too, but could not find out where !! Stéphane - Jörg - 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]
Re: [m1] multiproject dependency problem
Jörg Schaible a écrit :
stéphane bouchet wrote on Thursday, August 25, 2005 2:09 PM:
Hi all,
I have a problem using multiproject.
i have a project called 'core' and another called 'applet'.
the 'applet' project depends on the 'core' one.
So i defined in the 'applet' project.xml :
dependency
groupId${pom.groupId}/groupId
artifactIdcore/artifactId
version${current.version}/version
typejar/type
properties
eclipse.dependencytrue/eclipse.dependency
/properties /dependency
But when i do a multiproject:install, the build order is 'applet'
THEN 'core' ?? and of course i got a dependency error :)
Could some helps me ?
Which version of Maven exactly? Does you see an exception when starting with -X
?
- Jörg
Hi,
I am using Maven 1.0.2 with jdk 1.5 .
No exceptions with -X
Stéphane
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m1] multiproject dependency problem
OK, more infos :
1/ Using the multiproject 1.4.1 plugin
2/ Using Eclipse 3.1 with Mevenide
3/ in Fact, i have a project that manage the two others, called 'maven'.
it is in its project.properties that the props maven.multiproject.includes
and maven.multiproject.basedirare sets. in its project.xml, there is no
dependency att all (just reports), and this project is excluded when i launch
'multiproject:install' .
Thanks for any help
Stéphane
stéphane bouchet a écrit :
Jörg Schaible a écrit :
stéphane bouchet wrote on Thursday, August 25, 2005 2:09 PM:
Hi all,
I have a problem using multiproject.
i have a project called 'core' and another called 'applet'.
the 'applet' project depends on the 'core' one.
So i defined in the 'applet' project.xml :
dependency
groupId${pom.groupId}/groupId
artifactIdcore/artifactId
version${current.version}/version
typejar/type
properties
eclipse.dependencytrue/eclipse.dependency
/properties /dependency
But when i do a multiproject:install, the build order is 'applet'
THEN 'core' ?? and of course i got a dependency error :)
Could some helps me ?
Which version of Maven exactly? Does you see an exception when
starting with -X ?
- Jörg
Hi,
I am using Maven 1.0.2 with jdk 1.5 .
No exceptions with -X
Stéphane
-
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]
Re: [m1] multiproject dependency problem
Jörg Schaible a écrit : stéphane bouchet wrote on Friday, August 26, 2005 11:54 AM: OK, more infos : 1/ Using the multiproject 1.4.1 plugin 2/ Using Eclipse 3.1 with Mevenide 3/ in Fact, i have a project that manage the two others, called 'maven'. it is in its project.properties that the props maven.multiproject.includes and maven.multiproject.basedirare sets. in its project.xml, there is no dependency att all (just reports), and this project is excluded when i launch 'multiproject:install' . Can you call pom:validate ? - Jörg Wow. got lots of errors :) the problem is that the pom:validate don't work with extended descriptors. and my 'applets' and 'core' projects extends this one. Anyway i corrected some errors in 'maven' and still not working . SOmething strange too is that the docs in the maven site about the project descriptor does not match my acual (and corrected) pom ?? Maybe i could try Maven 1.1beta ? Stéphane - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m1] multiproject dependency problem
Hi all,
I have a problem using multiproject.
i have a project called 'core' and another called 'applet'.
the 'applet' project depends on the 'core' one.
So i defined in the 'applet' project.xml :
dependency
groupId${pom.groupId}/groupId
artifactIdcore/artifactId
version${current.version}/version
typejar/type
properties
eclipse.dependencytrue/eclipse.dependency
/properties
/dependency
But when i do a multiproject:install, the build order is 'applet' THEN 'core'
?? and of course i got a dependency error :)
Could some helps me ?
Stéphane
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m1] multiproject dependency problem
Thanks for the tip but not working :(
I got the same result.
Jeff Jensen a écrit :
Try setting this property with the projects in the order you want them
processed:
maven.multiproject.includes=
Quoting stéphane bouchet [EMAIL PROTECTED]:
Hi all,
I have a problem using multiproject.
i have a project called 'core' and another called 'applet'.
the 'applet' project depends on the 'core' one.
So i defined in the 'applet' project.xml :
dependency
groupId${pom.groupId}/groupId
artifactIdcore/artifactId
version${current.version}/version
typejar/type
properties
eclipse.dependencytrue/eclipse.dependency
/properties
/dependency
But when i do a multiproject:install, the build order is 'applet' THEN 'core'
?? and of course i got a dependency error :)
Could some helps me ?
Stéphane
-
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]
!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiproject build
Hi, i am in the same configuration, but even if i have all my projects depending on my utility project, it is not built in the first place ? So when i do a multiproject:install, my utility project is not on the top list and the build fails Using maven 1.0.2 and multiproject 1.4.1. Thanks Per Abich a écrit : Just put a dependency in your project.xml so that all project depend on your utility project. That should do the trick. Currently, there is no other way of orderig the build process. Per 2005/8/3, [EMAIL PROTECTED] [EMAIL PROTECTED]: Hi, I have a Maven multiproject set up. One of my project is a utility kind of project which is used by my other modules/projects. During the build, can i set up a order in which the projects will be built (or) can i set dependency between my projects so that my utility project will get built first ? newbie gurubaran. * This message and any attachments (the message) are confidential and intended solely for the addressee(s). Any unauthorised use or dissemination is prohibited.E-mails are susceptible to alteration. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. * - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Cobertura and Aspectj
Hi, i am trying to use cobertura with aspectj but it doesn't work : It seems that cobertura canot find the aspectJ libraries ? I use JDK 5.0, Win2k, Maven 1.0.2, last cobertura and aspectj plugins Thanks cobertura:on: [mkdir] Created dir: C:\eclipse\workspace\CASTOR-core\target\docs\cobertura [mkdir] Created dir: C:\eclipse\workspace\CASTOR-core\target\cobertura\classes instrumenting the class-files... Cobertura cvs The copyright for this program is retained by its contributors See the included COPYRIGHT file for a complete list of contributors Cobertura is licensed under the GNU General Public License Cobertura comes with ABSOLUTELY NO WARRANTY instrumenting 138 classes to C:\eclipse\workspace\CASTOR-core\target\cobertura\classes [cobertura-instrument] Exception in thread main java.lang.IllegalArgumentException: Unknown attribute type: org.aspectj.weaver.MethodDeclarationLineNumber [cobertura-instrument] at org.objectweb.asm.Attribute.a(Unknown Source) [cobertura-instrument] at org.objectweb.asm.MethodWriter.a(Unknown Source) [cobertura-instrument] at org.objectweb.asm.ClassWriter.toByteArray(Unknown Source) [cobertura-instrument] at net.sourceforge.cobertura.instrument.Main.addInstrumentation(Main.java:174) [cobertura-instrument] at net.sourceforge.cobertura.instrument.Main.addInstrumentation(Main.java:208) [cobertura-instrument] at net.sourceforge.cobertura.instrument.Main.parseArguments(Main.java:245) [cobertura-instrument] at net.sourceforge.cobertura.instrument.Main.main(Main.java:304) org.apache.commons.jelly.JellyTagException: C:\Documents and Settings\sbouchet\.maven\cache\maven-cobertura-plugin-1.1\plugin.jelly:125:115: ant:cobertura-instrument Error instrumenting classes. See messages above. org.apache.commons.jelly.JellyTagException: C:\Documents and Settings\sbouchet\.maven\cache\maven-cobertura-plugin-1.1\plugin.jelly:144:35: ant:fail org.apache.commons.jelly.JellyTagException: C:\Documents and Settings\sbouchet\.maven\cache\maven-cobertura-plugin-1.1\plugin.jelly:125:115: ant:cobertura-instrument Error instrumenting classes. See messages above. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Site generation failes to replace strings from template
this is a know bug on UNIX systems. (MPXDOC-148) Use the snapshot version of the plugin. To get the current snapshot, you can run : maven plugin:download -DgroupId=maven -DartifactId=maven-xdoc-plugin -Dversion=SNAPSHOT don't forget to set the maven.repo.remote properties to http://cvs.apache.org/repository Stéphane Olaf Lenzmann a écrit : Hi, I'm evaluating Maven 1-1-b1 on a small plain vanilla project, running it on XP and Debian Sarge. Running maven site completes on both OS, but on the Debian box the HTMLs in /target/docs do not contain the properly substituted localized strings, but still show the template keys, e.g. ???template.project_info.section.title???. Same thing works fine on XP. Forcing the site locale in project.properties to either en or de has not changed anything. The templates are available in ~/.maven/cache/maven-xdoc-plugin-1.9.1/plugin-resources/templates and look ok. Any help would be appreciated. Olaf - 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]
error when generate .classpath file using eclipse plugin
Hi, I am using maven 1.0.2 with JDK 1.5 and eclipse 3.1M6 i am trying to set up a multiproject and when i use 'maven eclipse' to generate .classpath files, i got an error when i try to add an eclipse dependency. I follow the described structure : dependency groupIdMYAPP/groupId artifactIdMYAPP-common/artifactId versionSNAPSHOT/version typejar/type properties eclipse.dependencytrue/eclipse.dependency /properties /dependency but when i look into the generated .classpath, i get an entry like : classpathentry kind=src path=C:/MYAPP-common/classpathentry rather than 'path=MYAPP-common'. Can anyone help me ? Stéphane - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: error when generate .classpath file using eclipse plugin
Hi After looking at my properties file, i removed the line maven.eclipse.classpath.include that caused the error. But Now the project is not dependent. when i launch maven eclipse, i got : Tentative de téléchargement de MYAPP-common-SNAPSHOT.jar. Response content length is not known ATTENTION: Impossible de télécharger MYAPP-common-SNAPSHOT.jar. BUILD FAILED File.. C:\Documents and Settings\sbouchet\.maven\cache\maven-multiproject-plugin-1.4.1\plugin.jelly Element... maven:reactor Line.. 218 Column 9 Le processus ne peut continuer à cause de la dépendance manquante suivante: MYAPP-common-SNAPSHOT.jar stéphane bouchet a écrit : Hi, I am using maven 1.0.2 with JDK 1.5 and eclipse 3.1M6 i am trying to set up a multiproject and when i use 'maven eclipse' to generate .classpath files, i got an error when i try to add an eclipse dependency. I follow the described structure : dependency groupIdMYAPP/groupId artifactIdMYAPP-common/artifactId versionSNAPSHOT/version typejar/type properties eclipse.dependencytrue/eclipse.dependency /properties /dependency but when i look into the generated .classpath, i get an entry like : classpathentry kind=src path=C:/MYAPP-common/classpathentry rather than 'path=MYAPP-common'. Can anyone help me ? Stéphane - 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]
Re: [REPOST] Having a problem with the Project Info Reports
for the moment i used maven 1.0.2 with latests plugins released. for the xdoc one, is used the snapshot and waiting for the release. i hope some of the issues in jira will be closed :) Stéphane Michael Niemaz a écrit : Very sorry for asking the question again but I need to know if I wait for an update or if I get back to maven-1.0.2. --mike Michael Niemaz wrote: When will it be shipped into the plugin? --mike stéphane bouchet wrote: Tested and working great. Thanks ! Stéphane Vincent Siveton a écrit : Done in svn. Cheers, Vincent 2005/6/21, Arnaud HERITIER [EMAIL PROTECTED]: Yes please. Vincent will fix it ;-D Arnaud -Message d'origine- De : stéphane bouchet [mailto:[EMAIL PROTECTED] Envoyé : mardi 21 juin 2005 16:14 À : Maven Users List Objet : Re: Having a problem with the Project Info Reports Well, after setting *by hand* the bundle from plugin-resources\templates\templates to plugin-resources/templates/templates the goal xdoc:jelly-transform generated the good html document. so do i need to fill an issue in JIRA ? Stéphane stéphane bouchet a écrit : Hi, I am having the same problem with differents environments. On my Win2k box, with JDK 1.4.2, i got a good report document But in my Solaris box, with JDK 1.5, i got a bad report document. when i look in the generated reports, for example maven-reports.xml, in both case i got : properties title key=template.maven_reports.title bundle=plugin-resources\templates\templates / /properties So in Unix environements, there is a problem with the bundle ? Cheers, Stéphane Incze Lajos a écrit : Vincent is right, bundle=plugin-resources\templates\templates is plain wrong (it may work on windows, but nowhere else). I checked the xdoc plugin templates with bundle=plugin-resources.templates.templates and it cures your problem. Also, it may cause problems, when files contain operators, this way they are not valid xml (they are not inside a CDATA section). Altough, as I see, all of them are in jelly directives, so they may disappear before parsing the xml, I don' know jelly. incze On Mon, Jun 20, 2005 at 10:54:35AM -0400, Mike Ratliff wrote: I am working on Mac OS X (10.4.1) I got the reports to work just fine if I downgraded to Maven version 1.0.2 from Beta 1 of 1.1. I am now working under the assumption that it is a problem with the beta and Mac OS X, but that is just a guess. On your suggestion of changing the backslash to a dot...I am not sure how to see the results of that change. Those files are generated and therefor I don't really have an opportunity to see the results of that change being processed. Am I missing something in your suggestion? On 6/20/05, Vincent Siveton [EMAIL PROTECTED] wrote: Hi Mike, What is your environnement? And just to be sure, lets try to replace the backslash character by a dot in the bundle definition, ie: bundle=plugin-resources\templates\templates by bundle=plugin-resources.templates.templates Gives me your feedback, Cheers, Vincent 2005/6/18, Mike Ratliff [EMAIL PROTECTED]: The problem that I am having is manifesting itself on all the reports under the Project Info group (mailing lists, project team, project inf, etc) The other reports (checkstyle, fileactivity, etc) work just fine. The problem is that all the section headers and such have odd references embedded instead of the text they should have. A sample of the project-info xml and html follows... ** *** document properties title key=template.project_info.title bundle=plugin-resources\templates\templates/ /properties body section key=template.project_info.section.title bundle=plugin-resources\templates\templates p message key=template.project_info.section.project_information1 bundle=plugin-resources\templates\templates/ a href=http://maven.apache.org/;Maven/a message key=template.project_info.section.project_information2 bundle=plugin-resources\templates\templates/ /p ** * this results in html output that looks something like: ** ** ???template.maven_reports.section.title??? ???template.maven_reports.section.maven_reports1??? Maven ???template.maven_reports.section.maven_reports2??? ???template.maven_reports.section.subsection.title??? ** I realize I must be missing something simple, but I don't have a clue as to what it is. -- --- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Mike
Re: [REPOST] Having a problem with the Project Info Reports
following the solution described in MPXDOC-148 : To get the current snapshot, you can run : maven plugin:download -DgroupId=maven -DartifactId=maven-xdoc-plugin -Dversion=SNAPSHOT don't forget to set the maven.repo.remote properties to http://cvs.apache.org/repository Stéphane Michael Niemaz a écrit : Could you tell me what maven file to modify in order to bind on that snapshot? thanx, --mike stéphane bouchet wrote: for the moment i used maven 1.0.2 with latests plugins released. for the xdoc one, is used the snapshot and waiting for the release. i hope some of the issues in jira will be closed :) Stéphane Michael Niemaz a écrit : Very sorry for asking the question again but I need to know if I wait for an update or if I get back to maven-1.0.2. --mike Michael Niemaz wrote: When will it be shipped into the plugin? --mike stéphane bouchet wrote: Tested and working great. Thanks ! Stéphane Vincent Siveton a écrit : Done in svn. Cheers, Vincent 2005/6/21, Arnaud HERITIER [EMAIL PROTECTED]: Yes please. Vincent will fix it ;-D Arnaud -Message d'origine- De : stéphane bouchet [mailto:[EMAIL PROTECTED] Envoyé : mardi 21 juin 2005 16:14 À : Maven Users List Objet : Re: Having a problem with the Project Info Reports Well, after setting *by hand* the bundle from plugin-resources\templates\templates to plugin-resources/templates/templates the goal xdoc:jelly-transform generated the good html document. so do i need to fill an issue in JIRA ? Stéphane stéphane bouchet a écrit : Hi, I am having the same problem with differents environments. On my Win2k box, with JDK 1.4.2, i got a good report document But in my Solaris box, with JDK 1.5, i got a bad report document. when i look in the generated reports, for example maven-reports.xml, in both case i got : properties title key=template.maven_reports.title bundle=plugin-resources\templates\templates / /properties So in Unix environements, there is a problem with the bundle ? Cheers, Stéphane Incze Lajos a écrit : Vincent is right, bundle=plugin-resources\templates\templates is plain wrong (it may work on windows, but nowhere else). I checked the xdoc plugin templates with bundle=plugin-resources.templates.templates and it cures your problem. Also, it may cause problems, when files contain operators, this way they are not valid xml (they are not inside a CDATA section). Altough, as I see, all of them are in jelly directives, so they may disappear before parsing the xml, I don' know jelly. incze On Mon, Jun 20, 2005 at 10:54:35AM -0400, Mike Ratliff wrote: I am working on Mac OS X (10.4.1) I got the reports to work just fine if I downgraded to Maven version 1.0.2 from Beta 1 of 1.1. I am now working under the assumption that it is a problem with the beta and Mac OS X, but that is just a guess. On your suggestion of changing the backslash to a dot...I am not sure how to see the results of that change. Those files are generated and therefor I don't really have an opportunity to see the results of that change being processed. Am I missing something in your suggestion? On 6/20/05, Vincent Siveton [EMAIL PROTECTED] wrote: Hi Mike, What is your environnement? And just to be sure, lets try to replace the backslash character by a dot in the bundle definition, ie: bundle=plugin-resources\templates\templates by bundle=plugin-resources.templates.templates Gives me your feedback, Cheers, Vincent 2005/6/18, Mike Ratliff [EMAIL PROTECTED]: The problem that I am having is manifesting itself on all the reports under the Project Info group (mailing lists, project team, project inf, etc) The other reports (checkstyle, fileactivity, etc) work just fine. The problem is that all the section headers and such have odd references embedded instead of the text they should have. A sample of the project-info xml and html follows... ** *** document properties title key=template.project_info.title bundle=plugin-resources\templates\templates/ /properties body section key=template.project_info.section.title bundle=plugin-resources\templates\templates p message key=template.project_info.section.project_information1 bundle=plugin-resources\templates\templates/ a href=http://maven.apache.org/;Maven/a message key=template.project_info.section.project_information2 bundle=plugin-resources\templates\templates/ /p ** * this results in html output that looks something like: ** ** ???template.maven_reports.section.title??? ???template.maven_reports.section.maven_reports1??? Maven
Re: Having a problem with the Project Info Reports
Tested and working great. Thanks ! Stéphane Vincent Siveton a écrit : Done in svn. Cheers, Vincent 2005/6/21, Arnaud HERITIER [EMAIL PROTECTED]: Yes please. Vincent will fix it ;-D Arnaud -Message d'origine- De : stéphane bouchet [mailto:[EMAIL PROTECTED] Envoyé : mardi 21 juin 2005 16:14 À : Maven Users List Objet : Re: Having a problem with the Project Info Reports Well, after setting *by hand* the bundle from plugin-resources\templates\templates to plugin-resources/templates/templates the goal xdoc:jelly-transform generated the good html document. so do i need to fill an issue in JIRA ? Stéphane stéphane bouchet a écrit : Hi, I am having the same problem with differents environments. On my Win2k box, with JDK 1.4.2, i got a good report document But in my Solaris box, with JDK 1.5, i got a bad report document. when i look in the generated reports, for example maven-reports.xml, in both case i got : properties title key=template.maven_reports.title bundle=plugin-resources\templates\templates / /properties So in Unix environements, there is a problem with the bundle ? Cheers, Stéphane Incze Lajos a écrit : Vincent is right, bundle=plugin-resources\templates\templates is plain wrong (it may work on windows, but nowhere else). I checked the xdoc plugin templates with bundle=plugin-resources.templates.templates and it cures your problem. Also, it may cause problems, when files contain operators, this way they are not valid xml (they are not inside a CDATA section). Altough, as I see, all of them are in jelly directives, so they may disappear before parsing the xml, I don' know jelly. incze On Mon, Jun 20, 2005 at 10:54:35AM -0400, Mike Ratliff wrote: I am working on Mac OS X (10.4.1) I got the reports to work just fine if I downgraded to Maven version 1.0.2 from Beta 1 of 1.1. I am now working under the assumption that it is a problem with the beta and Mac OS X, but that is just a guess. On your suggestion of changing the backslash to a dot...I am not sure how to see the results of that change. Those files are generated and therefor I don't really have an opportunity to see the results of that change being processed. Am I missing something in your suggestion? On 6/20/05, Vincent Siveton [EMAIL PROTECTED] wrote: Hi Mike, What is your environnement? And just to be sure, lets try to replace the backslash character by a dot in the bundle definition, ie: bundle=plugin-resources\templates\templates by bundle=plugin-resources.templates.templates Gives me your feedback, Cheers, Vincent 2005/6/18, Mike Ratliff [EMAIL PROTECTED]: The problem that I am having is manifesting itself on all the reports under the Project Info group (mailing lists, project team, project inf, etc) The other reports (checkstyle, fileactivity, etc) work just fine. The problem is that all the section headers and such have odd references embedded instead of the text they should have. A sample of the project-info xml and html follows... ** *** document properties title key=template.project_info.title bundle=plugin-resources\templates\templates/ /properties body section key=template.project_info.section.title bundle=plugin-resources\templates\templates p message key=template.project_info.section.project_information1 bundle=plugin-resources\templates\templates/ a href=http://maven.apache.org/;Maven/a message key=template.project_info.section.project_information2 bundle=plugin-resources\templates\templates/ /p ** * this results in html output that looks something like: ** ** ???template.maven_reports.section.title??? ???template.maven_reports.section.maven_reports1??? Maven ???template.maven_reports.section.maven_reports2??? ???template.maven_reports.section.subsection.title??? ** I realize I must be missing something simple, but I don't have a clue as to what it is. -- --- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Mike Ratliff - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL
Re: Having a problem with the Project Info Reports
Hi, I am having the same problem with differents environments. On my Win2k box, with JDK 1.4.2, i got a good report document But in my Solaris box, with JDK 1.5, i got a bad report document. when i look in the generated reports, for example maven-reports.xml, in both case i got : properties title key=template.maven_reports.title bundle=plugin-resources\templates\templates / /properties So in Unix environements, there is a problem with the bundle ? Cheers, Stéphane Incze Lajos a écrit : Vincent is right, bundle=plugin-resources\templates\templates is plain wrong (it may work on windows, but nowhere else). I checked the xdoc plugin templates with bundle=plugin-resources.templates.templates and it cures your problem. Also, it may cause problems, when files contain operators, this way they are not valid xml (they are not inside a CDATA section). Altough, as I see, all of them are in jelly directives, so they may disappear before parsing the xml, I don' know jelly. incze On Mon, Jun 20, 2005 at 10:54:35AM -0400, Mike Ratliff wrote: I am working on Mac OS X (10.4.1) I got the reports to work just fine if I downgraded to Maven version 1.0.2 from Beta 1 of 1.1. I am now working under the assumption that it is a problem with the beta and Mac OS X, but that is just a guess. On your suggestion of changing the backslash to a dot...I am not sure how to see the results of that change. Those files are generated and therefor I don't really have an opportunity to see the results of that change being processed. Am I missing something in your suggestion? On 6/20/05, Vincent Siveton [EMAIL PROTECTED] wrote: Hi Mike, What is your environnement? And just to be sure, lets try to replace the backslash character by a dot in the bundle definition, ie: bundle=plugin-resources\templates\templates by bundle=plugin-resources.templates.templates Gives me your feedback, Cheers, Vincent 2005/6/18, Mike Ratliff [EMAIL PROTECTED]: The problem that I am having is manifesting itself on all the reports under the Project Info group (mailing lists, project team, project inf, etc) The other reports (checkstyle, fileactivity, etc) work just fine. The problem is that all the section headers and such have odd references embedded instead of the text they should have. A sample of the project-info xml and html follows... * document properties title key=template.project_info.title bundle=plugin-resources\templates\templates/ /properties body section key=template.project_info.section.title bundle=plugin-resources\templates\templates p message key=template.project_info.section.project_information1 bundle=plugin-resources\templates\templates/ a href=http://maven.apache.org/;Maven/a message key=template.project_info.section.project_information2 bundle=plugin-resources\templates\templates/ /p *** this results in html output that looks something like: ???template.maven_reports.section.title??? ???template.maven_reports.section.maven_reports1??? Maven ???template.maven_reports.section.maven_reports2??? ???template.maven_reports.section.subsection.title??? ** I realize I must be missing something simple, but I don't have a clue as to what it is. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Mike Ratliff - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Having a problem with the Project Info Reports
Well, after setting *by hand* the bundle from plugin-resources\templates\templates to plugin-resources/templates/templates the goal xdoc:jelly-transform generated the good html document. so do i need to fill an issue in JIRA ? Stéphane stéphane bouchet a écrit : Hi, I am having the same problem with differents environments. On my Win2k box, with JDK 1.4.2, i got a good report document But in my Solaris box, with JDK 1.5, i got a bad report document. when i look in the generated reports, for example maven-reports.xml, in both case i got : properties title key=template.maven_reports.title bundle=plugin-resources\templates\templates / /properties So in Unix environements, there is a problem with the bundle ? Cheers, Stéphane Incze Lajos a écrit : Vincent is right, bundle=plugin-resources\templates\templates is plain wrong (it may work on windows, but nowhere else). I checked the xdoc plugin templates with bundle=plugin-resources.templates.templates and it cures your problem. Also, it may cause problems, when files contain operators, this way they are not valid xml (they are not inside a CDATA section). Altough, as I see, all of them are in jelly directives, so they may disappear before parsing the xml, I don' know jelly. incze On Mon, Jun 20, 2005 at 10:54:35AM -0400, Mike Ratliff wrote: I am working on Mac OS X (10.4.1) I got the reports to work just fine if I downgraded to Maven version 1.0.2 from Beta 1 of 1.1. I am now working under the assumption that it is a problem with the beta and Mac OS X, but that is just a guess. On your suggestion of changing the backslash to a dot...I am not sure how to see the results of that change. Those files are generated and therefor I don't really have an opportunity to see the results of that change being processed. Am I missing something in your suggestion? On 6/20/05, Vincent Siveton [EMAIL PROTECTED] wrote: Hi Mike, What is your environnement? And just to be sure, lets try to replace the backslash character by a dot in the bundle definition, ie: bundle=plugin-resources\templates\templates by bundle=plugin-resources.templates.templates Gives me your feedback, Cheers, Vincent 2005/6/18, Mike Ratliff [EMAIL PROTECTED]: The problem that I am having is manifesting itself on all the reports under the Project Info group (mailing lists, project team, project inf, etc) The other reports (checkstyle, fileactivity, etc) work just fine. The problem is that all the section headers and such have odd references embedded instead of the text they should have. A sample of the project-info xml and html follows... * document properties title key=template.project_info.title bundle=plugin-resources\templates\templates/ /properties body section key=template.project_info.section.title bundle=plugin-resources\templates\templates p message key=template.project_info.section.project_information1 bundle=plugin-resources\templates\templates/ a href=http://maven.apache.org/;Maven/a message key=template.project_info.section.project_information2 bundle=plugin-resources\templates\templates/ /p *** this results in html output that looks something like: ???template.maven_reports.section.title??? ???template.maven_reports.section.maven_reports1??? Maven ???template.maven_reports.section.maven_reports2??? ???template.maven_reports.section.subsection.title??? ** I realize I must be missing something simple, but I don't have a clue as to what it is. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Mike Ratliff - 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] - 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]
OutOfMemoryException during xdoc generation
Hi Maven Users, I am experiencing a little problem with the xdoc plugin. After upgrading to 1.9 version ,i got an exception when runnig the site goal. java.lang.reflect.InvocationTargetException 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 com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Caused by: java.lang.OutOfMemoryError: Java heap space Well, it is not very difficult to find the problem, but with the xdoc version before i didn't have this problem ??? My config is : SUN UltraSparc 2x900 Mhz 4096 Mo JDK 1.5.0 So my question is why i am getting this error ? is the xdoc plugin will improve performance to avoid that ? Of course i will pass the -Xmx arg to the JVM ;) Cheers, Stéphane - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OutOfMemoryException during xdoc generation
Thanks Brett, you're doing a great job ! Stéphane PS : after setting MAVEN_OPTS=-Xms512m -Xmx1024m, i have no more problems. Brett Porter a écrit : It is simply a matter of generating more files which has pushed it over the edge. Maven 1.1 Beta 1 will be released shortly, and it does not leak memory in that way, so it is not an issue. - Brett On 6/16/05, stéphane bouchet [EMAIL PROTECTED] wrote: Hi Maven Users, I am experiencing a little problem with the xdoc plugin. After upgrading to 1.9 version ,i got an exception when runnig the site goal. java.lang.reflect.InvocationTargetException 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 com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Caused by: java.lang.OutOfMemoryError: Java heap space Well, it is not very difficult to find the problem, but with the xdoc version before i didn't have this problem ??? My config is : SUN UltraSparc 2x900 Mhz 4096 Mo JDK 1.5.0 So my question is why i am getting this error ? is the xdoc plugin will improve performance to avoid that ? Of course i will pass the -Xmx arg to the JVM ;) Cheers, Stéphane - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Kodo Plugin 3.2.4 Released
The maven-kodo-plugin team is pleased to announce the Kodo Plugin 3.2.4 release! http://maven-plugins.sourceforge.net/maven-kodo-plugin/ Maven plugin for Solarmetric's Kodo JDO implementation Changes in this version include: New Features: o This version requires Kodo 3.2.4 jars. For a manual installation, you can download the plugin here: http://prdownloads.sourceforge.net/maven-plugins/maven-kodo-plugin-3.2.4.jar?download Have fun! -The maven-kodo-plugin team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Aspectj plugin missing ajdoc goal
Hi, Well, i'm using the last release of aspectj (1.2) with eclipse 3.1, and the ajdoc is included in this distribution. After a look on the eclipse website, it is possible to run ajdoc from the command line again :), but i don't know about an ant task. Thanks, Stephane Carlos Sanchez a écrit : Hi, It was removed because the ajdoc ant task was removed from AspectJ. There're no plans to implement it. If you're interested you can give some ideas or provide a patch. Regards Carlos Sanchez A Coruña, Spain http://www.jroller.com/page/carlossg -Original Message- From: stéphane bouchet [mailto:[EMAIL PROTECTED] Sent: Friday, October 15, 2004 10:54 AM To: Maven Users List Subject: Aspectj plugin missing ajdoc goal Hello, I am using the aspectJ plugin with success but it seems that the ajdoc goal was removed in the last version (3.2) . it was present in the first version of the plugin. It could be very usefull to generate the documentation in the same time than the javadoc. Is there any plan about this ? Thanks, Stephane - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Aspectj plugin missing ajdoc goal
Hello, I am using the aspectJ plugin with success but it seems that the ajdoc goal was removed in the last version (3.2) . it was present in the first version of the plugin. It could be very usefull to generate the documentation in the same time than the javadoc. Is there any plan about this ? Thanks, Stephane - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Jcoverage exclusion list
Hi, I'm using maven 1.0 and jcoverage plugin 1.0.7. I would like to exclude some classes from jcoverage and i used the maven.jcoverage.instrumentation.excludes property. the problem is that i would like to exclude differents files : *Tests.class and *Aspect.class . It's working if i put only one pattern, but not with both . The reference guide does not give me any clue... Can anyone help ? Thanks, Stephane. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jcoverage exclusion list
Emmanuel Venisse a écrit :
ant:fileset dir=${maven.build.dest}
ant:include name=**/*.class /
ant:exclude name=${maven.jcoverage.instrumentation.excludes} /
/ant:fileset
You can use this :
ant:fileset dir=${maven.build.dest} includes=**/*.class
excludes=${maven.jcoverage.instrumentation.excludes}/
and define maven.jcoverage.instrumentation.excludes like this:
maven.jcoverage.instrumentation.excludes=**/*Tests.class,**/*Aspect.class
Can you test this little patch and send us the result. If it's ok, I'll
commit it.
Emmanuel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks for the quick reply,
The patch submitted works great, and this is exactly what i needed. :)
In order to work correctly, i had to delete myself the jcoverage.ser
file, because it contains some reference to the files i wanted to exclude.
Could it be possible to delete this file when the clean goal is called ?
Stephane.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jcoverage exclusion list
Shinobu Kawai a écrit :
Hi stéphane,
The patch submitted works great, and this is exactly what i needed. :)
Terrific!
Humm, yes, it is a bad idea to exclude some files from coverage, because
it produce a non-realistic report . but in the same time, there is some
classes you know they will NEVER be called by your tests ( I.E : aspectJ
classes, constants, main() classes ) and to produce a better
report, it could be a solution to exclude these files.
but, it is my point of view ;)
In order to work correctly, i had to delete myself the jcoverage.ser
file, because it contains some reference to the files i wanted to exclude.
Could it be possible to delete this file when the clean goal is called ?
I put the following in my maven.xml:
postGoal name=clean:clean
ant:delete file=${basedir}/jcoverage.ser quiet=true failonerror=false/
/postGoal
Works for me!
Great !
Stephane
Best regards,
-- Shinobu Kawai
--
Shinobu Kawai [EMAIL PROTECTED], [EMAIL PROTECTED]
-
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]
Re: kodo plugin error
Thanks Brett for the reply. it seems the bug comes from kodo, because from an Ant script, i got the same error. Stephane. Brett Porter a écrit : Unfortunately, you'll need to sync. up the version of commons-logging you are using with the one given by Maven I think (1.0.3 IIRC). Quoting stéphane bouchet [EMAIL PROTECTED]: Hi, I am trying to use the kodo plugin with maven. i would like to enhance a set of classes which are using common-logging, but a ran to a classloader problem : Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.SimpleLog does not implement Log can someone help me ? Stephane. - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
kodo plugin error
Hi, I am trying to use the kodo plugin with maven. i would like to enhance a set of classes which are using common-logging, but a ran to a classloader problem : Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.SimpleLog does not implement Log can someone help me ? Stephane. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CheckStyle error:Unable to get class information for
that's right, one solution that worked for me is to put all the path in the @throws tag : @throws org.my.exception , even if the exception is in the same package. Stephane STRAYER, JON (SBCSI) a écrit : Well, I just realized that in my case it's having a problem when I have a @throws tag for and exception I don't import (and don't use the full package prefix). -Original Message- From: Ryan Sonnek [mailto:[EMAIL PROTECTED] Sent: Monday, April 26, 2004 12:11 PM To: Maven Users List Subject: RE: CheckStyle error:Unable to get class information for i've had the same problem. i've filled an issue in jira (http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCHECKSTYLE-20) regarding this problem and have also searched checkstyle's mailing lists to no avail. if anyone out there has a resolution, i have yet to find it. Ryan -Original Message- From: STRAYER, JON (SBCSI) [mailto:[EMAIL PROTECTED] Sent: Monday, April 26, 2004 12:06 PM To: Maven Users List Subject: CheckStyle error:Unable to get class information for I noticed some CheckStyle errors saying it couldn't get class information for some of the exceptions we throw. I thought I could solve the problem by adding the build path to the classpath Maven passes to CheckStyle, but it is already there. I'm out of ideas. - 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] - 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]
