maven default timeout

[guillaume . boucherie]

Hi all,

I'm facing timeout problem when I run maven command.
In fact maven can't find artifact and failed with this message :

[ERROR] Failed to execute goal on project sweetdev-ria-selenium-helpers: 
Could not resolve dependencies for project 
sweetdev-ria.test:sweetdev-ria-selenium-helpers:jar:4.1-SNAPSHOT: Could 
not transfer artifact xalan:xalan:jar:2.7.1 from/to mirrorId (
http://sweetdev.group.echonet/ipa-repository/content/groups/proxy/): No 
response received after 6 -> [Help 1]

I'm behind a proxy and sometimes its take time for the proxy to deliver 
resources.

Can I increase the default timeout and how to do ?

Thanks

Guillaume Boucherie


This message and any attachments (the "message") is
intended solely for the intended addressees and is confidential. 
If you receive this message in error,or are not the intended recipient(s), 
please delete it and any copies from your systems and immediately notify
the sender. Any unauthorized view, use that does not comply with its purpose, 
dissemination or disclosure, either whole or partial, is prohibited. Since the 
internet 
cannot guarantee the integrity of this message which may not be reliable, BNP 
PARIBAS 
(and its subsidiaries) shall not be liable for the message if modified, changed 
or falsified. 
Do not print this message unless it is necessary,consider the environment.

--

Ce message et toutes les pieces jointes (ci-apres le "message") 
sont etablis a l'intention exclusive de ses destinataires et sont confidentiels.
Si vous recevez ce message par erreur ou s'il ne vous est pas destine,
merci de le detruire ainsi que toute copie de votre systeme et d'en avertir
immediatement l'expediteur. Toute lecture non autorisee, toute utilisation de 
ce message qui n'est pas conforme a sa destination, toute diffusion ou toute 
publication, totale ou partielle, est interdite. L'Internet ne permettant pas 
d'assurer
l'integrite de ce message electronique susceptible d'alteration, BNP Paribas 
(et ses filiales) decline(nt) toute responsabilite au titre de ce message dans 
l'hypothese
ou il aurait ete modifie, deforme ou falsifie. 
N'imprimez ce message que si necessaire, pensez a l'environnement.

Re: RAD 7 + EJB Stubs generation + Maven 2

[Guillaume Boucherie]

Hi,

Maybe you can try to use this plugin.
was6-maven-plugin 

CletteBou


On Thu, Dec 11, 2008 at 6:23 PM, Wayne Fay  wrote:

> > Embedded error: Unable to parse setupCmdLine: null\bin\setupCmdLine.bat
> (The
> > system cannot
> > find the path specified.)
>
> I don't have RAD so my ability to help with this specific issue is
> pretty limited. But where is this "setupCmdLine.bat" coming from -- is
> that in RAD somewhere? I'd assume the EJB stub generation tools assume
> you are running the tools from the RAD directories, and it is getting
> confused when it cannot find files it depends on during its execution.
>
> Find the setupCmdLine.bat file in your file system, and then try to
> find what files are invoking it, and either provide it to them as they
> require or find a way to stop them from invoking it.
>
> Wayne
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Super POM PlugIn Configuration / Multimodule Setup

[Guillaume Boucherie]

Hi,
You could find a multimodule configuration for resources files (xml, txt
...) in the checkstyle plugin documentation.
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html

This tips is to create a new maven module (jar) that will contains all your
resources needed by your plugin configuration.
And some plugin could check the classpath to retrieve resources.

Guillaume Boucherie


2008/9/17 Karl Heinz Marbaise <[EMAIL PROTECTED]>

> Hi,
>
> i have a multimodule setup...
>
> Now i have the following question:
>
> I use a plugin (maven-license-plugin) in my parent pom and do the
> configuration of it there as well. The configuration of it are in a
> folder of this parent module
>
>  Parent
>+--- Module A
>+--- Module B
>+--- config-files
>
> Based on the deriving of the parent POM every module now does the
> license check, but within the modules the modules complains about not
> finding the configuration files, so i have added into the
> sub modules an configuration with referencing the configuration-files
> via things like this:
>
> ${basedir}/../config-files to have only a single set of configuration
> files for the plugin
>
> Does exist there an more elegant way to do this ?
>
> Kind regards
> Karl Heinz Marbaise
> --
> SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
> Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029
> Hauptstrasse 177 USt.IdNr: DE191347579
> 52146 Würselen   http://www.soebes.de
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Problems building EAR with HAR

[Guillaume Boucherie]

Hi,
Try to add this in your ear plugin configuration :
  
org.apache.maven.plugins
maven-ear-plugin

  [...]
  

  

  


Guillaume Boucherie


2008/9/8 hal arres <[EMAIL PROTECTED]>

> Hi,
>
> maybe you recognize from this morning :)
> After my first problem building a JAR with a dependeny on a HAR artifact I
> am trying to build the EAR which contains both files, the JAR and the HAR.
> But during this issue I got a build failure which I don't understand. I am
> trying to fix this since a few hours, but without success. It would be very
> nice if you could help me also with this problem.
>
> Maven prints the following message into the console:
> [INFO] Scanning for projects...
> [INFO]
> 
> [INFO] Building Example Backend
> [INFO]task-segment: [install]
> [INFO]
> 
> [INFO] [ear:generate-application-xml]
> [INFO]
> 
> [ERROR] BUILD FAILURE
> [INFO]
> 
> [INFO] Artifact[har:example:c-backend-persistence] is not a dependency of
> the project.
> [INFO]
> 
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> 
> [INFO] Total time: 1 second
> [INFO] Finished at: Mon Sep 08 16:40:32 CEST 2008
> [INFO] Final Memory: 4M/8M
> [INFO]
> 
>
>
> But inside the pom.xml of the ear I have defined the dependency on this
> artefact.
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
>
>4.0.0
>c-backend
>ear
>Example Backend
>
>
>example
>example-parent
>1-SNAPSHOT
>
>
>
>
>example
>c-backend-persistence
>1-SNAPSHOT
>jboss-har
>
>
>example
>c-backend-crs
>1-SNAPSHOT
>
>
>
>
>
>
>
>  org.codehaus.mojo
>  jboss-packaging-maven-plugin
>  
>  true
>
>
>org.apache.maven.plugins
>maven-ear-plugin
>
>
>
>  
> ${artifactId}/src/main/resources/application.xml
>lib
>
>
>true
>
>
>
>
>   example
>c-backend-crs
>
>  true
>
>
>   example
>c-backend-persistence
>
>
>
>
>
>
>
> 
>
>
> I would be glad if someone could help me to fix this problem.
>
> Thank you,
> Hal
>
> --
> Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
> Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Dependencies on a HAR-File

