Re: maven and distribution bundles with transitive deps: licensing

On Tue, Jul 11, 2017 at 8:10 PM Justin Mclean wrote: > Hi, > > > As I understand it / ASF policy, the newly generated distribution > bundles lack the necessary > > license/notice info for transitive deps contained in the bundle. > > In general dependancies don’t modify

Re: maven and distribution bundles with transitive deps: licensing

Hi, > As I understand it / ASF policy, the newly generated distribution bundles > lack the necessary > license/notice info for transitive deps contained in the bundle. In general dependancies don’t modify LICENSE or NOTICE files only what is bundled in an artefact does. Thanks, Justin

[GitHub] incubator-edgent pull request #309: Migration of the Edgent project to be ab...

Github user dlaboss commented on a diff in the pull request: https://github.com/apache/incubator-edgent/pull/309#discussion_r126820077 --- Diff: connectors/websocket/pom.xml --- @@ -27,10 +27,10 @@ 1.2.0-SNAPSHOT - edgent-connectors-websocket-wsclient

[GitHub] incubator-edgent pull request #309: Migration of the Edgent project to be ab...

Github user dlaboss commented on a diff in the pull request: https://github.com/apache/incubator-edgent/pull/309#discussion_r126819370 --- Diff: platforms/android/connectors/pom.xml --- @@ -37,19 +37,19 @@ command common csv -

Re: maven and distribution bundles with transitive deps: licensing

I'm not demanding the assembly ... It was just the last missing part in the migration to Maven. Most ASF projects provide such convenience binary archives, but an ASF release is the source only anyway. I admit that your script would do the job. Another thing worth looking into might be the

Re: Progress on Maven?

Sounds good for me :-) I just added "the works" for the sake of completeness. If we had an ASF Jenkins build doing the full thing, I guess a Travis build just doing the j8 build + unit-tests + integration-tests that would be enough and should be below the 4mb limit. Chris Von meinem

Re: Progress on Maven?

No idea from me. Any way to reduce the mvn output verbosity? Assuming that we setup Jenkins for nightly/snapshots and that does full j8/j7/android building/testing, I’m content to reduce what’s being done in travis for PR validation. e.g., toss android build, toss j7 test, toss j7 build if also

maven and distribution bundles with transitive deps: licensing

Hi, Can’t we eliminate releasing binary bundles containing transitive deps and in doing so eliminate a huge amount of licensing/notice pain for us? But still supply what users need. As I understand it / ASF policy, the newly generated distribution bundles lack the necessary license/notice

Re: Progress on Maven?

I’ll check the updates, pull down the latest, etc. Thanks! — Dale > On Jul 11, 2017, at 9:51 AM, Christofer Dutz > wrote: > > Hi, > > Ok … so I updated the wiki page and just pushed another update to the pull > request, in which I cleaned up the artifacts and

Re: Progress on Maven?

Ups … that’s already done and finished … at least in the PR :-) I didn’t like the old names as they only confused me… Chris Am 11.07.17, 16:41 schrieb "Dale LaBossiere" : Regarding the table and web socket connector, unless there’s discussion needed, always welcome,

Re: Progress on Maven?

Regarding the table and web socket connector, unless there’s discussion needed, always welcome, please rename the generated artifacts as indicated. Thanks! — Dale > On Jul 11, 2017, at 2:55 AM, Christofer Dutz > wrote: > > Hi Dale, > > Can I treat the last part

Re: Progress on Maven?

Sorry about that: https://paste.apache.org/p/GI0n — Dale > On Jul 11, 2017, at 2:54 AM, Christofer Dutz > wrote: > > Hi Dale, > > Seems the script was stripped from the email … eventually use > https://paste.apache.org/ for that. > > Chris > > Von: Dale

Re: Progress on Maven?

Hi, Ok … so I updated the wiki page and just pushed another update to the pull request, in which I cleaned up the artifacts and directories as wished in the bottom table of the wiki page. Also, I had to fix one or two problems. Now the tests and the apache-release profile seem to be running