1:07 p.m.
Migrate existing Nexus Audit information to standard XML format
---------------------------------------------------------------
Key: JBBUILD-670
URL: https://issues.jboss.org/browse/JBBUILD-670
Project: JBoss Build System
Issue Type: Task
Reporter: Paul Gier
Assignee: John Casey
Fix For: Build Support 2011
We currently have audit information (username, timestamp) stored in .json files in the
repository. Nexus uses an XML format to store this information, and recent versions of
Nexus allow easy way to view this information in the Nexus UI. The existing audit
information should be migrated to the standard Nexus XML format.
These XML files are located in the directory
"sonatype-work/nexus/proxy/attributes". For each file in each Maven repository
hosted by Nexus, there is a file with the same name in this attributes directory. For
example,
"sonatype-work/nexus/proxy/attributes/jboss-releases/org/jboss/javaee/jboss-servlet-api/2.5.0.GA/jboss-servlet-api-2.5.0.GA.jar"
is actually an XML file containing the attributes for the named jar file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:09 p.m.
New subject: [JBoss JIRA] Updated: (JBBUILD-670) Migrate existing Nexus Audit information to standard XML format
[
https://issues.jboss.org/browse/JBBUILD-670?page=com.atlassian.jira.plugi...
]
Paul Gier updated JBBUILD-670:
------------------------------
Attachment: jboss-servlet-api-2.5.0.GA.jar
jboss-test-1.1.6-SNAPSHOT.pom.md5
Migrate existing Nexus Audit information to standard XML format
---------------------------------------------------------------
Key: JBBUILD-670
URL: https://issues.jboss.org/browse/JBBUILD-670
Project: JBoss Build System
Issue Type: Task
Reporter: Paul Gier
Assignee: John Casey
Fix For: Build Support 2011
Attachments: jboss-servlet-api-2.5.0.GA.jar, jboss-test-1.1.6-SNAPSHOT.pom.md5
We currently have audit information (username, timestamp) stored in .json files in the
repository. Nexus uses an XML format to store this information, and recent versions of
Nexus allow easy way to view this information in the Nexus UI. The existing audit
information should be migrated to the standard Nexus XML format.
These XML files are located in the directory
"sonatype-work/nexus/proxy/attributes". For each file in each Maven repository
hosted by Nexus, there is a file with the same name in this attributes directory. For
example,
"sonatype-work/nexus/proxy/attributes/jboss-releases/org/jboss/javaee/jboss-servlet-api/2.5.0.GA/jboss-servlet-api-2.5.0.GA.jar"
is actually an XML file containing the attributes for the named jar file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:16 p.m.
New subject: [JBoss JIRA] Updated: (JBBUILD-670) Migrate existing Nexus Audit information to standard XML format
[
https://issues.jboss.org/browse/JBBUILD-670?page=com.atlassian.jira.plugi...
]
Paul Gier updated JBBUILD-670:
------------------------------
Description:
We currently have audit information (username, timestamp) stored in .json files in the
repository. Nexus uses an XML format to store this information, and recent versions of
Nexus allow easy way to view this information in the Nexus UI. The existing audit
information should be migrated to the standard Nexus XML format.
These XML files are located in the directory
"sonatype-work/nexus/proxy/attributes". For each file in each Maven repository
hosted by Nexus, there is a file with the same name in this attributes directory. For
example,
"sonatype-work/nexus/proxy/attributes/jboss-releases/org/jboss/javaee/jboss-servlet-api/2.5.0.GA/jboss-servlet-api-2.5.0.GA.jar"
is actually an XML file containing the attributes for the named jar file.
Note: even though the files end with ".jar" or ".md5", they are
actually XML files.
The artifacts that were released before the original Nexus migration do not include a
username in the XML file, although they do include a timestamp. This appears to be the
file creation date. In the migration, these timestamps should be overwritten if
possible.
1. Check whether the user field exists for a given file.
2. If it does not exist, copy the username and timestamp fields to the Nexus attribute
file.
was:
We currently have audit information (username, timestamp) stored in .json files in the
repository. Nexus uses an XML format to store this information, and recent versions of
Nexus allow easy way to view this information in the Nexus UI. The existing audit
information should be migrated to the standard Nexus XML format.
These XML files are located in the directory
"sonatype-work/nexus/proxy/attributes". For each file in each Maven repository
hosted by Nexus, there is a file with the same name in this attributes directory. For
example,
"sonatype-work/nexus/proxy/attributes/jboss-releases/org/jboss/javaee/jboss-servlet-api/2.5.0.GA/jboss-servlet-api-2.5.0.GA.jar"
is actually an XML file containing the attributes for the named jar file.
Migrate existing Nexus Audit information to standard XML format
---------------------------------------------------------------
Key: JBBUILD-670
URL: https://issues.jboss.org/browse/JBBUILD-670
Project: JBoss Build System
Issue Type: Task
Reporter: Paul Gier
Assignee: John Casey
Fix For: Build Support 2011
Attachments: jboss-servlet-api-2.5.0.GA.jar, jboss-test-1.1.6-SNAPSHOT.pom.md5
We currently have audit information (username, timestamp) stored in .json files in the
repository. Nexus uses an XML format to store this information, and recent versions of
Nexus allow easy way to view this information in the Nexus UI. The existing audit
information should be migrated to the standard Nexus XML format.
These XML files are located in the directory
"sonatype-work/nexus/proxy/attributes". For each file in each Maven repository
hosted by Nexus, there is a file with the same name in this attributes directory. For
example,
"sonatype-work/nexus/proxy/attributes/jboss-releases/org/jboss/javaee/jboss-servlet-api/2.5.0.GA/jboss-servlet-api-2.5.0.GA.jar"
is actually an XML file containing the attributes for the named jar file.
Note: even though the files end with ".jar" or ".md5", they are
actually XML files.
The artifacts that were released before the original Nexus migration do not include a
username in the XML file, although they do include a timestamp. This appears to be the
file creation date. In the migration, these timestamps should be overwritten if
possible.
1. Check whether the user field exists for a given file.
2. If it does not exist, copy the username and timestamp fields to the Nexus attribute
file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:17 p.m.
New subject: [JBoss JIRA] Updated: (JBBUILD-670) Migrate existing Nexus Audit information to standard XML format
[
https://issues.jboss.org/browse/JBBUILD-670?page=com.atlassian.jira.plugi...
]
Paul Gier updated JBBUILD-670:
------------------------------
Assignee: Paul Gier (was: John Casey)
Migrate existing Nexus Audit information to standard XML format
---------------------------------------------------------------
Key: JBBUILD-670
URL: https://issues.jboss.org/browse/JBBUILD-670
Project: JBoss Build System
Issue Type: Task
Reporter: Paul Gier
Assignee: Paul Gier
Fix For: Build Support 2011
Attachments: jboss-servlet-api-2.5.0.GA.jar, jboss-test-1.1.6-SNAPSHOT.pom.md5
We currently have audit information (username, timestamp) stored in .json files in the
repository. Nexus uses an XML format to store this information, and recent versions of
Nexus allow easy way to view this information in the Nexus UI. The existing audit
information should be migrated to the standard Nexus XML format.
These XML files are located in the directory
"sonatype-work/nexus/proxy/attributes". For each file in each Maven repository
hosted by Nexus, there is a file with the same name in this attributes directory. For
example,
"sonatype-work/nexus/proxy/attributes/jboss-releases/org/jboss/javaee/jboss-servlet-api/2.5.0.GA/jboss-servlet-api-2.5.0.GA.jar"
is actually an XML file containing the attributes for the named jar file.
Note: even though the files end with ".jar" or ".md5", they are
actually XML files.
The artifacts that were released before the original Nexus migration do not include a
username in the XML file, although they do include a timestamp. This appears to be the
file creation date. In the migration, these timestamps should be overwritten if
possible.
1. Check whether the user field exists for a given file.
2. If it does not exist, copy the username and timestamp fields to the Nexus attribute
file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:24 p.m.
New subject: [JBoss JIRA] Commented: (JBBUILD-670) Migrate existing Nexus Audit information to standard XML format
[
https://issues.jboss.org/browse/JBBUILD-670?page=com.atlassian.jira.plugi...
]
Paul Gier commented on JBBUILD-670:
-----------------------------------
A wiki page has been created containing some notes about the audit migration.
http://community.jboss.org/docs/DOC-16668
Migrate existing Nexus Audit information to standard XML format
---------------------------------------------------------------
Key: JBBUILD-670
URL: https://issues.jboss.org/browse/JBBUILD-670
Project: JBoss Build System
Issue Type: Task
Reporter: Paul Gier
Assignee: Paul Gier
Fix For: Build Support 2011
Attachments: jboss-servlet-api-2.5.0.GA.jar, jboss-test-1.1.6-SNAPSHOT.pom.md5
We currently have audit information (username, timestamp) stored in .json files in the
repository. Nexus uses an XML format to store this information, and recent versions of
Nexus allow easy way to view this information in the Nexus UI. The existing audit
information should be migrated to the standard Nexus XML format.
These XML files are located in the directory
"sonatype-work/nexus/proxy/attributes". For each file in each Maven repository
hosted by Nexus, there is a file with the same name in this attributes directory. For
example,
"sonatype-work/nexus/proxy/attributes/jboss-releases/org/jboss/javaee/jboss-servlet-api/2.5.0.GA/jboss-servlet-api-2.5.0.GA.jar"
is actually an XML file containing the attributes for the named jar file.
Note: even though the files end with ".jar" or ".md5", they are
actually XML files.
The artifacts that were released before the original Nexus migration do not include a
username in the XML file, although they do include a timestamp. This appears to be the
file creation date. In the migration, these timestamps should be overwritten if
possible.
1. Check whether the user field exists for a given file.
2. If it does not exist, copy the username and timestamp fields to the Nexus attribute
file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:07 p.m.
New subject: [JBoss JIRA] Updated: (JBBUILD-670) Migrate existing Nexus Audit information to standard XML format
[
https://issues.jboss.org/browse/JBBUILD-670?page=com.atlassian.jira.plugi...
]
Paul Gier updated JBBUILD-670:
------------------------------
Priority: Critical (was: Major)
Marking this as critical since it is blocking correct generation of the Nexus index
files.
https://issues.sonatype.org/browse/NEXUS-4187
Migrate existing Nexus Audit information to standard XML format
---------------------------------------------------------------
Key: JBBUILD-670
URL: https://issues.jboss.org/browse/JBBUILD-670
Project: JBoss Build System
Issue Type: Task
Reporter: Paul Gier
Assignee: Paul Gier
Priority: Critical
Fix For: Build Support 2011
Attachments: jboss-servlet-api-2.5.0.GA.jar, jboss-test-1.1.6-SNAPSHOT.pom.md5
We currently have audit information (username, timestamp) stored in .json files in the
repository. Nexus uses an XML format to store this information, and recent versions of
Nexus allow easy way to view this information in the Nexus UI. The existing audit
information should be migrated to the standard Nexus XML format.
These XML files are located in the directory
"sonatype-work/nexus/proxy/attributes". For each file in each Maven repository
hosted by Nexus, there is a file with the same name in this attributes directory. For
example,
"sonatype-work/nexus/proxy/attributes/jboss-releases/org/jboss/javaee/jboss-servlet-api/2.5.0.GA/jboss-servlet-api-2.5.0.GA.jar"
is actually an XML file containing the attributes for the named jar file.
Note: even though the files end with ".jar" or ".md5", they are
actually XML files.
The artifacts that were released before the original Nexus migration do not include a
username in the XML file, although they do include a timestamp. This appears to be the
file creation date. In the migration, these timestamps should be overwritten if
possible.
1. Check whether the user field exists for a given file.
2. If it does not exist, copy the username and timestamp fields to the Nexus attribute
file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:17 p.m.
New subject: [JBoss JIRA] Commented: (JBBUILD-670) Migrate existing Nexus Audit information to standard XML format
[
https://issues.jboss.org/browse/JBBUILD-670?page=com.atlassian.jira.plugi...
]
Paul Gier commented on JBBUILD-670:
-----------------------------------
The migration is complete. The last thing to do is create a permanent backup of the old
audit files, and review some of the migration logs.
Migrate existing Nexus Audit information to standard XML format
---------------------------------------------------------------
Key: JBBUILD-670
URL: https://issues.jboss.org/browse/JBBUILD-670
Project: JBoss Build System
Issue Type: Task
Reporter: Paul Gier
Assignee: Paul Gier
Priority: Critical
Fix For: Build Support 2011
Attachments: jboss-servlet-api-2.5.0.GA.jar, jboss-test-1.1.6-SNAPSHOT.pom.md5
We currently have audit information (username, timestamp) stored in .json files in the
repository. Nexus uses an XML format to store this information, and recent versions of
Nexus allow easy way to view this information in the Nexus UI. The existing audit
information should be migrated to the standard Nexus XML format.
These XML files are located in the directory
"sonatype-work/nexus/proxy/attributes". For each file in each Maven repository
hosted by Nexus, there is a file with the same name in this attributes directory. For
example,
"sonatype-work/nexus/proxy/attributes/jboss-releases/org/jboss/javaee/jboss-servlet-api/2.5.0.GA/jboss-servlet-api-2.5.0.GA.jar"
is actually an XML file containing the attributes for the named jar file.
Note: even though the files end with ".jar" or ".md5", they are
actually XML files.
The artifacts that were released before the original Nexus migration do not include a
username in the XML file, although they do include a timestamp. This appears to be the
file creation date. In the migration, these timestamps should be overwritten if
possible.
1. Check whether the user field exists for a given file.
2. If it does not exist, copy the username and timestamp fields to the Nexus attribute
file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:12 a.m.
New subject: [JBoss JIRA] Commented: (JBBUILD-670) Migrate existing Nexus Audit information to standard XML format
[
https://issues.jboss.org/browse/JBBUILD-670?page=com.atlassian.jira.plugi...
]
Paul Gier commented on JBBUILD-670:
-----------------------------------
The metadata audit.json files seem to have a different format than the other files. So
there are messages like in the log file like this:
Attribute request.user set to tcunning","captured-on":"2011-03-04
14:32:46 -0500
The audit file looks like this:
{quote}
\{"owner":"tcunning","captured-on":"2011-03-04 14:32:26
-0500",
"references-path":"/org/switchyard/switchyard-plugin/maven-metadata.xml",
"repository-id":"jboss_release_staging_profile-031"\}
{quote}
So the Perl script probably did a greedy match. These should be fixed, although it is not
urgent since it seems to only have affected the metadata files and not the artifact
files.
Migrate existing Nexus Audit information to standard XML format
---------------------------------------------------------------
Key: JBBUILD-670
URL: https://issues.jboss.org/browse/JBBUILD-670
Project: JBoss Build System
Issue Type: Task
Reporter: Paul Gier
Assignee: Paul Gier
Priority: Critical
Fix For: Build Support 2011
Attachments: jboss-servlet-api-2.5.0.GA.jar, jboss-test-1.1.6-SNAPSHOT.pom.md5
We currently have audit information (username, timestamp) stored in .json files in the
repository. Nexus uses an XML format to store this information, and recent versions of
Nexus allow easy way to view this information in the Nexus UI. The existing audit
information should be migrated to the standard Nexus XML format.
These XML files are located in the directory
"sonatype-work/nexus/proxy/attributes". For each file in each Maven repository
hosted by Nexus, there is a file with the same name in this attributes directory. For
example,
"sonatype-work/nexus/proxy/attributes/jboss-releases/org/jboss/javaee/jboss-servlet-api/2.5.0.GA/jboss-servlet-api-2.5.0.GA.jar"
is actually an XML file containing the attributes for the named jar file.
Note: even though the files end with ".jar" or ".md5", they are
actually XML files.
The artifacts that were released before the original Nexus migration do not include a
username in the XML file, although they do include a timestamp. This appears to be the
file creation date. In the migration, these timestamps should be overwritten if
possible.
1. Check whether the user field exists for a given file.
2. If it does not exist, copy the username and timestamp fields to the Nexus attribute
file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:09 p.m.
New subject: [JBoss JIRA] Updated: (JBBUILD-670) Migrate existing Nexus Audit information to standard XML format
[
https://issues.jboss.org/browse/JBBUILD-670?page=com.atlassian.jira.plugi...
]
Paul Gier updated JBBUILD-670:
------------------------------
Component/s: Artifact Repositories
Migrate existing Nexus Audit information to standard XML format
---------------------------------------------------------------
Key: JBBUILD-670
URL: https://issues.jboss.org/browse/JBBUILD-670
Project: JBoss Build System
Issue Type: Task
Components: Artifact Repositories
Reporter: Paul Gier
Assignee: Paul Gier
Priority: Critical
Fix For: Build Support 2011
Attachments: jboss-servlet-api-2.5.0.GA.jar, jboss-test-1.1.6-SNAPSHOT.pom.md5
We currently have audit information (username, timestamp) stored in .json files in the
repository. Nexus uses an XML format to store this information, and recent versions of
Nexus allow easy way to view this information in the Nexus UI. The existing audit
information should be migrated to the standard Nexus XML format.
These XML files are located in the directory
"sonatype-work/nexus/proxy/attributes". For each file in each Maven repository
hosted by Nexus, there is a file with the same name in this attributes directory. For
example,
"sonatype-work/nexus/proxy/attributes/jboss-releases/org/jboss/javaee/jboss-servlet-api/2.5.0.GA/jboss-servlet-api-2.5.0.GA.jar"
is actually an XML file containing the attributes for the named jar file.
Note: even though the files end with ".jar" or ".md5", they are
actually XML files.
The artifacts that were released before the original Nexus migration do not include a
username in the XML file, although they do include a timestamp. This appears to be the
file creation date. In the migration, these timestamps should be overwritten if
possible.
1. Check whether the user field exists for a given file.
2. If it does not exist, copy the username and timestamp fields to the Nexus attribute
file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:54 a.m.
New subject: [JBoss JIRA] (JBBUILD-670) Migrate existing Nexus Audit information to standard XML format
[
https://issues.jboss.org/browse/JBBUILD-670?page=com.atlassian.jira.plugi...
]
Paul Gier closed JBBUILD-670.
-----------------------------
Resolution: Done
Migrate existing Nexus Audit information to standard XML format
---------------------------------------------------------------
Key: JBBUILD-670
URL: https://issues.jboss.org/browse/JBBUILD-670
Project: JBoss Build System
Issue Type: Task
Components: Artifact Repositories
Reporter: Paul Gier
Assignee: Paul Gier
Priority: Critical
Fix For: Build Support 2012
Attachments: jboss-servlet-api-2.5.0.GA.jar, jboss-test-1.1.6-SNAPSHOT.pom.md5
We currently have audit information (username, timestamp) stored in .json files in the
repository. Nexus uses an XML format to store this information, and recent versions of
Nexus allow easy way to view this information in the Nexus UI. The existing audit
information should be migrated to the standard Nexus XML format.
These XML files are located in the directory
"sonatype-work/nexus/proxy/attributes". For each file in each Maven repository
hosted by Nexus, there is a file with the same name in this attributes directory. For
example,
"sonatype-work/nexus/proxy/attributes/jboss-releases/org/jboss/javaee/jboss-servlet-api/2.5.0.GA/jboss-servlet-api-2.5.0.GA.jar"
is actually an XML file containing the attributes for the named jar file.
Note: even though the files end with ".jar" or ".md5", they are
actually XML files.
The artifacts that were released before the original Nexus migration do not include a
username in the XML file, although they do include a timestamp. This appears to be the
file creation date. In the migration, these timestamps should be overwritten if
possible.
1. Check whether the user field exists for a given file.
2. If it does not exist, copy the username and timestamp fields to the Nexus attribute
file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4285
days inactive
4831
days old
9 comments
1 participants
participants (1)
-
Paul Gier (JIRA)