You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by han hongfang <ha...@gmail.com> on 2010/08/27 11:27:50 UTC
[maven-release-plugin] Is it possible to configure
maven-release-plugin to NOT pull in META-INF/LICENSE and NOTICE
Hi,
Our project uses maven-release-plugin in the release process. We maintain
the LICENSE.txt and NOTICE.txt (which contains module specifc statement) for
each of our modules in subversion. When we issue mvn release:prepare,
standard LICENSE and NOTICE files are pulled into META-INF folder of target
artifact. These standard files are duplicated with LICENSE.txt and
NOTICE.txt we maintained.
Is it possible to configure maven-release-plugin to not pull in these files?
If yes, could you show me how to do it?
Thanks in advance for your reply!
--
Best regards,
Han Hong Fang
Re: Fwd: [maven-release-plugin] Is it possible to configure
maven-release-plugin to NOT pull in META-INF/LICENSE and NOTICE
Posted by han hongfang <ha...@gmail.com>.
Hi Dan,
Really appreciated your reply.
With the clue your provided, I solve my probjem as below.
1. update maven-remote-resource to version 1.1
2. set the option attached with false in maven-remote-resource plugin, this
will disable the automatic copy of the files from remote resource bundle
3. use <reource> element in the pom.xml to only copy my interested files
from target/maven-shared-archive-resources directory
Thanks again Dan for your help.
Best regards,
Han Hong Fang
On Fri, Sep 3, 2010 at 9:19 PM, Daniel Kulp <dk...@apache.org> wrote:
> On Friday 03 September 2010 2:34:00 am han hongfang wrote:
> > Forward to dev list to see if somebody has some advice for me on this
> > question.
>
> It's not the release plugin, it's the remote-resources plugin generating
> them.
> You would need to figure out where the remote-resources thing is
> configured.
> You don't mention which project, but if it's and Apache project using the
> Apache parent pom, that would be pulled in automatically.
>
> Th easy fix is to rename your files to LICENSE and and NOTICE. remote-
> resources will not overwrite new files if existing files exist.
>
> Dan
>
>
>
> >
> > Best regards,
> >
> > Han Hong Fang
> >
> > ---------- Forwarded message ----------
> > From: han hongfang <ha...@gmail.com>
> > Date: Fri, Aug 27, 2010 at 5:27 PM
> > Subject: [maven-release-plugin] Is it possible to configure
> > maven-release-plugin to NOT pull in META-INF/LICENSE and NOTICE
> > To: users@maven.apache.org
> >
> >
> >
> > Hi,
> >
> > Our project uses maven-release-plugin in the release process. We maintain
> > the LICENSE.txt and NOTICE.txt (which contains module specifc statement)
> > for each of our modules in subversion. When we issue mvn release:prepare,
> > standard LICENSE and NOTICE files are pulled into META-INF folder of
> > target artifact. These standard files are duplicated with LICENSE.txt and
> > NOTICE.txt we maintained.
> >
> > Is it possible to configure maven-release-plugin to not pull in these
> > files? If yes, could you show me how to do it?
> >
> > Thanks in advance for your reply!
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
>
--
Best regards,
Han Hong Fang
Re: Fwd: [maven-release-plugin] Is it possible to configure
maven-release-plugin to NOT pull in META-INF/LICENSE and NOTICE
Posted by han hongfang <ha...@gmail.com>.
Hi Dan,
Really appreciated your reply.
With the clue your provided, I solve my probjem as below.
1. update maven-remote-resource to version 1.1
2. set the option attached with false in maven-remote-resource plugin, this
will disable the automatic copy of the files from remote resource bundle
3. use <reource> element in the pom.xml to only copy my interested files
from target/maven-shared-archive-resources directory
Thanks again Dan for your help.
Best regards,
Han Hong Fang
On Fri, Sep 3, 2010 at 9:19 PM, Daniel Kulp <dk...@apache.org> wrote:
> On Friday 03 September 2010 2:34:00 am han hongfang wrote:
> > Forward to dev list to see if somebody has some advice for me on this
> > question.
>
> It's not the release plugin, it's the remote-resources plugin generating
> them.
> You would need to figure out where the remote-resources thing is
> configured.
> You don't mention which project, but if it's and Apache project using the
> Apache parent pom, that would be pulled in automatically.
>
> Th easy fix is to rename your files to LICENSE and and NOTICE. remote-
> resources will not overwrite new files if existing files exist.
>
> Dan
>
>
>
> >
> > Best regards,
> >
> > Han Hong Fang
> >
> > ---------- Forwarded message ----------
> > From: han hongfang <ha...@gmail.com>
> > Date: Fri, Aug 27, 2010 at 5:27 PM
> > Subject: [maven-release-plugin] Is it possible to configure
> > maven-release-plugin to NOT pull in META-INF/LICENSE and NOTICE
> > To: users@maven.apache.org
> >
> >
> >
> > Hi,
> >
> > Our project uses maven-release-plugin in the release process. We maintain
> > the LICENSE.txt and NOTICE.txt (which contains module specifc statement)
> > for each of our modules in subversion. When we issue mvn release:prepare,
> > standard LICENSE and NOTICE files are pulled into META-INF folder of
> > target artifact. These standard files are duplicated with LICENSE.txt and
> > NOTICE.txt we maintained.
> >
> > Is it possible to configure maven-release-plugin to not pull in these
> > files? If yes, could you show me how to do it?
> >
> > Thanks in advance for your reply!
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
>
--
Best regards,
Han Hong Fang
Re: Fwd: [maven-release-plugin] Is it possible to configure maven-release-plugin to NOT pull in META-INF/LICENSE and NOTICE
Posted by Daniel Kulp <dk...@apache.org>.
On Friday 03 September 2010 2:34:00 am han hongfang wrote:
> Forward to dev list to see if somebody has some advice for me on this
> question.
It's not the release plugin, it's the remote-resources plugin generating them.
You would need to figure out where the remote-resources thing is configured.
You don't mention which project, but if it's and Apache project using the
Apache parent pom, that would be pulled in automatically.
Th easy fix is to rename your files to LICENSE and and NOTICE. remote-
resources will not overwrite new files if existing files exist.
Dan
>
> Best regards,
>
> Han Hong Fang
>
> ---------- Forwarded message ----------
> From: han hongfang <ha...@gmail.com>
> Date: Fri, Aug 27, 2010 at 5:27 PM
> Subject: [maven-release-plugin] Is it possible to configure
> maven-release-plugin to NOT pull in META-INF/LICENSE and NOTICE
> To: users@maven.apache.org
>
>
>
> Hi,
>
> Our project uses maven-release-plugin in the release process. We maintain
> the LICENSE.txt and NOTICE.txt (which contains module specifc statement)
> for each of our modules in subversion. When we issue mvn release:prepare,
> standard LICENSE and NOTICE files are pulled into META-INF folder of
> target artifact. These standard files are duplicated with LICENSE.txt and
> NOTICE.txt we maintained.
>
> Is it possible to configure maven-release-plugin to not pull in these
> files? If yes, could you show me how to do it?
>
> Thanks in advance for your reply!
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Fwd: [maven-release-plugin] Is it possible to configure
maven-release-plugin to NOT pull in META-INF/LICENSE and NOTICE
Posted by han hongfang <ha...@gmail.com>.
Forward to dev list to see if somebody has some advice for me on this
question.
Best regards,
Han Hong Fang
---------- Forwarded message ----------
From: han hongfang <ha...@gmail.com>
Date: Fri, Aug 27, 2010 at 5:27 PM
Subject: [maven-release-plugin] Is it possible to configure
maven-release-plugin to NOT pull in META-INF/LICENSE and NOTICE
To: users@maven.apache.org
Hi,
Our project uses maven-release-plugin in the release process. We maintain
the LICENSE.txt and NOTICE.txt (which contains module specifc statement) for
each of our modules in subversion. When we issue mvn release:prepare,
standard LICENSE and NOTICE files are pulled into META-INF folder of target
artifact. These standard files are duplicated with LICENSE.txt and
NOTICE.txt we maintained.
Is it possible to configure maven-release-plugin to not pull in these files?
If yes, could you show me how to do it?
Thanks in advance for your reply!
--
Best regards,
Han Hong Fang
--
Best regards,
Han Hong Fang
Re: [maven-release-plugin] Is it possible to configure
maven-release-plugin to NOT pull in META-INF/LICENSE and NOTICE
Posted by Baptiste MATHUS <ml...@batmat.net>.
Hi,
I don't think it's justified for you to write to dev list. This sound like a
typical user problem, not a dev one.
Note a lot of developers also follow the users list, so writing to dev list
is not always going to help you, if not worse.
First, try answering the question that're being asked to you: what parent
pom are you inheriting from?
Cheers
2010/8/27 Kalle Korhonen <ka...@gmail.com>
> Sounds like you are using the Apache super pom as the parent. If you
> simply name yours LICENSE and NOTICE, they'll overwrite the default
> ones.
>
> Kalle
>
>
> On Fri, Aug 27, 2010 at 7:03 AM, Justin Edelson <ju...@gmail.com>
> wrote:
> > Nothing in the release plugin will do this automatically; it must be
> > configured somewhere, either in your POM or (more likely from the sound
> > of it) in a parent POM.
> >
> > Justin
> >
> > On 8/27/10 5:27 AM, han hongfang wrote:
> >> Hi,
> >>
> >> Our project uses maven-release-plugin in the release process. We
> maintain
> >> the LICENSE.txt and NOTICE.txt (which contains module specifc statement)
> for
> >> each of our modules in subversion. When we issue mvn release:prepare,
> >> standard LICENSE and NOTICE files are pulled into META-INF folder of
> target
> >> artifact. These standard files are duplicated with LICENSE.txt and
> >> NOTICE.txt we maintained.
> >>
> >> Is it possible to configure maven-release-plugin to not pull in these
> files?
> >> If yes, could you show me how to do it?
> >>
> >> Thanks in advance for your reply!
>
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
Re: [maven-release-plugin] Is it possible to configure
maven-release-plugin to NOT pull in META-INF/LICENSE and NOTICE
Posted by Kalle Korhonen <ka...@gmail.com>.
Sounds like you are using the Apache super pom as the parent. If you
simply name yours LICENSE and NOTICE, they'll overwrite the default
ones.
Kalle
On Fri, Aug 27, 2010 at 7:03 AM, Justin Edelson <ju...@gmail.com> wrote:
> Nothing in the release plugin will do this automatically; it must be
> configured somewhere, either in your POM or (more likely from the sound
> of it) in a parent POM.
>
> Justin
>
> On 8/27/10 5:27 AM, han hongfang wrote:
>> Hi,
>>
>> Our project uses maven-release-plugin in the release process. We maintain
>> the LICENSE.txt and NOTICE.txt (which contains module specifc statement) for
>> each of our modules in subversion. When we issue mvn release:prepare,
>> standard LICENSE and NOTICE files are pulled into META-INF folder of target
>> artifact. These standard files are duplicated with LICENSE.txt and
>> NOTICE.txt we maintained.
>>
>> Is it possible to configure maven-release-plugin to not pull in these files?
>> If yes, could you show me how to do it?
>>
>> Thanks in advance for your reply!
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [maven-release-plugin] Is it possible to configure maven-release-plugin
to NOT pull in META-INF/LICENSE and NOTICE
Posted by Justin Edelson <ju...@gmail.com>.
Nothing in the release plugin will do this automatically; it must be
configured somewhere, either in your POM or (more likely from the sound
of it) in a parent POM.
Justin
On 8/27/10 5:27 AM, han hongfang wrote:
> Hi,
>
> Our project uses maven-release-plugin in the release process. We maintain
> the LICENSE.txt and NOTICE.txt (which contains module specifc statement) for
> each of our modules in subversion. When we issue mvn release:prepare,
> standard LICENSE and NOTICE files are pulled into META-INF folder of target
> artifact. These standard files are duplicated with LICENSE.txt and
> NOTICE.txt we maintained.
>
> Is it possible to configure maven-release-plugin to not pull in these files?
> If yes, could you show me how to do it?
>
> Thanks in advance for your reply!
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org