[Guillaume Boucherie]

Hi,
Did you try to use "jboss-har" for the type ?
And don't forget to declare the jboss-packaging-maven-plugin with extension
enabled.

  
org.codehaus.mojo
jboss-packaging-maven-plugin


true
    ...
  



Guillaume Boucherie


2008/9/8 hal arres <[EMAIL PROTECTED]>

> Hi,
>
> my name is Hal and I am starting with maven, but I have a little problem.
> I want to build an EAR-File with dependencies on an har and a jar file. I
> build the har file using the jboss-packaging-maven-plugin. This works fine
> and the artifact is also installed inside the repository, but I have a
> problem to build the jar file. The classes inside the jar file have
> dependencies on the har. I thought it is possible to build the artifact
> using the a dependency type, but it doesn't work.
>
> It would be nice if someone could help me to resolve this problem.
>
> This is the pom.xml of the jar file:
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
>4.0.0
>
>
>example
>example-parent
>1-SNAPSHOT
>
>
>c-backend-jar
>jar
>Example Backend JAR
>
>
>
>
>example
>c-common
>1-SNAPSHOT
>
>
>
>example
>c-backend-persistence
>1-SNAPSHOT
>har
>
>
>
>jboss
>jboss-system
>4.2.2.GA
>provided
>
>
>
>jboss
>jboss-ejb3x
>4.2.2.GA
>provided
>
>
>
>jboss
>jbossall-client
>4.2.2.GA
>test
>
>
>
>jboss
>jboss-ejb3
>4.2.2.GA
>provided
>
>
>
>
> 
>
>
> Thank you,
> Hal
> --
> Pt! Schon das coole Video vom GMX MultiMessenger gesehen?
> Der Eine für Alle: http://www.gmx.net/de/go/messenger03
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: custom packaging problem

[Guillaume Boucherie]

Hi,

I found a workaround. I use the version 2.2 of plexus-archiver instead of
version 2.3.

Guillaume Boucherie


2008/7/2 Guillaume Boucherie <[EMAIL PROTECTED]>:

> Hi all,
>
> I'm trying to make my own packaging type for my skin project.
> So I create a plugin with a components.xml that define my ArtifactHandler
> and my LifecycleMapping.
> But when I launch an mvn clean install on a project with my own packaging I
> have the following error :
>
> [FATAL ERROR] com.ideo.maven.plugins.skin.SkinBundledMojo#execute() caused
> a linkage error (java.lang.IncompatibleClassChangeError) and may be
> out-of-date. Check the realms:
> [FATAL ERROR] Plugin realm =
> app0.child-container[com.ideo.maven.plugins:maven-skin-plugin]
> urls[0] =
> file:/E:/tools/maven/repository-maven2/com/ideo/maven/plugins/maven-skin-plugin/1.0-SNAPSHOT/maven-skin-plugin-1.0-SNAPSHOT.jar
> urls[1] =
> file:/E:/tools/maven/repository-maven2/org/apache/maven/maven-archiver/2.3/maven-archiver-2.3.jar
> urls[2] =
> file:/E:/tools/maven/repository-maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> urls[3] =
> file:/E:/tools/maven/repository-maven2/org/codehaus/plexus/plexus-archiver/1.0-alpha-9/plexus-archiver-1.0-alpha-9.jar
> urls[4] =
> file:/E:/tools/maven/repository-maven2/org/codehaus/plexus/plexus-component-api/1.0-alpha-15/plexus-component-api-1.0-alpha-15.jar
>
> urls[5] =
> file:/E:/tools/maven/repository-maven2/org/codehaus/plexus/plexus-classworlds/1.2-alpha-6/plexus-classworlds-1.2-alpha-6.jar
> urls[6] =
> file:/E:/tools/maven/repository-maven2/org/codehaus/plexus/plexus-io/1.0-alpha-1/plexus-io-1.0-alpha-1.jar
> [FATAL ERROR] Container realm = plexus.core
> urls[0] = file:/E:/tools/maven/maven-2.0.9/lib/maven-2.0.9-uber.jar
> urls[1] =
> file:/E:/tools/maven/repository-maven2/com/ideo/sweetdev/sweetdev-build-tools/1.0/sweetdev-build-tools-1.0.jar
> urls[2] =
> file:/E:/tools/maven/repository-maven2/com/ideo/maven/ideo-build-tools/1.0/ideo-build-tools-1.0.jar
> [INFO]
> 
> [ERROR] FATAL ERROR
> [INFO]
> 
> [INFO] Class org.codehaus.plexus.logging.console.ConsoleLogger does not
> implement the requested interface org.codehaus.plexus.logging.Logger
>
> [INFO]
> 
> [INFO] Trace
> java.lang.IncompatibleClassChangeError: Class
> org.codehaus.plexus.logging.console.ConsoleLogger does not implement the
> requested interface org.codehaus.plexus.logging.Logger
> at
> org.codehaus.plexus.archiver.zip.AbstractZipArchiver.createArchiveMain(AbstractZipArchiver.java:318)
> at
> org.codehaus.plexus.archiver.zip.AbstractZipArchiver.execute(AbstractZipArchiver.java:242)
> at
> org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:673)
> at
> com.ideo.maven.plugins.skin.SkinBundledMojo.performPackaging(SkinBundledMojo.java:143)
> at
> com.ideo.maven.plugins.skin.SkinBundledMojo.execute(SkinBundledMojo.java:124)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> 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:597)
> 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)
>
> Can someone help me please ?
> Thanks
>
> Guillaume Boucherie
>

