[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229520#comment-14229520 ] Maurizio Pillitu commented on CONNECTORS-1105: -- I'll try this week and report back on this issue. Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229554#comment-14229554 ] Maurizio Pillitu commented on CONNECTORS-1105: -- First feedback: 1. Instead of targeting Maven Central, I'd follow Apache guidelines and deploy into https://repository.apache.org/index.html ; the repo is public and easily accessible; as soon as we have a proper deployment/release process, we can decide to sync with Maven Central (just a matter of overriding some configurations) 2. org.apache.apache (http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache%22%20AND%20a%3A%22apache%22) Maven Parent POM already provides all configurations needed to run a Maven deployment/release On rev. 1642650 I've updated org.apache.apache version to 16. To run a deployment you can simply run [noformat]mvn deploy -Papache-release[noformat] Currently it fails with the following error [noformat] Could not transfer artifact org.apache.manifoldcf:mcf-parent:pom:2.0-20141201.084714-1 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots): Failed to transfer file: https://repository.apache.org/content/repositories/snapshots/org/apache/manifoldcf/mcf-parent/2.0-SNAPSHOT/mcf-parent-2.0-20141201.084714-1.pom. Return code is: 401, ReasonPhrase: Unauthorized. - [Help 1] [noformat] I will investigate on how to get write access to repository.apache.org Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229554#comment-14229554 ] Maurizio Pillitu edited comment on CONNECTORS-1105 at 12/1/14 8:55 AM: --- First feedback: 1. Instead of targeting Maven Central, I'd follow Apache guidelines and deploy into https://repository.apache.org/index.html ; the repo is public and easily accessible; as soon as we have a proper deployment/release process, we can decide to sync with Maven Central (just a matter of overriding some configurations) 2. org.apache.apache (http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache%22%20AND%20a%3A%22apache%22) Maven Parent POM already provides all configurations needed to run a Maven deployment/release On rev. 1642650 I've updated org.apache.apache version to 16. To run a deployment you can simply run {noformat}mvn deploy -Papache-release{noformat} Currently it fails with the following error {noformat} Could not transfer artifact org.apache.manifoldcf:mcf-parent:pom:2.0-20141201.084714-1 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots): Failed to transfer file: https://repository.apache.org/content/repositories/snapshots/org/apache/manifoldcf/mcf-parent/2.0-SNAPSHOT/mcf-parent-2.0-20141201.084714-1.pom. Return code is: 401, ReasonPhrase: Unauthorized. - [Help 1] {noformat} I will investigate on how to get write access to repository.apache.org was (Author: maoo): First feedback: 1. Instead of targeting Maven Central, I'd follow Apache guidelines and deploy into https://repository.apache.org/index.html ; the repo is public and easily accessible; as soon as we have a proper deployment/release process, we can decide to sync with Maven Central (just a matter of overriding some configurations) 2. org.apache.apache (http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache%22%20AND%20a%3A%22apache%22) Maven Parent POM already provides all configurations needed to run a Maven deployment/release On rev. 1642650 I've updated org.apache.apache version to 16. To run a deployment you can simply run [noformat]mvn deploy -Papache-release[noformat] Currently it fails with the following error [noformat] Could not transfer artifact org.apache.manifoldcf:mcf-parent:pom:2.0-20141201.084714-1 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots): Failed to transfer file: https://repository.apache.org/content/repositories/snapshots/org/apache/manifoldcf/mcf-parent/2.0-SNAPSHOT/mcf-parent-2.0-20141201.084714-1.pom. Return code is: 401, ReasonPhrase: Unauthorized. - [Help 1] [noformat] I will investigate on how to get write access to repository.apache.org Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229560#comment-14229560 ] Maurizio Pillitu commented on CONNECTORS-1105: -- Simply adding the following in ~/.m2/settings.xml solved the issue; every Apache committer has granted access on repository.apache.org {noformat} servers server idapache.snapshots.https/id usernamemaoo/username passwordmy_pwd/password /server /servers {noformat} Unfortunately it seems that I don't have enough karma to write on it; I'll keep on investigating. {noformat} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project mcf-parent: Failed to deploy artifacts: Could not transfer artifact org.apache.manifoldcf:mcf-parent:pom:2.0-20141201.090528-1 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots): Access denied to: https://repository.apache.org/content/repositories/snapshots/org/apache/manifoldcf/mcf-parent/2.0-SNAPSHOT/mcf-parent-2.0-20141201.090528-1.pom, ReasonPhrase: Forbidden. {noformat} Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229570#comment-14229570 ] Maurizio Pillitu commented on CONNECTORS-1105: -- Great documentation published here - http://www.apache.org/dev/publishing-maven-artifacts.html I think that I've followed all instructions needed; I'll check again and - if still blocked - contact in...@apache.org Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229571#comment-14229571 ] Karl Wright commented on CONNECTORS-1105: - Hi Maurizio, So the maven target of mvn deploy should be sufficient to deliver all the ManifoldCF jars and wars? Also, what about signing the jars? Unless there's magic in Maven that interacts with gpg, I can't see how that would work automatically. Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229583#comment-14229583 ] Maurizio Pillitu commented on CONNECTORS-1105: -- All signing/deployment/release logic is part of the org.apache.apache parent; you need some local setups that are explained here - http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env During mvn install, you'll be prompted with your gpg passphrase, so that your artifacts will be signed before being upped. Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229585#comment-14229585 ] Karl Wright commented on CONNECTORS-1105: - The documentation says, in part: Note: Be sure that the generated artifacts respect the Apache release rules : NOTICE and LICENSE files should be present in the META-INF directory within the jar. For -sources artifacts, be sure that your POM does not use the maven-source-plugin:2.0.3 which is broken. I don't believe we even invoke the source plugin at this time. I would think we should? Also: This makes me think we need to nail down our release process, if it now includes Maven: {quote} 3 - Prepare the release mvn release:clean mvn release:prepare Note: Preparing the release will create the new tag in SVN, automatically checking in on your behalf. Note: If you're located in Europe then release:prepare may fail with 'Unable to tag SCM' and ' svn: No such revision X '. Wait 10 seconds and run mvn release:prepare again. 4 - Stage the release for a vote mvn release:perform The release will automatically be inserted into a temporary staging repository for you. See the Nexus staging documentation for full details. Now you must close the staging repository to indicate to Nexus that the build is done and to make the artifacts available. Follow the steps in Closing the Staged Repository to close your new repository, this will allow your community to VOTE on the staged atrifacts. {quote} Since our primary release artifacts are built with ant, and that is not changing, seems to me that our release scripts should be modified to include maven release prep and staging as well (but NOT tagging). What do you think? Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229597#comment-14229597 ] Karl Wright commented on CONNECTORS-1105: - Ah, ok, the parent pom apparently does a source release too. Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229598#comment-14229598 ] Karl Wright commented on CONNECTORS-1105: - And I get the same error that you do: {code} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project mcf-parent: Failed to deploy artifacts: Could not transfer artifact org.apache.manifoldcf:mcf-parent:pom:2.0-20141201.094239-1 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots): Access denied to: https://repository.apache.org/content/repositories/snapshots/org/apache/manifoldcf/mcf-parent/2.0-SNAPSHOT/mcf-parent-2.0-20141201.094239-1.pom, ReasonPhrase: Forbidden. - [Help 1] {code} Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229604#comment-14229604 ] Maurizio Pillitu commented on CONNECTORS-1105: -- Re. the maven-source-plugin, all configuration needed is part of the org.apache.apache parent pom; however, since version wasn't forced, I just added the following in our root pluginManagement section (rev. 1642658) {noformat} plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-source-plugin/artifactId version2.4/version /plugin {noformat} Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229607#comment-14229607 ] Karl Wright commented on CONNECTORS-1105: - I pulled up both pom changes to dev_1x branch. Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229669#comment-14229669 ] Karl Wright commented on CONNECTORS-1105: - I bet I know what the problem is: {code} 12/01/2014 04:48 AM 989,356,977 mcf-parent-2.0-SNAPSHOT-source-release.zip {code} Apache generally does not accept uploads in excess of 100M without special arrangements. We're 10x that size. What's more, it is clear that the source release is including jars and class files from the ant build. So, we will need local configuration for the source build, no question. Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229681#comment-14229681 ] Maurizio Pillitu commented on CONNECTORS-1105: -- I don't see any advantage of uploading that big zip file (since it's a ZIP file of what you can find in the SVN tag created by the release process). We could try to disable the configuration of the maven-assembly-plugin (inherited by apache parent). Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229681#comment-14229681 ] Maurizio Pillitu edited comment on CONNECTORS-1105 at 12/1/14 11:26 AM: I don't see any advantage of uploading that big zip file (since it's a ZIP file of what you can find in the SVN tag created by the release process). We could try to disable the configuration of the maven-assembly-plugin (inherited by apache parent). Nevertheless, reading your and my error messages, seems that it's failing trying to upload a .pom file, that should be few kbs. IMO the current issue is not caused by file size issue, there's something more. was (Author: maoo): I don't see any advantage of uploading that big zip file (since it's a ZIP file of what you can find in the SVN tag created by the release process). We could try to disable the configuration of the maven-assembly-plugin (inherited by apache parent). Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229738#comment-14229738 ] Karl Wright commented on CONNECTORS-1105: - I agree. Nevertheless, I played around a bit with configuring the assembly plugin locally, and committed that: r1642673. While I now create new source jars that have essentially the right things in them, this still does not disable the huge source release zip from being built or uploaded though: {code} Directory of C:\wip\mcf\trunk\target 12/01/2014 07:39 AMDIR . 12/01/2014 07:39 AMDIR .. 12/01/2014 07:38 AM30 .plxarc 12/01/2014 07:38 AMDIR archive-tmp 12/01/2014 07:38 AMDIR maven-shared-archive-resources 12/01/2014 07:39 AM 989,360,057 mcf-parent-2.0-SNAPSHOT-source-release.zip 12/01/2014 07:39 AM 851 mcf-parent-2.0-SNAPSHOT-source-release.zip.asc 12/01/2014 07:38 AM49,707,981 mcf-parent-2.0-SNAPSHOT-src.tar.gz 12/01/2014 07:39 AM 851 mcf-parent-2.0-SNAPSHOT-src.tar.gz.asc 12/01/2014 07:38 AM52,086,214 mcf-parent-2.0-SNAPSHOT-src.zip 12/01/2014 07:39 AM 851 mcf-parent-2.0-SNAPSHOT-src.zip.asc 12/01/2014 07:39 AM 8,529 mcf-parent-2.0-SNAPSHOT.pom 12/01/2014 07:39 AM 851 mcf-parent-2.0-SNAPSHOT.pom.asc {code} Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229788#comment-14229788 ] Karl Wright commented on CONNECTORS-1105: - I tried overriding the source-release assembly, using my src assembly contents instead, but that didn't work. I get: {code} [WARNING] The assembly id source-release is used more than once. {code} ... but although there is only one zip produced then, it includes far more files than my assembly description dictates. Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229800#comment-14229800 ] Karl Wright commented on CONNECTORS-1105: - Maven is quite a bit of black magic and voodoo for me still; the documentation for the assembly plugin is not great and doesn't say how you might override parent assembly configuration. But it does have this in the example: {code} executions execution idmake-assembly/id !-- this is used for inheritance merges -- phasepackage/phase !-- bind to the packaging phase -- goals goalsingle/goal /goals /execution /executions {code} ... but I don't understand what it does really. Any ideas? See: http://maven.apache.org/plugins/maven-assembly-plugin/usage.html Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229886#comment-14229886 ] Karl Wright commented on CONNECTORS-1105: - Ok, after consulting a maven expert, I found out that the parent pom allows the definition of the source assembly to be overwritten, using the following property: {code} sourceReleaseAssemblyDescriptorassembly_name/sourceReleaseAssemblyDescriptor {code} Unfortunately, there still does not seem to be any way to *define* the assembly name in a way that the parent pom allows access to it. The following does NOT work: {code} plugin artifactIdmaven-assembly-plugin/artifactId version2.5.2/version configuration descriptors descriptorsrc/main/assembly/src.xml/descriptor /descriptors !-- tarLongFileModegnu/tarLongFileMode -- /configuration /plugin {code} In this case, if src.xml defines the ID 'mcfsrc', and the property above also says 'mcfsrc', it nonetheless gives an error that it can't find assembly ID 'mcfsrc'. Hmm. I also determined that there is no way to completely disable the source generation without changing the parent pom. Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14230045#comment-14230045 ] Karl Wright commented on CONNECTORS-1105: - We also tried including an apache-release profile in the MCF root pom. This executed but did *not* override the profile definition in the parent pom. So no joy there. At this point I think perhaps the best approach would be to forget about using any parent pom targets/profiles, and instead copy what we need out of that parent pom, modifying it to suit MCF's requirements. Maurizio, do you agree? Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14230066#comment-14230066 ] Karl Wright commented on CONNECTORS-1105: - I've added a mcf-specific profile to use in doing releases. r1642716. The profile name is: apache-mcf-release. This seems to solve the problem of building a gigantic src release artifact at least. Still can't upload to staging repository though. Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14230070#comment-14230070 ] Maurizio Pillitu commented on CONNECTORS-1105: -- We can simply copy the apache-release profile of https://repository.apache.org/service/local/repositories/releases/content/org/apache/apache/16/apache-16.pom into the ManifoldCF root pom.xml and call it release, changing only the assembly plugin part. I'll give it a try and keep you posted. Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14230074#comment-14230074 ] Karl Wright commented on CONNECTORS-1105: - Maurizio, That's what I just did. Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14230108#comment-14230108 ] Maurizio Pillitu commented on CONNECTORS-1105: -- I see that our comment crossed (as it took me more than 3mins to write my comment :-) ) and we ended up with the same solution. Re. the forbidden issue, I think we can write to reposit...@apache.org and ask for support. Shall I proceed? Thanks. Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maurizio Pillitu updated CONNECTORS-1105: - Comment: was deleted (was: We can simply copy the apache-release profile of https://repository.apache.org/service/local/repositories/releases/content/org/apache/apache/16/apache-16.pom into the ManifoldCF root pom.xml and call it release, changing only the assembly plugin part. I'll give it a try and keep you posted.) Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-853) Japanese end-user-documentation needs to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14230771#comment-14230771 ] Mingchun Zhao commented on CONNECTORS-853: -- Hi Karl, Got it, Let me look into this. Japanese end-user-documentation needs to be updated --- Key: CONNECTORS-853 URL: https://issues.apache.org/jira/browse/CONNECTORS-853 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 1.5 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF next Japanese end-user-documentation needs to be updated to cover the new features of 1.5. Some new screen shots are needed too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CONNECTORS-1052) Invoking mvn from ant
[ https://issues.apache.org/jira/browse/CONNECTORS-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-1052: --- Fix Version/s: (was: ManifoldCF 2.0) ManifoldCF next Invoking mvn from ant - Key: CONNECTORS-1052 URL: https://issues.apache.org/jira/browse/CONNECTORS-1052 Project: ManifoldCF Issue Type: Improvement Components: Alfresco connector, Build Reporter: Shinichiro Abe Assignee: Shinichiro Abe Fix For: ManifoldCF next Using ant 'test', AlfrescoConnector test is ignored. Because ant doesn't call 'mvn package' at test-materials/alfresco-war and copy the war to proper test dir. It would be nice if we could call mvn command from ant, including compile jars and test. Currently, this test is skipped when we use ant. {noformat} $ ant make-core-deps make-deps build test Or $ cd connectors/alfresco $ ant run-IT-HSQLDB ... pretest-warn: [echo] Alfresco Connector integration tests cannot be be performed without alfresco.war {noformat} Also, it seems there is a difference between build.xml and pom.xml about test content(alfresco war/client version). I'm not sure what is correct. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1105) Add maven delivery targets to poms
[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14231058#comment-14231058 ] Karl Wright commented on CONNECTORS-1105: - bq. Re. the forbidden issue, I think we can write to reposit...@apache.org and ask for support. Shall I proceed? Please, feel free. Add maven delivery targets to poms -- Key: CONNECTORS-1105 URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 1.8 Reporter: Karl Wright Assignee: Maurizio Pillitu Fix For: ManifoldCF 2.0 We've been asked to deliver mcf jars and wars to maven central repository by some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)