You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brian E. Fox" <br...@reply.infinity.nu> on 2006/11/14 03:36:15 UTC
Plugin license injection
Was there ever a resolution about the new plugin releases needing the
apache license injected? We can probably do it with the dependency
plugin but I don't want to repeat work if there is already a solution.
Also, can someone point me to documentation on what the exact new
requirements are?
Thanks,
Brian
Re: Plugin license injection
Posted by Daniel Kulp <da...@iona.com>.
On Monday November 13 2006 10:47 pm, Brett Porter wrote:
> On 14/11/2006, at 2:41 PM, Daniel Kulp wrote:
> > That's an "OK" temporary solution. The biggest problem with it is
> > that
> > you cannot generate a working eclipse project with that setup. "mvn
> > eclipse:eclipe" doesn't generate a project that is importable into
> > eclipse.
>
> I thought this had been fixed. There should be no reason it can't be.
I think (not 100% sure though) that it is fixed in the snapshot versions
of the Eclipse plugin. That doesn't help those of use that haven't
built it locally though. If I just checkout the dependency plugin and
run "mvn eclipse:eclipse" right now, it does not generate a working
project.
That all said, I wouldn't holdup a release cause of that. Mark it as a
bug/feature request that will be fixed when the eclipse plugin is
released.
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194 F:781-902-8001
daniel.kulp@iona.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Plugin license injection
Posted by Brett Porter <br...@apache.org>.
On 14/11/2006, at 2:41 PM, Daniel Kulp wrote:
> That's an "OK" temporary solution. The biggest problem with it is
> that
> you cannot generate a working eclipse project with that setup. "mvn
> eclipse:eclipe" doesn't generate a project that is importable into
> eclipse.
I thought this had been fixed. There should be no reason it can't be.
>
>>
>> The full description is here: http://www.apache.org/legal/src-
>> headers.html
>
> The two major issues (I think, IANAL) are:
> 1) Inclusion of the notice/license stuff in META-INF dir of the jars
and the root of the source distribution
>
> 2) The license header in ALL the files has to change. The header
> has a
> whole new legal verbage (to point to the notice files) and the
> copyright
> date is removed.
There are scripts to aid in this, or you can use the IDEA Copyright
plugin.
>
> Enjoy!
> Dan
>
>>
>> On 14/11/2006, at 1:36 PM, Brian E. Fox wrote:
>>> Was there ever a resolution about the new plugin releases needing
>>> the
>>> apache license injected? We can probably do it with the dependency
>>> plugin but I don't want to repeat work if there is already a
>>> solution. Also, can someone point me to documentation on what the
>>> exact new requirements are?
>>>
>>> Thanks,
>>> Brian
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727 C: 508-380-7194 F:781-902-8001
> daniel.kulp@iona.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Plugin license injection
Posted by Daniel Kulp <da...@iona.com>.
On Monday November 13 2006 10:00 pm, Brett Porter wrote:
> Jason was going to whip something up. I believe he'll be back in a
> couple of days and can answer then.
>
> You can copy the technique used in pmd/checkstyle, at least for the
> files in the root directory if you are looking to move on it now.
That's an "OK" temporary solution. The biggest problem with it is that
you cannot generate a working eclipse project with that setup. "mvn
eclipse:eclipe" doesn't generate a project that is importable into
eclipse.
>
> The full description is here: http://www.apache.org/legal/src-
> headers.html
The two major issues (I think, IANAL) are:
1) Inclusion of the notice/license stuff in META-INF dir of the jars
2) The license header in ALL the files has to change. The header has a
whole new legal verbage (to point to the notice files) and the copyright
date is removed.
Enjoy!
Dan
>
> On 14/11/2006, at 1:36 PM, Brian E. Fox wrote:
> > Was there ever a resolution about the new plugin releases needing the
> > apache license injected? We can probably do it with the dependency
> > plugin but I don't want to repeat work if there is already a
> > solution. Also, can someone point me to documentation on what the
> > exact new requirements are?
> >
> > Thanks,
> > Brian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194 F:781-902-8001
daniel.kulp@iona.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Plugin license injection
Posted by Brett Porter <br...@apache.org>.
Jason was going to whip something up. I believe he'll be back in a
couple of days and can answer then.
You can copy the technique used in pmd/checkstyle, at least for the
files in the root directory if you are looking to move on it now.
The full description is here: http://www.apache.org/legal/src-
headers.html
On 14/11/2006, at 1:36 PM, Brian E. Fox wrote:
> Was there ever a resolution about the new plugin releases needing the
> apache license injected? We can probably do it with the dependency
> plugin but I don't want to repeat work if there is already a solution.
> Also, can someone point me to documentation on what the exact new
> requirements are?
>
> Thanks,
> Brian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org