custom packaging problem

[Guillaume Boucherie]

Hi all,

I'm trying to make my own packaging type for my skin project.
So I create a plugin with a components.xml that define my ArtifactHandler
and my LifecycleMapping.
But when I launch an mvn clean install on a project with my own packaging I
have the following error :

[FATAL ERROR] com.ideo.maven.plugins.skin.SkinBundledMojo#execute() caused a
linkage error (java.lang.IncompatibleClassChangeError) and may be
out-of-date. Check the realms:
[FATAL ERROR] Plugin realm =
app0.child-container[com.ideo.maven.plugins:maven-skin-plugin]
urls[0] =
file:/E:/tools/maven/repository-maven2/com/ideo/maven/plugins/maven-skin-plugin/1.0-SNAPSHOT/maven-skin-plugin-1.0-SNAPSHOT.jar
urls[1] =
file:/E:/tools/maven/repository-maven2/org/apache/maven/maven-archiver/2.3/maven-archiver-2.3.jar
urls[2] =
file:/E:/tools/maven/repository-maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
urls[3] =
file:/E:/tools/maven/repository-maven2/org/codehaus/plexus/plexus-archiver/1.0-alpha-9/plexus-archiver-1.0-alpha-9.jar
urls[4] =
file:/E:/tools/maven/repository-maven2/org/codehaus/plexus/plexus-component-api/1.0-alpha-15/plexus-component-api-1.0-alpha-15.jar

urls[5] =
file:/E:/tools/maven/repository-maven2/org/codehaus/plexus/plexus-classworlds/1.2-alpha-6/plexus-classworlds-1.2-alpha-6.jar
urls[6] =
file:/E:/tools/maven/repository-maven2/org/codehaus/plexus/plexus-io/1.0-alpha-1/plexus-io-1.0-alpha-1.jar
[FATAL ERROR] Container realm = plexus.core
urls[0] = file:/E:/tools/maven/maven-2.0.9/lib/maven-2.0.9-uber.jar
urls[1] =
file:/E:/tools/maven/repository-maven2/com/ideo/sweetdev/sweetdev-build-tools/1.0/sweetdev-build-tools-1.0.jar
urls[2] =
file:/E:/tools/maven/repository-maven2/com/ideo/maven/ideo-build-tools/1.0/ideo-build-tools-1.0.jar
[INFO]

[ERROR] FATAL ERROR
[INFO]

[INFO] Class org.codehaus.plexus.logging.console.ConsoleLogger does not
implement the requested interface org.codehaus.plexus.logging.Logger

[INFO]

[INFO] Trace
java.lang.IncompatibleClassChangeError: Class
org.codehaus.plexus.logging.console.ConsoleLogger does not implement the
requested interface org.codehaus.plexus.logging.Logger
at
org.codehaus.plexus.archiver.zip.AbstractZipArchiver.createArchiveMain(AbstractZipArchiver.java:318)
at
org.codehaus.plexus.archiver.zip.AbstractZipArchiver.execute(AbstractZipArchiver.java:242)
at
org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:673)
at
com.ideo.maven.plugins.skin.SkinBundledMojo.performPackaging(SkinBundledMojo.java:143)
at
com.ideo.maven.plugins.skin.SkinBundledMojo.execute(SkinBundledMojo.java:124)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
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:597)
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)

Can someone help me please ?
Thanks

Guillaume Boucherie

Re: Eclipse Plugin and WTP Facets problem

[Guillaume Boucherie]

Hello,

I'm think the m2eclipse goal is to be used with the eclipse plugin coled
m2eclipse (http://m2eclipse.codehaus.org/).
This plugin add support for maven2 directly in your eclipse and managed
dependencies in special way so you have to used m2eclipse goal.

Guillaume Boucherie


2008/5/21, Martin Höller <[EMAIL PROTECTED]>:
>
> On Wednesday 21 May 2008 Mario-Leander Reimer wrote:
>
> > Another question: Do you know whether the eclipse:m2eclipse goal is meant
> > be used in combination with the WTP settings?
>
>
> No idea, I never used the m2eclipse mojo.
>
>
> - martin
>
>

[maven-surefire-plugin] problem with my tests

[Guillaume Boucherie]

Hi all,

I have a strange behavior with my junit tests.
I have a project with multi-modules.
When I run the tests individually for module (mvn test) everything is ok.
But when I run the tests from the parent pom (mvn test) I have always an
error when my program try to parse an xml file.
See the stack trace for details on error :
org.apache.xml.utils.WrappedRuntimeException: Output method is xml could not
load output_xml.properties (check CLASSPATH)
at
org.apache.xalan.templates.OutputProperties.getDefaultMethodProperties(OutputProperties.java:394)
at
org.apache.xalan.templates.OutputProperties.(OutputProperties.java:132)
at
org.apache.xalan.transformer.TransformerIdentityImpl.(TransformerIdentityImpl.java:104)
at
org.apache.xalan.processor.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:842)
at
com.ideo.sweetdev.data.service.configxml.digester.ConfigXml$ConfigXmlUtil.documentToBytes(ConfigXml.java:506)
at
com.ideo.sweetdev.data.service.configxml.digester.ConfigXml.unmarshall(ConfigXml.java:355)
at
com.ideo.sweetdev.data.service.configxml.digester.ConfigXml.init(ConfigXml.java:253)
at
com.ideo.sweetdev.data.service.configxml.digester.ConfigXml.(ConfigXml.java:133)
at
com.ideo.sweetdev.data.service.configxml.digester.ConfigXmlService.getConfigXml(ConfigXmlService.java:138)
at
com.ideo.sweetdev.data.service.configxml.digester.ConfigXmlService.getConfigXml(ConfigXmlService.java:115)
at
com.ideo.sweetdev.data.service.configxml.digester.ConfigXmlHelper.getConfigXml(ConfigXmlHelper.java:73)
at
com.ideo.sweetdev.core.service.ServiceManager.loadServicesDefinition(ServiceManager.java:470)
at
com.ideo.sweetdev.core.service.ServiceManager.initialize(ServiceManager.java:304)
at
com.ideo.sweetdev.core.service.ServiceManager.(ServiceManager.java:153)
at
com.ideo.sweetdev.core.service.fileConfig.FileConfigHelper.getConfigService(FileConfigHelper.java:28)
at
com.ideo.sweetdev.core.controller.ControllerFactory.initialize(ControllerFactory.java:146)
at
com.ideo.sweetdev.core.controller.ControllerFactory.getInstance(ControllerFactory.java:113)
at
com.ideo.sweetdev.core.controller.TestControllerFactory.setUp(TestControllerFactory.java:77)
at junit.framework.TestCase.runBare(TestCase.java:125)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
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
org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:165)
at org.apache.maven.surefire.Surefire.run(Surefire.java:107)
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
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:289)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:993)

