You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@commons.apache.org by ni...@apache.org on 2008/01/03 14:00:26 UTC
svn commit: r608470 - /commons/proper/commons-parent/trunk/pom.xml
Author: niallp
Date: Thu Jan 3 05:00:26 2008
New Revision: 608470
URL: http://svn.apache.org/viewvc?rev=608470&view=rev
Log:
COMMONSSITE-21 - remove remote resources plugin
Modified:
commons/proper/commons-parent/trunk/pom.xml
Modified: commons/proper/commons-parent/trunk/pom.xml
URL: http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?rev=608470&r1=608469&r2=608470&view=diff
==============================================================================
--- commons/proper/commons-parent/trunk/pom.xml (original)
+++ commons/proper/commons-parent/trunk/pom.xml Thu Jan 3 05:00:26 2008
@@ -136,11 +136,6 @@
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-remote-resources-plugin</artifactId>
- <version>1.0-alpha-6</version>
- </plugin>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<version>2.0.4</version>
</plugin>
@@ -322,23 +317,6 @@
</execution>
</executions>
</plugin>
- <!-- We want to package license resources into the JARs -->
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-remote-resources-plugin</artifactId>
- <executions>
- <execution>
- <goals>
- <goal>process</goal>
- </goals>
- <configuration>
- <resourceBundles>
- <resourceBundle>org.apache:apache-jar-resource-bundle:1.3</resourceBundle>
- </resourceBundles>
- </configuration>
- </execution>
- </executions>
- </plugin>
</plugins>
</build>
</profile>
@@ -403,23 +381,6 @@
</goals>
<configuration>
<source>${maven.compile.source}</source>
- </configuration>
- </execution>
- </executions>
- </plugin>
- <!-- We want to package license resources into the JARs -->
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-remote-resources-plugin</artifactId>
- <executions>
- <execution>
- <goals>
- <goal>process</goal>
- </goals>
- <configuration>
- <resourceBundles>
- <resourceBundle>org.apache:apache-jar-resource-bundle:1.3</resourceBundle>
- </resourceBundles>
</configuration>
</execution>
</executions>
Re: svn commit: r608470 - /commons/proper/commons-parent/trunk/pom.xml
Posted by sebb <se...@gmail.com>.
On 04/01/2008, Henri Yandell <fl...@gmail.com> wrote:
> On Jan 3, 2008 11:53 AM, simon <si...@chello.at> wrote:
> >
> >
> > On Thu, 2008-01-03 at 19:46 +0000, Niall Pemberton wrote:
> > > On Jan 3, 2008 6:56 PM, Dennis Lundberg <de...@apache.org> wrote:
> > > > Niall Pemberton wrote:
> > > > > On Jan 3, 2008 5:00 PM, Dennis Lundberg <de...@apache.org> wrote:
> > > > >> I'd prefer if we could keep the section about
> > > > >> maven-remote-resources-plugin that is under pluginManagement. That way
> > > > >> we can ensure that those components that decide to use it, all use the
> > > > >> same version.
> > > > >
> > > > > Currrently all components have license and notice files so better to
> > > > > wait IMO till we have components wanting to use it first. Given some
> > > > > of the opinions expressed I would be surprised if any adopted it - or
> > > > > if they did that there weren't objections.
> > > >
> > > > Logging already uses it.
> > > >
> > > > The change that I propose does not mean that everyone will automatically
> > > > start using it. That decision is still up to the developers of each
> > > > component. But for those components that use, or decide to start using,
> > > > maven-remote-resources-plugin, it will make their builds more consistent.
> > >
> > > I understand but from the various discussions seems clear to me that
> > > the argument was lost. In the case of Logging I also think it
> > > confusing that it has Notice and License files in svn but it packages
> > > up different versions (i.e. those from the apache jar) in its jar.
> > > Also I just generated the logging jar and the generated Notice file
> > > included the following which IMO is worse than the one in svn:
> > >
> > > This product includes/uses software(s) developed by 'an unknown organization'
> > > - Unnamed - avalon-framework:avalon-framework:jar:4.1.3
> > > - Unnamed - log4j:log4j:jar:1.2.12
> > > - Unnamed - logkit:logkit:jar:1.0.1
> > >
> > > So perhaps logging should revert to its svn versions for now until the
> > > argument for the remote resources plugin is won and that plugin works
> > > better.
> >
> > I agree with Niall. I would have voted -1 on the logging release if I
> > had realised that the Notice/License files were auto-generated. I have
> > to kick myself for not having found time to check the logging release.
> >
> > I have seen little positive comment on the remote-resources approach,
> > certainly no consensus. Therefore there is little point in cluttering up
> > the poms with stuff that is not (and IMO should not) be used.
>
> Agreed.
>
> -1 Commons-wide on this. I'm not convinced by the remote resources
> plugin at all.
Agreed.
> Hen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: svn commit: r608470 - /commons/proper/commons-parent/trunk/pom.xml
Posted by Henri Yandell <fl...@gmail.com>.
On Jan 3, 2008 11:53 AM, simon <si...@chello.at> wrote:
>
>
> On Thu, 2008-01-03 at 19:46 +0000, Niall Pemberton wrote:
> > On Jan 3, 2008 6:56 PM, Dennis Lundberg <de...@apache.org> wrote:
> > > Niall Pemberton wrote:
> > > > On Jan 3, 2008 5:00 PM, Dennis Lundberg <de...@apache.org> wrote:
> > > >> I'd prefer if we could keep the section about
> > > >> maven-remote-resources-plugin that is under pluginManagement. That way
> > > >> we can ensure that those components that decide to use it, all use the
> > > >> same version.
> > > >
> > > > Currrently all components have license and notice files so better to
> > > > wait IMO till we have components wanting to use it first. Given some
> > > > of the opinions expressed I would be surprised if any adopted it - or
> > > > if they did that there weren't objections.
> > >
> > > Logging already uses it.
> > >
> > > The change that I propose does not mean that everyone will automatically
> > > start using it. That decision is still up to the developers of each
> > > component. But for those components that use, or decide to start using,
> > > maven-remote-resources-plugin, it will make their builds more consistent.
> >
> > I understand but from the various discussions seems clear to me that
> > the argument was lost. In the case of Logging I also think it
> > confusing that it has Notice and License files in svn but it packages
> > up different versions (i.e. those from the apache jar) in its jar.
> > Also I just generated the logging jar and the generated Notice file
> > included the following which IMO is worse than the one in svn:
> >
> > This product includes/uses software(s) developed by 'an unknown organization'
> > - Unnamed - avalon-framework:avalon-framework:jar:4.1.3
> > - Unnamed - log4j:log4j:jar:1.2.12
> > - Unnamed - logkit:logkit:jar:1.0.1
> >
> > So perhaps logging should revert to its svn versions for now until the
> > argument for the remote resources plugin is won and that plugin works
> > better.
>
> I agree with Niall. I would have voted -1 on the logging release if I
> had realised that the Notice/License files were auto-generated. I have
> to kick myself for not having found time to check the logging release.
>
> I have seen little positive comment on the remote-resources approach,
> certainly no consensus. Therefore there is little point in cluttering up
> the poms with stuff that is not (and IMO should not) be used.
Agreed.
-1 Commons-wide on this. I'm not convinced by the remote resources
plugin at all.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: svn commit: r608470 -
/commons/proper/commons-parent/trunk/pom.xml
Posted by simon <si...@chello.at>.
On Thu, 2008-01-03 at 19:46 +0000, Niall Pemberton wrote:
> On Jan 3, 2008 6:56 PM, Dennis Lundberg <de...@apache.org> wrote:
> > Niall Pemberton wrote:
> > > On Jan 3, 2008 5:00 PM, Dennis Lundberg <de...@apache.org> wrote:
> > >> I'd prefer if we could keep the section about
> > >> maven-remote-resources-plugin that is under pluginManagement. That way
> > >> we can ensure that those components that decide to use it, all use the
> > >> same version.
> > >
> > > Currrently all components have license and notice files so better to
> > > wait IMO till we have components wanting to use it first. Given some
> > > of the opinions expressed I would be surprised if any adopted it - or
> > > if they did that there weren't objections.
> >
> > Logging already uses it.
> >
> > The change that I propose does not mean that everyone will automatically
> > start using it. That decision is still up to the developers of each
> > component. But for those components that use, or decide to start using,
> > maven-remote-resources-plugin, it will make their builds more consistent.
>
> I understand but from the various discussions seems clear to me that
> the argument was lost. In the case of Logging I also think it
> confusing that it has Notice and License files in svn but it packages
> up different versions (i.e. those from the apache jar) in its jar.
> Also I just generated the logging jar and the generated Notice file
> included the following which IMO is worse than the one in svn:
>
> This product includes/uses software(s) developed by 'an unknown organization'
> - Unnamed - avalon-framework:avalon-framework:jar:4.1.3
> - Unnamed - log4j:log4j:jar:1.2.12
> - Unnamed - logkit:logkit:jar:1.0.1
>
> So perhaps logging should revert to its svn versions for now until the
> argument for the remote resources plugin is won and that plugin works
> better.
I agree with Niall. I would have voted -1 on the logging release if I
had realised that the Notice/License files were auto-generated. I have
to kick myself for not having found time to check the logging release.
I have seen little positive comment on the remote-resources approach,
certainly no consensus. Therefore there is little point in cluttering up
the poms with stuff that is not (and IMO should not) be used.
Regards,
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: svn commit: r608470 - /commons/proper/commons-parent/trunk/pom.xml
Posted by Niall Pemberton <ni...@gmail.com>.
On Jan 3, 2008 6:56 PM, Dennis Lundberg <de...@apache.org> wrote:
> Niall Pemberton wrote:
> > On Jan 3, 2008 5:00 PM, Dennis Lundberg <de...@apache.org> wrote:
> >> I'd prefer if we could keep the section about
> >> maven-remote-resources-plugin that is under pluginManagement. That way
> >> we can ensure that those components that decide to use it, all use the
> >> same version.
> >
> > Currrently all components have license and notice files so better to
> > wait IMO till we have components wanting to use it first. Given some
> > of the opinions expressed I would be surprised if any adopted it - or
> > if they did that there weren't objections.
>
> Logging already uses it.
>
> The change that I propose does not mean that everyone will automatically
> start using it. That decision is still up to the developers of each
> component. But for those components that use, or decide to start using,
> maven-remote-resources-plugin, it will make their builds more consistent.
I understand but from the various discussions seems clear to me that
the argument was lost. In the case of Logging I also think it
confusing that it has Notice and License files in svn but it packages
up different versions (i.e. those from the apache jar) in its jar.
Also I just generated the logging jar and the generated Notice file
included the following which IMO is worse than the one in svn:
This product includes/uses software(s) developed by 'an unknown organization'
- Unnamed - avalon-framework:avalon-framework:jar:4.1.3
- Unnamed - log4j:log4j:jar:1.2.12
- Unnamed - logkit:logkit:jar:1.0.1
So perhaps logging should revert to its svn versions for now until the
argument for the remote resources plugin is won and that plugin works
better.
Niall
> >
> > Niall
> >
> >> niallp@apache.org wrote:
> >>> Author: niallp
> >>> Date: Thu Jan 3 05:00:26 2008
> >>> New Revision: 608470
> >>>
> >>> URL: http://svn.apache.org/viewvc?rev=608470&view=rev
> >>> Log:
> >>> COMMONSSITE-21 - remove remote resources plugin
> >>>
> >>> Modified:
> >>> commons/proper/commons-parent/trunk/pom.xml
> >>>
> >>> Modified: commons/proper/commons-parent/trunk/pom.xml
> >>> URL: http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?rev=608470&r1=608469&r2=608470&view=diff
> >>> ==============================================================================
> >>> --- commons/proper/commons-parent/trunk/pom.xml (original)
> >>> +++ commons/proper/commons-parent/trunk/pom.xml Thu Jan 3 05:00:26 2008
> >>> @@ -136,11 +136,6 @@
> >>> </plugin>
> >>> <plugin>
> >>> <groupId>org.apache.maven.plugins</groupId>
> >>> - <artifactId>maven-remote-resources-plugin</artifactId>
> >>> - <version>1.0-alpha-6</version>
> >>> - </plugin>
> >>> - <plugin>
> >>> - <groupId>org.apache.maven.plugins</groupId>
> >>> <artifactId>maven-source-plugin</artifactId>
> >>> <version>2.0.4</version>
> >>> </plugin>
> >>> @@ -322,23 +317,6 @@
> >>> </execution>
> >>> </executions>
> >>> </plugin>
> >>> - <!-- We want to package license resources into the JARs -->
> >>> - <plugin>
> >>> - <groupId>org.apache.maven.plugins</groupId>
> >>> - <artifactId>maven-remote-resources-plugin</artifactId>
> >>> - <executions>
> >>> - <execution>
> >>> - <goals>
> >>> - <goal>process</goal>
> >>> - </goals>
> >>> - <configuration>
> >>> - <resourceBundles>
> >>> - <resourceBundle>org.apache:apache-jar-resource-bundle:1.3</resourceBundle>
> >>> - </resourceBundles>
> >>> - </configuration>
> >>> - </execution>
> >>> - </executions>
> >>> - </plugin>
> >>> </plugins>
> >>> </build>
> >>> </profile>
> >>> @@ -403,23 +381,6 @@
> >>> </goals>
> >>> <configuration>
> >>> <source>${maven.compile.source}</source>
> >>> - </configuration>
> >>> - </execution>
> >>> - </executions>
> >>> - </plugin>
> >>> - <!-- We want to package license resources into the JARs -->
> >>> - <plugin>
> >>> - <groupId>org.apache.maven.plugins</groupId>
> >>> - <artifactId>maven-remote-resources-plugin</artifactId>
> >>> - <executions>
> >>> - <execution>
> >>> - <goals>
> >>> - <goal>process</goal>
> >>> - </goals>
> >>> - <configuration>
> >>> - <resourceBundles>
> >>> - <resourceBundle>org.apache:apache-jar-resource-bundle:1.3</resourceBundle>
> >>> - </resourceBundles>
> >>> </configuration>
> >>> </execution>
> >>> </executions>
> >>>
> >>>
> >>>
> >>
> >> --
> >> Dennis Lundberg
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >> For additional commands, e-mail: dev-help@commons.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
>
> --
>
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: svn commit: r608470 - /commons/proper/commons-parent/trunk/pom.xml
Posted by Dennis Lundberg <de...@apache.org>.
Niall Pemberton wrote:
> On Jan 3, 2008 5:00 PM, Dennis Lundberg <de...@apache.org> wrote:
>> I'd prefer if we could keep the section about
>> maven-remote-resources-plugin that is under pluginManagement. That way
>> we can ensure that those components that decide to use it, all use the
>> same version.
>
> Currrently all components have license and notice files so better to
> wait IMO till we have components wanting to use it first. Given some
> of the opinions expressed I would be surprised if any adopted it - or
> if they did that there weren't objections.
Logging already uses it.
The change that I propose does not mean that everyone will automatically
start using it. That decision is still up to the developers of each
component. But for those components that use, or decide to start using,
maven-remote-resources-plugin, it will make their builds more consistent.
>
> Niall
>
>> niallp@apache.org wrote:
>>> Author: niallp
>>> Date: Thu Jan 3 05:00:26 2008
>>> New Revision: 608470
>>>
>>> URL: http://svn.apache.org/viewvc?rev=608470&view=rev
>>> Log:
>>> COMMONSSITE-21 - remove remote resources plugin
>>>
>>> Modified:
>>> commons/proper/commons-parent/trunk/pom.xml
>>>
>>> Modified: commons/proper/commons-parent/trunk/pom.xml
>>> URL: http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?rev=608470&r1=608469&r2=608470&view=diff
>>> ==============================================================================
>>> --- commons/proper/commons-parent/trunk/pom.xml (original)
>>> +++ commons/proper/commons-parent/trunk/pom.xml Thu Jan 3 05:00:26 2008
>>> @@ -136,11 +136,6 @@
>>> </plugin>
>>> <plugin>
>>> <groupId>org.apache.maven.plugins</groupId>
>>> - <artifactId>maven-remote-resources-plugin</artifactId>
>>> - <version>1.0-alpha-6</version>
>>> - </plugin>
>>> - <plugin>
>>> - <groupId>org.apache.maven.plugins</groupId>
>>> <artifactId>maven-source-plugin</artifactId>
>>> <version>2.0.4</version>
>>> </plugin>
>>> @@ -322,23 +317,6 @@
>>> </execution>
>>> </executions>
>>> </plugin>
>>> - <!-- We want to package license resources into the JARs -->
>>> - <plugin>
>>> - <groupId>org.apache.maven.plugins</groupId>
>>> - <artifactId>maven-remote-resources-plugin</artifactId>
>>> - <executions>
>>> - <execution>
>>> - <goals>
>>> - <goal>process</goal>
>>> - </goals>
>>> - <configuration>
>>> - <resourceBundles>
>>> - <resourceBundle>org.apache:apache-jar-resource-bundle:1.3</resourceBundle>
>>> - </resourceBundles>
>>> - </configuration>
>>> - </execution>
>>> - </executions>
>>> - </plugin>
>>> </plugins>
>>> </build>
>>> </profile>
>>> @@ -403,23 +381,6 @@
>>> </goals>
>>> <configuration>
>>> <source>${maven.compile.source}</source>
>>> - </configuration>
>>> - </execution>
>>> - </executions>
>>> - </plugin>
>>> - <!-- We want to package license resources into the JARs -->
>>> - <plugin>
>>> - <groupId>org.apache.maven.plugins</groupId>
>>> - <artifactId>maven-remote-resources-plugin</artifactId>
>>> - <executions>
>>> - <execution>
>>> - <goals>
>>> - <goal>process</goal>
>>> - </goals>
>>> - <configuration>
>>> - <resourceBundles>
>>> - <resourceBundle>org.apache:apache-jar-resource-bundle:1.3</resourceBundle>
>>> - </resourceBundles>
>>> </configuration>
>>> </execution>
>>> </executions>
>>>
>>>
>>>
>>
>> --
>> Dennis Lundberg
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: svn commit: r608470 - /commons/proper/commons-parent/trunk/pom.xml
Posted by Niall Pemberton <ni...@gmail.com>.
On Jan 3, 2008 5:00 PM, Dennis Lundberg <de...@apache.org> wrote:
> I'd prefer if we could keep the section about
> maven-remote-resources-plugin that is under pluginManagement. That way
> we can ensure that those components that decide to use it, all use the
> same version.
Currrently all components have license and notice files so better to
wait IMO till we have components wanting to use it first. Given some
of the opinions expressed I would be surprised if any adopted it - or
if they did that there weren't objections.
Niall
> niallp@apache.org wrote:
> > Author: niallp
> > Date: Thu Jan 3 05:00:26 2008
> > New Revision: 608470
> >
> > URL: http://svn.apache.org/viewvc?rev=608470&view=rev
> > Log:
> > COMMONSSITE-21 - remove remote resources plugin
> >
> > Modified:
> > commons/proper/commons-parent/trunk/pom.xml
> >
> > Modified: commons/proper/commons-parent/trunk/pom.xml
> > URL: http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?rev=608470&r1=608469&r2=608470&view=diff
> > ==============================================================================
> > --- commons/proper/commons-parent/trunk/pom.xml (original)
> > +++ commons/proper/commons-parent/trunk/pom.xml Thu Jan 3 05:00:26 2008
> > @@ -136,11 +136,6 @@
> > </plugin>
> > <plugin>
> > <groupId>org.apache.maven.plugins</groupId>
> > - <artifactId>maven-remote-resources-plugin</artifactId>
> > - <version>1.0-alpha-6</version>
> > - </plugin>
> > - <plugin>
> > - <groupId>org.apache.maven.plugins</groupId>
> > <artifactId>maven-source-plugin</artifactId>
> > <version>2.0.4</version>
> > </plugin>
> > @@ -322,23 +317,6 @@
> > </execution>
> > </executions>
> > </plugin>
> > - <!-- We want to package license resources into the JARs -->
> > - <plugin>
> > - <groupId>org.apache.maven.plugins</groupId>
> > - <artifactId>maven-remote-resources-plugin</artifactId>
> > - <executions>
> > - <execution>
> > - <goals>
> > - <goal>process</goal>
> > - </goals>
> > - <configuration>
> > - <resourceBundles>
> > - <resourceBundle>org.apache:apache-jar-resource-bundle:1.3</resourceBundle>
> > - </resourceBundles>
> > - </configuration>
> > - </execution>
> > - </executions>
> > - </plugin>
> > </plugins>
> > </build>
> > </profile>
> > @@ -403,23 +381,6 @@
> > </goals>
> > <configuration>
> > <source>${maven.compile.source}</source>
> > - </configuration>
> > - </execution>
> > - </executions>
> > - </plugin>
> > - <!-- We want to package license resources into the JARs -->
> > - <plugin>
> > - <groupId>org.apache.maven.plugins</groupId>
> > - <artifactId>maven-remote-resources-plugin</artifactId>
> > - <executions>
> > - <execution>
> > - <goals>
> > - <goal>process</goal>
> > - </goals>
> > - <configuration>
> > - <resourceBundles>
> > - <resourceBundle>org.apache:apache-jar-resource-bundle:1.3</resourceBundle>
> > - </resourceBundles>
> > </configuration>
> > </execution>
> > </executions>
> >
> >
> >
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: svn commit: r608470 - /commons/proper/commons-parent/trunk/pom.xml
Posted by Dennis Lundberg <de...@apache.org>.
I'd prefer if we could keep the section about
maven-remote-resources-plugin that is under pluginManagement. That way
we can ensure that those components that decide to use it, all use the
same version.
niallp@apache.org wrote:
> Author: niallp
> Date: Thu Jan 3 05:00:26 2008
> New Revision: 608470
>
> URL: http://svn.apache.org/viewvc?rev=608470&view=rev
> Log:
> COMMONSSITE-21 - remove remote resources plugin
>
> Modified:
> commons/proper/commons-parent/trunk/pom.xml
>
> Modified: commons/proper/commons-parent/trunk/pom.xml
> URL: http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?rev=608470&r1=608469&r2=608470&view=diff
> ==============================================================================
> --- commons/proper/commons-parent/trunk/pom.xml (original)
> +++ commons/proper/commons-parent/trunk/pom.xml Thu Jan 3 05:00:26 2008
> @@ -136,11 +136,6 @@
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> - <artifactId>maven-remote-resources-plugin</artifactId>
> - <version>1.0-alpha-6</version>
> - </plugin>
> - <plugin>
> - <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-source-plugin</artifactId>
> <version>2.0.4</version>
> </plugin>
> @@ -322,23 +317,6 @@
> </execution>
> </executions>
> </plugin>
> - <!-- We want to package license resources into the JARs -->
> - <plugin>
> - <groupId>org.apache.maven.plugins</groupId>
> - <artifactId>maven-remote-resources-plugin</artifactId>
> - <executions>
> - <execution>
> - <goals>
> - <goal>process</goal>
> - </goals>
> - <configuration>
> - <resourceBundles>
> - <resourceBundle>org.apache:apache-jar-resource-bundle:1.3</resourceBundle>
> - </resourceBundles>
> - </configuration>
> - </execution>
> - </executions>
> - </plugin>
> </plugins>
> </build>
> </profile>
> @@ -403,23 +381,6 @@
> </goals>
> <configuration>
> <source>${maven.compile.source}</source>
> - </configuration>
> - </execution>
> - </executions>
> - </plugin>
> - <!-- We want to package license resources into the JARs -->
> - <plugin>
> - <groupId>org.apache.maven.plugins</groupId>
> - <artifactId>maven-remote-resources-plugin</artifactId>
> - <executions>
> - <execution>
> - <goals>
> - <goal>process</goal>
> - </goals>
> - <configuration>
> - <resourceBundles>
> - <resourceBundle>org.apache:apache-jar-resource-bundle:1.3</resourceBundle>
> - </resourceBundles>
> </configuration>
> </execution>
> </executions>
>
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org