Re: Default Schedule do not work
do you have an exception or something in your logs? Mac-Systems a écrit : Actually i have 3 Builds running none is running any more. I have a SVN trunk and two branches in schedule. I configured Continuum that all are using the default schedule ... Why cannot Continuum not do this ? Iterate over all Projects an invoke the build (mabye a bit naive impl.). May there are issues that a simple iteration over all Project takes to long ? Also how many schedules do you have? If I remember it correctly, Continuum 1.0.3 doesn't work well with more than one schedule in some case. Emmanuel Mac-Systems a écrit : Anyone can help ??? Hello, Actually my Continuum (1.0.3) does not build anything which is Scheduled but i use the default schedule. Anyone can help correct this ? best regards, Jens
Re: Continuum 1.1.0-beta-2 UI performance
Damien Lecan a écrit : Hello, I've just installed Continuum 1.1.0-beta-2 to replace my old Continuum 1.0.3 instance. I'm working with MySql instead of embbeded sql server and with Tomcat 5.5.17 Nice new features, but UI is very, very, very slow :( I followed http://docs.codehaus.org/display/CONTINUUMUSER/Continuum+on+MySQL and http://docs.codehaus.org/display/CONTINUUMUSER/Continuum+on+Tomcat for installation. Everything works fine, but very, very slowly. For example, each item on the left menu appears one after the other. Same thing when displaying project group information. Each module name appears one after the other (25s for a 17 modules project). 25s for 17 modules??? With embedded derby database we have better performance (http://maven.zones.apache.org/continuum/) and all appears at the same time Are you sure you use the right jdbc driver? MySql database is shared with other Java applications. They work fine, with expected performances. What can be the problem ? Thanks Damien Lecan
Re: Continuum 1.1.0-beta-2 UI performance
I am using derby out of the box and noticed the same slowdown. I don't have any metrics to back it up but its definitely noticeably slower. -Justin Emmanuel Venisse wrote: Damien Lecan a écrit : Hello, I've just installed Continuum 1.1.0-beta-2 to replace my old Continuum 1.0.3 instance. I'm working with MySql instead of embbeded sql server and with Tomcat 5.5.17 Nice new features, but UI is very, very, very slow :( I followed http://docs.codehaus.org/display/CONTINUUMUSER/Continuum+on+MySQL and http://docs.codehaus.org/display/CONTINUUMUSER/Continuum+on+Tomcat for installation. Everything works fine, but very, very slowly. For example, each item on the left menu appears one after the other. Same thing when displaying project group information. Each module name appears one after the other (25s for a 17 modules project). 25s for 17 modules??? With embedded derby database we have better performance (http://maven.zones.apache.org/continuum/) and all appears at the same time Are you sure you use the right jdbc driver? MySql database is shared with other Java applications. They work fine, with expected performances. What can be the problem ? Thanks Damien Lecan !DSPAM:4007,46dd7d79203981439371379! -- Justin Deoliveira The Open Planning Project http://topp.openplans.org
RE: Continuum 1.1.0-beta-2 UI performance
Same problem with me. Slow UI. I had this problem as soon as I upgraded to the newer version of continuum. I thought it was a problem in my system, but now I know its something to do with the new version of continuum. Mrinal -Original Message- From: Justin Deoliveira [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 04, 2007 5:49 PM To: continuum-users@maven.apache.org Subject: Re: Continuum 1.1.0-beta-2 UI performance I am using derby out of the box and noticed the same slowdown. I don't have any metrics to back it up but its definitely noticeably slower. -Justin Emmanuel Venisse wrote: Damien Lecan a écrit : Hello, I've just installed Continuum 1.1.0-beta-2 to replace my old Continuum 1.0.3 instance. I'm working with MySql instead of embbeded sql server and with Tomcat 5.5.17 Nice new features, but UI is very, very, very slow :( I followed http://docs.codehaus.org/display/CONTINUUMUSER/Continuum+on+MySQL and http://docs.codehaus.org/display/CONTINUUMUSER/Continuum+on+Tomcat for installation. Everything works fine, but very, very slowly. For example, each item on the left menu appears one after the other. Same thing when displaying project group information. Each module name appears one after the other (25s for a 17 modules project). 25s for 17 modules??? With embedded derby database we have better performance (http://maven.zones.apache.org/continuum/) and all appears at the same time Are you sure you use the right jdbc driver? MySql database is shared with other Java applications. They work fine, with expected performances. What can be the problem ? Thanks Damien Lecan !DSPAM:4007,46dd7d79203981439371379! -- Justin Deoliveira The Open Planning Project http://topp.openplans.org No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.484 / Virus Database: 269.12.12/979 - Release Date: 8/29/2007 8:21 PM No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.484 / Virus Database: 269.12.12/979 - Release Date: 8/29/2007 8:21 PM
Maven for existing ANT project
Hi All, Currently we have existing project which is build using ANT. Our vision is to Integrate Maven2 into it. So that Maven can be used for site generation containing reports etc. We donot want to shift the build to Maven. Currently we have many context specfic build.xml and a common build.xml. We want as soon ANT run it will call maven or Maven side by side generated site with reports. Please provide some practical example to proceed on this. Thanks in Advance Anny - Once upon a time there was 1 GB storage in your inbox. Click here for happy ending.
RE: Classpaths behaviour in mvn
Great, Thanks a lot, it worked like a charm :) -Original Message- From: Tim Kettler [mailto:[EMAIL PROTECTED] Sent: Monday, September 03, 2007 8:38 PM To: Maven Users List Subject: Re: Classpaths behaviour in mvn Hi, Johan Iskandar schrieb: Hi, While I was running this command D:/proyek/mvn verify, I was hoping to find my surefire tests runs having in one of it's classpaths the path D:/proyek/proyek-core/target/classes. you can run with 'mvn -x ...' to enable verbose debug output. Maven then logs the classpaths it creates. I tested this by invoking the code in one of it's test classes: == URL url = ClassLoader.getSystemResource(file-to-find.xml); String file = url==null?null:url.getFile(); == But only to find that the variable file was null; you are using the wrong classloader. You should use Thread.getContextClassLoader() or Class.getClassLoader(). See this thread for an example [1] -Tim [1] http://www.nabble.com/Problems-with-loading-non-Java-resources-from- classpath-in-JUnit--tests-tf3734983s177.html#a10599455 I made sure the existence of the D:/proyek/proyek-core/target/classes/file-to-find.xml. Is there anyway that I could do in the pom.xml file or any other maven configs to actually adjust the classpath. Cuz, I'd prefer not to declare it in the mvn command or the shell environment.. Thanks, Johan Here's my pom: ?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; parent artifactIdproyek/artifactId groupIdcom.pro/groupId version1.0-SNAPSHOT/version /parent packagingjar/packaging modelVersion4.0.0/modelVersion groupIdcom.pro.core/groupId artifactIdproyek-core/artifactId nameproyek-core/name version1.0-SNAPSHOT/version urlhttp://maven.apache.org/url /project Hi, While I was running this command D:/proyek/mvn verify, I was hoping to find my surefire tests runs having in one of it's classpaths the path D:/proyek/proyek-core/target/classes. I tested this by invoking the code in one of it's test classes: == URL url = ClassLoader.getSystemResource(file-to-find.xml); String file = url==null?null:url.getFile(); == But only to find that the variable file was null; I made sure the existence of the D:/proyek/proyek-core/target/classes/file-to-find.xml. Is there anyway that I could do in the pom.xml file or any other maven configs to actually adjust the classpath. Cuz, I'd prefer not to declare it in the mvn command or the shell environment.. Thanks, Johan Here's my pom: ?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; parent artifactIdproyek/artifactId groupIdcom.pro/groupId version1.0-SNAPSHOT/version /parent packagingjar/packaging modelVersion4.0.0/modelVersion groupIdcom.pro.core/groupId artifactIdproyek-core/artifactId nameproyek-core/name version1.0-SNAPSHOT/version urlhttp://maven.apache.org/url /project - 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: Retrieving version of the pom itself - not the child projects pom
Hi,
Sorry for being unclear.
What I need is a way to in the parentpom access the version of the parent
pom regardless of where the builld was started from.
In your example I want to write something in pom.xml (not my-module/pom.xml)
that when the build is run from either parent, child or grandchild will
output 1.0-SNAPSHOT.
Peter
Thorsten Heit-3 wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Won't ${project.version} be resolved to the version of the pom in the
project
where the build was invoked?
No. ${project.version} in the child indeed contains the child's
version, not the one from the parent. Try this:
Parent:
project
modelVersion4.0.0/modelVersion
groupIdcom.mycompany.app/groupId
artifactIdmy-app/artifactId
packagingpom/packaging
version1.0-SNAPSHOT/version
namemy-app/name
modules
modulemy-module/module
/modules
/project
Child (my-module/pom.xml):
project
modelVersion4.0.0/modelVersion
groupIdcom.mycompany.app/groupId
artifactIdmy-app-test/artifactId
packagingjar/packaging
version2.0-SNAPSHOT/version
namemy-app/name
parent
groupIdcom.mycompany.app/groupId
artifactIdmy-app/artifactId
version1.0-SNAPSHOT/version
/parent
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phasegenerate-sources/phase
configuration
tasks
echo message=project.version: ${project.version} /
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
/plugins
/build
/project
mvn compile outputs
(...)
[INFO] Building my-app
[INFO]task-segment: [compile]
[INFO]
-
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[echo] project.version: 2.0-SNAPSHOT
[INFO] Executed tasks
[INFO] [resources:resources]
(...)
Regards
Thorsten
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkbccHkACgkQQvObkgCcDe3rWwCfeMXwqYi4Ouue0RuYmPxi1tNr
dIkAn35t6lya0ChFVKiFnYsD76Cb9Dpc
=47pS
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Retrieving-version-of-the-pom-itself---not-the-child-projects-pom-tf4359342s177.html#a12473366
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: Cyclic dependency problem
Any ideas ??
De : COPPENS, Fabien
Envoyé : mardi 28 août 2007 17:32
À : 'users@maven.apache.org'
Objet : Cyclic dependency problem
Hi all.
I have just joined the list, so please forgive me if the exact same question
has already been posted.
Here is my use case :
I have a project CORE_A which exposes a facade in the form of an EJB, which is
built in a separate project EJB_A.
I have a project CORE_B which exposes a facade in the form of an EJB, which is
built in a separate project EJB_B.
CORE_A needs to call remote EJB_B, so it has a dependency on the client jar of
EJB_B.
CORE_B needs to call remote EJB_A, so it has a dependency on the client jar of
EJB_A.
EJB_A depends on CORE_A for its build.
EJB_B depends on CORE_B for its build.
In my CORE_A and CORE_B POM files, I have tried to avoid getting a cyclic
dependency error in the build phase
by :
- using a client classifier for the depency of CORE to EJB client
- using an exclusion
e.g. for the pom.xml of the CORE_A project :
dependency
groupIdcom.acme/groupId
artifactIdEJB-B/artifactId
version${applicationVersion}/version
classifierclient/classifier
exclusions
exclusion
groupIdcom.acme/groupId
artifactIdCORE-B/artifactId
/exclusion
/exclusions
/dependency
But when I launch the install goal, I immediately get a cyclic dependency error
message, which seems to indicate that Maven
is ignoring my classifier or exclusion modifiers, and basing its graph
calculation solely on the list of depencies.
I use Maven 2.0.7.
Has anyone got a solution ?
Regards,
Fabien Coppens
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized
to read, print, retain, copy, disseminate, distribute, or use this message or
any part thereof. If you receive this message in error, please notify the
sender immediately and delete all copies of this message.
releasing 2.4
Hi everyone! I've got two questions about surefire 2.4 release. First, could you tell me expected date/week/month/year when it will be released? Second, what are the reasons that surefire development process is so slow? Maybe you do not have enough developers? If so then I could join you in order to speed it up. I'm asking because my team (any many other teams I suppose) want to use Maven with testng and currently surefire has lots of troubles with it. Waiting for reply, Marat Radchenko
Re: Cyclic dependency problem
Hello, I would suggest breaking explicitly the dependency by creating separate projects for the ejbs and the pure java code they encapsulate and expose. HTH -- OQube software engineering \ génie logiciel Arnaud Bailly, Dr. \web http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cyclic dependency problem
Hi,
the excludes won't help here. Maven calculates the dependencies based on
the projects in your reactor build. And as both, the main ejb-jar and
the ejb-client-jar are built by the same project the cyclic dependency
remains.
Your best option is to factor out the exposed ejb interfaces to seperate
projects and then let both, the ejb and core projects depend on that.
-Tim
COPPENS, Fabien schrieb:
Hi all.
I have just joined the list, so please forgive me if the exact same
question has already been posted.
Here is my use case :
I have a project CORE_A which exposes a facade in the form of an EJB,
which is built in a separate project EJB_A.
I have a project CORE_B which exposes a facade in the form of an EJB,
which is built in a separate project EJB_B.
CORE_A needs to call remote EJB_B, so it has a dependency on the client
jar of EJB_B.
CORE_B needs to call remote EJB_A, so it has a dependency on the client
jar of EJB_A.
EJB_A depends on CORE_A for its build.
EJB_B depends on CORE_B for its build.
In my CORE_A and CORE_B POM files, I have tried to avoid getting a
cyclic dependency error in the build phase
by :
- using a client classifier for the depency of CORE to EJB client
- using an exclusion
e.g. for the pom.xml of the CORE_A project :
dependency
groupIdcom.acme/groupId
artifactIdEJB-B/artifactId
version${applicationVersion}/version
classifierclient/classifier
exclusions
exclusion
groupIdcom.acme/groupId
artifactIdCORE-B/artifactId
/exclusion
/exclusions
/dependency
But when I launch the install goal, I immediately get a cyclic
dependency error message, which seems to indicate that Maven
is ignoring my classifier or exclusion modifiers, and basing its
graph calculation solely on the list of depencies.
I use Maven 2.0.7.
Has anyone got a solution ?
Regards,
Fabien Coppens
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized
to read, print, retain, copy, disseminate, distribute, or use this message or
any part thereof. If you receive this message in error, please notify the
sender immediately and delete all copies of this message.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Maven for existing ANT project
Hi All, Currently we have existing project which is build using ANT. Our vision is to Integrate Maven2 into it. So that Maven can be used for site generation containing reports etc. We donot want to shift the build to Maven. Currently we have many context specfic build.xml and a common build.xml. We want as soon ANT run it will call maven or Maven side by side generated site with reports. Please provide some practical example to proceed on this. Thanks in Advance Anny - Once upon a time there was 1 GB storage in your inbox. Click here for happy ending.
Reg: problem using ant task
Hi
I am using Maven2 in my project to build the target.
I am trying to use ant task in my pom.xml using the maven-antrun-plugin
plugin
Following is the snippet of my pom.xml
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
configuration
tasks
property name=compile_classpath refid=maven.compile.classpath/
property name=runtime_classpath refid=maven.runtime.classpath/
property name=test_classpath refid=maven.test.classpath/
property name=plugin_classpath refid=maven.plugin.classpath/
echo message=compile classpath: ${compile_classpath}/
echo message=runtime classpath: ${runtime_classpath}/
echo message=test classpath: ${test_classpath}/
echo message=plugin classpath: ${plugin_classpath}/
/tasks
/configuration
goals
goalrun/goal
/goals
/executions
/plugin
/plugins
When I try to run my pom.xml, I am getting following error at the
Command line
D:\ossj\jsr091\troubleticket-1_2\workspace\spec\maven\maven-2.0.7\bin\m
vn
[INFO] Scanning for projects...
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
Project ID: unknown
POM Location: D:\ossj\jsr091\troubleticket-1_2\workspace\spec\pom.xml
Reason: Parse error reading POM. Reason: parser must be on START_TAG or
TEXT to
read text (position: START_TAG seen ...configurationtasks... @58:43)
for pr
oject unknown at D:\ossj\jsr091\troubleticket-1_2\workspace\spec\pom.xml
[INFO]
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Parse error reading
POM. Reaso
n: parser must be on START_TAG or TEXT to read text (position: START_TAG
seen ..
.configurationtasks... @58:43) for project unknown at
D:\ossj\jsr091\troubl
eticket-1_2\workspace\spec\pom.xml
at
org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.InvalidProjectModelException: Parse
error re
ading POM. Reason: parser must be on START_TAG or TEXT to read text
(position: S
TART_TAG seen ...configurationtasks... @58:43) for project unknown
at D:\os
sj\jsr091\troubleticket-1_2\workspace\spec\pom.xml
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(Default
MavenProjectBuilder.java:1422)
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(Default
MavenProjectBuilder.java:1379)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi
leInternal(DefaultMavenProjectBuilder.java:477)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave
nProjectBuilder.java:200)
at
org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:553)
at
org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467)
at
org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:364)
... 11 more
Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException:
parser must
be on START_TAG or TEXT to read text (position: START_TAG seen
...configuratio
ntasks... @58:43)
at
org.codehaus.plexus.util.xml.pull.MXParser.nextText(MXParser.java:106
8)
at
org.apache.maven.model.io.xpp3.MavenXpp3Reader.parsePlugin(MavenXpp3R
eader.java:2905)
at
org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseBuild(MavenXpp3Re
ader.java:753)
at
org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Re
ader.java:2224)
at
org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.j
ava:4422)
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(Default
MavenProjectBuilder.java:1418)
... 17 more
[INFO]
[INFO] Total time: 1 second
Re: Reg: problem using ant task
Hi,
this is a question about using maven, not about developing it. Next time
please ask such questions on the user list [1].
In your pom you have a nesting of
plugin/executions/configuration/. You missed the execution/ tag:
plugin/executions/execution/configuration/
See here for a copy-and-paste example [2].
-Tim
[1] http://maven.apache.org/mail-lists.html
[2]
http://maven.apache.org/plugins/maven-antrun-plugin/examples/classpaths.html
[EMAIL PROTECTED] schrieb:
Hi
I am using Maven2 in my project to build the target.
I am trying to use ant task in my pom.xml using the maven-antrun-plugin
plugin
Following is the snippet of my pom.xml
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
configuration
tasks
property name=compile_classpath refid=maven.compile.classpath/
property name=runtime_classpath refid=maven.runtime.classpath/
property name=test_classpath refid=maven.test.classpath/
property name=plugin_classpath refid=maven.plugin.classpath/
echo message=compile classpath: ${compile_classpath}/
echo message=runtime classpath: ${runtime_classpath}/
echo message=test classpath: ${test_classpath}/
echo message=plugin classpath: ${plugin_classpath}/
/tasks
/configuration
goals
goalrun/goal
/goals
/executions
/plugin
/plugins
When I try to run my pom.xml, I am getting following error at the
Command line
D:\ossj\jsr091\troubleticket-1_2\workspace\spec\maven\maven-2.0.7\bin\m
vn
[INFO] Scanning for projects...
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
Project ID: unknown
POM Location: D:\ossj\jsr091\troubleticket-1_2\workspace\spec\pom.xml
Reason: Parse error reading POM. Reason: parser must be on START_TAG or
TEXT to
read text (position: START_TAG seen ...configurationtasks... @58:43)
for pr
oject unknown at D:\ossj\jsr091\troubleticket-1_2\workspace\spec\pom.xml
[INFO]
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Parse error reading
POM. Reaso
n: parser must be on START_TAG or TEXT to read text (position: START_TAG
seen ..
.configurationtasks... @58:43) for project unknown at
D:\ossj\jsr091\troubl
eticket-1_2\workspace\spec\pom.xml
at
org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.InvalidProjectModelException: Parse
error re
ading POM. Reason: parser must be on START_TAG or TEXT to read text
(position: S
TART_TAG seen ...configurationtasks... @58:43) for project unknown
at D:\os
sj\jsr091\troubleticket-1_2\workspace\spec\pom.xml
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(Default
MavenProjectBuilder.java:1422)
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(Default
MavenProjectBuilder.java:1379)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi
leInternal(DefaultMavenProjectBuilder.java:477)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave
nProjectBuilder.java:200)
at
org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:553)
at
org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467)
at
org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:364)
... 11 more
Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException:
parser must
be on START_TAG or TEXT to read text (position: START_TAG seen
...configuratio
ntasks... @58:43)
at
org.codehaus.plexus.util.xml.pull.MXParser.nextText(MXParser.java:106
8)
at
org.apache.maven.model.io.xpp3.MavenXpp3Reader.parsePlugin(MavenXpp3R
eader.java:2905)
at
Re: Test resources in final release ?
be careful that your ide is not putting resources into the target directory... eclipse should default to bin/ which is fine... On Tuesday 04 September 2007 14:01, Wayne Fay wrote: Try mvn help:effective-pom to see all the various configuration options you've set. Also try mvn -U package to perhaps update some of your plugins. It sounds like you have something special going on in your environment. I just did a test run myself, and the resources from test are definitely not included in target/classes nor are they included in the JAR. So I think you have some non-standard configuration options affecting your build. Wayne On 9/3/07, Werner Guttmann [EMAIL PROTECTED] wrote: Hi, did a 'mvn clean' folowed by a 'mvn package', and the JAR file in target still contains the various resources as stored in src/test/resources. Werner Werner Guttmann wrote: Damien, Damien Lecan wrote: When you do mvn package, what is the content of your artifact ? Let me get back to you with a reply to this question tomomrrow afternoon. Do you have any special profiles activated when releasing ? No, no profiles. I basically did a standard 'mvn deploy'. You have got another problem : your app has been released with SNAPSHOT dependencies. I have got an awareness of this. Thanks for pointing this out again. Look at : dependency groupIdorg.codehaus.castor/groupId artifactIdcastor-jdo/artifactId version1.1.3-SNAPSHOT/version /dependency I was not able to found spring-orm 1.1 tag in your svn (http://svn.castor.codehaus.org/browse/castor/castor-spring/tags) This is because I have used a 'mvn deploy' to deploy the artefacts to the Codehaus snapshot repo. Damien 2007/9/3, Werner Guttmann [EMAIL PROTECTED]: Hi, let me just restate my own question(s) below. I have had a look at existing Jira issues, and I cannot find anything that relates to my problem. As stated below, I have recently made available a final release of the Spring ORM for Castor JDO using Maven 2 (standard 'mvn deploy'), and to my surprise the JAR file uploaded to http://repository.codehaus.org/org/codehaus/castor/spring-orm/1.1/ included test artefacts as pointed out below - which it should not. And which is causing quite some problems with our users. Is anybody aware of a problem like this (where test resources are included with a deployed JAR) ? Werner Werner Guttmann wrote: Hi, a few days ago, I have made available a new (snapshot) release of a Castor module using Maven 2. A user just pointed out to me that the JAR file in question http://repository.codehaus.org/org/codehaus/castor/spring-orm/1.1/spring- orm-1.1.jar includes a few resources at the root level that it should not include by default. A short investigation revealed that the JAR file indeed includes e.g. a castor.properties file that within the project happens to be living in src/test/resources, viewable at http://svn.castor.codehaus.org/browse/castor/castor-spring/trunk/src/test /resources As far as I remember, I have built this release using Maven 2.0.7. Can anybody please try to explain what has gone wrong. Werner - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Test resources in final release ?
Hello, You have got another problem : your app has been released with SNAPSHOT dependencies. I have got an awareness of this. Thanks for pointing this out again. I was not able to found spring-orm 1.1 tag in your svn (http://svn.castor.codehaus.org/browse/castor/castor-spring/tags) This is because I have used a 'mvn deploy' to deploy the artefacts to the Codehaus snapshot repo. Do you know that your artifact is widely available ? http://repo1.maven.org/maven2/org/codehaus/castor/spring-orm/1.1/ Not just for testing purpose ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
release plugin configuration
Hello all, Is there a way to specify different configurations for the release:prepare and release:perform goals without using profiles? Specifically, what I'm trying to do is pass configuration arguments-Dmaven.test.skip=false/arguments /configuration to release:prepare but run release:perform with configuration arguments-Dmaven.test.skip=true/arguments /configuration I know this can be done using different profiles, but the problem is that you need to specify them when invoking the goals. What I want is to describe the default behavior when invoking 'mvn release:prepare'.. Using two executions didn't work, they simply aren't used. This is in line with what is stated at the bottom of http://maven.apache.org/guides/mini/guide-configuring-plugins.html So, any other suggestions? Regards, Marcel Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=listsid=396545433 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Q4E, a new Eclipse plugin for Maven
This is pretty sweet. Is there any way to get it to work when using the JDK instead of the JRE in Eclipse (I have to use the JDK for MyEclipse)? When I run install using JDK 1.6.0_2 I get build errors related to the the JDK, when running with the same version JRE it's OK though. On 9/4/07, Carlos Sanchez [EMAIL PROTECTED] wrote: I'd like to introduce the Q for Eclipse (Q4E) project http://code.google.com/p/q4e/, an Eclipse plugin for Maven. (see the formatted version at http://www.jroller.com/carlossg/entry/introducing_q4e_a_new_eclipse) === Features === * running Maven goals from the IDE * dependency managing using the Maven POM, with automatic download of dependencies * dependency graphing * direct import of Maven 2 projects * wizard for creation of new projects using the archetype mechanism * modular approach to improve reusability by other Eclipse projects ... and more to come === FAQ http://code.google.com/p/q4e/wiki/FAQ === * What can this Eclipse plugin do? It will allow you to run Maven goals from the Eclipse IDE, create new Maven projects using archetypes, import Maven projects without any intermediate steps, view the dependencies of your project in a graph,... we will keep adding features with the time * How do I install it? Refer to Installation http://code.google.com/p/q4e/wiki/Installation * What are the differences between this plugin and m2eclipse (aka Tycho)? The objective of this plugin is to be part of the Eclipse Foundation, for that reason the license is EPL and we are going to follow the foundation procedures. Thanks to the sponsorship of DevZuz, an Eclipse Strategic Developer Member we are in a good position to achieve this goal. Besides the objective, there are technical differences. While m2eclipse shows Maven output in a console, Q is based in events and will show them in an organized way that allows filtering by severity, search,... Functionality like the dependency graph, direct import of projects or creation of new projects using the archetype mechanism are only present in Q. * Why the name Q? Q, named after the special agent Q in the James Bond books and movies. No double meaning or anything like that, we are just James Bond fans ;) === Collaborating === The project is licensed under the EPL and collaborations are welcome, please join the user mailing list http://groups.google.com/group/q4e-users to be informed of updates, or the developers list http://groups.google.com/group/q4e-dev if you want to help with the development or extend the plugin. You can also take a look at the list of known issues. http://code.google.com/p/q4e/issues/list -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Adam Altemus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Default Schedule do not work
Actually i have 3 Builds running none is running any more. I have a SVN trunk and two branches in schedule. I configured Continuum that all are using the default schedule ... Why cannot Continuum not do this ? Iterate over all Projects an invoke the build (mabye a bit naive impl.). May there are issues that a simple iteration over all Project takes to long ? Also how many schedules do you have? If I remember it correctly, Continuum 1.0.3 doesn't work well with more than one schedule in some case. Emmanuel Mac-Systems a écrit : Anyone can help ??? Hello, Actually my Continuum (1.0.3) does not build anything which is Scheduled but i use the default schedule. Anyone can help correct this ? best regards, Jens
Re: Running heavy tests in the build lifecycle
On Monday 03 September 2007 18:06:48 Dave Feltenberger wrote: One approach I've seen used is to have a standard naming convention on your test cases. Maven will automatically run classes named *Test.java (and I believe any class that starts with Test), OK, so Test* classes and files named *Test.java, then? (I have a bit of getting used to naming conventions) so if you name the ones you want to run with every test phase during a build with that convention, then name the heavy-handed tests something like MyTestManual.java or MyTestIntegration.java or something along those lines, then you can manually run those test cases when it comes time. OK. Looking through the source tree, I see that we do allready have a naming convention, but in terms of directory naming: test: functional/ integration/ performance/ unit/ where a test may have a path like: test/integration/source/com/computas/eass/server/persistence/TestServiceProvider.java where the test/integration/source is not part of the package name. The tests to be run in the test phase are in unit/, the tests for the integration test phase is also well named. I suppose this is somewhat contrary to convention, so the question is if I should rename things or configure things to use these subdirs? You could also create a separate project for the heavy-handed ones and only build that test suite manually as needed. Right. My boss mentioned that, but I felt that it was a bit inelegant, and he is not very experienced with Maven either. Wouldn't it be nice to have a separate lifecycle phase for stuff like this? Kind regards Kjetil Kjernsmo -- Senior Knowledge Engineer Direct: +47 6783 1136 | Mobile: +47 986 48 234 Email: [EMAIL PROTECTED] Web: http://www.computas.com/ | SHARE YOUR KNOWLEDGE | Computas AS Vollsveien 9, PO Box 482, N-1327 Lysaker | Phone:+47 6783 1000 | Fax:+47 6783 1001 IMPORTANT NOTICE: This message may contain confidential information. If you have received this e-mail in error, do not use, copy or distribute it. Do not open any attachments. Delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: release plugin configuration
Hello, I believe the usage of profiles is the right way to pass arguments. But you're wrong saying you have to specify which profile when invoking the goals. In your case, you can do something like that : profile idenv-dev/id properties maven.test.skiptrue/maven.test.skip /properties /profile /profiles activeProfiles activeProfileenv-dev/activeProfile /activeProfiles by adding the activeProfile tag, you'll be able to select a profile which will be always used on that machine. Arnaud Marcel Schutte a écrit : Hello all, Is there a way to specify different configurations for the release:prepare and release:perform goals without using profiles? Specifically, what I'm trying to do is pass configuration arguments-Dmaven.test.skip=false/arguments /configuration to release:prepare but run release:perform with configuration arguments-Dmaven.test.skip=true/arguments /configuration I know this can be done using different profiles, but the problem is that you need to specify them when invoking the goals. What I want is to describe the default behavior when invoking 'mvn release:prepare'.. Using two executions didn't work, they simply aren't used. This is in line with what is stated at the bottom of http://maven.apache.org/guides/mini/guide-configuring-plugins.html So, any other suggestions? Regards, Marcel Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=listsid=396545433 - 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: Running heavy tests in the build lifecycle
Kjetil Kjernsmo [EMAIL PROTECTED] writes: Looking through the source tree, I see that we do allready have a naming convention, but in terms of directory naming: test: functional/ integration/ performance/ unit/ where a test may have a path like: test/integration/source/com/computas/eass/server/persistence/TestServiceProvider.java where the test/integration/source is not part of the package name. The tests to be run in the test phase are in unit/, the tests for the integration test phase is also well named. I suppose this is somewhat contrary to convention, so the question is if I should rename things or configure things to use these subdirs? You could also create a separate project for the heavy-handed ones and only build that test suite manually as needed. Right. My boss mentioned that, but I felt that it was a bit inelegant, and he is not very experienced with Maven either. Wouldn't it be nice to have a separate lifecycle phase for stuff like this? Maybe you could use two features peculiar to maven to achieve what you want within the confine of a single project (although I think moving integration tests out to another project is a good idea): 1. define a profile for each different kind of test you want to run: perf, func, unit... 2. in each profile, configure different set of test executions. this can be done by configuring surefire plugin (see http://maven.apache.org/plugins/maven-surefire-plugin/, it has a zillion parameters to play with). If you use testNG, you can define different test groups to be executed in each profile, if you use Junit, you can include/exclude test files (you can also do that with testNG of course). 3. configure the basic execution of surefire (ie. the one that gets executed always) to just run unit tests. Then running your tests is a matter of invoking maven with the right profile(s): mvn -Pfunc-test or mvn -Pperf-test or even mvn -Pfunc-test -Pperf-test HTH -- OQube software engineering \ génie logiciel Arnaud Bailly, Dr. \web http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
site deployment to url without parent information
Hello, I try to configure the site deployment for our projects. Because I don't want to include a distributionManagement.site section in all of our project poms I tried to centralize these settings in a common parent pom (rootpom) which is used as parent for all other projects. The site configuration in this parent pom looks like: site idwebserver/id urlscp://webserver.mycompany.com/projects//url /site Now I got the problem, that the computed URL for let's say MyTestproject contains the artifactID from all super poms and is deployed to ../projects/rootpom/MyTestproject Is it possible to ignore the parent artifactID and get something like: /projects/MyTestproject Thanks, Martin d.velop AG digital business solutions Schildarpstraße 6-8 48712 Gescher Fon: +49 25 42 93 07-0 Fax: +49 25 42 93 07-20 HRB 4903, Amtsgericht Coesfeld, Vorstand: Christoph Pliete, Aufsichtsratsvorsitzender: Dr. Helmut Bäumer Diese E-Mail enthält vertrauliche oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Re: release plugin configuration
Hi Arnaud, Thanks for your reply. You're right that I can use activeProfile to make one profile default. But that won't help in my situation: I would need some 'profileA' active when running release:prepare and 'profileB' active for release:perform. This is something I think can only be done by specifying them as in 'mvn -P profileA release:prepare'. Or do you have another suggestion? Marcel - Original Message From: Arnaud WEBER [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Tuesday, September 4, 2007 3:36:52 PM Subject: Re: release plugin configuration Hello, I believe the usage of profiles is the right way to pass arguments. But you're wrong saying you have to specify which profile when invoking the goals. In your case, you can do something like that : profile idenv-dev/id properties maven.test.skiptrue/maven.test.skip /properties /profile /profiles activeProfiles activeProfileenv-dev/activeProfile /activeProfiles by adding the activeProfile tag, you'll be able to select a profile which will be always used on that machine. Arnaud Marcel Schutte a écrit : Hello all, Is there a way to specify different configurations for the release:prepare and release:perform goals without using profiles? Specifically, what I'm trying to do is pass configuration arguments-Dmaven.test.skip=false/arguments /configuration to release:prepare but run release:perform with configuration arguments-Dmaven.test.skip=true/arguments /configuration I know this can be done using different profiles, but the problem is that you need to specify them when invoking the goals. What I want is to describe the default behavior when invoking 'mvn release:prepare'.. Using two executions didn't work, they simply aren't used. This is in line with what is stated at the bottom of http://maven.apache.org/guides/mini/guide-configuring-plugins.html So, any other suggestions? Regards, Marcel Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=listsid=396545433 - 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] Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool. http://autos.yahoo.com/carfinder/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running heavy tests in the build lifecycle
I think Arnaud's advice is right if you're going to keep one project for everything - set up the profiles. You may need to re-arrange the source tree a little bit, though - looks like you have several different source trees, one for each category of tests. I'm not sure how the surefire plugin will respond to having multiple source trees (the config section only takes one location), so if it complains, you'll probably need to move everything into e.g. src/test/java (/functional, /unit, etc.). Alternatively the separate project approach would let you configure the surefire plugin for each type of unit test. You can by default skip unit tests in the functional/integration/etc. projects with skiptrue/skip in the configuration of the plugin. If you make them child projects to the main, you can even inherit all the project properties/dependencies/etc. and have a really simple pom for each category of tests. Something like: computas-Eass-Main/pom.xml (type pom) \-- computas-Eass/pom.xml (where all your source code is) \-- functional-Tests/pom.xml (inherits from Main/parent project to share all deps etc., set to skip unit tests by default) \-- unit-Tests/pom.xml (also inherits parent properties, but set to run tests by default) etc. This will still relate the project/tests hierarchically and is (I think) fairly elegant as it allows fine-tuning of when to run which type of test and won't duplicate any effort (you're inheriting the parent project's properties). Dave On 9/4/07, Insitu [EMAIL PROTECTED] wrote: Kjetil Kjernsmo [EMAIL PROTECTED] writes: Looking through the source tree, I see that we do allready have a naming convention, but in terms of directory naming: test: functional/ integration/ performance/ unit/ where a test may have a path like: test/integration/source/com/computas/eass/server/persistence/TestServiceProvider.java where the test/integration/source is not part of the package name. The tests to be run in the test phase are in unit/, the tests for the integration test phase is also well named. I suppose this is somewhat contrary to convention, so the question is if I should rename things or configure things to use these subdirs? You could also create a separate project for the heavy-handed ones and only build that test suite manually as needed. Right. My boss mentioned that, but I felt that it was a bit inelegant, and he is not very experienced with Maven either. Wouldn't it be nice to have a separate lifecycle phase for stuff like this? Maybe you could use two features peculiar to maven to achieve what you want within the confine of a single project (although I think moving integration tests out to another project is a good idea): 1. define a profile for each different kind of test you want to run: perf, func, unit... 2. in each profile, configure different set of test executions. this can be done by configuring surefire plugin (see http://maven.apache.org/plugins/maven-surefire-plugin/, it has a zillion parameters to play with). If you use testNG, you can define different test groups to be executed in each profile, if you use Junit, you can include/exclude test files (you can also do that with testNG of course). 3. configure the basic execution of surefire (ie. the one that gets executed always) to just run unit tests. Then running your tests is a matter of invoking maven with the right profile(s): mvn -Pfunc-test or mvn -Pperf-test or even mvn -Pfunc-test -Pperf-test HTH -- OQube software engineering \ génie logiciel Arnaud Bailly, Dr. \web http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Test resources in final release ?
Yes, I am aware of this. It was meant to be a proper release, with just an announcement missing (which I am now holding back). Werner Damien Lecan wrote: Hello, You have got another problem : your app has been released with SNAPSHOT dependencies. I have got an awareness of this. Thanks for pointing this out again. I was not able to found spring-orm 1.1 tag in your svn (http://svn.castor.codehaus.org/browse/castor/castor-spring/tags) This is because I have used a 'mvn deploy' to deploy the artefacts to the Codehaus snapshot repo. Do you know that your artifact is widely available ? http://repo1.maven.org/maven2/org/codehaus/castor/spring-orm/1.1/ Not just for testing purpose ... - 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: release plugin configuration
why do you want to skip tests in release:prepare? On Wednesday 05 September 2007 02:20, Marcel Schutte wrote: Hi Arnaud, Thanks for your reply. You're right that I can use activeProfile to make one profile default. But that won't help in my situation: I would need some 'profileA' active when running release:prepare and 'profileB' active for release:perform. This is something I think can only be done by specifying them as in 'mvn -P profileA release:prepare'. Or do you have another suggestion? Marcel - Original Message From: Arnaud WEBER [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Tuesday, September 4, 2007 3:36:52 PM Subject: Re: release plugin configuration Hello, I believe the usage of profiles is the right way to pass arguments. But you're wrong saying you have to specify which profile when invoking the goals. In your case, you can do something like that : profile idenv-dev/id properties maven.test.skiptrue/maven.test.skip /properties /profile /profiles activeProfiles activeProfileenv-dev/activeProfile /activeProfiles by adding the activeProfile tag, you'll be able to select a profile which will be always used on that machine. Arnaud Marcel Schutte a écrit : Hello all, Is there a way to specify different configurations for the release:prepare and release:perform goals without using profiles? Specifically, what I'm trying to do is pass configuration arguments-Dmaven.test.skip=false/arguments /configuration to release:prepare but run release:perform with configuration arguments-Dmaven.test.skip=true/arguments /configuration I know this can be done using different profiles, but the problem is that you need to specify them when invoking the goals. What I want is to describe the default behavior when invoking 'mvn release:prepare'.. Using two executions didn't work, they simply aren't used. This is in line with what is stated at the bottom of http://maven.apache.org/guides/mini/guide-configuring-plugins.html So, any other suggestions? Regards, Marcel _ ___ Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=listsid=396545433 - 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] ___ _ Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool. http://autos.yahoo.com/carfinder/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Eclipse setup for Multi-module project
Has anyone come up with a decent way to setup a project in Eclipse that will support a multi-module project? The best example I've seen is in the Better Builds with Maven book ( http://www.devzuz.com/web/guest/products/resources#BBWM - Chapter 4) but I'm having some difficulty. The book is creating the DayTrader application and recommends the file structure that I've tried to describe below. It also mentioned that this flat structure is the best and a nested directory structure has some drawbacks -- especially for Eclipse users. daytrader | +--ear | +... | +--ejb | +... | +--streamer | +... | +--web | +... | +--wsappclient | +... | +--pom.xml Unless I'm missing something, this is a nested directory structure. I've tried creating Java Projects and Simple Projects in Eclipse for the daytrader. I've tried source folders for the ear, ejb... I can't seem to get this directory structure to work using Eclipse. Has anyone found a good way to make this work? I'm a maven newbie but it seems that there is some incompatibility between one of the main IDEs (Eclipse) and Maven. If Maven is geared to a particular directory structure and Eclipse to another, and you have to have major tweaks to Maven to make everything work, then you lose a large percentage of the benefits of using Maven. Hopefully I'm missing something easy on how to setup a project in Eclipse.
How to get dependencies with scope provided in a plugin
Hi all, I'm writting a maven plugin. I have a goal running on the phase pre-integration-test. For a continuous integration context, in this goal, I want to deploy external artefacts, available on a repository, so they are marked as provided in the section dependencies of the current project. In the goal, I need to get the provided dependencies. But I am not be able ti get them using documentation, Google and some plugin source code. How can I get them ? I had get them only if I run my plugin outside a lifecycle using the command line: mvn groupId:pluginId:goal. But I don't why ? ___ Christophe DENEUX / Capgemini Sud / Méditerranée Technical Leader Tel: + 33 4 93 95 55 92 / www.capgemini.com http://www.capgemini.com/ Porte de l'Arénas - Entrée B / 455 Promenade des Anglais / 06200 Nice / FRANCE Join the Collaborative Business Experience ___ Please consider the environment and do not print this email unless absolutely necessary. Capgemini encourages environmental awareness. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: Eclipse setup for Multi-module project
On Tue, September 4, 2007 5:08 pm, Brian Smith wrote: Has anyone come up with a decent way to setup a project in Eclipse that will support a multi-module project? I normally set up the project in maven, then run mvn eclipse:eclipse, and then use import existing project into workspace. Let maven do all the work, not eclipse. (We use this method to set up a set of multi-module projects, including one multi-module project with an eclipse plugin in it, the fun) Regards, Graham -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Example of setting up a maven 2 J2ee project
Folks: I'm new to maven and I'm looking for a good reference to how to set up a j2ee application using maven 2.0. Are there and good documents or examples out there that I could use to get started? Eric
RE: Example of setting up a maven 2 J2ee project
http://maven.apache.org/plugins/maven-archetype-plugin/examples/j2ee-sim ple.html | -Original Message- | From: Eric Wood [mailto:[EMAIL PROTECTED] | Sent: Tuesday, September 04, 2007 11:22 AM | To: users@maven.apache.org | Subject: Example of setting up a maven 2 J2ee project | | Folks: | | I'm new to maven and I'm looking for a good reference to how to set up a | j2ee application using maven 2.0. Are there and good documents or | examples out there that I could use to get started? | | Eric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse setup for Multi-module project
Nick Stolwijk wrote: In your daytrader directory, run mvn eclipse:eclipse. This will create the .project and .classpath files of the child modules with dependencies for eclipse between them if necessary. Then, in Eclipse, import your projects. If you want your parent pom.file easily accessible from eclipse, make a symlink to it from one of the other directories. If your developers use a SCM from Eclipse (like subclipse) they will not pickup any changes to the root directory. That's why we've setup our environment to send mails when the root pom changes. (This was often a pain in the butt, people not upgrading their parent pom) I hope it is clear, if not, ask. Nick Stolwijk Brian Smith wrote: Has anyone come up with a decent way to setup a project in Eclipse that will support a multi-module project? The best example I've seen is in the Better Builds with Maven book ( http://www.devzuz.com/web/guest/products/resources#BBWM - Chapter 4) but I'm having some difficulty. The book is creating the DayTrader application and recommends the file structure that I've tried to describe below. It also mentioned that this flat structure is the best and a nested directory structure has some drawbacks -- especially for Eclipse users. daytrader | +--ear | +... | +--ejb | +... | +--streamer | +... | +--web | +... | +--wsappclient | +... | +--pom.xml Unless I'm missing something, this is a nested directory structure. I've tried creating Java Projects and Simple Projects in Eclipse for the daytrader. I've tried source folders for the ear, ejb... I can't seem to get this directory structure to work using Eclipse. Has anyone found a good way to make this work? I'm a maven newbie but it seems that there is some incompatibility between one of the main IDEs (Eclipse) and Maven. If Maven is geared to a particular directory structure and Eclipse to another, and you have to have major tweaks to Maven to make everything work, then you lose a large percentage of the benefits of using Maven. Hopefully I'm missing something easy on how to setup a project in Eclipse. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: xdoclet plugin and weblogic-ejb-jar.xml descriptor
I'm using Weblogic 9.2. I think you're correct in that the weblogic plugin only works for versions 8.x and earlier. I haven't found any great solutions for this hurdle yet. On 8/31/07, Scott Ryan [EMAIL PROTECTED] wrote: What version of Weblogic are you using? You can use the weblogic tag to generate the XML files but as far as I know xdoclet can only generate xml files for 8.x and prior. 9.x and 10.x are not supported but then maybe you should be using JPA, EJB 3.0 or Hibernate by then. Scott Ryan CTO Soaring Eagle L.L.C. Denver, Co. 80129 www.soaringeagleco.com www.theryansplace.com (303) 263-3044 [EMAIL PROTECTED] On Aug 31, 2007, at 9:34 AM, Brian Smith wrote: I'm working on a simple HelloWorldEJB stateless session bean that I want to run in Weblogic. I'm using the xdoclet plugin and xdoclet is able to generate the home/remote classes. Should xdoclet be able to generate the weblogic-ejb-jar.xml descriptor? If so, how do I do this? Is there a special tag in the EJB source code or is there something in the pom I need to specify? I'm guessing this a task of xdoclet instead of maven but I'm not sure. Any input would be appreciated. Thanks, Brian
Re: Eclipse setup for Multi-module project
In your daytrader directory, run mvn eclipse:eclipse. This will create the .project and .classpath files of the child modules with dependencies for eclipse between them if necessary. Then, in Eclipse, import your projects. If you want your parent pom.file easily accessible from eclipse, make a symlink to it from one of the other directories. If your developers use a SCM from Eclipse (like subclipse) they will not pickup any changes to the root directory. That's why we've setup our environment to send mails when the root pom changes. (This was often a pain in the butt, people not upgrading their parent pom) I hope it is clear, if not, ask. Nick Stolwijk Brian Smith wrote: Has anyone come up with a decent way to setup a project in Eclipse that will support a multi-module project? The best example I've seen is in the Better Builds with Maven book ( http://www.devzuz.com/web/guest/products/resources#BBWM - Chapter 4) but I'm having some difficulty. The book is creating the DayTrader application and recommends the file structure that I've tried to describe below. It also mentioned that this flat structure is the best and a nested directory structure has some drawbacks -- especially for Eclipse users. daytrader | +--ear | +... | +--ejb | +... | +--streamer | +... | +--web | +... | +--wsappclient | +... | +--pom.xml Unless I'm missing something, this is a nested directory structure. I've tried creating Java Projects and Simple Projects in Eclipse for the daytrader. I've tried source folders for the ear, ejb... I can't seem to get this directory structure to work using Eclipse. Has anyone found a good way to make this work? I'm a maven newbie but it seems that there is some incompatibility between one of the main IDEs (Eclipse) and Maven. If Maven is geared to a particular directory structure and Eclipse to another, and you have to have major tweaks to Maven to make everything work, then you lose a large percentage of the benefits of using Maven. Hopefully I'm missing something easy on how to setup a project in Eclipse. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Continuum 1.1.0-beta-2 UI performance
We know that 1.1 is a little slower than 1.0.3 because lot of new request and full security added but 25s for 17 modules isn't a normal perf result Emmanuel Mrinal Mukherjee a écrit : Same problem with me. Slow UI. I had this problem as soon as I upgraded to the newer version of continuum. I thought it was a problem in my system, but now I know its something to do with the new version of continuum. Mrinal -Original Message- From: Justin Deoliveira [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 04, 2007 5:49 PM To: [EMAIL PROTECTED] Subject: Re: Continuum 1.1.0-beta-2 UI performance I am using derby out of the box and noticed the same slowdown. I don't have any metrics to back it up but its definitely noticeably slower. -Justin Emmanuel Venisse wrote: Damien Lecan a écrit : Hello, I've just installed Continuum 1.1.0-beta-2 to replace my old Continuum 1.0.3 instance. I'm working with MySql instead of embbeded sql server and with Tomcat 5.5.17 Nice new features, but UI is very, very, very slow :( I followed http://docs.codehaus.org/display/CONTINUUMUSER/Continuum+on+MySQL and http://docs.codehaus.org/display/CONTINUUMUSER/Continuum+on+Tomcat for installation. Everything works fine, but very, very slowly. For example, each item on the left menu appears one after the other. Same thing when displaying project group information. Each module name appears one after the other (25s for a 17 modules project). 25s for 17 modules??? With embedded derby database we have better performance (http://maven.zones.apache.org/continuum/) and all appears at the same time Are you sure you use the right jdbc driver? MySql database is shared with other Java applications. They work fine, with expected performances. What can be the problem ? Thanks Damien Lecan !DSPAM:4007,46dd7d79203981439371379!
Re: Eclipse setup for Multi-module project
Nick, I'm trying to keep things really small at this point (like HelloWorlds) but I setup a directory structure similar to the DayTrader and performed the import into eclipse. First thing I noticed (and I think this is what you mentioned) is that the top level directory is not there. Because of this, I can't run Maven (mvn install) because the parent pom is not available. You mentioned making a symlink but we're developing on our PCs (XP). Directory Structure Eclipse === === TestApp + testcommon + testcommon + testejb + testejb + testear + testear So, it seems like I'm back to where I started. Eclipse and Maven aren't too compatible. All the books and articles talk about a flat directory structure but it's really nested. Maven needs (or recommends) a top directory to hold the parent pom but Eclipse doesn't like the notion of sub-projects. I'm using CVS and I've played with the idea of having something setup like the following where I have a parent directory that just holds the parent pom and the ear to create the ear and then the two modules that actually hold the code but this seems pretty ugly. At least with Ant I can layout the code the way I want too. Eclipse === + testcommon + testejb + testear + testparent On 9/4/07, Nick Stolwijk [EMAIL PROTECTED] wrote: In your daytrader directory, run mvn eclipse:eclipse. This will create the .project and .classpath files of the child modules with dependencies for eclipse between them if necessary. Then, in Eclipse, import your projects. If you want your parent pom.file easily accessible from eclipse, make a symlink to it from one of the other directories. If your developers use a SCM from Eclipse (like subclipse) they will not pickup any changes to the root directory. That's why we've setup our environment to send mails when the root pom changes. (This was often a pain in the butt, people not upgrading their parent pom) I hope it is clear, if not, ask. Nick Stolwijk Brian Smith wrote: Has anyone come up with a decent way to setup a project in Eclipse that will support a multi-module project? The best example I've seen is in the Better Builds with Maven book ( http://www.devzuz.com/web/guest/products/resources#BBWM - Chapter 4) but I'm having some difficulty. The book is creating the DayTrader application and recommends the file structure that I've tried to describe below. It also mentioned that this flat structure is the best and a nested directory structure has some drawbacks -- especially for Eclipse users. daytrader | +--ear | +... | +--ejb | +... | +--streamer | +... | +--web | +... | +--wsappclient | +... | +--pom.xml Unless I'm missing something, this is a nested directory structure. I've tried creating Java Projects and Simple Projects in Eclipse for the daytrader. I've tried source folders for the ear, ejb... I can't seem to get this directory structure to work using Eclipse. Has anyone found a good way to make this work? I'm a maven newbie but it seems that there is some incompatibility between one of the main IDEs (Eclipse) and Maven. If Maven is geared to a particular directory structure and Eclipse to another, and you have to have major tweaks to Maven to make everything work, then you lose a large percentage of the benefits of using Maven. Hopefully I'm missing something easy on how to setup a project in Eclipse. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse setup for Multi-module project
On Tue, September 4, 2007 7:12 pm, Brian Smith wrote: First thing I noticed (and I think this is what you mentioned) is that the top level directory is not there. Because of this, I can't run Maven (mvn install) because the parent pom is not available. Why is the top level directory not there? One thing to make sure you do - check out the whole project using your source control tool of choice, then run mvn eclipse:eclipse from the root of your project, then import your projects into eclipse by selecting the root of your project and importing all the projects eclipse finds. Directory Structure Eclipse === === TestApp + testcommon + testcommon + testejb + testejb + testear + testear This is exactly what we have, and mvn install runs fine. Can you explain in more detail the exact steps you are trying to perform? Regards, Graham -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Manager username
On 03/09/07, Alexandre Gomes [EMAIL PROTECTED] wrote: Hi, based on [1], how can I pass a diferent username for Tomcat Manager, using -D command option (and not settings.xml) ? I tried -D tomcat.server.username=root, but it doesn't seem to work. [1] http://mojo.codehaus.org/tomcat-maven-plugin/configuration.html Sounds like a fair enough requirement - raise an issue under the tomcat component here: http://jira.codehaus.org/browse/MOJO I'd add username and password config params that could override the server param. Cheers, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse setup for Multi-module project
One little Note about the importing of the projects: Ensure that Copy projects into workspace is deselected. Event the top level project can be imported into eclipse. To do this you generate the project files of the submodules and import them. Then create a new Project (not Java, a General Project) with exactly the name of your Top-Level Module (In your application: TestApp). Eclipse will not overwrite the directory. Instead it will discover the contents. Inside this project executing mvn install will be possible. Graham Leggett schrieb: On Tue, September 4, 2007 7:12 pm, Brian Smith wrote: First thing I noticed (and I think this is what you mentioned) is that the top level directory is not there. Because of this, I can't run Maven (mvn install) because the parent pom is not available. Why is the top level directory not there? One thing to make sure you do - check out the whole project using your source control tool of choice, then run mvn eclipse:eclipse from the root of your project, then import your projects into eclipse by selecting the root of your project and importing all the projects eclipse finds. Directory Structure Eclipse === === TestApp + testcommon + testcommon + testejb + testejb + testear + testear This is exactly what we have, and mvn install runs fine. Can you explain in more detail the exact steps you are trying to perform? Regards, Graham -- - 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: Q4E, a new Eclipse plugin for Maven
Aside from license issues, I'm confused as to why we now have two Maven plugins for Eclipse? Surely it'd make sense for the two projects to collaborate to accelerate development, rather than having two plugins that are both rather thin on the ground in terms of features? Mark On 04/09/07, Carlos Sanchez [EMAIL PROTECTED] wrote: I'd like to introduce the Q for Eclipse (Q4E) project http://code.google.com/p/q4e/, an Eclipse plugin for Maven. (see the formatted version at http://www.jroller.com/carlossg/entry/introducing_q4e_a_new_eclipse) === Features === * running Maven goals from the IDE * dependency managing using the Maven POM, with automatic download of dependencies * dependency graphing * direct import of Maven 2 projects * wizard for creation of new projects using the archetype mechanism * modular approach to improve reusability by other Eclipse projects ... and more to come === FAQ http://code.google.com/p/q4e/wiki/FAQ === * What can this Eclipse plugin do? It will allow you to run Maven goals from the Eclipse IDE, create new Maven projects using archetypes, import Maven projects without any intermediate steps, view the dependencies of your project in a graph,... we will keep adding features with the time * How do I install it? Refer to Installation http://code.google.com/p/q4e/wiki/Installation * What are the differences between this plugin and m2eclipse (aka Tycho)? The objective of this plugin is to be part of the Eclipse Foundation, for that reason the license is EPL and we are going to follow the foundation procedures. Thanks to the sponsorship of DevZuz, an Eclipse Strategic Developer Member we are in a good position to achieve this goal. Besides the objective, there are technical differences. While m2eclipse shows Maven output in a console, Q is based in events and will show them in an organized way that allows filtering by severity, search,... Functionality like the dependency graph, direct import of projects or creation of new projects using the archetype mechanism are only present in Q. * Why the name Q? Q, named after the special agent Q in the James Bond books and movies. No double meaning or anything like that, we are just James Bond fans ;) === Collaborating === The project is licensed under the EPL and collaborations are welcome, please join the user mailing list http://groups.google.com/group/q4e-users to be informed of updates, or the developers list http://groups.google.com/group/q4e-dev if you want to help with the development or extend the plugin. You can also take a look at the list of known issues. http://code.google.com/p/q4e/issues/list -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - 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: Q4E, a new Eclipse plugin for Maven
2007/9/4, Mark Hobson [EMAIL PROTECTED]: Aside from license issues, I'm confused as to why we now have two Maven plugins for Eclipse? Surely it'd make sense for the two projects to collaborate to accelerate development, rather than having two plugins that are both rather thin on the ground in terms of features? It reminds me of the battle between Subclipse and Subversive, but in this case, Subversive is not community-driven. Carlos, is Q4E community-driven or privately-driven? Antonio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Odd dependency POM validation issue
I have a dependency for my project that is provided by another company.
I have built, installed, and deployed this other dependency in my local
repository as well as our company's internal repository. This
dependency, has something that is causing an issue in it's dependency
section. It has this:
dependency
groupId${repository.database.driver.groupId}/groupId
artifactId${repository.database.driver.artifactId}/artifactId
version${repository.database.driver.version}/version
/dependency
These values are provided to this project when it is built. This works
fine.
However, in my own project, when I reference the other company's
dependency that has it's own dependency identified above, I get the
following error message during the build:
[DEBUG] Retrieving parent-POM: com.jaspersoft.jasperserver:server::2.0.0
for project:
com.jaspersoft.jasperserver:jasperserver-export-tool-package:jar:2.0.0
from the repository.
[WARNING] POM for
'com.jaspersoft.jasperserver:jasperserver-export-tool-package:pom:2.0.0:compile'
is invalid. It will be ignored for artifact resolution. Reason: Failed to
validate POM for project
com.jaspersoft.jasperserver:jasperserver-export-tool-package at Artifact
[com.jaspersoft.jasperserver:jasperserver-export-tool-package:pom:2.0.0:compile]
[DEBUG] Reason: Failed to validate POM for project
com.jaspersoft.jasperserver:jasperserver-export-tool-package at Artifact
[com.jaspersoft.jasperserver:jasperserver-export-tool-package:pom:2.0.0:compile]
[DEBUG]
Validation Errors:
[DEBUG] 'dependencies.dependency.artifactId' with value
'${repository.database.driver.artifactId}' does not match a valid id
pattern.
[DEBUG] 'dependencies.dependency.groupId' with value
'${repository.database.driver.groupId}' does not match a valid id
pattern.
[DEBUG]
Now when I do my build, the property values of
repository.database.driver.artifactId and
repository.database.driver.groupId are available as I checked the
effective POM. Is this a bug with Maven? Or is the other company's POM
doing something it shouldn't be doing?
Thanks in advance for the help.
Eric
Project or module depends on assembly of another?
Hello, I am trying to setup a project like this: MyProj/ +---pom.xml +---MyProj-Core/pom.xml +---MyProj-Integration-Tests/pom.xml MyProj-Core and MyProj-Integration-Tests are both modules of and MyProj. What I would like to do is setup MyProj-Integration-Tests so that it will take the output of 'mvn package' from MyProj-Core, unarchive it (install it) and run some tests on it. Effectively, I'd like to create some tests that exercise our project the same way they would be used when installed on a machine. Is there a way to do this? At a basic starting point, even with MyProj-Core being a dependancy of MyProj-Integration-Tests, running 'mvn compile' in MyProj- Integration-Tests doesn't trigger a build in MyProj-Core. -- Joshua ChaitinPollak Software Engineer Kiva Systems - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
exec-maven-plugin - how to skip execution in a sub-project
Hi, My project has a structure similar to this: root +child1 +child2 I use the exec goal in the root project. During the compilation process of both children the exec goal from root project is executed and causes errors - thus I would like to skip it. I would like it to be executed only during the compilation of the root project. How can I achieve it? Thanks in advance. Tom -- View this message in context: http://www.nabble.com/exec-maven-plugin--%3E-how-to-skip-execution-in-a-sub-project-tf4379678s177.html#a12484500 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: Project or module depends on assembly of another?
You need to run mvn install to put the artifacts in your local cache from MyProj-Core. Then you can depend on it in MyProj-Integration-Tests (just like any other dependency) and it will pull the file out of the cache and use it during its own execution ie mvn test etc. As for calling mvn compile from a subproject and expecting that it will go build the parent and all modules, that's just not how Maven works. You can build from the top (parent) and get this kind of build, but not from modules themselves. Wayne On 9/4/07, Joshua ChaitinPollak [EMAIL PROTECTED] wrote: Hello, I am trying to setup a project like this: MyProj/ +---pom.xml +---MyProj-Core/pom.xml +---MyProj-Integration-Tests/pom.xml MyProj-Core and MyProj-Integration-Tests are both modules of and MyProj. What I would like to do is setup MyProj-Integration-Tests so that it will take the output of 'mvn package' from MyProj-Core, unarchive it (install it) and run some tests on it. Effectively, I'd like to create some tests that exercise our project the same way they would be used when installed on a machine. Is there a way to do this? At a basic starting point, even with MyProj-Core being a dependancy of MyProj-Integration-Tests, running 'mvn compile' in MyProj- Integration-Tests doesn't trigger a build in MyProj-Core. -- Joshua ChaitinPollak Software Engineer Kiva Systems - 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: Project or module depends on assembly of another?
On Sep 4, 2007, at 3:05 PM, Wayne Fay wrote: You need to run mvn install to put the artifacts in your local cache from MyProj-Core. Then you can depend on it in MyProj-Integration-Tests (just like any other dependency) and it will pull the file out of the cache and use it during its own execution ie mvn test etc. So what is the point of having modules at all? If you have to install them anyway, why aren't they all just separate projects? Ok, lets say I install the Core project, is there a way in my Integration-Tests to get a filename for that project? Core creates a tar.bz2 file, and my integration tests need to extract the tar.bz2 to a temp directory, then run some programs and verify the expected output. As for calling mvn compile from a subproject and expecting that it will go build the parent and all modules, that's just not how Maven works. You can build from the top (parent) and get this kind of build, but not from modules themselves. Poop. -- Joshua ChaitinPollak Software Engineer Kiva Systems - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: exec-maven-plugin - how to skip execution in a sub-project
This should work. In root/pom.xml, in the exec plugin config, set inherited=false. plugin artifactIdmaven-exec-plugin/artifactId inheritedfalse/inherited Alternatively, you could put the exec plugin in a profile, and only use that profile when building from the root ie -Pdoexec. Wayne On 9/4/07, szefo [EMAIL PROTECTED] wrote: Hi, My project has a structure similar to this: root +child1 +child2 I use the exec goal in the root project. During the compilation process of both children the exec goal from root project is executed and causes errors - thus I would like to skip it. I would like it to be executed only during the compilation of the root project. How can I achieve it? Thanks in advance. Tom -- View this message in context: http://www.nabble.com/exec-maven-plugin--%3E-how-to-skip-execution-in-a-sub-project-tf4379678s177.html#a12484500 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: Project or module depends on assembly of another?
So what is the point of having modules at all? If you have to install them anyway, why aren't they all just separate projects? For all intents, they are (completely) separate projects. Ok, lets say I install the Core project, is there a way in my Integration-Tests to get a filename for that project? Core creates a tar.bz2 file, and my integration tests need to extract the tar.bz2 to a temp directory, then run some programs and verify the expected output. Explain this more, and perhaps we'll have some suggestions for how to handle it. How/when does core create a tar.bz2 file -- during compile, test, when? There are lots of things you can do with the assistance of buildhelper, assembly, and dependency plugins. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse setup for Multi-module project
Actually, I did select the Copy projects into Workspace checkbox so that may be the source of my problem. I've been experimenting a little bit and it seems that if I create the whole directory structure in C:\temp (c:\temp\TestApp) and then do the imports, everything seems to work as expected. If I go ahead and check in one of the submodules (say testcommon), and then delete the directory from disk and check out of the repository, the code is in my workspace as opposed to c:\temp\TestApp. In a team environment, this still seems pretty ugly. It appears that you have to jump through quite a few hoops to get this to work. Could you explain more about how you can import the top level project into eclipse? I was able to see the top level pom but it also had the sub modules as well. On 9/4/07, Francois Fernandes [EMAIL PROTECTED] wrote: One little Note about the importing of the projects: Ensure that Copy projects into workspace is deselected. Event the top level project can be imported into eclipse. To do this you generate the project files of the submodules and import them. Then create a new Project (not Java, a General Project) with exactly the name of your Top-Level Module (In your application: TestApp). Eclipse will not overwrite the directory. Instead it will discover the contents. Inside this project executing mvn install will be possible. Graham Leggett schrieb: On Tue, September 4, 2007 7:12 pm, Brian Smith wrote: First thing I noticed (and I think this is what you mentioned) is that the top level directory is not there. Because of this, I can't run Maven (mvn install) because the parent pom is not available. Why is the top level directory not there? One thing to make sure you do - check out the whole project using your source control tool of choice, then run mvn eclipse:eclipse from the root of your project, then import your projects into eclipse by selecting the root of your project and importing all the projects eclipse finds. Directory Structure Eclipse === === TestApp + testcommon + testcommon + testejb + testejb + testear + testear This is exactly what we have, and mvn install runs fine. Can you explain in more detail the exact steps you are trying to perform? Regards, Graham -- - 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: site deployment to url without parent information
The answer is exactly what you're trying to avoid...
You must configure the site again in your children pom. You might be
able to avoid typing the full site URL in each child pom by using a
property in the parent ie ${shared.site} which is set to
scp://webserver.mycompany.com/projects/.
Wayne
On 9/4/07, Martin Testrot [EMAIL PROTECTED] wrote:
Hello,
I try to configure the site deployment for our projects.
Because I don't want to include a distributionManagement.site section in all
of our project poms I tried to centralize these settings in a common parent
pom (rootpom) which is used as parent for all other projects.
The site configuration in this parent pom looks like:
site
idwebserver/id
urlscp://webserver.mycompany.com/projects//url
/site
Now I got the problem, that the computed URL for let's say MyTestproject
contains the artifactID from all super poms and is deployed to
../projects/rootpom/MyTestproject
Is it possible to ignore the parent artifactID and get something like:
/projects/MyTestproject
Thanks,
Martin
d.velop AG
digital business solutions
Schildarpstraße 6-8
48712 Gescher
Fon: +49 25 42 93 07-0
Fax: +49 25 42 93 07-20
HRB 4903, Amtsgericht Coesfeld, Vorstand: Christoph Pliete,
Aufsichtsratsvorsitzender: Dr. Helmut Bäumer
Diese E-Mail enthält vertrauliche oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich
erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie
diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
Mail ist nicht gestattet.
This e-mail may contain confidential or privileged information. If you are
not the intended recipient (or have received this e-mail in error) please
notify the sender immediately and destroy this e-mail. Any unauthorized
copying, disclosure or distribution of the material in this e-mail is
strictly forbidden.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: exec-maven-plugin - how to skip execution in a sub-project
Inherited=false works! Thanks Wayne Fay wrote: This should work. In root/pom.xml, in the exec plugin config, set inherited=false. plugin artifactIdmaven-exec-plugin/artifactId inheritedfalse/inherited Alternatively, you could put the exec plugin in a profile, and only use that profile when building from the root ie -Pdoexec. Wayne On 9/4/07, szefo [EMAIL PROTECTED] wrote: Hi, My project has a structure similar to this: root +child1 +child2 I use the exec goal in the root project. During the compilation process of both children the exec goal from root project is executed and causes errors - thus I would like to skip it. I would like it to be executed only during the compilation of the root project. How can I achieve it? Thanks in advance. Tom -- View this message in context: http://www.nabble.com/exec-maven-plugin--%3E-how-to-skip-execution-in-a-sub-project-tf4379678s177.html#a12484500 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/exec-maven-plugin--%3E-how-to-skip-execution-in-a-sub-project-tf4379678s177.html#a12485061 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: Eclipse setup for Multi-module project
I may be running into a couple of different issues. When I did my import, I selected the Copy projects into workspace which appears to ignore the top level directory. Also, I was trying to use Eclipse to check in/out of CVS. It appears that you don't use Eclipse to check the code into your workspace. If I'm understanding you correctly, you checkout to a temp directory and then import into Eclipse to do your work. Doesn't this cause problems in a team environment? Everyone would have to agree on the directory structure where the code will be checked out to? On 9/4/07, Graham Leggett [EMAIL PROTECTED] wrote: On Tue, September 4, 2007 7:12 pm, Brian Smith wrote: First thing I noticed (and I think this is what you mentioned) is that the top level directory is not there. Because of this, I can't run Maven (mvn install) because the parent pom is not available. Why is the top level directory not there? One thing to make sure you do - check out the whole project using your source control tool of choice, then run mvn eclipse:eclipse from the root of your project, then import your projects into eclipse by selecting the root of your project and importing all the projects eclipse finds. Directory Structure Eclipse === === TestApp + testcommon + testcommon + testejb + testejb + testear + testear This is exactly what we have, and mvn install runs fine. Can you explain in more detail the exact steps you are trying to perform? Regards, Graham -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse setup for Multi-module project
Brian Smith schrieb: Actually, I did select the Copy projects into Workspace checkbox so that may be the source of my problem. I've been experimenting a little bit and it seems that if I create the whole directory structure in C:\temp (c:\temp\TestApp) and then do the imports, everything seems to work as expected. If I go ahead and check in one of the submodules (say testcommon), and then delete the directory from disk and check out of the repository, the code is in my workspace as opposed to c:\temp\TestApp. In a team environment, this still seems pretty ugly. It appears that you have to jump through quite a few hoops to get this to work. If you have a multi-module project beeing organized in a hierarchical way you'll have to checkin the top level directory (e.g. the TestApp) and not the submodules. Then checkout the whole project out of the repository, create the project files (mvn eclipse:eclipse) and import the projects. If you're looking for a easier eclipse-way of working with maven, have a look at the M2Eclipse plugin at: http://m2eclipse.codehaus.org/ This plugin will manage your project inside eclipse including all dependencies. Using this plugin all submodules won't be seperate projects. Instead all modules will be appear as source-folders inside your parent project. e.g. TestApp [Eclipse Project] + testcommon/src/main/java + testcommon/src/main/resources + testcommon/src/test/java + testcommon/src/test/resources + testejb/src/main/java + testejb/src/main/resources + testejb/src/test/java + testejb/src/test/resources + testear/src/main/java + testear/src/main/resources + testear/src/test/java + testear/src/test/resources Could you explain more about how you can import the top level project into eclipse? I was able to see the top level pom but it also had the sub modules as well. This is how it is expected to be. Eclipse is only representing the file structure beeing on the disk. On 9/4/07, Francois Fernandes [EMAIL PROTECTED] wrote: One little Note about the importing of the projects: Ensure that Copy projects into workspace is deselected. Event the top level project can be imported into eclipse. To do this you generate the project files of the submodules and import them. Then create a new Project (not Java, a General Project) with exactly the name of your Top-Level Module (In your application: TestApp). Eclipse will not overwrite the directory. Instead it will discover the contents. Inside this project executing mvn install will be possible. Graham Leggett schrieb: On Tue, September 4, 2007 7:12 pm, Brian Smith wrote: First thing I noticed (and I think this is what you mentioned) is that the top level directory is not there. Because of this, I can't run Maven (mvn install) because the parent pom is not available. Why is the top level directory not there? One thing to make sure you do - check out the whole project using your source control tool of choice, then run mvn eclipse:eclipse from the root of your project, then import your projects into eclipse by selecting the root of your project and importing all the projects eclipse finds. Directory Structure Eclipse === === TestApp + testcommon + testcommon + testejb + testejb + testear + testear This is exactly what we have, and mvn install runs fine. Can you explain in more detail the exact steps you are trying to perform? Regards, Graham -- - 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: Project or module depends on assembly of another?
On Sep 4, 2007, at 3:20 PM, Wayne Fay wrote: So what is the point of having modules at all? If you have to install them anyway, why aren't they all just separate projects? For all intents, they are (completely) separate projects. Ok, lets say I install the Core project, is there a way in my Integration-Tests to get a filename for that project? Core creates a tar.bz2 file, and my integration tests need to extract the tar.bz2 to a temp directory, then run some programs and verify the expected output. Explain this more, and perhaps we'll have some suggestions for how to handle it. How/when does core create a tar.bz2 file -- during compile, test, when? There are lots of things you can do with the assistance of buildhelper, assembly, and dependency plugins. ok, so mvn package in core creates a target/MyProj-.tar.bz2 file. In integration-test, I'd like to take this tar.bz2 file and do the following (programmatically): tar jxvf MyProj-Core.tar.bz2 MyProj-Core/bin/runProgram And then validate the output of runProgram. Ideally, I would write Java code (as a junit test) to call System.exec() which would monitor MyProj-Core/bin/runProgram. So what I'm looking for is a way for maven to take a tarball, and extract it to a known location before calling the integration-test phase. Heck, even a suggestion of how my Java code could get a handle on the path to the filename of a specific dependancy (MyProj-Core) so it would know what file to extract, would be a big help. Does that explain what I'm trying to do? Thanks, Josh -- Joshua ChaitinPollak Software Engineer Kiva Systems - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse setup for Multi-module project
use the latest snapshot of m2eclipse, run mvn eclipse:m2eclipse the lastest snapshot will automagically introduce project referecences for projects depended upon... very handy for refactoring quickly On Wednesday 05 September 2007 03:20, Graham Leggett wrote: On Tue, September 4, 2007 5:08 pm, Brian Smith wrote: Has anyone come up with a decent way to setup a project in Eclipse that will support a multi-module project? I normally set up the project in maven, then run mvn eclipse:eclipse, and then use import existing project into workspace. Let maven do all the work, not eclipse. (We use this method to set up a set of multi-module projects, including one multi-module project with an eclipse plugin in it, the fun) Regards, Graham -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: NoClassDefFoundError: org/apache/log4j/Category
Hi Dennis, Thank you for your helpful note. I tried specifying the property to turn on common-logging 1.1 diags using all of the following but did not get any output: * mvn -Dorg.apache.commons.logging.diagnostics.dest=STDOUT cargo:start * env MAVEN_OPTS=-Dorg.apache.commons.logging.diagnostics.dest=STDOUT mvn cargo:start What am I doing wrong? Thanks for your help. Dennis Lundberg wrote: This is a classic, but really has nothing to do with Maven. The root cause is that commons-logging and log4j are in different class loaders. The best way to track down what is going on is to install commons-logging 1.1 (if you are not already using that version) and to turn on diagnostics [1]. Commons-logging might be installed in the container and/or your webapp, so make sure you install 1.1 everywhere. [1] http://commons.apache.org/logging/troubleshooting.html Farrukh Najmi wrote: Hello, I am using cargo-maven2-plugin for deploying my webapp into my webcontainer. I have no problems using tomcat5x profile but when I use the jetty6x profile with: container containerIdjetty6x/containerId typeembedded/type /container I get the following exception... Caused by: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@13ce64f6 for org.apache.commons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Category) at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:413) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529) ... 28 more Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Category at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357) at java.lang.Class.getConstructor0(Class.java:2671) at java.lang.Class.getConstructor(Class.java:1629) at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:410) ... 29 more Having scanned the web I find the following thread that looks similar and indicates some sort of classloader issue: http://www.nabble.com/Issue-stopping-Resin-3.0.23-with-Cargo-t3270890.html However, I cannot figure out what I need to do to fix the problem. Thanks for any help on this show stopper issue as I would really like to use jetty6 for deployment. -- Regards, Farrukh Web: http://www.wellfleetsoftware.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: release plugin configuration
Can't you disable the Junit tests normally? -Dmaven.test.skip=true It means some extra typing on each release though. -- Daniel Siegmann FJA-US, Inc. 512 7th Ave. 15th Flr. New York, NY 10018 (212) 840-2618 x139 -Original Message- From: Marcel Schutte [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 04, 2007 12:05 PM To: Maven Users List Subject: Re: release plugin configuration I want to run test in release:prepare but skip them in release:perform. And that's because I just don't want to run them twice on exactly the same code. - Original Message From: Michael McCallum [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Tuesday, September 4, 2007 4:38:12 PM Subject: Re: release plugin configuration why do you want to skip tests in release:prepare? On Wednesday 05 September 2007 02:20, Marcel Schutte wrote: Hi Arnaud, Thanks for your reply. You're right that I can use activeProfile to make one profile default. But that won't help in my situation: I would need some 'profileA' active when running release:prepare and 'profileB' active for release:perform. This is something I think can only be done by specifying them as in 'mvn -P profileA release:prepare'. Or do you have another suggestion? Marcel - Original Message From: Arnaud WEBER [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Tuesday, September 4, 2007 3:36:52 PM Subject: Re: release plugin configuration Hello, I believe the usage of profiles is the right way to pass arguments. But you're wrong saying you have to specify which profile when invoking the goals. In your case, you can do something like that : profile idenv-dev/id properties maven.test.skiptrue/maven.test.skip /properties /profile /profiles activeProfiles activeProfileenv-dev/activeProfile /activeProfiles by adding the activeProfile tag, you'll be able to select a profile which will be always used on that machine. Arnaud Marcel Schutte a écrit : Hello all, Is there a way to specify different configurations for the release:prepare and release:perform goals without using profiles? Specifically, what I'm trying to do is pass configuration arguments-Dmaven.test.skip=false/arguments /configuration to release:prepare but run release:perform with configuration arguments-Dmaven.test.skip=true/arguments /configuration I know this can be done using different profiles, but the problem is that you need to specify them when invoking the goals. What I want is to describe the default behavior when invoking 'mvn release:prepare'.. Using two executions didn't work, they simply aren't used. This is in line with what is stated at the bottom of http://maven.apache.org/guides/mini/guide-configuring-plugins.html So, any other suggestions? Regards, Marcel _ ___ Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=listsid=396545433 - 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] ___ _ Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool. http://autos.yahoo.com/carfinder/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. http://sims.yahoo.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: Question on automatically adding files to a local repository
See, I define all my jar versions in a settings.xml and this works fine but somehow when it sees that pom.xml, it gets confused and cannot pickup any versions. Easy answer -- don't do that. Use dependencyManagement and pluginManagement to control versions. And where it makes sense, insert these nodes in a shared parent pom to further reduce management overhead. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: xdoclet plugin and weblogic-ejb-jar.xml descriptor
You could always try ejbgen. I was going to build that into the Weblogic plugin but most people have gone to JPA instead so there was not much demand. Scott Ryan CTO Soaring Eagle L.L.C. Denver, Co. 80129 www.soaringeagleco.com www.theryansplace.com (303) 263-3044 [EMAIL PROTECTED] On Sep 4, 2007, at 9:30 AM, Brian Smith wrote: I'm using Weblogic 9.2. I think you're correct in that the weblogic plugin only works for versions 8.x and earlier. I haven't found any great solutions for this hurdle yet. On 8/31/07, Scott Ryan [EMAIL PROTECTED] wrote: What version of Weblogic are you using? You can use the weblogic tag to generate the XML files but as far as I know xdoclet can only generate xml files for 8.x and prior. 9.x and 10.x are not supported but then maybe you should be using JPA, EJB 3.0 or Hibernate by then. Scott Ryan CTO Soaring Eagle L.L.C. Denver, Co. 80129 www.soaringeagleco.com www.theryansplace.com (303) 263-3044 [EMAIL PROTECTED] On Aug 31, 2007, at 9:34 AM, Brian Smith wrote: I'm working on a simple HelloWorldEJB stateless session bean that I want to run in Weblogic. I'm using the xdoclet plugin and xdoclet is able to generate the home/remote classes. Should xdoclet be able to generate the weblogic-ejb-jar.xml descriptor? If so, how do I do this? Is there a special tag in the EJB source code or is there something in the pom I need to specify? I'm guessing this a task of xdoclet instead of maven but I'm not sure. Any input would be appreciated. Thanks, Brian
Call for 2.1 Proposals
As we are approaching an alpha release of 2.1, the Maven Team would like to make a final call for proposals. The cutoff date for new proposals will be Friday 9/21. During this time, we will review and discuss new proposals and make a final cut at scheduling the 2.1 release. The current aim is to keep the number of newly included proposals small so that we can get a release out sooner than later. Proposals that are accepted but not scheduled for 2.1.0 will be tentatively scheduled for 2.1.x or 2.2 If you have an idea you would like evaluated, please create a new wiki page here: (for users) http://docs.codehaus.org/display/MAVENUSER/User+Proposals or (for developers) http://docs.codehaus.org/display/MAVEN/All+Proposals --The Maven Team
Re: Q4E, a new Eclipse plugin for Maven
Hi Mark, That's certainly a good point - thanks for bringing it up. This would definitely be the ideal scenario and the Q developers initially intended to collaborate around the one codebase (in fact, DevZuz also sponsored the initial development of m2eclipse). However, as you'll see from the differences listed earlier, there are some different approaches that we wanted to try. The m2eclipse developers and Q developers have agreed to disagree on these points and continue with separate projects. We hope that the competition will actually make both solutions better, and of course we will certainly continue to collaborate wherever possible, particularly in the space of the Maven embedder here at the Maven project. Q has made rapid progress over recent times, and with the essential features now in place we hope to continue to add new and unique features, as well as gaining tighter integration with the Eclipse ecosystem. I'd encourage anyone to try both for themselves and use whichever solution best suits their current needs, and is most responsive to their desired features. On 9/4/07, Mark Hobson [EMAIL PROTECTED] wrote: Aside from license issues, I'm confused as to why we now have two Maven plugins for Eclipse? Surely it'd make sense for the two projects to collaborate to accelerate development, rather than having two plugins that are both rather thin on the ground in terms of features? Mark On 04/09/07, Carlos Sanchez [EMAIL PROTECTED] wrote: I'd like to introduce the Q for Eclipse (Q4E) project http://code.google.com/p/q4e/, an Eclipse plugin for Maven. (see the formatted version at http://www.jroller.com/carlossg/entry/introducing_q4e_a_new_eclipse) === Features === * running Maven goals from the IDE * dependency managing using the Maven POM, with automatic download of dependencies * dependency graphing * direct import of Maven 2 projects * wizard for creation of new projects using the archetype mechanism * modular approach to improve reusability by other Eclipse projects ... and more to come === FAQ http://code.google.com/p/q4e/wiki/FAQ === * What can this Eclipse plugin do? It will allow you to run Maven goals from the Eclipse IDE, create new Maven projects using archetypes, import Maven projects without any intermediate steps, view the dependencies of your project in a graph,... we will keep adding features with the time * How do I install it? Refer to Installation http://code.google.com/p/q4e/wiki/Installation * What are the differences between this plugin and m2eclipse (aka Tycho)? The objective of this plugin is to be part of the Eclipse Foundation, for that reason the license is EPL and we are going to follow the foundation procedures. Thanks to the sponsorship of DevZuz, an Eclipse Strategic Developer Member we are in a good position to achieve this goal. Besides the objective, there are technical differences. While m2eclipse shows Maven output in a console, Q is based in events and will show them in an organized way that allows filtering by severity, search,... Functionality like the dependency graph, direct import of projects or creation of new projects using the archetype mechanism are only present in Q. * Why the name Q? Q, named after the special agent Q in the James Bond books and movies. No double meaning or anything like that, we are just James Bond fans ;) === Collaborating === The project is licensed under the EPL and collaborations are welcome, please join the user mailing list http://groups.google.com/group/q4e-users to be informed of updates, or the developers list http://groups.google.com/group/q4e-dev if you want to help with the development or extend the plugin. You can also take a look at the list of known issues. http://code.google.com/p/q4e/issues/list -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - 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 could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Q4E, a new Eclipse plugin for Maven
Hi Antonio, The Q developers and DevZuz are committed to Q being a community driven project, developed and planned openly. We've just added another committer, Abel, who became interested after his work on Candy for AppFuse, and we'd certainly welcome any users who would like to get involved in the ongoing development. In addition, we continue to work with other Eclipse projects to ensure that we achieve the best possible fit in the Eclipse ecosystem, and best experience for Eclipse users. Thanks for asking! On 9/4/07, Antonio Petrelli [EMAIL PROTECTED] wrote: 2007/9/4, Mark Hobson [EMAIL PROTECTED]: Aside from license issues, I'm confused as to why we now have two Maven plugins for Eclipse? Surely it'd make sense for the two projects to collaborate to accelerate development, rather than having two plugins that are both rather thin on the ground in terms of features? It reminds me of the battle between Subclipse and Subversive, but in this case, Subversive is not community-driven. Carlos, is Q4E community-driven or privately-driven? Antonio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
