apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vrozov <...@git.apache.org>
Subject [GitHub] incubator-apex-core pull request: APEX-190 Replace Maven group and...
Date Tue, 13 Oct 2015 00:25:55 GMT
Github user vrozov commented on a diff in the pull request:

    https://github.com/apache/incubator-apex-core/pull/111#discussion_r41815875
  
    --- Diff: pom.xml ---
    @@ -18,13 +18,12 @@
         specific language governing permissions and limitations
         under the License.
     
    --->
    -<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    +--><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
       <modelVersion>4.0.0</modelVersion>
     
    --- End diff --
    
    I guess that if there are conflicts with the Apache parent pom it may indicate compliance
issue on the Apex side. Will it be better to resolve it, rather than going unnoticed?
    
    Do we need to include LICENSE and NOTICE into apex jars? There is no consistency among
Apache projects, but it seems that Apache prefers it to be included.
     


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message