I'm on a windows XP with java-1.6 and maven-2.0.9
Does anybody know something about my problem ?
Thanks

Guillaume B.

Re: maven2 was plugin

[Guillaume Boucherie]

Hum,

Ok thank you, I will try it.

Guillaume Boucherie


2008/5/5, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
>
> You must use the plugin on a machine where Websphere is installed, but you
> can deploy TO any machine running websphere by setting the configuration
> parameters of "host", "port","username" and "password".
>
> Robert Egan
>
> "Guillaume Boucherie" <[EMAIL PROTECTED]> wrote on 05/05/2008
> 09:23:17 AM:
>
>
> > Hi all,
> >
> > I'm trying to find a maven2 plugin for was.
> > I'm want to be able to deploy an ear on a remote websphere.
> >
> > I'm trying the was6 maven plugin from codehaus
> > http://mojo.codehaus.org/was6-maven-plugin/index.html
> > But with this plugin I must run maven on the same machine where
> websphere is
> > install.
> >
> > Does anybody know a plugin that do this work ?
> >
> > Thanks
>
> 
> This email message and any attachments may contain confidential,
> proprietary or non-public information.  The information is intended solely
> for the designated recipient(s).  If an addressing or transmission error
> has misdirected this email, please notify the sender immediately and
> destroy this email.  Any review, dissemination, use or reliance upon this
> information by unintended recipients is prohibited.  Any opinions
> expressed in this email are those of the author personally.
>

maven2 was plugin

[Guillaume Boucherie]

Hi all,

I'm trying to find a maven2 plugin for was.
I'm want to be able to deploy an ear on a remote websphere.

I'm trying the was6 maven plugin from codehaus
http://mojo.codehaus.org/was6-maven-plugin/index.html
But with this plugin I must run maven on the same machine where websphere is
install.

Does anybody know a plugin that do this work ?

Thanks

question about changes plugin

[Guillaume Boucherie]

Hi,

It's possible to generate maven site report for changelog and roadmap from
jira ?
Thanks

Guillaume B.

maven plugin question

[Guillaume Boucherie]

Hi all,

I want to make a maven2 plugin for selenium-grid.
This selenium tools try to read a file named "grid_configuration.yml" at the
root of the classpath with ClassLoader.getResources().
In my plugin I create a "grid_configuration.yml" file but how can I had it
to the classpath ?
Thanks

Guillaume B.

maven plugin question

[Guillaume Boucherie]

Hi all,

I'm trying to make a custom plugin and I have a question about maven API.
In my plugin I want to have two goal. First will run some thing via ssh and
second must stop them.
Is there a way in maven API to store (share, cache ?) custom object between
two different goals ?
Thanks

Guillaume B.

Re: [site plugin] problem for deploying site

[Guillaume Boucherie]

I haven't get exception.
The problem is with the generation of href for the module.
With staging I get the correct value, something like that : module1
But when I deploy I have this module1
I think I will take a look at code's site plugin if I find the time.


2008/3/20, cody zhang <[EMAIL PROTECTED]>:
>
> what exception? print list:
> ...
>
> 2008/3/20, Guillaume Boucherie <[EMAIL PROTECTED]>:
>
> > Hi all,
> >
> >  I have a strange behavior when I try to deploy my site.
> >  I have a multi module project something like that :
> >   project
> > |-- module1
> > '-- module2
> >
> >  In my parent pom.xml I defined the site distributionManagement like
> that :
> >   
> > 
> >   my_id
> >   my name
> >   scp://server/var/www/project
> > 
> >   
> >
> >  First I launch a mvn clean site:stage -DstagingDirectory=E:\test and
> the
> >  generated site was ok.
> >  But when I launch mvn clean site-deploy my generated site is bad.
> >  In fact the module link is broken.
> >
> >  I use maven-2.0.8 with maven-site-plugin:2.0-beta-6
> >
> >  Can you help me please ?
> >
> >
> >  Guillaume
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

[site plugin] problem for deploying site

[Guillaume Boucherie]

Hi all,

I have a strange behavior when I try to deploy my site.
I have a multi module project something like that :
  project
|-- module1
'-- module2

In my parent pom.xml I defined the site distributionManagement like that :
  

  my_id
  my name
  scp://server/var/www/project

  

First I launch a mvn clean site:stage -DstagingDirectory=E:\test and the
generated site was ok.
But when I launch mvn clean site-deploy my generated site is bad.
In fact the module link is broken.

I use maven-2.0.8 with maven-site-plugin:2.0-beta-6

Can you help me please ?

Guillaume

Re: [surefire] problem with xml

[Guillaume Boucherie]

I'm find that the error only appends with jdk1.4
But my project must be compiled and test with jdk1.4
So I can I use the latest version of surefire plugin without problem.
I'm trying to search surefire related thread in archive but I don't see
interesting thing.
Can anyone help me ?

Guillaume Boucherie


