You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Edelson, Justin" <Ju...@mtvn.com> on 2006/08/09 22:55:09 UTC

Thread about automating install/deploy

So hopefully I didn't turn off Mr. Syer entirely... but it did get me
thinking. Does Maven need a new packaging type to do what he's talking
about?

Something like this...


<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd">
	<modelVersion>4.0.0</modelVersion>
	<groupId>com.mycompany.maven</groupId>
	<artifactId>3rdparty</artifactId>
	<packaging>3rdparty</packaging>
	<name>My Company's 3rdparty Jars</name>
	<version>1.0-SNAPSHOT</version>
	<build>
		<plugins>
			<plugin>
	
<groupId>org.apache.maven.plugins</groupId>
	
<artifactId>maven-3rdparty-plugin</artifactId>
					<configuration>
						<basedir>lib</basedir>
						<jarFiles>
							<jarFile>
	
<generatePom>true</generatePom>
	
<artifactId>jconnect</artifactId>
	
<groupId>com.sybase</groupId>
	
<version>5.5.EBF11656</version>
	
<fileName>jConnect5.5.EBF11656.jar</fileName>
							</jarFile>
							<jarFile>
	
<generatePom>true</generatePom>
	
<artifactId>jai-core</artifactId>
	
<groupId>javax.media</groupId>
	
<version>1.1.2</version>
	
<fileName>jai-1.1.2/jai_core.jar</fileName>
							</jarFile>
						</jarFiles>
					</configuration>
					<extensions>true</extensions>
			</plugin>
		</plugins>
	</build>
</project>

This new packaging type is only configured for deploy and install phases
(maybe verify as well).

Thoughts?

Although I'm perfectly happy with my shell scripts, I can see the virtue
in doing this with a pom.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Thread about automating install/deploy

Posted by Brett Porter <br...@apache.org>.
Not quite sure which direction you are going here, but I'd recommend 
using the assembly plugin + its unpack goal to do this (shipping just 
the one big artifact around, and it can retain internal directory 
structure).

- Brett

On 10/08/2006 9:40 AM, Edelson, Justin wrote:
> http://www.nabble.com/Automating-install%3Ainstall-file-t2071058.html
> 
> ________________________________
> 
> From: Brett Porter [mailto:brett@apache.org]
> Sent: Wed 8/9/2006 6:35 PM
> To: Maven Developers List
> Subject: Re: Thread about automating install/deploy
> 
> 
> 
> What messages are you referring to?
> 
> On 10/08/2006 6:55 AM, Edelson, Justin wrote:
>> So hopefully I didn't turn off Mr. Syer entirely... but it did get me
>> thinking. Does Maven need a new packaging type to do what he's talking
>> about?
>>
>> Something like this...
>>
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <project xmlns="http://maven.apache.org/POM/4.0.0"
>>       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>       xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
>> http://maven.apache.org/maven-v4_0_0.xsd">
>>       <modelVersion>4.0.0</modelVersion>
>>       <groupId>com.mycompany.maven</groupId>
>>       <artifactId>3rdparty</artifactId>
>>       <packaging>3rdparty</packaging>
>>       <name>My Company's 3rdparty Jars</name>
>>       <version>1.0-SNAPSHOT</version>
>>       <build>
>>               <plugins>
>>                       <plugin>
>>      
>> <groupId>org.apache.maven.plugins</groupId>
>>      
>> <artifactId>maven-3rdparty-plugin</artifactId>
>>                                       <configuration>
>>                                               <basedir>lib</basedir>
>>                                               <jarFiles>
>>                                                       <jarFile>
>>      
>> <generatePom>true</generatePom>
>>      
>> <artifactId>jconnect</artifactId>
>>      
>> <groupId>com.sybase</groupId>
>>      
>> <version>5.5.EBF11656</version>
>>      
>> <fileName>jConnect5.5.EBF11656.jar</fileName>
>>                                                       </jarFile>
>>                                                       <jarFile>
>>      
>> <generatePom>true</generatePom>
>>      
>> <artifactId>jai-core</artifactId>
>>      
>> <groupId>javax.media</groupId>
>>      
>> <version>1.1.2</version>
>>      
>> <fileName>jai-1.1.2/jai_core.jar</fileName>
>>                                                       </jarFile>
>>                                               </jarFiles>
>>                                       </configuration>
>>                                       <extensions>true</extensions>
>>                       </plugin>
>>               </plugins>
>>       </build>
>> </project>
>>
>> This new packaging type is only configured for deploy and install phases
>> (maybe verify as well).
>>
>> Thoughts?
>>
>> Although I'm perfectly happy with my shell scripts, I can see the virtue
>> in doing this with a pom.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
> 
> 
> --
> Apache Maven - http://maven.apache.org/
> Better Builds with Maven - http://library.mergere.com/
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 
> 
> 


