Bugzilla – Full Text Bug Listing
| Summary: | Make the fwk available in Maven Central | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Technology] Dash | Reporter: | Pascal Rapicault <pascal> | ||||||
| Component: | Maven | Assignee: | Project Dash Incoming bugs <dash-inbox> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||
| Severity: | enhancement | ||||||||
| Priority: | P3 | CC: | digulla, d_a_carver, irbull, mober.at+eclipse, pwebster, remy.suen, thanh.ha, tjwatson, wayne.beaton | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Pascal Rapicault
See also bug 337068 PW The link to the testing repo: http://maven.eclipse.org/nexus/content/repositories/testing/org/eclipse/osgi/org.eclipse.osgi/3.6.2/ PW I am confused on who owns this bug and who is responsible for publishing the artifacts to maven.eclipse.org? Also, have we changed to scope of this bug from publishing to Maven Central to publishing to maven.eclipse.org? I'm adding Aarron to this bug as well as he was working on an automatic conversion. BTW, the first step is to publish to maven.eclipse.org. There are some requirements that the POMs need to meet in order to make it into Maven Central. I do think that going to Maven Central should be the ultimate goal, but the first step is to get things into maven.eclipse.org. I will create a pom file for equinox and attach it there when available. Created attachment 198939 [details]
Pom file for equinox released with Indigo SR0
Attached is the pom file for the equinox framework.
I did not find a way to specify a tag in the CVS connection and the CVS view was busted so I could not get the right URL but I think it is fine for now.
To be compliant with the Central rules, we are missing the developers.
(In reply to comment #7) > Created attachment 198939 [details] > Pom file for equinox released with Indigo SR0 > > Attached is the pom file for the equinox framework. > I did not find a way to specify a tag in the CVS connection and the CVS view > was busted so I could not get the right URL but I think it is fine for now. > To be compliant with the Central rules, we are missing the developers. Does the Eclipse-SourceReferences header give a hint at what the correct URL should be: Eclipse-SourceReferences = scm:cvs:pserver:dev.eclipse.org:/cvsroot/rt:org.eclipse.equinox/framework/bundles/org.eclipse.osgi;tag=v20110613 Seems a ;tag=XXX can be put on the end there. Not sure if that is simply a convention for the Eclipse-SourceReferences header or not though. For developers should we list all the active commiters? (In reply to comment #8) > Does the Eclipse-SourceReferences header give a hint at what the correct URL > should be: > > Eclipse-SourceReferences = > scm:cvs:pserver:dev.eclipse.org:/cvsroot/rt:org.eclipse.equinox/framework/bundles/org.eclipse.osgi;tag=v20110613 > > Seems a ;tag=XXX can be put on the end there. Not sure if that is simply a > convention for the Eclipse-SourceReferences header or not though. For > developers should we list all the active commiters? Here's the maven definition: http://maven.apache.org/scm/cvs.html It doesn't seem to include a tag, unless you can put that in the CVS command line section like <r>v20110630-1800</r> ... but it's not clear what data that section accepts. PW (In reply to comment #9) > (In reply to comment #8) > > Does the Eclipse-SourceReferences header give a hint at what the correct URL > > should be: > > > > Eclipse-SourceReferences = > > scm:cvs:pserver:dev.eclipse.org:/cvsroot/rt:org.eclipse.equinox/framework/bundles/org.eclipse.osgi;tag=v20110613 > > > > Seems a ;tag=XXX can be put on the end there. Not sure if that is simply a > > convention for the Eclipse-SourceReferences header or not though. For > > developers should we list all the active commiters? > > Here's the maven definition: > http://maven.apache.org/scm/cvs.html > > It doesn't seem to include a tag, unless you can put that in the CVS command > line section like <r>v20110630-1800</r> ... but it's not clear what data that > section accepts. There is a tag element you can use as well under the <scm> </scm> entry: <tag>v20110630-1800</tag> http://maven.apache.org/scm/maven-scm-plugin/tag-mojo.html (In reply to comment #7) > Created attachment 198939 [details] > Pom file for equinox released with Indigo SR0 > > Attached is the pom file for the equinox framework. > I did not find a way to specify a tag in the CVS connection and the CVS view > was busted so I could not get the right URL but I think it is fine for now. > To be compliant with the Central rules, we are missing the developers. A suggestion, you may also want to inherrit from the eclipse-parent pom. It contains additional information such as license, CI system, issue tracking location, etc. An example of the CVS tag entry can be found in this article: http://java.dzone.com/articles/automating-releases-maven-0 Created attachment 199012 [details]
Better pom
Here is a better pom with CVS tag, developer list and parent pom.
I'm not sure the parent pom is a necessity / good thing since we have not used it to build equinox.
maven.eclipse.org was decommissioned via bug 405750 and replaced with repo.eclipse.org. See: https://wiki.eclipse.org/Services/Nexus |