Test results in shell project
Hi, I would like to include the building and testing of a Python project into Continuum. I can build the project fine as a Shell project, but is there any way to have Continuum recognize the test results? Is it enough to write out a jUnit-style XML file in the build directory somewhere that Continuum can pick up, or is there more too it? Thanks, Wim. -- ir. Wim Heirman, ELIS Department, Ghent University, Belgium Phone: +32-9-264.95.27 E-mail: [EMAIL PROTECTED] http://www.elis.UGent.be/~wheirman/
Re: Continuum report incorrect build results?
If you use maven 2.0.7, you must patch mvn.bat. It is explains in continuum FAQs Emmanuel On Thu, Feb 21, 2008 at 12:41 AM, Tawfik, Sameh E [EMAIL PROTECTED] wrote: When Continuum runs my maven 2 project, it send an email: [continuum] BUILD SUCCESSFUL:, but when I checked the build results I found out the build failed when it was building the last component, so why is Continuum is reporting success when the build failed? Does anyone know how to make Continuum detect this failure and correctly report back this result? The following is the build failed error messages: [javac] 33. ERROR in C:\Auto_Builds\working-directory\12\ csvimport\job\DelimImportJob.java (at line 128) [javac] ls.setCharacterSet(DelimitedLayoutImpl.CHARACTER_SET_EBCIDIC); [javac] ^ [javac] DelimitedLayoutImpl.CHARACTER_SET_EBCIDIC cannot be resolved BUILD FAILED C:\Auto_Builds\working-directory\12\mabc\build.xml:32: The following error occurred while executing this line: C:\Auto_Builds\working-directory\12\mabc\build.xml:16: The following error occurred while executing this line: C:\Auto_Builds\working-directory\12\mabc\build.xml:291: The following error occurred while executing this line: C:\Auto_Builds\working-directory\12\mabc\build.xml:258: Compile failed; see the compiler error output for details. Total time: 13 seconds [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error executing command line. Exit code:13 [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 25 minutes 14 seconds [INFO] Finished at: Wed Feb 20 15:23:17 PST 2008 [INFO] Final Memory: 23M/63M [INFO] This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.
Re: Windows path length limitation
its a limitation of the file system...not a lot we can do about it :( On Tue, Feb 19, 2008 at 12:33 PM, KURT TOMETICH [EMAIL PROTECTED] wrote: Thanks for the quick response. That was my fall-back option, but I wasn't sure if there was just an easy way to configure it to use an absolute path. Shortening the root path length should help, but its still possible to reach the limit. Kurt Date: Tue, 19 Feb 2008 18:19:23 +0100 From: [EMAIL PROTECTED] To: continuum-users@maven.apache.org Subject: Re: Windows path length limitation Try to configure Build Output Directory and Working Directory to c:\\bd and c:\\wd Go to the configuration entry of the administration menu [1] -- Olivier [1] http://maven.apache.org/continuum/docs/1.1/administrator_guides/configuration.html 2008/2/19, KURT TOMETICH [EMAIL PROTECTED]: Is there a way to configure Continuum to checkout project from Subversion using an absolute path instead of a relative path? This would solve the path limitation issue on Windows. I ran into the problem where the path was too long and was able to verify that if I checked out the project using an absolute path it worked fine. Is this something I can configure on and end user system or does the project have to be recompiled to make this change? Kurt -- jesse mcconnell [EMAIL PROTECTED]
Re: How to apply a patch
if you have it in patch format then you would use the patch command something like patch -p0 issue.patch jesse On Tue, Feb 19, 2008 at 1:27 PM, Rafael da Silva Chiarinelli [EMAIL PROTECTED] wrote: Hi everyone, how can I apply a given patch in order to fix a bug? Best Regards, Rafael -- jesse mcconnell [EMAIL PROTECTED]
RE: Windows path length limitation
I agree its a limitation of the file system; however, if Continuum would feed Subversion an absolute path (when running svn commands) as opposed to a relative path then their would not be a 256 character limit. I tried this and it does work when I send Subversion an absolute path and it fails when I send it a relative path. I found an article about it online here: http://svn.haxx.se/users/archive-2005-02/1088.shtml. This shouldn't be a hard change to make and would allow Windows users to not have to worry about running into this problem. Kurt Date: Thu, 21 Feb 2008 10:48:08 -0600 From: [EMAIL PROTECTED] To: continuum-users@maven.apache.org Subject: Re: Windows path length limitation its a limitation of the file system...not a lot we can do about it :( On Tue, Feb 19, 2008 at 12:33 PM, KURT TOMETICH [EMAIL PROTECTED] wrote: Thanks for the quick response. That was my fall-back option, but I wasn't sure if there was just an easy way to configure it to use an absolute path. Shortening the root path length should help, but its still possible to reach the limit. Kurt Date: Tue, 19 Feb 2008 18:19:23 +0100 From: [EMAIL PROTECTED] To: continuum-users@maven.apache.org Subject: Re: Windows path length limitation Try to configure Build Output Directory and Working Directory to c:\\bd and c:\\wd Go to the configuration entry of the administration menu [1] -- Olivier [1] http://maven.apache.org/continuum/docs/1.1/administrator_guides/configuration.html 2008/2/19, KURT TOMETICH [EMAIL PROTECTED]: Is there a way to configure Continuum to checkout project from Subversion using an absolute path instead of a relative path? This would solve the path limitation issue on Windows. I ran into the problem where the path was too long and was able to verify that if I checked out the project using an absolute path it worked fine. Is this something I can configure on and end user system or does the project have to be recompiled to make this change? Kurt -- jesse mcconnell [EMAIL PROTECTED]
Re: How to apply a patch
Jesse McConnell wrote: if you have it in patch format then you would use the patch command something like patch -p0 issue.patch jesse On Tue, Feb 19, 2008 at 1:27 PM, Rafael da Silva Chiarinelli [EMAIL PROTECTED] wrote: Hi everyone, how can I apply a given patch in order to fix a bug? Best Regards, Rafael hmmm, tks a lot! Rafael
RE: Windows path length limitation
I went ahead and logged an improvement to Maven SCM (http://jira.codehaus.org/browse/SCM-368). Hopefully they will fix this so Windows users won't have to experience this shortcoming. Kurt Date: Thu, 21 Feb 2008 11:22:36 -0600 From: [EMAIL PROTECTED] To: continuum-users@maven.apache.org Subject: Re: Windows path length limitation oh interesting...You should check and see if there is an issue on this under maven SCM and if not open an issue there with this information http://jira.codehaus.org/browse/SCM jesse On Thu, Feb 21, 2008 at 11:15 AM, KURT TOMETICH [EMAIL PROTECTED] wrote: I agree its a limitation of the file system; however, if Continuum would feed Subversion an absolute path (when running svn commands) as opposed to a relative path then their would not be a 256 character limit. I tried this and it does work when I send Subversion an absolute path and it fails when I send it a relative path. I found an article about it online here: http://svn.haxx.se/users/archive-2005-02/1088.shtml. This shouldn't be a hard change to make and would allow Windows users to not have to worry about running into this problem. Kurt Date: Thu, 21 Feb 2008 10:48:08 -0600 From: [EMAIL PROTECTED] To: continuum-users@maven.apache.org Subject: Re: Windows path length limitation its a limitation of the file system...not a lot we can do about it :( On Tue, Feb 19, 2008 at 12:33 PM, KURT TOMETICH [EMAIL PROTECTED] wrote: Thanks for the quick response. That was my fall-back option, but I wasn't sure if there was just an easy way to configure it to use an absolute path. Shortening the root path length should help, but its still possible to reach the limit. Kurt Date: Tue, 19 Feb 2008 18:19:23 +0100 From: [EMAIL PROTECTED] To: continuum-users@maven.apache.org Subject: Re: Windows path length limitation Try to configure Build Output Directory and Working Directory to c:\\bd and c:\\wd Go to the configuration entry of the administration menu [1] -- Olivier [1] http://maven.apache.org/continuum/docs/1.1/administrator_guides/configuration.html 2008/2/19, KURT TOMETICH [EMAIL PROTECTED]: Is there a way to configure Continuum to checkout project from Subversion using an absolute path instead of a relative path? This would solve the path limitation issue on Windows. I ran into the problem where the path was too long and was able to verify that if I checked out the project using an absolute path it worked fine. Is this something I can configure on and end user system or does the project have to be recompiled to make this change? Kurt -- jesse mcconnell [EMAIL PROTECTED] -- jesse mcconnell [EMAIL PROTECTED]
Re: maven-eclipse-plugin writes to src/main/webapp
I think we have several problems with manifest in 2.5-SNAPSHOT :-( wtpmanifest = true creates several problems. We noticed this one : http://jira.codehaus.org/browse/MECLIPSE-389 It can be (or not) related Arnaud On Thu, Feb 21, 2008 at 8:20 AM, Martin Höller [EMAIL PROTECTED] wrote: On Wednesday 20 February 2008 wrote Graham Leggett: Martin Höller wrote: I just noticed that the maven-eclipse-plugin (2.5-SNAPHSOT) writes a MANIFEST.MF output to src/main/webapp/META-INF when mvn eclipse:eclipse is called for a web-application. Is this behaviour intentional? I wouldn't expect maven or any plugin to write something into src/main. Is your project marked as a pde project? No, it's not, it's a WTP 2.0 project. My plugin configuration is as follows: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId version2.5-SNAPSHOT/version configuration downloadSourcesfalse/downloadSources downloadJavadocsfalse/downloadJavadocs wtpversion2.0/wtpversion wtpmanifesttrue/wtpmanifest /configuration /plugin If the MANIFEST.MF is needed by eclipse, couldn't it be written to target/ and eclipse be configured to use that instead, just as it happens for EARs? Not practically, no. Eclipse does not have a clear distinction between source directories and target directories, so you need to modify the files where they lie, which can be annoying, particularly for Eclipse plugin builds. Well, this file is not created by eclipse but by the m-eclipse-p. And I would say this plugin shouldn't write to src/main/... What I want is already done for EARs: an application.xml is required for a valid EAR, so m-eclipse-p creates one in target/eclipseEar/META-INF/ and points eclipse to this file as the application descriptor. I think this should also be possible for WARs, shouldn't it? - martin -- Martin Höller | [EMAIL PROTECTED] *x Software + Systeme | http://www.xss.co.at/ Karmarschgasse 51/2/20 | Tel: +43-1-6060114-30 A-1100 Vienna, Austria | Fax: +43-1-6060114-71 -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ...
Re: maven-eclipse-plugin writes to src/main/webapp
Martin Höller wrote: No, it's not, it's a WTP 2.0 project. My plugin configuration is as follows: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId version2.5-SNAPSHOT/version configuration downloadSourcesfalse/downloadSources downloadJavadocsfalse/downloadJavadocs wtpversion2.0/wtpversion wtpmanifesttrue/wtpmanifest /configuration /plugin What purpose does this serve? Well, this file is not created by eclipse but by the m-eclipse-p. And I would say this plugin shouldn't write to src/main/... The way Eclipse deals with manifest files is they are considered part of the source code, not a generated artifact. As a result, if you want to synchronise Eclipse with anything in maven, you have to edit the existing files where Eclipse put them. Remember that unlike in the maven world, where absolutely everything is in the pom, and all other files are generated from scratch, in the Eclipse world information is scattered across the various files in the source tree. Maven can only edit a subset of the information in these files, as maven doesn't have enough knowledge to regenerate the file from scratch. Regards, Graham -- smime.p7s Description: S/MIME Cryptographic Signature
maven appends sub-project artifactId to urls - Please help
I have an organization POM, with common defs, including url templates
for scm and distribution.
Here are the relevant snippets, from the parent pom
scm
connectionscm:svn:https://www.myhost.com/svn/pub/${project.name}/trunk/connection
developerConnectionscm:svn:https://www.myhost.com/svn/pub/${project.name}/trunk/developerConnection
urlhttp://www.myhost.com/websvn/${project.name}/trunk/url
/scm
site
iddoc/id
urldav:http://dav.myhost.com:8000/doc/${project.name}//url
/site
Here are the relevant snippets, from a test sub-pom
parent
...
/parent
artifactIdhello/artifactId
version0.17/version
packagingjar/packaging
nameHelloMvn/name
The problem is that the URLs of the effective pom of the sub-project has the
artifactId appended.
scm
connectionscm:svn:https://www.myhost.com/svn/pub/HelloMvn/trunk/hello/connection
developerConnectionscm:svn:https://www.myhost.com/svn/pub/HelloMvn/trunk/hello/developerConnection
urlhttp://www.myhost.com/websvn/HelloMvn/trunk/hello/url
/scm
site
iddoc/id
urldav:http://dav.myhost.com:8000/doc/HelloMvn/hello/url
/site
So my question is: How can I disable this feature, or configure the way it is
working?
As it stands right now, I consider this feature to be a bug. It's not
documented and I hardly see the benefit of it.
There was a mail trail touching this back in December, but it didn't come to a
conclusion
http://www.mail-archive.com/users@maven.apache.org/msg77123.html
Regards,
/jens
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-eclipse-plugin writes to src/main/webapp
On Thursday 21 February 2008 wrote Arnaud HERITIER: I think we have several problems with manifest in 2.5-SNAPSHOT :-( wtpmanifest = true creates several problems. We noticed this one : http://jira.codehaus.org/browse/MECLIPSE-389 It can be (or not) related It is (at least somehow) related. Should I file an extra issue for this one or just add a comment to MECLIPSE-389 and wait till it's eventually fixed? thanks, - martin -- Martin Höller | [EMAIL PROTECTED] *x Software + Systeme | http://www.xss.co.at/ Karmarschgasse 51/2/20 | Tel: +43-1-6060114-30 A-1100 Vienna, Austria | Fax: +43-1-6060114-71 signature.asc Description: This is a digitally signed message part.
Re: maven-eclipse-plugin writes to src/main/webapp
On Thursday 21 February 2008 wrote Graham Leggett: Martin Höller wrote: No, it's not, it's a WTP 2.0 project. My plugin configuration is as follows: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId version2.5-SNAPSHOT/version configuration downloadSourcesfalse/downloadSources downloadJavadocsfalse/downloadJavadocs wtpversion2.0/wtpversion wtpmanifesttrue/wtpmanifest /configuration /plugin What purpose does this serve? I need a MANIFEST.MF for the classpath (it's a skinny war as it is part of an EAR) Well, this file is not created by eclipse but by the m-eclipse-p. And I would say this plugin shouldn't write to src/main/... The way Eclipse deals with manifest files is they are considered part of the source code, not a generated artifact. Yeah, that's why I want maven to generate it for eclipse as maven has all the information that belongs into the MANIFEST.MF As a result, if you want to synchronise Eclipse with anything in maven, you have to edit the existing files where Eclipse put them. Eclipse didn't and wouldn't put MANIFEST.MF anywhere if it didn't exist, so either I create it by hand (what is not what I want) or let maven create it for me, which the m-eclipse-p obviously is designed for. It's just the location of the file that isn't configurable and has IMHO a bad default. thanks for you answer anyway, - martin -- Martin Höller | [EMAIL PROTECTED] *x Software + Systeme | http://www.xss.co.at/ Karmarschgasse 51/2/20 | Tel: +43-1-6060114-30 A-1100 Vienna, Austria | Fax: +43-1-6060114-71 signature.asc Description: This is a digitally signed message part.
RE: Surefire 2.4.1 classpath order
I took a copy of the project POM and put it in the surefire-integration-tests
directory. The tests failed. I then trawled through the project POM and then
its parent POM commenting out plugins, reporting, dependencies, and other bits
until the test passed.
The thing that was causing the test to fail was that in the parent POM:
defaultGoalpackage/defaultGoal
directorytarget/directory
finalName${pom.artifactId}-${pom.version}/finalName
sourceDirectory${basedir}/src/main/java/sourceDirectory
testSourceDirectory${basedir}/src/test/java/testSourceDirectory
testOutputDirectory${basedir}/target/test-classes/testOutputDirectory
outputDirectory${basedir}/target/classes/outputDirectory
Changing just testOutputDirectory to
testOutputDirectorytarget/test-classes/testOutputDirectory
Made the tests pass. I've no idea why. Do you want me to raise this as a bug?
Ben
This e-mail is confidential and intended solely for the use of the
individual(s) to whom it is addressed. Any views or opinions expressed are
those of the author. If you are not the intended recipient, please be advised
that any use, dissemination, printing or copying of this email is strictly
prohibited.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Overriding Plugin Configuration in Settings.xml
You need two profiles in your pom with the different settings. Then you can add the appropriate profile in the settings.xml and set activeByDefaulttrue/ for the one to use. Stefan DHARNA, AJAY [AG/1000] wrote: Please let me know if there is a way in which I can override my cargo plugin configuration and execution from a profile that is in my settings.xml. I want the project pom to remain the same, however, when I am running this project in tomcat on my machine, I would like to change the configuration and also change what goals it executes. Ajay - This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto, including its subsidiaries. The recipient of this e-mail is solely responsible for checking for the presence of Viruses or other Malware. Monsanto, along with its subsidiaries, accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. - -- best regards, Stefan Seidel software developer VUB Printmedia GmbH Chopinstraße 4 D-04103 Leipzig Germany tel.+49 (341) 9 60 50 07 fax.+49 (341) 9 60 50 92 mail. [EMAIL PROTECTED] web.www.vub.de HRB Köln 24015 UStID DE 122 649 251 GF Dr. Achim Preuss Neudorf, Dr. Christian Preuss Neudorf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Extending Maven2 plugins
Hi Stuart,
I tried it and it worked like a charm.
Great plugin !
Thanks a lot.
--
Julien
PS: thank you Rémy and Sahoo too for your answers
On Thu, Feb 21, 2008 at 11:45:09AM +0800, Stuart McCulloch wrote:
On 21/02/2008, Julien Stern [EMAIL PROTECTED] wrote:
Hi list,
I just tried to extend a plugin, by creating a local plugin
with a Mojo that extends (in the Java sense) an other Mojo
from an existing plugin.
It overrides the execute method and calls several super methods
along with doing its own work.
However, when I try to execute the plugin, none of the parameters
seem to be set and I keep on getting NullPointerExceptions.
For instance, project, as defined below in a super class in null.
/**
* POM.
*
* @parameter expression=${project}
* @readonly
* @required
*/
protected MavenProject project;
It that a bug? Is there a way to do want I'm trying to do?
Hi Julien,
when you build a maven plugin, the [plugin:descriptor] goal generates an XML
file
to target/classes/META-INF/maven/plugin.xml that tells the plexus container
what
fields need to be injected, and where to get them from (along with defaults,
etc.)
unfortunately, the tool used to generate the plugin.xml works on javadoc
comments
which means that when you extend a mojo from another project, it doesn't see
the
source (and therefore the javadoc) and doesn't add the fields to the
plugin.xml
this means when you come to use the extended mojo, a lot of the fields will
be null.
I do have a tool (another maven plugin) that will help add inherited fields
and goals
to the plugin.xml, which is documented here (may upload it to repo1 if it's
useful):
http://www.ops4j.org/projects/pax/construct/maven-inherit-plugin/index.html
however, you do need to have the plugin being extended as a dependency in
your
new plugin project, and some people have said this is not necessarily a good
thing
btw, if you have commit access to both codebases, another solution is to
refactor
the common code into a plexus component that can then be used in both
plugins.
HTH
Regards,
--
Julien
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Cheers, Stuart
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven appends sub-project artifactId to urls - Please help
Hi Jens,
you are complaining about an essential feature of maven. Having maven
automatically extend the urls, scm urls, site urls etc. with the list of
parent artifact ids is crucial for multi-module projects. No-one would
want to enter this information again and again through several levels of
child modules which are hosted within a common directory tree. I agree
that the docs are not clear about it, at least I couldn't find it
documented. I see your point, and there are other problems, like when
the directory name of a sub-module is not equal to the artifact id, but
in general it is an important feature.
How to disable - I don't know. Maybe you will need to file two things in
JIRA: a documentation request and a feature request to disable it.
HTH,
Stefan
Jens Riboe wrote:
I have an organization POM, with common defs, including url templates
for scm and distribution.
Here are the relevant snippets, from the parent pom
scm
connectionscm:svn:https://www.myhost.com/svn/pub/${project.name}/trunk/connection
developerConnectionscm:svn:https://www.myhost.com/svn/pub/${project.name}/trunk/developerConnection
urlhttp://www.myhost.com/websvn/${project.name}/trunk/url
/scm
site
iddoc/id
urldav:http://dav.myhost.com:8000/doc/${project.name}//url
/site
Here are the relevant snippets, from a test sub-pom
parent
...
/parent
artifactIdhello/artifactId
version0.17/version
packagingjar/packaging
nameHelloMvn/name
The problem is that the URLs of the effective pom of the sub-project has
the artifactId appended.
scm
connectionscm:svn:https://www.myhost.com/svn/pub/HelloMvn/trunk/hello/connection
developerConnectionscm:svn:https://www.myhost.com/svn/pub/HelloMvn/trunk/hello/developerConnection
urlhttp://www.myhost.com/websvn/HelloMvn/trunk/hello/url
/scm
site
iddoc/id
urldav:http://dav.myhost.com:8000/doc/HelloMvn/hello/url
/site
So my question is: How can I disable this feature, or configure the
way it is working?
As it stands right now, I consider this feature to be a bug. It's not
documented and I hardly see the benefit of it.
There was a mail trail touching this back in December, but it didn't
come to a conclusion
http://www.mail-archive.com/users@maven.apache.org/msg77123.html
Regards,
/jens
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
best regards,
Stefan Seidel
software developer
VUB Printmedia GmbH
Chopinstraße 4
D-04103 Leipzig
Germany
tel.+49 (341) 9 60 50 07
fax.+49 (341) 9 60 50 92
mail. [EMAIL PROTECTED]
web.www.vub.de
HRB Köln 24015
UStID DE 122 649 251
GF Dr. Achim Preuss Neudorf,
Dr. Christian Preuss Neudorf
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Shared modules and versioning
Create an extra artifact A of packing type pom. Declare the dependency to the shared module M within A, with the version you want/need. In your projects P1, P2, ... declare a dependency on A (here, a version range is useful, since A is your own project). Thus, all projects P1...Px use the same version of M, namely the one you declare in A. If you want to change to another version of M, change it in A and deploy/release it. regards, Stefan EJ Ciramella wrote: So we have a module that is shared across multiple deployable units. It's imperative that each deployable unit uses the SAME version of this dependency. If these deployable units are in their OWN project structure, how do you uniformly enforce they use the same version without letting each deployable unit have it's very own dependency listing. We've tried making the version a property in our current parent project, but this doesn't feel like it's the correct place to put them (we're slowly becoming more and more modular - and realizing there's no true parent to all projects). How have people solved this in scenario? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven appends sub-project artifactId to urls - Please help
-Original Message- From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] Sent: 21 February 2008 09:52 To: Maven Users List Subject: Re: maven appends sub-project artifactId to urls - Please help Hi Jens, you are complaining about an essential feature of maven. Having maven automatically extend the urls, scm urls, site urls etc. with the list of parent artifact ids is crucial for multi-module projects. No-one would want to enter this information again and again through several levels of child modules which are hosted within a common directory tree. I agree that the docs are not clear about it, at least I couldn't find it documented. I see your point, and there are other problems, like when the directory name of a sub-module is not equal to the artifact id, but in general it is an important feature. How to disable - I don't know. Maybe you will need to file two things in JIRA: a documentation request and a feature request to disable it. HTH, Stefan We have a similar problem to Jens as our projects are structured in Eclipse friendly structure, e.g. ParentProject - pom.xml ChildProject1 - pom.xml - src/java etc ChildProject2 - pom.xml - src/java etc Which is different to the standard Maven dir structure, e.g. ParentProject - pom.xml - ChildProject1 - pom.xml - src/java etc - ChildProject2 - pom.xml - src/java etc It would make sense to me to be able to specify a different naming strategy, perhaps the Maven one is used as a default, but you could define a different naming strategy and set that to be used instead, e.g. scm namingStrategy=org.apache.maven.scm.FlatTreeNamingStrategy ... /scm That doesn't append artifactIds. Then if people had other weird and whacky ways of structuring projects they could write custom naming strategies to behave in accordance with their structures. Ben This e-mail is confidential and intended solely for the use of the individual(s) to whom it is addressed. Any views or opinions expressed are those of the author. If you are not the intended recipient, please be advised that any use, dissemination, printing or copying of this email is strictly prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Adding a folder to classpath at runtime
Hi,
Is it possible to add a newly created folder(and its contents) to the
classpath at the runtime(on the fly) using maven.
I am using this pde-maven-plugin where I am copying the dependencies to the
lib folder inside the ${basedir} and wants it to be available while
compiling the source code.
Any help?
Regards,
Amit
Re: maven appends sub-project artifactId to urls - Please help
I added a comment to http://jira.codehaus.org/browse/MNG-3244. You may want to add you votes. Apparently, it was originally planned to not append the artifact id unless the URL would end with a /. Stefan Ben Lidgey wrote: -Original Message- From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] Sent: 21 February 2008 09:52 To: Maven Users List Subject: Re: maven appends sub-project artifactId to urls - Please help Hi Jens, you are complaining about an essential feature of maven. Having maven automatically extend the urls, scm urls, site urls etc. with the list of parent artifact ids is crucial for multi-module projects. No-one would want to enter this information again and again through several levels of child modules which are hosted within a common directory tree. I agree that the docs are not clear about it, at least I couldn't find it documented. I see your point, and there are other problems, like when the directory name of a sub-module is not equal to the artifact id, but in general it is an important feature. How to disable - I don't know. Maybe you will need to file two things in JIRA: a documentation request and a feature request to disable it. HTH, Stefan We have a similar problem to Jens as our projects are structured in Eclipse friendly structure, e.g. ParentProject - pom.xml ChildProject1 - pom.xml - src/java etc ChildProject2 - pom.xml - src/java etc Which is different to the standard Maven dir structure, e.g. ParentProject - pom.xml - ChildProject1 - pom.xml - src/java etc - ChildProject2 - pom.xml - src/java etc It would make sense to me to be able to specify a different naming strategy, perhaps the Maven one is used as a default, but you could define a different naming strategy and set that to be used instead, e.g. scm namingStrategy=org.apache.maven.scm.FlatTreeNamingStrategy ... /scm That doesn't append artifactIds. Then if people had other weird and whacky ways of structuring projects they could write custom naming strategies to behave in accordance with their structures. Ben This e-mail is confidential and intended solely for the use of the individual(s) to whom it is addressed. Any views or opinions expressed are those of the author. If you are not the intended recipient, please be advised that any use, dissemination, printing or copying of this email is strictly prohibited. - 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]
fixed absolute references on referenced projects (Maven Ant Plugin)
Hi User Group
I have found and fix one problem with Maven Ant plugin. I had worked with
multi-module maven projects and found that Maven Ant plugin generate absolute
path for referenced projects (another modules). Ant doesn't find them during
compilation. So I have fix plugin - it calculates relative path to referenced
projects.
I am working on Windows XP, Java 1.5.0_11.
maven-build.xml before fix:
!-- ==
--
!-- Defining classpaths
--
!-- ==
--
path id=build.classpath
fileset dir=${maven.repo.local}
include name=javax/transaction/jta/1.0.1B/jta-1.0.1B.jar/
include name=javax/servlet/servlet-api/2.4/servlet-api-2.4.jar/
!-- other libs --
include
name=D:/dev/projects/trunk/src/Security/target/Security-1.0.0.21-SNAPSHOT.jar/
include
name=D:/dev/projects/trunk/src/BusinessLogic/target/BusinessLogic-1.0.0.21-SNAPSHOT.jar/
!-- other module references --
/fileset
/path
maven-build.xml after fix:
!-- ==
--
!-- Defining classpaths
--
!-- ==
--
path id=build.classpath
fileset dir=${maven.repo.local}
include name=javax/transaction/jta/1.0.1B/jta-1.0.1B.jar/
include name=javax/servlet/servlet-api/2.4/servlet-api-2.4.jar/
include name=commons-lang/commons-lang/2.1/commons-lang-2.1.jar/
!-- other libs --
/fileset
pathelement location=../Security/target/Security-1.0.0.21-SNAPSHOT.jar/
pathelement
location=../BusinessLogic/target/BusinessLogic-1.0.0.21-SNAPSHOT.jar/
!-- other module references --
/path
SVN diff in attachments.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
how to define a goal which wil depends on other goal in maven?
hi all, how can i define a goal which depends on other goal in my maven.xml in ant we can do it as follow like blabla ... target name=a depends =b blabla ... please let me know -- View this message in context: http://www.nabble.com/how-to-define-a-goal-which-wil-depends-on-other-goal-in-maven--tp15610275s177p15610275.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to define a goal which wil depends on other goal in maven?
Since you mention maven.xml I assume that you are using maven 1.x. In this case, the equivalent of ant's 'depends' is 'prereqs', see eg http://maven.apache.org/maven-1.x/reference/scripting.html#Declaring_Goals -Lukas san84 wrote: hi all, how can i define a goal which depends on other goal in my maven.xml in ant we can do it as follow like blabla ... target name=a depends =b blabla ... please let me know - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to define a goal which wil depends on other goal in maven?
Firstly, when someone replies in bottom posting style, ie with text beneath the original then do not reply with your text at the top. This makes the email very hard to read - and is just rude. I will put my reply at top here because it is now the least bad solution.. In maven, compiling always runs before jar. To be precise, the compile plugin (maven-compile-plugin) is attached to an earlier phase than the jar plugin (maven-jar-plugin). So there is nothing to do here; maven has this already set up. When you run maven, you just tell it what phase you want to run, eg mvn compile (runs all phases up to the compile phase) or mvn test (runs all phases up to the test phase) or mvn package (runs all phases up to the package phase) Please read the introduction to maven pages on the maven website. Regards, Simon san84 schrieb: consider , target name=jar depends=compile how can we achieve the same using maven. wil u please explain with examples plz [EMAIL PROTECTED] wrote: san84 schrieb: hi all, how can i define a goal which depends on other goal in my maven.xml in ant we can do it as follow like blabla ... target name=a depends =b blabla ... please let me know What is the actual problem you are trying to solve? In other words, what do a and b do, and why does b need to run first? Maven has this concept of phases that it runs through in order, with zero or more plugins attached to each phase. So to do something before some other thing, the plugins are bound to the appropriate phases. But the stuff which is set up by default covers almost all cases already... Regards, Simon - 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: how to define a goal which wil depends on other goal in maven?
Ah.. thanks for pointing that out Lukas. My other reply was about maven 2. Sorry about that. Maven 2 is **much** better than maven1. Do not use maven 1.x unless you absolutely have to. Regards, Simon Lukas Theussl schrieb: Since you mention maven.xml I assume that you are using maven 1.x. In this case, the equivalent of ant's 'depends' is 'prereqs', see eg http://maven.apache.org/maven-1.x/reference/scripting.html#Declaring_Goals -Lukas san84 wrote: hi all, how can i define a goal which depends on other goal in my maven.xml in ant we can do it as follow like blabla ... target name=a depends =b blabla ... please let me know - 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: Shared modules and versioning
No no - if module A and module C depend on module B (which is developed
by your company), how do you NOT put different versions in module A and
C?
We've done things like created a property in the pom that's the parent
(the top most) of all the projects and in the sub projects, they all
reference this property via the ${some.version.name} type convention.
But, shortly, all these modules will be in their own branch and the
concept of a parent pom (the one to rule them all) will go away and
we'll lose this ability.
What we've talked about doing is module A and module C will have the
property and all their sub projects will reference that property via the
${foo.property} convention as described above. THEN - we'll have a pom
that has dependencies on all these various modules poms (they'll have to
be installed in our internal repository) and we can run the dependency
convergence/dependency:analyze plugins.
-Original Message-
From: Michael McCallum [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 20, 2008 10:01 PM
To: Maven Users List
Subject: Re: Shared modules and versioning
i use standard refactoring techniques to avoid duplication and ensure
clean
dependency trees
On Thu, 21 Feb 2008 14:56:19 EJ Ciramella wrote:
Hmmm - that seems like a lot of work/duplication. Why not set it in
some higher level pom as a property and then use ${} type syntax to
expand it at your lower poms? What if someone doesn't
fix/change/update
one of the poms version entries?
-Original Message-
From: Michael McCallum [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 20, 2008 7:29 PM
To: Maven Users List
Subject: Re: Shared modules and versioning
all the poms... although I would not recommend using version ranges
for
external libraries that you have no control over
i've worked around that by using dependency compositions
On Thu, 21 Feb 2008 12:03:53 EJ Ciramella wrote:
How do you implement version ranges? I think that could get us a
bit
further along, but still - where do you store this range of
versions?
Which pom?
-Original Message-
From: Michael McCallum [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 20, 2008 5:19 PM
To: Maven Users List
Subject: Re: Shared modules and versioning
by a process of review by the person responsible...
however you could use version ranges and have a project that depends
on
all
your deployable units. With appropriate version ranges you will get
overcontrained version exceptions when someone has made the
deployables
inconsistent.
On Thu, 21 Feb 2008 08:11:35 EJ Ciramella wrote:
So we have a module that is shared across multiple deployable
units.
It's imperative that each deployable unit uses the SAME version of
this
dependency.
If these deployable units are in their OWN project structure, how
do
you
uniformly enforce they use the same version without letting each
deployable unit have it's very own dependency listing. We've
tried
making the version a property in our current parent project, but
this
doesn't feel like it's the correct place to put them (we're slowly
becoming more and more modular - and realizing there's no true
parent
to
all projects).
How have people solved this in scenario?
--
Michael McCallum
Enterprise Engineer
mailto:[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: maven appends sub-project artifactId to urls - Please help
I agree, it is a bit too late to change this behaviour now. Maybe some
other suffix like $ or ${fixed} or you-name-it could be the cure. Then
all existing builds would continue to work and if someone would not want
the artifact id appended, they can add the special character.
Stefan
Brian E. Fox wrote:
The discussion in the issue revolves around the fact that changing this
behavior to as documented will break every build where there isn't a /
at the end. It's not apparent how to fix this without hosing tons of
unsuspecting users.
--Brian
-Original Message-
From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 21, 2008 6:03 AM
To: Maven Users List
Subject: Re: maven appends sub-project artifactId to urls - Please help
I added a comment to http://jira.codehaus.org/browse/MNG-3244.
You may want to add you votes. Apparently, it was originally planned to
not append the artifact id unless the URL would end with a /.
Stefan
Ben Lidgey wrote:
-Original Message-
From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED]
Sent: 21 February 2008 09:52
To: Maven Users List
Subject: Re: maven appends sub-project artifactId to urls -
Please help
Hi Jens,
you are complaining about an essential feature of maven.
Having maven automatically extend the urls, scm urls, site
urls etc. with the list of parent artifact ids is crucial for
multi-module projects. No-one would want to enter this
information again and again through several levels of child
modules which are hosted within a common directory tree. I
agree that the docs are not clear about it, at least I
couldn't find it documented. I see your point, and there are
other problems, like when the directory name of a sub-module
is not equal to the artifact id, but in general it is an
important feature.
How to disable - I don't know. Maybe you will need to file
two things in
JIRA: a documentation request and a feature request to disable it.
HTH,
Stefan
We have a similar problem to Jens as our projects are structured in
Eclipse friendly structure, e.g.
ParentProject
- pom.xml
ChildProject1
- pom.xml
- src/java etc
ChildProject2
- pom.xml
- src/java etc
Which is different to the standard Maven dir structure, e.g.
ParentProject
- pom.xml
- ChildProject1
- pom.xml
- src/java etc
- ChildProject2
- pom.xml
- src/java etc
It would make sense to me to be able to specify a different naming
strategy, perhaps the Maven one is used as a default, but you could
define a different naming strategy and set that to be used instead, e.g.
scm namingStrategy=org.apache.maven.scm.FlatTreeNamingStrategy
...
/scm
That doesn't append artifactIds. Then if people had other weird and
whacky ways of structuring projects they could write custom naming
strategies to behave in accordance with their structures.
Ben
This e-mail is confidential and intended solely for the use of the
individual(s) to whom it is addressed. Any views or opinions expressed
are those of the author. If you are not the intended recipient, please
be advised that any use, dissemination, printing or copying of this
email is strictly prohibited.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to define a goal which wil depends on other goal in maven?
thank u but how can i do using maven 2? plz let me know with ex [EMAIL PROTECTED] wrote: san84 schrieb: hi all, how can i define a goal which depends on other goal in my maven.xml in ant we can do it as follow like blabla ... target name=a depends =b blabla ... please let me know What is the actual problem you are trying to solve? In other words, what do a and b do, and why does b need to run first? Maven has this concept of phases that it runs through in order, with zero or more plugins attached to each phase. So to do something before some other thing, the plugins are bound to the appropriate phases. But the stuff which is set up by default covers almost all cases already... Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/how-to-define-a-goal-which-wil-depends-on-other-goal-in-maven--tp15610275s177p15612428.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
surefire 2.4.2 fixes manifest issue (was Re: [ANN] Maven Surefire Plugin 2.4.1 for Maven 2 Released)
On Feb 7 at 6:01pm, DF=Dan Fabulich [EMAIL PROTECTED] wrote: DF [..snip..] DF DF Ah, hearing that makes me strongly suspect that this is SUREFIRE-445 and DF SUREFIRE-451. DF DF http://jira.codehaus.org/browse/SUREFIRE-445 DF http://jira.codehaus.org/browse/SUREFIRE-451 DF DF Thanks for doing this research; I've moved these bugs into the upcoming DF 2.4.2 release. DF DF -Dan DF Hi Dan, I can report that my earlier reported problems with jdk 1.6 and surefire 2.4.1 and errors with the manifest have now been fixed with surefire 2.4.2. Running under cruisecontrol with surefire 2.4.2 and the jdk 1.6, I no longer get the manifest related errors. Regards, -- Haroon Rafique [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: dependencyManagement and conflicts
You can't use the depMgt in this way. You will have to just specify the version in your poms that you prefer instead of the range. The normal way to use depMgt is to specify your version at the top of your project and then leave out the version in all the child poms...then you can switch them all together from one place. The analyze-dep-mgt will really only be usefull in maven 2.0.5 because of the change to depMgt overriding transitive dependencies. -Original Message- From: Benoit Decherf [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 20, 2008 2:31 PM To: Maven Users List Subject: Re: dependencyManagement and conflicts I'm not sure to use the dependencyManagement in the correct way: I put range in dependencies so that others components that are using it can detect conflict on versions. And I want to use dependencyManagement to fix the version that should be used, as you said to set the preferred version. What the correct way to do it ? The second question is on the use of the dependency:analyze-dep-mgt. Can I use it to detect a conflict ? How can I use the failBuild option ? Benoit Brian E. Fox wrote: DependencyManagment is only used for direct dependencies when you don't specify a version. Think of it as a preference. If you do specify one, then depMgt doesn't come into play. -Original Message- From: Benoit Decherf [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 20, 2008 11:12 AM To: Maven Users List Subject: Re: dependencyManagement and conflicts I still don't understand the useage of dependencyManagement : * A declare a dependency on log4j [1.2.0,1.3.0) and a dependencyManagement to force on version 1.2.4 mvn dependency:resolve show that log4j 1.2.14 is resolved. * B declare a dependency on A and a dependencyManagement to force on version 1.2.4 mvn dependency:resolve show that log4j 1.2.4 So dependencyManagement surcharge the dependencies declared in the transitive dependencies but not the direct dependencies. Is it right ? So, I'd like to know when this type of conflict occurs: mvn dependency:analyze-dep-mgt -DfailBuild=true -DignoreDirect=false -X [DEBUG] (s) failBuild = false [DEBUG] (s) ignoreDirect = true [DEBUG] (s) project = MavenProject: test:A:1.0-SNAPSHOT @ /home/decherfb/tmp/depMgmt/A/pom.xml [DEBUG] -- end configuration -- [INFO] [dependency:analyze-dep-mgt] [INFO] Found Resolved Dependency / DependencyManagement mismatches: [INFO] Ignoring Direct Dependencies. [INFO] Dependency: log4j:log4j:jar [INFO] DepMgt : 1.2.4 [INFO] Resolved: 1.2.14 [INFO]None [INFO] [INFO] BUILD SUCCESSFUL Why doesn't it fail ? What is the correct way to use this plugin ? I want to include this check to the release:prepare configuration. Benoit Brian E. Fox wrote: Yes. I think it was mng-1577 that made this intentional change. The dependencyManagement overrides the transitive versions. Dependency:analyze-dep-mgt can help you detect these conflicts later. -Original Message- From: Benoit Decherf [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 12, 2008 11:21 AM To: Maven Users List Subject: dependencyManagement and conflicts Hi, I have 3 projects with their dependencies: * A |- B[1.0] |- C [1.1] * B |- C [1.0] * C So here there is a conflict in A for C, and this is what I'm expected: [INFO] Failed to resolve artifact. The artifact has no valid ranges test:C:jar:1.0 Path to dependency: 1) test:A:jar:1.0 2) test:B:jar:1.0 But now, if I define in A a dependencyManagement, I can force the verson of C and I don't have any warning about the conflict. Is this normal? Benoit - 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]
Maven exec:java ClassNotFoundException
Hello,
I am using maven for a multi module project. The project consists of three
modules (each having its own directory):
hmiCore
eBioFlowCore
eBioFlowLauncher
I have a central pom.xml and which contains the build settings, and the
modules (corresponding to the directories mentioned above). Each module has
his own pom.xml file, containing module specific dependencies. This pom.xml
file are childs (inheritance) from the central pom.xml file to copy the
central settings. The eBioFlowLauncher contains a main class
(nl.utwente.ewi.hmi.ebioflow.launcher.EBioFlowLauncher).
The project compiles well and packages well (using maven package from
command line). All modules are compiled into their target/classes directory
and also the jar files are created.
However, when I perform a mvn exec:java, I get a classNotFoundException. The
main pom file is:
--- Pom.xml --
?xml version=1.0 encoding=UTF-8?
project
modelVersion4.0.0/modelVersion
groupIdnl.utwente.ewi.hmi.ebioflow/groupId
artifactIdeBioFlow/artifactId
packagingpom/packaging
nameeBioFlow/name
version1.0/version
urlhttp://maven.apache.org/url
build
directory${project.basedir}/target/directory
outputDirectory
${project.basedir}/target/${pom.artifactId}/classes
/outputDirectory
finalName
${pom.groupId}.${pom.artifactId}-${pom.version}
/finalName
plugins
plugin
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
/plugin
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
descriptors
descriptor
src/main/descriptors/assembly.xml
/descriptor
/descriptors
archive
manifest
mainClass
nl.utwente.ewi.hmi.ebioflow.launcher.EBioFlowLauncher
/mainClass
/manifest
/archive
executions
execution
idmake-assembly/id
phasepackage/phase
goals
goalattached/goal
/goals
/execution
/executions
/configuration
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
executions
execution
goals
goaljava/goal
/goals
/execution
/executions
configuration
mainClass
nl.utwente.ewi.hmi.ebioflow.launcher.EBioFlowLauncher
/mainClass
executableDependency
groupIdnl.utwente.ewi.hmi.ebioflow/groupId
artifactIdEBioFlowLauncher/artifactId
/executableDependency
dependencies
dependency
groupIdnet.sf.jpf/groupId
artifactIdjpf-boot/artifactId
version1.5/version
Re: How to override POM properties from CLI
This seems to work ok for me. I tried it locally and my profile properties override my pom properties, and cli props defined with -D override both pom and profile properties. I tried with maven 2.0.6 and 2.0.8. Can you attach a small zipped project to a jira issue that reproduces the problem? Igor Romanov wrote: Thank you for reply. Are you saying that properties specified in POM can not be overridden with -D option? Igor Wayne Fay wrote: You should put the properties in different profiles, and then specify which profile using -Penv1 when running Maven. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Doxia XDOC issue?
Switching out with amp; took care of it. I knew I just needed someone else's perspective. Darn trees get in the way of my view of the forest. :) Thanks Simon! On Thu, Feb 21, 2008 at 10:30 AM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Mykel Alvis schrieb: I seem to have a problem with generating site information with xdoc. I haven't done an enormous amount of this lately, so can someone tell me what's wrong with this subsection subsection name=JBoss 4.2.1 p ol liNeed to replace ttjboss-remoting.jar/tt. See a href=http://www.jboss.com/index.html?module=bbop=viewtopicp=4063410#4063410;here/a for details/li Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: entity reference name can not contain character =' (position: TEXT seen ...a href=http://www.jboss.com/index.html?module=bbop=... @11:115) at org.codehaus.plexus.util.xml.pull.MXParser.parseEntityRef(MXParser.java:2219) at org.codehaus.plexus.util.xml.pull.MXParser.parseAttribute(MXParser.java:2044) It appears that it's illegal to have a query inside an anchor in an Xdoc. Is that true? Is there some other way to do this? Switching to apt isn't an option. This is xml. And ampersand characters are not allowed in xml; they are interpreted as an entity reference, eg apos;. This is exactly what the xml parser is complaining about here. It's an xml issue, not an xdoc one. Replace the characters with amp; and everything should be ok, eg instead of op= write amp;op= It might also be possible to surround the problem block with CDATA, like: ![CDATA[ some text other stuff ]] Not sure whether that will be accepted here though.. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Is it possible to make some delaying between surefire plugin executions?
Hello experts Could you please give me the answer on few questions: 1. Is it possible to add some delaying between few execution phases of surefire plugin, e.g 10 seconds (hsqldb says: .lck file is locked by another process)? 2. Is it possible to run my surefire executions in the same JVM across all executions?. This is the snip of pom.xml: plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId configuration skiptrue/skip /configuration executions execution idexecution1/id phasetest/phase goals goaltest/goal /goals configuration skipfalse/skip forkModenever/forkMode includes include**/usecases/Test1.java/include /includes /configuration /execution execution idexecution2/id phasetest/phase goals goaltest/goal /goals configuration skipfalse/skip forkModenever/forkMode includes include**/usecases/Test2.java/include /includes /configuration /execution /executions /plugin Thanks -- View this message in context: http://www.nabble.com/Is-it-possible-to-make-some-delaying-between-surefire-plugin-executions--tp15613830s177p15613830.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Doxia XDOC issue?
I seem to have a problem with generating site information with xdoc. I haven't done an enormous amount of this lately, so can someone tell me what's wrong with this subsection subsection name=JBoss 4.2.1 p ol liNeed to replace ttjboss-remoting.jar/tt. See a href=http://www.jboss.com/index.html?module=bbop=viewtopicp=4063410#4063410;here/a for details/li liNeed to eliminate bundled Hibernate:br/ ol litthibernate3.jar/tt/li litthibernate-annotations.jar/tt/li litthibernate-entitymanager.jar/tt/li litthibernate3.jar/tt/li littejb3-persistence.jar/tt/li /ol /li /ol /p /subsection When I have this subsection in install.xml, I get the following error on transformation: [ERROR] Error parsing /home/mykel/work/jj/JJ/src/site/xdoc/install.xml: line [-1] Error parsing the model. org.apache.maven.doxia.parser.ParseException: Error parsing the model. at org.apache.maven.doxia.module.xdoc.XdocParser.parse(XdocParser.java:55) at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:52) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:264) at org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:43) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:239) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:115) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:124) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) 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(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: entity reference name can not contain character =' (position: TEXT seen ...a href=http://www.jboss.com/index.html?module=bbop=... @11:115) at org.codehaus.plexus.util.xml.pull.MXParser.parseEntityRef(MXParser.java:2219) at org.codehaus.plexus.util.xml.pull.MXParser.parseAttribute(MXParser.java:2044) at org.codehaus.plexus.util.xml.pull.MXParser.parseStartTag(MXParser.java:1796) at org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1124) at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1090) at org.apache.maven.doxia.module.xdoc.XdocParser.parseXdoc(XdocParser.java:312) at org.apache.maven.doxia.module.xdoc.XdocParser.parse(XdocParser.java:51) ... 25 more [ It appears that it's illegal to have a query inside an anchor in an Xdoc. Is that true? Is there some other way to do this? Switching to
Connecting to an internal Maven Repository using Vista
I am not able to connect to my internal Maven Repository using Vista...does anyone have any ideas on how to solve this? Thank you. This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
running a single integration test during integration-test-phase
Hello, Is there a way to configure a POM to run a single test during the integration-test-phase via command line? ie, mvn verify -Dtest=MyIntegrationTest That way I can do the necessary build work in pre-integration-test to prepare to run the integration-test phase. Thanks, David
Re: Connecting to an internal Maven Repository using Vista
You're not the first and I'm sure you won't be the last person to have problems with Vista (just check the archives). Try disabling your firewall, antivirus etc and see if it helps. As I've said previously, I don't run Vista (on purpose), so I'm not much help with these issues. Wayne On 2/21/08, Morgovsky, Alexander (US - Glen Mills) [EMAIL PROTECTED] wrote: I am not able to connect to my internal Maven Repository using Vista...does anyone have any ideas on how to solve this? Thank you. This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Shared modules and versioning
for A and C i have...
dependencies
dependency
artifactIdB/artifactId
groupIdmy.company/groupId
version[1,2-!)/version
/dependency
/depedencies
if I release B such that I create an incompatible release then release B as
2.X
we don't use modules, or pom inheritance for dependency management...
and it works very well...
On Fri, 22 Feb 2008 02:38:30 EJ Ciramella wrote:
No no - if module A and module C depend on module B (which is developed
by your company), how do you NOT put different versions in module A and
C?
We've done things like created a property in the pom that's the parent
(the top most) of all the projects and in the sub projects, they all
reference this property via the ${some.version.name} type convention.
But, shortly, all these modules will be in their own branch and the
concept of a parent pom (the one to rule them all) will go away and
we'll lose this ability.
What we've talked about doing is module A and module C will have the
property and all their sub projects will reference that property via the
${foo.property} convention as described above. THEN - we'll have a pom
that has dependencies on all these various modules poms (they'll have to
be installed in our internal repository) and we can run the dependency
convergence/dependency:analyze plugins.
-Original Message-
From: Michael McCallum [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 20, 2008 10:01 PM
To: Maven Users List
Subject: Re: Shared modules and versioning
i use standard refactoring techniques to avoid duplication and ensure
clean
dependency trees
On Thu, 21 Feb 2008 14:56:19 EJ Ciramella wrote:
Hmmm - that seems like a lot of work/duplication. Why not set it in
some higher level pom as a property and then use ${} type syntax to
expand it at your lower poms? What if someone doesn't
fix/change/update
one of the poms version entries?
-Original Message-
From: Michael McCallum [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 20, 2008 7:29 PM
To: Maven Users List
Subject: Re: Shared modules and versioning
all the poms... although I would not recommend using version ranges
for
external libraries that you have no control over
i've worked around that by using dependency compositions
On Thu, 21 Feb 2008 12:03:53 EJ Ciramella wrote:
How do you implement version ranges? I think that could get us a
bit
further along, but still - where do you store this range of
versions?
Which pom?
-Original Message-
From: Michael McCallum [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 20, 2008 5:19 PM
To: Maven Users List
Subject: Re: Shared modules and versioning
by a process of review by the person responsible...
however you could use version ranges and have a project that depends
on
all
your deployable units. With appropriate version ranges you will get
overcontrained version exceptions when someone has made the
deployables
inconsistent.
On Thu, 21 Feb 2008 08:11:35 EJ Ciramella wrote:
So we have a module that is shared across multiple deployable
units.
It's imperative that each deployable unit uses the SAME version of
this
dependency.
If these deployable units are in their OWN project structure, how
do
you
uniformly enforce they use the same version without letting each
deployable unit have it's very own dependency listing. We've
tried
making the version a property in our current parent project, but
this
doesn't feel like it's the correct place to put them (we're slowly
becoming more and more modular - and realizing there's no true
parent
to
all projects).
How have people solved this in scenario?
--
Michael McCallum
Enterprise Engineer
mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven appends sub-project artifactId to urls - Please help - design suggestion
As I understand it; the current rule implements implicit URLs as
${parent.url}/${project.artifactId}
For example:
scm
connection${parentPOM.scm.connection}/${project.artifactId}/connection
...
/scm
Where parentPOM is a made-up symbol denoting an upward search for the
pom property that follows (scm.connection).
So, how about the following suggestion:
The Super POM contains this kind of definition for all URLs where this
rule applies today. When the effective POM
is computed for a sub-project it uses the closest url definition that
contains the symbol parentPOM. If none is
found expect the def in super pom, this one is used and the rule applies
as it always has.
On the other hand, if one decides to put an url expression containing
parentPOM into a POM of type 'pom',
then there is a new definition and will be used. That means, we have a
way to define how sub-project urls should
be constructed. I would be delighted if I could define an expression as
${parentPOM.scm.connection}/${project.name}/trunk
There is a residual problem, however: I cannot define both an url
expansion expression and an actual url expression
that is intended to be used in sub-projects. The easiest solution, is
just to have two organization poms, the top-most
pom contains the url expansion expressions (overriding the rule from the
super pom) and the one beneath is the
original org pom, containing actual urls that will be used in the
expansions further down.
I'm convinced there are other more elegant solutions. However, the
suggestion above would be fairly easy to implement
without breaking existing code and poms (or require a POM version
increment), but still provide a way for org-pom
designers to tweak the url expansions the way they want.
Comments / Objections ???
Cheers,
Jens
VUB Stefan Seidel skrev:
I agree, it is a bit too late to change this behaviour now. Maybe some
other suffix like $ or ${fixed} or you-name-it could be the cure. Then
all existing builds would continue to work and if someone would not
want the artifact id appended, they can add the special character.
Stefan
Brian E. Fox wrote:
The discussion in the issue revolves around the fact that changing this
behavior to as documented will break every build where there isn't a /
at the end. It's not apparent how to fix this without hosing tons of
unsuspecting users.
--Brian
-Original Message-
From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] Sent: Thursday,
February 21, 2008 6:03 AM
To: Maven Users List
Subject: Re: maven appends sub-project artifactId to urls - Please help
I added a comment to http://jira.codehaus.org/browse/MNG-3244.
You may want to add you votes. Apparently, it was originally planned
to not append the artifact id unless the URL would end with a /.
Stefan
Ben Lidgey wrote:
-Original Message-
From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED]
Sent: 21 February 2008 09:52
To: Maven Users List
Subject: Re: maven appends sub-project artifactId to urls -
Please help
Hi Jens,
you are complaining about an essential feature of maven.
Having maven automatically extend the urls, scm urls, site
urls etc. with the list of parent artifact ids is crucial for
multi-module projects. No-one would want to enter this
information again and again through several levels of child
modules which are hosted within a common directory tree. I
agree that the docs are not clear about it, at least I
couldn't find it documented. I see your point, and there are
other problems, like when the directory name of a sub-module
is not equal to the artifact id, but in general it is an
important feature.
How to disable - I don't know. Maybe you will need to file
two things in
JIRA: a documentation request and a feature request to disable it.
HTH,
Stefan
We have a similar problem to Jens as our projects are structured in
Eclipse friendly structure, e.g.
ParentProject
- pom.xml
ChildProject1
- pom.xml
- src/java etc
ChildProject2
- pom.xml
- src/java etc
Which is different to the standard Maven dir structure, e.g.
ParentProject
- pom.xml
- ChildProject1
- pom.xml
- src/java etc
- ChildProject2
- pom.xml
- src/java etc
It would make sense to me to be able to specify a different naming
strategy, perhaps the Maven one is used as a default, but you could
define a different naming strategy and set that to be used instead, e.g.
scm namingStrategy=org.apache.maven.scm.FlatTreeNamingStrategy
...
/scm
That doesn't append artifactIds. Then if people had other weird and
whacky ways of structuring projects they could write custom naming
strategies to behave in accordance with their structures.
Ben
This e-mail is confidential and intended solely for the use of the
individual(s) to whom it is addressed. Any views or opinions expressed
are those of the author. If you are not the intended recipient, please
be advised that any use, dissemination, printing or copying of this
email is strictly prohibited.
assembly plugin and project inheritance
Hello I'm having many projects that share some dependencies and that should be packaged the same way. So I wanted to have a parent project configuring the maven-assembly-plugin. I did this with the following in the parent pom: plugin artifactIdmaven-assembly-plugin/artifactId configuration descriptors descriptor../rwcf-apps/src/assembly/dist.xml/descriptor /descriptors /configuration This only works when the parent is checked out in a sibling directory of the child. If one just check out a child project without checking out the parent assembly:assembly wont work. Things work using a descriptorRef but the predefined descriptors don't do what I'm looking for. Possibly ways to solve the issues might be: * have the plugin look up the descriptor from the parent rather * reference a descriptor with an http uri * include the content of descriptor directly in the pom ...but I didn't find a way to do it in any of these ways. Any suggestion on how to make it possible to check out a single child-project and being able to assemble it? If you would like to know more precisely what I'm doing, you may look at * The descriptor: https://knobot.svn.sourceforge.net/svnroot/knobot/rwcf-apps/trunk/src/assembly/dist.xml * The parent pom: https://knobot.svn.sourceforge.net/svnroot/knobot/rwcf-apps/trunk/pom.xml * A child pom: https://knobot.svn.sourceforge.net/svnroot/knobot/rwcf-app-webdav/trunk/pom.xml Cheers, reto signature.asc Description: OpenPGP digital signature
Re: maven-eclipse-plugin writes to src/main/webapp
I prefer to have a new issue and a link between them. You can wait to have it fixed OR you can propose a patch (code+test+doc) to be sure it will be. Arnaud On Thu, Feb 21, 2008 at 10:24 AM, Martin Höller [EMAIL PROTECTED] wrote: On Thursday 21 February 2008 wrote Arnaud HERITIER: I think we have several problems with manifest in 2.5-SNAPSHOT :-( wtpmanifest = true creates several problems. We noticed this one : http://jira.codehaus.org/browse/MECLIPSE-389 It can be (or not) related It is (at least somehow) related. Should I file an extra issue for this one or just add a comment to MECLIPSE-389 and wait till it's eventually fixed? thanks, - martin -- Martin Höller | [EMAIL PROTECTED] *x Software + Systeme | http://www.xss.co.at/ Karmarschgasse 51/2/20 | Tel: +43-1-6060114-30 A-1100 Vienna, Austria | Fax: +43-1-6060114-71 -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ...
Migrating from Maven 1 to Maven 2
Hi, I am currently migrating a big legacy project from Maven 1.02 to Maven 2.08. The project has lots of dependencies, many of which are not even used anymore, which are just transitive dependencies, or are just outdated. Are there any tools, or best practices, that could help me in getting this tedious job done? Thanks in advance, Stefanie -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Migrating from Maven 1 to Maven 2
What exactly are you looking for help with? Converting the project.xml into pom.xml? Analyzing your dependencies to see what is actually needed? Something else entirely? Wayne On 2/21/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, I am currently migrating a big legacy project from Maven 1.02 to Maven 2.08. The project has lots of dependencies, many of which are not even used anymore, which are just transitive dependencies, or are just outdated. Are there any tools, or best practices, that could help me in getting this tedious job done? Thanks in advance, Stefanie -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger - 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: Migrating from Maven 1 to Maven 2
[EMAIL PROTECTED] wrote: Hi, I am currently migrating a big legacy project from Maven 1.02 to Maven 2.08. The project has lots of dependencies, many of which are not even used anymore, which are just transitive dependencies, or are just outdated. Are there any tools, or best practices, that could help me in getting this tedious job done? The Maven One Plugin [1] can be used to convert your project.xml and project.properties files into pom.xml files. [1] http://maven.apache.org/plugins/maven-one-plugin/ Thanks in advance, Stefanie -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Surefire 2.4.1 classpath order
Ben Lidgey wrote: Made the tests pass. I've no idea why. Do you want me to raise this as a bug? Yes... nice work! That sounds like a Core bug and not a Surefire bug, so file it against Maven 2 (MNG) in JIRA. Thanks! -Dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is it possible to make some delaying between surefire plugin executions?
vetalok wrote: 1. Is it possible to add some delaying between few execution phases of surefire plugin, e.g 10 seconds (hsqldb says: .lck file is locked by another process)? Not really. Much easier to add a Thread.sleep() line to your tests. 2. Is it possible to run my surefire executions in the same JVM across all executions?. You've already set forkMode=never, which should do that by virtue of never spawning another JVM. Do you find it's not doing that? -Dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Assemblies and locations beyond the target directory
I've been looking at the assembly:directory-inline target here:
http://maven.apache.org/plugins/maven-assembly-plugin/directory-inline-m
ojo.html
outputDirectory
http://maven.apache.org/plugins/maven-assembly-plugin/directory-inline-
mojo.html#outputDirectory -- The output directory of the
assembled distribution file. Default value is
${project.build.directory}.
But no matter what I pass (or how) I do so on the commandline (via
-DoutputDirectory=C:\asdf), it chooses the target directory instead and
totally ignores my property.
Any other suggestions?
Re: Maven ignores my archetype selection
On Sunday 17 February 2008 10:31:01 Brian E. Fox wrote: I think the list is currently embedded, but you might be able to add it to ~home/.m2/archetype.xml, otherwise you'll need to back down to 1.0-alpha-7 (this issue is fixed in 2.0-alpha-2 once it gets released) I just had the problem yesterday, and got around it by adding -DarchetypeRepository=my local repo, and it picked it up from there Eric -Original Message- From: Tom Cook [mailto:[EMAIL PROTECTED] Sent: Saturday, February 16, 2008 5:13 PM To: Maven Users List Subject: Re: Maven ignores my archetype selection Ah, OK, I see. So how do I tell it that I want to use the trails archetype? It's not in the list it gives me. Do I need to download the archetype manually first? Thanks for the help. Tom On Feb 17, 2008 1:35 AM, Brian E. Fox [EMAIL PROTECTED] wrote: The new ones prompt you from the command line. Just pick the one you need from the prompts. -Original Message- From: Tom Cook [mailto:[EMAIL PROTECTED] Sent: Saturday, February 16, 2008 4:07 AM To: Maven Users List Subject: Re: Maven ignores my archetype selection Thanks for the quick answer. I don't particularly need old style commands, and didn't really realise there were 'old-style' and 'new-style' commands, I was just following the documentation - eg. Maven in 5 Minutes, http://maven.apache.org/guides/getting-started/maven-in-five-minutes.html from which the first command in my post was taken. So, given that I don't need old-style commands, what do new-style commands look like? Where can I find documentation on them? Regards, Tom On Sat, Feb 16, 2008 at 6:03 PM, Brian E. Fox [EMAIL PROTECTED] wrote: Use org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:createif you need the old style commands. The new version 2.0 has an issue with backwards compat and should be fixed shortly. -Original Message- From: Tom Cook [mailto:[EMAIL PROTECTED] Sent: Friday, February 15, 2008 9:42 PM To: users@maven.apache.org Subject: Maven ignores my archetype selection Hi all, I hate asking noob questions, but I have looked in the bug tracker, the FAQ, the list archive and the doco and can't see any mention of it, so here goes: I have downloaded maven 2.0.8 on my Ubuntu gutsy machine, unpacked it and moved it to /usr/local/apache-maven. I have set up my environment as follows: echo $M2 /usr/local/apache-maven/bin echo $M2_HOME /usr/local/apache-maven echo $JAVA_HOME /usr/lib/jvm/java-1.5.0-sun java -version java version 1.5.0_13 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05) Java HotSpot(TM) Client VM (build 1.5.0_13-b05, mixed mode, sharing) mvn -version /usr/lib/jvm/java-1.5.0-sun/bin/java -classpath /usr/local/apache-maven/boot/classworlds-1.1.jar - Dclassworlds.conf=/usr/local/apache-maven/bin/m2.conf - Dmaven.home=/usr/local/apache-maven org.codehaus.classworlds.Launcher -version Maven version: 2.0.8 Java version: 1.5.0_13 OS name: linux version: 2.6.22-14-generic arch: i386 Family: unix But when I try: mvn archetype:create -DgroupId=com.my-package -DartifactId=my-app [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] --- - [INFO] Building Maven Default Project [INFO]task-segment: [archetype:create] (aggregator-style) [INFO] --- - [INFO] Preparing archetype:create [INFO] No goals needed for project - skipping Downloading: http://repo1.maven.org/maven2/com/my-package/wagon-http-shared/1.0-beta-2 /wagon-http-shared-1.0-beta-2.pom Downloading: http://repo1.maven.org/maven2/com/my-package/wagon-http-shared/1.0-beta-2 /wagon-http-shared-1.0-beta-2.pom [INFO] Setting property: classpath.resource.loader.class = ' org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on = 'false'. [INFO] Setting property: resource.loader = 'classpath'. [INFO] Setting property: resource.manager.logwhenfound = 'false'. [INFO] [archetype:create] Choose archetype: 1: internal - appfuse-basic-jsf (AppFuse archetype for creating a web application with Hibernate, Spring and JSF) 2: internal - appfuse-basic-spring (AppFuse archetype for creating a web application with Hibernate, Spring and Spring MVC) 3: internal - appfuse-basic-struts (AppFuse archetype for creating a web application with Hibernate, Spring and Struts 2) 4: internal - appfuse-basic-tapestry (AppFuse archetype for creating a web application with Hibernate, Spring and Tapestry 4) 5: internal - appfuse-core (AppFuse
Re: Create one jar including all dependencies
did you see http://maven.apache.org/plugins/maven-assembly-plugin/index.html , the pre-defined descriptor jar-with-dependencies http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html#jar-with-dependencies - can be used for general assembly of a binary package with all the dependency libraries included unpacked inside the archive. Cheers, reto krishnan.1000 wrote: Hi, I am a Maven newbie. So please forgive my ignorance. I am using Maven 2x for project and dependency management. I am creating a jar package. My project requires that the jar be deployed on a remote server. I can create a jar of all the classes. I would like to create a mega jar with all the expanded dependent jars in the generated jars. Is there a command for this or do I have to create a customized goal for this? Thanks, Karthik signature.asc Description: OpenPGP digital signature
Re: Maven ignores my archetype selection
Tom, I already replied to your comment you left at http://docs.codehaus.org/display/TRAILS/Quick+Start with the same informatoin others have provided: use the older archetype. Kalle On Sat, Feb 16, 2008 at 2:13 PM, Tom Cook [EMAIL PROTECTED] wrote: Ah, OK, I see. So how do I tell it that I want to use the trails archetype? It's not in the list it gives me. Do I need to download the archetype manually first? Thanks for the help. Tom On Feb 17, 2008 1:35 AM, Brian E. Fox [EMAIL PROTECTED] wrote: The new ones prompt you from the command line. Just pick the one you need from the prompts. -Original Message- From: Tom Cook [mailto:[EMAIL PROTECTED] Sent: Saturday, February 16, 2008 4:07 AM To: Maven Users List Subject: Re: Maven ignores my archetype selection Thanks for the quick answer. I don't particularly need old style commands, and didn't really realise there were 'old-style' and 'new-style' commands, I was just following the documentation - eg. Maven in 5 Minutes, http://maven.apache.org/guides/getting-started/maven-in-five-minutes.html from which the first command in my post was taken. So, given that I don't need old-style commands, what do new-style commands look like? Where can I find documentation on them? Regards, Tom On Sat, Feb 16, 2008 at 6:03 PM, Brian E. Fox [EMAIL PROTECTED] wrote: Use org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:createif you need the old style commands. The new version 2.0 has an issue with backwards compat and should be fixed shortly. -Original Message- From: Tom Cook [mailto:[EMAIL PROTECTED] Sent: Friday, February 15, 2008 9:42 PM To: users@maven.apache.org Subject: Maven ignores my archetype selection Hi all, I hate asking noob questions, but I have looked in the bug tracker, the FAQ, the list archive and the doco and can't see any mention of it, so here goes: I have downloaded maven 2.0.8 on my Ubuntu gutsy machine, unpacked it and moved it to /usr/local/apache-maven. I have set up my environment as follows: echo $M2 /usr/local/apache-maven/bin echo $M2_HOME /usr/local/apache-maven echo $JAVA_HOME /usr/lib/jvm/java-1.5.0-sun java -version java version 1.5.0_13 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05) Java HotSpot(TM) Client VM (build 1.5.0_13-b05, mixed mode, sharing) mvn -version /usr/lib/jvm/java-1.5.0-sun/bin/java -classpath /usr/local/apache-maven/boot/classworlds-1.1.jar - Dclassworlds.conf=/usr/local/apache-maven/bin/m2.conf - Dmaven.home=/usr/local/apache-maven org.codehaus.classworlds.Launcher -version Maven version: 2.0.8 Java version: 1.5.0_13 OS name: linux version: 2.6.22-14-generic arch: i386 Family: unix But when I try: mvn archetype:create -DgroupId=com.my-package -DartifactId=my-app [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [archetype:create] (aggregator-style) [INFO] [INFO] Preparing archetype:create [INFO] No goals needed for project - skipping Downloading: http://repo1.maven.org/maven2/com/my-package/wagon-http-shared/1.0-beta-2/wagon-http-shared-1.0-beta-2.pom Downloading: http://repo1.maven.org/maven2/com/my-package/wagon-http-shared/1.0-beta-2/wagon-http-shared-1.0-beta-2.pom [INFO] Setting property: classpath.resource.loader.class = ' org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on = 'false'. [INFO] Setting property: resource.loader = 'classpath'. [INFO] Setting property: resource.manager.logwhenfound = 'false'. [INFO] [archetype:create] Choose archetype: 1: internal - appfuse-basic-jsf (AppFuse archetype for creating a web application with Hibernate, Spring and JSF) 2: internal - appfuse-basic-spring (AppFuse archetype for creating a web application with Hibernate, Spring and Spring MVC) 3: internal - appfuse-basic-struts (AppFuse archetype for creating a web application with Hibernate, Spring and Struts 2) 4: internal - appfuse-basic-tapestry (AppFuse archetype for creating a web application with Hibernate, Spring and Tapestry 4) 5: internal - appfuse-core (AppFuse archetype for creating a jar application with Hibernate and Spring and XFire) 6: internal - appfuse-modular-jsf (AppFuse archetype for creating a modular application with Hibernate, Spring and JSF) 7: internal - appfuse-modular-spring (AppFuse archetype for creating a modular application with Hibernate, Spring and Spring MVC) 8: internal -
RE: Assemblies and locations beyond the target directory
Ok, I have my head on straight now - but how can you get rid of the .dir
it attaches to the directory output of an assembly?
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 21, 2008 5:57 PM
To: users@maven.apache.org
Subject: Assemblies and locations beyond the target directory
I've been looking at the assembly:directory-inline target here:
http://maven.apache.org/plugins/maven-assembly-plugin/directory-inline-m
ojo.html
outputDirectory
http://maven.apache.org/plugins/maven-assembly-plugin/directory-inline-
mojo.html#outputDirectory -- The output directory of the
assembled distribution file. Default value is
${project.build.directory}.
But no matter what I pass (or how) I do so on the commandline (via
-DoutputDirectory=C:\asdf), it chooses the target directory instead and
totally ignores my property.
Any other suggestions?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Create one jar including all dependencies
At 2:51 PM -0800 2/21/08, krishnan.1000 wrote: Hi, I am a Maven newbie. So please forgive my ignorance. I am using Maven 2x for project and dependency management. I am creating a jar package. My project requires that the jar be deployed on a remote server. I can create a jar of all the classes. I would like to create a mega jar with all the expanded dependent jars in the generated jars. Is there a command for this or do I have to create a customized goal for this? we tend to use the dependency plugin to fetch the jars, and then just package up the result. you need a separate pom for each package (so you can list the dependencies). there are several example poms in the following directories with various levels of complexity in the final package requirements. listed from simplest to more complex: https://open-jbi-components.dev.java.net/source/browse/open-jbi-components/ojc-core/filebc/packaging https://open-jbi-components.dev.java.net/source/browse/open-jbi-components/packaging/ https://open-esb.dev.java.net/source/browse/open-esb/esb-packages/ If you need something even more complex, then the assembly plugin may be the way to go. -Russ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Trouble compiling jsps in embedded
Hello, I have a project with an embedded tomcat instance which is supposed to be compiling some JSPs. When I run a simple unit test that fetches our index page, I get a javac compiler error in our logs. (See below, complaining that package javax.servlet is missing). I have all the needed tomcat packages (especially servlet-api) as a dependency in the pom file, so it should be on the classpath, yet the compile doesn't see it. I'm wondering if the Java compiler doesn't disect the surefirebooter jar properly? Is there anyone who has run into this or has a solution? -Josh 2008-02-21 20:13:40,251 [http-8080-Processor4] ERROR apache.jasper.compiler.Compiler - Javac exception Compile failed; see the compiler error output for details. The compiler output looks like this: 008-02-21 20:13:40,252 [http-8080-Processor4] ERROR apache.jasper.compiler.Compiler - Env: Compile: javaFileName=/Users/ jpollak/src/software/projects/mhs/trunk/ mhs-core/work/mhsEngine/kiva/distrosite//org/apache/jsp/index_jsp.java classpath=/Users/jpollak/src/software/projects/mhs/trunk/mhs-core/ work/mhsEngine/kiva/distrosite:/private/tmp/surefirebooter4943.jar:/ System/Library/Java/Ext ensions/CoreAudio.jar:/System/Library/Java/Extensions/dns_sd.jar:/ System/Library/Java/Extensions/j3daudio.jar:/System/Library/Java/ Extensions/j3dcore.jar:/System /Library/Java/Extensions/j3dutils.jar:/System/Library/Java/Extensions/ jai_codec.jar:/System/Library/Java/Extensions/jai_core.jar:/System/ Library/Java/Extensions/ libJ3D.jnilib:/System/Library/Java/Extensions/libJ3DAudio.jnilib:/ System/Library/Java/Extensions/libJ3DUtils.jnilib:/System/Library/Java/ Extensions/libmlib_jai.j nilib:/System/Library/Java/Extensions/libQTJNative.jnilib:/System/ Library/Java/Extensions/libShark.jnilib:/System/Library/Java/ Extensions/mlibwrapper_jai.jar:/Sy stem/Library/Java/Extensions/MRJToolkit.jar:/System/Library/Java/ Extensions/QTJava.zip:/System/Library/Java/Extensions/vecmath.jar:/ System/Library/Frameworks/Jav aVM.framework/Versions/1.5.0/Home/lib/ext/apple_provider.jar:/System/ Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/ dnsns.jar:/System/Library/Fr ameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/localedata.jar:/ System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/ sunjce_provider.jar: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ ext/sunpkcs11.jar cp=/opt/maven/boot/classworlds-1.1.jar cp=/Users/jpollak/src/software/projects/mhs/trunk/mhs-core/work/ mhsEngine/kiva/distrosite cp=/private/tmp/surefirebooter4943.jar cp=/System/Library/Java/Extensions/CoreAudio.jar cp=/System/Library/Java/Extensions/dns_sd.jar cp=/System/Library/Java/Extensions/j3daudio.jar cp=/System/Library/Java/Extensions/j3dcore.jar cp=/System/Library/Java/Extensions/j3dutils.jar cp=/System/Library/Java/Extensions/jai_codec.jar cp=/System/Library/Java/Extensions/jai_core.jar cp=/System/Library/Java/Extensions/libJ3D.jnilib cp=/System/Library/Java/Extensions/libJ3DAudio.jnilib cp=/System/Library/Java/Extensions/libJ3DUtils.jnilib cp=/System/Library/Java/Extensions/libmlib_jai.jnilib cp=/System/Library/Java/Extensions/libQTJNative.jnilib cp=/System/Library/Java/Extensions/libShark.jnilib cp=/System/Library/Java/Extensions/mlibwrapper_jai.jar cp=/System/Library/Java/Extensions/MRJToolkit.jar cp=/System/Library/Java/Extensions/QTJava.zip cp=/System/Library/Java/Extensions/vecmath.jar cp=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext/apple_provider.jar cp=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext/dnsns.jar cp=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext/localedata.jar cp=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext/sunjce_provider.jar cp=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext/sunpkcs11.jar work dir=/Users/jpollak/src/software/projects/mhs/trunk/mhs-core/ work/mhsEngine/kiva/distrosite extension dir=/Library/Java/Extensions:/System/Library/Java/ Extensions:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext srcDir=/Users/jpollak/src/software/projects/mhs/trunk/mhs-core/ work/mhsEngine/kiva/distrosite compilerTargetVM=1.5 compilerSourceVM=1.5 include=org/apache/jsp/index_jsp.java 2008-02-21 20:13:40,253 [http-8080-Processor4] ERROR apache.jasper.compiler.Compiler - Error compiling file: /Users/jpollak/ src/software/projects/mhs/trunk/mhs-c ore/work/mhsEngine/kiva/distrosite//org/apache/jsp/index_jsp.java [javac] Compiling 1 source file /Users/jpollak/src/software/projects/mhs/trunk/mhs-core/work/mhsEngine/ kiva/distrosite/org/apache/jsp/index_jsp.java:3: package javax.servlet does not exist import javax.servlet.*; ^
Re: Trouble compiling jsps in embedded
You could try adding the servlet-api artifact as a dependency to surefire, that might do it. Could you perhaps compile the JSPs with jspc-maven-plugin instead of asking Tomcat to do it? I don't know that its an ideal solution, but we've been using j-m-p for a while very successfully. Wayne On 2/21/08, Joshua Pollak [EMAIL PROTECTED] wrote: Hello, I have a project with an embedded tomcat instance which is supposed to be compiling some JSPs. When I run a simple unit test that fetches our index page, I get a javac compiler error in our logs. (See below, complaining that package javax.servlet is missing). I have all the needed tomcat packages (especially servlet-api) as a dependency in the pom file, so it should be on the classpath, yet the compile doesn't see it. I'm wondering if the Java compiler doesn't disect the surefirebooter jar properly? Is there anyone who has run into this or has a solution? -Josh 2008-02-21 20:13:40,251 [http-8080-Processor4] ERROR apache.jasper.compiler.Compiler - Javac exception Compile failed; see the compiler error output for details. The compiler output looks like this: 008-02-21 20:13:40,252 [http-8080-Processor4] ERROR apache.jasper.compiler.Compiler - Env: Compile: javaFileName=/Users/ jpollak/src/software/projects/mhs/trunk/ mhs-core/work/mhsEngine/kiva/distrosite//org/apache/jsp/index_jsp.java classpath=/Users/jpollak/src/software/projects/mhs/trunk/mhs-core/ work/mhsEngine/kiva/distrosite:/private/tmp/surefirebooter4943.jar:/ System/Library/Java/Ext ensions/CoreAudio.jar:/System/Library/Java/Extensions/dns_sd.jar:/ System/Library/Java/Extensions/j3daudio.jar:/System/Library/Java/ Extensions/j3dcore.jar:/System /Library/Java/Extensions/j3dutils.jar:/System/Library/Java/Extensions/ jai_codec.jar:/System/Library/Java/Extensions/jai_core.jar:/System/ Library/Java/Extensions/ libJ3D.jnilib:/System/Library/Java/Extensions/libJ3DAudio.jnilib:/ System/Library/Java/Extensions/libJ3DUtils.jnilib:/System/Library/Java/ Extensions/libmlib_jai.j nilib:/System/Library/Java/Extensions/libQTJNative.jnilib:/System/ Library/Java/Extensions/libShark.jnilib:/System/Library/Java/ Extensions/mlibwrapper_jai.jar:/Sy stem/Library/Java/Extensions/MRJToolkit.jar:/System/Library/Java/ Extensions/QTJava.zip:/System/Library/Java/Extensions/vecmath.jar:/ System/Library/Frameworks/Jav aVM.framework/Versions/1.5.0/Home/lib/ext/apple_provider.jar:/System/ Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/ dnsns.jar:/System/Library/Fr ameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/localedata.jar:/ System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/ sunjce_provider.jar: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ ext/sunpkcs11.jar cp=/opt/maven/boot/classworlds-1.1.jar cp=/Users/jpollak/src/software/projects/mhs/trunk/mhs-core/work/ mhsEngine/kiva/distrosite cp=/private/tmp/surefirebooter4943.jar cp=/System/Library/Java/Extensions/CoreAudio.jar cp=/System/Library/Java/Extensions/dns_sd.jar cp=/System/Library/Java/Extensions/j3daudio.jar cp=/System/Library/Java/Extensions/j3dcore.jar cp=/System/Library/Java/Extensions/j3dutils.jar cp=/System/Library/Java/Extensions/jai_codec.jar cp=/System/Library/Java/Extensions/jai_core.jar cp=/System/Library/Java/Extensions/libJ3D.jnilib cp=/System/Library/Java/Extensions/libJ3DAudio.jnilib cp=/System/Library/Java/Extensions/libJ3DUtils.jnilib cp=/System/Library/Java/Extensions/libmlib_jai.jnilib cp=/System/Library/Java/Extensions/libQTJNative.jnilib cp=/System/Library/Java/Extensions/libShark.jnilib cp=/System/Library/Java/Extensions/mlibwrapper_jai.jar cp=/System/Library/Java/Extensions/MRJToolkit.jar cp=/System/Library/Java/Extensions/QTJava.zip cp=/System/Library/Java/Extensions/vecmath.jar cp=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext/apple_provider.jar cp=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext/dnsns.jar cp=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext/localedata.jar cp=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext/sunjce_provider.jar cp=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext/sunpkcs11.jar work dir=/Users/jpollak/src/software/projects/mhs/trunk/mhs-core/ work/mhsEngine/kiva/distrosite extension dir=/Library/Java/Extensions:/System/Library/Java/ Extensions:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/ext srcDir=/Users/jpollak/src/software/projects/mhs/trunk/mhs-core/ work/mhsEngine/kiva/distrosite compilerTargetVM=1.5 compilerSourceVM=1.5 include=org/apache/jsp/index_jsp.java 2008-02-21 20:13:40,253 [http-8080-Processor4] ERROR apache.jasper.compiler.Compiler - Error compiling file: /Users/jpollak/
Newbie: how to do a release?
I've got a standard Java app. I've got a pom that successfully generates a jar file, and I got it to generate some javadoc as well. Now how do I generate a standard release? In a normal app, the jar goes in a /lib folder along with all the dependencies, the javadoc in /doc/api, there's /bin folder with a startup script, and a license and readme in the root. The /target directory doesn't look at all like this. There are things there that don't belong in a released app at all, like all the separate .class files. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Newbie: how to do a release?
Hi, Check out the assembly plugin. It does just that. You have to write an assembly descriptor xml to customize the release the way you want it. http://maven.apache.org/plugins/maven-assembly-plugin/howto.html Here is a very simple assembly descriptor file which bundles all jar files to the a lib folder and copy a given run script to the root of the distribution. assembly idbin/id includeBaseDirectorytrue/includeBaseDirectory formats formatzip/format /formats fileSets fileSet directorysrc/main/bin/directory outputDirectory//outputDirectory includes includerun.sh/include /includes fileMode755/fileMode /fileSet /fileSets dependencySets dependencySet outputDirectorylib/outputDirectory /dependencySet /dependencySets /assembly Descriptor file can be given in the pom.xml directly like this without giving it in the command line. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId version2.1/version configuration descriptors descriptorsrc/main/assembly/bin.xml/descriptor /descriptors /configuration /plugin Hope this helps. Upul On Fri, Feb 22, 2008 at 9:26 AM, Chris [EMAIL PROTECTED] wrote: I've got a standard Java app. I've got a pom that successfully generates a jar file, and I got it to generate some javadoc as well. Now how do I generate a standard release? In a normal app, the jar goes in a /lib folder along with all the dependencies, the javadoc in /doc/api, there's /bin folder with a startup script, and a license and readme in the root. The /target directory doesn't look at all like this. There are things there that don't belong in a released app at all, like all the separate .class files. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PDE Plugin
With the help of people here especially Graham, I am able to build the plug
in successfully using pde-maven-plugin. The only thing left now is that I
want to package the lib folder along with the plugin, which I can do by
using copy-dependency but I am not able the lib entries to Manifest file
thus leaving the plug in handicapped at run time. The manifest entries tell
plug in to expect the dependencies in the root folder of plugin, while I
want to package it in lib folder(the tidier option).
Could someone please help on that?
Regards,
Amit Kumar
On Wed, Feb 20, 2008 at 3:14 PM, amit kumar [EMAIL PROTECTED]
wrote:
Thanks Dan, but these files are already in eclipse and I just need to copy
them to the final zipped file.(The outcome of pde-maven-plugin).
Thanks for the kind help. Would look into it.
Regards,
Amit
On Feb 20, 2008 2:55 PM, Dan Tran [EMAIL PROTECTED] wrote:
again pde plugin knows nothing about maven pom's resource, you will
need some help from antrun plugin to copy those files to
a place eclipse can pickup.
About the source, you will need to lookup how eclipse's ant build
their stuff, there must by a property
you can passing into ant build via pde plugin
On Feb 20, 2008 1:16 AM, amit kumar [EMAIL PROTECTED] wrote:
Hi Dan,
Thanks for valuable pointers , now its able to compile the source
using
dependencies from both Plugin Dependencies part and pom.xml. Still
there are
few doubts and issues
1) pde-plugin is also zipping the source in the zip file that it
packages
out of the project. Is there a way to avoid this?
2) Resources folders seems to be not working when pde-maven-plugin is
being
used, I tried packaging plugin.properties and message.properties(two
of the
required files). But I can't see them in the final zipped file.
I tried
resources
resource
directory${basedir}/resources/directory
targetPath//targetPath
/resource
/resources
and as well as
resources
resource
directory${basedir}/directory
includes
includeplugin.properties/include
includemessage.properties.properties/include
/includes
excludes
exclude**/*.java/exclude
/excludes
targetPath//targetPath
/resource
/resources
But both seems to be not working.
3) Is it possible to bundle the pom.xml dependencies along with the
zipped
file as well?
It is a requirement that the pom.xml dependency jar files must be
bundled
with the plugin(zip/jar) inside a lib folder or something of that
sort.
Thanks and Regards,
Amit
On Feb 19, 2008 4:29 PM, Dan Tran [EMAIL PROTECTED] wrote:
The question here is how do you want pde plugin to consume your
pom's
dependencies thru a way that eclipse can understand?
I maven-dependency-plugin to copy my dependencies to a place that
eclispe's pde can pick up.
-D
On Feb 19, 2008 2:42 AM, amit kumar [EMAIL PROTECTED]
wrote:
Oh Ok. But how to inform pde-maven-plugin about the declared
dependencies? I
mean is there any configuration that I am missing?
Thanks and regards,
Amit
On Feb 19, 2008 3:57 PM, Dan Tran [EMAIL PROTECTED] wrote:
pde-maven-plugin does not know about your declared dependencies
in
pom.xml. Every thing must still going thru the eclipse way.
-D
On Feb 19, 2008 12:50 AM, amit kumar [EMAIL PROTECTED]
wrote:
Hi!
I am trying to use maven-pde-plugin but without any success.
When I do mvn install to a plug in project, maven-pde-plugin
is not
able
to
resolve the pom.xml's dependencies.
I am unable to locate any relevant document over net.
Could someone please help me? It has been continuously 2nd day
when
I am
stuck with it.
The build.xml that maven-pde-plugin is generating doesn't have
the
pom.xml's
dependenies in the classpath items. It has only the Plugin
dependenies.
Is there any workaround for the same?
As linked to by Dan I tried
http://mojo.codehaus.org/pde-maven-plugin/examples/m2eclipse.htmlthis
as
well. Any plugin with only plugin dependencies is working
fine, but
as
soon
as I describe dependencies in pom.xml compilation errors start
coming
owing
to the non availability of the dependencies in the jar file.
Many thanks in anticipation.
Regards,
On Feb 13, 2008 2:48 PM, Dan Tran [EMAIL PROTECTED] wrote:
IT = integration test
try this
http://mojo.codehaus.org/pde-maven-plugin/examples/m2eclipse.html
On Feb 13, 2008 12:54 AM, amit kumar
Re: Problem with maven-dependency-plugin: copy-dependencies
Can I modify Manifest entries along with the copy-dependencies goal in configuration? Or something like that. I want the Manifest.mf to have entries for the copied dependencies(in the specific folder). Regards, Amit Kumar On Wed, Jan 2, 2008 at 2:18 PM, PatrickV [EMAIL PROTECTED] wrote: The attachments are there. My first posting did indeed not include the attachements, I edited the posting and now the file (pp.zip) is there. Brian E Fox wrote: The attachments didn't come through. Try writing a jira at http://jira.codehaus.org/browse/MDEP and attach the files there. -Original Message- From: PatrickV [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 01, 2008 11:08 AM To: users@maven.apache.org Subject: RE: Problem with maven-dependency-plugin: copy-dependencies I hope I can make it clear by attaching the pom's to this message. The poms are stripped versions of the real stuff. Module A = pp-common.xml Module B = pp-client.xml Module C = pp-server.xml The copy dependencies plugin is stated in pp-server.xml. pp-server depends on pp-common and pp-client. I expect to see after running the copy-dependency goal to target directory: pp-common.jar in target directory pp-client.jar in target directory all dependencies from pp-server all dependencies from pp-common not yet included in target directory all dependencies from pp-client not yet included in target directory What I do see in target directory all dependencies from pp-server all dependencies from pp-common all dependencies from pp-client BUT NOT... pp-common.jar and pp-client.jar, allthough they too ARE listed in the dependencies of the pp-server project. Packaging of pp-server (war or jar) has no influence on result. The process is triggered by executing mvn -U clean package on parent. I hope the issue is clear now. KR PatrickV Brian E Fox wrote: -Original Mes http://www.nabble.com/file/p14567676/pp.zip pp.zip sage- From: PatrickV [mailto:[EMAIL PROTECTED] Sent: Sunday, December 30, 2007 2:11 PM To: users@maven.apache.org Subject: RE: Problem with maven-dependency-plugin: copy-dependencies I changed the packaging of module C into jar, and no difference. I think the copy-dependency plugin does not take into account dependencies on artifacts on the reactor (in this case Module A and Module B), but only on real dependencies from the repositorie. Not sure what you mean here. If a dependency is listed in the pom, it is included. There are no other ways for dependencies to be included. Sharing a reactor has other subtle effects but doesn't change the fact that a dependency needs to be listed. Perhaps I'm not getting what you're saying. ...I don't want to pull in the dependencies of Module C (the war), but I want to copy all the dependencies of Module C (including Module A and Module B).. Huh? You do or don't want the dependencies of Module C? to a specific directory, so that later on I can do some additional processing on it. All dependencies are there, even the transitive dependencies of module A and module B (which are both packaged as Jar), except for ModuleA.jar and ModuleB.jar. Simply binding copy-dependencies should get you all dependencies of whatever pom you've put it in. If it's module C, then you'll get all transitive dependencies of that Module. If you put it in the parent, chances are that parent doesn't declare dependencies like you want so you won't get what you want (module != dependency). Brian E Fox wrote: I think the problem is the war packaging. Maven doesn't normally pull in war dependencies transitively because the dependencies are included inside it. The dependency plugin xxx-dependencies goals are asking Maven to do the resolution and then filters the results, so in this case the transitive deps are not included. One thing you could try is copying the dependencies from Module C's pom since the plugin would have knowledge of all the dependencies, or you could unpack the war (because presumably the dependencies you need are in /lib). (using the latest snapshot, you can filter the contents as they are unpacked). -Original Message- From: Patrick Vanbrabant [mailto:[EMAIL PROTECTED] Sent: Sunday, December 30, 2007 5:53 AM To: users@maven.apache.org Subject: Problem with maven-dependency-plugin: copy-dependencies Hi, I have a multi-module project set up as follows. Parent Module A depenencies: x, y,z Module B dependencies: A, y,d, Module C dependencies: A, B, t,u,y Each module with its own dependencies. Now I want to execute the goal copy-dependencies on module C, but through the parent pom. So I execute mvn -U package on the parent project. The plugin is configured as follows: plugin
Re: Migrating from Maven 1 to Maven 2
What exactly are you looking for help with? Converting the project.xml into pom.xml? Analyzing your dependencies to see what is actually needed? Something else entirely? Wayne Well, a converter from project.xml to pom.xml would be a first start, then, yes, something to analyze the depependencies, to tell me which dependencies are simply transitive dependencies - example - if I had a maven 1project with dependencies a, b, c, and this analyzer tells me that b needs c, I could realize that a needs be and b needs c - transitive. But how could I find out which dependencies are not used at all anymore? And is there a way to tell maven to just retrieve the newest version from the repo? I know there is dependencymanagement, which I am using at great extend, is there a way / shouldn't it be possible to just leave the version number, so that maven retrieves the newest version of this dependeny? As I am doing a big step anyway - moving to maven 2 - I think I could just as well do a big clean up and also update all dependencies were possible. Thanks, Stefanie -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-eclipse-plugin writes to src/main/webapp
On Thursday 21 February 2008 wrote Arnaud HERITIER: I prefer to have a new issue and a link between them. Created: http://jira.codehaus.org/browse/MECLIPSE-392 You can wait to have it fixed OR you can propose a patch (code+test+doc) to be sure it will be. Currently I'm too busy but maybe I'll have a look at it later... thx, - martin -- Martin Höller | [EMAIL PROTECTED] *x Software + Systeme | http://www.xss.co.at/ Karmarschgasse 51/2/20 | Tel: +43-1-6060114-30 A-1100 Vienna, Austria | Fax: +43-1-6060114-71 signature.asc Description: This is a digitally signed message part.
Using variables in src\site\apt\index.apt - is there a default-index.apt or even inheritance?
Hi,
what´s the magic behind the default Site generation ? Without specifying
anything the index.html is being generated containing
About ${project.name}
${project.description}
The index.html looks like:
...
div id=bodyColumn
div id=contentBox
div class=sectionh2About Proficio API/h2pProficio sample
application from quot;Better Builds with Mavenquot;/p/div
/div
/div
...
When I now create my own src\site\apt\index.apt File, the Default with
About and Description is gone.
a) is there a default-index.apt file I can copy and modify? A
default-site.xml I´ve found in the maven-site-plugin-version.jar
b) how can I use dynamic content in an apt File,e.g. ${project.version}
or what´s the recommended way ?
I´ve read something at
http://www.nabble.com/-M2--Insert-variables-in-xdoc-apt-files-to5366829.html#a5371135
Is that the recommended way to play around with the directories using the
filtering process?
Thanx for any hints,
Torsten
Re: maven-eclipse-plugin writes to src/main/webapp
On synchronizing a pde plugin with maven-eclipse-plugin, it looks to me that Manifest.mf file do get synchronized even though it is in META-INF folder. Does maven-eclipse-plugin synchronizes it with .classpath or how? Regards, Amit On Fri, Feb 22, 2008 at 1:13 PM, Martin Höller [EMAIL PROTECTED] wrote: On Thursday 21 February 2008 wrote Arnaud HERITIER: I prefer to have a new issue and a link between them. Created: http://jira.codehaus.org/browse/MECLIPSE-392 You can wait to have it fixed OR you can propose a patch (code+test+doc) to be sure it will be. Currently I'm too busy but maybe I'll have a look at it later... thx, - martin -- Martin Höller | [EMAIL PROTECTED] *x Software + Systeme | http://www.xss.co.at/ Karmarschgasse 51/2/20 | Tel: +43-1-6060114-30 A-1100 Vienna, Austria | Fax: +43-1-6060114-71