2008/3/18, Guillaume Boucherie <[EMAIL PROTECTED]>:
>
> I try with version 2.0.7 and 2.0.8. I have the same error.
> I'm on windows with jdk1.6.0.
> My project is compiled with a jdk1.4.2 and my test is run with the same
> jdk.
>
> Guillaume Boucherie
>
>
> 2008/3/18, Martin Höller <[EMAIL PROTECTED]>:
> >
> > On Tuesday 18 March 2008 Guillaume Boucherie wrote:
> > > I have the problem with surefire 2.4.2 but it works for 2.3.1 !!
> >
> >
> > Which maven versions?
> >
> > There were some issues with combinations of surefire 2.4.x and maven
> > prior
> > to 2.0.8 as well as with maven 2.0.8 and surefire 2.3.x. Try searching
> > the
> > archive for "surefire" to get more details.
> >
> > hth,
> >
> > - martin
> >
> >
>

Re: [surefire] problem with xml

[Guillaume Boucherie]

I try with version 2.0.7 and 2.0.8. I have the same error.
I'm on windows with jdk1.6.0.
My project is compiled with a jdk1.4.2 and my test is run with the same jdk.

Guillaume Boucherie


2008/3/18, Martin Höller <[EMAIL PROTECTED]>:
>
> On Tuesday 18 March 2008 Guillaume Boucherie wrote:
> > I have the problem with surefire 2.4.2 but it works for 2.3.1 !!
>
>
> Which maven versions?
>
> There were some issues with combinations of surefire 2.4.x and maven prior
> to 2.0.8 as well as with maven 2.0.8 and surefire 2.3.x. Try searching the
> archive for "surefire" to get more details.
>
> hth,
>
> - martin
>
>

[surefire] problem with xml

[Guillaume Boucherie]

Hi all,

I encounter problem with my junit tests when I try to update version of
surefire plugin.
Actually all my tests that need to read xml files failed with the following
error :

org.apache.xml.utils.WrappedRuntimeException: Output method is xml could not
load output_xml.properties (check CLASSPATH)
at
org.apache.xalan.templates.OutputProperties.getDefaultMethodProperties(
OutputProperties.java:394)
at org.apache.xalan.templates.OutputProperties.(
OutputProperties.java:132)
at org.apache.xalan.transformer.TransformerIdentityImpl.(
TransformerIdentityImpl.java:104)
at org.apache.xalan.processor.TransformerFactoryImpl.newTransformer(
TransformerFactoryImpl.java:842)
at
com.ideo.sweetdev.data.service.configxml.digester.ConfigXml$ConfigXmlUtil.documentToBytes
(ConfigXml.java:506)
at
com.ideo.sweetdev.data.service.configxml.digester.ConfigXml.unmarshall(
ConfigXml.java:355)
at com.ideo.sweetdev.data.service.configxml.digester.ConfigXml.init(
ConfigXml.java:253)
at com.ideo.sweetdev.data.service.configxml.digester.ConfigXml
.(ConfigXml.java:133)
at
com.ideo.sweetdev.data.service.configxml.digester.ConfigXmlService.getConfigXml
(ConfigXmlService.java:138)
at
com.ideo.sweetdev.data.service.configxml.digester.ConfigXmlService.getConfigXml
(ConfigXmlService.java:115)
at
com.ideo.sweetdev.data.service.configxml.digester.ConfigXmlHelper.getConfigXml
(ConfigXmlHelper.java:73)
at
com.ideo.sweetdev.core.service.ServiceManager.loadServicesDefinition(
ServiceManager.java:470)
at com.ideo.sweetdev.core.service.ServiceManager.initialize(
ServiceManager.java:266)
at com.ideo.sweetdev.core.service.ServiceManager.(
ServiceManager.java:153)
at
com.ideo.sweetdev.core.service.broker.BrokerHelper.getBrokerService(
BrokerHelper.java:51)
at com.ideo.sweetdev.core.service.broker.BrokerHelper.getBroker(
BrokerHelper.java:78)
at
com.ideo.sweetdev.core.service.broker.TestBroker.testServiceCallOk(
TestBroker.java:40)
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 junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
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 org.apache.maven.surefire.junit.JUnitTestSet.execute(
JUnitTestSet.java:213)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(
AbstractDirectoryTestSuite.java:140)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(
AbstractDirectoryTestSuite.java:165)
at org.apache.maven.surefire.Surefire.run(Surefire.java:107)
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
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(
SurefireBooter.java:289)


I have the problem with surefire 2.4.2 but it works for 2.3.1 !!
Any help are welcome.
Thanks

Guillaume Boucherie

problem with dependencies

[Guillaume Boucherie]

Hi,

I have a project with modules.
My first module depends on poi, and my second depends on my first.
When I run eclipse:eclipse from my root project I have poi in both classpath
of my projects, so everything works.
But when I run it from my second project poi isn't in the classpath.
So I try it with the compile plugin and I have the same error.
But maven must use transitive dependencies so why it does not work ?

-- 
CletteBou
clettebou.miniville.fr

[maven-site-plugin] skip subprojects

[Guillaume Boucherie]

Hi,

