Hi Robert,

Well I am just worried, that in the end the situation in the incubator will not 
change.
There still might be -1 votes for not mentioning in the LICENSE that software 
from the ASF is included in a software package that is ASF anyway.
I do recall that it is considered nice to reference the project if the code is 
Apache Licensed and no NOTICE or LICENSE requires you to mention it.
But I also recall that it's not mandatory. 

So if the maven project would announce "you don't need to" this question could 
be off the table indefinitely ...

But IANALT so I would be interested in if this is actually correct.

Chris


Am 13.02.20, 19:33 schrieb "Robert Scholte" <rfscho...@apache.org>:

    AFAIK these files are partly generated. Might be better to improve it there.
    
    Robert
    On 13-2-2020 07:29:46, Christofer Dutz <christofer.d...@c-ware.de> wrote:
    Hi all,
    
    would it also be possible for some sort of official statement that when 
copying the maven wrapper scripts (For Apache Projects), this doesn't 
explicitly have to be mentioned in the NOTICE or LICENSE file? I know that this 
could ease quite some +1/-1 discussions (especially on the incubator).
    
    Chris
    
    Am 13.02.20, 06:12 schrieb "James Gao" :
    
    With maven wrapper, most maven project could be build out of box iff jdk is
    installed, and the maven version used for build is locked by the project
    owner. So in run time, each version of wrapper should be able to integrate
    with as many as versions of maven. And so does the wrapper plugin, but
    plugin is seldom used by by developers.
    
    What the wrapper depends on are two very stable things:
    a) how maven is distributed (a zip/tgz archive and its internal file
    structures),
    b) how maven is executed without wrapper (entry scripts, e.g. bin/mvn and
    bin/mvn.cmd)
    
    No matter how wrapper is distributed (via plugin or just copy from another
    project), the deployed wrapper based on previous dependents, will deploy a
    configurable version of maven to a personal location on the fly if needed,
    then executed the previous deployed maven, but will not update the deployed
    script itself.
    
    So although wrapper will be released with maven core, it still better not
    to lock the runtime version of maven.
    
    On Thu, Feb 13, 2020 at 4:24 AM Robert Scholte wrote:
    
    > well, with every release of Maven, some versions needed to be updated, see
    > the commit logs.
    > Also the release instructions show some relation with the Maven version.
    >
    > Based on that it looks like it should be part of core.
    > I've understood doing a release of is a bit problematic due to some
    > chicken-egg issue.
    >
    > However, I did start with the plugin and that one is now capable of
    > recognizing the runtime version of Maven, not hardcoded.
    >
    > So it depends, I just haven't figured it out yet.
    > On 12-2-2020 20:28:24, Enrico Olivelli wrote:
    > Il Mer 12 Feb 2020, 19:58 Robert Scholte ha scritto:
    >
    > > Hi,
    > >
    > > This month we've finished the incubator process to move to code from the
    > > maven wrapper to our project.
    > >
    >
    > Cool
    >
    > >
    > > Initially the idea was to move both the maven-wrapper and the
    > > takari-maven-plugin (which contains a wrapper goal) to our codebase, but
    > > due to conflicting licensing we only moved the maven-wrapper.
    > >
    > > Right now I've moved the code of the maven-wrapper to his own branch
    > under
    > > maven-studies.
    > > From here we can work on it. I think it makes sense to make it a module
    > of
    > > Maven core, but that's still a decision we need to make.
    > >
    >
    > Is it strictly dependent on a Maven version? I thought it was totally
    > independent.
    > Why not having a separate repository and release lifecycle?
    >
    > Enrico
    >
    >
    > > For the maven-wrapper-plugin a new repository has been created. And I've
    > > started with a clean branch, trying to set the base of this plugin.
    > >
    > > Both are open for further development, not just by me.
    > >
    > > So here are the 2 new git repositories:
    > > https://gitbox.apache.org/repos/asf/maven-wrapper-plugin.git
    > > (branch MWRAPPER-0_WIP)
    > > https://gitbox.apache.org/repos/asf/maven-studies.git (branch
    > > maven-wrapper)
    > >
    > >
    > > Enjoy,
    > > Robert
    >
    
    
    
Т���������������������������������������������������������������������ХF�?V�7V'67&�&R�?R��?�â?FWb�V�7V'67&�&T?�?fV��???6�R��&pФf�"??FF�F���?�?6���?�G2�?R��?�â?FWbֆV�??�?fV��???6�R��&pР

Reply via email to