AW: umlgraph doccheck
Hi Brett,
thx for your answer. Which debug flag do you mean, the -e switch provided by
maven? How can I integrate the parameters to my pom (via additionalparams ?)
Sorry, I'm very new to maven and javadoc :-/
Thank you,
Matthias
-Ursprüngliche Nachricht-
Von: Brett Porter [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 9. Oktober 2008 02:22
An: Maven Users List; [EMAIL PROTECTED]
Betreff: Re: umlgraph doccheck
Try running with the javadoc debug flag and -X to see the command
actually constructed and ensure the artifact is provided correctly. I
noticed in a previous version that it hid the fact it was ignoring
some doclet artifacts.
You might also be able to upgrade to the latest release by explicitly
providing the version of the javadoc version which should report this
better now.
- Brett
2008/10/9 Matthias Dorfner [EMAIL PROTECTED]:
Hi everybody,
I try to integrate umlgraph and doccheck in my reporting site. I therefore
installed the doccheck 1.2b2 version via install-file successfully to my
local repository:
C:\Dok~\Matty\.m2\repository\com\sun\tools\doclets\doccheck\1.2b2
My reporting section of the POM looks like this:
plugins…
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
configuration
!--showprivate/show--
docletgr.spinellis.umlgraph.doclet.UmlGraphDoc/doclet
docletArtifact
groupIdgr.spinellis/groupId
artifactIdUmlGraph/artifactId
version4.6/version
/docletArtifact
additionalparam
-inferrel
-inferdep
-collpackages java.util.*
/additionalparam !---hide java.*--
/configuration
reportSets
reportSet
idhtml/id
reports
reportjavadoc/report
/reports
/reportSet
reportSet
iddoccheck/id
configuration
docletcom.sun.tools.doclet.DocCheck/doclet
!-- docletPath/path/to/doccheck.jar/docletPath --
docletArtifact
groupIdcom.sun.tools.doclets/groupId
artifactIddoccheck/artifactId
version1.2b2/version
/docletArtifact
additionalparam
-d ${project.build.directory}/site/doccheck
/additionalparam
!-- Other dir than apidocs --
destDirdoccheck/destDir
!-- For the project-reports page--
nameDocCheck/name
descriptionDocCheck documentation./description
/configuration
reports
reportjavadoc/report
/reports
/reportSet
/reportSets
/plugin
…
The error is following: [ERROR] BUILD ERROR
[INFO]
[INFO] Error during page generation
Embedded error: Error rendering Maven report: Exit code: 1 - javadoc:
error - Cannot find doclet class com.sun.tools.doclet.DocCheck
What am I'm doing wrong?
Maybe someone can explain me the meaning of the reportSet Tag and how I can
integrate these settings in my project page?
Thank you in advance!
Regards,
Matthias
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
-
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: Generate list of plugins and their versions used in a build
Couldn't you parse the output of mvn help:effective-pom? Or do you need another format? Maybe it could be another goal on the help plugin. What is your use case and what do you need? Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Thu, Oct 9, 2008 at 12:00 PM, Michael McCallum [EMAIL PROTECTED] wrote: mvn help:effective-pom On Thu, 09 Oct 2008 22:16:39 aman kohli wrote: Hi, For a build, I need to generate the plugins used and their versions. Is there a way to do this? Ideally something as simple as the effective-pom mechanism would be great. One mechanism would be to to use the plugin-registry, if there is a way to auto generate that. http://maven.apache.org/guides/introduction/introduction-to-plugin-registry .html thanks -- aman -- 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]
sequence of plugin execution
Hi, 1. how can I control the sequence of execution when more than one plugin is bound to the same phase? 2. When I bind a plugin to a phase, can I control if it is executed just before or after the phase? Wolfgang
Re: umlgraph doccheck
http://maven.apache.org/plugins/maven-javadoc-plugin/faq.html#How_to_know_exactly_the_Javadoc_command_line
2008/10/9 Matthias Dorfner [EMAIL PROTECTED]:
Hi Brett,
thx for your answer. Which debug flag do you mean, the -e switch provided by
maven? How can I integrate the parameters to my pom (via additionalparams
?) Sorry, I'm very new to maven and javadoc :-/
Thank you,
Matthias
-Ursprüngliche Nachricht-
Von: Brett Porter [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 9. Oktober 2008 02:22
An: Maven Users List; [EMAIL PROTECTED]
Betreff: Re: umlgraph doccheck
Try running with the javadoc debug flag and -X to see the command
actually constructed and ensure the artifact is provided correctly. I
noticed in a previous version that it hid the fact it was ignoring
some doclet artifacts.
You might also be able to upgrade to the latest release by explicitly
providing the version of the javadoc version which should report this
better now.
- Brett
2008/10/9 Matthias Dorfner [EMAIL PROTECTED]:
Hi everybody,
I try to integrate umlgraph and doccheck in my reporting site. I therefore
installed the doccheck 1.2b2 version via install-file successfully to my
local repository:
C:\Dok~\Matty\.m2\repository\com\sun\tools\doclets\doccheck\1.2b2
My reporting section of the POM looks like this:
plugins…
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
configuration
!--showprivate/show--
docletgr.spinellis.umlgraph.doclet.UmlGraphDoc/doclet
docletArtifact
groupIdgr.spinellis/groupId
artifactIdUmlGraph/artifactId
version4.6/version
/docletArtifact
additionalparam
-inferrel
-inferdep
-collpackages java.util.*
/additionalparam !---hide java.*--
/configuration
reportSets
reportSet
idhtml/id
reports
reportjavadoc/report
/reports
/reportSet
reportSet
iddoccheck/id
configuration
docletcom.sun.tools.doclet.DocCheck/doclet
!-- docletPath/path/to/doccheck.jar/docletPath --
docletArtifact
groupIdcom.sun.tools.doclets/groupId
artifactIddoccheck/artifactId
version1.2b2/version
/docletArtifact
additionalparam
-d ${project.build.directory}/site/doccheck
/additionalparam
!-- Other dir than apidocs --
destDirdoccheck/destDir
!-- For the project-reports page--
nameDocCheck/name
descriptionDocCheck documentation./description
/configuration
reports
reportjavadoc/report
/reports
/reportSet
/reportSets
/plugin
…
The error is following: [ERROR] BUILD ERROR
[INFO]
[INFO] Error during page generation
Embedded error: Error rendering Maven report: Exit code: 1 - javadoc:
error - Cannot find doclet class com.sun.tools.doclet.DocCheck
What am I'm doing wrong?
Maybe someone can explain me the meaning of the reportSet Tag and how I
can integrate these settings in my project page?
Thank you in advance!
Regards,
Matthias
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Version conflict resolution and stable builds
On Thu, 09 Oct 2008 12:47:13 Ian Robertson wrote: I'm actually curious if anyone knows the reason for this; it seams that a far better choice would be to choose the *lowest* version which matches all range requirements, so that builds could be temporally stable. ranges would be useless because they would never change, ultimately it assumes that you are converging on the goal and new releases are better... which is quite reasonable -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EclipsePlugin] downloading sources without writing .project and .classpath files
Thanks a lot. It works. I never found this in search google for this. All solutions refer to eclipse:eclipse Many thanks. Andreas --- Thor [EMAIL PROTECTED] schrieb am Mi, 8.10.2008: Von: Thor [EMAIL PROTECTED] Betreff: Re: [EclipsePlugin] downloading sources without writing .project and .classpath files An: Maven Users List users@maven.apache.org, [EMAIL PROTECTED] Datum: Mittwoch, 8. Oktober 2008, 21:15 Use the dependency plugin: mvn dependency:sources http://maven.apache.org/plugins/maven-dependency-plugin/ On Wed, Oct 8, 2008 at 5:00 AM, Andreas Riedel [EMAIL PROTECTED]wrote: Hello List. I've a question by using the Eclipse Plugin. We will dispose the Q4E Eclipse Plugin. So call the Plugin with: mvn eclipse:eclipse -DdownloadSources=true works fine. But the writen .project and .classpath files are shared by SVN. So the other developer aren't beholden to run write the .project and .classpath files new. So, is it possible to download the sources by the plugin but don't write the .project and .classpath files again and again. TIA Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- (o_ \*/ \ / / / )_ | | O | v v In a free world... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: sequence of plugin execution
I never developed a real plugin, but I guess that having a look here could here : http://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/maven-core/src/main/resources/META-INF/plexus/components.xml In fact, you'll see there the existing phase (pre- or post- ones). Cheers. 2008/10/9 [EMAIL PROTECTED] Hi, 1. how can I control the sequence of execution when more than one plugin is bound to the same phase? 2. When I bind a plugin to a phase, can I control if it is executed just before or after the phase? Wolfgang -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: sequence of plugin execution
Answer to question 1: No, you can't control in which order the plugins in a specific phase run. And indeed, there are some pre and post phases (or other phases, which normally are not very heavily used): For the default lifecycle: phases phasevalidate/phase phaseinitialize/phase phasegenerate-sources/phase phaseprocess-sources/phase phasegenerate-resources/phase phaseprocess-resources/phase phasecompile/phase phaseprocess-classes/phase phasegenerate-test-sources/phase phaseprocess-test-sources/phase phasegenerate-test-resources/phase phaseprocess-test-resources/phase phasetest-compile/phase phaseprocess-test-classes/phase phasetest/phase phasepackage/phase phasepre-integration-test/phase phaseintegration-test/phase phasepost-integration-test/phase phaseverify/phase phaseinstall/phase phasedeploy/phase /phases What are you trying to accomplish? With regards, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Thu, Oct 9, 2008 at 3:04 PM, Baptiste MATHUS [EMAIL PROTECTED] wrote: I never developed a real plugin, but I guess that having a look here could here : http://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/maven-core/src/main/resources/META-INF/plexus/components.xml In fact, you'll see there the existing phase (pre- or post- ones). Cheers. 2008/10/9 [EMAIL PROTECTED] Hi, 1. how can I control the sequence of execution when more than one plugin is bound to the same phase? 2. When I bind a plugin to a phase, can I control if it is executed just before or after the phase? Wolfgang -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Multi-module ejb builds pulling from the repository
Hi all, Environment: Maven 2.0.8, jdk 1.6 I'm having a problem with an ejb-based project, whose build process I've recently converted to use maven2. As the project involves several ejbs, and the existing build structure already had these targeted to separate jar files, it made sense to me to use maven modules. I'm seeing a problem which this bug report describes pretty much exactly - http://jira.codehaus.org/browse/MNG-2502 . Does anyone know a way around this problem, or if/when this might get addressed? Presently I'm having to run a package build (which fails after changes have been made to anything in the ejb jars), run a shell script to copy the ejb jars into the repository, then run the package build again (at which point it uses the jars from the repository, as explained in the bug report above). - it seems odd that this issue has been open for two years - are there really so few people doing multi-module builds with ejb? Regards, Andy The contents of this message and any attachments are confidential and are intended for the use of the persons to whom it is addressed. If you are not the intended recipient, you should not copy, forward, use or alter the message in any way, nor disclose its contents to any other person. Please notify the sender immediately and delete the e-mail from your system, if you so wish you can contact us on +44 1624 688000. The sender is not responsible for any alterations that may have occurred without authorisation. Any files attached to this email will have been checked by us with virus detection software before transmission. You should carry out your own virus checks before opening any attachments, as we do not accept any liability for loss or damage which may be caused by viruses. For information regarding company registration please visit the contact page at www.hansard.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Version conflict resolution and stable builds
Lets got back to the basics of development... you need to develop something to that is delivered to be run So by my way of thinking I want an acurate description of whats delivered and run such that I can reproduce it. Have the convention that versions are in the jar names and the pom and its properties end up in the jar facilitates this. But I also need to have a flexible develoment environment with low overheads. If I use best guess or open ranges I have no power to control things because i need to tweak poms all over the place. So my approach is a design and build by contract when i use the major version to indicate a contract... and all my ranges restrict a dependency to a single major version. e.g. a.b.c-1.5 depends on a.b.d with [1,2) This is arbitrarily simple see a more complex example attached Now what this means is that when you break your project down into its component pieces you can by convention relate them to other things stably. Not reproducibly but thats ok because its determinable. If you try to build your deliverable and there is a range conflict you get an error on build... you can't build a dodgy deliverable. With open version ranges or best guess deps you can end up with any released dependency! and even if you have a process to know when you got it wrong but its very difficult other than adding dependencies to the deliverable project to get it right. Now your developers need to make a call when they release - usually after discussion - is my change breaking - you can test this with CI - and if so should I increment the major version. If you get broken because they make a mistake you have options... roll back deps... release a new rolled back version... The funny thing I avoided most of the gotches due to my approach... Now the gotchas... 1) don't use modules 2) don't use snapshot parents or relative paths 3) inherit by function which means have parents that configure particular plugins and keep them simple and try to have a little as possible in children poms. i have a 2 deep hierarhcy with one root and 9 sub parents The convention i use to break projects down is by function that means I have api, model aka domain, strategy, composition, configuration, webapp, abstract webapp, webservice, repository. It means a proliferation of artifacts but at the same time a proliferation of reuse... 4) use a 2 point version major.release and always start at X.1 never at X.0 otherwise ranges don't work... its not a bug just an ideosyncracy... consider [1,2) this does not match 1.0-SNAPSHOT and matches 2.0-SNAPSHOT which seems odd... if you never make 1.0-SNAPSHOT or 2.0-SNAPSHOT then range boundaries work determinably. range calculations break down if have more that 3 points so you need to leave wiggle room. 5) save the third point for patches which are releases off branches 6) don't use dependency management it encourages bad inheritance, you can just use transitive dependencies and they are more flexible 7) wrap 3rd party dependencies with local projects that just enforce consistent resolution - they don't use ranges so you need to manage it theres a taste i probably missed something as this is just off the top of my head, gotta do some work now On Thu, 09 Oct 2008 12:47:13 Ian Robertson wrote: On Sun, 2008-10-05 at 04:48 -0600, Michael McCallum wrote: On Sat, 04 Oct 2008 14:16:57 Keith Branton wrote: 1. Can anyone please tell me of a way to achieve this with 2.0.9 today? With the appropriate use of ranges you can do this and it resolves as described. There are about 11 gotchas to doing it though, all worked around by appropriate conventions. Can you elaborate on what these 11 gotchas are, or point to a place which does? One of the biggest issues I see with ranges is that maven chooses the most recent version in the repository which matches a given range. Consequently, if a pom specifies a version range for a dependency like [1.5,), the exact same code can create different builds on different days if a new release of the dependency is made. I'm actually curious if anyone knows the reason for this; it seams that a far better choice would be to choose the *lowest* version which matches all range requirements, so that builds could be temporally stable. - Ian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'dependency'. WAGON_VERSION: 1.0-beta-2 [INFO] [INFO] Building Jis Products [INFO]task-segment: [dependency:tree] [INFO] [INFO] [dependency:tree] [INFO]
Generate list of plugins and their versions used in a build
Hi, For a build, I need to generate the plugins used and their versions. Is there a way to do this? Ideally something as simple as the effective-pom mechanism would be great. One mechanism would be to to use the plugin-registry, if there is a way to auto generate that. http://maven.apache.org/guides/introduction/introduction-to-plugin-registry.html thanks -- aman
Re: Question about JIRA question type？
*Hi,* Well, just have a look some millimeters on the right of the combo for Issue Type... There's a bug ?. If you click on it, you'll have the documentation open... *Thanks.* Cheers. 2008/10/9 陈思淼 [EMAIL PROTECTED] when I use JIRA trying to make some new function,there are some of question type,including: new function,improvement,task, what's the difference of these kind of types? anybody can tell me that? -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: Version conflict resolution and stable builds
I believe using dependencyManagement actually helps you... it gives you the power to control the dependency versions... from the doc: very important use of the dependency management section is to control the versions of artifacts used in transitive dependencies --zoly Michael McCallum wrote: Lets got back to the basics of development... you need to develop something to that is delivered to be run So by my way of thinking I want an acurate description of whats delivered and run such that I can reproduce it. Have the convention that versions are in the jar names and the pom and its properties end up in the jar facilitates this. But I also need to have a flexible develoment environment with low overheads. If I use best guess or open ranges I have no power to control things because i need to tweak poms all over the place. So my approach is a design and build by contract when i use the major version to indicate a contract... and all my ranges restrict a dependency to a single major version. e.g. a.b.c-1.5 depends on a.b.d with [1,2) This is arbitrarily simple see a more complex example attached Now what this means is that when you break your project down into its component pieces you can by convention relate them to other things stably. Not reproducibly but thats ok because its determinable. If you try to build your deliverable and there is a range conflict you get an error on build... you can't build a dodgy deliverable. With open version ranges or best guess deps you can end up with any released dependency! and even if you have a process to know when you got it wrong but its very difficult other than adding dependencies to the deliverable project to get it right. Now your developers need to make a call when they release - usually after discussion - is my change breaking - you can test this with CI - and if so should I increment the major version. If you get broken because they make a mistake you have options... roll back deps... release a new rolled back version... The funny thing I avoided most of the gotches due to my approach... Now the gotchas... 1) don't use modules 2) don't use snapshot parents or relative paths 3) inherit by function which means have parents that configure particular plugins and keep them simple and try to have a little as possible in children poms. i have a 2 deep hierarhcy with one root and 9 sub parents The convention i use to break projects down is by function that means I have api, model aka domain, strategy, composition, configuration, webapp, abstract webapp, webservice, repository. It means a proliferation of artifacts but at the same time a proliferation of reuse... 4) use a 2 point version major.release and always start at X.1 never at X.0 otherwise ranges don't work... its not a bug just an ideosyncracy... consider [1,2) this does not match 1.0-SNAPSHOT and matches 2.0-SNAPSHOT which seems odd... if you never make 1.0-SNAPSHOT or 2.0-SNAPSHOT then range boundaries work determinably. range calculations break down if have more that 3 points so you need to leave wiggle room. 5) save the third point for patches which are releases off branches 6) don't use dependency management it encourages bad inheritance, you can just use transitive dependencies and they are more flexible 7) wrap 3rd party dependencies with local projects that just enforce consistent resolution - they don't use ranges so you need to manage it theres a taste i probably missed something as this is just off the top of my head, gotta do some work now On Thu, 09 Oct 2008 12:47:13 Ian Robertson wrote: On Sun, 2008-10-05 at 04:48 -0600, Michael McCallum wrote: On Sat, 04 Oct 2008 14:16:57 Keith Branton wrote: 1. Can anyone please tell me of a way to achieve this with 2.0.9 today? With the appropriate use of ranges you can do this and it resolves as described. There are about 11 gotchas to doing it though, all worked around by appropriate conventions. Can you elaborate on what these 11 gotchas are, or point to a place which does? One of the biggest issues I see with ranges is that maven chooses the most recent version in the repository which matches a given range. Consequently, if a pom specifies a version range for a dependency like [1.5,), the exact same code can create different builds on different days if a new release of the dependency is made. I'm actually curious if anyone knows the reason for this; it seams that a far better choice would be to choose the *lowest* version which matches all range requirements, so that builds could be temporally stable. - Ian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL
Re: javaee.jar issues
After posting this to the Glassfish list, I was redirected to the Glassfish dev list where my issue was promptly ignored. Next step is probably to enter an issue for it on the Glassfish site and see if someone picks that up. On Tue, Sep 30, 2008 at 11:32, Mykel Alvis [EMAIL PROTECTED] wrote: I haven't but that does sound like a good plan. I'll give it a try. Thanks! On Tue, Sep 30, 2008 at 11:30, Stephen Connolly [EMAIL PROTECTED] wrote: have you tried the glassfish mailing list? If this was glassfish 3 I'd say email sahoo directly too... but i'm not sure if v2 is his bag 2008/9/30 Mykel Alvis [EMAIL PROTECTED] As my original post indicated, I couldn't find a place to do so. If you happen to know how to contact them regarding this sort of matter, I'd love that have that information and I'll immediately start the contact process. On Tue, Sep 30, 2008 at 11:13, Martin Gainty [EMAIL PROTECTED] wrote: if there is a duplicate manifest.mf on javaee.jar from their distro did you contact sun on this issue and what was the response? Martin
How to rename or copy resource files when packaging war-file
Hi! In my project I have two files, foo-dev.xml and foo-production.xml, in src/main/resources. When I package the project as a war-file I want to rename or copy one of those files to foo.xml. Which file to rename or copy depends on which profile I run maven with. Is this possible and where can I learn more about this? Regards, Johan Hammar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Documentation woes
So there exists a problem in the last 4 places that I've worked. I've implemented Maven as a build tool at all the places, and eventually people come around to seeing what it provides. But the documentation issue is still a pain. I primarily use Subversion for SCM, and committing binaries to it in the form of the ubiquitous M$ Word document is painful, both from a philosophical standpoint and from the occasionally checkout delay when a document undergoes a lot of revision. Developers being the lazy sorts that we tend to be aren't interested in writing what little documentation they actually provide in anything other than the corporate mandated word document. As for anyone other than developers, forget it. Many of the BAs in my company don't even understand that other document formats even exist. In the end, for the several hundred maven projects that we have here, all the real documentation is in word docs committed to the subversion tree that then have to be bundled into src/site/resources and then links made to them in the site descriptor. Since the generated site is one the most useful elements of a maven build (at least for us), the documentation being part of the site is preferable to having a download link for a piece of documentation. So my question is does anyone has a template or transformation tool for taking Word documents and turning them into clean XDOC? I just spent about an hour using Open Office to export a word doc to XHTML and try to clean it up. The results are acceptable if unspectacular, but that's more likely due to the template that the original docs were written using. I'm not particularly familiar with Open Office's tools other than the standard ones, but I know that people regularly produce filters and such. Has anyone here written a filter/export tool/XSL transformer/anything that could automate this task? Any thoughts on this? Thanks! Mykel
Re: Generate list of plugins and their versions used in a build
mvn help:effective-pom On Thu, 09 Oct 2008 22:16:39 aman kohli wrote: Hi, For a build, I need to generate the plugins used and their versions. Is there a way to do this? Ideally something as simple as the effective-pom mechanism would be great. One mechanism would be to to use the plugin-registry, if there is a way to auto generate that. http://maven.apache.org/guides/introduction/introduction-to-plugin-registry .html thanks -- aman -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Documentation woes
On Thu, Oct 9, 2008 at 7:33 AM, Mykel Alvis [EMAIL PROTECTED] wrote: So my question is does anyone has a template or transformation tool for taking Word documents and turning them into clean XDOC? Any thoughts on this? If you end up needing to write something to do it, I wonder whether anything in Apache POI could help. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Documentation woes
Wendy Smoak wrote: On Thu, Oct 9, 2008 at 7:33 AM, Mykel Alvis [EMAIL PROTECTED] wrote: So my question is does anyone has a template or transformation tool for taking Word documents and turning them into clean XDOC? Any thoughts on this? If you end up needing to write something to do it, I wonder whether anything in Apache POI could help. Or, maybe one of the open document format processing libraries: http://www.jopendocument.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
URL encoding issues on Windows platform
One of our developers is using the exec:java plugin to launch a Java application. Within the application the JBoss Microcontainer is used and a java.net.MalformedURLException occurs. Apparently this is a known problem: http://web.aanet.com.au/persabi/andromda/faq.html#MalformedURLException_with_Tests However the workaround recommended in the reference above is to move the local .m2 repo to a directory with no spaces in the pathname. This seems like a drastic approach to me. Does anyone here know of a way to use Spring and the JBoss Microcontainer on a Windows platform without having to move the .m2 repo? TIA -- View this message in context: http://www.nabble.com/URL-encoding-issues-on-Windows-platform-tp19901546p19901546.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: Documentation woes
It seems likely that I will need to write something, having found nothing using teh interwebs so far. Thanks, Aaron and Wendy, for some direction. I may be incorrect about this, but it seems like the doxia documentation is a little sparse. During site generation I see a lot of download attempts for artifacts, templates I believe. I can't seem to locate any written docs on how one uses such things. Are there any such docs? On Thu, Oct 9, 2008 at 10:22, Aaron Metzger [EMAIL PROTECTED] wrote: Wendy Smoak wrote: On Thu, Oct 9, 2008 at 7:33 AM, Mykel Alvis [EMAIL PROTECTED] wrote: So my question is does anyone has a template or transformation tool for taking Word documents and turning them into clean XDOC? Any thoughts on this? If you end up needing to write something to do it, I wonder whether anything in Apache POI could help. Or, maybe one of the open document format processing libraries: http://www.jopendocument.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How do I exclude an xml file from a jar?
I need to have persistence.xml file on the classpath in order to perform DDL generation using the Hibernate Tool hbm2ddl. However I don't want the persistence.xml file to be included in the jar file. How can I exclude persistence.xml from the jar file even though it needs to be on the classpath earlier in the lifecycle? TIA -- View this message in context: http://www.nabble.com/How-do-I-exclude-an-xml-file-from-a-jar--tp19902363p19902363.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: sequence of plugin execution
On Thu, Oct 9, 2008 at 9:14 AM, Nick Stolwijk [EMAIL PROTECTED]wrote: Answer to question 1: No, you can't control in which order the plugins in a specific phase run. And indeed, there are some pre and post phases (or other phases, which normally are not very heavily used): I looked this up recently; there are some feature requests filed, but the impression I came away with is that informally, declaration order does determine order (which didn't help me, since I want something declared in a profile later in the pom to take effect before something declared earlier in the pom). So you might be able to move things around and achieve some semblance of ordering; I haven't tried it, so I could have misinterpreted some of what I read. - Geoffrey -- Geoffrey Wiseman
WSDL as Maven artifact
We are building web services and in our approach multiple maven projects would be consumers of the service WSDL in order to generate their server / client stubs. I think it would be good to have a project of packaging type wsdl and then have consumer projects depend on that artifact. Has anybody tried to do this or is there a better pattern for doing this? I found one reference on the web about this : http://myarch.com/using-maven-repository-as-web-services-registry Possibly the hard part would be integrating with existing wsdl2java plugins that expect a file path to the WSDL file. I would guess that I would have to customize one to automatically grab depencies of type wsdl and then pass them to the code generator. Peter Hayes http://www.linkedin.com/in/petehayes Architecture Shared Technology Services | Fidelity Investments Management Technology
trying to use Toolchain plugin
I am trying to use the Toolchain feature described here: http://maven.apache.org/guides/mini/guide-using-toolchains.html (By the way, I find it a little disconcerting that SNAPSHOT features are described on the public site without more warning and information on how to actually use such features by enabling shapshot repos). When I try to use this, I quickly found that I needed to add Apache's maven shapshot repo like so to my pom.xml: pluginRepository idsnapshots/id urlhttp://people.apache.org/repo/m2-snapshot-repository//url releases enabledfalse/enabled /releases /pluginRepository However, now maven isn't finding org.codehaus.plexus:plexus-compiler-api:jar:1.6-SNAPSHOT I know codehaus has a snapshot repo but I can't find a snapshot here: http://snapshots.repository.codehaus.org/org/codehaus/plexus/ this directory listing is only showing: [DIR] plexus-spring/ 08-Oct-2008 16:42- [DIR] plexus-stylus-skin/ 08-Oct-2008 17:15 Where do I get this from? Cheers, David Smiley -- View this message in context: http://www.nabble.com/trying-to-use-Toolchain-plugin-tp19904145p19904145.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: Generate list of plugins and their versions used in a build
I can't believe you said that. :-/ Just fork the mojo and actually write the output to a file or even better patch the help plugin to 'attach' its output to the artifact. On Thu, 09 Oct 2008 23:03:37 Nick Stolwijk wrote: Couldn't you parse the output of mvn help:effective-pom? Or do you need another format? Maybe it could be another goal on the help plugin. What is your use case and what do you need? Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Thu, Oct 9, 2008 at 12:00 PM, Michael McCallum [EMAIL PROTECTED] wrote: mvn help:effective-pom On Thu, 09 Oct 2008 22:16:39 aman kohli wrote: Hi, For a build, I need to generate the plugins used and their versions. Is there a way to do this? Ideally something as simple as the effective-pom mechanism would be great. One mechanism would be to to use the plugin-registry, if there is a way to auto generate that. http://maven.apache.org/guides/introduction/introduction-to-plugin-regis try .html thanks -- aman -- 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] -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to rename or copy resource files when packaging war-file
why not externalise - as in not in the war - the configuration? because by inferrence you are talking about rebuilding your war file for different environments... how do you guarantee that its the same without a bunch of extra hassle? On Fri, 10 Oct 2008 03:27:04 Johan Hammar wrote: Hi! In my project I have two files, foo-dev.xml and foo-production.xml, in src/main/resources. When I package the project as a war-file I want to rename or copy one of those files to foo.xml. Which file to rename or copy depends on which profile I run maven with. Is this possible and where can I learn more about this? Regards, Johan Hammar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Dependency SNAPSHOT problem
Hi all, I'm working on a module that is a dependency of our main project. I created this module as a snapshot since its currently under development as well and its not a stable version yet. I upload it to our internal remote repository, however, whenever anyone updates their dependencies they don't get the latest version of my module, the copy still remains the same as the previous version until they delete their local copy of the dependency. This is a sample of my module's pom file project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdca.abc/groupId artifactIdlist/artifactId version1.0-SNAPSHOT/version namesome List/name descriptionXMLBeans created schema jar/description /project I use mvn deploy plugin to deploy this file (its an xmlbean created jar file if anyone cares to know). And this is what I use to deploy the jar file mvn deploy:deploy-file -Durl=scp://address -DrepositoryId=repo_id -Dfile=file.jar -DpomFile=pom.xml This part seems to be working fine since it creates a new jar file on the repo with a new timestamp everytime I deploy the new verison of my jar file, however the other users can't get the latest copy. This is the sample pom file of our main project project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdca.abc/groupId artifactIdqc/artifactId packagingjar/packaging version2.0/version nameQC/name build plugins plugin artifactIdmaven-compiler-plugin/artifactId version2.0.2/version configuration source1.6/source target1.6/target /configuration /plugin /plugins /build repositories repository idrepo_id/id urlhttp://address/url /repository /repositories dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version4.3.1/version scopetest/scope /dependency dependency groupIdca.abc/groupId artifactIdlist/artifactId version1.0-SNAPSHOT/version scopecompile/scope /dependency /dependencies /project Any ideas? Or do I've the whole idea of SNAPSHOT wrong? Thank you
Re: WSDL as Maven artifact
I think in typical cases a single WSDL is too small of a source fragment to be a build artifact. The pattern I've often followed is that I keep the wsdl and the generated client stubs in one module with an obvious packaging type jar, then use the jar both on the client and the server side. Kalle On Thu, Oct 9, 2008 at 10:02 AM, Hayes, Peter [EMAIL PROTECTED] wrote: We are building web services and in our approach multiple maven projects would be consumers of the service WSDL in order to generate their server / client stubs. I think it would be good to have a project of packaging type wsdl and then have consumer projects depend on that artifact. Has anybody tried to do this or is there a better pattern for doing this? I found one reference on the web about this : http://myarch.com/using-maven-repository-as-web-services-registry Possibly the hard part would be integrating with existing wsdl2java plugins that expect a file path to the WSDL file. I would guess that I would have to customize one to automatically grab depencies of type wsdl and then pass them to the code generator. Peter Hayes [image: LinkedIn Profile]http://www.linkedin.com/in/petehayes Architecture Shared Technology Services | Fidelity Investments Management Technology
RE: WSDL as Maven artifact
How do you end up generating the server side skeleton files? Is this done as part of the module with the WSDL? -Original Message- From: Kalle Korhonen [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2008 3:00 PM To: Maven Users List Subject: Re: WSDL as Maven artifact I think in typical cases a single WSDL is too small of a source fragment to be a build artifact. The pattern I've often followed is that I keep the wsdl and the generated client stubs in one module with an obvious packaging type jar, then use the jar both on the client and the server side. Kalle On Thu, Oct 9, 2008 at 10:02 AM, Hayes, Peter [EMAIL PROTECTED] wrote: We are building web services and in our approach multiple maven projects would be consumers of the service WSDL in order to generate their server / client stubs. I think it would be good to have a project of packaging type wsdl and then have consumer projects depend on that artifact. Has anybody tried to do this or is there a better pattern for doing this? I found one reference on the web about this : http://myarch.com/using-maven-repository-as-web-services-registry Possibly the hard part would be integrating with existing wsdl2java plugins that expect a file path to the WSDL file. I would guess that I would have to customize one to automatically grab depencies of type wsdl and then pass them to the code generator. Peter Hayes [image: LinkedIn Profile]http://www.linkedin.com/in/petehayes Architecture Shared Technology Services | Fidelity Investments Management Technology - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Version conflict resolution and stable builds
On Fri, 10 Oct 2008 03:00:38 Zoltan Farkas wrote: I believe using dependencyManagement actually helps you... it gives you the power to control the dependency versions... in very simple cases it helps and with the import scope it can be quite useful but its more difficult to understand the result of depedency resolution. The issue I have is that depedency management is an attempt to force a version of a library but from outside of the resolution tree. It has side effects and ultimately it makes it harder to manage dependencies because it makes it easy consolidate all your version for a short term gain. For a small project it makes sense and works. For larger projects it does not. And I take the java view, fewer more well understood approaches to problems leads to better code sometimes more verbose but easy to understand. But even more than that when I manage versions of external libraries I just just manage versions, I also manage related libraries and exclusions and probably the most important: I provide an independent release cycle from the upstream projects which means all my projects can be exposed in stages to upstream releases. I fear that most of the things I say will make no sense to windows and linux users and a reaonsable portion of linux users who don't really understand how far package management has come and its parallels with maven. from the doc: very important use of the dependency management section is to control the versions of artifacts used in transitive dependencies --zoly -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL as Maven artifact
If the wsdl is in a jar, I know the CXF wsdl2java tooling (maven plugins) can grab the wsdl out of the jar and generate code from it. Thus, a common jar could have the wsdl and the common generated stuff (like the jaxb types, the service interface, etc...) and the others could use it. Dan On Thursday 09 October 2008 3:10:23 pm Hayes, Peter wrote: How do you end up generating the server side skeleton files? Is this done as part of the module with the WSDL? -Original Message- From: Kalle Korhonen [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2008 3:00 PM To: Maven Users List Subject: Re: WSDL as Maven artifact I think in typical cases a single WSDL is too small of a source fragment to be a build artifact. The pattern I've often followed is that I keep the wsdl and the generated client stubs in one module with an obvious packaging type jar, then use the jar both on the client and the server side. Kalle On Thu, Oct 9, 2008 at 10:02 AM, Hayes, Peter [EMAIL PROTECTED] wrote: We are building web services and in our approach multiple maven projects would be consumers of the service WSDL in order to generate their server / client stubs. I think it would be good to have a project of packaging type wsdl and then have consumer projects depend on that artifact. Has anybody tried to do this or is there a better pattern for doing this? I found one reference on the web about this : http://myarch.com/using-maven-repository-as-web-services-registry Possibly the hard part would be integrating with existing wsdl2java plugins that expect a file path to the WSDL file. I would guess that I would have to customize one to automatically grab depencies of type wsdl and then pass them to the code generator. Peter Hayes [image: LinkedIn Profile]http://www.linkedin.com/in/petehayes Architecture Shared Technology Services | Fidelity Investments Management Technology - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Daniel Kulp [EMAIL PROTECTED] http://dankulp.com/blog - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dependency SNAPSHOT problem
It depends how often your repository has been configured to check for updates... and also if you repository has been configured for snapshots Have a look in your settings.xml 2008/10/9 Qureshi,Shahzad [Ontario] [EMAIL PROTECTED]: Hi all, I'm working on a module that is a dependency of our main project. I created this module as a snapshot since its currently under development as well and its not a stable version yet. I upload it to our internal remote repository, however, whenever anyone updates their dependencies they don't get the latest version of my module, the copy still remains the same as the previous version until they delete their local copy of the dependency. This is a sample of my module's pom file project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdca.abc/groupId artifactIdlist/artifactId version1.0-SNAPSHOT/version namesome List/name descriptionXMLBeans created schema jar/description /project I use mvn deploy plugin to deploy this file (its an xmlbean created jar file if anyone cares to know). And this is what I use to deploy the jar file mvn deploy:deploy-file -Durl=scp://address -DrepositoryId=repo_id -Dfile=file.jar -DpomFile=pom.xml This part seems to be working fine since it creates a new jar file on the repo with a new timestamp everytime I deploy the new verison of my jar file, however the other users can't get the latest copy. This is the sample pom file of our main project project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdca.abc/groupId artifactIdqc/artifactId packagingjar/packaging version2.0/version nameQC/name build plugins plugin artifactIdmaven-compiler-plugin/artifactId version2.0.2/version configuration source1.6/source target1.6/target /configuration /plugin /plugins /build repositories repository idrepo_id/id urlhttp://address/url /repository /repositories dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version4.3.1/version scopetest/scope /dependency dependency groupIdca.abc/groupId artifactIdlist/artifactId version1.0-SNAPSHOT/version scopecompile/scope /dependency /dependencies /project Any ideas? Or do I've the whole idea of SNAPSHOT wrong? Thank you - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to rename or copy resource files when packaging war-file
Yes, that is of course the best solution, however our way of doing it is just temporary until we get some other stuff sorted out. I'm still interested if it is possible or not. Thanks, Johan On Thu, Oct 9, 2008 at 8:56 PM, Michael McCallum [EMAIL PROTECTED] wrote: why not externalise - as in not in the war - the configuration? because by inferrence you are talking about rebuilding your war file for different environments... how do you guarantee that its the same without a bunch of extra hassle? On Fri, 10 Oct 2008 03:27:04 Johan Hammar wrote: Hi! In my project I have two files, foo-dev.xml and foo-production.xml, in src/main/resources. When I package the project as a war-file I want to rename or copy one of those files to foo.xml. Which file to rename or copy depends on which profile I run maven with. Is this possible and where can I learn more about this? Regards, Johan Hammar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
reusing jar-with-dependencies assembly as primary artifact
Greetings, kinda simple tweak that apparently makes a lot of pain in maven. I need to use jar-with-dependencies instead of jar as *primary* artifact for 3 of 9 modules we have in our system. Anyway - the usual jar packaging is not used in the build process (for those 3 modules), only jar-with-deps, so the most natural idea is to switch jars somehow. For now I'm thinking of firing a small ant script doing exactly that immediately after package phase, so maven does not know I've hacked the jars and uses the thing I need. First - I don't like the idea to issue 'mvn install' each time I want to verify the project (as code changes from modules spill over to the local repo while subsequent modules may fail). So it would be quite fine to keep the whole project packageable w/o any local repo updates, e.g. using 'mvn package' most of the time. Thus I would like to stick to using only primary artifacts, which are visible across project siblings in 'mvn package' usecase. Attached artifacts are not visible, so if a sibling depends on jar-with-deps, and nothing is installed - then 'mvn package' would bother all the registered remote repos before failing. ...and even worse - it would silently use something stale from the local repo (!), which I am currently trying to prevent. Please remember that 'mvn install' may install something broken from a module while as some integration tests in subsequent modules would fail the whole build process. So - doing an assembly (as most samples suggest) does not fit as it generates the attached artifact (which requires that unsafe 'install' scenario). If I'm doing a custom packaging - I end up loosing a day or so tinkering with automagical maven internals which is of course a non-productive way to perform such a simple change. Any ideas, suggestions? Thanks in advance, Anton S. Kraievoy P.SOFF: We're currently migrating 1KLOC of ant code to maven. I'll try to do the same for ant + ivy and compare the experience (and leave the most convenient in charge). Looks like maven currently has vanishing chance to survive. I'll post an update on this matter in a week or two on my blog: http://java.akraievoy.org -- View this message in context: http://www.nabble.com/reusing-jar-with-dependencies-assembly-as-primary-artifact-tp19906052p19906052.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: Dependency SNAPSHOT problem
Thanks for your reply Stephen. I forgot to mention that we use m2eclipse so we manually update the dependencies. I don't know if you use m2eclipse but there is a option in m2eclipse that I can use to force update the dependencies and that is when I don't get the updates Shahzad Qureshi Systems Analyst Scientific Data Stewardship Division (CIOB-IM) Environment Canada [EMAIL PROTECTED] -Original Message- From: Stephen Connolly [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2008 3:20 PM To: Maven Users List Subject: Re: Dependency SNAPSHOT problem It depends how often your repository has been configured to check for updates... and also if you repository has been configured for snapshots Have a look in your settings.xml 2008/10/9 Qureshi,Shahzad [Ontario] [EMAIL PROTECTED]: Hi all, I'm working on a module that is a dependency of our main project. I created this module as a snapshot since its currently under development as well and its not a stable version yet. I upload it to our internal remote repository, however, whenever anyone updates their dependencies they don't get the latest version of my module, the copy still remains the same as the previous version until they delete their local copy of the dependency. This is a sample of my module's pom file project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdca.abc/groupId artifactIdlist/artifactId version1.0-SNAPSHOT/version namesome List/name descriptionXMLBeans created schema jar/description /project I use mvn deploy plugin to deploy this file (its an xmlbean created jar file if anyone cares to know). And this is what I use to deploy the jar file mvn deploy:deploy-file -Durl=scp://address -DrepositoryId=repo_id -Dfile=file.jar -DpomFile=pom.xml This part seems to be working fine since it creates a new jar file on the repo with a new timestamp everytime I deploy the new verison of my jar file, however the other users can't get the latest copy. This is the sample pom file of our main project project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdca.abc/groupId artifactIdqc/artifactId packagingjar/packaging version2.0/version nameQC/name build plugins plugin artifactIdmaven-compiler-plugin/artifactId version2.0.2/version configuration source1.6/source target1.6/target /configuration /plugin /plugins /build repositories repository idrepo_id/id urlhttp://address/url /repository /repositories dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version4.3.1/version scopetest/scope /dependency dependency groupIdca.abc/groupId artifactIdlist/artifactId version1.0-SNAPSHOT/version scopecompile/scope /dependency /dependencies /project Any ideas? Or do I've the whole idea of SNAPSHOT wrong? Thank you - 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: WSDL as Maven artifact
I second Kalle about the fact that wsdl are too small entities to elect them artifacts. In my current project I keep the wsdl in the service implementation artifact and I package the wsdl with clients stubs in another artifact. The client artifact being built with the following sequence : unpack the wsdl from the service artifact using maven-dependency-plugin and then generate the client stubs with the appropriate maven plugin. Paul Le Thursday 09 October 2008 19:02:45 Hayes, Peter, vous avez écrit : We are building web services and in our approach multiple maven projects would be consumers of the service WSDL in order to generate their server / client stubs. I think it would be good to have a project of packaging type wsdl and then have consumer projects depend on that artifact. Has anybody tried to do this or is there a better pattern for doing this? I found one reference on the web about this : http://myarch.com/using-maven-repository-as-web-services-registry Possibly the hard part would be integrating with existing wsdl2java plugins that expect a file path to the WSDL file. I would guess that I would have to customize one to automatically grab depencies of type wsdl and then pass them to the code generator. Peter Hayes http://www.linkedin.com/in/petehayes Architecture Shared Technology Services | Fidelity Investments Management Technology - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: URL encoding issues on Windows platform
You'll probably get better traction on this issue by talking to the JBoss Microcontainer guys, considering this sounds like a bug in their code. Since you're on Windows, you could also use subst to point c:\documents...\.m2 to another drive, say G:\, which has no spaces. Then configure settings.xml to use G:\ for your repo. I don't see this as being particularly drastic. Wayne On Thu, Oct 9, 2008 at 8:40 AM, stug23 [EMAIL PROTECTED] wrote: One of our developers is using the exec:java plugin to launch a Java application. Within the application the JBoss Microcontainer is used and a java.net.MalformedURLException occurs. Apparently this is a known problem: http://web.aanet.com.au/persabi/andromda/faq.html#MalformedURLException_with_Tests However the workaround recommended in the reference above is to move the local .m2 repo to a directory with no spaces in the pathname. This seems like a drastic approach to me. Does anyone here know of a way to use Spring and the JBoss Microcontainer on a Windows platform without having to move the .m2 repo? TIA -- View this message in context: http://www.nabble.com/URL-encoding-issues-on-Windows-platform-tp19901546p19901546.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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dependency SNAPSHOT problem
What does stable mean? Ultimately the only thing that matters is that you are happy for testers to test it or users to use it. Don' t jt avoid given things version because its not stable. I just version everything and only Release some versions. Not sure how big you team is but consider... you release a snapshot and your colleague is like awesome new feature really needed that... works diligently... you realise theres a mistake and fix it - or even better someone else deploys from the same project with some different changes... you collegue finds that all of the sudden hes broken... and no way to go back... you spend x minutes/hours trying to resolve what should happen next. Now add 10 people with various project interelations... its unmanageable.. you might as well use ant and build everything from source. However if you use the release plugin and release rather than deploy then your collegues can choose when to upgrade and take the integration pain. There are two approaches pessimistic with fixed versions or optimistic using ranges back to work... On Fri, 10 Oct 2008 07:58:12 Qureshi,Shahzad [Ontario] wrote: Hi all, I'm working on a module that is a dependency of our main project. I created this module as a snapshot since its currently under development as well and its not a stable version yet. I upload it to our internal remote repository, however, whenever anyone updates their dependencies they don't get the latest version of my module, the copy still remains the same as the previous version until they delete their local copy of the dependency. This is a sample of my module's pom file project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdca.abc/groupId artifactIdlist/artifactId version1.0-SNAPSHOT/version namesome List/name descriptionXMLBeans created schema jar/description /project I use mvn deploy plugin to deploy this file (its an xmlbean created jar file if anyone cares to know). And this is what I use to deploy the jar file mvn deploy:deploy-file -Durl=scp://address -DrepositoryId=repo_id -Dfile=file.jar -DpomFile=pom.xml This part seems to be working fine since it creates a new jar file on the repo with a new timestamp everytime I deploy the new verison of my jar file, however the other users can't get the latest copy. This is the sample pom file of our main project project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdca.abc/groupId artifactIdqc/artifactId packagingjar/packaging version2.0/version nameQC/name build plugins plugin artifactIdmaven-compiler-plugin/artifactId version2.0.2/version configuration source1.6/source target1.6/target /configuration /plugin /plugins /build repositories repository idrepo_id/id urlhttp://address/url /repository /repositories dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version4.3.1/version scopetest/scope /dependency dependency groupIdca.abc/groupId artifactIdlist/artifactId version1.0-SNAPSHOT/version scopecompile/scope /dependency /dependencies /project Any ideas? Or do I've the whole idea of SNAPSHOT wrong? Thank you -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Documentation woes
I don't like recommending commercial products, but you might have a try with Adobe InDesign. It does a decent job of importing Word files, especially if a word template was used (or formats or something like that; it's been awhile since I used it). Once you have it in InDesign I suspect that it will be easier to spit it back out in xml. It's been awhile since I played with InDesign so it might even be better than I remember. Mykel Alvis wrote: It seems likely that I will need to write something, having found nothing using teh interwebs so far. Thanks, Aaron and Wendy, for some direction. I may be incorrect about this, but it seems like the doxia documentation is a little sparse. During site generation I see a lot of download attempts for artifacts, templates I believe. I can't seem to locate any written docs on how one uses such things. Are there any such docs? On Thu, Oct 9, 2008 at 10:22, Aaron Metzger [EMAIL PROTECTED] wrote: Wendy Smoak wrote: On Thu, Oct 9, 2008 at 7:33 AM, Mykel Alvis [EMAIL PROTECTED] wrote: So my question is does anyone has a template or transformation tool for taking Word documents and turning them into clean XDOC? Any thoughts on this? If you end up needing to write something to do it, I wonder whether anything in Apache POI could help. Or, maybe one of the open document format processing libraries: http://www.jopendocument.org/ - 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: Documentation woes
I might give that a look if it's got a trial edition. Thanks! On Thu, Oct 9, 2008 at 16:35, Rusty Wright [EMAIL PROTECTED] wrote: I don't like recommending commercial products, but you might have a try with Adobe InDesign. It does a decent job of importing Word files, especially if a word template was used (or formats or something like that; it's been awhile since I used it). Once you have it in InDesign I suspect that it will be easier to spit it back out in xml. It's been awhile since I played with InDesign so it might even be better than I remember. Mykel Alvis wrote: It seems likely that I will need to write something, having found nothing using teh interwebs so far. Thanks, Aaron and Wendy, for some direction. I may be incorrect about this, but it seems like the doxia documentation is a little sparse. During site generation I see a lot of download attempts for artifacts, templates I believe. I can't seem to locate any written docs on how one uses such things. Are there any such docs? On Thu, Oct 9, 2008 at 10:22, Aaron Metzger [EMAIL PROTECTED] wrote: Wendy Smoak wrote: On Thu, Oct 9, 2008 at 7:33 AM, Mykel Alvis [EMAIL PROTECTED] wrote: So my question is does anyone has a template or transformation tool for taking Word documents and turning them into clean XDOC? Any thoughts on this? If you end up needing to write something to do it, I wonder whether anything in Apache POI could help. Or, maybe one of the open document format processing libraries: http://www.jopendocument.org/ - 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 do I exclude an xml file from a jar?
It would b ebetter to introduce the file onto the classpath for the tool through whatever plugin you are using from a different location if possible. If you must exclude it from the JAR: http://maven.apache.org/plugins/maven-jar-plugin/jar-mojo.html#excludes Cheers, Brett 2008/10/10 stug23 [EMAIL PROTECTED]: I need to have persistence.xml file on the classpath in order to perform DDL generation using the Hibernate Tool hbm2ddl. However I don't want the persistence.xml file to be included in the jar file. How can I exclude persistence.xml from the jar file even though it needs to be on the classpath earlier in the lifecycle? TIA -- View this message in context: http://www.nabble.com/How-do-I-exclude-an-xml-file-from-a-jar--tp19902363p19902363.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] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: reusing jar-with-dependencies assembly as primary artifact
Try the shade plugin instead, which has an option to be able to replace the primary artifact with the new JAR, and has other processors for merging the JAR. - Brett 2008/10/10 a.kraievoy [EMAIL PROTECTED]: Greetings, kinda simple tweak that apparently makes a lot of pain in maven. I need to use jar-with-dependencies instead of jar as *primary* artifact for 3 of 9 modules we have in our system. Anyway - the usual jar packaging is not used in the build process (for those 3 modules), only jar-with-deps, so the most natural idea is to switch jars somehow. For now I'm thinking of firing a small ant script doing exactly that immediately after package phase, so maven does not know I've hacked the jars and uses the thing I need. First - I don't like the idea to issue 'mvn install' each time I want to verify the project (as code changes from modules spill over to the local repo while subsequent modules may fail). So it would be quite fine to keep the whole project packageable w/o any local repo updates, e.g. using 'mvn package' most of the time. Thus I would like to stick to using only primary artifacts, which are visible across project siblings in 'mvn package' usecase. Attached artifacts are not visible, so if a sibling depends on jar-with-deps, and nothing is installed - then 'mvn package' would bother all the registered remote repos before failing. ...and even worse - it would silently use something stale from the local repo (!), which I am currently trying to prevent. Please remember that 'mvn install' may install something broken from a module while as some integration tests in subsequent modules would fail the whole build process. So - doing an assembly (as most samples suggest) does not fit as it generates the attached artifact (which requires that unsafe 'install' scenario). If I'm doing a custom packaging - I end up loosing a day or so tinkering with automagical maven internals which is of course a non-productive way to perform such a simple change. Any ideas, suggestions? Thanks in advance, Anton S. Kraievoy P.SOFF: We're currently migrating 1KLOC of ant code to maven. I'll try to do the same for ant + ivy and compare the experience (and leave the most convenient in charge). Looks like maven currently has vanishing chance to survive. I'll post an update on this matter in a week or two on my blog: http://java.akraievoy.org -- View this message in context: http://www.nabble.com/reusing-jar-with-dependencies-assembly-as-primary-artifact-tp19906052p19906052.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] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL as Maven artifact
On Thu, Oct 9, 2008 at 12:10 PM, Hayes, Peter [EMAIL PROTECTED] wrote: How do you end up generating the server side skeleton files? Is this done as part of the module with the WSDL? The answer is we don't - only if a developer needs the skeletons to get started with the right annotations in place for a new service, he runs it manually. I've never found them particularly useful since you need to modify them anyway. Kalle -Original Message- From: Kalle Korhonen [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2008 3:00 PM To: Maven Users List Subject: Re: WSDL as Maven artifact I think in typical cases a single WSDL is too small of a source fragment to be a build artifact. The pattern I've often followed is that I keep the wsdl and the generated client stubs in one module with an obvious packaging type jar, then use the jar both on the client and the server side. Kalle On Thu, Oct 9, 2008 at 10:02 AM, Hayes, Peter [EMAIL PROTECTED] wrote: We are building web services and in our approach multiple maven projects would be consumers of the service WSDL in order to generate their server / client stubs. I think it would be good to have a project of packaging type wsdl and then have consumer projects depend on that artifact. Has anybody tried to do this or is there a better pattern for doing this? I found one reference on the web about this : http://myarch.com/using-maven-repository-as-web-services-registry Possibly the hard part would be integrating with existing wsdl2java plugins that expect a file path to the WSDL file. I would guess that I would have to customize one to automatically grab depencies of type wsdl and then pass them to the code generator. Peter Hayes [image: LinkedIn Profile]http://www.linkedin.com/in/petehayes Architecture Shared Technology Services | Fidelity Investments Management Technology - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: WSDL as Maven artifact
Thanks for the info. I will plan on using your process. Pete -Original Message- From: Paul [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2008 4:37 PM To: users@maven.apache.org Cc: Hayes, Peter Subject: Re: WSDL as Maven artifact I second Kalle about the fact that wsdl are too small entities to elect them artifacts. In my current project I keep the wsdl in the service implementation artifact and I package the wsdl with clients stubs in another artifact. The client artifact being built with the following sequence : unpack the wsdl from the service artifact using maven-dependency-plugin and then generate the client stubs with the appropriate maven plugin. Paul Le Thursday 09 October 2008 19:02:45 Hayes, Peter, vous avez écrit : We are building web services and in our approach multiple maven projects would be consumers of the service WSDL in order to generate their server / client stubs. I think it would be good to have a project of packaging type wsdl and then have consumer projects depend on that artifact. Has anybody tried to do this or is there a better pattern for doing this? I found one reference on the web about this : http://myarch.com/using-maven-repository-as-web-services-registry Possibly the hard part would be integrating with existing wsdl2java plugins that expect a file path to the WSDL file. I would guess that I would have to customize one to automatically grab depencies of type wsdl and then pass them to the code generator. Peter Hayes http://www.linkedin.com/in/petehayes Architecture Shared Technology Services | Fidelity Investments Management Technology - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: URL encoding issues on Windows platform
whitespace characters play havoc with Windows based File Systems the OS delivers back a 8.3 shortened name which you can use e.g. C:\DOCUME~1\ADMINI~1\.m2 HTH Martin __ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. Date: Thu, 9 Oct 2008 08:40:06 -0700 From: [EMAIL PROTECTED] To: users@maven.apache.org Subject: URL encoding issues on Windows platform One of our developers is using the exec:java plugin to launch a Java application. Within the application the JBoss Microcontainer is used and a java.net.MalformedURLException occurs. Apparently this is a known problem: http://web.aanet.com.au/persabi/andromda/faq.html#MalformedURLException_with_Tests However the workaround recommended in the reference above is to move the local .m2 repo to a directory with no spaces in the pathname. This seems like a drastic approach to me. Does anyone here know of a way to use Spring and the JBoss Microcontainer on a Windows platform without having to move the .m2 repo? TIA -- View this message in context: http://www.nabble.com/URL-encoding-issues-on-Windows-platform-tp19901546p19901546.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] _ See how Windows connects the people, information, and fun that are part of your life. http://clk.atdmt.com/MRT/go/msnnkwxp1020093175mrt/direct/01/