Is there a way to skip subprojects in site generation.
Let see an example:
  project
  |-- subproject1
  |   `-- pom.xml
  |-- subproject2
  |   |-- subproject21
  |   |   `-- pom.xml
  |   |-- subproject22
  |   |   `-- pom.xml
  |   `--pom.xml
  `-- pom.xml

How can I disable site generation for subproject2, subproject21 and
subproject22 ?
Thanks

-- 
CletteBou
clettebou.miniville.fr

[maven-javadoc-plugin]

[Guillaume Boucherie]

Hi,

I have a project with modules and I configure the javadoc report plugin in
the top level pom.
Is there a way to skip the javadoc report for some projects ?
Thanks

-- 
CletteBou
clettebou.miniville.fr

plugin classpath question

[Guillaume Boucherie]

Hi all,
I have questions about he classpath of maven2 plugin:
  1. How the classpath of a plugin is constructed ?
  2. Is it possible to change it ?
  3. Is it possible to have the generated classes of a project in the
classpath of a plugin ?

Thanks

-- 
CletteBou
clettebou.miniville.fr

Re: [maven2 antrun plugin] problem with classpath

[Guillaume Boucherie]

Hi,

Ok it's finally works fine.
I'm just use the 1.0-beta-1-SNAPSHOT version because the versions in central
repository doesn't work for me.
Thanks

-- 
CletteBou
clettebou.miniville.fr


2007/10/3, Tim Kettler <[EMAIL PROTECTED]>:
>
> Hi,
>
> I can reproduce the problem but have no clue either what the root cause
> could be. Howerver, it's working for me with the xdoclet-maven-plugin
>   [1] from the mojo project:
>
>
>  org.codehaus.mojo
>  xdoclet-maven-plugin
>  
>
>  process-resources
>  
>xdoclet
>  
>  
>
>  
>
>   name="com/ideo/sweetdev/presentation/struts/tag/**/*Tag*.java" />
>
>   jspversion="1.2"
>   shortname="sweetdev-struts"
>   description="This tag library contains the
> SweetDEV standard tags"
>   uri="http://www.sweetdev.com/sweetdev-struts";
>   displayname="SweetDEV"
>   smallicon="icone.jpg"
>   filename="sweetdev-struts.tld"
>>
>
>  
>
>  
>
>  
>
>
> -Tim
>
> [1] http://mojo.codehaus.org/xdoclet-maven-plugin/
>
> Guillaume Boucherie schrieb:
> > Hi all,
> >
> > I'm trying to use xdoclet for my project via the antrun plugin, but I'm
> > encounter problem with classpath.
> > I configure antrun like this:
> > 
> >   [...]
> >   
> > 
> >   
> > maven-antrun-plugin
> > 
> >   
> > process-resources
> > 
> >   
> > 
> > 
> > 
> >   
> > 
> > 
> >   
> >  > name="com/ideo/sweetdev/presentation/struts/tag/**/*Tag*.java" />
> >   
> >>  jspversion="1.2"
> >  shortname="sweetdev-struts"
> >  description="This tag library contains the
> > SweetDEV standard tags"
> >  uri="
> http://www.sweetdev.com/sweetdev-struts";
> >  displayname="SweetDEV"
> >  smallicon="icone.jpg"
> >  filename="sweetdev-struts.tld"
> >   >
> >   
> > 
> >   
> > 
> > 
> >   run
> > 
> >   
> > 
> > 
> >   
> > xdoclet
> > xdoclet-web-module
> > 1.2.3
> >   
> >   
> > xdoclet
> > xjavadoc
> > 1.1
> >   
> > 
> >   
> > 
> >   [...]
> > 
> >
> > And when I run phase process-resources I got this:
> > E:\projects\sweetdev\branches\sweetdev-maven2\sweetdev-struts>mvn
> > process-resources
> > [INFO] Scanning for projects...
> > [INFO]
> >
> 
> > [INFO] Building sweetdev-struts
> > [INFO]task-segment: [process-resources]
> > [INFO]
> >
> 
> > [INFO] [enforcer:enforce {execution: enforce-java}]
> > [INFO] [resources:resources]
> > [INFO] Using default encoding to copy filtered resources.
> > [INFO] [antrun:run {execution: default}]
> > [INFO] Executing tasks
> >  [echo] plugin classpath:
> >   E:\tools\maven\repository-maven2\junit\junit\3.8.1\junit-3.8.1.jar;
> >   E:\tools\maven\repository-maven2\xdoclet\xdoclet\1.2.3\xdoclet-
> 1.2.3.jar;
> >
> E:\tools\maven\repository-maven2\xdoclet\xdoclet-web-module\1.2.3\xdoclet-
> > web-module-1.2.3.jar;
> >
> >
> E:\tools\maven\repository-maven2\commons-logging\commons-logging\1.0.4\commons-
> > logging-1.0.4.jar;
> >   E:\tools\maven\repository-maven2\ant\ant\1.6.5\ant-1.6.5.jar;
> >
> >

[maven2 antrun plugin] problem with classpath

[Guillaume Boucherie]

Hi all,

I'm trying to use xdoclet for my project via the antrun plugin, but I'm
encounter problem with classpath.
I configure antrun like this:

  [...]
  

  
maven-antrun-plugin

  
process-resources

  



  


  

  
  http://www.sweetdev.com/sweetdev-struts";
 displayname="SweetDEV"
 smallicon="icone.jpg"
 filename="sweetdev-struts.tld"
  >
  

  


  run

  


  
xdoclet
xdoclet-web-module
1.2.3
  
  
xdoclet
xjavadoc
1.1
  

  

  [...]


And when I run phase process-resources I got this:
E:\projects\sweetdev\branches\sweetdev-maven2\sweetdev-struts>mvn
process-resources
[INFO] Scanning for projects...
[INFO]

[INFO] Building sweetdev-struts
[INFO]task-segment: [process-resources]
[INFO]

[INFO] [enforcer:enforce {execution: enforce-java}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
 [echo] plugin classpath:
  E:\tools\maven\repository-maven2\junit\junit\3.8.1\junit-3.8.1.jar;
  E:\tools\maven\repository-maven2\xdoclet\xdoclet\1.2.3\xdoclet-1.2.3.jar;
  E:\tools\maven\repository-maven2\xdoclet\xdoclet-web-module\1.2.3\xdoclet-
web-module-1.2.3.jar;

E:\tools\maven\repository-maven2\commons-logging\commons-logging\1.0.4\commons-
logging-1.0.4.jar;
  E:\tools\maven\repository-maven2\ant\ant\1.6.5\ant-1.6.5.jar;

E:\tools\maven\repository-maven2\commons-collections\commons-collections\2.1\commons-
collections-2.1.jar;

E:\tools\maven\repository-maven2\org\codehaus\plexus\plexus-utils\1.1\plexus-
utils-1.1.jar;
  E:\tools\maven\repository-maven2\ant\ant-launcher\1.6.5\ant-
launcher-1.6.5.jar;
  E:\tools\maven\repository-maven2\xdoclet\xjavadoc\1.1\xjavadoc-1.1.jar
;E:\tools\maven\maven-2.0.7\lib\maven-core-2.0.7-uber.jar
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Error executing ant tasks

Embedded error: Can't create a jsptaglib element under webdoclet. Make sure
the jar file containing the corresponding subtask class is on the classpath
specified in the  that defined {2}.
[INFO]

[INFO] For more information, run Maven with the -e switch
[INFO]

[INFO] Total time: 3 seconds
[INFO] Finished at: Tue Oct 02 11:00:01 CEST 2007
[INFO] Final Memory: 6M/12M
[INFO]


I don't understand why antrun can't find the jsptaglib task as it is include
in the jar xdoclet-web-module present in the classpath !!!
Could you help me please ?
Thanks in advance.

-- 
CletteBou
clettebou.miniville.fr

[maven2 plugin development] classpath management

[Guillaume Boucherie]

Hi all,

Is it possible to access and modify the classpath of a maven2 plugin at
runtime ?
In fact I'm trying to develop a plugin and I need to have the class files,
generated in the compile phase, in the classpath for my plugin to work
correctly.
How can I do that ?
Thanks in advance.

-- 
CletteBou
clettebou.miniville.fr

Re: maven-surefire-plugin

[Guillaume Boucherie]

Thanks a lot, I've just tested on my project and it work fine.

-- 
CletteBou
clettebou.miniville.fr


2007/9/26, Tim Kettler <[EMAIL PROTECTED]>:
>
> Ah ok, that's something different. I understand that you don't want to
> create extra projects for this jars as they probably never will change.
>
> First I thought you just could place the jars in a directory in your
> project and add system dependendcies to them. But then I realized that
> 'system' is already a scope and thus one can't further limit the scope
> to 'test'. Thinking about this a bit I think 'system' shouldn't be a
> scope at all, it's more of a dependency type.
>
> The only other solution I can think of is to store the jars in a
> repository like directory layout (for example under src/test/testjars)
> and declare this directory as a repository in your pom:
>
>
>  my-test-artifact-repository
>  file://${basedir}/src/test/testjars
>
>
> and then declare the jars as normal test-scoped dependencies.
>
> -Tim
>
> Guillaume Boucherie schrieb:
> > Oh I'm sorry I'm not clear.
> > In my project I have a functionality that search xml files with the same
> > name in the classpath and merge it before read it.
> > And to test it I must have jars that just contains xml file, I don't
> want to
> > create a maven project just for this type of jar.
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: maven-surefire-plugin

[Guillaume Boucherie]

Oh I'm sorry I'm not clear.
In my project I have a functionality that search xml files with the same
name in the classpath and merge it before read it.
And to test it I must have jars that just contains xml file, I don't want to
create a maven project just for this type of jar.

-- 
CletteBou
clettebou.miniville.fr


2007/9/26, Tim Kettler <[EMAIL PROTECTED]>:
>
> Hi,
>
> you want test dependencies. From [1]:
>
> "test - this scope indicates that the dependency is not required for
> normal use of the application, and is only available for the test
> compilation and execution phases."
>
> -Tim
>
> [1]
>
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
>
> Guillaume Boucherie schrieb:
> > Hi,
> >
> > In the maven1 test plugin it's possible to add jar's in the classpath
> with
> > the properties maven.test.classpath
> > Does maven2 surefire plugin provide a way do to the same ?
> > Thanks
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

maven-surefire-plugin

[Guillaume Boucherie]

Hi,

In the maven1 test plugin it's possible to add jar's in the classpath with
the properties maven.test.classpath
Does maven2 surefire plugin provide a way do to the same ?
Thanks

-- 
CletteBou
clettebou.miniville.fr

Re: maven-jar-plugin - manifest customization

[Guillaume Boucherie]

Thanks for you reply.


2007/9/25, Wayne Fay <[EMAIL PROTECTED]>:
>
> The other approach of course is to change your JAVA_HOME and use the
> jdk4 compiler to run your Java process. Then everything will match up
> and you won't need any extra configuration.
>
> Wayne
>
> On 9/25/07, Tim Kettler <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > this is because the compilation of the sources (compiler-plugin) and the
> > packaging (jar-plugin) is done in two steps.  Even if you fork the
> > compiler, the jar-plugin execution isn't forked and thus runs under the
> > java version you invoked maven with.
> >
> > You can override the maven generated entry like this:
> >
> >
> >  org.apache.maven.plugins
> >  maven-jar-plugin
> >  
> >
> >  
> >1.4.2
> >  
> >
> >  
> >
> >
> > -Tim
> >
> > Guillaume Boucherie schrieb:
> > > My problem is not on jdk version.
> > > I just want to test maven.
> > > And when you use the fork mode in compiler the jdk's manifest entry is
> not
> > > correct.
> > > So I want to know how to get the correct value in manifest.
> > > Thanks
> > >
> >
> >
> > -
> > 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]
>
>


-- 
CletteBou
clettebou.miniville.fr

Re: maven-jar-plugin - manifest customization

[Guillaume Boucherie]

My problem is not on jdk version.
I just want to test maven.
And when you use the fork mode in compiler the jdk's manifest entry is not
correct.
So I want to know how to get the correct value in manifest.
Thanks

-- 
CletteBou
clettebou.miniville.fr


2007/9/25, Jim Sellers <[EMAIL PROTECTED]>:
>
> Do you just need to compile to 1.4 or do you actually need to use a
> different jdk (sun vs ibm)?
>
> If you just need 1.4, this might help:
>
> http://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html
>
> Jim
>
>
> On 9/25/07, Guillaume Boucherie <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> > On my system I have two java installed :
> >   JAVA_HOME that point to a jdk1.5
> >   JAVA_1_4_HOME that point to a jdk1.4
> > So when I run maven it use jdk1.5 and in my project I configure
> > maven-compiler-plugin to use my jdk1.4.
> > But when maven create the manifest for my project he use jdk1.5 for the
> > Build-Jdk entry.
> > How can I customize the manifest to have the correct jdk version in ?
> > Thanks
> >
> > --
> > CletteBou
> > clettebou.miniville.fr
> >
>

maven-jar-plugin - manifest customization

[Guillaume Boucherie]

Hi,
On my system I have two java installed :
  JAVA_HOME that point to a jdk1.5
  JAVA_1_4_HOME that point to a jdk1.4
So when I run maven it use jdk1.5 and in my project I configure
maven-compiler-plugin to use my jdk1.4.
But when maven create the manifest for my project he use jdk1.5 for the
Build-Jdk entry.
How can I customize the manifest to have the correct jdk version in ?
Thanks

-- 
CletteBou
clettebou.miniville.fr

maven2 blacklist

[Guillaume Boucherie]

Hi all,
I'm trying to use archiva and unfortunately maven2 blacklist one of my
repository because of bad configuration.
How can I turn off the blacklisted repository ?
Thanks

CletteBou

Re: ${project.version} is not being resolved

[Guillaume Boucherie]

try ${pom.version} instead of ${project.version}

CletteBou


2007/6/26, Stefan Reinhold <[EMAIL PROTECTED]>:



Hi there,

I'm trying to use ${project.version} in resolving a parent project. But it
does not resolve the property. If I try using an environment variable, e.g
.
${env.VERSION} it fails the same way.

This is the Maven output:

$ mvn -e -X help:effective-pom
+ Error stacktraces are turned on.
Maven version: 2.0.7
Java version: 1.5.0_11
OS name: "windows xp" version: "5.1" arch: "x86"
[DEBUG] Building Maven user-level plugin registry from: 'C:\Dokumente und
Einstellungen\w90115e\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from:
'c:\tools\maven-2.0.7\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[DEBUG] Searching for parent-POM:
com.wieland.wfs:ZentraleKonfiguration::${project.version} of project:
com.wieland.wfs:WFS:pom:1.0-SNAPSHOT in relative path:
ZentraleKonfiguration
[DEBUG] Path specified in  (ZentraleKonfiguration) is a
directory. Searching for 'pom.xml' within this directory.
[DEBUG] Invalid parent-POM referenced by relative path
'ZentraleKonfiguration' in parent specification in
com.wieland.wfs:WFS:pom:1.0-SNAPSHOT:
  Specified: com.wieland.wfs:ZentraleKonfiguration::${project.version}
  Found: com.wieland.wfs:ZentraleKonfiguration:pom:1.0-SNAPSHOT
[DEBUG] Retrieving parent-POM:
com.wieland.wfs:ZentraleKonfiguration::${project.version} for project:
com.wieland.wfs:WFS:pom:1.0-SNAPSHOT from the repository.
[DEBUG] Trying repository central
Downloading:

http://repo1.maven.org/maven2/com/wieland/wfs/ZentraleKonfiguration/${project.version}/ZentraleKonfiguration-${project.version}.pom

My pom.xml is:


http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="
http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd
">
4.0.0
com.wieland.wfs
WFS
Wieland Factory Suite
1.0-SNAPSHOT
pom
http://iwod/jee-wfs

   com.wieland.wfs
   ZentraleKonfiguration
  ${project.version}
  ZentraleKonfiguration

   




Wieland-Werke Aktiengesellschaft
Vorstand:
Harald Kroener, Sprecher
Dr. Jörg Hanisch
Werner T. Traa
Dr. Ulrich Hartmann

Vorsitzender des Aufsichtsrats:
Dr.-Ing. Wolfgang Eychmüller
Sitz der Gesellschaft: Ulm


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

Re: How can the checkstyle plugin be configured to fail the build?

[Guillaume Boucherie]

try something like this.


 
   
 org.apache.maven.plugins
 maven-checkstyle-plugin
 
   
 
   check
 
   
 
   
 


by default the check goal is link to verify phase

CletteBou


2007/6/21, Andrew Moores <[EMAIL PROTECTED]>:


Hello

I want to make my build fail if there are any checkstyle errors in my
code.  I have added the following to my pom:


  

  org.apache.maven.plugins
  maven-checkstyle-plugin
  
  true
  

  


When I execute mvn checkstyle:check my build fails when I have a
checkstyle error.

When I execute mvn install the build does not fail.  Reading the plugin
pages I expected my build to fail for the intall goal as well, what else do
I need to add to the POM to make the build fail?

I am running Maven 2.0.5.

Thanks
Andrew

Re: [ANN] Maven 2.0.7 Released

[Guillaume Boucherie]

stupid cache, it ok
thanks

Clettebou


2007/6/21, Antonio Petrelli <[EMAIL PROTECTED]>:


2007/6/21, Guillaume Boucherie <[EMAIL PROTECTED]>:
>
> The maven's download page, still reference maven-2.0.6, is it correct ?



Strange, I see 2.0.7, maybe you need to clear your cache.

Antonio

Re: [ANN] Maven 2.0.7 Released

[Guillaume Boucherie]

The maven's download page, still reference maven-2.0.6, is it correct ?

CletteBou


2007/6/21, Jason van Zyl <[EMAIL PROTECTED]>:


The Apache Maven team would like to announce the availability of
Maven 2.0.7.

You can find the binaries here:

http://maven.apache.org/download.html

You can find the release notes here:

http://maven.apache.org/release-notes.html

You can find the roadmap here:

http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&&pid=10500&fixfor=13010&sorter/field=issuekey&sorter/
order=DESC

Enjoy,

The Apache Maven Team



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

checkstyle plugin

[Guillaume Boucherie]

I find in the documentation that the goal checkstyle:check is linked to 
the phase verify, but when I lanch the phase verify the goal 
checkstyle:check is never launch.

There is something special to configure ?
Thanks

Guillaume Boucherie

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