You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Andy Jefferson (JIRA)" <ji...@apache.org> on 2010/10/19 21:03:33 UTC
[jira] Created: (INFRA-3081) Enable Nexus Access For Apache JDO
Enable Nexus Access For Apache JDO
----------------------------------
Key: INFRA-3081
URL: https://issues.apache.org/jira/browse/INFRA-3081
Project: Infrastructure
Issue Type: Task
Security Level: public (Regular issues)
Components: Nexus
Reporter: Andy Jefferson
Assignee: Brian Fox
Priority: Blocker
Project URL: http://db.apache.org/jdo/index.html
SVN URL: http://svn.apache.org/repos/asf/db/jdo
Maven Group Ids: org.apache.jdo, javax.jdo
Managed By This TLP Project: Apache DB (http://db.apache.org/)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-3081) Enable Nexus Access For Apache JDO
Posted by "Andy Jefferson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923450#action_12923450 ]
Andy Jefferson commented on INFRA-3081:
---------------------------------------
Thanks for your fast help on this Brian. I've looked at central and it hasn't made it across (yet); does the lack of a "maven-metadata.xml" in
https://repository.apache.org/content/repositories/releases/javax/jdo/jdo-api/
make a difference to whether it gets synced? The other artifact directories have one
> Enable Nexus Access For Apache JDO
> ----------------------------------
>
> Key: INFRA-3081
> URL: https://issues.apache.org/jira/browse/INFRA-3081
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: Andy Jefferson
> Assignee: Brian Fox
> Priority: Blocker
>
> Project URL: http://db.apache.org/jdo/index.html
> SVN URL: http://svn.apache.org/repos/asf/db/jdo
> Maven Group Ids: org.apache.jdo, javax.jdo
> Managed By This TLP Project: Apache DB (http://db.apache.org/)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (INFRA-3081) Enable Nexus Access For Apache JDO
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox closed INFRA-3081.
----------------------------
Resolution: Fixed
Fixed and verified it's in central:
http://repo1.maven.org/maven2/javax/jdo/jdo-api/3.0/
> Enable Nexus Access For Apache JDO
> ----------------------------------
>
> Key: INFRA-3081
> URL: https://issues.apache.org/jira/browse/INFRA-3081
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: Andy Jefferson
> Assignee: Brian Demers
> Priority: Blocker
>
> Project URL: http://db.apache.org/jdo/index.html
> SVN URL: http://svn.apache.org/repos/asf/db/jdo
> Maven Group Ids: org.apache.jdo, javax.jdo
> Managed By This TLP Project: Apache DB (http://db.apache.org/)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-3081) Enable Nexus Access For Apache JDO
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922935#action_12922935 ]
Brian Fox commented on INFRA-3081:
----------------------------------
This is pretty confusing at the moment.
There are no artifacts in the Apache Maven 2 repo for javax.jdo or org.apache.jdo :
http://people.apache.org/repo/m2-ibiblio-rsync-repository/javax/jdo/ (those are essentially empty)
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/jdo/
Central however does have Maven2 artifacts:
http://repo2.maven.org/maven2/javax/jdo/
http://repo2.maven.org/maven2/org/apache/jdo/
Can you confirm that all of those artifacts in Central belong to the Apache DB project? If so, i'll use that as the source to backfill repository.apache.org.
I haven't yet located the javax.jdo jdo3 artifact as it's not in the old apache repo or central that I see.
> Enable Nexus Access For Apache JDO
> ----------------------------------
>
> Key: INFRA-3081
> URL: https://issues.apache.org/jira/browse/INFRA-3081
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: Andy Jefferson
> Assignee: Brian Fox
> Priority: Blocker
>
> Project URL: http://db.apache.org/jdo/index.html
> SVN URL: http://svn.apache.org/repos/asf/db/jdo
> Maven Group Ids: org.apache.jdo, javax.jdo
> Managed By This TLP Project: Apache DB (http://db.apache.org/)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (INFRA-3081) Enable Nexus Access For Apache JDO
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox closed INFRA-3081.
----------------------------
Resolution: Fixed
Ok i pulled in the pom from the datanucleus link and jdo3 is in the repo and should be synced to central later today.
You can see it here on the repo: https://repository.apache.org/content/repositories/releases/javax/jdo/
> Enable Nexus Access For Apache JDO
> ----------------------------------
>
> Key: INFRA-3081
> URL: https://issues.apache.org/jira/browse/INFRA-3081
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: Andy Jefferson
> Assignee: Brian Fox
> Priority: Blocker
>
> Project URL: http://db.apache.org/jdo/index.html
> SVN URL: http://svn.apache.org/repos/asf/db/jdo
> Maven Group Ids: org.apache.jdo, javax.jdo
> Managed By This TLP Project: Apache DB (http://db.apache.org/)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-3081) Enable Nexus Access For Apache JDO
Posted by "Andy Jefferson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922941#action_12922941 ]
Andy Jefferson commented on INFRA-3081:
---------------------------------------
What used to happen (AFAIK) was that the artifacts (jar, M1 pom) were put in the M1 sync area. Some (Apache Infra?) process used to create the M2 artifacts (or at least the POM) on central ... maybe as part of the sync?. The maven-metadata.xml was the only file generated by the Apache JDO project since the aforementioned automated process didn't handle that part. No idea what this process was but I'd guess Carlos Sanchez would know since he was involved in the past.
The artifacts in Central M2 are for this project, yes.
Future "Apache JDO" releases can (should) be generated using Maven2 since we've had a pom.xml for a while (or at least for the javax.jdo part, and the org.apache.jdo is currently being worked on for the next release), just that this release was done using the Maven1 route.
> Enable Nexus Access For Apache JDO
> ----------------------------------
>
> Key: INFRA-3081
> URL: https://issues.apache.org/jira/browse/INFRA-3081
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: Andy Jefferson
> Assignee: Brian Fox
> Priority: Blocker
>
> Project URL: http://db.apache.org/jdo/index.html
> SVN URL: http://svn.apache.org/repos/asf/db/jdo
> Maven Group Ids: org.apache.jdo, javax.jdo
> Managed By This TLP Project: Apache DB (http://db.apache.org/)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-3081) Enable Nexus Access For Apache JDO
Posted by "Andy Jefferson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922964#action_12922964 ]
Andy Jefferson commented on INFRA-3081:
---------------------------------------
The change in artifactId is intentional (the "2" in jdo2-api was a version really, and ought not have been there, and now we're at JDO 3+ then it was time to fix it).
For a pom.xml from Subversion, look at
http://svn.apache.org/viewvc/db/jdo/trunk/api/pom.xml?revision=946804&view=markup
or look at the DataNucleus M2 repo where we're housing this temporarily for users sho need to use it with DataNucleus.
http://www.datanucleus.org/downloads/maven2/javax/jdo/jdo-api/3.0/
> Enable Nexus Access For Apache JDO
> ----------------------------------
>
> Key: INFRA-3081
> URL: https://issues.apache.org/jira/browse/INFRA-3081
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: Andy Jefferson
> Assignee: Brian Fox
> Priority: Blocker
>
> Project URL: http://db.apache.org/jdo/index.html
> SVN URL: http://svn.apache.org/repos/asf/db/jdo
> Maven Group Ids: org.apache.jdo, javax.jdo
> Managed By This TLP Project: Apache DB (http://db.apache.org/)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (INFRA-3081) Enable Nexus Access For Apache JDO
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox reopened INFRA-3081:
------------------------------
Assignee: Brian Demers (was: Brian Fox)
The metadata was supposed to be rebuilt by Nexus, see why it didn't.
Andy no that isn't a cause of the sync, I'll check on that part separately.
> Enable Nexus Access For Apache JDO
> ----------------------------------
>
> Key: INFRA-3081
> URL: https://issues.apache.org/jira/browse/INFRA-3081
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: Andy Jefferson
> Assignee: Brian Demers
> Priority: Blocker
>
> Project URL: http://db.apache.org/jdo/index.html
> SVN URL: http://svn.apache.org/repos/asf/db/jdo
> Maven Group Ids: org.apache.jdo, javax.jdo
> Managed By This TLP Project: Apache DB (http://db.apache.org/)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-3081) Enable Nexus Access For Apache JDO
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922953#action_12922953 ]
Brian Fox commented on INFRA-3081:
----------------------------------
Ok the artifacts are imported from central to the repo and the project is all setup.
The jdo 3 artifacts are not pulled in. I notice that the artifactid changed from jdo2-api to jdo-api, was that intentional? Then I checked the pom to see what was up but this is an M1 pom. Do you have any M2 poms for this artifact? Now is the time to fix it because it doesn't yet exist in any m2 repo officially so there will be no trouble caused by changing it around.
> Enable Nexus Access For Apache JDO
> ----------------------------------
>
> Key: INFRA-3081
> URL: https://issues.apache.org/jira/browse/INFRA-3081
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: Andy Jefferson
> Assignee: Brian Fox
> Priority: Blocker
>
> Project URL: http://db.apache.org/jdo/index.html
> SVN URL: http://svn.apache.org/repos/asf/db/jdo
> Maven Group Ids: org.apache.jdo, javax.jdo
> Managed By This TLP Project: Apache DB (http://db.apache.org/)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.