Generate Source problem due to org.jvnet.jaxb2.maven2 plugin 0.4.M3 plugin overriding 0.7.1
Hello Everyone,
I am facing strange problem while generating sources from XSD, I am having
multiple modules in my project and some of old modules are using
org.jvnet.jaxb2.maven2 plugin 0.4.M3. New module is using version 0.7.1 of
org.jvnet.jaxb2.maven2 plugin. It works fine while building independently
but fails with existing modules. I suspect that version 0.7.1 is not picked
up at all while building my new module along with others, same has been
confirmed via console output for generate sources.
Configuration details :
Maven version : 2.0.10
JDK : 1.5
POM.xml
build
finalName${project.artifactId}-${version}/finalName
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
/plugin
plugin
groupIdorg.jvnet.jaxb2.maven2/groupId
artifactIdmaven-jaxb2-plugin/artifactId
version0.7.1/version
configuration
args
arg-target/arg
arg2.0/arg
/args
forceRegeneratetrue/forceRegenerate
removeOldOutputtrue/removeOldOutput
extensiontrue/extension
verbosetrue/verbose
/configuration
executions
execution
idSchema Generation/id
phasegenerate-sources/phase
configuration
generatePackagecom.rajesh.health.benefit.scheme.schema/generatePackage
schemaDirectorysrc\main\resources\com\rajesh\benefit\scheme\wsdl/schemaDi
rectory
schemaIncludes
schemaInclude*.xsd/schemaInclude
/schemaIncludes
generateDirectorytarget\generated-sources\xjc\/generateDirectory
/configuration
goals
goalgenerate/goal
/goals
/execution
/executions
/plugin
/plugins
/build
Failed Console output
INFO]
[INFO] Building BenefitSchemeClientWS
[INFO]task-segment: [clean, generate-sources]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory D:\Development Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\target
[INFO] [jaxb2:generate {execution: Schema Generation}]
[INFO] The schemaLanguage setting was not defined, assuming 'AUTODETECT'.
[INFO] The bindingDirectory setting was not defined, assuming the same as
schemaDirectory: D:\Development Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com\rajesh\benefit\scheme\
wsdl
[INFO] Plugin's mojo parameters:
schemaLanguage: AUTODETECT
schemaDirectory: D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com\rajesh\benefit\scheme\
wsdl
schemaIncludes: [*.xsd]
schemaExcludes: null
bindingDirectory: D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com\rajesh\benefit\scheme\
wsdl
bindingIncludes: [*.xjb]
bindingExcludes: null
disableDefaultExcludes: false
catalog: null
defaultPackage:
com.rajesh.health.benefit.scheme.schema
destinationDirectory: D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\target\generated-sources\xjc
forceRegenerate: true
otherDepends: null
removeOldOutput: true
writeCode: true
readOnly: false
extension: true
strict: true
verbose: true
debug: false
xjcArgs: [-target, 2.0, -episode, D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\target\generated-sources\xjc\META-INF\sun-jax
b.episode]
Calculated options:
Schema File(s): [D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com\rajesh\benefit\scheme\
wsdl\BenefitSchemeDomainTypes-1.0.xsd, D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com\rajesh\benefit\scheme\
wsdl\BenefitSchemeExceptionMessage-1.0.xsd, D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com\rajesh\benefit\scheme\
wsdl\BenefitSchemeMessageTypes-1.0.xsd, D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com\rajesh\benefit\scheme\
wsdl
Re: Generate Source problem due to org.jvnet.jaxb2.maven2 plugin 0.4.M3 plugin overriding 0.7.1
Yes, Maven 2.0.10 can't handle different plugin classpaths for the modules.
Either align the versions or (preferably) upgrade to Maven 3.0.4+.
/Anders
On Mon, Oct 28, 2013 at 7:55 AM, Rajesh Singh Rathore
rajesh.rath...@zensar.in wrote:
Hello Everyone,
I am facing strange problem while generating sources from XSD, I am having
multiple modules in my project and some of old modules are using
org.jvnet.jaxb2.maven2 plugin 0.4.M3. New module is using version 0.7.1 of
org.jvnet.jaxb2.maven2 plugin. It works fine while building independently
but fails with existing modules. I suspect that version 0.7.1 is not picked
up at all while building my new module along with others, same has been
confirmed via console output for generate sources.
Configuration details :
Maven version : 2.0.10
JDK : 1.5
POM.xml
build
finalName${project.artifactId}-${version}/finalName
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
/plugin
plugin
groupIdorg.jvnet.jaxb2.maven2/groupId
artifactIdmaven-jaxb2-plugin/artifactId
version0.7.1/version
configuration
args
arg-target/arg
arg2.0/arg
/args
forceRegeneratetrue/forceRegenerate
removeOldOutputtrue/removeOldOutput
extensiontrue/extension
verbosetrue/verbose
/configuration
executions
execution
idSchema Generation/id
phasegenerate-sources/phase
configuration
generatePackagecom.rajesh.health.benefit.scheme.schema/generatePackage
schemaDirectorysrc\main\resources\com\rajesh\benefit\scheme\wsdl/schemaDi
rectory
schemaIncludes
schemaInclude*.xsd/schemaInclude
/schemaIncludes
generateDirectorytarget\generated-sources\xjc\/generateDirectory
/configuration
goals
goalgenerate/goal
/goals
/execution
/executions
/plugin
/plugins
/build
Failed Console output
INFO]
[INFO] Building BenefitSchemeClientWS
[INFO]task-segment: [clean, generate-sources]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory D:\Development Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\target
[INFO] [jaxb2:generate {execution: Schema Generation}]
[INFO] The schemaLanguage setting was not defined, assuming 'AUTODETECT'.
[INFO] The bindingDirectory setting was not defined, assuming the same as
schemaDirectory: D:\Development Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com\rajesh\benefit\scheme\
wsdl
[INFO] Plugin's mojo parameters:
schemaLanguage: AUTODETECT
schemaDirectory: D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com\rajesh\benefit\scheme\
wsdl
schemaIncludes: [*.xsd]
schemaExcludes: null
bindingDirectory: D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com\rajesh\benefit\scheme\
wsdl
bindingIncludes: [*.xjb]
bindingExcludes: null
disableDefaultExcludes: false
catalog: null
defaultPackage:
com.rajesh.health.benefit.scheme.schema
destinationDirectory: D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\target\generated-sources\xjc
forceRegenerate: true
otherDepends: null
removeOldOutput: true
writeCode: true
readOnly: false
extension: true
strict: true
verbose: true
debug: false
xjcArgs: [-target, 2.0, -episode, D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\target\generated-sources\xjc\META-INF\sun-jax
b.episode]
Calculated options:
Schema File(s): [D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com\rajesh\benefit\scheme\
wsdl\BenefitSchemeDomainTypes-1.0.xsd, D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com\rajesh\benefit\scheme\
wsdl\BenefitSchemeExceptionMessage-1.0.xsd, D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com
RE: Generate Source problem due to org.jvnet.jaxb2.maven2 plugin 0.4.M3 plugin overriding 0.7.1
Thanks Anders for you reply, I upgraded maven to version 2.2.1 and it worked
like a charm :)
-Original Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf
Of Anders Hammar
Sent: 28 October 2013 12:36
To: Maven Users List
Subject: Re: Generate Source problem due to org.jvnet.jaxb2.maven2 plugin
0.4.M3 plugin overriding 0.7.1
Yes, Maven 2.0.10 can't handle different plugin classpaths for the modules.
Either align the versions or (preferably) upgrade to Maven 3.0.4+.
/Anders
On Mon, Oct 28, 2013 at 7:55 AM, Rajesh Singh Rathore
rajesh.rath...@zensar.in wrote:
Hello Everyone,
I am facing strange problem while generating sources from XSD, I am
having multiple modules in my project and some of old modules are
using
org.jvnet.jaxb2.maven2 plugin 0.4.M3. New module is using version
0.7.1 of
org.jvnet.jaxb2.maven2 plugin. It works fine while building
independently but fails with existing modules. I suspect that version
0.7.1 is not picked up at all while building my new module along with
others, same has been confirmed via console output for generate sources.
Configuration details :
Maven version : 2.0.10
JDK : 1.5
POM.xml
build
finalName${project.artifactId}-${version}/finalName
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
/plugin
plugin
groupIdorg.jvnet.jaxb2.maven2/groupId
artifactIdmaven-jaxb2-plugin/artifactId
version0.7.1/version
configuration
args
arg-target/arg
arg2.0/arg
/args
forceRegeneratetrue/forceRegenerate
removeOldOutputtrue/removeOldOutput
extensiontrue/extension
verbosetrue/verbose
/configuration
executions
execution
idSchema Generation/id
phasegenerate-sources/phase
configuration
generatePackagecom.rajesh.health.benefit.scheme.schema/generatePack
age
schemaDirectorysrc\main\resources\com\rajesh\benefit\scheme\wsdl/sc
hemaDi
rectory
schemaIncludes
schemaInclude*.xsd/schemaInclude
/schemaIncludes
generateDirectorytarget\generated-sources\xjc\/generateDirectory
/configuration
goals
goalgenerate/goal
/goals
/execution
/executions
/plugin
/plugins
/build
Failed Console output
INFO]
--
--
[INFO] Building BenefitSchemeClientWS
[INFO]task-segment: [clean, generate-sources]
[INFO]
--
--
[INFO] [clean:clean]
[INFO] Deleting directory D:\Development Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\target
[INFO] [jaxb2:generate {execution: Schema Generation}]
[INFO] The schemaLanguage setting was not defined, assuming
'AUTODETECT'.
[INFO] The bindingDirectory setting was not defined, assuming the
same as
schemaDirectory: D:\Development Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com\rajesh\benefit\s
cheme\
wsdl
[INFO] Plugin's mojo parameters:
schemaLanguage: AUTODETECT
schemaDirectory: D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com\rajesh\benefit\s
cheme\
wsdl
schemaIncludes: [*.xsd]
schemaExcludes: null
bindingDirectory: D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com\rajesh\benefit\s
cheme\
wsdl
bindingIncludes: [*.xjb]
bindingExcludes: null
disableDefaultExcludes: false
catalog: null
defaultPackage:
com.rajesh.health.benefit.scheme.schema
destinationDirectory: D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\target\generated-sources\xjc
forceRegenerate: true
otherDepends: null
removeOldOutput: true
writeCode: true
readOnly: false
extension: true
strict: true
verbose: true
debug: false
xjcArgs: [-target, 2.0, -episode,
D:\Development Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\target\generated-sources\xjc\META-INF\s
un-jax
b.episode]
Calculated options:
Schema File(s): [D:\Development
RE: Generate Source problem due to org.jvnet.jaxb2.maven2 plugin 0.4.M3 plugin overriding 0.7.1
Strange, Maven 2.2.1 should have the same problem. It was fixed in Maven 3.
/Anders (mobile)
Den 28 okt 2013 12:55 skrev Rajesh Singh Rathore rajesh.rath...@zensar.in
:
Thanks Anders for you reply, I upgraded maven to version 2.2.1 and it
worked
like a charm :)
-Original Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On
Behalf
Of Anders Hammar
Sent: 28 October 2013 12:36
To: Maven Users List
Subject: Re: Generate Source problem due to org.jvnet.jaxb2.maven2 plugin
0.4.M3 plugin overriding 0.7.1
Yes, Maven 2.0.10 can't handle different plugin classpaths for the modules.
Either align the versions or (preferably) upgrade to Maven 3.0.4+.
/Anders
On Mon, Oct 28, 2013 at 7:55 AM, Rajesh Singh Rathore
rajesh.rath...@zensar.in wrote:
Hello Everyone,
I am facing strange problem while generating sources from XSD, I am
having multiple modules in my project and some of old modules are
using
org.jvnet.jaxb2.maven2 plugin 0.4.M3. New module is using version
0.7.1 of
org.jvnet.jaxb2.maven2 plugin. It works fine while building
independently but fails with existing modules. I suspect that version
0.7.1 is not picked up at all while building my new module along with
others, same has been confirmed via console output for generate sources.
Configuration details :
Maven version : 2.0.10
JDK : 1.5
POM.xml
build
finalName${project.artifactId}-${version}/finalName
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
/plugin
plugin
groupIdorg.jvnet.jaxb2.maven2/groupId
artifactIdmaven-jaxb2-plugin/artifactId
version0.7.1/version
configuration
args
arg-target/arg
arg2.0/arg
/args
forceRegeneratetrue/forceRegenerate
removeOldOutputtrue/removeOldOutput
extensiontrue/extension
verbosetrue/verbose
/configuration
executions
execution
idSchema Generation/id
phasegenerate-sources/phase
configuration
generatePackagecom.rajesh.health.benefit.scheme.schema/generatePack
age
schemaDirectorysrc\main\resources\com\rajesh\benefit\scheme\wsdl/sc
hemaDi
rectory
schemaIncludes
schemaInclude*.xsd/schemaInclude
/schemaIncludes
generateDirectorytarget\generated-sources\xjc\/generateDirectory
/configuration
goals
goalgenerate/goal
/goals
/execution
/executions
/plugin
/plugins
/build
Failed Console output
INFO]
--
--
[INFO] Building BenefitSchemeClientWS
[INFO]task-segment: [clean, generate-sources]
[INFO]
--
--
[INFO] [clean:clean]
[INFO] Deleting directory D:\Development Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\target
[INFO] [jaxb2:generate {execution: Schema Generation}]
[INFO] The schemaLanguage setting was not defined, assuming
'AUTODETECT'.
[INFO] The bindingDirectory setting was not defined, assuming the
same as
schemaDirectory: D:\Development Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com\rajesh\benefit\s
cheme\
wsdl
[INFO] Plugin's mojo parameters:
schemaLanguage: AUTODETECT
schemaDirectory: D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com\rajesh\benefit\s
cheme\
wsdl
schemaIncludes: [*.xsd]
schemaExcludes: null
bindingDirectory: D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com\rajesh\benefit\s
cheme\
wsdl
bindingIncludes: [*.xjb]
bindingExcludes: null
disableDefaultExcludes: false
catalog: null
defaultPackage:
com.rajesh.health.benefit.scheme.schema
destinationDirectory: D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\target\generated-sources\xjc
forceRegenerate: true
otherDepends: null
removeOldOutput: true
writeCode: true
readOnly: false
RE: Generate Source problem due to org.jvnet.jaxb2.maven2 plugin 0.4.M3 plugin overriding 0.7.1
Hmmm, I was having v2.2.1 handy so used it and it worked. I have also tried
with v3.1.1 but having build errors due to required compiler version and I
am not having any control on local maven repository :(
Regards,
Rajesh Rathore
-Original Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf
Of Anders Hammar
Sent: 28 October 2013 17:31
To: Maven Users List
Subject: RE: Generate Source problem due to org.jvnet.jaxb2.maven2 plugin
0.4.M3 plugin overriding 0.7.1
Strange, Maven 2.2.1 should have the same problem. It was fixed in Maven 3.
/Anders (mobile)
Den 28 okt 2013 12:55 skrev Rajesh Singh Rathore rajesh.rath...@zensar.in
:
Thanks Anders for you reply, I upgraded maven to version 2.2.1 and it
worked like a charm :)
-Original Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On
Behalf Of Anders Hammar
Sent: 28 October 2013 12:36
To: Maven Users List
Subject: Re: Generate Source problem due to org.jvnet.jaxb2.maven2
plugin
0.4.M3 plugin overriding 0.7.1
Yes, Maven 2.0.10 can't handle different plugin classpaths for the
modules.
Either align the versions or (preferably) upgrade to Maven 3.0.4+.
/Anders
On Mon, Oct 28, 2013 at 7:55 AM, Rajesh Singh Rathore
rajesh.rath...@zensar.in wrote:
Hello Everyone,
I am facing strange problem while generating sources from XSD, I am
having multiple modules in my project and some of old modules are
using
org.jvnet.jaxb2.maven2 plugin 0.4.M3. New module is using version
0.7.1 of
org.jvnet.jaxb2.maven2 plugin. It works fine while building
independently but fails with existing modules. I suspect that
version
0.7.1 is not picked up at all while building my new module along
with others, same has been confirmed via console output for generate
sources.
Configuration details :
Maven version : 2.0.10
JDK : 1.5
POM.xml
build
finalName${project.artifactId}-${version}/finalName
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
/plugin
plugin
groupIdorg.jvnet.jaxb2.maven2/groupId
artifactIdmaven-jaxb2-plugin/artifactId
version0.7.1/version
configuration
args
arg-target/arg
arg2.0/arg
/args
forceRegeneratetrue/forceRegenerate
removeOldOutputtrue/removeOldOutput
extensiontrue/extension
verbosetrue/verbose
/configuration
executions
execution
idSchema Generation/id
phasegenerate-sources/phase
configuration
generatePackagecom.rajesh.health.benefit.scheme.schema/generatePa
ck
age
schemaDirectorysrc\main\resources\com\rajesh\benefit\scheme\wsdl/
sc
hemaDi
rectory
schemaIncludes
schemaInclude*.xsd/schemaInclude
/schemaIncludes
generateDirectorytarget\generated-sources\xjc\/generateDirectory
/configuration
goals
goalgenerate/goal
/goals
/execution
/executions
/plugin
/plugins
/build
Failed Console output
INFO]
--
--
[INFO] Building BenefitSchemeClientWS
[INFO]task-segment: [clean, generate-sources]
[INFO]
--
--
[INFO] [clean:clean]
[INFO] Deleting directory D:\Development Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\target
[INFO] [jaxb2:generate {execution: Schema Generation}]
[INFO] The schemaLanguage setting was not defined, assuming
'AUTODETECT'.
[INFO] The bindingDirectory setting was not defined, assuming the
same as
schemaDirectory: D:\Development Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com\rajesh\benefit
\s
cheme\
wsdl
[INFO] Plugin's mojo parameters:
schemaLanguage: AUTODETECT
schemaDirectory: D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com\rajesh\benefit
\s
cheme\
wsdl
schemaIncludes: [*.xsd]
schemaExcludes: null
bindingDirectory: D:\Development
Dev\CAS\Release\Business
Services\BenefitSchemeClientWS\src\main\resources\com\rajesh\benefit
\s
cheme\
wsdl
bindingIncludes: [*.xjb]
bindingExcludes: null
disableDefaultExcludes
cargo-maven2-plugin, java.lang.ClassNotFoundException: org.mortbay.jetty.Server
Hi guys, I have a problem! I'm trying start a jetty6x embedded with the maven using the cargo-maven2-plugin, but, when i execute the command: mvn cargo:start , it throw a exception: [INFO] Trace org.codehaus.cargo.container.ContainerException: Failed to start the Jetty 6.x Embedded container. at org.codehaus.cargo.container.spi.AbstractLocalContainer.start(AbstractLocalContainer.java:168) ... Caused by: org.codehaus.cargo.container.ContainerException: Failed to create Jetty Server instance at org.codehaus.cargo.container.jetty.internal.AbstractJettyEmbeddedLocalContainer.createServerObject(AbstractJettyEmbeddedLocalContainer.java:78) Caused by: java.lang.ClassNotFoundException: org.mortbay.jetty.Server at java.net.URLClassLoader$1.run(URLClassLoader.java:202) My configuration in the pom.xml contains: plugin groupIdorg.codehaus.cargo/groupId artifactIdcargo-maven2-plugin/artifactId version1.0/version configuration container containerIdjetty6x/containerId typeembedded/type /container /configuration /plugin Anyone know what's the problem? att, -- Everton Cardoso http://vertocardoso.wordpress.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: cargo-maven2-plugin, java.lang.ClassNotFoundException: org.mortbay.jetty.Server
Hi guys, I was looked the maven-jetty-plugin and i discovered that it was possible running in daemon mode. That it solves my problem already that i want to start the jetty before of execute the integration tests. [...] execution idstart-jetty/id phasepre-integration-test/phase goals goalrun/goal /goals configuration daemontrue/daemon /configuration /execution [...] On Tue, May 25, 2010 at 1:06 PM, Everton Cardoso ercard...@gmail.comwrote: Hi guys, I have a problem! I'm trying start a jetty6x embedded with the maven using the cargo-maven2-plugin, but, when i execute the command: mvn cargo:start , it throw a exception: [INFO] Trace org.codehaus.cargo.container.ContainerException: Failed to start the Jetty 6.x Embedded container. at org.codehaus.cargo.container.spi.AbstractLocalContainer.start(AbstractLocalContainer.java:168) ... Caused by: org.codehaus.cargo.container.ContainerException: Failed to create Jetty Server instance at org.codehaus.cargo.container.jetty.internal.AbstractJettyEmbeddedLocalContainer.createServerObject(AbstractJettyEmbeddedLocalContainer.java:78) Caused by: java.lang.ClassNotFoundException: org.mortbay.jetty.Server at java.net.URLClassLoader$1.run(URLClassLoader.java:202) My configuration in the pom.xml contains: plugin groupIdorg.codehaus.cargo/groupId artifactIdcargo-maven2-plugin/artifactId version1.0/version configuration container containerIdjetty6x/containerId typeembedded/type /container /configuration /plugin Anyone know what's the problem? att, -- Everton Cardoso http://vertocardoso.wordpress.com att, -- Everton Cardoso http://vertocardoso.wordpress.com
Re: Maven2 plugin execution sequence
created feature request 4330, please vote :o)
however i found a work around, not very optimal but it works. - if anybody
knows an alternative im still very interested.
plugin
groupIddk.fujitsu.mavenplugins/groupId
artifactIdsvn/artifactId
version1.9-SNAPSHOT/version
executions
execution
configuration
skip${maven.deploy.skip}/skip
/configuration
phasevalidate/phase
goals
goaluptodate-check/goal
/goals
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
version2.4/version
configuration
skip${maven.deploy.skip}/skip
/configuration
/plugin
properties
maven.deploy.skiptrue/maven.deploy.skip
/properties
now it is only possible to do a deploy by
mvn deploy -Dmaven.deploy.skip=false
which also triggers my plugin in the validation phase
/Claus
--
View this message in context:
http://www.nabble.com/Maven2-plugin-execution-sequence-tp25172369p25204335.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven2 plugin execution sequence
:o( - ok thnaks i will do... Dan Tran wrote: not possible at moment, you may want to file a request to add pre-deploy phase -D On Thu, Aug 27, 2009 at 8:52 AM, claus437claus...@gmail.com wrote: Hi All I have created a little maven 2 plugin that i would like to run each time i do a mvn deploy. The problem is that it needs to be executed before the deploy phase but only if the deploy phase is to be executed in the build, so i can not just bind it to the install phase - and if i bind it to the deploy phase it will be executed afterwards. How do i accomplish this. thanks in advance Best regards Claus -- View this message in context: http://www.nabble.com/Maven2-plugin-execution-sequence-tp25172369p25172369.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Maven2-plugin-execution-sequence-tp25172369p25190360.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven2 plugin execution sequence
file a jira so that people can vote on it On Fri, Aug 28, 2009 at 6:55 AM, claus437claus...@gmail.com wrote: :o( - ok thnaks i will do... Dan Tran wrote: not possible at moment, you may want to file a request to add pre-deploy phase -D On Thu, Aug 27, 2009 at 8:52 AM, claus437claus...@gmail.com wrote: Hi All I have created a little maven 2 plugin that i would like to run each time i do a mvn deploy. The problem is that it needs to be executed before the deploy phase but only if the deploy phase is to be executed in the build, so i can not just bind it to the install phase - and if i bind it to the deploy phase it will be executed afterwards. How do i accomplish this. thanks in advance Best regards Claus -- View this message in context: http://www.nabble.com/Maven2-plugin-execution-sequence-tp25172369p25172369.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Maven2-plugin-execution-sequence-tp25172369p25190360.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven2 plugin execution sequence
Hi All I have created a little maven 2 plugin that i would like to run each time i do a mvn deploy. The problem is that it needs to be executed before the deploy phase but only if the deploy phase is to be executed in the build, so i can not just bind it to the install phase - and if i bind it to the deploy phase it will be executed afterwards. How do i accomplish this. thanks in advance Best regards Claus -- View this message in context: http://www.nabble.com/Maven2-plugin-execution-sequence-tp25172369p25172369.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven2 plugin execution sequence
not possible at moment, you may want to file a request to add pre-deploy phase -D On Thu, Aug 27, 2009 at 8:52 AM, claus437claus...@gmail.com wrote: Hi All I have created a little maven 2 plugin that i would like to run each time i do a mvn deploy. The problem is that it needs to be executed before the deploy phase but only if the deploy phase is to be executed in the build, so i can not just bind it to the install phase - and if i bind it to the deploy phase it will be executed afterwards. How do i accomplish this. thanks in advance Best regards Claus -- View this message in context: http://www.nabble.com/Maven2-plugin-execution-sequence-tp25172369p25172369.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
antlr2, maven2 plugin and importvocab
Hi
I am struggling to get the antlrv2 maven plugin to find the vocabulary of a
grammar.
If I put the grammar in src/main/antlr it finds the grammar ok but the
importVocab command fails.
If I put the vocabulary in the base directory of the maven project, it will
find the vocabulary.
However, if I build the project as part of a modular maven project (i.e it is a
sub module of another module) it cannot find the vocabulary.
I have fiddled with sourceDirectory and the grammar localtion in the plugin.
For example below I have tried to make the sourceDirectory the basedir of the
submodule.
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdantlr-maven-plugin/artifactId
configuration
sourceDirectory${basedir}/sourceDirectory
grammarssrc/main/antlr/MySqlParser.g/grammars
/configuration
executions
execution
goals
goalgenerate/goal
/goals
/execution
/executions
/plugin
Anyone else found a way around this problem? I guess changing maven2's working
directory to that of the grammar would work but it is not clear to me how to do
this.
James
Re: cargo-maven2-plugin
Hi Rémy, You'd better ask your question directly to the cargo mailing list (cf. http://www.nabble.com/Cargo---User-f2406.html). Rémy
cargo-maven2-plugin
Hi, I try to use the cargo-maven2-plugin to merge 2 war projects. I've got the following error when I run the cargo:uberwar goal. Caused by: org.apache.maven.project.InvalidProjectModelException: Not a v4.0.0 POM. for project unknown at... This is my pom.xml : groupIdfr.xxx/groupId artifactIdmergeProject/artifactId packaginguberwar/packaging version1.0-SNAPSHOT/version build plugins plugin groupIdorg.codehaus.cargo/groupId artifactIdcargo-maven2-plugin/artifactId version1.0-beta-1/version configuration descriptormerge.xml/descriptor /configuration /plugin /plugins /build dependencies dependency groupIdfr.xxx/groupId artifactIdproject1/artifactId typewar/type version5.0-SNAPSHOT/version /dependency dependency groupIdfr.xxx/groupId artifactIdproject2/artifactId typewar/type version2.10-SNAPSHOT/version /dependency /dependencies I understand, uberwar is not a Maven's packaging, but it's well specified http://cargo.codehaus.org/Merging+WAR+files here to use this packaging. Thanks for your help. Rémy. -- View this message in context: http://www.nabble.com/cargo-maven2-plugin-tp20270526p20270526.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
hibernate3 maven2 plugin problem
Hi,
While using hibernate3 maven2 plugin. I m getting this error:
[INFO] [hibernate3:hbm2ddl]
[DEBUG] Setting context classloader for plugin to:
/plugins/org.codehaus.mojo:hibernate3-maven-plugin:[EMAIL
PROTECTED]/thread:main (instance is:
ClassRealm[/plugins/org.codehaus.mojo:hibernate3-maven-plugin:[EMAIL
PROTECTED]/thread:main, parent: ClassRealm[plexus.core, parent: null]])
13:00:20,800 INFO org.hibernate.cfg.Environment - Hibernate 3.2.0.cr5
13:00:20,800 INFO org.hibernate.cfg.Environment - loaded properties from
resource hibernate.properties:
{hibernate.dialect=org.hibernate.dialect.MySQLDialect,
hibernate.bytecode.use_reflection_optimizer=false}
13:00:20,800 INFO org.hibernate.cfg.Environment - Bytecode provider name :
cglib
13:00:20,815 INFO org.hibernate.cfg.Environment - using JDK 1.4
java.sql.Timestamp handling
13:00:20,894 INFO org.hibernate.cfg.Configuration - configuring from file:
hibernate.cfg.xml
[DEBUG] basedir: F:\Documents and
Settings\rvgupta\eclipsemavenworkspace\trial-plugin
[INFO] Configuration XML file loaded: F:\Documents and
Settings\rvgupta\eclipsemavenworkspace\trial-plugin\src\main\resources\hibernate.cfg.xml
13:00:21,050 INFO org.hibernate.cfg.JDBCMetaDataConfiguration - Ignoring null
mapping
13:00:21,050 INFO org.hibernate.cfg.Configuration - Configured SessionFactory:
null
[INFO] src/main/resources/database.properties not found within the project.
Trying absolute path.
[INFO] No hibernate properties file loaded.
13:00:21,097 INFO org.hibernate.connection.DriverManagerConnectionProvider -
Using Hibernate built-in connection pool (not for production use!)
13:00:21,097 INFO org.hibernate.connection.DriverManagerConnectionProvider -
Hibernate connection pool size: 20
13:00:21,097 INFO org.hibernate.connection.DriverManagerConnectionProvider -
autocommit mode: false
13:00:21,097 INFO org.hibernate.connection.DriverManagerConnectionProvider -
using driver: com.mysql.jdbc.Driver at URL:
jdbc:mysql://localhost/firsthibernate
13:00:21,112 INFO org.hibernate.connection.DriverManagerConnectionProvider -
connection properties: {user=root, password=}
13:00:21,112 WARN org.hibernate.cfg.SettingsFactory - Could not obtain
connection metadata
java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getConnection(DriverManager.java:545)
at java.sql.DriverManager.getConnection(DriverManager.java:140)
at
org.hibernate.connection.DriverManagerConnectionProvider.getConnection(DriverManagerConnectionProvider.java:110)
at
org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:76)
at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:1929)
at
org.hibernate.cfg.JDBCMetaDataConfiguration.readFromJDBC(JDBCMetaDataConfiguration.java:38)
at
org.codehaus.mojo.hibernate3.configuration.JDBCComponentConfiguration.doConfiguration(JDBCComponentConfiguration.java:67)
at
org.codehaus.mojo.hibernate3.configuration.AbstractComponentConfiguration.getConfiguration(AbstractComponentConfiguration.java:37)
at
org.codehaus.mojo.hibernate3.exporter.Hbm2DDLExporterMojo.doExecute(Hbm2DDLExporterMojo.java:87)
at
org.codehaus.mojo.hibernate3.HibernateExporterMojo.execute(HibernateExporterMojo.java:140)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:577)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
at
org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
at
org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
at
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:903)
at
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:52)
13:00:21,144 INFO org.hibernate.dialect.Dialect - Using dialect:
org.hibernate.dialect.MySQLDialect
13:00:21,269 INFO org.hibernate.transaction.TransactionFactoryFactory -
Transaction strategy: org.hibernate.transaction.JDBCTransactionFactory
13:00:21,284 INFO org.hibernate.transaction.TransactionManagerLookupFactory -
No TransactionManagerLookup configured (in JTA environment, use of read-write
or transactional second
Re: hibernate3 maven2 plugin problem
Caused by: java.sql.SQLException: No suitable driver
Set Driver_class in hibernate.properties ?
hibernate.connection.driver_class com.mysql.jdbc.Driver
- Original Message -
From: Renu Gupta [EMAIL PROTECTED]
To: Maven Users List users@maven.apache.org
Sent: Monday, July 21, 2008 9:41 AM
Subject: hibernate3 maven2 plugin problem
Hi,
While using hibernate3 maven2 plugin. I m getting this error:
[INFO] [hibernate3:hbm2ddl]
[DEBUG] Setting context classloader for plugin to:
/plugins/org.codehaus.mojo:hibernate3-maven-plugin:[EMAIL
PROTECTED]/thread:main (instance is:
ClassRealm[/plugins/org.codehaus.mojo:hibernate3-maven-plugin:[EMAIL
PROTECTED]/thread:main, parent: ClassRealm[plexus.core, parent: null]])
13:00:20,800 INFO org.hibernate.cfg.Environment - Hibernate 3.2.0.cr5
13:00:20,800 INFO org.hibernate.cfg.Environment - loaded properties from
resource hibernate.properties:
{hibernate.dialect=org.hibernate.dialect.MySQLDialect,
hibernate.bytecode.use_reflection_optimizer=false}
13:00:20,800 INFO org.hibernate.cfg.Environment - Bytecode provider name :
cglib
13:00:20,815 INFO org.hibernate.cfg.Environment - using JDK 1.4
java.sql.Timestamp handling
13:00:20,894 INFO org.hibernate.cfg.Configuration - configuring from file:
hibernate.cfg.xml
[DEBUG] basedir: F:\Documents and
Settings\rvgupta\eclipsemavenworkspace\trial-plugin
[INFO] Configuration XML file loaded: F:\Documents and
Settings\rvgupta\eclipsemavenworkspace\trial-plugin\src\main\resources\hibernate.cfg.xml
13:00:21,050 INFO org.hibernate.cfg.JDBCMetaDataConfiguration - Ignoring null
mapping
13:00:21,050 INFO org.hibernate.cfg.Configuration - Configured SessionFactory:
null
[INFO] src/main/resources/database.properties not found within the project.
Trying absolute path.
[INFO] No hibernate properties file loaded.
13:00:21,097 INFO org.hibernate.connection.DriverManagerConnectionProvider -
Using Hibernate built-in connection pool (not for production use!)
13:00:21,097 INFO org.hibernate.connection.DriverManagerConnectionProvider -
Hibernate connection pool size: 20
13:00:21,097 INFO org.hibernate.connection.DriverManagerConnectionProvider -
autocommit mode: false
13:00:21,097 INFO org.hibernate.connection.DriverManagerConnectionProvider -
using driver: com.mysql.jdbc.Driver at URL:
jdbc:mysql://localhost/firsthibernate
13:00:21,112 INFO org.hibernate.connection.DriverManagerConnectionProvider -
connection properties: {user=root, password=}
13:00:21,112 WARN org.hibernate.cfg.SettingsFactory - Could not obtain
connection metadata
java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getConnection(DriverManager.java:545)
at java.sql.DriverManager.getConnection(DriverManager.java:140)
at
org.hibernate.connection.DriverManagerConnectionProvider.getConnection(DriverManagerConnectionProvider.java:110)
at
org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:76)
at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:1929)
at
org.hibernate.cfg.JDBCMetaDataConfiguration.readFromJDBC(JDBCMetaDataConfiguration.java:38)
at
org.codehaus.mojo.hibernate3.configuration.JDBCComponentConfiguration.doConfiguration(JDBCComponentConfiguration.java:67)
at
org.codehaus.mojo.hibernate3.configuration.AbstractComponentConfiguration.getConfiguration(AbstractComponentConfiguration.java:37)
at
org.codehaus.mojo.hibernate3.exporter.Hbm2DDLExporterMojo.doExecute(Hbm2DDLExporterMojo.java:87)
at
org.codehaus.mojo.hibernate3.HibernateExporterMojo.execute(HibernateExporterMojo.java:140)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:577)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
at
org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
at
org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
at
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:903)
at
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:52)
13:00:21,144 INFO org.hibernate.dialect.Dialect - Using dialect
RE: hibernate3 maven2 plugin problem
Hello Renu
That stills looks that is looking for the JDBC driver. Refer to the bottom
of this page:
http://mojo.codehaus.org/hibernate3/hibernate3-maven-plugin/usage.html
Johann Reyes
-Original Message-
From: Renu Gupta [mailto:[EMAIL PROTECTED]
Sent: Monday, July 21, 2008 6:48 AM
To: Maven Users List
Subject: RE: hibernate3 maven2 plugin problem
Hey thanx for ur help.. :)
But I m still getting error. :(
[DEBUG] Setting context classloader for plugin to:
/plugins/org.codehaus.mojo:hibernate3-maven-plugin:[EMAIL PROTECTED]/thread:mai
n (instance is:
ClassRealm[/plugins/org.codehaus.mojo:hibernate3-maven-plugin:[EMAIL PROTECTED]
/thread:main, parent: ClassRealm[plexus.core, parent: null]])
16:10:24,279 INFO org.hibernate.cfg.Environment - Hibernate 3.2.0.cr5
16:10:24,310 INFO org.hibernate.cfg.Environment - loaded properties from
resource hibernate.properties:
{hibernate.dialect=org.hibernate.dialect.MySQLDialect,
hibernate.bytecode.use_reflection_optimizer=false,
hibernate.connection.driver_class=com.mysql.jdbc.Driver}
16:10:24,310 INFO org.hibernate.cfg.Environment - Bytecode provider name :
cglib
16:10:24,342 INFO org.hibernate.cfg.Environment - using JDK 1.4
java.sql.Timestamp handling
[DEBUG] basedir: F:\Documents and
Settings\rvgupta\eclipsemavenworkspace\trial-plugin
16:10:24,795 INFO org.hibernate.cfg.Configuration - configuring from file:
hibernate.cfg.xml
[INFO] Configuration XML file loaded: F:\Documents and
Settings\rvgupta\eclipsemavenworkspace\trial-plugin\src\main\resources\hiber
nate.cfg.xml
16:10:25,201 INFO org.hibernate.cfg.JDBCMetaDataConfiguration - Ignoring
null mapping
16:10:25,201 INFO org.hibernate.cfg.Configuration - Configured
SessionFactory: null
[INFO] src/main/resources/database.properties not found within the project.
Trying absolute path.
[INFO] No hibernate properties file loaded.
16:10:25,326 INFO org.hibernate.connection.DriverManagerConnectionProvider
- Using Hibernate built-in connection pool (not for production use!)
16:10:25,326 INFO org.hibernate.connection.DriverManagerConnectionProvider
- Hibernate connection pool size: 20
16:10:25,326 INFO org.hibernate.connection.DriverManagerConnectionProvider
- autocommit mode: false
16:10:25,373 INFO org.hibernate.connection.DriverManagerConnectionProvider
- using driver: com.mysql.jdbc.Driver at URL:
jdbc:mysql://localhost/firsthibernate
16:10:25,373 INFO org.hibernate.connection.DriverManagerConnectionProvider
- connection properties: {user=root, password=}
16:10:25,389 WARN org.hibernate.cfg.SettingsFactory - Could not obtain
connection metadata
java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getConnection(DriverManager.java:545)
at java.sql.DriverManager.getConnection(DriverManager.java:140)
at
org.hibernate.connection.DriverManagerConnectionProvider.getConnection(Drive
rManagerConnectionProvider.java:110)
at
org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:76)
at
org.hibernate.cfg.Configuration.buildSettings(Configuration.java:1929)
at
org.hibernate.cfg.JDBCMetaDataConfiguration.readFromJDBC(JDBCMetaDataConfigu
ration.java:38)
at
org.codehaus.mojo.hibernate3.configuration.JDBCComponentConfiguration.doConf
iguration(JDBCComponentConfiguration.java:67)
at
org.codehaus.mojo.hibernate3.configuration.AbstractComponentConfiguration.ge
tConfiguration(AbstractComponentConfiguration.java:37)
at
org.codehaus.mojo.hibernate3.exporter.Hbm2DDLExporterMojo.doExecute(Hbm2DDLE
xporterMojo.java:87)
at
org.codehaus.mojo.hibernate3.HibernateExporterMojo.execute(HibernateExporter
Mojo.java:140)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManage
r.java:577)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail
ures(DefaultLifecycleExecutor.java:498)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForPro
ject(DefaultLifecycleExecutor.java:265)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Defa
ultLifecycleExecutor.java:191)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle
Executor.java:149)
at
org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
at
org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:3
04)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
at
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.ja
va:903)
at
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbe
dder.java:304)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:52)
16
RE: hibernate3 maven2 plugin problem
Hey Johann,
Thanx for ur help :)
It worked out.But, for ur knowledge I didn't had to add any extension tag in my
pom.
Just had to add mysql java connector dependency in plugin.
Here is my pom:
project xmlns=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;
modelVersion4.0.0/modelVersion
groupIdhibernate/groupId
artifactIdtrial-plugin/artifactId
packagingmaven-plugin/packaging
version0.0.1-SNAPSHOT/version
nametrial-plugin Maven Mojo/name
urlhttp://maven.apache.org/url
dependencies
dependency
groupIdorg.apache.maven/groupId
artifactIdmaven-plugin-api/artifactId
version2.0/version
/dependency
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version3.8.1/version
scopetest/scope
/dependency
/dependencies
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdhibernate3-maven-plugin/artifactId
version2.0-alpha-2/version
configuration
verbosetrue/verbose
components
component
namehbm2ddl/name
implementationjdbcconfiguration/implementation
/component
component
namehbm2hbmxml/name
outputDirectorysrc/main/resources/outputDirectory
/component
/components
componentProperties
droptrue/drop
configurationfile/src/main/resources/hibernate.cfg.xml/configurationfile
/componentProperties
/configuration
dependencies
dependency
groupIdmysql/groupId
artifactIdmysql-connector-java/artifactId
version5.0.5/version
/dependency
/dependencies
/plugin
/plugins
/build
/project
And I executed the goal: mvn hibernate3:hbm2ddl
And it created corresponding table in my database.
Cheers!
Renu
-Original Message-
From: Johann Reyes [mailto:[EMAIL PROTECTED]
Sent: Monday, July 21, 2008 5:49 PM
To: 'Maven Users List'
Subject: RE: hibernate3 maven2 plugin problem
Hello Renu
That stills looks that is looking for the JDBC driver. Refer to the bottom
of this page:
http://mojo.codehaus.org/hibernate3/hibernate3-maven-plugin/usage.html
Johann Reyes
-Original Message-
From: Renu Gupta [mailto:[EMAIL PROTECTED]
Sent: Monday, July 21, 2008 6:48 AM
To: Maven Users List
Subject: RE: hibernate3 maven2 plugin problem
Hey thanx for ur help.. :)
But I m still getting error. :(
[DEBUG] Setting context classloader for plugin to:
/plugins/org.codehaus.mojo:hibernate3-maven-plugin:[EMAIL PROTECTED]/thread:mai
n (instance is:
ClassRealm[/plugins/org.codehaus.mojo:hibernate3-maven-plugin:[EMAIL PROTECTED]
/thread:main, parent: ClassRealm[plexus.core, parent: null]])
16:10:24,279 INFO org.hibernate.cfg.Environment - Hibernate 3.2.0.cr5
16:10:24,310 INFO org.hibernate.cfg.Environment - loaded properties from
resource hibernate.properties:
{hibernate.dialect=org.hibernate.dialect.MySQLDialect,
hibernate.bytecode.use_reflection_optimizer=false,
hibernate.connection.driver_class=com.mysql.jdbc.Driver}
16:10:24,310 INFO org.hibernate.cfg.Environment - Bytecode provider name :
cglib
16:10:24,342 INFO org.hibernate.cfg.Environment - using JDK 1.4
java.sql.Timestamp handling
[DEBUG] basedir: F:\Documents and
Settings\rvgupta\eclipsemavenworkspace\trial-plugin
16:10:24,795 INFO org.hibernate.cfg.Configuration - configuring from file:
hibernate.cfg.xml
[INFO] Configuration XML file loaded: F:\Documents and
Settings\rvgupta\eclipsemavenworkspace\trial-plugin\src\main\resources\hiber
nate.cfg.xml
16:10:25,201 INFO org.hibernate.cfg.JDBCMetaDataConfiguration - Ignoring
null mapping
16:10:25,201 INFO org.hibernate.cfg.Configuration - Configured
SessionFactory: null
[INFO] src/main/resources/database.properties not found within the project.
Trying absolute path.
[INFO] No hibernate properties file loaded.
16:10:25,326 INFO org.hibernate.connection.DriverManagerConnectionProvider
- Using Hibernate built-in connection pool (not for production use!)
16:10:25,326 INFO org.hibernate.connection.DriverManagerConnectionProvider
- Hibernate connection pool size: 20
16:10:25,326 INFO org.hibernate.connection.DriverManagerConnectionProvider
- autocommit mode: false
16:10:25,373 INFO org.hibernate.connection.DriverManagerConnectionProvider
- using driver: com.mysql.jdbc.Driver at URL:
jdbc:mysql://localhost/firsthibernate
16:10:25,373 INFO org.hibernate.connection.DriverManagerConnectionProvider
- connection properties: {user=root, password=}
16:10:25,389 WARN org.hibernate.cfg.SettingsFactory - Could not obtain
connection metadata
java.sql.SQLException: No suitable driver
RE: hibernate3 maven2 plugin problem
Hello Renu
Yes, that's correct. That's another way, I just posted the form that was
documented in the site.
Regards
Johann
-Original Message-
From: Renu Gupta [mailto:[EMAIL PROTECTED]
Sent: Monday, July 21, 2008 9:32 AM
To: Maven Users List
Subject: RE: hibernate3 maven2 plugin problem
Hey Johann,
Thanx for ur help :)
It worked out.But, for ur knowledge I didn't had to add any extension tag in
my pom.
Just had to add mysql java connector dependency in plugin.
Here is my pom:
project xmlns=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;
modelVersion4.0.0/modelVersion
groupIdhibernate/groupId
artifactIdtrial-plugin/artifactId
packagingmaven-plugin/packaging
version0.0.1-SNAPSHOT/version
nametrial-plugin Maven Mojo/name
urlhttp://maven.apache.org/url
dependencies
dependency
groupIdorg.apache.maven/groupId
artifactIdmaven-plugin-api/artifactId
version2.0/version
/dependency
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version3.8.1/version
scopetest/scope
/dependency
/dependencies
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdhibernate3-maven-plugin/artifactId
version2.0-alpha-2/version
configuration
verbosetrue/verbose
components
component
namehbm2ddl/name
implementationjdbcconfiguration/implementation
/component
component
namehbm2hbmxml/name
outputDirectorysrc/main/resources/outputDirectory
/component
/components
componentProperties
droptrue/drop
configurationfile/src/main/resources/hibernate.cfg.xml/configurationfile
/componentProperties
/configuration
dependencies
dependency
groupIdmysql/groupId
artifactIdmysql-connector-java/artifactId
version5.0.5/version
/dependency
/dependencies
/plugin
/plugins
/build
/project
And I executed the goal: mvn hibernate3:hbm2ddl
And it created corresponding table in my database.
Cheers!
Renu
-Original Message-
From: Johann Reyes [mailto:[EMAIL PROTECTED]
Sent: Monday, July 21, 2008 5:49 PM
To: 'Maven Users List'
Subject: RE: hibernate3 maven2 plugin problem
Hello Renu
That stills looks that is looking for the JDBC driver. Refer to the bottom
of this page:
http://mojo.codehaus.org/hibernate3/hibernate3-maven-plugin/usage.html
Johann Reyes
-Original Message-
From: Renu Gupta [mailto:[EMAIL PROTECTED]
Sent: Monday, July 21, 2008 6:48 AM
To: Maven Users List
Subject: RE: hibernate3 maven2 plugin problem
Hey thanx for ur help.. :)
But I m still getting error. :(
[DEBUG] Setting context classloader for plugin to:
/plugins/org.codehaus.mojo:hibernate3-maven-plugin:[EMAIL PROTECTED]/thread:mai
n (instance is:
ClassRealm[/plugins/org.codehaus.mojo:hibernate3-maven-plugin:[EMAIL PROTECTED]
/thread:main, parent: ClassRealm[plexus.core, parent: null]])
16:10:24,279 INFO org.hibernate.cfg.Environment - Hibernate 3.2.0.cr5
16:10:24,310 INFO org.hibernate.cfg.Environment - loaded properties from
resource hibernate.properties:
{hibernate.dialect=org.hibernate.dialect.MySQLDialect,
hibernate.bytecode.use_reflection_optimizer=false,
hibernate.connection.driver_class=com.mysql.jdbc.Driver}
16:10:24,310 INFO org.hibernate.cfg.Environment - Bytecode provider name :
cglib
16:10:24,342 INFO org.hibernate.cfg.Environment - using JDK 1.4
java.sql.Timestamp handling
[DEBUG] basedir: F:\Documents and
Settings\rvgupta\eclipsemavenworkspace\trial-plugin
16:10:24,795 INFO org.hibernate.cfg.Configuration - configuring from file:
hibernate.cfg.xml
[INFO] Configuration XML file loaded: F:\Documents and
Settings\rvgupta\eclipsemavenworkspace\trial-plugin\src\main\resources\hiber
nate.cfg.xml
16:10:25,201 INFO org.hibernate.cfg.JDBCMetaDataConfiguration - Ignoring
null mapping
16:10:25,201 INFO org.hibernate.cfg.Configuration - Configured
SessionFactory: null
[INFO] src/main/resources/database.properties not found within the project.
Trying absolute path.
[INFO] No hibernate properties file loaded.
16:10:25,326 INFO org.hibernate.connection.DriverManagerConnectionProvider
- Using Hibernate built-in connection pool (not for production use!)
16:10:25,326 INFO org.hibernate.connection.DriverManagerConnectionProvider
- Hibernate connection pool size: 20
16:10:25,326 INFO org.hibernate.connection.DriverManagerConnectionProvider
- autocommit mode: false
16:10:25,373 INFO org.hibernate.connection.DriverManagerConnectionProvider
- using driver: com.mysql.jdbc.Driver at URL:
jdbc:mysql://localhost/firsthibernate
16:10:25,373 INFO
Hibernate maven2 Plugin
Hi, I m new to hibernate maven2 plugin. Since I haven't developed any thing in this. And unfortunately googling is not of much help... :( Can anyone tell me how to start from?// Any reference or tutorial would be appreciable... Regards, Renu Gupta Impetus Infotech Pvt Ltd 14-B, Sangam House,Palasia A.B. Road,Indore - 452001 Phone: 0731-4269200-4693
Re: [Update]Findbugs Maven2 Plugin future direction
All respondents to the survey picked option 2 but upon discussion with another Maven committer we are going to do the first option. This is because the minimum version requirement for Plugin in the Apache and Codehaus is Java 1.4. Here is the plan of action: 1. Change the 1.2-Snapshot to use Findbugs 1.2.1 which uses Java 1.4 as a minimum. This will be the final version of the Findbugs plugin for Java 1.4. The only changes will be bug fixes. 2. Submit a vote request for the release of the Findbugs 1.2 plugin release. 3. Create a 2.0-SNAPSHOT of the Findbugs plugin that uses Findbugs 1.3.2 and requires Java 5 as a minimum to run. 4. Submit a vote request for the release of the Findbugs 2.0 plugin release. Regards, Garvin LeClaire [EMAIL PROTECTED] Garvin LeClaire wrote: The current version of the Maven2 FindBug plugin (1.1.1) uses Findbugs 1.2.0 and the 1.2-SNAPSHOT version uses Findbugs 1.2. Since Maven2 requires as a minimum Java 1.4 to run and Findbugs 1.3.x requires Java 5 I think we at at a fork in the rode where I would like some feedback from users. [] Release Maven2 Findbugs Plugin 1.2.0 using Findbugs 1.2.1. All subsequent releases will use Findbugs 1.3.x and require Java 5 to run. No new enhancements, features or bug fixes will be put into the Maven2 Findbugs Plugin 1.2.0 version. I can still analyze byte code compile for Java 1.4 [] Release Maven2 Findbugs Plugin 1.2.0 using Findbugs 1.3.x and require Java 5 to run. [] Create and maintain two versions of the Maven2 Findbugs Plugin with one using Findbugs 1.2.1 requiring Java 1.4 as a minimum and another using Findbugs 1.3.x and requiring Java 5 to run. The two version would have the same bug fixes and enhancements where possible. Regards, Garvin LeClaire [EMAIL PROTECTED]
Re: Findbug's Maven2 Plugin future direction
And the winner (and only on that got votes) is. Release Maven2 Findbugs Plugin 1.2.0 using Findbugs 1.3.x and require Java 5 to run. I update the snapshot and let others test it as I and others at my company have been using the new version for a couple of weeks. I will call for a vote to do a release after the weekend if there are not any bugs reported. Regards, Garvin LeClaire [EMAIL PROTECTED] Garvin LeClaire wrote: The current version of the Maven2 FindBug plugin (1.1.1) uses Findbugs 1.2.0 and the 1.2-SNAPSHOT version uses Findbugs 1.2. Since Maven2 requires as a minimum Java 1.4 to run and Findbugs 1.3.x requires Java 5 I think we at at a fork in the rode where I would like some feedback from users. [] Release Maven2 Findbugs Plugin 1.2.0 using Findbugs 1.2.1. All subsequent releases will use Findbugs 1.3.x and require Java 5 to run. No new enhancements, features or bug fixes will be put into the Maven2 Findbugs Plugin 1.2.0 version. I can still analyze byte code compile for Java 1.4 [] Release Maven2 Findbugs Plugin 1.2.0 using Findbugs 1.3.x and require Java 5 to run. [] Create and maintain two versions of the Maven2 Findbugs Plugin with one using Findbugs 1.2.1 requiring Java 1.4 as a minimum and another using Findbugs 1.3.x and requiring Java 5 to run. The two version would have the same bug fixes and enhancements where possible. Regards, Garvin LeClaire [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Findbug's Maven2 Plugin future direction
[x] Release Maven2 Findbugs Plugin 1.2.0 using Findbugs 1.3.x and require Java 5 to run. -- GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen! Jetzt dabei sein: http://www.shortview.de/[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Findbug's Maven2 Plugin future direction
[x] Release Maven2 Findbugs Plugin 1.2.0 using Findbugs 1.3.x and require Java 5 to run.
Re: Findbug's Maven2 Plugin future direction
last one release 1.2, branch it, then release 2.0 on trunk -D On Fri, Mar 14, 2008 at 12:19 AM, Emmanuel Hugonnet [EMAIL PROTECTED] wrote: [x] Release Maven2 Findbugs Plugin 1.2.0 using Findbugs 1.3.x and require Java 5 to run. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Findbug's Maven2 Plugin future direction
I agree with Dan. It's better to keep a branch for the jdk 1.4 in case for legacy systems. I f we found a bug in the plugin it's better to be able to load a jira and fix it. +1 to use Findbugs 1.3.x and require Java 5 to run for the trunk Rémy 2008/3/14, Dan Tran [EMAIL PROTECTED]: last one release 1.2, branch it, then release 2.0 on trunk -D
Re: Findbug's Maven2 Plugin future direction
However, I would add a check that won't try and run findbugs if maven is started with jdk 1.4... have it instead print diagnostic information or a friendly error message to let people know that JDK 5.0 is required or else that they should use the 1.2 branch version On Fri, Mar 14, 2008 at 8:58 AM, Rémy Sanlaville [EMAIL PROTECTED] wrote: I agree with Dan. It's better to keep a branch for the jdk 1.4 in case for legacy systems. I f we found a bug in the plugin it's better to be able to load a jira and fix it. +1 to use Findbugs 1.3.x and require Java 5 to run for the trunk Rémy 2008/3/14, Dan Tran [EMAIL PROTECTED]: last one release 1.2, branch it, then release 2.0 on trunk -D
Re: Findbug's Maven2 Plugin future direction
2008/3/14, Stephen Connolly [EMAIL PROTECTED]: However, I would add a check that won't try and run findbugs if maven is started with jdk 1.4... have it instead print diagnostic information or a friendly error message to let people know that JDK 5.0 is required or else that they should use the 1.2 branch version Agree, it would be nice to have this check (perhaps via the maven-enforcer-plugin) and have an error message when the check failed. Rémy
RE: [FB-Discuss] Findbug's Maven2 Plugin future direction
By all means, do option 2. Update the plugin for Findbugs 1.3.x/Java 5. Burn the ships. Don Kautz -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Garvin LeClaire Sent: Thursday, March 13, 2008 8:51 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; users@maven.apache.org Subject: [FB-Discuss] Findbug's Maven2 Plugin future direction The current version of the Maven2 FindBug plugin (1.1.1) uses Findbugs 1.2.0 and the 1.2-SNAPSHOT version uses Findbugs 1.2. Since Maven2 requires as a minimum Java 1.4 to run and Findbugs 1.3.x requires Java 5 I think we at at a fork in the rode where I would like some feedback from users. [] Release Maven2 Findbugs Plugin 1.2.0 using Findbugs 1.2.1. All subsequent releases will use Findbugs 1.3.x and require Java 5 to run. No new enhancements, features or bug fixes will be put into the Maven2 Findbugs Plugin 1.2.0 version. I can still analyze byte code compile for Java 1.4 [] Release Maven2 Findbugs Plugin 1.2.0 using Findbugs 1.3.x and require Java 5 to run. [] Create and maintain two versions of the Maven2 Findbugs Plugin with one using Findbugs 1.2.1 requiring Java 1.4 as a minimum and another using Findbugs 1.3.x and requiring Java 5 to run. The two version would have the same bug fixes and enhancements where possible. Regards, Garvin LeClaire [EMAIL PROTECTED] ___ Findbugs-discuss mailing list [EMAIL PROTECTED] http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [FB-Discuss] Findbug's Maven2 Plugin future direction
[X] Create and maintain two versions of the Maven2 Findbugs Plugin Raphaël 2008/3/14, Kautz, Don [EMAIL PROTECTED]: By all means, do option 2. Update the plugin for Findbugs 1.3.x/Java 5. Burn the ships. Don Kautz -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Garvin LeClaire Sent: Thursday, March 13, 2008 8:51 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; users@maven.apache.org Subject: [FB-Discuss] Findbug's Maven2 Plugin future direction The current version of the Maven2 FindBug plugin (1.1.1) uses Findbugs 1.2.0 and the 1.2-SNAPSHOT version uses Findbugs 1.2. Since Maven2 requires as a minimum Java 1.4 to run and Findbugs 1.3.x requires Java 5 I think we at at a fork in the rode where I would like some feedback from users. [] Release Maven2 Findbugs Plugin 1.2.0 using Findbugs 1.2.1. All subsequent releases will use Findbugs 1.3.x and require Java 5 to run. No new enhancements, features or bug fixes will be put into the Maven2 Findbugs Plugin 1.2.0 version. I can still analyze byte code compile for Java 1.4 [] Release Maven2 Findbugs Plugin 1.2.0 using Findbugs 1.3.x and require Java 5 to run. [] Create and maintain two versions of the Maven2 Findbugs Plugin with one using Findbugs 1.2.1 requiring Java 1.4 as a minimum and another using Findbugs 1.3.x and requiring Java 5 to run. The two version would have the same bug fixes and enhancements where possible. Regards, Garvin LeClaire [EMAIL PROTECTED] ___ Findbugs-discuss mailing list [EMAIL PROTECTED] http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Findbug's Maven2 Plugin future direction
Could retroweaver be used here? http://retroweaver.sourceforge.net/ Regards, Matt Garvin LeClaire wrote: The current version of the Maven2 FindBug plugin (1.1.1) uses Findbugs 1.2.0 and the 1.2-SNAPSHOT version uses Findbugs 1.2. Since Maven2 requires as a minimum Java 1.4 to run and Findbugs 1.3.x requires Java 5 I think we at at a fork in the rode where I would like some feedback from users. [] Release Maven2 Findbugs Plugin 1.2.0 using Findbugs 1.2.1. All subsequent releases will use Findbugs 1.3.x and require Java 5 to run. No new enhancements, features or bug fixes will be put into the Maven2 Findbugs Plugin 1.2.0 version. I can still analyze byte code compile for Java 1.4 [] Release Maven2 Findbugs Plugin 1.2.0 using Findbugs 1.3.x and require Java 5 to run. [] Create and maintain two versions of the Maven2 Findbugs Plugin with one using Findbugs 1.2.1 requiring Java 1.4 as a minimum and another using Findbugs 1.3.x and requiring Java 5 to run. The two version would have the same bug fixes and enhancements where possible. Regards, Garvin LeClaire [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ This e-mail has been scanned for viruses by MessageLabs. -- Matt J. Gumbley Senior Java Developer, Development Team Lead Inspired Gaming UK 2-4 Bucknall Street London WC2H 8LA Tel: +44 (0)20 7438 5849 Fax: +44 (0)20 7240 1302 Mob: +44 (0)7711 311 943 (Private) Yahoo!: mattgumbley Skype: MattJGumbley http://www.ingg.com ** Confidentiality : This e-mail and any attachments are intended for the addressee only and may be confidential. If they come to you in error you must take no action based on them, nor must you copy or show them to anyone. Please advise the sender by replying to this e-mail immediately and then delete the original from your computer. Opinion : Any opinions expressed in this e-mail are entirely those of the author and unless specifically stated to the contrary, are not necessarily those of the authors employer. Security Warning : Internet e-mail is not necessarily a secure communications medium and can be subject to data corruption. We advise that you consider this fact when e-mailing us. Viruses : We have taken steps to ensure that this e-mail and any attachments are free from known viruses but in keeping with good computing practice, you should ensure that they are virus free. Inspired Gaming (UK) Limited Registered in England No 3565640 Registered Office 3 The Maltings Wetmore Road, Burton On Trent, Staffordshire DE14 1SE ___ This message has been checked for all known viruses by the MessageLabs Virus Control Centre. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [FB-Discuss] Findbug's Maven2 Plugin future direction
On Thu, Mar 13, 2008 at 08:51:16PM -0400, Garvin LeClaire wrote: [] Release Maven2 Findbugs Plugin 1.2.0 using Findbugs 1.3.x and require Java 5 to run. I think this would be a sensible thing to do: for those few unlucky ones who still use java4 not only in production but also exclusively on their development/CI machines, the current plugin should be pretty functional. Arnout - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Findbug's Maven2 Plugin future direction
The current version of the Maven2 FindBug plugin (1.1.1) uses Findbugs 1.2.0 and the 1.2-SNAPSHOT version uses Findbugs 1.2. Since Maven2 requires as a minimum Java 1.4 to run and Findbugs 1.3.x requires Java 5 I think we at at a fork in the rode where I would like some feedback from users. [] Release Maven2 Findbugs Plugin 1.2.0 using Findbugs 1.2.1. All subsequent releases will use Findbugs 1.3.x and require Java 5 to run. No new enhancements, features or bug fixes will be put into the Maven2 Findbugs Plugin 1.2.0 version. I can still analyze byte code compile for Java 1.4 [] Release Maven2 Findbugs Plugin 1.2.0 using Findbugs 1.3.x and require Java 5 to run. [] Create and maintain two versions of the Maven2 Findbugs Plugin with one using Findbugs 1.2.1 requiring Java 1.4 as a minimum and another using Findbugs 1.3.x and requiring Java 5 to run. The two version would have the same bug fixes and enhancements where possible. Regards, Garvin LeClaire [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Findbug's Maven2 Plugin future direction
[X] Release Maven2 Findbugs Plugin 1.2.0 using Findbugs 1.3.x and require Java 5 to run. On Fri, Mar 14, 2008 at 8:51 AM, Garvin LeClaire [EMAIL PROTECTED] wrote: The current version of the Maven2 FindBug plugin (1.1.1) uses Findbugs 1.2.0 and the 1.2-SNAPSHOT version uses Findbugs 1.2. Since Maven2 requires as a minimum Java 1.4 to run and Findbugs 1.3.x requires Java 5 I think we at at a fork in the rode where I would like some feedback from users. [] Release Maven2 Findbugs Plugin 1.2.0 using Findbugs 1.2.1. All subsequent releases will use Findbugs 1.3.x and require Java 5 to run. No new enhancements, features or bug fixes will be put into the Maven2 Findbugs Plugin 1.2.0 version. I can still analyze byte code compile for Java 1.4 [] Release Maven2 Findbugs Plugin 1.2.0 using Findbugs 1.3.x and require Java 5 to run. [] Create and maintain two versions of the Maven2 Findbugs Plugin with one using Findbugs 1.2.1 requiring Java 1.4 as a minimum and another using Findbugs 1.3.x and requiring Java 5 to run. The two version would have the same bug fixes and enhancements where possible. Regards, Garvin LeClaire [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Eclipse Maven2 Plugin
1) Set localRepository[path-to-your-local-repo]/localRepository in [your-maven-install-dir]/conf/settings.xml 2) Make sure that you remove your ~/.m2 directory 3) Add the M2_REPO: mvn -Declipse.workspace=path-to-eclipse-workspace eclipse:add-maven-repo 4) mvn eclipse:clean eclipse:eclipse 5) Read http://maven.apache.org/plugins/maven-eclipse-plugin/usage.html -Original Message- From: Oren Livne [mailto:[EMAIL PROTECTED] Sent: Friday, December 21, 2007 5:24 PM To: users@maven.apache.org Subject: Eclipse Maven2 Plugin Dear All, I am using the Maven 2 integration for Eclipse, http://m2eclipse.codehaus.org/ I am trying to set a custom path for my local maven repository. I went to Windows-Preferences -Maven 2 and set it there, but it doesn't have any effect and still uses ~/.m2/repository. My command line maven is configured through MAVEN_HOME/conf/settings.xml to go to a custom folder, and that works. How can I tell MyEclipse (or Eclipse for this matter) to use the same folder? Otherwise I might run into directory differences between different windows machines that I use MyEclipse on. Thanks so much, Oren -- === PERSISTENT, adj. Remaining infective for a relatively long time in a vector after an initial period of incubation. -- Meriam-Webster Dictionary --- Oren Livne, Ph.D. RUReady Software Architect Academic Outreach and Continuing Education, 1901 E South Campus Dr. Room 2197-D, University of Utah, Salt Lake City, UT 84112-9399 Tel : (801) 581-6831 Cell: (801) 631-3885 Fax: (801) 585-5414 Email: [EMAIL PROTECTED] Web: http://ruready.net/oren === - 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 Maven2 Plugin
Hi, 5) Read http://maven.apache.org/plugins/maven-eclipse-plugin/usage.html afaik is m2eclipse != maven-eclipse-plugin. Jan -- Please try to use a nice quotation your mails and posts - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: RE: Eclipse Maven2 Plugin
Right, but you can use maven-eclipse-plugin to create an eclipse project that is ready to use m2eclipse: http://maven.apache.org/plugins/maven-eclipse-plugin/m2eclipse-mojo.html -Original Message- From: news [mailto:[EMAIL PROTECTED] Behalf Of Jan Torben Heuer Sent: Monday, December 24, 2007 11:22 AM To: users@maven.apache.org Subject: RE: Eclipse Maven2 Plugin Hi, 5) Read http://maven.apache.org/plugins/maven-eclipse-plugin/usage.html afaik is m2eclipse != maven-eclipse-plugin. Jan -- Please try to use a nice quotation your mails and posts - 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 Maven2 Plugin
Hi, There is a separate mailing list for the m2eclipse plugin. You should probably try that mailing list to get a quicker reponse. Oren Livne wrote: Dear All, I am using the Maven 2 integration for Eclipse, http://m2eclipse.codehaus.org/ I am trying to set a custom path for my local maven repository. I went to Windows-Preferences -Maven 2 and set it there, but it doesn't have any effect and still uses ~/.m2/repository. My command line maven is configured through MAVEN_HOME/conf/settings.xml to go to a custom folder, and that works. How can I tell MyEclipse (or Eclipse for this matter) to use the same folder? Otherwise I might run into directory differences between different windows machines that I use MyEclipse on. Thanks so much, Oren -- === PERSISTENT, adj. Remaining infective for a relatively long time in a vector after an initial period of incubation. -- Meriam-Webster Dictionary --- Oren Livne, Ph.D. RUReady Software Architect Academic Outreach and Continuing Education, 1901 E South Campus Dr. Room 2197-D, University of Utah, Salt Lake City, UT 84112-9399 Tel : (801) 581-6831 Cell: (801) 631-3885 Fax: (801) 585-5414 Email: [EMAIL PROTECTED] Web: http://ruready.net/oren === - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Eclipse-Maven2-Plugin-tp14463522s177p14473154.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Eclipse Maven2 Plugin
Dear All, I am using the Maven 2 integration for Eclipse, http://m2eclipse.codehaus.org/ I am trying to set a custom path for my local maven repository. I went to Windows-Preferences -Maven 2 and set it there, but it doesn't have any effect and still uses ~/.m2/repository. My command line maven is configured through MAVEN_HOME/conf/settings.xml to go to a custom folder, and that works. How can I tell MyEclipse (or Eclipse for this matter) to use the same folder? Otherwise I might run into directory differences between different windows machines that I use MyEclipse on. Thanks so much, Oren -- === PERSISTENT, adj. Remaining infective for a relatively long time in a vector after an initial period of incubation. -- Meriam-Webster Dictionary --- Oren Livne, Ph.D. RUReady Software Architect Academic Outreach and Continuing Education, 1901 E South Campus Dr. Room 2197-D, University of Utah, Salt Lake City, UT 84112-9399 Tel : (801) 581-6831 Cell: (801) 631-3885 Fax: (801) 585-5414 Email: [EMAIL PROTECTED] Web: http://ruready.net/oren === - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 plugin development] classpath management
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: maven2 plugin
On 9/11/07, Roy van der Kuil [EMAIL PROTECTED] wrote:
Hi,
For internal use at our company I have written a small maven plugin that
uses a configuration similar to:
pom
blablabla
configuration
myobjects
myobject
namea_name/name
type
namea_type/name
/type
/myobject
myobject
namea_name2/name
type
namea_type2/name
/type
/myobject
/myobjects
/configuration
/configuration
With matching javacode:
public class MyobjectsMojo extends AbstractMojo {
}
Hmm.. tab-enter is not a good idea in a browser :)
Here is more javacode:
public class MyobjectsMojo extends AbstractMojo {
private MyObject[] myobjects[]
}
public class Type {
private String name;
}
Everything works fine with maven2.x up to 2.0.4. After that.. it simply
fails to find the configuration for myobjects. Is there any way I can find
out why it fails to map? I have tried mvn -e but no errors at all..
Thanks for your help,
Roy
maven2 plugin
Hi,
For internal use at our company I have written a small maven plugin that
uses a configuration similar to:
pom
blablabla
configuration
myobjects
myobject
namea_name/name
type
namea_type/name
/type
/myobject
myobject
namea_name2/name
type
namea_type2/name
/type
/myobject
/myobjects
/configuration
/configuration
With matching javacode:
public class MyobjectsMojo extends AbstractMojo {
}
issue with cobertura / maven2 plugin build
Greetings: I'm using jdk 1.5 cobertura 1.7 cobertura-maven-plugin 2.0 (because of the 2.1 100% complete) error I am using these 2 dependencies. dependency groupIdorg.codehaus.mojo/groupId artifactIdcobertura-maven-plugin/artifactId version2.0/version /dependency dependency groupIdcobertura/groupId artifactIdcobertura/artifactId version1.7/version /dependency I am using this build plugin: plugin groupIdorg.codehaus.mojo/groupId artifactIdcobertura-maven-plugin/artifactId executions execution goals goalclean/goal /goals /execution /executions /plugin I am using this reporting plugin: reporting plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdcobertura-maven-plugin/artifactId version2.0/version /plugin /plugins /reporting When I run the mvn cobertura:cobertura target I get the following error: [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'cobertura'. [INFO] org.apache.maven.plugins: checking for updates from com.eb [INFO] org.codehaus.mojo: checking for updates from com.eb [INFO] artifact org.codehaus.mojo:cobertura-maven-plugin: checking for updates from com.eb [INFO] [INFO] Building eb [INFO]task-segment: [clean, cobertura:cobertura] [INFO] [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for updates from com.eb [INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking for updates from com.eb [INFO] clean:clean [INFO] Deleting directory C:\Documents and Settings\eb\My Documents\workspace\eb\target [INFO] Deleting directory C:\Documents and Settings\eb\My Documents\workspace\eb\target\classes [INFO] Deleting directory C:\Documents and Settings\eb\My Documents\workspace\eb\target\test-classes [ERROR] project-execute : com.eb:eb:war:1.0.0.0-SNAPSHOT ( task-segment: [clean, cobertura:cobertura] ) Diagnosis: Error configuring: org.codehaus.mojo:cobertura-maven-plugin. Reason: Unable to parse the created DOM for plugin configuration FATAL ERROR: Error executing Maven for a project [ERROR] reactor-execute : C:\Documents and Settings\eb\My Documents\workspace\eb Diagnosis: Error configuring: org.codehaus.mojo:cobertura-maven-plugin. Reason: Unable to parse the created DOM for plugin configuration FATAL ERROR: Error executing Maven for a project [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to configure plugin parameters for: org.codehaus.mojo:cobertura-maven-plugin:2.1 on the command line, specify: '-Dcheck=VALUE' Cause: Class name which was explicitly given in configuration using 'implementation' attribute: 'org.codehaus.mojo.cobertura.configuration.ConfigCheck' cannot be loaded [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Wed Jun 13 09:49:06 CDT 2007 [INFO] Final Memory: 3M/6M [INFO] [INFO] Error for project: eb (during clean) [INFO] [INFO] Failed to configure plugin parameters for: org.codehaus.mojo:cobertura-maven-plugin:2.1 on the command line, specify: '-Dcheck=VALUE' Cause: Class name which was explicitly given in configuration using 'implementation' attribute: 'org.codehaus.mojo.cobertura.configuration.ConfigCheck' cannot be loaded [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [ERROR] reactor-execute : C:\Documents and Settings\eb\My Documents\workspace\eb FATAL ERROR: Error executing Maven for a project [INFO] BUILD ERRORS [INFO] [INFO] Total time: 1 second [INFO] Finished at: Wed Jun 13 09:49:06 CDT 2007 [INFO] Final Memory: 3M/6M [INFO] Does anyone here know how to fix this? Thanks. Bill. -- View this message in context: http://www.nabble.com/issue-with-cobertura---maven2--plugin-build-tf3915408s177.html#a11101878 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: issue with cobertura / maven2 plugin build
/issue-with-cobertura---maven2--plugin-build-tf3915408s177.html#a11101878 Sent from the Maven - Users mailing list archive at Nabble.com. - 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: issue with cobertura / maven2 plugin build
[INFO] Deleting directory C:\Documents and Settings\eb\My Documents\workspace\eb\target\classes [INFO] Deleting directory C:\Documents and Settings\eb\My Documents\workspace\eb\target\test-classes [ERROR] project-execute : com.eb:eb:war:1.0.0.0-SNAPSHOT ( task-segment: [clean, cobertura:cobertura] ) Diagnosis: Error configuring: org.codehaus.mojo:cobertura-maven-plugin. Reason: Unable to parse the created DOM for plugin configuration FATAL ERROR: Error executing Maven for a project [ERROR] reactor-execute : C:\Documents and Settings\eb\My Documents\workspace\eb Diagnosis: Error configuring: org.codehaus.mojo:cobertura-maven-plugin. Reason: Unable to parse the created DOM for plugin configuration FATAL ERROR: Error executing Maven for a project [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to configure plugin parameters for: org.codehaus.mojo:cobertura-maven-plugin:2.1 on the command line, specify: '-Dcheck=VALUE' Cause: Class name which was explicitly given in configuration using 'implementation' attribute: 'org.codehaus.mojo.cobertura.configuration.ConfigCheck' cannot be loaded [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Wed Jun 13 09:49:06 CDT 2007 [INFO] Final Memory: 3M/6M [INFO] [INFO] Error for project: eb (during clean) [INFO] [INFO] Failed to configure plugin parameters for: org.codehaus.mojo:cobertura-maven-plugin:2.1 on the command line, specify: '-Dcheck=VALUE' Cause: Class name which was explicitly given in configuration using 'implementation' attribute: 'org.codehaus.mojo.cobertura.configuration.ConfigCheck' cannot be loaded [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [ERROR] reactor-execute : C:\Documents and Settings\eb\My Documents\workspace\eb FATAL ERROR: Error executing Maven for a project [INFO] BUILD ERRORS [INFO] [INFO] Total time: 1 second [INFO] Finished at: Wed Jun 13 09:49:06 CDT 2007 [INFO] Final Memory: 3M/6M [INFO] Does anyone here know how to fix this? Thanks. Bill. -- View this message in context: http://www.nabble.com/issue-with-cobertura---maven2--plugin-build-tf3915408s177.html#a11101878 Sent from the Maven - Users mailing list archive at Nabble.com. - 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] -- View this message in context: http://www.nabble.com/issue-with-cobertura---maven2--plugin-build-tf3915408s177.html#a11104422 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven2 plugin for eclipse
Hi Jacek, I'm using Tycho now and am quite happy with its features. I'm trying to migrate a large RCP project to tycho build, but It's lacking documentation. Is there any URL or sample project I could check? Thanks in advance. -- Danilo -- View this message in context: http://www.nabble.com/Maven2-plugin-for-eclipse-tf3391213s177.html#a10784428 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: OT: JAXWS Maven2 plugin
Hi,
I took the JAXWS maven2 plugin (current version 1.2) from the following
repository:
pluginRepositories
pluginRepository
idmaven2-repository.dev.java.net/id
nameJava.net Repository for Maven/name
urlhttp://download.java.net/maven/2//url
/pluginRepository
/pluginRepositories
This is e.g. my plugin entry to run wsimport with JAX-WS 2.1 for 2 wsdl files:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjaxws-maven-plugin/artifactId
executions
execution
idrel510/id
goals
goalwsimport/goal
/goals
configuration
wsdlFiles
wsdlFileREL-5-MM7-1-0.wsdl/wsdlFile
/wsdlFiles
bindingFiles
bindingFilecustomSchema510.xml/bindingFile
bindingFilecustomWsdl510.xml/bindingFile
/bindingFiles
staleFile
${project.build.directory}/jaxws/stale/rel510.staleFlag.
/staleFile
/configuration
/execution
execution
idrel513/id
goals
goalwsimport/goal
/goals
configuration
wsdlFiles
wsdlFileREL-5-MM7-1-3.wsdl/wsdlFile
/wsdlFiles
bindingFiles
bindingFilecustomSchema513.xml/bindingFile
bindingFilecustomWsdl513.xml/bindingFile
/bindingFiles
staleFile
${project.build.directory}/jaxws/stale/rel513.staleFlag.
/staleFile
/configuration
/execution
/executions
configuration
wsdlDirectory${basedir}/src/main/wsdl/wsdlDirectory
bindingDirectory${basedir}/src/main/jaxws/bindingDirectory
sourceDestDir
${basedir}/target/generated-sources/jaxws
/sourceDestDir
verbosetrue/verbose
/configuration
/plugin
Kind regards,
Gonne
-Ursprüngliche Nachricht-
Von: Dan Tran [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 2. Mai 2007 23:00
An: Maven Users List; [EMAIL PROTECTED]
Betreff: Re: OT: JAXWS Maven2 plugin
where did you get it?
java.net?
On 5/2/07, Seth Mason [EMAIL PROTECTED] wrote:
Apologies if this is too off topic, but has anyone used the JAXWS
maven2 plugin? I just downloaded the samples and those don't even
run. I keep getting errors about the plugin not existing even though
I've tried many different repos and many different versions.
There doesn't seem to be any support for it otherwise I'd ask there.
Thanks in advance,
SETH
-
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]
OT: JAXWS Maven2 plugin
Apologies if this is too off topic, but has anyone used the JAXWS maven2 plugin? I just downloaded the samples and those don't even run. I keep getting errors about the plugin not existing even though I've tried many different repos and many different versions. There doesn't seem to be any support for it otherwise I'd ask there. Thanks in advance, SETH - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OT: JAXWS Maven2 plugin
where did you get it? java.net? On 5/2/07, Seth Mason [EMAIL PROTECTED] wrote: Apologies if this is too off topic, but has anyone used the JAXWS maven2 plugin? I just downloaded the samples and those don't even run. I keep getting errors about the plugin not existing even though I've tried many different repos and many different versions. There doesn't seem to be any support for it otherwise I'd ask there. Thanks in advance, SETH - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven2 plugin for Cactus
2007/4/11, Sambit Bharimalla [EMAIL PROTECTED]: Hi, I have developed a J2EE project. I have choosen Maven2 for automation build process. My J2EE project involves some incontainer test cases written in Cactus. I need suggestion if following is possible or not. I want to - i- compile the code ii- test out of container test cases iii- build ear iv- deploy the ear. (I ve separate scripts for deploying the ear) v- run the incontainer test cases. Any pointer how to achieve point # 5. Has cactus provided plugin for Maven2. I searched net a lot. but didnt get any definite answer. -- Thanks Regards Sambit Sambit hi, Me and the rest of the Cactus team are currently involved in moving Cactus in the incubator where we will develop the new maven2 build system and the Cactus-m2-plugin. I will try to answer to your questions below: 1) Yes you can compile your code with maven (see compiler plugin) 2) as well as run all of the out-of-container test cases like JUnit, TestNG, ... (see the corresponding plugin) 3) and eventually build jar/war/ear/(see the corresponding plugin) 4) For deploying the archive you may consider using Cargo ( cargo.codehaus.org) - it is possible to start/stop/deploy artifacts in a large variety of containers. 5) Currently the cactus-m2 plugin is able to cactify your package and merge your webxmls. When the project is moved in the incubator we will consider finishing the plugin. If you are interested in helping, that will be a good thing. Hope that helped! -- Regards, Petar! Karlovo, Bulgaria. Public PGP Key at: https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611 Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
Maven2 plugin for Cactus
Hi, I have developed a J2EE project. I have choosen Maven2 for automation build process. My J2EE project involves some incontainer test cases written in Cactus. I need suggestion if following is possible or not. I want to - i- compile the code ii- test out of container test cases iii- build ear iv- deploy the ear. (I ve separate scripts for deploying the ear) v- run the incontainer test cases. Any pointer how to achieve point # 5. Has cactus provided plugin for Maven2. I searched net a lot. but didnt get any definite answer. -- Thanks Regards Sambit
XD2 maven2 plugin / problems with mergedir
hi all,
i am trying to move my current m2 project to use xd2 maven2 plugin but i am
encountering big problems, so i appreciate if anyone
could help me out.
this is my pom.. i have used previously xd maven2 plugin where i specified
mergedir attribute to merge files about servlets, filters etc... from
docs i read on web (http://xdoclet.codehaus.org/Maven2+plugin) looks like
mergedir is not supported in web plugin or is it?
?xml version=1.0 encoding=UTF-8?
project xmlns=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;
modelVersion4.0.0/modelVersion
groupIdWebWork/groupId
artifactIdWebWorkWebApp/artifactId
packagingwar/packaging
nameWebWorkWebApp/name
version1.0-SNAPSHOT/version
urlhttp://maven.apache.org/url
build
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idAntPlugin/id
phasegenerate-sources/phase
configuration
tasks
echoDeleting stale web.xml/echo
delete
file=${basedir}/src/main/webapp/WEB-INF/web.xml/
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
plugin
groupIdxdoclet/groupId
artifactIdmaven2-xdoclet2-plugin/artifactId
executions
execution
idgenerateSources/id
phasegenerate-sources/phase
goals
goalxdoclet/goal
/goals
/execution
/executions
dependencies
dependency
groupIdxdoclet-plugins/groupId
artifactIdxdoclet-plugin-web/artifactId
version1.0.4-SNAPSHOT/version
/dependency
/dependencies
configuration
configs
config
components
component
classname
org.xdoclet.plugin.web.WebPlugin/classname
params
mergedir${basedir}/metadata/web/mergedir
destdir${basedir}/src/main/webapp/WEB-INF//destdir
/params
/component
/components
/config
/configs
/configuration
!-- configuration
tasks
webdoclet
destDir=${basedir}/src/main/webapp/WEB-INF/
mergeDir=${basedir}/metadata/web
fileset
dir=${basedir}/src/main/java/
deploymentdescriptor /
/webdoclet
/tasks
/configuration
/execution
/executions--
/plugin
plugin
artifactIdmaven-war-plugin/artifactId
version2.0/version
configuration
warNameSpringApp/warName
outputDirectory${jbossDir}/server/default/deploy/outputDirectory
/configuration
/plugin
/plugins
/build
dependencies
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version3.8.1/version
scopetest/scope
/dependency
dependency
groupIdopensymphony/groupId
artifactIdwebwork/artifactId
version2.2/version
/dependency
dependency
groupIdopensymphony/groupId
artifactIdxwork/artifactId
version1.2/version
/dependency
dependency
groupIdjavax.servlet/groupId
artifactIdservlet-api/artifactId
version2.4/version
/dependency
dependency
groupIdorg.springframework/groupId
artifactIdspring/artifactId
version2.0-rc1/version
/dependency
dependency
groupIdcommons-logging/groupId
artifactIdcommons-logging/artifactId
version1.0.3/version
/dependency
dependency
groupIdcommons-collections/groupId
artifactIdcommons-collections/artifactId
version3.0/version
/dependency
dependency
groupIdjstl/groupId
artifactIdjstl/artifactId
version1.1.2/version
/dependency
Maven2 Plugin for Canoo Webtest available
Hi folks, is there any plugin available to run Canoo Webtests for M2? Thanks in advance Siegfried Goeschl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven2 plugin for eclipse
That's indeed a nice workaround for a failure inside the maven2 plugin.
I've set up these externaltools and nog it's ok.
It's rather a pitty that the build-in functionality (e.g. maven2 install)
fails
because the pmd:pmd mojo cannot be executed.
If anybody has any idea why it's failing, please let me know ;-)
Thanks,
LeS.
Pete [EMAIL PROTECTED]
14/03/2007 17:30
Please respond to
Maven Users List users@maven.apache.org
To
Maven Users List users@maven.apache.org
cc
Subject
Re: Maven2 plugin for eclipse
I'd say give up with all these Maven integration plugins and just use
Eclipse's external tools facility to run mvn for any selected folder
e.g.
Set up a new External Tool as follows :
Name: mvn clean install
Location: ${env_var:M2_HOME}/bin/mvn.bat
Working Directory: ${resource_loc}
Arguments: clean install
Then just select the folder or project in the Eclipse Java Tree
(folder must have a pom.xml in it) then select this external tool 'mvn
clean install' - once run once it will be on the drop down.
You can set up the common maven goals like this, then share the
External tools configuration by using the 'Common' tab and specifying
a folder that is under SCM.
At least this way you know Maven is behaving as it does from the
command line, periodically you need to run eclipse:eclipse, but this
can be done as above.
Also can set up an 'General Project' in Eclipse that points to your
local repo folder, this allows you to search this area and open pom
files if necessary.
I would gladly swap to a Plugin but there always seems to be
unexpected side effects.
On 14/03/07, Leslie Bertels [EMAIL PROTECTED] wrote:
Hi,
I trying to run pmd using the maven-pmd-plugin configured in my pom.xml
from within Eclipse.
Using the command line, everything works fine (mvn pmd:pmd)
When invoking the maven2 verify goal from within Eclipse using the Run
as
- Maven2 build ...
I receive the following error:
INFO] pmd:pmd
[ERROR] mojo-execute : pmd:pmd
Diagnosis: An error has occurred in PMD Report report generation.
FATAL ERROR: Error executing Maven for a project
[ERROR] project-execute : project.test:test-pojo:jar:1.0.0 (
task-segment:
[pmd:pmd] )
Diagnosis: An error has occurred in PMD Report report generation.
FATAL ERROR: Error executing Maven for a project
[ERROR] reactor-execute : D:\dev.env\dev\projects\test\TestProject
Diagnosis: An error has occurred in PMD Report report generation.
FATAL ERROR: Error executing Maven for a project
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An error has occurred in PMD Report report generation.
[INFO]
[DEBUG] Trace An error has occurred in PMD Report report generation.
[INFO]
[INFO] Total time: 2 seconds
[INFO] Finished at: Wed Mar 14 16:18:17 CET 2007
[INFO] Final Memory: 3M/6M
[INFO]
[INFO] Error for project: Unnamed - project.test:test-pojo:jar:1.0.0
(during pmd:pmd)
[INFO]
[INFO] An error has occurred in PMD Report report generation.
[INFO]
[DEBUG] Trace An error has occurred in PMD Report report generation.
[INFO]
[ERROR] reactor-execute : D:\dev.env\dev\projects\test\TestProject
FATAL ERROR: Error executing Maven for a project
[INFO] BUILD ERRORS
[INFO]
[INFO] Total time: 2 seconds
[INFO] Finished at: Wed Mar 14 16:18:17 CET 2007
[INFO] Final Memory: 3M/6M
[INFO]
Has anybody had the same problems?
Thanks in advance,
Regards,
Les.
Reference info:
I'm using the following pom.xml
?xml version=1.0 encoding=UTF-8?
project xmlns=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;
modelVersion4.0.0/modelVersion
groupIdproject.test/groupId
artifactIdtest-pojo/artifactId
version1.0.0/version
descriptionTemplate for Pojo Projects supported by Maven
Build/
description
build
plugins
plugin
artifactIdmaven-compiler-plugin/
artifactId
configuration
source1.5/source
target1.5/target
Maven2 plugin for eclipse
Hi, I trying to run pmd using the maven-pmd-plugin configured in my pom.xml from within Eclipse. Using the command line, everything works fine (mvn pmd:pmd) When invoking the maven2 verify goal from within Eclipse using the Run as - Maven2 build ... I receive the following error: INFO] pmd:pmd [ERROR] mojo-execute : pmd:pmd Diagnosis: An error has occurred in PMD Report report generation. FATAL ERROR: Error executing Maven for a project [ERROR] project-execute : project.test:test-pojo:jar:1.0.0 ( task-segment: [pmd:pmd] ) Diagnosis: An error has occurred in PMD Report report generation. FATAL ERROR: Error executing Maven for a project [ERROR] reactor-execute : D:\dev.env\dev\projects\test\TestProject Diagnosis: An error has occurred in PMD Report report generation. FATAL ERROR: Error executing Maven for a project [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An error has occurred in PMD Report report generation. [INFO] [DEBUG] Trace An error has occurred in PMD Report report generation. [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Wed Mar 14 16:18:17 CET 2007 [INFO] Final Memory: 3M/6M [INFO] [INFO] Error for project: Unnamed - project.test:test-pojo:jar:1.0.0 (during pmd:pmd) [INFO] [INFO] An error has occurred in PMD Report report generation. [INFO] [DEBUG] Trace An error has occurred in PMD Report report generation. [INFO] [ERROR] reactor-execute : D:\dev.env\dev\projects\test\TestProject FATAL ERROR: Error executing Maven for a project [INFO] BUILD ERRORS [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Wed Mar 14 16:18:17 CET 2007 [INFO] Final Memory: 3M/6M [INFO] Has anybody had the same problems? Thanks in advance, Regards, Les. Reference info: I'm using the following pom.xml ?xml version=1.0 encoding=UTF-8? project xmlns=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; modelVersion4.0.0/modelVersion groupIdproject.test/groupId artifactIdtest-pojo/artifactId version1.0.0/version descriptionTemplate for Pojo Projects supported by Maven Build/ description build plugins plugin artifactIdmaven-compiler-plugin/ artifactId configuration source1.5/source target1.5/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId executions execution goals goalcheck/goal goalcpd-check/ goal /goals /execution /executions /plugin /plugins /build dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version4.1/version /dependency /dependencies reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId configuration sourceEncodingutf-8/ sourceEncoding minimumTokens100/minimumTokens targetJdk1.5/targetJdk /configuration /plugin /plugins /reporting /project The information contained in this communication is confidential and may be legally privileged. It is intended solely for the use of the individual or the
Re: Maven2 plugin for eclipse
I'd say give up with all these Maven integration plugins and just use
Eclipse's external tools facility to run mvn for any selected folder
e.g.
Set up a new External Tool as follows :
Name: mvn clean install
Location: ${env_var:M2_HOME}/bin/mvn.bat
Working Directory: ${resource_loc}
Arguments: clean install
Then just select the folder or project in the Eclipse Java Tree
(folder must have a pom.xml in it) then select this external tool 'mvn
clean install' - once run once it will be on the drop down.
You can set up the common maven goals like this, then share the
External tools configuration by using the 'Common' tab and specifying
a folder that is under SCM.
At least this way you know Maven is behaving as it does from the
command line, periodically you need to run eclipse:eclipse, but this
can be done as above.
Also can set up an 'General Project' in Eclipse that points to your
local repo folder, this allows you to search this area and open pom
files if necessary.
I would gladly swap to a Plugin but there always seems to be
unexpected side effects.
On 14/03/07, Leslie Bertels [EMAIL PROTECTED] wrote:
Hi,
I trying to run pmd using the maven-pmd-plugin configured in my pom.xml
from within Eclipse.
Using the command line, everything works fine (mvn pmd:pmd)
When invoking the maven2 verify goal from within Eclipse using the Run as
- Maven2 build ...
I receive the following error:
INFO] pmd:pmd
[ERROR] mojo-execute : pmd:pmd
Diagnosis: An error has occurred in PMD Report report generation.
FATAL ERROR: Error executing Maven for a project
[ERROR] project-execute : project.test:test-pojo:jar:1.0.0 ( task-segment:
[pmd:pmd] )
Diagnosis: An error has occurred in PMD Report report generation.
FATAL ERROR: Error executing Maven for a project
[ERROR] reactor-execute : D:\dev.env\dev\projects\test\TestProject
Diagnosis: An error has occurred in PMD Report report generation.
FATAL ERROR: Error executing Maven for a project
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An error has occurred in PMD Report report generation.
[INFO]
[DEBUG] Trace An error has occurred in PMD Report report generation.
[INFO]
[INFO] Total time: 2 seconds
[INFO] Finished at: Wed Mar 14 16:18:17 CET 2007
[INFO] Final Memory: 3M/6M
[INFO]
[INFO] Error for project: Unnamed - project.test:test-pojo:jar:1.0.0
(during pmd:pmd)
[INFO]
[INFO] An error has occurred in PMD Report report generation.
[INFO]
[DEBUG] Trace An error has occurred in PMD Report report generation.
[INFO]
[ERROR] reactor-execute : D:\dev.env\dev\projects\test\TestProject
FATAL ERROR: Error executing Maven for a project
[INFO] BUILD ERRORS
[INFO]
[INFO] Total time: 2 seconds
[INFO] Finished at: Wed Mar 14 16:18:17 CET 2007
[INFO] Final Memory: 3M/6M
[INFO]
Has anybody had the same problems?
Thanks in advance,
Regards,
Les.
Reference info:
I'm using the following pom.xml
?xml version=1.0 encoding=UTF-8?
project xmlns=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;
modelVersion4.0.0/modelVersion
groupIdproject.test/groupId
artifactIdtest-pojo/artifactId
version1.0.0/version
descriptionTemplate for Pojo Projects supported by Maven Build/
description
build
plugins
plugin
artifactIdmaven-compiler-plugin/
artifactId
configuration
source1.5/source
target1.5/target
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-pmd-plugin/artifactId
executions
execution
goals
goalcheck/goal
goalcpd-check/
goal
/goals
SV: Maven2 plugin for eclipse
Hi
The Maven2 plugin works just fine - Believe me. It's just a case of learning
how to use it right, and how to deal with it's quirks.
Hermod
-Opprinnelig melding-
Fra: Pete [mailto:[EMAIL PROTECTED]
Sendt: 14. mars 2007 17:30
Til: Maven Users List
Emne: Re: Maven2 plugin for eclipse
I'd say give up with all these Maven integration plugins and just use
Eclipse's external tools facility to run mvn for any selected folder
e.g.
Set up a new External Tool as follows :
Name: mvn clean install
Location: ${env_var:M2_HOME}/bin/mvn.bat
Working Directory: ${resource_loc}
Arguments: clean install
Then just select the folder or project in the Eclipse Java Tree
(folder must have a pom.xml in it) then select this external tool 'mvn
clean install' - once run once it will be on the drop down.
You can set up the common maven goals like this, then share the
External tools configuration by using the 'Common' tab and specifying
a folder that is under SCM.
At least this way you know Maven is behaving as it does from the
command line, periodically you need to run eclipse:eclipse, but this
can be done as above.
Also can set up an 'General Project' in Eclipse that points to your
local repo folder, this allows you to search this area and open pom
files if necessary.
I would gladly swap to a Plugin but there always seems to be
unexpected side effects.
On 14/03/07, Leslie Bertels [EMAIL PROTECTED] wrote:
Hi,
I trying to run pmd using the maven-pmd-plugin configured in my pom.xml
from within Eclipse.
Using the command line, everything works fine (mvn pmd:pmd)
When invoking the maven2 verify goal from within Eclipse using the Run as
- Maven2 build ...
I receive the following error:
INFO] pmd:pmd
[ERROR] mojo-execute : pmd:pmd
Diagnosis: An error has occurred in PMD Report report generation.
FATAL ERROR: Error executing Maven for a project
[ERROR] project-execute : project.test:test-pojo:jar:1.0.0 ( task-segment:
[pmd:pmd] )
Diagnosis: An error has occurred in PMD Report report generation.
FATAL ERROR: Error executing Maven for a project
[ERROR] reactor-execute : D:\dev.env\dev\projects\test\TestProject
Diagnosis: An error has occurred in PMD Report report generation.
FATAL ERROR: Error executing Maven for a project
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An error has occurred in PMD Report report generation.
[INFO]
[DEBUG] Trace An error has occurred in PMD Report report generation.
[INFO]
[INFO] Total time: 2 seconds
[INFO] Finished at: Wed Mar 14 16:18:17 CET 2007
[INFO] Final Memory: 3M/6M
[INFO]
[INFO] Error for project: Unnamed - project.test:test-pojo:jar:1.0.0
(during pmd:pmd)
[INFO]
[INFO] An error has occurred in PMD Report report generation.
[INFO]
[DEBUG] Trace An error has occurred in PMD Report report generation.
[INFO]
[ERROR] reactor-execute : D:\dev.env\dev\projects\test\TestProject
FATAL ERROR: Error executing Maven for a project
[INFO] BUILD ERRORS
[INFO]
[INFO] Total time: 2 seconds
[INFO] Finished at: Wed Mar 14 16:18:17 CET 2007
[INFO] Final Memory: 3M/6M
[INFO]
Has anybody had the same problems?
Thanks in advance,
Regards,
Les.
Reference info:
I'm using the following pom.xml
?xml version=1.0 encoding=UTF-8?
project xmlns=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;
modelVersion4.0.0/modelVersion
groupIdproject.test/groupId
artifactIdtest-pojo/artifactId
version1.0.0/version
descriptionTemplate for Pojo Projects supported by Maven Build/
description
build
plugins
plugin
artifactIdmaven-compiler-plugin/
artifactId
configuration
source1.5/source
target1.5/target
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-pmd-plugin
RE: Maven2 plugin for eclipse
I enabled the maven project , but still have error compilation due of the dependency I have this classpath : .classpath ?xml version=1.0 encoding=UTF-8? classpath classpathentry kind=src path=src/java/ classpathentry output=target/test-classes kind=src path=src/test/ classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/ classpathentry kind=con path=org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER/ classpathentry kind=output path=target/classes/ /classpath .project ?xml version=1.0 encoding=UTF-8? projectDescription nameframework/name comment/comment projects /projects buildSpec buildCommand nameorg.eclipse.jdt.core.javabuilder/name arguments /arguments /buildCommand buildCommand nameorg.maven.ide.eclipse.maven2Builder/name arguments /arguments /buildCommand /buildSpec natures natureorg.eclipse.jdt.core.javanature/nature natureorg.maven.ide.eclipse.maven2Nature/nature /natures /projectDescription -Message d'origine- De : Hayes, Peter [mailto:[EMAIL PROTECTED] Envoyé : lundi 12 mars 2007 19:39 À : Maven Users List Objet : RE: Maven2 plugin for eclipse Yes, you will not have to manage the .classpath manually. Make sure to remove any entries defined in there that are now redundant based on the m2eclipse plugin's classpath management. I generally have the following in my .classpath files : ?xml version=1.0 encoding=UTF-8? classpath classpathentry kind=src path=src/main/java/ classpathentry kind=src path=src/main/resources/ classpathentry kind=src path=src/test/java/ classpathentry kind=src path=src/test/resources/ classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/ classpathentry kind=con path=org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER/ classpathentry kind=output path=classes/ /classpath Pete -Original Message- From: Marouane Amraoui [mailto:[EMAIL PROTECTED] Sent: Monday, March 12, 2007 3:31 PM To: Maven Users List Subject: RE: Maven2 plugin for eclipse I didn't have enabled my project maven . so If I enable it we don't need to execute eclipse:eclipse inorder to synchronize the pom dependency and .classpth -Message d'origine- De : Hayes, Peter [mailto:[EMAIL PROTECTED] Envoyé : lundi 12 mars 2007 19:22 À : Maven Users List Objet : RE: Maven2 plugin for eclipse Sorry, make sure that you enable the plugin on your project. You have to right-click the project and there should be a Maven2 menu. Select enable. Pete -Original Message- From: Hayes, Peter Sent: Monday, March 12, 2007 3:20 PM To: Maven Users List Subject: RE: Maven2 plugin for eclipse http://m2eclipse.codehaus.org/ This plugin keeps your classpath in synch with your pom file via an Eclipse classpath container. It's very good. -Original Message- From: Marouane Amraoui [mailto:[EMAIL PROTECTED] Sent: Monday, March 12, 2007 2:05 PM To: Maven Users List Subject: Maven2 plugin for eclipse I m using Maven2 plugin for eclipse . Version plugin is : 0.0.10. I created a maven project . I added dependency using the plugin. when I add the dependency it only added in pom file and note in eclipse file .classpath this obligate me to do A double work There is a solution for that ??? --- Merouane AMRAOUI Consultant Expert Division Développement Email.: [EMAIL PROTECTED] Gsm .: 065 19 60 99 Tél. | Tel.: 022 98 70 70Téléc | Fax: 022 98 70 70 OMNIDATA , 74 Bv AbdelMoumen - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven2 plugin for eclipse : OK now
Is OK now :). So i noticed that in the pom file signal an error of a messing jar . for that the container doesn't work I think. Thx a lot for your help. -Message d'origine- De : Marouane Amraoui [mailto:[EMAIL PROTECTED] Envoyé : mardi 13 mars 2007 10:56 À : Maven Users List Objet : RE: Maven2 plugin for eclipse I enabled the maven project , but still have error compilation due of the dependency I have this classpath : .classpath ?xml version=1.0 encoding=UTF-8? classpath classpathentry kind=src path=src/java/ classpathentry output=target/test-classes kind=src path=src/test/ classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/ classpathentry kind=con path=org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER/ classpathentry kind=output path=target/classes/ /classpath .project ?xml version=1.0 encoding=UTF-8? projectDescription nameframework/name comment/comment projects /projects buildSpec buildCommand nameorg.eclipse.jdt.core.javabuilder/name arguments /arguments /buildCommand buildCommand nameorg.maven.ide.eclipse.maven2Builder/name arguments /arguments /buildCommand /buildSpec natures natureorg.eclipse.jdt.core.javanature/nature natureorg.maven.ide.eclipse.maven2Nature/nature /natures /projectDescription -Message d'origine- De : Hayes, Peter [mailto:[EMAIL PROTECTED] Envoyé : lundi 12 mars 2007 19:39 À : Maven Users List Objet : RE: Maven2 plugin for eclipse Yes, you will not have to manage the .classpath manually. Make sure to remove any entries defined in there that are now redundant based on the m2eclipse plugin's classpath management. I generally have the following in my .classpath files : ?xml version=1.0 encoding=UTF-8? classpath classpathentry kind=src path=src/main/java/ classpathentry kind=src path=src/main/resources/ classpathentry kind=src path=src/test/java/ classpathentry kind=src path=src/test/resources/ classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/ classpathentry kind=con path=org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER/ classpathentry kind=output path=classes/ /classpath Pete -Original Message- From: Marouane Amraoui [mailto:[EMAIL PROTECTED] Sent: Monday, March 12, 2007 3:31 PM To: Maven Users List Subject: RE: Maven2 plugin for eclipse I didn't have enabled my project maven . so If I enable it we don't need to execute eclipse:eclipse inorder to synchronize the pom dependency and .classpth -Message d'origine- De : Hayes, Peter [mailto:[EMAIL PROTECTED] Envoyé : lundi 12 mars 2007 19:22 À : Maven Users List Objet : RE: Maven2 plugin for eclipse Sorry, make sure that you enable the plugin on your project. You have to right-click the project and there should be a Maven2 menu. Select enable. Pete -Original Message- From: Hayes, Peter Sent: Monday, March 12, 2007 3:20 PM To: Maven Users List Subject: RE: Maven2 plugin for eclipse http://m2eclipse.codehaus.org/ This plugin keeps your classpath in synch with your pom file via an Eclipse classpath container. It's very good. -Original Message- From: Marouane Amraoui [mailto:[EMAIL PROTECTED] Sent: Monday, March 12, 2007 2:05 PM To: Maven Users List Subject: Maven2 plugin for eclipse I m using Maven2 plugin for eclipse . Version plugin is : 0.0.10. I created a maven project . I added dependency using the plugin. when I add the dependency it only added in pom file and note in eclipse file .classpath this obligate me to do A double work There is a solution for that ??? --- Merouane AMRAOUI Consultant Expert Division Développement Email.: [EMAIL PROTECTED] Gsm .: 065 19 60 99 Tél. | Tel.: 022 98 70 70Téléc | Fax: 022 98 70 70 OMNIDATA , 74 Bv AbdelMoumen - 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: Maven2 plugin for eclipse
On 3/13/07, Marouane Amraoui [EMAIL PROTECTED] wrote: I enabled the maven project , but still have error compilation due of the dependency I have this classpath : ... .project I wonder why you care about these files? They're for Eclipse not M2. Take a look at pom.xml. That's where the troubles live ;-) Keep in mind that the Maven Integration plugin for Eclipse (Tycho) is not finished yet and it's long before it becomes a production ready so even though you can do many M2 operations from within Eclipse, that's the pom.xml where project information lives. I have recently worked with the plugin and added the TestNG dependency to the project of mine. It worked fine from Eclipse perspective, but pom.xml was incorrect. There was no classifier specified. I had to edit the file manually and move on. Overall, I'm satisfied with the plugin, but don't expect too much at such an early stage of its development. Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven2 plugin for eclipse : OK now
The missing file jar is com.sun.tools . is a dependency of commons-
attributs-compiler. In the pom file of commons-attributs-compiler :
groupIdcom.sun/groupId
artifactIdtools/artifactId
version1.4.2/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
I didn't undrestand what i need to do in this case
-Message d'origine-
De : Marouane Amraoui [mailto:[EMAIL PROTECTED]
Envoyé : mardi 13 mars 2007 11:11
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse : OK now
Is OK now :). So i noticed that in the pom file signal an error of a messing
jar . for that the container doesn't work I think.
Thx a lot for your help.
-Message d'origine-
De : Marouane Amraoui [mailto:[EMAIL PROTECTED]
Envoyé : mardi 13 mars 2007 10:56
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse
I enabled the maven project , but still have error compilation due of the
dependency
I have this classpath :
.classpath
?xml version=1.0 encoding=UTF-8?
classpath
classpathentry kind=src path=src/java/
classpathentry output=target/test-classes kind=src
path=src/test/
classpathentry kind=con
path=org.eclipse.jdt.launching.JRE_CONTAINER/
classpathentry kind=con
path=org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER/
classpathentry kind=output path=target/classes/
/classpath
.project
?xml version=1.0 encoding=UTF-8?
projectDescription
nameframework/name
comment/comment
projects
/projects
buildSpec
buildCommand
nameorg.eclipse.jdt.core.javabuilder/name
arguments
/arguments
/buildCommand
buildCommand
nameorg.maven.ide.eclipse.maven2Builder/name
arguments
/arguments
/buildCommand
/buildSpec
natures
natureorg.eclipse.jdt.core.javanature/nature
natureorg.maven.ide.eclipse.maven2Nature/nature
/natures
/projectDescription
-Message d'origine-
De : Hayes, Peter [mailto:[EMAIL PROTECTED]
Envoyé : lundi 12 mars 2007 19:39
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse
Yes, you will not have to manage the .classpath manually. Make sure to remove
any entries defined in there that are now redundant based on the m2eclipse
plugin's classpath management.
I generally have the following in my .classpath files :
?xml version=1.0 encoding=UTF-8?
classpath
classpathentry kind=src path=src/main/java/
classpathentry kind=src path=src/main/resources/
classpathentry kind=src path=src/test/java/
classpathentry kind=src path=src/test/resources/
classpathentry kind=con
path=org.eclipse.jdt.launching.JRE_CONTAINER/
classpathentry kind=con
path=org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER/
classpathentry kind=output path=classes/
/classpath
Pete
-Original Message-
From: Marouane Amraoui [mailto:[EMAIL PROTECTED]
Sent: Monday, March 12, 2007 3:31 PM
To: Maven Users List
Subject: RE: Maven2 plugin for eclipse
I didn't have enabled my project maven . so If I enable it we don't need to
execute eclipse:eclipse inorder to synchronize the pom dependency and .classpth
-Message d'origine-
De : Hayes, Peter [mailto:[EMAIL PROTECTED]
Envoyé : lundi 12 mars 2007 19:22
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse
Sorry, make sure that you enable the plugin on your project. You have to
right-click the project and there should be a Maven2 menu. Select enable.
Pete
-Original Message-
From: Hayes, Peter
Sent: Monday, March 12, 2007 3:20 PM
To: Maven Users List
Subject: RE: Maven2 plugin for eclipse
http://m2eclipse.codehaus.org/
This plugin keeps your classpath in synch with your pom file via an Eclipse
classpath container. It's very good.
-Original Message-
From: Marouane Amraoui [mailto:[EMAIL PROTECTED]
Sent: Monday, March 12, 2007 2:05 PM
To: Maven Users List
Subject: Maven2 plugin for eclipse
I m using Maven2 plugin for eclipse .
Version plugin is : 0.0.10.
I created a maven project . I added dependency using the plugin.
when I add the dependency it only added in pom file and note in eclipse file
.classpath this obligate me to do
A double work
There is a solution for that ???
---
Merouane AMRAOUI
Consultant Expert
Division Développement
Email.: [EMAIL PROTECTED]
Gsm .: 065 19 60 99
Tél. | Tel.: 022 98 70 70Téléc | Fax: 022 98 70 70
OMNIDATA , 74 Bv AbdelMoumen
-
To unsubscribe, e-mail: [EMAIL
Re: Maven2 plugin for eclipse
Any idea what's the shedule for a first release (milestone or something similar) on the eclipse plugin (Tycho)? Jacek Laskowski [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 13/03/2007 12:15 Please respond to Maven Users List users@maven.apache.org To Maven Users List users@maven.apache.org cc Subject Re: Maven2 plugin for eclipse On 3/13/07, Marouane Amraoui [EMAIL PROTECTED] wrote: I enabled the maven project , but still have error compilation due of the dependency I have this classpath : ... .project I wonder why you care about these files? They're for Eclipse not M2. Take a look at pom.xml. That's where the troubles live ;-) Keep in mind that the Maven Integration plugin for Eclipse (Tycho) is not finished yet and it's long before it becomes a production ready so even though you can do many M2 operations from within Eclipse, that's the pom.xml where project information lives. I have recently worked with the plugin and added the TestNG dependency to the project of mine. It worked fine from Eclipse perspective, but pom.xml was incorrect. There was no classifier specified. I had to edit the file manually and move on. Overall, I'm satisfied with the plugin, but don't expect too much at such an early stage of its development. Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The information contained in this communication is confidential and may be legally privileged. It is intended solely for the use of the individual or the entity to whom it is addressed and others authorised to receive it. If you have received it by mistake, please let the sender know by e-mail reply and delete it from your system. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance of the contents of this information is strictly prohibited and may be unlawful. Honda Europe NV is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.
RE: Maven2 plugin for eclipse : OK now
Hi,
It is possible that dependencies with system scope are not correctly
handled by the plugin. Check that tools.jar appears in the list of jars
within the Maven Dependencies library container. If it is not there,
just add it manually to the Eclipse project classpath.
Hope this helps you,
Rodrigo
Marouane Amraoui wrote:
The missing file jar is com.sun.tools . is a dependency of commons-
attributs-compiler. In the pom file of commons-attributs-compiler :
groupIdcom.sun/groupId
artifactIdtools/artifactId
version1.4.2/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
I didn't undrestand what i need to do in this case
-Message d'origine-
De : Marouane Amraoui [mailto:[EMAIL PROTECTED]
Envoyé : mardi 13 mars 2007 11:11
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse : OK now
Is OK now :). So i noticed that in the pom file signal an error of a
messing jar . for that the container doesn't work I think.
Thx a lot for your help.
-Message d'origine-
De : Marouane Amraoui [mailto:[EMAIL PROTECTED]
Envoyé : mardi 13 mars 2007 10:56
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse
I enabled the maven project , but still have error compilation due of the
dependency
I have this classpath :
.classpath
?xml version=1.0 encoding=UTF-8?
classpath
classpathentry kind=src path=src/java/
classpathentry output=target/test-classes kind=src
path=src/test/
classpathentry kind=con
path=org.eclipse.jdt.launching.JRE_CONTAINER/
classpathentry kind=con
path=org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER/
classpathentry kind=output path=target/classes/
/classpath
.project
?xml version=1.0 encoding=UTF-8?
projectDescription
nameframework/name
comment/comment
projects
/projects
buildSpec
buildCommand
nameorg.eclipse.jdt.core.javabuilder/name
arguments
/arguments
/buildCommand
buildCommand
nameorg.maven.ide.eclipse.maven2Builder/name
arguments
/arguments
/buildCommand
/buildSpec
natures
natureorg.eclipse.jdt.core.javanature/nature
natureorg.maven.ide.eclipse.maven2Nature/nature
/natures
/projectDescription
-Message d'origine-
De : Hayes, Peter [mailto:[EMAIL PROTECTED]
Envoyé : lundi 12 mars 2007 19:39
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse
Yes, you will not have to manage the .classpath manually. Make sure to
remove any entries defined in there that are now redundant based on the
m2eclipse plugin's classpath management.
I generally have the following in my .classpath files :
?xml version=1.0 encoding=UTF-8?
classpath
classpathentry kind=src path=src/main/java/
classpathentry kind=src path=src/main/resources/
classpathentry kind=src path=src/test/java/
classpathentry kind=src path=src/test/resources/
classpathentry kind=con
path=org.eclipse.jdt.launching.JRE_CONTAINER/
classpathentry kind=con
path=org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER/
classpathentry kind=output path=classes/
/classpath
Pete
-Original Message-
From: Marouane Amraoui [mailto:[EMAIL PROTECTED]
Sent: Monday, March 12, 2007 3:31 PM
To: Maven Users List
Subject: RE: Maven2 plugin for eclipse
I didn't have enabled my project maven . so If I enable it we don't need
to execute eclipse:eclipse inorder to synchronize the pom dependency and
.classpth
-Message d'origine-
De : Hayes, Peter [mailto:[EMAIL PROTECTED]
Envoyé : lundi 12 mars 2007 19:22
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse
Sorry, make sure that you enable the plugin on your project. You have to
right-click the project and there should be a Maven2 menu. Select enable.
Pete
-Original Message-
From: Hayes, Peter
Sent: Monday, March 12, 2007 3:20 PM
To: Maven Users List
Subject: RE: Maven2 plugin for eclipse
http://m2eclipse.codehaus.org/
This plugin keeps your classpath in synch with your pom file via an
Eclipse classpath container. It's very good.
-Original Message-
From: Marouane Amraoui [mailto:[EMAIL PROTECTED]
Sent: Monday, March 12, 2007 2:05 PM
To: Maven Users List
Subject: Maven2 plugin for eclipse
I m using Maven2 plugin for eclipse .
Version plugin is : 0.0.10.
I created a maven project . I added dependency using the plugin.
when I add the dependency it only added in pom file and note in eclipse
file .classpath this obligate me to do
A double work
There is a solution
RE: Maven2 plugin for eclipse : OK now
This actually should work in the 0.0.10 version of the m2eclipse plugin. Make
sure that you are using a _JDK_ and not a JRE to run Eclipse / Maven. The
tools.jar is not present in the JRE package.
-Original Message-
From: Rodrigo Ruiz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 13, 2007 8:31 AM
To: Maven Users List
Subject: RE: Maven2 plugin for eclipse : OK now
Hi,
It is possible that dependencies with system scope are not correctly
handled by the plugin. Check that tools.jar appears in the list of jars
within the Maven Dependencies library container. If it is not there,
just add it manually to the Eclipse project classpath.
Hope this helps you,
Rodrigo
Marouane Amraoui wrote:
The missing file jar is com.sun.tools . is a dependency of commons-
attributs-compiler. In the pom file of commons-attributs-compiler :
groupIdcom.sun/groupId
artifactIdtools/artifactId
version1.4.2/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
I didn't undrestand what i need to do in this case
-Message d'origine-
De : Marouane Amraoui [mailto:[EMAIL PROTECTED]
Envoyé : mardi 13 mars 2007 11:11
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse : OK now
Is OK now :). So i noticed that in the pom file signal an error of a
messing jar . for that the container doesn't work I think.
Thx a lot for your help.
-Message d'origine-
De : Marouane Amraoui [mailto:[EMAIL PROTECTED]
Envoyé : mardi 13 mars 2007 10:56
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse
I enabled the maven project , but still have error compilation due of the
dependency
I have this classpath :
.classpath
?xml version=1.0 encoding=UTF-8?
classpath
classpathentry kind=src path=src/java/
classpathentry output=target/test-classes kind=src
path=src/test/
classpathentry kind=con
path=org.eclipse.jdt.launching.JRE_CONTAINER/
classpathentry kind=con
path=org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER/
classpathentry kind=output path=target/classes/
/classpath
.project
?xml version=1.0 encoding=UTF-8?
projectDescription
nameframework/name
comment/comment
projects
/projects
buildSpec
buildCommand
nameorg.eclipse.jdt.core.javabuilder/name
arguments
/arguments
/buildCommand
buildCommand
nameorg.maven.ide.eclipse.maven2Builder/name
arguments
/arguments
/buildCommand
/buildSpec
natures
natureorg.eclipse.jdt.core.javanature/nature
natureorg.maven.ide.eclipse.maven2Nature/nature
/natures
/projectDescription
-Message d'origine-
De : Hayes, Peter [mailto:[EMAIL PROTECTED]
Envoyé : lundi 12 mars 2007 19:39
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse
Yes, you will not have to manage the .classpath manually. Make sure to
remove any entries defined in there that are now redundant based on the
m2eclipse plugin's classpath management.
I generally have the following in my .classpath files :
?xml version=1.0 encoding=UTF-8?
classpath
classpathentry kind=src path=src/main/java/
classpathentry kind=src path=src/main/resources/
classpathentry kind=src path=src/test/java/
classpathentry kind=src path=src/test/resources/
classpathentry kind=con
path=org.eclipse.jdt.launching.JRE_CONTAINER/
classpathentry kind=con
path=org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER/
classpathentry kind=output path=classes/
/classpath
Pete
-Original Message-
From: Marouane Amraoui [mailto:[EMAIL PROTECTED]
Sent: Monday, March 12, 2007 3:31 PM
To: Maven Users List
Subject: RE: Maven2 plugin for eclipse
I didn't have enabled my project maven . so If I enable it we don't need
to execute eclipse:eclipse inorder to synchronize the pom dependency and
.classpth
-Message d'origine-
De : Hayes, Peter [mailto:[EMAIL PROTECTED]
Envoyé : lundi 12 mars 2007 19:22
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse
Sorry, make sure that you enable the plugin on your project. You have to
right-click the project and there should be a Maven2 menu. Select enable.
Pete
-Original Message-
From: Hayes, Peter
Sent: Monday, March 12, 2007 3:20 PM
To: Maven Users List
Subject: RE: Maven2 plugin for eclipse
http://m2eclipse.codehaus.org/
This plugin keeps your classpath in synch with your pom file via an
Eclipse classpath container. It's very good.
-Original Message-
From: Marouane Amraoui [mailto:[EMAIL PROTECTED]
Sent: Monday, March 12, 2007 2:05 PM
To: Maven
RE: Maven2 plugin for eclipse : OK now
At the begining in InstalledJRE it was : c:\eclipse.
I modified it to C:\j2sdk1.4.2_13. but still the same error.
So I must run eclipse with -Djava.home or what
thx
-Message d'origine-
De : Hayes, Peter [mailto:[EMAIL PROTECTED]
Envoyé : mardi 13 mars 2007 12:36
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse : OK now
This actually should work in the 0.0.10 version of the m2eclipse plugin. Make
sure that you are using a _JDK_ and not a JRE to run Eclipse / Maven. The
tools.jar is not present in the JRE package.
-Original Message-
From: Rodrigo Ruiz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 13, 2007 8:31 AM
To: Maven Users List
Subject: RE: Maven2 plugin for eclipse : OK now
Hi,
It is possible that dependencies with system scope are not correctly
handled by the plugin. Check that tools.jar appears in the list of jars
within the Maven Dependencies library container. If it is not there,
just add it manually to the Eclipse project classpath.
Hope this helps you,
Rodrigo
Marouane Amraoui wrote:
The missing file jar is com.sun.tools . is a dependency of commons-
attributs-compiler. In the pom file of commons-attributs-compiler :
groupIdcom.sun/groupId
artifactIdtools/artifactId
version1.4.2/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
I didn't undrestand what i need to do in this case
-Message d'origine-
De : Marouane Amraoui [mailto:[EMAIL PROTECTED]
Envoyé : mardi 13 mars 2007 11:11
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse : OK now
Is OK now :). So i noticed that in the pom file signal an error of a
messing jar . for that the container doesn't work I think.
Thx a lot for your help.
-Message d'origine-
De : Marouane Amraoui [mailto:[EMAIL PROTECTED]
Envoyé : mardi 13 mars 2007 10:56
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse
I enabled the maven project , but still have error compilation due of the
dependency
I have this classpath :
.classpath
?xml version=1.0 encoding=UTF-8?
classpath
classpathentry kind=src path=src/java/
classpathentry output=target/test-classes kind=src
path=src/test/
classpathentry kind=con
path=org.eclipse.jdt.launching.JRE_CONTAINER/
classpathentry kind=con
path=org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER/
classpathentry kind=output path=target/classes/
/classpath
.project
?xml version=1.0 encoding=UTF-8?
projectDescription
nameframework/name
comment/comment
projects
/projects
buildSpec
buildCommand
nameorg.eclipse.jdt.core.javabuilder/name
arguments
/arguments
/buildCommand
buildCommand
nameorg.maven.ide.eclipse.maven2Builder/name
arguments
/arguments
/buildCommand
/buildSpec
natures
natureorg.eclipse.jdt.core.javanature/nature
natureorg.maven.ide.eclipse.maven2Nature/nature
/natures
/projectDescription
-Message d'origine-
De : Hayes, Peter [mailto:[EMAIL PROTECTED]
Envoyé : lundi 12 mars 2007 19:39
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse
Yes, you will not have to manage the .classpath manually. Make sure to
remove any entries defined in there that are now redundant based on the
m2eclipse plugin's classpath management.
I generally have the following in my .classpath files :
?xml version=1.0 encoding=UTF-8?
classpath
classpathentry kind=src path=src/main/java/
classpathentry kind=src path=src/main/resources/
classpathentry kind=src path=src/test/java/
classpathentry kind=src path=src/test/resources/
classpathentry kind=con
path=org.eclipse.jdt.launching.JRE_CONTAINER/
classpathentry kind=con
path=org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER/
classpathentry kind=output path=classes/
/classpath
Pete
-Original Message-
From: Marouane Amraoui [mailto:[EMAIL PROTECTED]
Sent: Monday, March 12, 2007 3:31 PM
To: Maven Users List
Subject: RE: Maven2 plugin for eclipse
I didn't have enabled my project maven . so If I enable it we don't need
to execute eclipse:eclipse inorder to synchronize the pom dependency and
.classpth
-Message d'origine-
De : Hayes, Peter [mailto:[EMAIL PROTECTED]
Envoyé : lundi 12 mars 2007 19:22
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse
Sorry, make sure that you enable the plugin on your project. You have to
right-click the project and there should be a Maven2 menu. Select enable.
Pete
-Original Message-
From: Hayes, Peter
Sent: Monday, March 12, 2007 3
RE: Maven2 plugin for eclipse : OK now
In this case, it is not the JDK configured within Eclipse itself (this
configures the JDK's available to compile with), but the JDK that Eclipse is
run with externally. Check your environment variables for JAVA_HOME and your
path for the version of Java that you use. In my case I have (for Windows) :
MAVEN_HOME = c:\dev\tools\maven-2.0.5
JAVA_HOME = c:\Program Files\Java\jdk1.5.0_10
PATH = %MAVEN_HOME%\bin;%JAVA_HOME%\bin
This means that when eclipse is invoked (or Maven) it uses the JDK1.5.0_10 to
run.
HTH,
Pete
-Original Message-
From: Marouane Amraoui [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 13, 2007 8:49 AM
To: Maven Users List
Subject: RE: Maven2 plugin for eclipse : OK now
At the begining in InstalledJRE it was : c:\eclipse.
I modified it to C:\j2sdk1.4.2_13. but still the same error.
So I must run eclipse with -Djava.home or what
thx
-Message d'origine-
De : Hayes, Peter [mailto:[EMAIL PROTECTED]
Envoyé : mardi 13 mars 2007 12:36
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse : OK now
This actually should work in the 0.0.10 version of the m2eclipse plugin. Make
sure that you are using a _JDK_ and not a JRE to run Eclipse / Maven. The
tools.jar is not present in the JRE package.
-Original Message-
From: Rodrigo Ruiz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 13, 2007 8:31 AM
To: Maven Users List
Subject: RE: Maven2 plugin for eclipse : OK now
Hi,
It is possible that dependencies with system scope are not correctly
handled by the plugin. Check that tools.jar appears in the list of jars
within the Maven Dependencies library container. If it is not there,
just add it manually to the Eclipse project classpath.
Hope this helps you,
Rodrigo
Marouane Amraoui wrote:
The missing file jar is com.sun.tools . is a dependency of commons-
attributs-compiler. In the pom file of commons-attributs-compiler :
groupIdcom.sun/groupId
artifactIdtools/artifactId
version1.4.2/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
I didn't undrestand what i need to do in this case
-Message d'origine-
De : Marouane Amraoui [mailto:[EMAIL PROTECTED]
Envoyé : mardi 13 mars 2007 11:11
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse : OK now
Is OK now :). So i noticed that in the pom file signal an error of a
messing jar . for that the container doesn't work I think.
Thx a lot for your help.
-Message d'origine-
De : Marouane Amraoui [mailto:[EMAIL PROTECTED]
Envoyé : mardi 13 mars 2007 10:56
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse
I enabled the maven project , but still have error compilation due of the
dependency
I have this classpath :
.classpath
?xml version=1.0 encoding=UTF-8?
classpath
classpathentry kind=src path=src/java/
classpathentry output=target/test-classes kind=src
path=src/test/
classpathentry kind=con
path=org.eclipse.jdt.launching.JRE_CONTAINER/
classpathentry kind=con
path=org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER/
classpathentry kind=output path=target/classes/
/classpath
.project
?xml version=1.0 encoding=UTF-8?
projectDescription
nameframework/name
comment/comment
projects
/projects
buildSpec
buildCommand
nameorg.eclipse.jdt.core.javabuilder/name
arguments
/arguments
/buildCommand
buildCommand
nameorg.maven.ide.eclipse.maven2Builder/name
arguments
/arguments
/buildCommand
/buildSpec
natures
natureorg.eclipse.jdt.core.javanature/nature
natureorg.maven.ide.eclipse.maven2Nature/nature
/natures
/projectDescription
-Message d'origine-
De : Hayes, Peter [mailto:[EMAIL PROTECTED]
Envoyé : lundi 12 mars 2007 19:39
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse
Yes, you will not have to manage the .classpath manually. Make sure to
remove any entries defined in there that are now redundant based on the
m2eclipse plugin's classpath management.
I generally have the following in my .classpath files :
?xml version=1.0 encoding=UTF-8?
classpath
classpathentry kind=src path=src/main/java/
classpathentry kind=src path=src/main/resources/
classpathentry kind=src path=src/test/java/
classpathentry kind=src path=src/test/resources/
classpathentry kind=con
path=org.eclipse.jdt.launching.JRE_CONTAINER/
classpathentry kind=con
path=org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER/
classpathentry kind=output path=classes/
/classpath
Pete
-Original Message-
From
RE: Maven2 plugin for eclipse : OK now
My env parameters are :
M2_HOME = C:\Program Files\Apache Software Foundation\maven-2.0.4
JAVA_HOME = C:\j2sdk1.4.2_13
PATH = %JAVA_HOME%\bin; %MAVEN_HOME%\bin
But the problem still occure. !!!
Any suggestion please ?
thx
-Message d'origine-
De : Hayes, Peter [mailto:[EMAIL PROTECTED]
Envoyé : mardi 13 mars 2007 13:01
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse : OK now
In this case, it is not the JDK configured within Eclipse itself (this
configures the JDK's available to compile with), but the JDK that Eclipse is
run with externally. Check your environment variables for JAVA_HOME and your
path for the version of Java that you use. In my case I have (for Windows) :
MAVEN_HOME = c:\dev\tools\maven-2.0.5
JAVA_HOME = c:\Program Files\Java\jdk1.5.0_10
PATH = %MAVEN_HOME%\bin;%JAVA_HOME%\bin
This means that when eclipse is invoked (or Maven) it uses the JDK1.5.0_10 to
run.
HTH,
Pete
-Original Message-
From: Marouane Amraoui [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 13, 2007 8:49 AM
To: Maven Users List
Subject: RE: Maven2 plugin for eclipse : OK now
At the begining in InstalledJRE it was : c:\eclipse.
I modified it to C:\j2sdk1.4.2_13. but still the same error.
So I must run eclipse with -Djava.home or what
thx
-Message d'origine-
De : Hayes, Peter [mailto:[EMAIL PROTECTED]
Envoyé : mardi 13 mars 2007 12:36
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse : OK now
This actually should work in the 0.0.10 version of the m2eclipse plugin. Make
sure that you are using a _JDK_ and not a JRE to run Eclipse / Maven. The
tools.jar is not present in the JRE package.
-Original Message-
From: Rodrigo Ruiz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 13, 2007 8:31 AM
To: Maven Users List
Subject: RE: Maven2 plugin for eclipse : OK now
Hi,
It is possible that dependencies with system scope are not correctly
handled by the plugin. Check that tools.jar appears in the list of jars
within the Maven Dependencies library container. If it is not there,
just add it manually to the Eclipse project classpath.
Hope this helps you,
Rodrigo
Marouane Amraoui wrote:
The missing file jar is com.sun.tools . is a dependency of commons-
attributs-compiler. In the pom file of commons-attributs-compiler :
groupIdcom.sun/groupId
artifactIdtools/artifactId
version1.4.2/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
I didn't undrestand what i need to do in this case
-Message d'origine-
De : Marouane Amraoui [mailto:[EMAIL PROTECTED]
Envoyé : mardi 13 mars 2007 11:11
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse : OK now
Is OK now :). So i noticed that in the pom file signal an error of a
messing jar . for that the container doesn't work I think.
Thx a lot for your help.
-Message d'origine-
De : Marouane Amraoui [mailto:[EMAIL PROTECTED]
Envoyé : mardi 13 mars 2007 10:56
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse
I enabled the maven project , but still have error compilation due of the
dependency
I have this classpath :
.classpath
?xml version=1.0 encoding=UTF-8?
classpath
classpathentry kind=src path=src/java/
classpathentry output=target/test-classes kind=src
path=src/test/
classpathentry kind=con
path=org.eclipse.jdt.launching.JRE_CONTAINER/
classpathentry kind=con
path=org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER/
classpathentry kind=output path=target/classes/
/classpath
.project
?xml version=1.0 encoding=UTF-8?
projectDescription
nameframework/name
comment/comment
projects
/projects
buildSpec
buildCommand
nameorg.eclipse.jdt.core.javabuilder/name
arguments
/arguments
/buildCommand
buildCommand
nameorg.maven.ide.eclipse.maven2Builder/name
arguments
/arguments
/buildCommand
/buildSpec
natures
natureorg.eclipse.jdt.core.javanature/nature
natureorg.maven.ide.eclipse.maven2Nature/nature
/natures
/projectDescription
-Message d'origine-
De : Hayes, Peter [mailto:[EMAIL PROTECTED]
Envoyé : lundi 12 mars 2007 19:39
À : Maven Users List
Objet : RE: Maven2 plugin for eclipse
Yes, you will not have to manage the .classpath manually. Make sure to
remove any entries defined in there that are now redundant based on the
m2eclipse plugin's classpath management.
I generally have the following in my .classpath files :
?xml version=1.0 encoding=UTF-8?
classpath
classpathentry kind=src path=src/main/java/
classpathentry kind=src
Re: Maven2 plugin for eclipse
On 3/13/07, Leslie Bertels [EMAIL PROTECTED] wrote: Any idea what's the shedule for a first release (milestone or something similar) on the eclipse plugin (Tycho)? I don't, but does it really matter? If it meets your needs now, why should you care if it's 1.0 or 0.1? It's a common understanding that 1.0 is better than 0.1, but don't be misinformed it does not have to be. I'm using Tycho now and am quite happy with its features. Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven2 plugin for eclipse
Does is matter? Well euhm... Not really ;-) If it meets your needs now... It does, it does... however I do seem to be using a command line alot since some things seem to fail or are missing. (eg. building a war project) Thanks for the reply Rgds, Les. On 3/13/07, Leslie Bertels [EMAIL PROTECTED] wrote: Any idea what's the shedule for a first release (milestone or something similar) on the eclipse plugin (Tycho)? I don't, but does it really matter? If it meets your needs now, why should you care if it's 1.0 or 0.1? It's a common understanding that 1.0 is better than 0.1, but don't be misinformed it does not have to be. I'm using Tycho now and am quite happy with its features. Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The information contained in this communication is confidential and may be legally privileged. It is intended solely for the use of the individual or the entity to whom it is addressed and others authorised to receive it. If you have received it by mistake, please let the sender know by e-mail reply and delete it from your system. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance of the contents of this information is strictly prohibited and may be unlawful. Honda Europe NV is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.
Maven2 plugin for eclipse
I m using Maven2 plugin for eclipse . Version plugin is : 0.0.10. I created a maven project . I added dependency using the plugin. when I add the dependency it only added in pom file and note in eclipse file .classpath this obligate me to do A double work There is a solution for that ??? --- Merouane AMRAOUI Consultant Expert Division Développement Email.: [EMAIL PROTECTED] Gsm .: 065 19 60 99 Tél. | Tel.: 022 98 70 70Téléc | Fax: 022 98 70 70 OMNIDATA , 74 Bv AbdelMoumen
Re: Maven2 plugin for eclipse
mvn eclipse:eclipse? http://maven.apache.org/guides/mini/guide-ide-eclipse.html Hope this helps. Steffen Marouane Amraoui schrieb: I m using Maven2 plugin for eclipse . Version plugin is : 0.0.10. I created a maven project . I added dependency using the plugin. when I add the dependency it only added in pom file and note in eclipse file .classpath this obligate me to do A double work There is a solution for that ??? --- Merouane AMRAOUI Consultant Expert Division Développement Email.: [EMAIL PROTECTED] Gsm .: 065 19 60 99 Tél. | Tel.: 022 98 70 70Téléc | Fax: 022 98 70 70 OMNIDATA , 74 Bv AbdelMoumen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven2 plugin for eclipse
http://m2eclipse.codehaus.org/ This plugin keeps your classpath in synch with your pom file via an Eclipse classpath container. It's very good. -Original Message- From: Marouane Amraoui [mailto:[EMAIL PROTECTED] Sent: Monday, March 12, 2007 2:05 PM To: Maven Users List Subject: Maven2 plugin for eclipse I m using Maven2 plugin for eclipse . Version plugin is : 0.0.10. I created a maven project . I added dependency using the plugin. when I add the dependency it only added in pom file and note in eclipse file .classpath this obligate me to do A double work There is a solution for that ??? --- Merouane AMRAOUI Consultant Expert Division Développement Email.: [EMAIL PROTECTED] Gsm .: 065 19 60 99 Tél. | Tel.: 022 98 70 70Téléc | Fax: 022 98 70 70 OMNIDATA , 74 Bv AbdelMoumen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven2 plugin for eclipse
Exactly :) We add in pom and we call from eclipse:eclipse using the plugin external tools fro eclipse. Thx . -Message d'origine- De : Steffen Mazanek [mailto:[EMAIL PROTECTED] Envoyé : lundi 12 mars 2007 19:01 À : Maven Users List Objet : Re: Maven2 plugin for eclipse mvn eclipse:eclipse? http://maven.apache.org/guides/mini/guide-ide-eclipse.html Hope this helps. Steffen Marouane Amraoui schrieb: I m using Maven2 plugin for eclipse . Version plugin is : 0.0.10. I created a maven project . I added dependency using the plugin. when I add the dependency it only added in pom file and note in eclipse file .classpath this obligate me to do A double work There is a solution for that ??? --- Merouane AMRAOUI Consultant Expert Division Développement Email.: [EMAIL PROTECTED] Gsm .: 065 19 60 99 Tél. | Tel.: 022 98 70 70Téléc | Fax: 022 98 70 70 OMNIDATA , 74 Bv AbdelMoumen - 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: Maven2 plugin for eclipse
Sorry, make sure that you enable the plugin on your project. You have to right-click the project and there should be a Maven2 menu. Select enable. Pete -Original Message- From: Hayes, Peter Sent: Monday, March 12, 2007 3:20 PM To: Maven Users List Subject: RE: Maven2 plugin for eclipse http://m2eclipse.codehaus.org/ This plugin keeps your classpath in synch with your pom file via an Eclipse classpath container. It's very good. -Original Message- From: Marouane Amraoui [mailto:[EMAIL PROTECTED] Sent: Monday, March 12, 2007 2:05 PM To: Maven Users List Subject: Maven2 plugin for eclipse I m using Maven2 plugin for eclipse . Version plugin is : 0.0.10. I created a maven project . I added dependency using the plugin. when I add the dependency it only added in pom file and note in eclipse file .classpath this obligate me to do A double work There is a solution for that ??? --- Merouane AMRAOUI Consultant Expert Division Développement Email.: [EMAIL PROTECTED] Gsm .: 065 19 60 99 Tél. | Tel.: 022 98 70 70Téléc | Fax: 022 98 70 70 OMNIDATA , 74 Bv AbdelMoumen - 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: Maven2 plugin for eclipse
I didn't have enabled my project maven . so If I enable it we don't need to execute eclipse:eclipse inorder to synchronize the pom dependency and .classpth -Message d'origine- De : Hayes, Peter [mailto:[EMAIL PROTECTED] Envoyé : lundi 12 mars 2007 19:22 À : Maven Users List Objet : RE: Maven2 plugin for eclipse Sorry, make sure that you enable the plugin on your project. You have to right-click the project and there should be a Maven2 menu. Select enable. Pete -Original Message- From: Hayes, Peter Sent: Monday, March 12, 2007 3:20 PM To: Maven Users List Subject: RE: Maven2 plugin for eclipse http://m2eclipse.codehaus.org/ This plugin keeps your classpath in synch with your pom file via an Eclipse classpath container. It's very good. -Original Message- From: Marouane Amraoui [mailto:[EMAIL PROTECTED] Sent: Monday, March 12, 2007 2:05 PM To: Maven Users List Subject: Maven2 plugin for eclipse I m using Maven2 plugin for eclipse . Version plugin is : 0.0.10. I created a maven project . I added dependency using the plugin. when I add the dependency it only added in pom file and note in eclipse file .classpath this obligate me to do A double work There is a solution for that ??? --- Merouane AMRAOUI Consultant Expert Division Développement Email.: [EMAIL PROTECTED] Gsm .: 065 19 60 99 Tél. | Tel.: 022 98 70 70Téléc | Fax: 022 98 70 70 OMNIDATA , 74 Bv AbdelMoumen - 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: Maven2 plugin for eclipse
Yes, you will not have to manage the .classpath manually. Make sure to remove any entries defined in there that are now redundant based on the m2eclipse plugin's classpath management. I generally have the following in my .classpath files : ?xml version=1.0 encoding=UTF-8? classpath classpathentry kind=src path=src/main/java/ classpathentry kind=src path=src/main/resources/ classpathentry kind=src path=src/test/java/ classpathentry kind=src path=src/test/resources/ classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/ classpathentry kind=con path=org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER/ classpathentry kind=output path=classes/ /classpath Pete -Original Message- From: Marouane Amraoui [mailto:[EMAIL PROTECTED] Sent: Monday, March 12, 2007 3:31 PM To: Maven Users List Subject: RE: Maven2 plugin for eclipse I didn't have enabled my project maven . so If I enable it we don't need to execute eclipse:eclipse inorder to synchronize the pom dependency and .classpth -Message d'origine- De : Hayes, Peter [mailto:[EMAIL PROTECTED] Envoyé : lundi 12 mars 2007 19:22 À : Maven Users List Objet : RE: Maven2 plugin for eclipse Sorry, make sure that you enable the plugin on your project. You have to right-click the project and there should be a Maven2 menu. Select enable. Pete -Original Message- From: Hayes, Peter Sent: Monday, March 12, 2007 3:20 PM To: Maven Users List Subject: RE: Maven2 plugin for eclipse http://m2eclipse.codehaus.org/ This plugin keeps your classpath in synch with your pom file via an Eclipse classpath container. It's very good. -Original Message- From: Marouane Amraoui [mailto:[EMAIL PROTECTED] Sent: Monday, March 12, 2007 2:05 PM To: Maven Users List Subject: Maven2 plugin for eclipse I m using Maven2 plugin for eclipse . Version plugin is : 0.0.10. I created a maven project . I added dependency using the plugin. when I add the dependency it only added in pom file and note in eclipse file .classpath this obligate me to do A double work There is a solution for that ??? --- Merouane AMRAOUI Consultant Expert Division Développement Email.: [EMAIL PROTECTED] Gsm .: 065 19 60 99 Tél. | Tel.: 022 98 70 70Téléc | Fax: 022 98 70 70 OMNIDATA , 74 Bv AbdelMoumen - 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]
[ANN] Transcoder Maven2 plugin - check completeness of your multilingual resources
Hi.
I've recently release the Transcoder plugin:
https://transcoder.dev.java.net/
I hope you'll find it useful.
Here's a small description.
The Transcoder plugin for Maven2 is used to check multilingual resources for the
completeness of translation. This plugin analyzes property files contained
within the application and reports entries which were not translated into one of
the required languages. Missing entries are written into property files in some
target directory.
In practice, if you develop a multi-lingual project, you may need to be sure
that you've translated all the language entries into all of the required
languages. In case your language resources are distributed among multiple JARs,
this may be hard to do. The Transcoder plugin performs the in-depth check of
your JARs/resources and generates a list of properties yet-to-be-translated.
How is the check performed?
The plugin is configured with a list of languages (locales) and a list of
resource names. It also implicitly knows runtime dependencies of the project. So
the Transcoder plugin checks that:
* for every runtime dependency and every resource name,
* if certain entry exists in resource property file for one of the
configured languages,
* then it exists in resource property files for all of the configured
languages (within the same dependency).
What is the output?
The plugin has the target configuration parameter
${project.build.directory}/missing-resources by default. In case resource file
within some given dependency misses some entries for one of the languages, they
will be written into the
${target}/${groupId}/${artifactId}/${resourceName}_${locale}.properties file.
${target} is the target directory (see above), ${groupId} and ${artifactId} are
the group id and the artifact id of the given dependency, ${resourceName} and
${locale} are current resource name and language.
Example. Consider we're missing the German user.username (locale: de) entry
in the resource de/disy/preludio2/messages of the
de.disy.preludio2:preludio2-shared. In this case we'll get the file
target/missing-resources/de.disy.preludio2/preludio2-shared/de/disy/preludio2/messages_de.properties
containing something like:
user.username=@@TODO.user.username@@
Bye.
/lexi
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Transcoder Maven2 plugin - check completeness of your multilingual resources
Aleksei Valikov wrote: I've recently release the Transcoder plugin: https://transcoder.dev.java.net/ Awesome! I was actually getting ready to work on something like this for md4j-quickstarter [1], although more webapp oriented. Can this be extended to: * Parse a set of JSP (or other presentation technology) files with user-provided regexps to build a set of property keys * Compare these against the property files, to output files with missing or unused property keys If you are interested, i would be happy to give a helping hand :-) [1] http://www.geekologue.com/md4j/tutorial-with-maven.html Cheers, Manos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Transcoder Maven2 plugin - check completeness of your multilingual resources
Hi. I've recently release the Transcoder plugin: https://transcoder.dev.java.net/ Awesome! I was actually getting ready to work on something like this for md4j-quickstarter [1], although more webapp oriented. Can this be extended to: * Parse a set of JSP (or other presentation technology) files with user-provided regexps to build a set of property keys * Compare these against the property files, to output files with missing or unused property keys If you are interested, i would be happy to give a helping hand :-) [1] http://www.geekologue.com/md4j/tutorial-with-maven.html Thanks! Well, this surely can be extended. I just wanted to start with a small and simple but yet complete thing. The plugin now just checks resources for cross-language completeness. That is, the set of keys per dependency/resource name is calculated as a set of all keys in all languages for that dependency/resource. This is just one algorithm to calculate this set. You are right, there must be much more of them. Like, parsing JSPs/Java code/Facelets templates/whatever. I think I'll make these algorithms extensible/pluggable and probably start with the Java code parsing (this is what I need for my projects). You are welcome to join the project and do the JSP parsing as you see it. Bye. /lexi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Transcoder Maven2 plugin - check completeness of your multilingual resources
Aleksei Valikov wrote: You are welcome to join the project and do the JSP parsing as you see it. Request sent, thanks for sharing :-) Cheers, Manos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: I need help with cargo-maven2-plugin.
Can someone point me to an example of cargo-maven2-plugin use case? Many Thanks Maruf Maruf Aytekin wrote: Hi All, I need help with cargo-maven2-plugin. I have jboss-4.0.5.GA installed on my testcip server. I am trying to deploy a war webapp to jboss with cargo-maven-plugin. Related part of the pom.xml is below: build plugin groupIdorg.codehaus.cargo/groupId artifactIdcargo-maven2-plugin/artifactId version0.2/version configuration container containerIdjboss4x/containerId typeremote/type /container configuration typeruntime/type properties cargo.hostnametestcip/cargo.hostname cargo.servlet.port8080/cargo.servlet.port cargo.rmi.port8009/cargo.rmi.port /properties /configuration deployer typeremote/type deployables deployable groupIdcom.aspone.baydonhill.customer/groupId artifactIdbaydonline/artifactId typewar/type /deployable /deployables /deployer /configuration /plugin /plugins /build The produced artifact is located under c:/baydonhill/customer/target/ directory. It seems plugin cannot see file:C%3A%5Cbaydonhill%5Ccustomer%5Ctarget%5Cbaydonline-1.0-SNAPSHOT.war. I am using windows XP and Maven version: 2.0.4. I am not sure what I am doing wrong? I am getting the following exception: Many thanks in advance. Maruf C:\baydonhill\customermvn -e cargo:deploy + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'cargo'. [INFO] - --- [INFO] Building Baydonline webapp [INFO]task-segment: [cargo:deploy] [INFO] - --- [INFO] [cargo:deploy] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Failed to deploy to [http://testcip:8080/jmx-console/HtmlAdaptor?action=i nvokeOpByNamename=jboss.system:service%3DMainDeployermethodName=deployargType =java.net.URLarg0=file:C%3A%5Cbaydonhill%5Ccustomer%5Ctarget%5Cbaydonline-1.0-S NAPSHOT.war] Server returned HTTP response code: 500 for URL: http://testcip:8080/jmx-console /HtmlAdaptor?action=invokeOpByNamename=jboss.system:service%3DMainDeployermeth odName=deployargType=java.net.URLarg0=file:C%3A%5Cbaydonhill%5Ccustomer%5Ctarg et%5Cbaydonline-1.0-SNAPSHOT.war [INFO] [INFO] Trace org.codehaus.cargo.container.ContainerException: Failed to deploy to [http://tes tcip:8080/jmx-console/HtmlAdaptor?action=invokeOpByNamename=jboss.system:servic e%3DMainDeployermethodName=deployargType=java.net.URLarg0=file:C%3A%5Cbaydonh ill%5Ccustomer%5Ctarget%5Cbaydonline-1.0-SNAPSHOT.war] at org.codehaus.cargo.container.jboss.internal.JdkHttpURLConnection.conn ect(JdkHttpURLConnection.java:57) at org.codehaus.cargo.container.jboss.JBossJMXDeployer.invokeURL(JBossJM XDeployer.java:154) at org.codehaus.cargo.container.jboss.JBossJMXDeployer.deploy(JBossJMXDe - 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]
cargo-maven2-plugin containerIdjbos4x/containerId
Hi All, I need an example usage of cargo-maven2-plugin. Can someone point me to an example usage for remote deployment on runtime? I have seen http://cargo.codehaus.org/Home it's not helping much. I tried everything on that page but still getting exceptions. Many thanks in advance, Maruf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: I need help with cargo-maven2-plugin.
Perhaps you should take this email to the Cargo Users mailing list? Wayne On 2/14/07, Maruf Aytekin [EMAIL PROTECTED] wrote: Can someone point me to an example of cargo-maven2-plugin use case? Many Thanks Maruf Maruf Aytekin wrote: Hi All, I need help with cargo-maven2-plugin. I have jboss-4.0.5.GA installed on my testcip server. I am trying to deploy a war webapp to jboss with cargo-maven-plugin. Related part of the pom.xml is below: build plugin groupIdorg.codehaus.cargo/groupId artifactIdcargo-maven2-plugin/artifactId version0.2/version configuration container containerIdjboss4x/containerId typeremote/type /container configuration typeruntime/type properties cargo.hostnametestcip/cargo.hostname cargo.servlet.port8080/cargo.servlet.port cargo.rmi.port8009/cargo.rmi.port /properties /configuration deployer typeremote/type deployables deployable groupIdcom.aspone.baydonhill.customer/groupId artifactIdbaydonline/artifactId typewar/type /deployable /deployables /deployer /configuration /plugin /plugins /build The produced artifact is located under c:/baydonhill/customer/target/ directory. It seems plugin cannot see file:C%3A%5Cbaydonhill%5Ccustomer%5Ctarget%5Cbaydonline-1.0-SNAPSHOT.war. I am using windows XP and Maven version: 2.0.4. I am not sure what I am doing wrong? I am getting the following exception: Many thanks in advance. Maruf C:\baydonhill\customermvn -e cargo:deploy + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'cargo'. [INFO] - --- [INFO] Building Baydonline webapp [INFO]task-segment: [cargo:deploy] [INFO] - --- [INFO] [cargo:deploy] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Failed to deploy to [http://testcip:8080/jmx-console/HtmlAdaptor?action=i nvokeOpByNamename=jboss.system:service%3DMainDeployermethodName=deployargType =java.net.URLarg0=file:C%3A%5Cbaydonhill%5Ccustomer%5Ctarget%5Cbaydonline-1.0-S NAPSHOT.war] Server returned HTTP response code: 500 for URL: http://testcip:8080/jmx-console /HtmlAdaptor?action=invokeOpByNamename=jboss.system:service%3DMainDeployermeth odName=deployargType=java.net.URLarg0=file:C%3A%5Cbaydonhill%5Ccustomer%5Ctarg et%5Cbaydonline-1.0-SNAPSHOT.war [INFO] [INFO] Trace org.codehaus.cargo.container.ContainerException: Failed to deploy to [http://tes tcip:8080/jmx-console/HtmlAdaptor?action=invokeOpByNamename=jboss.system:servic e%3DMainDeployermethodName=deployargType=java.net.URLarg0=file:C%3A%5Cbaydonh ill%5Ccustomer%5Ctarget%5Cbaydonline-1.0-SNAPSHOT.war] at org.codehaus.cargo.container.jboss.internal.JdkHttpURLConnection.conn ect(JdkHttpURLConnection.java:57) at org.codehaus.cargo.container.jboss.JBossJMXDeployer.invokeURL(JBossJM XDeployer.java:154) at org.codehaus.cargo.container.jboss.JBossJMXDeployer.deploy(JBossJMXDe - 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]
I need help with cargo-maven2-plugin.
Hi All, I need help with cargo-maven2-plugin. I have jboss-4.0.5.GA installed on my testcip server. I am trying to deploy a war webapp to jboss with cargo-maven-plugin. Related part of the pom.xml is below: build plugin groupIdorg.codehaus.cargo/groupId artifactIdcargo-maven2-plugin/artifactId version0.2/version configuration container containerIdjboss4x/containerId typeremote/type /container configuration typeruntime/type properties cargo.hostnametestcip/cargo.hostname cargo.servlet.port8080/cargo.servlet.port cargo.rmi.port8009/cargo.rmi.port /properties /configuration deployer typeremote/type deployables deployable groupIdcom.aspone.baydonhill.customer/groupId artifactIdbaydonline/artifactId typewar/type /deployable /deployables /deployer /configuration /plugin /plugins /build The produced artifact is located under c:/baydonhill/customer/target/ directory. It seems plugin cannot see file:C%3A%5Cbaydonhill%5Ccustomer%5Ctarget%5Cbaydonline-1.0-SNAPSHOT.war. I am using windows XP and Maven version: 2.0.4. I am not sure what I am doing wrong? I am getting the following exception: Many thanks in advance. Maruf C:\baydonhill\customermvn -e cargo:deploy + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'cargo'. [INFO] - --- [INFO] Building Baydonline webapp [INFO]task-segment: [cargo:deploy] [INFO] - --- [INFO] [cargo:deploy] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Failed to deploy to [http://testcip:8080/jmx-console/HtmlAdaptor?action=i nvokeOpByNamename=jboss.system:service%3DMainDeployermethodName=deployargType =java.net.URLarg0=file:C%3A%5Cbaydonhill%5Ccustomer%5Ctarget%5Cbaydonline-1.0-S NAPSHOT.war] Server returned HTTP response code: 500 for URL: http://testcip:8080/jmx-console /HtmlAdaptor?action=invokeOpByNamename=jboss.system:service%3DMainDeployermeth odName=deployargType=java.net.URLarg0=file:C%3A%5Cbaydonhill%5Ccustomer%5Ctarg et%5Cbaydonline-1.0-SNAPSHOT.war [INFO] [INFO] Trace org.codehaus.cargo.container.ContainerException: Failed to deploy to [http://tes tcip:8080/jmx-console/HtmlAdaptor?action=invokeOpByNamename=jboss.system:servic e%3DMainDeployermethodName=deployargType=java.net.URLarg0=file:C%3A%5Cbaydonh ill%5Ccustomer%5Ctarget%5Cbaydonline-1.0-SNAPSHOT.war] at org.codehaus.cargo.container.jboss.internal.JdkHttpURLConnection.conn ect(JdkHttpURLConnection.java:57) at org.codehaus.cargo.container.jboss.JBossJMXDeployer.invokeURL(JBossJM XDeployer.java:154) at org.codehaus.cargo.container.jboss.JBossJMXDeployer.deploy(JBossJMXDe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: xdoclet2 maven2 plugin
Hi, http://repo1.maven.org/maven2/org/codehaus/mojo/xdoclet-maven-plugin/ Try with plugin artifactIdxdoclet-maven-plugin/artifactId groupIdorg.codehaus.mojo/groupId version1.0-alpha-2/version ... /plugin Look http://mojo.codehaus.org/xdoclet-maven-plugin/usage.html I think http://xdoclet.codehaus.org/Maven2+plugin is not up to date. -- Olivier -Message d'origine- De : nicolas de loof [mailto:[EMAIL PROTECTED] Envoyé : mercredi 10 janvier 2007 08:52 À : Maven Users List Objet : xdoclet2 maven2 plugin Hello, According to http://xdoclet.codehaus.org/Maven2+plugin, the xdoclet2 plugin for maven2 can be downloaded from http://dist.codehaus.org/xdoclet/maven-plugins/. This folder contains both a SNAPSHOT and a 2.0.5.jar. Is this plugin ready for production ? Why isn't it deployed on public maven repository ? Nico. This e-mail, any attachments and the information contained therein (this message) are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. -- Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après le message ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: xdoclet2 maven2 plugin
Thanks ! the mojo is for xDoclet, not xDoclet2. Is there active dev on xDoclet2 ? Nico. Le 10/01/07, LAMY Olivier [EMAIL PROTECTED] a écrit : Hi, http://repo1.maven.org/maven2/org/codehaus/mojo/xdoclet-maven-plugin/ Try with plugin artifactIdxdoclet-maven-plugin/artifactId groupIdorg.codehaus.mojo/groupId version1.0-alpha-2/version ... /plugin Look http://mojo.codehaus.org/xdoclet-maven-plugin/usage.html I think http://xdoclet.codehaus.org/Maven2+plugin is not up to date. -- Olivier -Message d'origine- De : nicolas de loof [mailto:[EMAIL PROTECTED] Envoyé : mercredi 10 janvier 2007 08:52 À : Maven Users List Objet : xdoclet2 maven2 plugin Hello, According to http://xdoclet.codehaus.org/Maven2+plugin, the xdoclet2 plugin for maven2 can be downloaded from http://dist.codehaus.org/xdoclet/maven-plugins/. This folder contains both a SNAPSHOT and a 2.0.5.jar. Is this plugin ready for production ? Why isn't it deployed on public maven repository ? Nico. This e-mail, any attachments and the information contained therein (this message) are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. -- Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après le message ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: xdoclet2 maven2 plugin
I don't know, I use xDoclet. Ask mojo ML or xdoclet ML. -- Olivier -Message d'origine- De : nicolas de loof [mailto:[EMAIL PROTECTED] Envoyé : mercredi 10 janvier 2007 09:14 À : Maven Users List Objet : Re: xdoclet2 maven2 plugin Thanks ! the mojo is for xDoclet, not xDoclet2. Is there active dev on xDoclet2 ? Nico. Le 10/01/07, LAMY Olivier [EMAIL PROTECTED] a écrit : Hi, http://repo1.maven.org/maven2/org/codehaus/mojo/xdoclet-maven-plugin/ Try with plugin artifactIdxdoclet-maven-plugin/artifactId groupIdorg.codehaus.mojo/groupId version1.0-alpha-2/version ... /plugin Look http://mojo.codehaus.org/xdoclet-maven-plugin/usage.html I think http://xdoclet.codehaus.org/Maven2+plugin is not up to date. -- Olivier -Message d'origine- De : nicolas de loof [mailto:[EMAIL PROTECTED] Envoyé : mercredi 10 janvier 2007 08:52 À : Maven Users List Objet : xdoclet2 maven2 plugin Hello, According to http://xdoclet.codehaus.org/Maven2+plugin, the xdoclet2 plugin for maven2 can be downloaded from http://dist.codehaus.org/xdoclet/maven-plugins/. This folder contains both a SNAPSHOT and a 2.0.5.jar. Is this plugin ready for production ? Why isn't it deployed on public maven repository ? Nico. This e-mail, any attachments and the information contained therein (this message) are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. -- Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après le message ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites. -- --- - 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: xdoclet2 maven2 plugin
Hi,
i have tried to use xdoclet2 plugin for hibernate
here's how i m using it
plugin
groupIdxdoclet/groupId
artifactIdmaven2-xdoclet2-plugin/artifactId
version2.0.5/version
executions
execution
idxdoclet/id
phaseprocess-classes/phase
goals
goalxdoclet/goal
/goals
/execution
/executions
dependencies
dependency
groupIdxdoclet-plugins/groupId
artifactIdxdoclet-plugin-hibernate/artifactId
version1.0.4-SNAPSHOT/version
/dependency
/dependencies
configuration
configs
config
components
component
classname
org.xdoclet.plugin.hibernate.HibernateMappingPlugin/classname
params
version3.0/version
destdir${project.build.outputDirectory}/destdir
/params
/component
/components
/config
/configs
/configuration
/plugin
i suppose other uses are similar
hth
marco
PS got a problem wit 2.0.5-SNAPSHOT last wkend... i was suggested to move to
2.0.5
On 1/10/07, nicolas de loof [EMAIL PROTECTED] wrote:
Thanks !
the mojo is for xDoclet, not xDoclet2.
Is there active dev on xDoclet2 ?
Nico.
Le 10/01/07, LAMY Olivier [EMAIL PROTECTED] a écrit :
Hi,
http://repo1.maven.org/maven2/org/codehaus/mojo/xdoclet-maven-plugin/
Try with
plugin
artifactIdxdoclet-maven-plugin/artifactId
groupIdorg.codehaus.mojo/groupId
version1.0-alpha-2/version
...
/plugin
Look http://mojo.codehaus.org/xdoclet-maven-plugin/usage.html
I think http://xdoclet.codehaus.org/Maven2+plugin is not up to date.
--
Olivier
-Message d'origine-
De : nicolas de loof [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 10 janvier 2007 08:52
À : Maven Users List
Objet : xdoclet2 maven2 plugin
Hello,
According to http://xdoclet.codehaus.org/Maven2+plugin, the xdoclet2
plugin for maven2 can be downloaded from
http://dist.codehaus.org/xdoclet/maven-plugins/.
This folder contains both a SNAPSHOT and a 2.0.5.jar. Is this plugin
ready for production ? Why isn't it deployed on public maven repository
?
Nico.
This e-mail, any attachments and the information contained therein
(this
message) are confidential and intended solely for the use of the
addressee(s). If you have received this message in error please send it
back
to the sender and delete it. Unauthorized publication, use,
dissemination or
disclosure of this message, either in whole or in part is strictly
prohibited.
--
Ce message électronique et tous les fichiers joints ainsi que les
informations contenues dans ce message ( ci après le message ), sont
confidentiels et destinés exclusivement à l'usage de la personne à
laquelle
ils sont adressés. Si vous avez reçu ce message par erreur, merci de le
renvoyer à son émetteur et de le détruire. Toutes diffusion,
publication,
totale ou partielle ou divulgation sous quelque forme que se soit non
expressément autorisées de ce message, sont interdites.
-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: xdoclet2 maven2 plugin
Thanks a lot for code sample.
2007/1/10, Marco Mistroni [EMAIL PROTECTED]:
Hi,
i have tried to use xdoclet2 plugin for hibernate
here's how i m using it
plugin
groupIdxdoclet/groupId
artifactIdmaven2-xdoclet2-plugin/artifactId
version2.0.5/version
executions
execution
idxdoclet/id
phaseprocess-classes/phase
goals
goalxdoclet/goal
/goals
/execution
/executions
dependencies
dependency
groupIdxdoclet-plugins/groupId
artifactIdxdoclet-plugin-hibernate/artifactId
version1.0.4-SNAPSHOT/version
/dependency
/dependencies
configuration
configs
config
components
component
classname
org.xdoclet.plugin.hibernate.HibernateMappingPlugin/classname
params
version3.0/version
destdir${project.build.outputDirectory}/destdir
/params
/component
/components
/config
/configs
/configuration
/plugin
i suppose other uses are similar
hth
marco
PS got a problem wit 2.0.5-SNAPSHOT last wkend... i was suggested to move
to
2.0.5
On 1/10/07, nicolas de loof [EMAIL PROTECTED] wrote:
Thanks !
the mojo is for xDoclet, not xDoclet2.
Is there active dev on xDoclet2 ?
Nico.
Le 10/01/07, LAMY Olivier [EMAIL PROTECTED] a écrit :
Hi,
http://repo1.maven.org/maven2/org/codehaus/mojo/xdoclet-maven-plugin/
Try with
plugin
artifactIdxdoclet-maven-plugin/artifactId
groupIdorg.codehaus.mojo/groupId
version1.0-alpha-2/version
...
/plugin
Look http://mojo.codehaus.org/xdoclet-maven-plugin/usage.html
I think http://xdoclet.codehaus.org/Maven2+plugin is not up to date.
--
Olivier
-Message d'origine-
De : nicolas de loof [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 10 janvier 2007 08:52
À : Maven Users List
Objet : xdoclet2 maven2 plugin
Hello,
According to http://xdoclet.codehaus.org/Maven2+plugin, the xdoclet2
plugin for maven2 can be downloaded from
http://dist.codehaus.org/xdoclet/maven-plugins/.
This folder contains both a SNAPSHOT and a 2.0.5.jar. Is this plugin
ready for production ? Why isn't it deployed on public maven
repository
?
Nico.
This e-mail, any attachments and the information contained therein
(this
message) are confidential and intended solely for the use of the
addressee(s). If you have received this message in error please send
it
back
to the sender and delete it. Unauthorized publication, use,
dissemination or
disclosure of this message, either in whole or in part is strictly
prohibited.
--
Ce message électronique et tous les fichiers joints ainsi que les
informations contenues dans ce message ( ci après le message ), sont
confidentiels et destinés exclusivement à l'usage de la personne à
laquelle
ils sont adressés. Si vous avez reçu ce message par erreur, merci de
le
renvoyer à son émetteur et de le détruire. Toutes diffusion,
publication,
totale ou partielle ou divulgation sous quelque forme que se soit non
expressément autorisées de ce message, sont interdites.
-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: xdoclet2 maven2 plugin
hello,
u r welcome
if by any chance u get it to work with ejbdodclet and webdoclet could you
post your pom.xml? i'd need to convert my existing projects to use m2 xd2
plugin.. but right now i am busy with ohter stuff
regards
marco
On 1/10/07, nicolas de loof [EMAIL PROTECTED] wrote:
Thanks a lot for code sample.
2007/1/10, Marco Mistroni [EMAIL PROTECTED]:
Hi,
i have tried to use xdoclet2 plugin for hibernate
here's how i m using it
plugin
groupIdxdoclet/groupId
artifactIdmaven2-xdoclet2-plugin/artifactId
version2.0.5/version
executions
execution
idxdoclet/id
phaseprocess-classes/phase
goals
goalxdoclet/goal
/goals
/execution
/executions
dependencies
dependency
groupIdxdoclet-plugins/groupId
artifactIdxdoclet-plugin-hibernate/artifactId
version1.0.4-SNAPSHOT/version
/dependency
/dependencies
configuration
configs
config
components
component
classname
org.xdoclet.plugin.hibernate.HibernateMappingPlugin/classname
params
version3.0/version
destdir${project.build.outputDirectory}/destdir
/params
/component
/components
/config
/configs
/configuration
/plugin
i suppose other uses are similar
hth
marco
PS got a problem wit 2.0.5-SNAPSHOT last wkend... i was suggested to
move
to
2.0.5
On 1/10/07, nicolas de loof [EMAIL PROTECTED] wrote:
Thanks !
the mojo is for xDoclet, not xDoclet2.
Is there active dev on xDoclet2 ?
Nico.
Le 10/01/07, LAMY Olivier [EMAIL PROTECTED] a écrit :
Hi,
http://repo1.maven.org/maven2/org/codehaus/mojo/xdoclet-maven-plugin/
Try with
plugin
artifactIdxdoclet-maven-plugin/artifactId
groupIdorg.codehaus.mojo/groupId
version1.0-alpha-2/version
...
/plugin
Look http://mojo.codehaus.org/xdoclet-maven-plugin/usage.html
I think http://xdoclet.codehaus.org/Maven2+plugin is not up to
date.
--
Olivier
-Message d'origine-
De : nicolas de loof [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 10 janvier 2007 08:52
À : Maven Users List
Objet : xdoclet2 maven2 plugin
Hello,
According to http://xdoclet.codehaus.org/Maven2+plugin, the xdoclet2
plugin for maven2 can be downloaded from
http://dist.codehaus.org/xdoclet/maven-plugins/.
This folder contains both a SNAPSHOT and a 2.0.5.jar. Is this
plugin
ready for production ? Why isn't it deployed on public maven
repository
?
Nico.
This e-mail, any attachments and the information contained therein
(this
message) are confidential and intended solely for the use of the
addressee(s). If you have received this message in error please send
it
back
to the sender and delete it. Unauthorized publication, use,
dissemination or
disclosure of this message, either in whole or in part is strictly
prohibited.
--
Ce message électronique et tous les fichiers joints ainsi que les
informations contenues dans ce message ( ci après le message ),
sont
confidentiels et destinés exclusivement à l'usage de la personne à
laquelle
ils sont adressés. Si vous avez reçu ce message par erreur,
merci de
le
renvoyer à son émetteur et de le détruire. Toutes diffusion,
publication,
totale ou partielle ou divulgation sous quelque forme que se soit
non
expressément autorisées de ce message, sont interdites.
-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: xdoclet2 maven2 plugin
I'd like to use xDoclet for Hibernate. My project has no ejb and the web is
hand-made, so I'll have no chance to test ejbdodclet or webdoclet.
I now have to convince my customer to use xDoclet to generate hibernate
mapping files, as he prefers hibernate-tools to be used from Eclipse.
2007/1/10, Marco Mistroni [EMAIL PROTECTED]:
hello,
u r welcome
if by any chance u get it to work with ejbdodclet and webdoclet could you
post your pom.xml? i'd need to convert my existing projects to use m2 xd2
plugin.. but right now i am busy with ohter stuff
regards
marco
On 1/10/07, nicolas de loof [EMAIL PROTECTED] wrote:
Thanks a lot for code sample.
2007/1/10, Marco Mistroni [EMAIL PROTECTED]:
Hi,
i have tried to use xdoclet2 plugin for hibernate
here's how i m using it
plugin
groupIdxdoclet/groupId
artifactIdmaven2-xdoclet2-plugin/artifactId
version2.0.5/version
executions
execution
idxdoclet/id
phaseprocess-classes/phase
goals
goalxdoclet/goal
/goals
/execution
/executions
dependencies
dependency
groupIdxdoclet-plugins/groupId
artifactIdxdoclet-plugin-hibernate/artifactId
version1.0.4-SNAPSHOT/version
/dependency
/dependencies
configuration
configs
config
components
component
classname
org.xdoclet.plugin.hibernate.HibernateMappingPlugin/classname
params
version3.0/version
destdir${project.build.outputDirectory
}/destdir
/params
/component
/components
/config
/configs
/configuration
/plugin
i suppose other uses are similar
hth
marco
PS got a problem wit 2.0.5-SNAPSHOT last wkend... i was suggested to
move
to
2.0.5
On 1/10/07, nicolas de loof [EMAIL PROTECTED] wrote:
Thanks !
the mojo is for xDoclet, not xDoclet2.
Is there active dev on xDoclet2 ?
Nico.
Le 10/01/07, LAMY Olivier [EMAIL PROTECTED] a écrit :
Hi,
http://repo1.maven.org/maven2/org/codehaus/mojo/xdoclet-maven-plugin/
Try with
plugin
artifactIdxdoclet-maven-plugin/artifactId
groupIdorg.codehaus.mojo/groupId
version1.0-alpha-2/version
...
/plugin
Look http://mojo.codehaus.org/xdoclet-maven-plugin/usage.html
I think http://xdoclet.codehaus.org/Maven2+plugin is not up to
date.
--
Olivier
-Message d'origine-
De : nicolas de loof [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 10 janvier 2007 08:52
À : Maven Users List
Objet : xdoclet2 maven2 plugin
Hello,
According to http://xdoclet.codehaus.org/Maven2+plugin, the
xdoclet2
plugin for maven2 can be downloaded from
http://dist.codehaus.org/xdoclet/maven-plugins/.
This folder contains both a SNAPSHOT and a 2.0.5.jar. Is this
plugin
ready for production ? Why isn't it deployed on public maven
repository
?
Nico.
This e-mail, any attachments and the information contained therein
(this
message) are confidential and intended solely for the use of the
addressee(s). If you have received this message in error please
send
it
back
to the sender and delete it. Unauthorized publication, use,
dissemination or
disclosure of this message, either in whole or in part is strictly
prohibited.
--
Ce message électronique et tous les fichiers joints ainsi que les
informations contenues dans ce message ( ci après le message ),
sont
confidentiels et destinés exclusivement à l'usage de la personne
à
laquelle
ils sont adressés. Si vous avez reçu ce message par erreur,
merci de
le
renvoyer à son émetteur et de le détruire. Toutes diffusion,
publication,
totale ou partielle ou divulgation sous quelque forme que se soit
non
expressément autorisées de ce message, sont interdites.
-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
xdoclet2 maven2 plugin
Hello, According to http://xdoclet.codehaus.org/Maven2+plugin, the xdoclet2 plugin for maven2 can be downloaded from http://dist.codehaus.org/xdoclet/maven-plugins/. This folder contains both a SNAPSHOT and a 2.0.5.jar. Is this plugin ready for production ? Why isn't it deployed on public maven repository ? Nico.
RE: Additional features for maven2 plugin
Thank you all for your answers, My intention was to have the ability configure the versions of the dependencies before the building, using a GUI. For example, when selecting to build using the eclipse maven plugin, the eclipse plugin will open a configuration dialog that contains for each dependency a combo box with all the available versions. After the user selects the versions, it presses on the 'build' button in this dialog and this will cause the new versions to take affect (propogate them to the maven) and only then continue with the building process. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 01, 2006 8:30 AM To: Maven Users List Subject: Re: Additional features for maven2 plugin Defining the version for a dependency is one of the base features of Maven: dependency artifactId/ groupId/ scope/ version[2.0.8]/version /dependency The [x.y.z] notation locks the artifact to that version. Use [x.y.z, ) to force a minimum but no maximum on the version number ie if a new feature is added in build 3.1.2 that you require for your code to work, etc. Is this not working for you, do you have some other requirement(s) which are not currently available, or what? Wayne On 11/1/06, Rahamim, Zvi (Zvi) [EMAIL PROTECTED] wrote: Hi, I think that a very important feature is to have the ability to define, before maven starts building, the versions of the dependencies. Is there an intention to add this feature? Thanks! Zvi. - 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]
Additional features for maven2 plugin
Hi, I think that a very important feature is to have the ability to define, before maven starts building, the versions of the dependencies. Is there an intention to add this feature? Thanks! Zvi. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Additional features for maven2 plugin
Maven already requires you to define the versions for all of your dependencies before it builds: http://maven.apache.org/pom.html#Dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version4.0/version /dependency If you mean something else, please describe it more clearly, perhaps with an example. -Max On Wed, 2006-11-01 at 08:13 +0200, Rahamim, Zvi (Zvi) wrote: Hi, I think that a very important feature is to have the ability to define, before maven starts building, the versions of the dependencies. Is there an intention to add this feature? Thanks! Zvi. - 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]
Maven2 Plugin Ant or Java
Hi All, Ejaz has made available some code that wraps webtest as a Maven 2 Ant Plugin. Whilst I am very grateful to Ejaz for his code I had expected it to be a native Maven 2 Java Plugin. All the Maven Plugins that I have written have been in Java. So my question is does anybody have any opinions; ant or java? Java would involve plugging into the webtest api behind the Ant layer. Is this a good or bad thing to do or is webtest bound tightly to Ant. I guess if it is bound tightly to Ant Ejaz's Maven Ant plugin may be the way to go. If it has been designed to be loosely coupled then maybe I should look at writing Java version. Best Regards Peter Anning Sr. Developer www.dialectsolutions.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven2 Plugin Ant or Java
Hi Peter, a Canoo WebTest script is actually an ANT script using custom tags, i.e. you must run ANT to execute Canoo WebTest. The best what you can do is a Java implementation invoking ANT to run the tests. Cheers, Siegfried Goeschl Peter Anning wrote: Hi All, Ejaz has made available some code that wraps webtest as a Maven 2 Ant Plugin. Whilst I am very grateful to Ejaz for his code I had expected it to be a native Maven 2 Java Plugin. All the Maven Plugins that I have written have been in Java. So my question is does anybody have any opinions; ant or java? Java would involve plugging into the webtest api behind the Ant layer. Is this a good or bad thing to do or is webtest bound tightly to Ant. I guess if it is bound tightly to Ant Ejaz's Maven Ant plugin may be the way to go. If it has been designed to be loosely coupled then maybe I should look at writing Java version. Best Regards Peter Anning Sr. Developer www.dialectsolutions.com - 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]
Equivalent of One-Jar as Maven2 plugin
I was trying to deliver my Maven2-built desktop application as a single executable JAR with all dependencies included (using Assembly plugin) when I realized that the default classloading mechanism doesn't allow it. I had a look à One-Jar (http://one-jar.sourceforge.net/) and I was told that UberJar did that for Maven1. Is there an equivalent for this kind of use with Maven2? -- Sébastien Arbogast http://www.sebastien-arbogast.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Equivalent of One-Jar as Maven2 plugin
El 16/10/2006 18:08, Sebastien Arbogast escribió:
I was trying to deliver my Maven2-built desktop application as a
single executable JAR with all dependencies included (using Assembly
plugin) when I realized that the default classloading mechanism
doesn't allow it. I had a look à One-Jar
(http://one-jar.sourceforge.net/) and I was told that UberJar did that
for Maven1.
Is there an equivalent for this kind of use with Maven2?
I also looked for a one-jar plug-in, and I didn't find it. Instead, I
used assembly plug-in with these files:
--- pom.xml (into build):
plugins
!-- Propiedades de assembly --
plugin
artifactIdmaven-assembly-plugin/artifactId
executions
execution
phasepackage/phase
goalsgoalsingle/goal/goals
configuration
descriptors
descriptorsrc/main/assembly/assembly-bin.xml/descriptor
/descriptors
outputDirectorytarget/distrib/outputDirectory
appendAssemblyIdtrue/appendAssemblyId
archive
manifestFilesrc/main/assembly/manifest/boot-manifest.mf/manifestFile
/archive
/configuration
/execution
/executions
/plugin
!-- Manifest --
plugin
artifactIdmaven-jar-plugin/artifactId
configuration
archive
manifest
mainClassX [[[your main
class]]]/mainClass
addClasspathtrue/addClasspath
/manifest
/archive
/configuration
/plugin
/plugins
- pom.xml (dependencies)
dependency
groupIdcom.simontuffs/groupId
artifactIdone-jar-boot/artifactId
version0.95/version
scoperuntime/scope
/dependency
- src/main/assembly/assembly-bin.xml
?xml version=1.0 encoding=ISO-8859-1?
assembly
idall/id
formats
formatjar/format
/formats
includeBaseDirectoryfalse/includeBaseDirectory
dependencySets
dependencySet
excludes
excludecom.simontuffs:one-jar-boot/exclude
exclude${project.groupId}:${project.artifactId}/exclude
/excludes
outputDirectory/lib/outputDirectory
unpackfalse/unpack
scoperuntime/scope
/dependencySet
dependencySet
includes
include${project.groupId}:${project.artifactId}/include
/includes
outputDirectory/main/outputDirectory
unpackfalse/unpack
scoperuntime/scope
/dependencySet
dependencySet
includes
includecom.simontuffs:one-jar-boot/include
/includes
outputDirectory//outputDirectory
unpacktrue/unpack
scoperuntime/scope
/dependencySet
/dependencySets
/assembly
- src/main/assembly/manifest/boot-manifest.mf
Manifest-Version: 1.0
Main-Class: com.simontuffs.onejar.Boot
Class-Path: . config/. ../config/. ../.
Additional files / actions:
* Deploy One-Jar into your repository (I didn't find it in ibiblio)
Nonetheless, it would be great if a one-jar plug-in exist!
Hope it helps,
Andrés Viedma
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
