You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by bo...@werken.com on 2002/12/03 19:36:08 UTC

[maven-bug] Created: (MAVEN-169) most plugin issue tracking links are wrong

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-169


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-169
    Summary: most plugin issue tracking links are wrong
       Type: Bug

     Status: Assigned
   Priority: Trivial

 Time Spent: Unknown
   Estimate: 0 minutes

    Project: maven
  Component: None
   Versions:
             1.0-beta-8

   Assignee: Jason van Zyl
   Reporter: Brian Ewins

    Created: Tue, 3 Dec 2002 12:36 PM
    Updated: Tue, 3 Dec 2002 12:36 PM
Environment: website, example: http://jakarta.apache.org/turbine/maven/reference/plugins/changelog/project-info.html


Description:
54 plugin project.xml's have the wrong issue tracking URL (the deprecated http://nagoya.apache.org/scarab/servlet/scarab/ which links through to http://scarab.werken.com/scarab/issues/, which isnt used for maven issues). You can fix them all in one fell swoop with...

$ perl -i.bak -pe 's,http://nagoya.apache.org/scarab/servlet/scarab/,http://jira.werken.com/BrowseProject.jspa?id=10030,' src/plugins-build/*/project.xml

Or at least you could if JIRA worked properly without you logging in (browsing project issues doesnt work at all without login???)

$ perl -i.bak -pe 's,http://nagoya.apache.org/scarab/servlet/scarab/,http://jira.werken.com/,' src/plugins-build/*/project.xml

might be a better fix as the login is in yer face, though it doesnt link through to the maven project.

I've not submitted a patch as cygwin perl is screwing up the line endings.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.werken.com/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira