Bug 119455 - [PATCH] devel/maven2: update to version 2.0.8
Summary: [PATCH] devel/maven2: update to version 2.0.8
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Herve Quiroz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-08 15:30 UTC by Tomas Verbaitis
Modified: 2008-01-09 20:30 UTC (History)
1 user (show)

See Also:


Attachments
maven2-2.0.8.patch (1.53 KB, patch)
2008-01-08 15:30 UTC, Tomas Verbaitis
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Verbaitis 2008-01-08 15:30:01 UTC
Update to version 2.0.8

As files distributed by Apache Maven project changed their name to apache-maven, maybe the port name should also be updated to reflect that change? Currently I just fixed the port's Makefile to deal with the change (package name and WRKSRC).

Port maintainer (hq@FreeBSD.org) is cc'd.

Generated with FreeBSD Port Tools 0.77
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2008-01-08 15:30:09 UTC
Responsible Changed
From-To: freebsd-ports-bugs->hq

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 dfilter service freebsd_committer freebsd_triage 2008-01-09 20:16:58 UTC
hq          2008-01-09 20:16:53 UTC

  FreeBSD ports repository

  Modified files:
    devel/maven2         Makefile distinfo 
  Log:
  Update to version 2.0.8
  
  PR:             119455
  Submitted by:   Tomas Verbaitis <tomasv@megalogika.lt>
  
  Revision  Changes    Path
  1.11      +3 -3      ports/devel/maven2/Makefile
  1.11      +3 -3      ports/devel/maven2/distinfo
_______________________________________________
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
Comment 3 Herve Quiroz freebsd_committer freebsd_triage 2008-01-09 20:17:12 UTC
State Changed
From-To: open->closed

Patch commited. Thanks for your contribution! 

Regarding the package name change, I think we should keep the port as it for 
now. Apache projects are known to change package prefix often (e.g. the 
somewhat recent promoting of the commons project as a top-level Apache project, 
out of Jakarta). IMHO 'maven2' is explicit for now and unless another port is 
named maven, it should be fine. 

Herve