Re: install/deploy plugin renaming assemblies?
2008/8/28 Beyer,Nathan <[EMAIL PROTECTED]>
> Would that be essentially two artifacts deployed from the same POM, then?
Sorry, I misremembered. The build-helper will only attach with the same
artifact ID but you can change the type and classifier. This makes sense
since the POM would otherwise be incorrect.
>
>
> What's the rationale for allowing a custom 'finalName' in the configuration
> of the assembly plugin, if this can't be deployed?
For local manipulation as part of the build (it is admittedly limited).
At present, deploying it to the repo in the way you're looking at would make
it inaccessible to Maven as a dependency. If that's ok, I suggest you use an
upload plugin to get it into the location you expect.
>
>
> -Nathan
>
>
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Sun 8/24/2008 11:13 PM
> To: Maven Users List
> Subject: Re: install/deploy plugin renaming assemblies?
>
> This is standard practice with the Maven repository - final name is
> never used to represent the artifact in the repository, as the
> repository path formats are pre-defined. You can alter the classifier
> it is uploaded with through the assembly configuration, but not the
> other elements. If you want to attach it with a completely different
> artifactId (service), you can do that with the build helper plugin
> instead, but note that will also change the directory it is stored in.
>
> HTH,
> Brett
>
> 2008/8/23 Beyer,Nathan <[EMAIL PROTECTED]>:
> > I have an assembly that I'm creating with a custom final name. When I run
> 'mvn clean package' the target folder contains the JAR with the correct name
> and the Zip assembly with a name the custom name. When I run 'mvn clean
> install' or 'mvn clean deploy', the Zip file is installed/deployed using the
> artifactId and the classifier from the assembly ID, instead of the name of
> the actual file. Why doesn't it use the name of the file as it is?
> >
> > Example -
> > pom.xml
> >
> >jar
> >org.example
> >library
> >1.0-SNAPSHOT
> >
> >
> >
> >org.apache.maven.plugins
> >maven-assembly-plugin
> >
> >
> >
> >single
> >
> >package
> >
> >
> >
> >service-${project.version}
> >
> >
> src/main/assembly/service-x86-win32.xml
> >
> >
> >
> >
> >
> >
> >
> > service-x86-win32.xml
> >
> >x86-win32
> >
> >zip
> >
> >false
> >
> >
> >
> ${project.build.directory}/${project.build.finalName}.jar
> >datastore.war
> >0644
> >webapps
> >
> >
> >
> >
> > This example will produce the following files in 'target'.
> > target/
> > library-1.0-SNAPSHOT.jar
> > service-1.0-SNAPSHOT-x86-win32.zip
> >
> > When deployed or installed, the files end up being
> >
> > library/
> > library-1.0-SNAPSHOT.jar
> > library-1.0-SNAPSHOT-x86-win32.zip
> >
> > --
> > CONFIDENTIALITY NOTICE This message and any included attachments are from
> Cerner Corporation and are intended only for the addressee. The information
> contained in this message is confidential and may constitute inside or
> non-public information under international, federal, or state securities
> laws. Unauthorized forwarding, printing, copying, distribution, or use of
> such information is strictly prohibited and may be unlawful. If you are not
> the addressee, please promptly delete this message and notify the sender of
> the delivery error by e-mail or you may call Cerner's corporate offices in
> Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
> >
>
>
>
> --
> 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]
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
RE: install/deploy plugin renaming assemblies?
Would that be essentially two artifacts deployed from the same POM, then?
What's the rationale for allowing a custom 'finalName' in the configuration of
the assembly plugin, if this can't be deployed?
-Nathan
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Sun 8/24/2008 11:13 PM
To: Maven Users List
Subject: Re: install/deploy plugin renaming assemblies?
This is standard practice with the Maven repository - final name is
never used to represent the artifact in the repository, as the
repository path formats are pre-defined. You can alter the classifier
it is uploaded with through the assembly configuration, but not the
other elements. If you want to attach it with a completely different
artifactId (service), you can do that with the build helper plugin
instead, but note that will also change the directory it is stored in.
HTH,
Brett
2008/8/23 Beyer,Nathan <[EMAIL PROTECTED]>:
> I have an assembly that I'm creating with a custom final name. When I run
> 'mvn clean package' the target folder contains the JAR with the correct name
> and the Zip assembly with a name the custom name. When I run 'mvn clean
> install' or 'mvn clean deploy', the Zip file is installed/deployed using the
> artifactId and the classifier from the assembly ID, instead of the name of
> the actual file. Why doesn't it use the name of the file as it is?
>
> Example -
> pom.xml
>
>jar
>org.example
>library
>1.0-SNAPSHOT
>
>
>
>org.apache.maven.plugins
>maven-assembly-plugin
>
>
>
>single
>
>package
>
>
>
>service-${project.version}
>
>
> src/main/assembly/service-x86-win32.xml
>
>
>
>
>
>
>
> service-x86-win32.xml
>
>x86-win32
>
>zip
>
>false
>
>
>
> ${project.build.directory}/${project.build.finalName}.jar
>datastore.war
>0644
>webapps
>
>
>
>
> This example will produce the following files in 'target'.
> target/
> library-1.0-SNAPSHOT.jar
> service-1.0-SNAPSHOT-x86-win32.zip
>
> When deployed or installed, the files end up being
>
> library/
> library-1.0-SNAPSHOT.jar
> library-1.0-SNAPSHOT-x86-win32.zip
>
> --
> CONFIDENTIALITY NOTICE This message and any included attachments are from
> Cerner Corporation and are intended only for the addressee. The information
> contained in this message is confidential and may constitute inside or
> non-public information under international, federal, or state securities
> laws. Unauthorized forwarding, printing, copying, distribution, or use of
> such information is strictly prohibited and may be unlawful. If you are not
> the addressee, please promptly delete this message and notify the sender of
> the delivery error by e-mail or you may call Cerner's corporate offices in
> Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
>
--
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: install/deploy plugin renaming assemblies?
This is standard practice with the Maven repository - final name is
never used to represent the artifact in the repository, as the
repository path formats are pre-defined. You can alter the classifier
it is uploaded with through the assembly configuration, but not the
other elements. If you want to attach it with a completely different
artifactId (service), you can do that with the build helper plugin
instead, but note that will also change the directory it is stored in.
HTH,
Brett
2008/8/23 Beyer,Nathan <[EMAIL PROTECTED]>:
> I have an assembly that I'm creating with a custom final name. When I run
> 'mvn clean package' the target folder contains the JAR with the correct name
> and the Zip assembly with a name the custom name. When I run 'mvn clean
> install' or 'mvn clean deploy', the Zip file is installed/deployed using the
> artifactId and the classifier from the assembly ID, instead of the name of
> the actual file. Why doesn't it use the name of the file as it is?
>
> Example -
> pom.xml
>
>jar
>org.example
>library
>1.0-SNAPSHOT
>
>
>
>org.apache.maven.plugins
>maven-assembly-plugin
>
>
>
>single
>
>package
>
>
>
>service-${project.version}
>
>
> src/main/assembly/service-x86-win32.xml
>
>
>
>
>
>
>
> service-x86-win32.xml
>
>x86-win32
>
>zip
>
>false
>
>
>
> ${project.build.directory}/${project.build.finalName}.jar
>datastore.war
>0644
>webapps
>
>
>
>
> This example will produce the following files in 'target'.
> target/
> library-1.0-SNAPSHOT.jar
> service-1.0-SNAPSHOT-x86-win32.zip
>
> When deployed or installed, the files end up being
>
> library/
> library-1.0-SNAPSHOT.jar
> library-1.0-SNAPSHOT-x86-win32.zip
>
> --
> CONFIDENTIALITY NOTICE This message and any included attachments are from
> Cerner Corporation and are intended only for the addressee. The information
> contained in this message is confidential and may constitute inside or
> non-public information under international, federal, or state securities
> laws. Unauthorized forwarding, printing, copying, distribution, or use of
> such information is strictly prohibited and may be unlawful. If you are not
> the addressee, please promptly delete this message and notify the sender of
> the delivery error by e-mail or you may call Cerner's corporate offices in
> Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
