Re: Use assembly and deploy togeather
I tried it with this command but my problem is the created zip file does not contain the deployed jar file. It still has a -SNAPSHOT postfix which is quite ugly. On Tue, Apr 8, 2008 at 1:44 AM, Luke Daley <[EMAIL PROTECTED]> wrote: > > > On 07/04/2008, at 11:14 PM, Michael Mühlebach wrote: > > > > I want to create an assembly and deploy it but I have some troubles with > it. > > > > I tried it with the command: > > > > mvn assembly:single deploy > > > > I got almost what I expected except: All artifacts from my project, > > including the one I executed maven for, are snapshot versions! (have > > the classifier -SNAPSHOT instead of a build date and number). > > What have I done wrong or did I misunderstand the assembly/deploy build > cycle?! > > > > I am not sure exactly what you are trying to do, but if you are trying to > create another build artifact (such as a distribution zip or something) and > have it deployed along side your built jars (or whatever) then you might > want to look at the assembly:attached goal. > > http://maven.apache.org/plugins/maven-assembly-plugin/attached-mojo.html > > LD. > - > 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]
Use assembly and deploy togeather
Hello I want to create an assembly and deploy it but I have some troubles with it. I tried it with the command: mvn assembly:single deploy I got almost what I expected except: All artifacts from my project, including the one I executed maven for, are snapshot versions! (have the classifier -SNAPSHOT instead of a build date and number). What have I done wrong or did I misunderstand the assembly/deploy build cycle?! best wishes michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with assembly attached deploy
Hello I try to create an assembly with the deployed artifact in it (with the correct version number)! I used to achive this the following command: mvn assembly:single deploy What I expected is an archive which looks like this: test-project-0.1.0-20080404.140018-1.tar.gz -- test-project-0.1.0-20080404.140018-1.jar -- other files But I got instead: test-project-0.1.0-20080404.140018-1.tar.gz -- test-project-0.1.0-SNAPSHOT.jar -- other files I am not sure if it even works with assembly:single or :attached because of the build lifecycle but I do not know any other way. Has somebody a solution for this? best wishes Michael P.S. I know that the containing jar file should have no difference to the one with the correct version number. But for deployments and releases the version number is quite important and is one of the reasons why we try to use maven. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Build an Eclipse (3.3) RCP Application with Maven2
Hello I am sure this question must have been asked several times but I really searched for an answer in here as well as with google etc and found nothing sophisticating. It might be related with me being quite new in the maven world and maybe do not really know what I want to know :-) But now to my question: In our project we have a classic server client application (nothing special on server side .. pure old java with tibco for our communication). The client is an Eclipse RCP application built on version 3.3.1 which has several plugins. Here are my fist difficulties: Is the client one project in maven or a multi module project which has for each plugin a project like it is in eclipse itself? I choose the second choice because the first would end in a huge project which will make testing a pain in the *** and with the second one we can add common projects which are shared between server and client easily as plugin in the client and as jar in the server. With the maven-eclipse-plugin it works just fine with the manifest generation but I have real difficulties with the dependencies to the RCP Libraries/Plugins ... I tried the way explained on codehaus (http://docs.codehaus.org/display/MAVENUSER/Eclipse+Plugin) but it did not work :-( Is this the correct way to go and I just have to solve my last dependency problem or am I completely off? I ask this because I have seen solutions which only use the pde build which is in my opinion the wrong stage: The pde build is something for installation/deployment and should be used at the end for integration tests AFTER compilation and unit tests. Why? Unit tests should be quite fast (just several seconds) which is not possible if they depend on the pde build. I hope somebody can point me the right direction or could show me an other project with a similar build up. thanks in advance greets Michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
