[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-tabpanel=17478818#comment-17478818
]
Markus Schuch edited comment on CONNECTORS-1105 at 1/19/22, 5:02 PM:
-
{quote}Trying to search in the Apache Maven repo it seems that we have
2.14-SNAPSHOT published:
{quote}
Yes. I was able to publish those with the setup described here. Then i lost
focus, while waiting for edit permissions in the wiki .
Now that I think about it again, I have the feeling we have yet to talk about
what the artifacts we would deploy to Maven Central represent. The Maven
artifacts are obviously not binary identical to the artifacts from the Ant
build, but worse, there could also be discrepancies in terms of dependencies
describe by the published POMs because we don't ensure that the versions of all
dependencies are in sync between build.xml and pom.xml files.
What do you think about releasing the Maven artifacts in this state? I think we
should first take a step back and first formulate the problem we are trying to
solve here more precisely.
was (Author: schuchm):
{quote}Trying to search in the Apache Maven repo it seems that we have
2.14-SNAPSHOT published:
{quote}
Yes. I was able to publish those with the setup described here. Then i lost
focus, while waiting for edit permissions in the wiki .
Now that I think about it again, I have the feeling we have yet to talk about
what the artifacts we would deploy to Maven Central represent. The Maven
artifacts are logically not binary identical to the artifacts from the Ant
build, but worse, there could also be discrepancies in terms of dependencies
because we don't ensure that the versions of all dependencies are in sync
between build.xml and pom.xml files.
What do you think about releasing the Maven artifacts in this state? I think we
should first take a step back and first formulate the problem we are trying to
solve here more precisely.
> 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: Markus Schuch
>Priority: Major
> Fix For: ManifoldCF next
>
>
> 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
(v8.20.1#820001)
[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-tabpanel=17478818#comment-17478818
]
Markus Schuch edited comment on CONNECTORS-1105 at 1/19/22, 5:01 PM:
-
{quote}Trying to search in the Apache Maven repo it seems that we have
2.14-SNAPSHOT published:
{quote}
Yes. I was able to publish those with the setup described here. Then i lost
focus, while waiting for edit permissions in the wiki .
Now that I think about it again, I have the feeling we have yet to talk about
what the artifacts we would deploy to Maven Central represent. The Maven
artifacts are logically not binary identical to the artifacts from the Ant
build, but worse, there could also be discrepancies in terms of dependencies
because we don't ensure that the versions of all dependencies are in sync
between build.xml and pom.xml files.
What do you think about releasing the Maven artifacts in this state? I think we
should first take a step back and first formulate the problem we are trying to
solve here more precisely.
was (Author: schuchm):
{quote}Trying to search in the Apache Maven repo it seems that we have
2.14-SNAPSHOT published:
{quote}
Yes. I was able to publish those with the setup described here. Then i lost
focus, while waiting for edit permissions in the wiki .
Now that I think about it again, I have the feeling we have yet to talk about
what the artifacts we would deploy to Maven Central represent. The Maven
artifacts are logically not binary identical to the artifacts from the Ant
build, but worse, there could also be discrepancies in terms of dependencies
because we don't ensure that the versions of all dependencies are in sync
between build.xml and pom.xml files.
What do you think about releasing the Maven artifacts in this state? I think we
should first take a step back and first formulate the problem we are trying to
solve here more precisely.
> 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: Markus Schuch
>Priority: Major
> Fix For: ManifoldCF next
>
>
> 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
(v8.20.1#820001)
[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-tabpanel=16921716#comment-16921716 ] Markus Schuch edited comment on CONNECTORS-1105 at 9/3/19 8:56 PM: --- The referred wiki pages are * [https://cwiki.apache.org/confluence/display/CONNECTORS/Release+Process] * [https://cwiki.apache.org/confluence/display/CONNECTORS/Distributing+Releases] I will write up the steps there. was (Author: schuchm): The referred wiki pages are * [https://cwiki.apache.org/confluence/display/CONNECTORS/Release+Process] * [https://cwiki.apache.org/confluence/display/CONNECTORS/Distributing+Releases] I will write up the steps there. > 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: Markus Schuch >Priority: Major > Fix For: ManifoldCF next > > > 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 (v8.3.2#803003)
[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-tabpanel=16906581#comment-16906581
]
Markus Schuch edited comment on CONNECTORS-1105 at 8/13/19 8:22 PM:
I am resuming this and try to find out how to fix the {{forbidden}} error right
now.
was (Author: schuchm):
I am resuming this and try to find out how to fix the 401 error right now.
> 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
>Priority: Major
> Fix For: ManifoldCF next
>
>
> 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
(v7.6.14#76016)
[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] [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)
