Way to customize file names in archetypes?
Is there any way to customize the names of the files generated by an archetype? eg I would like to generate a shell file that is installed by the project and naturally this shell file should be named according to one of the archetype properties... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Adding/updating archetype automatically to catalog?
I wonder if there is any standard way of automatically updating the archetype catalog when deploying/releasing an archetype? We are using nexus and continuum, but first of all I see no archetype catalog at all on the nexus public repo? Do you have to create it manually? Is there any way of automatic this in a nice way? we will be creating several archetypes, probably releasing new versions etc - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to keep the original file name during installation/deployment?
I know maven is quite java centric, but I assume there should be some
strategy for handling this type of problem in the maven way?
What would be the proper way for accomplishing this in maven?
2009/3/12 Wayne Fay wayne...@gmail.com
As you can see, the file group-project-2.3.0.1-16287.noarch.rpm is
installed as project-2.3.0-1.rpm. Is there a way to prevent this, ie.
keep the original file name?
I'm not aware of any way to force Maven to install into a repo using
the finalName you've defined. There are a lot of good reasons for
this.
If you require this naming you've suggested above, the -16287 part
belongs in your version tag, and the noarch bit belongs in the
classifier. Then Maven will install this file as:
${project.artifactId}-${project.version}-${project.classifier}.rpm
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Kent Närling
System Architect
SEAMLESS
Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden
Phone: +46 8 5648 7800, fax: +46 8 5648 7823
Mobile: +46 70 836 9925
Mail: kent.narl...@seamless.se
www.seamless.se
Anyone? Snapshots repositories, how should they work?
Anyone give me a pointer regarding this? please? Is it a very stupid question... ? :-( -- Forwarded message -- From: Kent Närling kent.narl...@seamless.se Date: 2009/2/11 Subject: Snapshots repositories, how should they work? To: Maven Users List users@maven.apache.org This might be a newbie question, bit I have tried to find documentation explaining how snapshot repositories should work... can anyone give me a pointer? We have an internal repository (nexus) and a build server (continuum) which works fine with released artifacts etc However I cannot get automatic download of snapshot dependencies to work successfully...? I have added a snapshot-enabled repository to my settings and it does try to download it, but it seems it gets the timestamp/build number incorrect all the time! For instance, I can see that maven is trying to download: Downloading: http://nexus:8081/nexus/content/groups/public-snapshots/com.my.common/poms/my-artifact-0.11-20090211.000500-295.pom But when I check the repo manually, the latest snapshot was actually named: http://nexus:8081/nexus/content/groups/public-snapshots/com.my.common/poms/my-artifact-0.11-20090211.000348-293.pom What am I doing wrong? -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: kent.narl...@seamless.se www.seamless.se
Re: Anyone? Snapshots repositories, how should they work?
I thought legacy layout was standard for snapshot repositories? Is it even possible to use non-legacy layout for snapshots? And it does try to use the correct path, it is just the timestamp/buildnumber that mismatch...? 2009/2/16 Nick Stolwijk nick.stolw...@gmail.com http://nexus:8081/nexus/content/groups/public-snapshots/com.my.common/poms/my-artifact-0.11-20090211.000348-293.pom Seeing you have a special directory for poms it looks like you have a legacy repository defined. Maybe that goes wrong? Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Mon, Feb 16, 2009 at 5:44 PM, Kent Närling kent.narl...@seamless.se wrote: Anyone give me a pointer regarding this? please? Is it a very stupid question... ? :-( -- Forwarded message -- From: Kent Närling kent.narl...@seamless.se Date: 2009/2/11 Subject: Snapshots repositories, how should they work? To: Maven Users List users@maven.apache.org This might be a newbie question, bit I have tried to find documentation explaining how snapshot repositories should work... can anyone give me a pointer? We have an internal repository (nexus) and a build server (continuum) which works fine with released artifacts etc However I cannot get automatic download of snapshot dependencies to work successfully...? I have added a snapshot-enabled repository to my settings and it does try to download it, but it seems it gets the timestamp/build number incorrect all the time! For instance, I can see that maven is trying to download: Downloading: http://nexus:8081/nexus/content/groups/public-snapshots/com.my.common/poms/my-artifact-0.11-20090211.000500-295.pom But when I check the repo manually, the latest snapshot was actually named: http://nexus:8081/nexus/content/groups/public-snapshots/com.my.common/poms/my-artifact-0.11-20090211.000348-293.pom What am I doing wrong? -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: kent.narl...@seamless.se www.seamless.se - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: kent.narl...@seamless.se www.seamless.se
Re: Anyone? Snapshots repositories, how should they work?
Ok, funny enough, I have set the format in nexus to maven2, but it still insists on storing it in legacy format... strange... Could this be a bug in nexus? we are using an older beta version ... The meta data file very correctly says the incorrect build number and timestamp: versioning - snapshot timestamp20090213.090140/timestamp buildNumber303/buildNumber /snapshot - versions version1.1-SNAPSHOT/version version4.2.2-SNAPSHOT/version It seems this timestamp buildnumber refers to another artifact in the same directory?!? I can see why the legacy format is messed up... :-( 2009/2/16 Nick Stolwijk nick.stolw...@gmail.com Legacy layout is the maven 1 layout. If you only use maven 2, don't use the legacy layout. I guess something goes wrong with your metadata. If you use a maven 2 layout like maven[1] there will be a metadata file, to construct the final url. What does your metadata file say about your snapshots? [1] http://repository.sonatype.org/content/repositories/apache-snapshots/org/apache/maven/maven/2.0.10-SNAPSHOT/maven-metadata.xml With regards, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Mon, Feb 16, 2009 at 6:03 PM, Kent Närling kent.narl...@seamless.se wrote: I thought legacy layout was standard for snapshot repositories? Is it even possible to use non-legacy layout for snapshots? And it does try to use the correct path, it is just the timestamp/buildnumber that mismatch...? 2009/2/16 Nick Stolwijk nick.stolw...@gmail.com http://nexus:8081/nexus/content/groups/public-snapshots/com.my.common/poms/my-artifact-0.11-20090211.000348-293.pom Seeing you have a special directory for poms it looks like you have a legacy repository defined. Maybe that goes wrong? Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Mon, Feb 16, 2009 at 5:44 PM, Kent Närling kent.narl...@seamless.se wrote: Anyone give me a pointer regarding this? please? Is it a very stupid question... ? :-( -- Forwarded message -- From: Kent Närling kent.narl...@seamless.se Date: 2009/2/11 Subject: Snapshots repositories, how should they work? To: Maven Users List users@maven.apache.org This might be a newbie question, bit I have tried to find documentation explaining how snapshot repositories should work... can anyone give me a pointer? We have an internal repository (nexus) and a build server (continuum) which works fine with released artifacts etc However I cannot get automatic download of snapshot dependencies to work successfully...? I have added a snapshot-enabled repository to my settings and it does try to download it, but it seems it gets the timestamp/build number incorrect all the time! For instance, I can see that maven is trying to download: Downloading: http://nexus:8081/nexus/content/groups/public-snapshots/com.my.common/poms/my-artifact-0.11-20090211.000500-295.pom But when I check the repo manually, the latest snapshot was actually named: http://nexus:8081/nexus/content/groups/public-snapshots/com.my.common/poms/my-artifact-0.11-20090211.000348-293.pom What am I doing wrong? -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: kent.narl...@seamless.se www.seamless.se - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: kent.narl...@seamless.se www.seamless.se - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: kent.narl...@seamless.se www.seamless.se
Snapshots repositories, how should they work?
This might be a newbie question, bit I have tried to find documentation explaining how snapshot repositories should work... can anyone give me a pointer? We have an internal repository (nexus) and a build server (continuum) which works fine with released artifacts etc However I cannot get automatic download of snapshot dependencies to work successfully...? I have added a snapshot-enabled repository to my settings and it does try to download it, but it seems it gets the timestamp/build number incorrect all the time! For instance, I can see that maven is trying to download: Downloading: http://nexus:8081/nexus/content/groups/public-snapshots/com.my.common/poms/my-artifact-0.11-20090211.000500-295.pom But when I check the repo manually, the latest snapshot was actually named: http://nexus:8081/nexus/content/groups/public-snapshots/com.my.common/poms/my-artifact-0.11-20090211.000348-293.pom What am I doing wrong?
Adding pre-release steps...?
Just asking to see if anyone wanted to do the same and hints about the best way of doing this: I would like to add some simple standard pre-validation steps before making a release of any project in the company. For instance checking that some standard files (release notes, etc) are present and up-to-date etc What is the best way to achieve this? Adding standard configuration for the release plugin in the root parent project? We are running continuum and invoice the release plugin there, which is working nicely so I don't want to change any of that behaviour, just want to add this behaviour... Grateful for any pointers or if there is stuff others did in this area etc :-)
Re: Adding pre-release steps...?
That was what I was planning, which is easy enough for me, just wanted to check before that this was the best way... thanks! :-) Will this configuration setting be inherited even if I change other parts of the configuration in the inherited projects? or will they then override this with the default empty list (removing my called plugins)? //Kent 2009/1/26 Edelson, Justin justin.edel...@mtvstaff.com Write plugins to perform your validation and add them to the preparationGoals of the release plugin. Justin On Jan 26, 2009, at 7:12 AM, Kent Närling kent.narl...@seamless.se wrote: Just asking to see if anyone wanted to do the same and hints about the best way of doing this: I would like to add some simple standard pre-validation steps before making a release of any project in the company. For instance checking that some standard files (release notes, etc) are present and up-to-date etc What is the best way to achieve this? Adding standard configuration for the release plugin in the root parent project? We are running continuum and invoice the release plugin there, which is working nicely so I don't want to change any of that behaviour, just want to add this behaviour... Grateful for any pointers or if there is stuff others did in this area etc :-) -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: kent.narl...@seamless.se www.seamless.se
Re: Sharing (big) parts of source across projects
What is the reason for the heavy part for the full featured? More functionality? it has an UI? It seems you probably might to create something like: - myproject - myproject-common (jar) - myproject-heavy (jar) - myproject-webservices (war) 2009/1/26 Yves Dessertine yvesd.pub...@gmail.com 2009/1/26 Geoffrey Wiseman geoffrey.wise...@gmail.com: The WAR is your web services? What do you use the JAR for? Based on the limited understanding I have of your project, I'd say that basically, you want: myproject (pom project, no real implementation other than the two modules) - myproject-jar -- whatever this project is for; common? library? domain? JAR packaging. - myproject-web-services -- depends on myproject-jar as a JAR, WAR packaging. Thank you Geoffrey for your answer. Yes, that's what I want. It now compiles, thank you. The WAR contains the web services, and the JAR is a common lib, that we need to distribute. But, a new problem now pops up : can we build two versions of the JAR ? One light version to use with the Web services, and another, heavy version to distribute and full-featured ? While it works as it's now, the JAR included in the war, is much more heavy than before (where an Ant task picked up a few files to generate the lightweight jar). The few files are shared across the lightweight and the heavy jar... What to do now ? Put them in a seperate sub project ? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: kent.narl...@seamless.se www.seamless.se
Re: Getting log4j output from ANT tasks to maven output
I assume you mean to the console when you run maven on the command line, or? The default behaviour of maven is to just write to stdout, so if you configure the log4j file to do so as well, then if you just configure a CONSOLE appender in log4j your should get what you want? 2009/1/22 ez ere...@gmail.com Well, I havn't.. So, i should just place log4j.properties file? how will i make it redirect all logs to maven output? Jaikiran wrote: ez wrote: instead i get this: log4j:WARN No appenders could be found for logger (com.i18n.Excel2Properties). log4j:WARN Please initialize the log4j system properly. The warning is because the log4j.properties or log4j.xml is not present in the classpath. Where have you placed it? -- View this message in context: http://www.nabble.com/Getting-log4j-output-from-ANT-tasks-to-maven-output-tp21558678p21609797.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: kent.narl...@seamless.se www.seamless.se
Re: How to import multi-module projects in Eclipse through mvn eclipse:eclipse
If you want to do this, why not use one of the maven eclipse plugins? At least I know m2eclipse supports this very nicely... 2009/1/23 Jaikiran jai_forums2...@yahoo.co.in I have a multiple module project with this parent pom containing this: modulemyappone/module modulemyapptwo/module The myappone and myapptwo have their own poms and are jar artifacts. From the top level parent i do a mvn eclipse:clean eclipse:eclipse And then from Eclipse (which does not have any plugins) i do a File - Import - Top level Project. At this point, i expected to see myappone and myapptwo availble for selection, in the list of projects to be selected. But i only see the top level parent in the selection. When i import this top level project, the child modules myappone and myapptwo are imported as resources for the top level project. As a result, whenever i want to traverse between the java classes of these projects (the F3 way) i get a pop-up saying (The resource is not in build path). Is there a way through which i can import these child projects as java projects all at once from the top level instead of having to import them one at a time? -- View this message in context: http://www.nabble.com/How-to-import-multi-module-projects-in-Eclipse-through-mvn-eclipse%3Aeclipse-tp21621731p21621731.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: kent.narl...@seamless.se www.seamless.se
Re: How can maven be used in a continuous integration situation?
Well, first of all, maybe you should get a CI server? (unless you have one?)I would recommend continuum (http://continuum.apache.org)http://continuum.apache.org/ at least to get started and then things will probably clear up... No, usually the CI server does not generate releases every night, it usually does deploy (but this is configurable in continuum) on the project which will uploade the snapshot to the snapshot repository. A remark, here: continuuum only generates a build if there are any changes... and it checks for changes regularly (by default hourly) 2008/12/4 Matthew Jaskula mjask...@nyx.com Are you suggesting that our CI server performs a 'mvn release' nightly? From the documentation that you linked to it seems like this is not intended to be an automated process, as there are several steps that prompt the user for information. I assume that you can provide this information on the command line? Regardless of this issue, what is standard practice in this situation? We want a CI server to use maven to produce regular versioned builds of a project that is a dependency of other projects. Is there something about this that doesn't fin in the maven philosophy? Thanks. Matthew Jaskula t +1 212.542.8299 From: Wayne Fay wayne...@gmail.com Reply-To: Maven Users List users@maven.apache.org Date: Wed, 3 Dec 2008 16:35:01 -0800 To: Maven Users List users@maven.apache.org Subject: Re: How can maven be used in a continuous integration situation? The problem with this method is that the maven install plugin only uses the version in the pom file, not the version passed in on the command line. This is noted in [this maven issue][1]. If you use mvn release rather than simply mvn install, this is handled for you via the release plugin. Since you are literally cutting a release, I think this is appropriate anyway. mvn install only installs the artifacts in the local repo cache. mvn release does a lot more. You probably want to use the batch mode: http://maven.apache.org/plugins/maven-release-plugin/howto.html Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Visit our website at http://www.nyse.com Note: The information contained in this message and any attachment to it is privileged, confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to the message, and please delete it from your system. Thank you. NYSE Euronext, Inc. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: kent.narl...@seamless.se www.seamless.se
Out of memory using docbkx plugin?
When I try to build some of our project using the docbkx docbook plugin, I get the following out of memory exception: INFO] Trace java.lang.OutOfMemoryError: Java heap space at org.apache.fop.image.ImageIOImage.loadBitmap(ImageIOImage.java:183) at org.apache.fop.image.ImageIOImage.loadDimensions(ImageIOImage.java:68) at org.apache.fop.image.AbstractFopImage.load(AbstractFopImage.java:161) at org.apache.fop.fo.properties.CommonBorderPaddingBackground.init(CommonBorderPaddingBackground.java:172) at org.apache.fop.fo.PropertyList.getBorderPaddingBackgroundProps(PropertyList.java:577) at org.apache.fop.fo.pagination.Region.bind(Region.java:64) at org.apache.fop.fo.pagination.RegionBody.bind(RegionBody.java:56) at org.apache.fop.fo.FObj.processNode(FObj.java:125) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.java:320) at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:185) at org.apache.xalan.transformer.TransformerIdentityImpl.startElement(TransformerIdentityImpl.java:1072) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:484) at com.agilejava.docbkx.maven.AbstractPdfMojo.postProcessResult(AbstractPdfMojo.java:85) at com.agilejava.docbkx.maven.AbstractTransformerMojo.execute(AbstractTransformerMojo.java:174) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) It only occurs when I build the docbook pdf files, anyone know why this happens? Also, it does go away if I increase the heap space to 1,5 Mb, but that is hard to change in all environments etc...
Re: Running selective reports causes site/index.html to dissapear?!?
2008/12/16 Jörg Schaible joerg.schai...@gmx.de Hi Kent, Kent Närling wrote at Dienstag, 16. Dezember 2008 13:14: I am trying to customize the site generation and only want to generate selected reports... however when I do this as described in the examples: plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId reportSets reportSet reports reportdependencies/report reportproject-team/report reportmailing-list/report reportcim/report reportissue-tracking/report reportlicense/report reportscm/report /reports /reportSet /reportSets /plugin Then suddenly target/site/index.html is not generated anymore!?! why? You did not select the index report ;-) Right, I knew that ... *argh* Sorry for the troll question... :-(
Trying to deploy site...
I am trying to deploy a project site, but it seems that the deployment possibilities are very limited? eg. I am trying this: distributionManagement site idproject-site/id urlscp://localhost/home/admin/test/url /site /distributionManagement But then I get: Embedded error: The host was not known and was not accepted by the configuration: localhost reject HostKey: localhost It doesn't accept localhost?? why?? Also, I would actually like to be able to use another port (than 22) is this even possible? The documentation regarding the distribution options/protocols seems almost non-existant, or?
Re: Trying to deploy site...
So, you are saying that only signature/key-based SSH works with deployment? not simply username+password? (that was what I tried) I do make site-stage too, just wanted to test the first deployment against a port-forwarded port to another host ... //Kent 2008/12/16 Mick Knutson mickknut...@gmail.com scp is using ssh so you need a key generated. If you are building and deploying locally, try to just stage the site to the directory you want. site-stage --- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://baselogic.com Linked IN: http://linkedin.com/in/mickknutson Vacation Rental: http://tahoe.baselogic.com --- On Tue, Dec 16, 2008 at 10:05 AM, Kent Närling kent.narl...@seamless.se wrote: I am trying to deploy a project site, but it seems that the deployment possibilities are very limited? eg. I am trying this: distributionManagement site idproject-site/id urlscp://localhost/home/admin/test/url /site /distributionManagement But then I get: Embedded error: The host was not known and was not accepted by the configuration: localhost reject HostKey: localhost It doesn't accept localhost?? why?? Also, I would actually like to be able to use another port (than 22) is this even possible? The documentation regarding the distribution options/protocols seems almost non-existant, or? -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: kent.narl...@seamless.se www.seamless.se
Running selective reports causes site/index.html to dissapear?!?
I am trying to customize the site generation and only want to generate selected reports... however when I do this as described in the examples: plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId reportSets reportSet reports reportdependencies/report reportproject-team/report reportmailing-list/report reportcim/report reportissue-tracking/report reportlicense/report reportscm/report /reports /reportSet /reportSets /plugin Then suddenly target/site/index.html is not generated anymore!?! why? Also, the documentation for site.xml is very brief, is there any good reference description on all available elements in site.xml etc
Re: Not happy with maven
MAVEN REPOSITORY AS ONLY SOURCE OF DEPENDENCIES I don't see the big issue here , as others have pointed out you can solve this with a system scope. On the other hand, setting up your own repository is actually very simple and gives a lot of advantages (like proper version tracking of the dependencies etc) ORDER OF TASKS I do agree that the logic of maven is sometimes unclear in this regard (and others), however this is a type of problem common to many tools. Also, as others have said, a simple antun task solves your example problem quite nicely. TOO SLOW Yes, if you use it in the way you described then I agree that it will be slow. On the other hand, if you use a sensible IDE like Eclipse or Netbeans, the test cycle you describe will be MUCH shorter than ANY build tool! (you never have to build just to test run) If you don't want to use these nice IDE:s, then you really want to do it in your specific way and then I definitely think maven is a bad pick for you. We use Eclipse and then maven is simply the build tool when we run a FULL build, either manually or in the build server. SECURITY CONCERNS for every artifact Maven wants to download or update. So a malicious repository could introduce malicious artifacts into my local repository, affecting all my other projects as well. Well, if you use the public repositories directly then you decide to trust them and then I guess you have to accept that. One option I guess is to set up your own repository as the ONLY repository and them set it to mirror the central repositories selectively. Nexus has a lot of configuration options regarding this at least. Naturally this would require some work, but if you want to use open-source components in your code, then you will have this problem anyway and either have to accept it or manually manage and validate your repository . JNI ISSUES In some cases I use libraries which employ JNI, or write JNI code myself. Mavens lack of cross-compiler support severely limits the development of JNI builds. Installing third party JNI artifacts in the repository in such a way that they can be loaded seems difficult work at best, if possible at all. Probably native libs would have to be copied to some library dir from where they could be loaded. The fact that the install:install-file mojo doesn't seem able to attach additional artifacts further complicates issues, as I would need one POM per os/arch combination, instead of a classifier. It is interesting that noone here has commented this so far? I am no expert in this area (but we will need to look more at non-java compilation soon), however I get the feeling that the non-java support in maven is a bit less mature than the java side (for natural reasons maybe). However AFAIK this should not be a problem with the maven architecture, but more likely lack of plugins(mature) for the different aspects? The dependencies and compilation should be solvable using classifiers and profiles quite nicely? anyone more experienced care to comment on this? it is an interesting problem... DOM STRUCTURE Again interesting that this has not been commented by others yet. I personally don't see the huge contradiction/ambiguity that you describe, yes the POM IS wide, but that is something that is pretty obvious from the scope of maven. plugins. Foremost among these I would count file encoding. Why do I need I definitely see a point here, but this is a detail that should be fairly easy and sensible to fix in future versions of maven? EXTENDING MAVEN Many things in maven can be solved by writing your own plugins. I don't like the plugin interface at all, though, especially the way I have to say I like that it is VERY easy to get started writing your own plugin, something that is not true for many other frameworks... I do agree to your points regarding configuration and I hope your points regarding this are taken as feedback for future versions as they are very specific and constructive. DOCUMENTATION Maven documentation is difficult to find and to read. Help pages for mojos consist mostly of machine-generated text, with often only a single sentence of less about the role of each parameter. Most maven generated project pages provide little information distributed over many pages. Amen to this! I like maven a lot and have a lot of gratitute for the people writing plugins etc but if it is one thing that is constantly frustrating is that the documentation many times is lacking/confusing/hard to find etc etc Granted, this IS a very common for many open-source projects, but given the talent in the maven community and the efforts that have been attempted in standardizing plugin documentation etc it is a pity. It is particularly frustrating when you find a nice and relatively mature plugin that HAS some documentation but it is very hard to find without searching forums for links to it etc (eg docbkx plugin here)
Possible to resolve non-java dependencies using maven dependencies?
Is it possible to resolve non-java dependencies using maven dependencies? For example, if one project has XSD:s that depends on XSD:s in other projects? I can obviously declare the dependent XSD as an artifact with a classifier and then depend on it so that part is pretty natural. However, how do I then declare it in the XSD referring to it? And I might also want this to work inside Eclipse etc... Maybe there a way for the dependencies to put the dependent files in a well defined place under target/ however you naturally want to avoid a statement like ../../target/... bla bla inside your XSD... ? And this does not only apply to XSD:s... for instance we would like to have some DTD:s for docbook files available for grammar verification in the editors etc and inputting the proper internet URL makes the build slooow... and makes it not work offline...
Fallback strategy for buildnumber plugin?
Anyone knows if there is a way to configure a fallback strategy for the buildnumber plugin when a project is not yet in the SCM? The background is this: It makes sense to add a company wide buildnumber strategy to the company POM, ok? However if you create a new project you might want to be able to build it before adding it to the SCM? Right now (if you use the company POM) this will fail since the buildnumber plugin fails if it is not is added to the SCM (at least with SVN)
What is attached and not?
I have tried to find out what qualifies a result as being attached and not, but cannot find the answer? More specifically, I am using the rpm-maven-plugin, but simply fail to get the resulting rpm to be considered attached and hence uploaded to the repository when I release the project... Is it only beccause the rpm is generated into rpm/RPMS/noarch ? unfortunately it seems impossible to configure the plugin to put the rpm:s directly under target...
Anone using the rpm-maven-plugin successfully?
Is anyone using the rpm-maven-plugin to generate practical rpm:s? My colleague is quite sceptical and prefers us to call a simple rpm-generation script from maven, should I try to concinve him not to? and why? ie. what advantages/disadvantages do we have from using a proper plugin instead of a script (for ONLY generating the actual RPM)? We are already quite used to writing SPEC files so that is not an issue... Also, we did run into the little issue that the plugin only takes ONE filemode setting which it applies to both the file AND the directory!! Thanks for any advice...
More sofisticated resource filtering? extracting substrings from properties etc?
Is there anyway of doing string operations when using resource filtering?
eg. something like ${project.version?substring(0,2)} or
${project.version?replace(-,.)} ? (freemarker style here)
I ask since I want to generate an RPM spec file and then rpmbuild doesn't
like dashes (-) in the version (eg as in 0.0.1-SNAPSHOT)
But I can imagine other situation were similar situations can occur as
well...
If not, is there any other resource filtering plugin that could be used?
Re: What is the purpose of finalName? really?
2008/10/24 Jörg Schaible [EMAIL PROTECTED] Hi Kent, Kent Närling wrote: What IS really the purpose of finalName? It is used to give the resulting artifact a different name locally in your target directory. only locally? a bit limited usefulness, but ok if that is the defined purpose... Apparently, the install plugin ignores the artifact name when deploying it to the repository anyway?? Definitely. The filename is part of the Maven repository's meta data. Otherwise Maven would have no chance of pulling it from there again. Well, technically speaking... it COULD have looked in the POM file to find out which filename to look for... ;-) We would like to have a version-less filename on the artifact in the repository (the version is in the path anyway), is this possible? No. These are Maven structures. IIRC there is a possibility to inject a different implementation for the RepositoryManager (or whatever the interface is called), but I am not aware of any alternative implementation. Ok, but I was kind of hoping that we could use the maven repository as a product download repository as well, which would have been nice? (anyone else see the logic in this?) Essentially what we are looking for is to make the release process automated and standarddized with maven, including making it available to our delivery department. ie. when doing a release: - branching/taging it etc (done nicely by the relase plugin already) - uploading it to the repository for dependencies etc (done by maven nicely already) - updating a project site with product information , release notes and download links to the artifacts belonging to it (so they can grab it and install it at a customer) - sending a release mail to relevant parties with links to the updated product site, possibly with release notes etc What would be the recommended maven way to achieve this behaviour? If not, what is the real purpose of finalName if it is not used for the name of the artifact/file in the end anyway... ? You may either use the local file directly for a hot deployment on your developer machine or you can use additional plugins to process the file further. Well, that is hardly a practical solution for non-developers ... ;-)
Re: What is the purpose of finalName? really?
You may either use the local file directly for a hot deployment on your developer machine or you can use additional plugins to process the file further. To give Kent an example: Consider a pom for building a WAR. If you set finalNamemycontextpath/finalName and use e.g. the jetty plugin to start your webserver in 1 go: $ mvn package jetty:run Then your finalName is being used for 'deployment' and you may access your webapp via http://localhost:8080/mycontextpath/ Well, this is all very nice... but not so practical for creating a proper context for a production environment? Also, to make things more annoying, tomcat has a tendency to ignore symlink names and picking the actual filename (pointed to by the symlink) as context ANYWAY!?! It is possible to work around this, but it seems it gets quite messy... so our best solution so far is to make sure that the actual filename matches the desired context name...
What is the purpose of finalName? really?
What IS really the purpose of finalName? Apparently, the install plugin ignores the artifact name when deploying it to the repository anyway?? We would like to have a version-less filename on the artifact in the repository (the version is in the path anyway), is this possible? If not, what is the real purpose of finalName if it is not used for the name of the artifact/file in the end anyway... ? Best regards Kent
Re: What is the purpose of finalName? really?
Exactly what we wanted too! But when I do this, the filename in the repository gets the default name anyway!! When running it locally for instance, I get the following message: [INFO] Installing C:\Workspaces\main\requestparser\requestparser-servlet\target\requestparser-servletxx.war to C:\Documents and Settings\kent\.m2\repository\com\seamless\ers\requestparser-servlet\1.0rc3-SNAPSHOT\requestparser-servlet-1.0rc3-SNAPSHOT.war ie, it seems the install plugin simply ignores the finalName tag?!? I mean, obviously it is nice to have a war file have a fixed name since it usually dictates the default path to the context in the container and you don't want the version in that?!? Naturally it is possible to manually re-name it, but that kind of defeats the purpose of a company repository if you have to re-name the files before you use them?!? 2008/10/23 Stephen Connolly [EMAIL PROTECTED] For us we use it to ensure that the war file in target is always the same, so that other scripts we have can pick it up irrespective of the version. If you are pulling the file out of the repo, you can always specify the name to pull it out of the repo as 2008/10/23 Kent Närling [EMAIL PROTECTED] What IS really the purpose of finalName? Apparently, the install plugin ignores the artifact name when deploying it to the repository anyway?? We would like to have a version-less filename on the artifact in the repository (the version is in the path anyway), is this possible? If not, what is the real purpose of finalName if it is not used for the name of the artifact/file in the end anyway... ? Best regards Kent -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se
Re: What is the purpose of finalName? really?
Well, when our deployment team wants to install eg a new version of a component, they just download it from the repo. And they don't run maven, for them the repo is just a download server, which is kind of natural, or? Why keep another copy of all artifact versions etc? Is this a very unusual way of using a maven repo? On 23/10/2008, Stephen Connolly [EMAIL PROTECTED] wrote: But why are you pulling them from your repo by hand. When we need to get the artifact we copy it out of the local repo with either the dependencies:copy goal in a little project, or with maven ant tasks Both of these allow us to control the name. 2008/10/23 Kent Närling [EMAIL PROTECTED] Exactly what we wanted too! But when I do this, the filename in the repository gets the default name anyway!! When running it locally for instance, I get the following message: [INFO] Installing C:\Workspaces\main\requestparser\requestparser-servlet\target\requestparser-servletxx.war to C:\Documents and Settings\kent\.m2\repository\com\seamless\ers\requestparser-servlet\1.0rc3-SNAPSHOT\requestparser-servlet-1.0rc3-SNAPSHOT.war ie, it seems the install plugin simply ignores the finalName tag?!? I mean, obviously it is nice to have a war file have a fixed name since it usually dictates the default path to the context in the container and you don't want the version in that?!? Naturally it is possible to manually re-name it, but that kind of defeats the purpose of a company repository if you have to re-name the files before you use them?!? 2008/10/23 Stephen Connolly [EMAIL PROTECTED] For us we use it to ensure that the war file in target is always the same, so that other scripts we have can pick it up irrespective of the version. If you are pulling the file out of the repo, you can always specify the name to pull it out of the repo as 2008/10/23 Kent Närling [EMAIL PROTECTED] What IS really the purpose of finalName? Apparently, the install plugin ignores the artifact name when deploying it to the repository anyway?? We would like to have a version-less filename on the artifact in the repository (the version is in the path anyway), is this possible? If not, what is the real purpose of finalName if it is not used for the name of the artifact/file in the end anyway... ? Best regards Kent -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Generating changelog since last release?
Is there any simple way of generating a report of SCM changes since last release? The changelog only takes range, date or tag (which doesn't even work with svn) as types... I guess there is no way for maven guess what tag/date belongs to previous releases or even what the previous release number was? (which makes this quite hard) On the other hand, this would be a very sensible functionality to support... maybe it would be possible to store historic information in the project that plugins could use? just a thought...
Generating performance tests/reports?
Does anyone have pointers to easily generate performance reports for the tests? with historical comparisons etc? ie. similar to how the eclipse project reports etc (example: http://download.eclipse.org/eclipse/downloads/drops/R-3.4-200806172000/performance/performance.php ) Looking at the surefire documentation, it doesn't seem surefire can do this? Thanks, Kent
Re: How to use ear plugin? Am I stupid??
2008/7/23 Stefan Seidel [EMAIL PROTECTED]: Kent Närling wrote: I do understand the dependency and packaging concepts, but I failed to get it working by refering to another artifact even though i ran mvn install on the dependent artifact. (ok, it only installed it in my local repository, but that shouldn't matter?) But this is the way it is supposed to work apparently? This is the way maven in general works, what did you expect? My comment was not meant to indicate that this was a stupid way, just a confirmation that I must have misunderstood it. Sorry, my bad formulation of words. I think I see now that I forgot for a moment that it is ONLY pom projects that can have sub-projects/modules which in combination with the references to modules in the plugin docs mislead me, sorry for the troll question. In my head I was imagining an EAR project with the ejb:s, war:s etc being modules to the parent EAR project, which wouldn't have been entirely unlogical either? ;-) So, the EAR packaging is actually just an artifact packaging a bunch of other artifacts into an EAR package? Yes. Are you sure you understand what EAR means? See [0]. Again, what did you expect? The documentation for the EAR plugin describes this badly... also, what packaging types should the referred packages have? I assume jar? In a normal Enterprise Application, it is common to have at least one EJB and one WAR. Thus, the dependent projects should have packaging ejb and war, respectively. IMHO the EAR plugin doc is not perfect, but clear enough iff you know what an EAR is and what it is used for. So actually, to get you started, your EAR pom could look something like this: ... packagingear/packaging ... dependencies dependency ... typeejb/type /dependency dependency ... typewar/type /dependency ... /dependencies ... This should be all that is needed for starters. If you need to configure special things the application.xml, you can add: build plugins plugin artifactIdmaven-ear-plugin/artifactId configuration webModule ... contextRoot/myWebApp/contextRoot /webModule ... jarModule ... includeInApplicationXmltrue/includeInApplicationXml /jarModule ... /configuration /plugin /plugins /build regards, Ok, this in combination with vedanta's example makes this much clearer for me, thanks! I think a complete example project scetch (similar to yours above) would be very valuable in the plugin documentation! //Kent Stefan [0] http://en.wikipedia.org/wiki/EAR_(file_format)http://en.wikipedia.org/wiki/EAR_%28file_format%29 -- 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] -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se
Re: How to use ear plugin? Am I stupid??
I do understand the dependency and packaging concepts, but I failed to get it working by refering to another artifact even though i ran mvn install on the dependent artifact. (ok, it only installed it in my local repository, but that shouldn't matter?) But this is the way it is supposed to work apparently? So, the EAR packaging is actually just an artifact packaging a bunch of other artifacts into an EAR package? The documentation for the EAR plugin describes this badly... also, what packaging types should the referred packages have? I assume jar? //Kent 2008/7/22 Stefan Seidel [EMAIL PROTECTED]: It is really very easy, you add the artifacts you want to include in the EAR as dependencies to the pom.xml. Modules refers not to Maven modules, but to the WARs and EJB-JARs that are included in the EAR. If dependencies and packaging are relatively new for you, I recommend reading one of [0], [1] or especially [2]. Stefan [0] http://maven.apache.org/guides/introduction/introduction-to-the-pom.html [1] http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html [2] http://www.exist.com/download/BetterBuildsWithMaven.pdf Kent Närling wrote: Can anyone please enlighten me how to use the EAR plugin? The documentation is (as usual) a bit cryptic... In the documentation it almost seems like the EAR project packaging can contain sub-modules, but if I try to declare modules inside t I just get errors?!? (aggregator projects require 'pom' as packaging) But the configuration refers to modules (like ejb3 etc) ? Also each EAR module refer to groupId and artifactId, from where? I tried to build install a separate jar project and then refer to it in the EAR project, but nothing gets packaged? Please anyone give me a few pointers... Best regards, //Kent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se
How to use ear plugin? Am I stupid??
Can anyone please enlighten me how to use the EAR plugin? The documentation is (as usual) a bit cryptic... In the documentation it almost seems like the EAR project packaging can contain sub-modules, but if I try to declare modules inside t I just get errors?!? (aggregator projects require 'pom' as packaging) But the configuration refers to modules (like ejb3 etc) ? Also each EAR module refer to groupId and artifactId, from where? I tried to build install a separate jar project and then refer to it in the EAR project, but nothing gets packaged? Please anyone give me a few pointers... Best regards, //Kent
Re: Access to e.g. jboss lib
Unfortunately, it is only the JBoss 5 stuff that has proper maven repository
and projects etc... I guess it is doubtful that it is JBoss 5 he wants?
(even though it is soon to have a release candidate)
I suggest he does what we did:
1, Create a local company repository (we use nexus, completely adequate)
2, Make sure the maven settings always uses the local repository as proxy
3, Install the JBoss jar:s you need into the local repository (sugest using
the thirdparty repository id)
The JBoss jar:s can just be taken from an installed JBoss of choice
(witth the version desired)
//Kent
2008/7/5 Tim Kettler [EMAIL PROTECTED]:
What does accessing the jboss jars has to do with plugins?
Anyway, JBoss maintains an own maven repository [1] you can add to
settings.xml or pom. I don't know if the specific jars you need are
available from there, but it's worth a try.
-Tim
[1] http://repository.jboss.com/maven2/
buters schrieb:
This difficult way I want to avoid. This is difficult because I have to do
with a number of plugins. It is me circumstantially for every plugin mvn
install:install-file to execute. I want to find a better way.
Wayne Fay wrote:
The proper way to do this is to refer to the JBoss dependencies just
like any other dep, with a dependency tag.
If you can't find the specific file/version of the jar you need
already deployed in Central, then you can use mvn
install:install-file to install it into your local repo cache
directly, then add the dependency tag to add it to your project.
Wayne
On 7/5/08, buters [EMAIL PROTECTED] wrote:
Hi,
how can I access e.g. to jboss jars? I know that ${env.JBOSS_HOME} can
be
used. But how can I use this, that I don't know. What schould I insert
in
my
pom.xml?
Thanks beforehand,
best regards, buters
--
View this message in context:
http://www.nabble.com/Access-to-e.g.-jboss-lib-tp18290267p18290267.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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Kent Närling
System Architect
SEAMLESS
Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden
Phone: +46 8 5648 7800, fax: +46 8 5648 7823
Mobile: +46 70 836 9925
Mail: [EMAIL PROTECTED]
www.seamless.se
Re: Please help with assembly plugin dependency problems! :-(
Update to this one, this seems to happen if I execute the build from within the M2 plugin in eclipse only. If I run it on the command line it works fine!?! Anyone know why the plugin makes this behave differently? On the command line it also tries to download the failing POM and fails too, but it seems to ignore it then! (but not from within Eclipse) 2008/6/25 Kent Närling [EMAIL PROTECTED]: Hi, I still cannot get the assembly plugin to work properly in many situations. There are a lot of situations where a plugin/depenedency depends on something else where it works nicely for building and running since it only requires the jar. But then the assembly plugin tries to get the POM which fails! (since the known repositories doesn't have it) Yet another fresh example: Error retrieving POM of module-dependency: com.sun.xml.fastinfoset:FastInfoset:jar:1.2.2; Reason: POM 'com.sun.xml.fastinfoset:FastInfoset' not found in repository: Unable to download the artifact from any repository And this seems quite common... ? Can anyone explain why this is and enlighten me how to fix it? I am pulling out my hair trying to get this working ... :-( //Kent -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se
Re: Please help with assembly plugin dependency problems! :-(
Thanks a lot, this fixed it! :-) 2008/6/25 De Smet Ringo [EMAIL PROTECTED]: Kent, -Original Message- From: Kent Närling Sent: woensdag 25 juni 2008 10:53 To: Maven Users List Subject: Re: Please help with assembly plugin dependency problems! :-( Update to this one, this seems to happen if I execute the build from within the M2 plugin in eclipse only. If I run it on the command line it works fine!?! Anyone know why the plugin makes this behave differently? On the command line it also tries to download the failing POM and fails too, but it seems to ignore it then! (but not from within Eclipse) I also encountered problems once where a build using the m2eclipse plugin failed, while it worked on the command line. What I did was to disable the Maven Embedder in m2eclipse and select a normal Maven2 installation to use. Check the Eclipse Preferences (Window - Preferences - Maven - Installations). Ringo * Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie bevatten die vertrouwelijk is en/of beschermd door intellectuele eigendomsrechten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n). Elk gebruik van de informatie vervat in dit bericht (waaronder de volledige of gedeeltelijke reproductie of verspreiding onder elke vorm) door andere personen dan de geadresseerde(n) is verboden. Indien u dit bericht per vergissing heeft ontvangen, gelieve de afzender hiervan te verwittigen en dit bericht te verwijderen. This e-mail and any attachment thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the addressees. Any use of the information contained herein (including but not limited to total or partial reproduction or distribution in any form) by other persons than the addressees is prohibited. If you have received this e-mail in error, please notify the sender and delete its contents. Ce courriel et les annexes éventuelles peuvent contenir des informations confidentielles et/ou protégées par des droits de propriété intellectuelle. Ce message est adressé exclusivement à son (ses) destinataire(s). Toute utilisation du contenu de ce message (y compris la reproduction ou diffusion partielle ou complète sous toute forme) par une autre personne que le(s) destinataire(s) est formellement interdite. Si vous avez reçu ce message par erreur, veuillez prévenir l'expéditeur du message et en détruire le contenu. * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se
org.apache.xerces.jaxp.SAXParserFactoryImpl not found, anyone have an up-to-date view feedback on this?
I get this error when I check out one of our projects into Eclipse (with the m2 plugin), anyone know why? This project also uses jaxb2-maven-plugin to compile XSD files and then put the generated files into target/generated-sources. I have searched the forums etc on this and there is a lot of feedback, but it is all 2006 or earlier and refer to older versions of Eclipse/maven... If I refresh and manually do a build once it actually seems to work, but I have to repair the java build settings since Eclipse for some reason removed the reference to target/generated-sources (silently, which is very annoying) //Kent
Problems creating assembly for project using org.codehaus.xfire modules...
Hi, I am trying to build an assembly (with the assembly plugin) of a project using some xfire stuff, however the assembly fails with: Reason: Failed to create assembly: Error retrieving POM of module-dependency: org.codehaus.xfire:bcprov-jdk15:jar:133; Reason: POM 'org.codehaus.xfire:bcprov-jdk15' not found in repository: Unable to download the artifact from any repository Now, this seems to be since the xfire people haven't provided a POM for this artifact...but compiling the project and running it works!?! So apparently, the assembly plugin is more picky? Is there anyway to configure the assembly plugin to ignore this? I could install the module into our repository, but would like to avoid this if necessary (can easily become a lot of garbage there) Additionally, anyone know why the xfire people hasn't just added a dependency to the bouncycastle modules directly? //Kent
Re: How to make nexus work with thirdparty libraries??
Actually, I got it working if I manually added it to the dependencies... so this seems to be a bug in the M2 maven eclipse plugin, since I could not find it by browsing... Anyone have a comment on that? Apart from this I have found the m2 plugin great so far and the artifact browser is very nice! :-) //Kent 2008/6/11 Ed Hillmann [EMAIL PROTECTED]: On Tue, Jun 10, 2008 at 3:58 PM, Kent Närling [EMAIL PROTECTED] wrote: I have read the FAQ on how to upload thirdparty jars to a repository, but cannot seem to get it working? I have tried to upload the jacorb jar to our own local repository (nexus) with the command: mvn deploy:deploy-file -DgroupId=org.jacorb -DartifactId=jacorb -Dversion=2.3 -Dpackaging=jar -Dfile=jacorb.jar -Durl= http://nexus:8081/nexus/content/repositories/releases And then I have the following settings.xml: ?xml version=1.0? settings mirrors mirror idNexus/id nameNexus Public Mirror/name urlhttp://nexus:8081/nexus/content/groups/public/url mirrorOfcentral/mirrorOf /mirror /mirrors /settings But still I cannot use this artifact!! I tried searching for it using the index plugin in M2 eclipse but cannot find it (and cannot add it as a dependency either). But when I go into nexus I can easily find it when searching for artifacts in the web user interface... I also tried to upload it to repositories/thirdparty (in nexus) but no difference? Can anyone tell me what I am doing wrong? //Kent Is the releases repository defined as a member of the public group? When we've added additional repositories, we've had to make sure that we include them in the group definition if they're to be found at the group URL. Hope this helps, Ed - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se
Good (documented) JAXB compiler plugin?
Related to my previous problem with nexu, I have a problem getting the maven-jaxb-plugin (com.sun.tools.xjc.maven2), I beleive that it could be that nexus doesn't support proxy:ing repositories with legacy layout? (can anyone confirm this?) ie I get it working in my own environment by declaring : repository idjava.net/id namejava.net Maven Repository/name url https://maven-repository.dev.java.net/nonav/repository /url layoutlegacy/layout /repository In the pom, but nexus doesn't seem to be able to use this information? The only reason I used this specific jaxb compiler plugin is since this was the only one I found decent examples and configuration for. Anyone have tip:s for another good jaxb compiler plugin? (with links to documentation) The other maven-jaxb-plugin ( http://maven-plugins.sourceforge.net/maven-jaxb-plugin/) doesn't seem to work by just declaring it and the web site indicates that you have to have installed some libraries ie that maven dependencies doesn't solve this automatically which kind of defeats the whole maven idea...? //Kent
Re: How to make nexus work with thirdparty libraries??
Actually, I tried to upload this plugin manually to our nexus repository, but cannot get it to install properly... Trying the command: b-plugin\1.1mvn deploy:deploy-file -DgroupId=com.sun.tools.xjc.maven2 -DartifactId=maven-jaxb-plugin -Dversion=1.1 -Dpackaging=maven-plugin -Dfile=maven-jaxb-p lugin-1.1.jar -Durl=http://localhost:8081/nexus/content/repositories/central-DrepositoryId=central But only get the error: [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Failed to transfer file: http://localhost:8081/nexus/content/repositories/central/com/sun/tools/xjc/maven2/maven-jaxb-plugin/1.1/maven-jaxb-plugin-1.1.jar. Return code is: 401 Guess I probably use the wrong URL, but the documentation regarding which URL to specify is well, non-existing? Should it point to the nexus root? (would be logical considering you specify -DrepositoryId etc) tried this too, doesn't work... //Kent 2008/6/11 Kent Närling [EMAIL PROTECTED]: Actually, I got it working if I manually added it to the dependencies... so this seems to be a bug in the M2 maven eclipse plugin, since I could not find it by browsing... Anyone have a comment on that? Apart from this I have found the m2 plugin great so far and the artifact browser is very nice! :-) //Kent 2008/6/11 Ed Hillmann [EMAIL PROTECTED]: On Tue, Jun 10, 2008 at 3:58 PM, Kent Närling [EMAIL PROTECTED] wrote: I have read the FAQ on how to upload thirdparty jars to a repository, but cannot seem to get it working? I have tried to upload the jacorb jar to our own local repository (nexus) with the command: mvn deploy:deploy-file -DgroupId=org.jacorb -DartifactId=jacorb -Dversion=2.3 -Dpackaging=jar -Dfile=jacorb.jar -Durl= http://nexus:8081/nexus/content/repositories/releases And then I have the following settings.xml: ?xml version=1.0? settings mirrors mirror idNexus/id nameNexus Public Mirror/name urlhttp://nexus:8081/nexus/content/groups/public/url mirrorOfcentral/mirrorOf /mirror /mirrors /settings But still I cannot use this artifact!! I tried searching for it using the index plugin in M2 eclipse but cannot find it (and cannot add it as a dependency either). But when I go into nexus I can easily find it when searching for artifacts in the web user interface... I also tried to upload it to repositories/thirdparty (in nexus) but no difference? Can anyone tell me what I am doing wrong? //Kent Is the releases repository defined as a member of the public group? When we've added additional repositories, we've had to make sure that we include them in the group definition if they're to be found at the group URL. Hope this helps, Ed - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se
Re: How to make nexus work with thirdparty libraries??
Using a local repository? But then every developer has to add this to their local repository?? And it gets even more messy to get this working with automatic builds? Or do you mean that I should add another hosted repository in nexus? (usually local repository refers to the repository on your own machine?) Again, the central part was just an example, the question was more: If I have a nexus server, WHERE should I install it? http://localhost:8081/nexus/content/repositories/thirdparty -DrepositoryId=thirdpartyhttp://localhost:8081/nexus/content/repositories/central-DrepositoryId=central? (since a thirdparty hosted repository is already defined in the default nexus setup?) And by the way, why IS there a -DrepositoryId if that is part of the URL anyway? 2008/6/12 Ed Hillmann [EMAIL PROTECTED]: On Wed, Jun 11, 2008 at 4:59 PM, Kent Närling [EMAIL PROTECTED] wrote: Actually, I tried to upload this plugin manually to our nexus repository, but cannot get it to install properly... Trying the command: b-plugin\1.1mvn deploy:deploy-file -DgroupId=com.sun.tools.xjc.maven2 -DartifactId=maven-jaxb-plugin -Dversion=1.1 -Dpackaging=maven-plugin -Dfile=maven-jaxb-p lugin-1.1.jar -Durl= http://localhost:8081/nexus/content/repositories/central-DrepositoryId=central But only get the error: [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Failed to transfer file: http://localhost:8081/nexus/content/repositories/central/com/sun/tools/xjc/maven2/maven-jaxb-plugin/1.1/maven-jaxb-plugin-1.1.jar . Return code is: 401 Guess I probably use the wrong URL, but the documentation regarding which URL to specify is well, non-existing? Should it point to the nexus root? (would be logical considering you specify -DrepositoryId etc) tried this too, doesn't work... //Kent So, you are trying to deploy an artifact to your mirror of central? I don't know if you can do that or not. But taking an uneducated guess I'd think you couldn't do that. Wouldn't you be better off having a local repository called third.party and use that as repository of third party artifacts that are manually deployed to your Nexus server? Then, you can include the third.party repository in the public group and it's available. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se
How to make nexus work with thirdparty libraries??
I have read the FAQ on how to upload thirdparty jars to a repository, but cannot seem to get it working? I have tried to upload the jacorb jar to our own local repository (nexus) with the command: mvn deploy:deploy-file -DgroupId=org.jacorb -DartifactId=jacorb -Dversion=2.3 -Dpackaging=jar -Dfile=jacorb.jar -Durl= http://nexus:8081/nexus/content/repositories/releases And then I have the following settings.xml: ?xml version=1.0? settings mirrors mirror idNexus/id nameNexus Public Mirror/name urlhttp://nexus:8081/nexus/content/groups/public/url mirrorOfcentral/mirrorOf /mirror /mirrors /settings But still I cannot use this artifact!! I tried searching for it using the index plugin in M2 eclipse but cannot find it (and cannot add it as a dependency either). But when I go into nexus I can easily find it when searching for artifacts in the web user interface... I also tried to upload it to repositories/thirdparty (in nexus) but no difference? Can anyone tell me what I am doing wrong? //Kent
Creating integration tests for a complex project...
I already wrote to ask about feedback how to organize a project (thanks for the responses so far), now another question: Let's assume we have a project like this: myproject - EAR-module1 EAR-module2 plugins plugin-module1 plugin-module2 doc tools etc And let's say the main project generates RPM:s which actually include a full bundled J2EE server (JBoss) Now, what if I would like to have integration tests that do: 1 - Install RPM:s 2 - Start J2EE server (and hence the application) 3 - Configure the application using a reference configuration (part of the integration test files) 4 - Run reference tests (already exists a test tool for this with beanshell test scripts) 5 - After all finished, stop system and un-install RPM:s How would we do this? Would the integration test simply be JUnit tests under myproject/src/test/java etc ? In that case I guess there would have to be one test (THEtest) executing an external script/tool? //Kent
Advice how to structure a project I want to move to maven...
We have a project in SVN that is made of several projects, something like this: - core - core project - common - common libraries - pluginA - pluginB ... etc - doc - for documentation) - tools - some command line tools - dist - distribution project which packages all of the above projects into one or more packages (RPM:s for instance) Most of the the projects generate jar:s, but some generate EAR:s. Now on one hand we could create a main project with modules, but that ties the modules so tightly to the main project, or? And the plugins (and future plugins) we would like to be able to give to third-party resources etc and they should not have access to most core sources etc Additionally, if we put modules in subdirectories in SVN (as recommended) it becomes more awkward to release separate versions of the modules? At the end it should be easy to build the whole project and package it, for instance automatically from within continuum for instance. Additionally, for developers it should be easy to check out all projects automatically and recursively into Eclipse... Any suggestions about the best strategy for a project like this? //Kent
Re: Advice how to structure a project I want to move to maven...
Sorry, didn't get what you mean by that? You mean dist should not be a project on its own, or? 2008/6/5 Mick Knutson [EMAIL PROTECTED]: dist should be src/assemble for assemblies. On Thu, Jun 5, 2008 at 2:41 PM, Kent Närling [EMAIL PROTECTED] wrote: We have a project in SVN that is made of several projects, something like this: - core - core project - common - common libraries - pluginA - pluginB ... etc - doc - for documentation) - tools - some command line tools - dist - distribution project which packages all of the above projects into one or more packages (RPM:s for instance) Most of the the projects generate jar:s, but some generate EAR:s. Now on one hand we could create a main project with modules, but that ties the modules so tightly to the main project, or? And the plugins (and future plugins) we would like to be able to give to third-party resources etc and they should not have access to most core sources etc Additionally, if we put modules in subdirectories in SVN (as recommended) it becomes more awkward to release separate versions of the modules? At the end it should be easy to build the whole project and package it, for instance automatically from within continuum for instance. Additionally, for developers it should be easy to check out all projects automatically and recursively into Eclipse... Any suggestions about the best strategy for a project like this? //Kent -- --- Thank You… Mick Knutson BASE Logic, inc. Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Tahoe: http://tahoe.baselogic.com -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se
Re: Advice how to structure a project I want to move to maven...
2008/6/6 Mick Knutson [EMAIL PROTECTED]: dist is usually going to be an assembly, and you add assembly descriptors into src/assemble/*.xml You do not store the rpm's or bin's there. They do not end up in svn in other words. I have: root pom.xml |--common 1..* jar's |--core |--src |--assemble |--main/resources |--site |--/xdoc/**.* (docs) |--tools |--webapps 1..* wars So common, core, tools, webapps etc would be modules of the main project? So you all seem to recommend creating a module based layout? Maybe I expressed myself a bit unclear, I never meant that the dist CONTAINED RPM:s or so! I mean that it's CREATES RPM:s etc ;-) In a module based layout like this, what if I then want to work on a module (ie a plugin etc) without having to checkout the main project? Maybe I don't even have access to it? (only the jar:s) Also, what if we would like to release a separate version of a module outside of a release? (ie a patch or a feature without having to do a release cycle for the whole product) I can only imagine that it will be a bit messy in SVN then? since the modules won't have separate trunk:s and tag:s etc? or? On Thu, Jun 5, 2008 at 3:01 PM, Kent Närling [EMAIL PROTECTED] wrote: Sorry, didn't get what you mean by that? You mean dist should not be a project on its own, or? 2008/6/5 Mick Knutson [EMAIL PROTECTED]: dist should be src/assemble for assemblies. On Thu, Jun 5, 2008 at 2:41 PM, Kent Närling [EMAIL PROTECTED] wrote: We have a project in SVN that is made of several projects, something like this: - core - core project - common - common libraries - pluginA - pluginB ... etc - doc - for documentation) - tools - some command line tools - dist - distribution project which packages all of the above projects into one or more packages (RPM:s for instance) Most of the the projects generate jar:s, but some generate EAR:s. Now on one hand we could create a main project with modules, but that ties the modules so tightly to the main project, or? And the plugins (and future plugins) we would like to be able to give to third-party resources etc and they should not have access to most core sources etc Additionally, if we put modules in subdirectories in SVN (as recommended) it becomes more awkward to release separate versions of the modules? At the end it should be easy to build the whole project and package it, for instance automatically from within continuum for instance. Additionally, for developers it should be easy to check out all projects automatically and recursively into Eclipse... Any suggestions about the best strategy for a project like this? //Kent -- --- Thank You… Mick Knutson BASE Logic, inc. Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Tahoe: http://tahoe.baselogic.com -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se -- --- Thank You… Mick Knutson BASE Logic, inc. Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Tahoe: http://tahoe.baselogic.com -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se
Re: Advice how to structure a project I want to move to maven...
Well, this is actually an J2EE project (EJB3 to be specific)... But my questions remain even for a J2EE project? 2008/6/6 Mick Knutson [EMAIL PROTECTED]: I always use multi-module, but I always am working on J2EE apps. If you want common shared projects, then split this up, but you still might have multi-modules if you are creating j2ee apps. On Thu, Jun 5, 2008 at 3:22 PM, Kent Närling [EMAIL PROTECTED] wrote: 2008/6/6 Mick Knutson [EMAIL PROTECTED]: dist is usually going to be an assembly, and you add assembly descriptors into src/assemble/*.xml You do not store the rpm's or bin's there. They do not end up in svn in other words. I have: root pom.xml |--common 1..* jar's |--core |--src |--assemble |--main/resources |--site |--/xdoc/**.* (docs) |--tools |--webapps 1..* wars So common, core, tools, webapps etc would be modules of the main project? So you all seem to recommend creating a module based layout? Maybe I expressed myself a bit unclear, I never meant that the dist CONTAINED RPM:s or so! I mean that it's CREATES RPM:s etc ;-) In a module based layout like this, what if I then want to work on a module (ie a plugin etc) without having to checkout the main project? Maybe I don't even have access to it? (only the jar:s) Also, what if we would like to release a separate version of a module outside of a release? (ie a patch or a feature without having to do a release cycle for the whole product) I can only imagine that it will be a bit messy in SVN then? since the modules won't have separate trunk:s and tag:s etc? or? On Thu, Jun 5, 2008 at 3:01 PM, Kent Närling [EMAIL PROTECTED] wrote: Sorry, didn't get what you mean by that? You mean dist should not be a project on its own, or? 2008/6/5 Mick Knutson [EMAIL PROTECTED]: dist should be src/assemble for assemblies. On Thu, Jun 5, 2008 at 2:41 PM, Kent Närling [EMAIL PROTECTED] wrote: We have a project in SVN that is made of several projects, something like this: - core - core project - common - common libraries - pluginA - pluginB ... etc - doc - for documentation) - tools - some command line tools - dist - distribution project which packages all of the above projects into one or more packages (RPM:s for instance) Most of the the projects generate jar:s, but some generate EAR:s. Now on one hand we could create a main project with modules, but that ties the modules so tightly to the main project, or? And the plugins (and future plugins) we would like to be able to give to third-party resources etc and they should not have access to most core sources etc Additionally, if we put modules in subdirectories in SVN (as recommended) it becomes more awkward to release separate versions of the modules? At the end it should be easy to build the whole project and package it, for instance automatically from within continuum for instance. Additionally, for developers it should be easy to check out all projects automatically and recursively into Eclipse... Any suggestions about the best strategy for a project like this? //Kent -- --- Thank You… Mick Knutson BASE Logic, inc. Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Tahoe: http://tahoe.baselogic.com -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se -- --- Thank You… Mick Knutson BASE Logic, inc. Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Tahoe: http://tahoe.baselogic.com -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se -- --- Thank You… Mick Knutson BASE Logic, inc. Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Tahoe: http
Re: Creating a nice application package with execution bat+sh files... problem with maven-assembly-plugin?
Actually, the include the world problem was me having a bad dependency to some stufff... :-( Does the shade plugin bundle all classes unpacked inside the jar? That usually becomes a bit clumsy... //Kent 2008/5/30 [EMAIL PROTECTED] [EMAIL PROTECTED]: Kent Närling schrieb: Hi! I would like to be able to build a self-sufficient application package from a project into a zip/tar, ie with all dependencies and a prepared scrip to execute it. I have so far tried two approches: A, Using maven-assembly-plugin and creating my own assembly file This has two problems: 1, I have set the dependency scope to runtime, but it still includes the whole world! I mean, it even includes a lot of maven jar:s! (which are obviously not necessary to run the app) 2, It becomes very inconvenient to write the script and manually updating the jar:s that should be in the classpath... :-( B, Using the Mojo appassembler-maven-plugin, but this is very buggy... it even gives me nullpointer exceptions! :-( Anyone have tips about the best we to achive this? //Kent I've not seen any problems with maven-assembly-plugin trying to include jars used only by maven plugins. Are you sure that's what is happening? Running mvn dependency:tree will show you what your projects dependencies are. You might also want to look at the maven-shade-plugin. This can generate an executable jar for a maven project, with all the necessary dependencies bundled within it; very convenient. Unfortunately while the plugin is great, the documentation is . It doesn't even mention this very important feature. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-shade-plugin/artifactId version1.1/version executions execution phasepackage/phase goals goalshade/goal /goals /execution /executions /plugin Just make sure that the manifest file has a Main-Class: ... and all works nicely. Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kent Närling System Developer SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se
Creating a nice application package with execution bat+sh files... problem with maven-assembly-plugin?
Hi! I would like to be able to build a self-sufficient application package from a project into a zip/tar, ie with all dependencies and a prepared scrip to execute it. I have so far tried two approches: A, Using maven-assembly-plugin and creating my own assembly file This has two problems: 1, I have set the dependency scope to runtime, but it still includes the whole world! I mean, it even includes a lot of maven jar:s! (which are obviously not necessary to run the app) 2, It becomes very inconvenient to write the script and manually updating the jar:s that should be in the classpath... :-( B, Using the Mojo appassembler-maven-plugin, but this is very buggy... it even gives me nullpointer exceptions! :-( Anyone have tips about the best we to achive this? //Kent