-- 
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


RE: Thread about automating install/deploy

Posted by "Edelson, Justin" <Ju...@mtvn.com>.
http://www.nabble.com/Automating-install%3Ainstall-file-t2071058.html

________________________________

From: Brett Porter [mailto:brett@apache.org]
Sent: Wed 8/9/2006 6:35 PM
To: Maven Developers List
Subject: Re: Thread about automating install/deploy



What messages are you referring to?

On 10/08/2006 6:55 AM, Edelson, Justin wrote:
> So hopefully I didn't turn off Mr. Syer entirely... but it did get me
> thinking. Does Maven need a new packaging type to do what he's talking
> about?
>
> Something like this...
>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <project xmlns="http://maven.apache.org/POM/4.0.0"
>       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>       xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd">
>       <modelVersion>4.0.0</modelVersion>
>       <groupId>com.mycompany.maven</groupId>
>       <artifactId>3rdparty</artifactId>
>       <packaging>3rdparty</packaging>
>       <name>My Company's 3rdparty Jars</name>
>       <version>1.0-SNAPSHOT</version>
>       <build>
>               <plugins>
>                       <plugin>
>      
> <groupId>org.apache.maven.plugins</groupId>
>      
> <artifactId>maven-3rdparty-plugin</artifactId>
>                                       <configuration>
>                                               <basedir>lib</basedir>
>                                               <jarFiles>
>                                                       <jarFile>
>      
> <generatePom>true</generatePom>
>      
> <artifactId>jconnect</artifactId>
>      
> <groupId>com.sybase</groupId>
>      
> <version>5.5.EBF11656</version>
>      
> <fileName>jConnect5.5.EBF11656.jar</fileName>
>                                                       </jarFile>
>                                                       <jarFile>
>      
> <generatePom>true</generatePom>
>      
> <artifactId>jai-core</artifactId>
>      
> <groupId>javax.media</groupId>
>      
> <version>1.1.2</version>
>      
> <fileName>jai-1.1.2/jai_core.jar</fileName>
>                                                       </jarFile>
>                                               </jarFiles>
>                                       </configuration>
>                                       <extensions>true</extensions>
>                       </plugin>
>               </plugins>
>       </build>
> </project>
>
> This new packaging type is only configured for deploy and install phases
> (maybe verify as well).
>
> Thoughts?
>
> Although I'm perfectly happy with my shell scripts, I can see the virtue
> in doing this with a pom.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>


--
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org



Re: Thread about automating install/deploy

Posted by Brett Porter <br...@apache.org>.
What messages are you referring to?

On 10/08/2006 6:55 AM, Edelson, Justin wrote:
> So hopefully I didn't turn off Mr. Syer entirely... but it did get me
> thinking. Does Maven need a new packaging type to do what he's talking
> about?
> 
> Something like this...
> 
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <project xmlns="http://maven.apache.org/POM/4.0.0"
> 	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> 	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd">
> 	<modelVersion>4.0.0</modelVersion>
> 	<groupId>com.mycompany.maven</groupId>
> 	<artifactId>3rdparty</artifactId>
> 	<packaging>3rdparty</packaging>
> 	<name>My Company's 3rdparty Jars</name>
> 	<version>1.0-SNAPSHOT</version>
> 	<build>
> 		<plugins>
> 			<plugin>
> 	
> <groupId>org.apache.maven.plugins</groupId>
> 	
> <artifactId>maven-3rdparty-plugin</artifactId>
> 					<configuration>
> 						<basedir>lib</basedir>
> 						<jarFiles>
> 							<jarFile>
> 	
> <generatePom>true</generatePom>
> 	
> <artifactId>jconnect</artifactId>
> 	
> <groupId>com.sybase</groupId>
> 	
> <version>5.5.EBF11656</version>
> 	
> <fileName>jConnect5.5.EBF11656.jar</fileName>
> 							</jarFile>
> 							<jarFile>
> 	
> <generatePom>true</generatePom>
> 	
> <artifactId>jai-core</artifactId>
> 	
> <groupId>javax.media</groupId>
> 	
> <version>1.1.2</version>
> 	
> <fileName>jai-1.1.2/jai_core.jar</fileName>
> 							</jarFile>
> 						</jarFiles>
> 					</configuration>
> 					<extensions>true</extensions>
> 			</plugin>
> 		</plugins>
> 	</build>
> </project>
> 
> This new packaging type is only configured for deploy and install phases
> (maybe verify as well).
> 
> Thoughts?
> 
> Although I'm perfectly happy with my shell scripts, I can see the virtue
> in doing this with a pom.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 


-- 
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org