You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Paul Smith <ps...@aconex.com> on 2007/06/21 04:10:01 UTC

jul-log4j-bridge distribution test

I've been tweaking the jul-log4j-bridge pom to experiment with the  
distribution mechanism, and have placed a site and repo sample here:

http://people.apache.org/~psmith/logging.apache.org/

I'm not sure why the source distribution doesn't go with it.  Any  
ideas appreciated.

Paul

Re: jul-log4j-bridge distribution test

Posted by Paul Smith <ps...@aconex.com>.
Thanks muchly!

On 21/06/2007, at 1:55 PM, Curt Arnold wrote:

>
> On Jun 20, 2007, at 9:10 PM, Paul Smith wrote:
>
>> I've been tweaking the jul-log4j-bridge pom to experiment with the  
>> distribution mechanism, and have placed a site and repo sample here:
>>
>> http://people.apache.org/~psmith/logging.apache.org/
>>
>> I'm not sure why the source distribution doesn't go with it.  Any  
>> ideas appreciated.
>>
>> Paul
>
> You need to specify a maven-source-plugin in your builds section.   
> Here is a section borrowed from the component's pom.xml.
>
>
> Index: pom.xml
> ===================================================================
> --- pom.xml	(revision 549346)
> +++ pom.xml	(working copy)
> @@ -126,6 +126,27 @@
>  					</executions>
>  				</configuration>
>  			</plugin>
> +      <plugin>
> +        <artifactId>maven-javadoc-plugin</artifactId>
> +        <executions>
> +            <execution>
> +                <goals>
> +                    <goal>jar</goal>
> +                    <goal>javadoc</goal>
> +                </goals>
> +            </execution>
> +        </executions>
> +      </plugin>
> +      <plugin>
> +        <artifactId>maven-source-plugin</artifactId>
> +        <executions>
> +            <execution>
> +                <goals>
> +                    <goal>jar</goal>
> +                </goals>
> +            </execution>
> +        </executions>
> +      </plugin>
>  		</plugins>
>  	</build>
>  	<dependencies>
>

Paul Smith
Core Engineering Manager

Aconex
The easy way to save time and money on your project

696 Bourke Street, Melbourne,
VIC 3000, Australia
Tel: +61 3 9240 0200  Fax: +61 3 9240 0299
Email: psmith@aconex.com  www.aconex.com

This email and any attachments are intended solely for the addressee.  
The contents may be privileged, confidential and/or subject to  
copyright or other applicable law. No confidentiality or privilege is  
lost by an erroneous transmission. If you have received this e-mail  
in error, please let us know by reply e-mail and delete or destroy  
this mail and all copies. If you are not the intended recipient of  
this message you must not disseminate, copy or take any action in  
reliance on it. The sender takes no responsibility for the effect of  
this message upon the recipient's computer system.




Re: jul-log4j-bridge distribution test

Posted by Curt Arnold <ca...@apache.org>.
On Jun 20, 2007, at 9:10 PM, Paul Smith wrote:

> I've been tweaking the jul-log4j-bridge pom to experiment with the  
> distribution mechanism, and have placed a site and repo sample here:
>
> http://people.apache.org/~psmith/logging.apache.org/
>
> I'm not sure why the source distribution doesn't go with it.  Any  
> ideas appreciated.
>
> Paul

You need to specify a maven-source-plugin in your builds section.   
Here is a section borrowed from the component's pom.xml.


Index: pom.xml
===================================================================
--- pom.xml	(revision 549346)
+++ pom.xml	(working copy)
@@ -126,6 +126,27 @@
  					</executions>
  				</configuration>
  			</plugin>
+      <plugin>
+        <artifactId>maven-javadoc-plugin</artifactId>
+        <executions>
+            <execution>
+                <goals>
+                    <goal>jar</goal>
+                    <goal>javadoc</goal>
+                </goals>
+            </execution>
+        </executions>
+      </plugin>
+      <plugin>
+        <artifactId>maven-source-plugin</artifactId>
+        <executions>
+            <execution>
+                <goals>
+                    <goal>jar</goal>
+                </goals>
+            </execution>
+        </executions>
+      </plugin>
  		</plugins>
  	</build>
  	<dependencies>