Benson Margulies wrote:
I don't see why not, but we'll have to ask. The easiest way it to just
open another ticket.
Hi Benson,
thanks for your quick reply.
In the ticket below, I specified:
Project URL: http://incubator.apache.org/projects/jena.html
SVN URL: http://svn.apache.org/repos/asf/incubator/jena/Jena2/LARQ/
Maven Group Ids: org.apache.jena
LARQ's pom.xml file is here:
http://svn.apache.org/repos/asf/incubator/jena/Jena2/LARQ/trunk/pom.xml
At the time, I was not sure if it was possible to publish SNAPSHOTs
on the Apache Snapshot Repository with a groupId different from
org.apache.jena.
There are multiple modules in the Apache Jena project:
ARQ, Eyeball, Fuseki, IRI, Joseki, SDB, TDB, jena.
They have a variety of groupIds:
- com.hp.hpl.jena
- org.joseki
- org.openjena
Are the credentials to publish artifacts to the Nexus server associated
to the project (i.e. Apache Jena) or are they different, based on the
groupId?
Do we need to open three separate tickets (one per groupId) then?
Paolo
On Wed, Jun 15, 2011 at 10:43 AM, Paolo Castagna
<[email protected]> wrote:
Paolo Castagna wrote:
Benson Margulies wrote:
You you need a ticket. I also recommend switching to the generic ASF
parent POM as a way to setting up this stuff, it will make things
easier when you get to your first release.
Hi Benson,
thanks.
I've just opened a ticket for Jena's LARQ module:
https://issues.apache.org/jira/browse/INFRA-3646
Hi Benson, (hi mentors, hi all),
I am sorry to bother you again, but I have a question.
I opened the ticket above and we are now able to publish
SNAPSHOTs on the Apache Maven repository for Jena modules
which have groupId=org.apache.jena.
Is it possible to publish SNAPSHOTs on the Apache Maven
repository with groupId=com.hp.hpl.jena? So, that we can
start publishing snapshots there, but with the old name
until we decide to change package names?
Thanks,
Paolo
I am not sure about adding com.hp.hpl.jena to the Maven Group Ids...
the documentation says "they should all be subgroups of org.apache".
So, I did not put com.hp.hpl.jena on that ticket and made it specific
to LARQ module only.
Re: parent POM... yep, using it already! ;-)
<parent>
<groupId>org.apache</groupId>
<artifactId>apache</artifactId>
<version>9</version>
</parent>
http://svn.apache.org/repos/asf/incubator/jena/Jena2/LARQ/trunk/pom.xml
Paolo
On Thu, May 19, 2011 at 3:16 AM, Paolo Castagna
<[email protected]> wrote:
Benson Margulies wrote:
Yes, any time. Snapshots are not formally releases and require no
process. Many projects publish them from their Jenkins jobs.
Great, thanks.
I have this in my pom.xml file:
<distributionManagement>
[...]
<snapshotRepository>
<id>apache.snapshots.https</id>
<name>Apache Development Snapshot Repository</name>
<url>https://repository.apache.org/content/repositories/snapshots</url>
</snapshotRepository>
</distributionManagement>
And this in my Maven's settings.xml file:
<server>
<id>apache.snapshots.https</id>
<username>castagna</username>
<password>...</password>
</server>
However, I have a "Authorization failed: Access denied to:..." error.
I think this is because of: "Before a project can use the repository to
release Maven artifacts, it must be configured in Nexus. This is
generally
a quick and easy process. To get setup, create a JIRA ticket here with
the following information [...]"
-- http://www.apache.org/dev/publishing-maven-artifacts.html
I'll go ahead and create a JIRA ticket later.
Thanks,
Paolo
On Wed, May 18, 2011 at 1:55 PM, Paolo Castagna
<[email protected]> wrote:
Hi mentors,
just to double check that my understanding is correct.
Can I go ahead and publish any SNAPSHOT on the Maven Snapshot
repository at Apache [1] at any time?
I am almost ready to try with the LARQ module for which I am
planning to use:
<groupId>org.apache.jena</groupId>
<artifactId>larq</artifactId>
<version>0.2.2-incubating-SNAPSHOT</version>
and inherit from:
<parent>
<groupId>org.apache</groupId>
<artifactId>apache</artifactId>
<version>9</version>
</parent>
Thanks,
Paolo
[1] https://repository.apache.org/content/repositories/snapshots/
