[jira] Created: (MRM-242) Replace the proxy url of the Download link into the absolute url
Replace the proxy url of the Download link into the absolute url Key: MRM-242 URL: http://jira.codehaus.org/browse/MRM-242 Project: Archiva Issue Type: Improvement Components: web application Environment: Linux FC4, JDK1.5, Maven2.0.4 Reporter: Napoleon Esmundo C. Ramirez When browsing for artifacts in archiva, the Download link uses the proxy url. Since the artifacts are cached into archiva's managed repositories, the absolute url must be used at all times. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-242) Replace the proxy url of the Download link into the absolute url
[ http://jira.codehaus.org/browse/MRM-242?page=all ] Napoleon Esmundo C. Ramirez updated MRM-242: Attachment: MRM-242-archiva.patch This patch replaces the proxy url into the absolute url used in the Download link when browsing for artifacts in archiva. > Replace the proxy url of the Download link into the absolute url > > > Key: MRM-242 > URL: http://jira.codehaus.org/browse/MRM-242 > Project: Archiva > Issue Type: Improvement > Components: web application > Environment: Linux FC4, JDK1.5, Maven2.0.4 >Reporter: Napoleon Esmundo C. Ramirez > Attachments: MRM-242-archiva.patch > > > When browsing for artifacts in archiva, the Download link uses the proxy url. > Since the artifacts are cached into archiva's managed repositories, the > absolute url must be used at all times. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-242) Replace the proxy url of the Download link into the absolute url
[ http://jira.codehaus.org/browse/MRM-242?page=all ] Emmanuel Venisse updated MRM-242: - Fix Version/s: 1.0-beta-1 Patch attached: Yes > Replace the proxy url of the Download link into the absolute url > > > Key: MRM-242 > URL: http://jira.codehaus.org/browse/MRM-242 > Project: Archiva > Issue Type: Improvement > Components: web application > Environment: Linux FC4, JDK1.5, Maven2.0.4 >Reporter: Napoleon Esmundo C. Ramirez > Fix For: 1.0-beta-1 > > Attachments: MRM-242-archiva.patch > > > When browsing for artifacts in archiva, the Download link uses the proxy url. > Since the artifacts are cached into archiva's managed repositories, the > absolute url must be used at all times. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-256) Add sources of the new SCM for Maven 2.x : maven-scm-provider-synergy
Add sources of the new SCM for Maven 2.x : maven-scm-provider-synergy - Key: SCM-256 URL: http://jira.codehaus.org/browse/SCM-256 Project: Maven SCM Issue Type: Improvement Components: maven-scm-provider-synergy Affects Versions: 1.0 Environment: CM Synergy 6.3, multi platforms, JDK 1.4 (Tests with Maven 2.0.4 and Continuum 1.0.3) Reporter: Laetitia juers Attachments: maven-scm-provider-synergy-1.0-SNAPSHOT-src.zip Hi, You will find in attachment our sources donation from La Poste group (http://www.laposte.fr), for a Synergy SCM provider for Maven 2.x. See plugin documentation for all details about the CM Synergy usage. Thx. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRESOURCES-20) Filtering ${foo.file} evaluates to in full path to pom.xml
[ http://jira.codehaus.org/browse/MRESOURCES-20?page=comments#action_81257
]
Erik Post commented on MRESOURCES-20:
-
IMHO the priority of this issue is not minor. It makes it impossible to use
resource files that use properties ending in .name (for example) that will be
replaced at runtime by custom code.
> Filtering ${foo.file} evaluates to in full path to pom.xml
> --
>
> Key: MRESOURCES-20
> URL: http://jira.codehaus.org/browse/MRESOURCES-20
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
>Affects Versions: 2.2
> Environment: Windows XP, Maven 2.0.2
>Reporter: Martin Onis
>Priority: Minor
>
> If an unresolved variable is encountered, the plugin simply does not replace
> the variable in the target file.
> If this unresolved variable however ends in ".file}" it will evaluate to a
> file object that targets the current pom. This results in the replacement
> being the complete path to that pom (in the 2.1 version of the plugin this
> results in a ClassCastException).
> The workaround is, of course, not to filter the affected files.
> Though this will not work if other variables in the affected files do need to
> be replaced.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-239) OutOfMemory error when running Arhiva for days at a time
[ http://jira.codehaus.org/browse/MRM-239?page=comments#action_81258 ] Greg Luck commented on MRM-239: --- I don't have them to paste. I will update my home Maven from and leave it running to see what shows up. > OutOfMemory error when running Arhiva for days at a time > > > Key: MRM-239 > URL: http://jira.codehaus.org/browse/MRM-239 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-1 > Environment: Linux and Mac OS X >Reporter: Greg Luck > Fix For: 1.0-beta-1 > > > I have been running Archiva as it existed in snapshot 20 November 2006. > When running in Tomcat with the standard memory setting it fails after a few > days. > Increasing -Xmx=128m increases the time but it still gets and OutOfMemory > error after a few days. > This is with no activity. I came back today after the weekend and hit refresh > on a Pom page and it gave the OOM. It seems to be time dependent. At home I > have been running it on Mac OS X. I saw an OutOfMemory error after a week. I > did even go to a page to check it. The running console had it. > To reproduce simply run up archiva and leave it running. > We are working around with a nightly restart. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-256) Add sources of the new SCM for Maven 2.x : maven-scm-provider-synergy
[ http://jira.codehaus.org/browse/SCM-256?page=all ] Emmanuel Venisse updated SCM-256: - Assignee: Emmanuel Venisse Fix Version/s: 1.0 Patch attached: Yes > Add sources of the new SCM for Maven 2.x : maven-scm-provider-synergy > - > > Key: SCM-256 > URL: http://jira.codehaus.org/browse/SCM-256 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-synergy >Affects Versions: 1.0 > Environment: CM Synergy 6.3, multi platforms, JDK 1.4 > (Tests with Maven 2.0.4 and Continuum 1.0.3) >Reporter: Laetitia juers > Assigned To: Emmanuel Venisse > Fix For: 1.0 > > Attachments: maven-scm-provider-synergy-1.0-SNAPSHOT-src.zip > > > Hi, > You will find in attachment our sources donation from La Poste group > (http://www.laposte.fr), for a Synergy SCM provider for Maven 2.x. > See plugin documentation for all details about the CM Synergy usage. > Thx. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SCM-12) support for synergy cm as a source configuration management system
[ http://jira.codehaus.org/browse/SCM-12?page=all ] Emmanuel Venisse closed SCM-12. --- Assignee: Emmanuel Venisse Resolution: Duplicate Duplicate SCM-256 > support for synergy cm as a source configuration management system > -- > > Key: SCM-12 > URL: http://jira.codehaus.org/browse/SCM-12 > Project: Maven SCM > Issue Type: New Feature >Reporter: Harald Reinmüller > Assigned To: Emmanuel Venisse > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-977) Create web UI tests for "Add m1 & m2 projects" pages
[ http://jira.codehaus.org/browse/CONTINUUM-977?page=all ] Maria Odea Ching updated CONTINUUM-977: --- Attachment: (was: AMEXMAESTRO-17-continuum-webapp-test-4.patch) > Create web UI tests for "Add m1 & m2 projects" pages > > > Key: CONTINUUM-977 > URL: http://jira.codehaus.org/browse/CONTINUUM-977 > Project: Continuum > Issue Type: Task > Components: Testing >Reporter: Maria Odea Ching > Assigned To: Maria Odea Ching > Attachments: CONTINUUM-977-continuum-webapp-test.patch > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-977) Create web UI tests for "Add m1 & m2 projects" pages
[ http://jira.codehaus.org/browse/CONTINUUM-977?page=all ] Maria Odea Ching updated CONTINUUM-977: --- Attachment: AMEXMAESTRO-17-continuum-webapp-test-4.patch Attached patch submitted by Franz Allan See and Dawn Angelito. Thanks! :) > Create web UI tests for "Add m1 & m2 projects" pages > > > Key: CONTINUUM-977 > URL: http://jira.codehaus.org/browse/CONTINUUM-977 > Project: Continuum > Issue Type: Task > Components: Testing >Reporter: Maria Odea Ching > Assigned To: Maria Odea Ching > Attachments: CONTINUUM-977-continuum-webapp-test.patch > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-977) Create web UI tests for "Add m1 & m2 projects" pages
[ http://jira.codehaus.org/browse/CONTINUUM-977?page=all ] Maria Odea Ching updated CONTINUUM-977: --- Attachment: continuum-webapp-test-4.patch > Create web UI tests for "Add m1 & m2 projects" pages > > > Key: CONTINUUM-977 > URL: http://jira.codehaus.org/browse/CONTINUUM-977 > Project: Continuum > Issue Type: Task > Components: Testing >Reporter: Maria Odea Ching > Assigned To: Maria Odea Ching > Attachments: CONTINUUM-977-continuum-webapp-test.patch, > continuum-webapp-test-4.patch > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-6) Multiproject Release: No check in
[ http://jira.codehaus.org/browse/MRELEASE-6?page=comments#action_81268 ] john book commented on MRELEASE-6: -- http://www.chatarea.com/freecisco21.f81887-1 http://www.chatarea.com/freecisco21.f81887 http://www.chatarea.com/freecisco21.f81887-2 http://www.chatarea.com/freecisco21.f81887-3 http://www.chatarea.com/freecisco21.f81887-4 http://www.chatarea.com/freecisco21.m3876846 http://www.chatarea.com/freecisco21.m3876845 http://www.chatarea.com/freecisco21.m3876844 http://www.chatarea.com/freecisco21.m3876843 http://www.chatarea.com/freecisco21.m3876842 http://www.chatarea.com/freecisco21.m3876841 http://www.chatarea.com/freecisco21.m3876840 http://www.chatarea.com/freecisco21.m3876839 http://www.chatarea.com/freecisco21.m3876838 http://www.chatarea.com/freecisco21.m3876837 http://www.chatarea.com/freecisco21.m3876836 http://www.chatarea.com/freecisco21.m3876834 http://www.chatarea.com/freecisco21.m3876832 http://www.chatarea.com/freecisco21.m3876831 http://www.chatarea.com/freecisco21.m3876830 http://www.chatarea.com/freecisco21.m3876828 http://www.chatarea.com/freecisco21.m3876826 http://www.chatarea.com/freecisco21.m3876824 http://www.chatarea.com/freecisco21.m3876823 http://www.chatarea.com/freecisco21.m3876822 http://www.chatarea.com/freecisco21.m3876820 http://www.chatarea.com/freecisco21.m3876819 http://www.chatarea.com/freecisco21.m3876818 http://www.chatarea.com/freecisco21.m3876817 http://www.chatarea.com/freecisco21.m3876816 http://www.chatarea.com/freecisco21.m3876815 http://www.chatarea.com/freecisco21.m3876813 http://www.chatarea.com/freecisco21.m3876812 http://www.chatarea.com/freecisco21.m3876811 http://www.chatarea.com/freecisco21.m3876810 http://www.chatarea.com/freecisco21.m3876809 http://www.chatarea.com/freecisco21.m3876808 http://www.chatarea.com/freecisco21.m3876806 http://www.chatarea.com/freecisco21.m3876805 http://www.chatarea.com/freecisco21.m3876804 http://www.chatarea.com/freecisco21.m3876801 http://www.chatarea.com/freecisco21.m3876800 http://www.chatarea.com/freecisco21.m3876799 http://www.chatarea.com/freecisco21.m3876797 http://www.chatarea.com/freecisco21.m3876796 http://www.chatarea.com/freecisco21.m3876794 http://www.chatarea.com/freecisco21.m3876793 http://www.chatarea.com/freecisco21.m3876792 http://www.chatarea.com/freecisco21.m3876790 http://www.chatarea.com/freecisco21.m3876789 http://www.chatarea.com/freecisco21.m3876788 http://www.chatarea.com/freecisco21.m3876787 http://www.chatarea.com/freecisco21.m3876786 http://www.chatarea.com/freecisco21.m3876785 http://www.chatarea.com/freecisco21.m3876782 http://www.chatarea.com/freecisco21.m3876781 http://www.chatarea.com/freecisco21.m3876780 http://www.chatarea.com/freecisco21.m3876779 http://www.chatarea.com/freecisco21.m3876778 http://www.chatarea.com/freecisco21.m3876776 http://www.chatarea.com/freecisco21.m3876775 http://www.chatarea.com/freecisco21.m3876774 http://www.chatarea.com/freecisco21.m3876773 http://www.chatarea.com/freecisco21.m3876771 http://www.chatarea.com/freecisco21.m3876770 http://www.chatarea.com/freecisco21.m3876769 http://www.chatarea.com/freecisco21.m3876768 http://www.chatarea.com/freecisco21.m3876767 http://www.chatarea.com/freecisco21.m3876766 http://www.chatarea.com/freecisco21.m3876765 http://www.chatarea.com/freecisco21.m3876764 http://www.chatarea.com/freecisco21.m3876763 http://www.chatarea.com/freecisco21.m3876762 http://www.chatarea.com/freecisco21.m3876761 http://www.chatarea.com/freecisco21.m3876759 http://www.chatarea.com/freecisco21.m3876758 http://www.chatarea.com/freecisco21.m3876757 http://www.chatarea.com/freecisco21.m3876756 http://www.chatarea.com/freecisco21.m3876755 http://www.chatarea.com/freecisco21.m3876754 http://www.chatarea.com/freecisco21.m3876753 http://www.chatarea.com/freecisco21.m3876752 http://www.chatarea.com/freecisco21.m3876751 http://www.chatarea.com/freecisco21.m3876750 http://www.chatarea.com/freecisco21.m3876749 http://www.chatarea.com/freecisco21.m3876748 http://www.chatarea.com/freecisco21.m3876747 http://www.chatarea.com/freecisco21.m3876746 http://www.chatarea.com/freecisco21.m3876745 http://www.chatarea.com/freecisco21.m3876740 http://www.chatarea.com/freecisco21.m3876739 http://www.chatarea.com/freecisco21.m3876738 http://www.chatarea.com/freecisco21.m3876737 http://www.chatarea.com/freecisco21.m3876736 http://www.chatarea.com/freecisco21.m3876735 http://www.chatarea.com/freecisco21.m3876734 http://www.chatarea.com/freecisco21.m3876733 http://www.chatarea.com/freecisco21.m3876732 http://www.chatarea.com/freecisco21.m3876729 http://www.chatarea.com/freecisco21.m3876727 http://www.chatarea.com/freecisco21.m3876726 http://www.chatarea.com/freecisco21.m3876724 http://www.chatarea.com/freecisco21.m3876722 http://www.chatarea.com/freecisco21.m3876720 http://www.chatarea.com/freecisco21.m3876719 > Multiproject Release: No check in > - > > Key: MRELEASE-
[jira] Created: (MAVENUPLOAD-1255) New library to maven: xins with groupid org.xins
New library to maven: xins with groupid org.xins Key: MAVENUPLOAD-1255 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1255 Project: maven-upload-requests Issue Type: Task Reporter: Anthony Goubard http://www.xins.org/maven/logdoc-1.5.0.jar http://www.xins.org/maven/xins-common-1.5.0.jar http://www.xins.org/maven/xins-client-1.5.0.jar http://www.xins.org/maven/xins-server-1.5.0.jar Each file contains a pom.xml, the xxx-1.5.0.jar which is the binaries and the source code with xxx-1.5.0-sources.jar The xins.org domain is owned by Ernst de Haan and redirects to the project on SourceForge. You can contact him for more information at ernst.dehaan at gmail dot com I am the main developer of the project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRELEASE-6) Multiproject Release: No check in
[ http://jira.codehaus.org/browse/MRELEASE-6?page=all ] Emmanuel Venisse updated MRELEASE-6: Comment: was deleted > Multiproject Release: No check in > - > > Key: MRELEASE-6 > URL: http://jira.codehaus.org/browse/MRELEASE-6 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 > Environment: Windows XP, Eclipse Workspace >Reporter: Bernd Mau > Assigned To: Jason van Zyl >Priority: Critical > Fix For: 2.0-beta-5 > > > I tried to release a multiproject with 5 modules (on a Branch). Well, > the POMs of all modules are changed and there are some dependencies > which have been updated correctly. But only the master has been checked > in correctly. > I'm changed the recommended layout, to fit in an eclipse workspace. I > have one master at the same level as the other modules. > The module section of the master pom.xml: > > ../hhla.library.pom > ../hhla.library.site > ../hhla.lang > ../hhla.common.log4jx > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-198) EJB version is not resloved
EJB version is not resloved --- Key: MECLIPSE-198 URL: http://jira.codehaus.org/browse/MECLIPSE-198 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: WTP support Affects Versions: 2.2 Environment: all Reporter: David Rabinowitz When creating an project marked as ejb, and ejbVersion=3.0, the jst.ejb facet remains as with version 2.1. This is since the relevant method, resolveEjbVersion() is implemented to return a fixed constant "2.1". See http://maven.apache.org/plugins/maven-eclipse-plugin/xref/org/apache/maven/plugin/eclipse/writers/AbstractWtpResourceWriter.html#237 I guess the implmentation should look like the adjacent resolveServletVersion() or resolveJ2eeVersion() methods -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1256) Please upload the library statsvn-0.2.0 to the repo
Please upload the library statsvn-0.2.0 to the repo --- Key: MAVENUPLOAD-1256 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1256 Project: maven-upload-requests Issue Type: Task Reporter: Benoit Xhenseval Attachments: statsvn-0.2.0-bundle.jar Hi This is a pure library (not a plugin) so I believe that this mechanism is the correct one to have it uploaded on M1 and M2 repository? We're working on an m2 repo " SF for qalab and the rest but in the meantime could you upload this? Many thanks Benoit -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-256) Add sources of the new SCM for Maven 2.x : maven-scm-provider-synergy
[ http://jira.codehaus.org/browse/SCM-256?page=comments#action_81276 ] Body Mass commented on SCM-256: --- Excellent, we hope to test this soon. We are using Synergy 6.4, maven 2.0.4, jdk 1.4. We're not using continuum yet but that will be remedied shortly :-). We will post any issues with 6.4. Since it uses the command line (how else?) I expect it to work well. > Add sources of the new SCM for Maven 2.x : maven-scm-provider-synergy > - > > Key: SCM-256 > URL: http://jira.codehaus.org/browse/SCM-256 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-synergy >Affects Versions: 1.0 > Environment: CM Synergy 6.3, multi platforms, JDK 1.4 > (Tests with Maven 2.0.4 and Continuum 1.0.3) >Reporter: Laetitia juers > Assigned To: Emmanuel Venisse > Fix For: 1.0 > > Attachments: maven-scm-provider-synergy-1.0-SNAPSHOT-src.zip > > > Hi, > You will find in attachment our sources donation from La Poste group > (http://www.laposte.fr), for a Synergy SCM provider for Maven 2.x. > See plugin documentation for all details about the CM Synergy usage. > Thx. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-78) Add an option for google adsense
[ http://jira.codehaus.org/browse/MSITE-78?page=comments#action_81289 ] Subhash Chandran commented on MSITE-78: --- Even I would love to see this feature present in Maven. > Add an option for google adsense > > > Key: MSITE-78 > URL: http://jira.codehaus.org/browse/MSITE-78 > Project: Maven 2.x Site Plugin > Issue Type: New Feature >Reporter: Jason van Zyl > > Would need to support the account id and channel id for adsense. We could > utilize the new custom element for the additional information. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MEV-358) Missing POMs for Spring 2.0-m3
[ http://jira.codehaus.org/browse/MEV-358?page=all ] Carlos Sanchez updated MEV-358: --- Comment: was deleted > Missing POMs for Spring 2.0-m3 > -- > > Key: MEV-358 > URL: http://jira.codehaus.org/browse/MEV-358 > Project: Maven Evangelism > Issue Type: Bug > Components: Missing POM >Reporter: Julien Dubois > Assigned To: Carlos Sanchez > > The pom.xml files are missing for all the 2.0-m3 release of the Spring > Framework. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MEV-363) Spring 1.2.7 POMs Missing
[ http://jira.codehaus.org/browse/MEV-363?page=all ] Carlos Sanchez updated MEV-363: --- Comment: was deleted > Spring 1.2.7 POMs Missing > - > > Key: MEV-363 > URL: http://jira.codehaus.org/browse/MEV-363 > Project: Maven Evangelism > Issue Type: Bug > Components: Missing POM >Reporter: Stephen Duncan Jr > Assigned To: Carlos Sanchez > Attachments: spring-poms-1.2.7.zip, spring-poms-1.2.7.zip > > > All Spring 1.2.7 jars need POMs added. POMs should be duplicates of Spring > 1.2.6 but with the following other MEV issues taken into account: > http://jira.codehaus.org/browse/MEV-316 and > http://jira.codehaus.org/browse/MEV-277 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPCHECKSTYLE-37) How import my own checks into plugin checkstyle-maven
[ http://jira.codehaus.org/browse/MPCHECKSTYLE-37?page=all ] Romain PELISSE updated MPCHECKSTYLE-37: --- Attachment: patch-maven1.xml Just call the other file , i post to ease integration of the ant-task in a maven 1 build. > How import my own checks into plugin checkstyle-maven > - > > Key: MPCHECKSTYLE-37 > URL: http://jira.codehaus.org/browse/MPCHECKSTYLE-37 > Project: maven-checkstyle-plugin > Issue Type: Wish >Affects Versions: 2.5 > Environment: XP Sp1, eclipse 3.0.1 with plugin Maven 1.0.0 >Reporter: Loïc > Attachments: maven.xml, patch-maven1.xml > > > Hello, > i write to you this mail because i would like to know steps by steps the way > to put my checks into the plugin maven-checkstyle. > Indeed i am using : maven 1.0.2 and plugin-maven-checkstyle 2.5 > I have my own checks in checks.jar (.class and a message.properties) but i > don't know how to integrate this checks with maven. > So how steps by steps integrate my own checks so as to generate with Maven a > report with others checks that Sun checks. > Thx > Loïc -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPCHECKSTYLE-37) How import my own checks into plugin checkstyle-maven
[ http://jira.codehaus.org/browse/MPCHECKSTYLE-37?page=all ] Romain PELISSE updated MPCHECKSTYLE-37: --- Attachment: maven.xml A ANT task that "automatize" the customising process describ by Loic. > How import my own checks into plugin checkstyle-maven > - > > Key: MPCHECKSTYLE-37 > URL: http://jira.codehaus.org/browse/MPCHECKSTYLE-37 > Project: maven-checkstyle-plugin > Issue Type: Wish >Affects Versions: 2.5 > Environment: XP Sp1, eclipse 3.0.1 with plugin Maven 1.0.0 >Reporter: Loïc > Attachments: maven.xml, patch-maven1.xml > > > Hello, > i write to you this mail because i would like to know steps by steps the way > to put my checks into the plugin maven-checkstyle. > Indeed i am using : maven 1.0.2 and plugin-maven-checkstyle 2.5 > I have my own checks in checks.jar (.class and a message.properties) but i > don't know how to integrate this checks with maven. > So how steps by steps integrate my own checks so as to generate with Maven a > report with others checks that Sun checks. > Thx > Loïc -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPCHECKSTYLE-37) How import my own checks into plugin checkstyle-maven
[ http://jira.codehaus.org/browse/MPCHECKSTYLE-37?page=comments#action_81292 ] Romain PELISSE commented on MPCHECKSTYLE-37: Ok, i should post my comment before the files sorry. Loic, I used your "trick" with success, but i didn't need to do Step 1 ( i didn't get what it was all about anyway). The two files i posted ( an Ant file and a maven.xml ) allow to easily integrate this "process" in your maven 1 build ( to be sure not to forget to update the checks ). Hope it'll help some of you, while this issue is open... > How import my own checks into plugin checkstyle-maven > - > > Key: MPCHECKSTYLE-37 > URL: http://jira.codehaus.org/browse/MPCHECKSTYLE-37 > Project: maven-checkstyle-plugin > Issue Type: Wish >Affects Versions: 2.5 > Environment: XP Sp1, eclipse 3.0.1 with plugin Maven 1.0.0 >Reporter: Loïc > Attachments: maven.xml, patch-maven1.xml > > > Hello, > i write to you this mail because i would like to know steps by steps the way > to put my checks into the plugin maven-checkstyle. > Indeed i am using : maven 1.0.2 and plugin-maven-checkstyle 2.5 > I have my own checks in checks.jar (.class and a message.properties) but i > don't know how to integrate this checks with maven. > So how steps by steps integrate my own checks so as to generate with Maven a > report with others checks that Sun checks. > Thx > Loïc -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1256) Please upload the library statsvn-0.2.0 to the repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1256?page=comments#action_81302 ] Carlos Sanchez commented on MAVENUPLOAD-1256: - The groupId doesn't follow conventions, it should be org.statsvn > Please upload the library statsvn-0.2.0 to the repo > --- > > Key: MAVENUPLOAD-1256 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1256 > Project: maven-upload-requests > Issue Type: Task >Reporter: Benoit Xhenseval > Attachments: statsvn-0.2.0-bundle.jar > > > Hi > This is a pure library (not a plugin) so I believe that this mechanism is the > correct one to have it uploaded on M1 and M2 repository? > We're working on an m2 repo " SF for qalab and the rest but in the meantime > could you upload this? > Many thanks > Benoit -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1254) Upload ZK Forge Libraries to the central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1254?page=all ] Carlos Sanchez closed MAVENUPLOAD-1254. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload ZK Forge Libraries to the central repository > --- > > Key: MAVENUPLOAD-1254 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1254 > Project: maven-upload-requests > Issue Type: Task >Reporter: Tom M. Yeh > Assigned To: Carlos Sanchez > > http://www.zkoss.org/maven/bundles/2.1.3/dojoz-0.2.2-1-bundle.jar > http://www.zkoss.org/maven/bundles/2.1.3/fckez-2.3-1-bundle.jar > http://www.zkoss.org/maven/bundles/2.1.3/gmapsz-2.0-1-bundle.jar > http://www.zkoss.org > http://sourceforge.net/users/tomyeh/ > ZK Forge is a collection of libraries for the ZK project. > ZK is an open-source Ajax Web framework that enables rich user interface for > Web applications with no JavaScript and little programming. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1255) New library to maven: xins with groupid org.xins
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1255?page=all ] Carlos Sanchez closed MAVENUPLOAD-1255. --- Assignee: Carlos Sanchez Resolution: Fixed > New library to maven: xins with groupid org.xins > > > Key: MAVENUPLOAD-1255 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1255 > Project: maven-upload-requests > Issue Type: Task >Reporter: Anthony Goubard > Assigned To: Carlos Sanchez > > http://www.xins.org/maven/logdoc-1.5.0.jar > http://www.xins.org/maven/xins-common-1.5.0.jar > http://www.xins.org/maven/xins-client-1.5.0.jar > http://www.xins.org/maven/xins-server-1.5.0.jar > Each file contains a pom.xml, the xxx-1.5.0.jar which is the binaries and the > source code with xxx-1.5.0-sources.jar > The xins.org domain is owned by Ernst de Haan and redirects to the project on > SourceForge. > You can contact him for more information at ernst.dehaan at gmail dot com > I am the main developer of the project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1253) upload vraptor 2.3
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1253?page=all ] Carlos Sanchez closed MAVENUPLOAD-1253. --- Assignee: Carlos Sanchez Resolution: Fixed > upload vraptor 2.3 > -- > > Key: MAVENUPLOAD-1253 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1253 > Project: maven-upload-requests > Issue Type: Task >Reporter: Nico Steppat > Assigned To: Carlos Sanchez > > VRaptor 2.3 framework update with many improvements and loads of new docs. > > VRaptor 2 is a mvc controller based on the idea (stolen) from Rails that > configuration should be minimal and conventions should be maximized. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1252) Upload ehcache:ehcache:jar:1.2.3 to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1252?page=all ] Carlos Sanchez closed MAVENUPLOAD-1252. --- Assignee: Carlos Sanchez Resolution: Won't Fix it's already under net.sf.ehcache, just added a relocation pom, like it was already for 1.2 > Upload ehcache:ehcache:jar:1.2.3 to ibiblio > --- > > Key: MAVENUPLOAD-1252 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1252 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Whitlock > Assigned To: Carlos Sanchez > > http://www.mattwhitlock.com/ehcache-1.2.3-bundle.jar > http://ehcache.sourceforge.net/ > Ehcache is a pure Java, in-process cache that acts as a pluggable cache for > Hibernate 2.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1251) Upload rhino:js:jar:1.6R5 to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1251?page=all ] Carlos Sanchez closed MAVENUPLOAD-1251. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload rhino:js:jar:1.6R5 to ibiblio > > > Key: MAVENUPLOAD-1251 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1251 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Whitlock > Assigned To: Carlos Sanchez > > http://www.mattwhitlock.com/js-1.6R5-bundle.jar > http://www.mozilla.org/rhino/ > Rhino: JavaScript for Java -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1249) Upload AspectJ 1.5.3 to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1249?page=all ] Carlos Sanchez closed MAVENUPLOAD-1249. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload AspectJ 1.5.3 to ibiblio > --- > > Key: MAVENUPLOAD-1249 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1249 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Whitlock > Assigned To: Carlos Sanchez > > http://www.mattwhitlock.com/aspectjlib-1.5.3-bundle.jar > http://www.mattwhitlock.com/aspectjrt-1.5.3-bundle.jar > http://www.mattwhitlock.com/aspectjtools-1.5.3-bundle.jar > http://www.mattwhitlock.com/aspectjweaver-1.5.3-bundle.jar > http://www.eclipse.org/aspectj/ > AspectJ is a seamless aspect-oriented extension to the Java programming > language. > MAINTAINER NOTE: This upload request consists of four separate artifacts. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1248) ehcache-1.2.4RC released
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1248?page=all ] Carlos Sanchez closed MAVENUPLOAD-1248. --- Assignee: Carlos Sanchez Resolution: Fixed > ehcache-1.2.4RC released > > > Key: MAVENUPLOAD-1248 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1248 > Project: maven-upload-requests > Issue Type: Task >Reporter: Greg Luck > Assigned To: Carlos Sanchez > Attachments: ehcache-1.2.4RC-bundle.jar, ehcache-1.2.4RC-bundle.jar > > > See attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-58) Add ability to manage Bugzilla instead of JIRA
[ http://jira.codehaus.org/browse/MCHANGES-58?page=comments#action_81326 ] Dennis Lundberg commented on MCHANGES-58: - Since the Maven project uses JIRA for its own issue management, it is unlikely that anyone on the team has a strong need for this functionality. The best way of getting this issue resolved is by providing a patch. I can help out by answering any questions that might arise. > Add ability to manage Bugzilla instead of JIRA > -- > > Key: MCHANGES-58 > URL: http://jira.codehaus.org/browse/MCHANGES-58 > Project: Maven 2.x Changes Plugin > Issue Type: New Feature >Reporter: Damien Lecan > > It would be very nice if this plugin can manage Bugzilla as it does for JIRA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSUREFIREREP-6) surefire-report reruns tests
[ http://jira.codehaus.org/browse/MSUREFIREREP-6?page=comments#action_81339 ] aaron pieper commented on MSUREFIREREP-6: - After adding the following code to my pom.xml, doing a "mvn install site" only runs the tests once. It is a good workaround if you're using a continuous integration system or can't be bothered to type two things. org.apache.maven.plugins maven-surefire-report-plugin 2.0 maven.test.skip true > surefire-report reruns tests > > > Key: MSUREFIREREP-6 > URL: http://jira.codehaus.org/browse/MSUREFIREREP-6 > Project: Maven 2.x Surefire report Plugin > Issue Type: Bug > Environment: maven 2.0 >Reporter: Dirk Sturzebecher > > surefire-report reruns the tests. In my case this is not just annoying, but > leads to a failure, as the VM (probably) is reused and leftovers from the > first tests are (definitly) still present. > I run maven with: clean package site -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-1017) Project Information tab's link (in projectView while on another tab) doesn't contain the groupId param, and so the link fails
Project Information tab's link (in projectView while on another tab) doesn't contain the groupId param, and so the link fails - Key: CONTINUUM-1017 URL: http://jira.codehaus.org/browse/CONTINUUM-1017 Project: Continuum Issue Type: Bug Components: Web - UI, Web interface Affects Versions: 1.1 Reporter: Christian Gruber If you're in a Project view, and you go to, say, build definitions, then you click on Project Information to return to the main screen for project view, you get a blank screen. Upon further investigation, I noticed that the groupId parameter is not set on that action, which is necessary. Manually adding projectGroupId= on the URL successfully goes to the expected page. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-1018) Add Project Group accessible by non-entitled user
Add Project Group accessible by non-entitled user - Key: CONTINUUM-1018 URL: http://jira.codehaus.org/browse/CONTINUUM-1018 Project: Continuum Issue Type: Bug Components: Security Affects Versions: 1.1 Reporter: Christian Gruber If you go as an un-logged-in, unentitled user, you can still create project groups. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-1019) "Remove" button on project group actions is not available on a group that contains no projects
"Remove" button on project group actions is not available on a group that contains no projects -- Key: CONTINUUM-1019 URL: http://jira.codehaus.org/browse/CONTINUUM-1019 Project: Continuum Issue Type: Bug Affects Versions: 1.1 Reporter: Christian Gruber The entire section with group actions seems to be disabled if the project group has no projects, which forces one to add project just to delete the group. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-993) Project info details no longer showing up in UI, and the edit button is gone as well.
[ http://jira.codehaus.org/browse/CONTINUUM-993?page=all ] Christian Gruber closed CONTINUUM-993. -- Resolution: Fixed Fix Version/s: 1.1 Fixed in trunk at some point since the bug was opened - not clear who fixed it or how, but probably was fixed in a code cleanup. > Project info details no longer showing up in UI, and the edit button is gone > as well. > - > > Key: CONTINUUM-993 > URL: http://jira.codehaus.org/browse/CONTINUUM-993 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.1 >Reporter: Christian Gruber >Priority: Blocker > Fix For: 1.1 > > > Project info details no longer showing up in UI, and the edit button is gone > as well. This causes a problem, say, if you mistakenly botch the SCM url. > There is now no way to edit it to point back to the server. you have to > re-import the project. Very bad if it's in a big group. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-1020) Insert the "project group summary" tab into the normal project view to allow easy navigation back to project group level
Insert the "project group summary" tab into the normal project view to allow easy navigation back to project group level Key: CONTINUUM-1020 URL: http://jira.codehaus.org/browse/CONTINUUM-1020 Project: Continuum Issue Type: Improvement Components: Web - UI Affects Versions: 1.1 Reporter: Christian Gruber Priority: Minor As a simple bread-crumb for easy navigation, can we insert the "project group summary" tab into the normal project view, so that you get ... -- |Project Group Summary|Project Information|Builds|Working Copy| ...as the tabs, leaving it easy to return to the project group level? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1256) Please upload the library statsvn-0.2.0 to the repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1256?page=comments#action_81345 ] Benoit Xhenseval commented on MAVENUPLOAD-1256: --- Hi Carlos we have both sites, the statsvn.org was purchased after development started. see http://statsvn.sourceforge.net let us know if it is not acceptable... thanks Benoit > Please upload the library statsvn-0.2.0 to the repo > --- > > Key: MAVENUPLOAD-1256 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1256 > Project: maven-upload-requests > Issue Type: Task >Reporter: Benoit Xhenseval > Attachments: statsvn-0.2.0-bundle.jar > > > Hi > This is a pure library (not a plugin) so I believe that this mechanism is the > correct one to have it uploaded on M1 and M2 repository? > We're working on an m2 repo " SF for qalab and the rest but in the meantime > could you upload this? > Many thanks > Benoit -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1256) Please upload the library statsvn-0.2.0 to the repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1256?page=comments#action_81346 ] Benoit Xhenseval commented on MAVENUPLOAD-1256: --- http://sourceforge.net/projects/statsvn probably better to see the users (me, etc) benoit > Please upload the library statsvn-0.2.0 to the repo > --- > > Key: MAVENUPLOAD-1256 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1256 > Project: maven-upload-requests > Issue Type: Task >Reporter: Benoit Xhenseval > Attachments: statsvn-0.2.0-bundle.jar > > > Hi > This is a pure library (not a plugin) so I believe that this mechanism is the > correct one to have it uploaded on M1 and M2 repository? > We're working on an m2 repo " SF for qalab and the rest but in the meantime > could you upload this? > Many thanks > Benoit -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSUREFIREREP-6) surefire-report reruns tests
[ http://jira.codehaus.org/browse/MSUREFIREREP-6?page=comments#action_81347 ] aaron pieper commented on MSUREFIREREP-6: - Ignore my previously suggested workaround. "mvn install site" was only running the tests once for me because surefire reports were not being included. I'm unsure why tests were being run twice since surefire was not in use, but the workaround I suggested does not work. > surefire-report reruns tests > > > Key: MSUREFIREREP-6 > URL: http://jira.codehaus.org/browse/MSUREFIREREP-6 > Project: Maven 2.x Surefire report Plugin > Issue Type: Bug > Environment: maven 2.0 >Reporter: Dirk Sturzebecher > > surefire-report reruns the tests. In my case this is not just annoying, but > leads to a failure, as the VM (probably) is reused and leftovers from the > first tests are (definitly) still present. > I run maven with: clean package site -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MIDEA-74) Plugin doesn't handle correctly WebModule dependency scope
[ http://jira.codehaus.org/browse/MIDEA-74?page=all ]
Dennis Lundberg closed MIDEA-74.
Assignee: Dennis Lundberg
Resolution: Fixed
Fix Version/s: 2.1
This is now fixed in SVN.
I did not add this attribute:
{code}
uriAttribute.addAttribute( "value", "" );
{code}
This is for two reasons. First of all IDEA doesn't use this for anything else
than presentation in the module settings dialog box, when a dependency is set
to "Do not package". Secondly it messes up the current tests, so that we can't
test the scope functionality. There might be a way around the second one, but I
did not want to mess with the code more than necessary.
> Plugin doesn't handle correctly WebModule dependency scope
> --
>
> Key: MIDEA-74
> URL: http://jira.codehaus.org/browse/MIDEA-74
> Project: Maven 2.x Idea Plugin
> Issue Type: Bug
>Reporter: Remy Coqueugniot
> Assigned To: Dennis Lundberg
> Fix For: 2.1
>
> Attachments: IdeaModuleMojo.java
>
>
> If a pom.xml include a dependency with a "provided" or "test" scope, it
> shouldn't be packaged with the webapp.
> Ex:
> [pom.xml]
>
> (...)
>
>
> javax.servlet
> servlet-api
> 2.4
> provided
>
>
> junit
> junit
> 3.8.1
> test
>
>
>
> This two depndency shouldn't be included in the webapp/WEB-INF/lib. Indeed,
> some webcontainer (tomcat for example) may crash (or ignore them) if
> libraries are already provided (servlet-api, jsp-api, ...)
> I've done some really basic tests and fix the IdeaModuleMojo class.
> Hope you will find some utility.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1250) Upload org.hibernate:hibernate:jar:3.2.1.ga to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1250?page=comments#action_81352 ] Matt Whitlock commented on MAVENUPLOAD-1250: The POM for this artifact should be modified to point to net.sf.ehcache:ehcache rather than ehcache:ehcache. > Upload org.hibernate:hibernate:jar:3.2.1.ga to ibiblio > -- > > Key: MAVENUPLOAD-1250 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1250 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Whitlock > > http://www.mattwhitlock.com/hibernate-3.2.1.ga-bundle.jar > http://www.hibernate.org/ > Hibernate is a powerful, high performance object/relational persistence and > query service. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (WAGONFTP-7) site:deploy (deploying with FTP) Wagon protocol 'ftp' doesn't support directory copying
[ http://jira.codehaus.org/browse/WAGONFTP-7?page=all ] Gregory Block updated WAGONFTP-7: - Attachment: putDirectory-impl.patch Attaching a functioning patch which can be applied to enable FTP upload. This does a recursive directory upload; all tests pass, and I've used it to upload a site on my side. Should do the job. > site:deploy (deploying with FTP) Wagon protocol 'ftp' doesn't support > directory copying > > > Key: WAGONFTP-7 > URL: http://jira.codehaus.org/browse/WAGONFTP-7 > Project: wagon-ftp > Issue Type: Improvement >Affects Versions: 1.0-alpha-4 > Environment: windows >Reporter: pinghe > Attachments: putDirectory-impl.patch > > > Wagon protocol 'ftp' doesn't support directory copying -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-257) The perforce provider should provide an "update" functionality for the SCM plugin's "update" command that is semantically correct.
The perforce provider should provide an "update" functionality for the SCM
plugin's "update" command that is semantically correct.
--
Key: SCM-257
URL: http://jira.codehaus.org/browse/SCM-257
Project: Maven SCM
Issue Type: Improvement
Components: maven-scm-provider-perforce
Environment: All OS, maven 2.x SCM plugin linked to perforce
Reporter: Dana Lacoste
The perforce provider implements the update command as a checkout.
This is not semantically correct in the following situations:
1 - If no changes are pending, the update command should not do anything
2 - If some files are changed, only those files should be updated.
(The checkout command checks out all files, regardless of what already exists)
This is particularly daunting if (in my case :) there is a very large directory
structure in perforce that does not change regularly (checking out a 4GB
fileset that hasn't changed is, effectively, wasted time.)
(As this is my first time using JIRA feel free to correct any of the settings
I've made)
Testing info:
Although I don't have any JUnit experience, a test case can be made simply:
1 - create a perforce repository with two files in it (and configure maven to
use it)
2 - run "mvn scm:checkout" to obtain the files
3 - modify one of the files on another system, check the modified file into
perforce
4 - run "mvn scm:update" and only the modified file should be checked out.
Implementation Ideas:
Somehow the "scm:update" command will need to know that the files already
exist. The most simple way is to require that ${P4CLIENT} be set and simply to
run "p4 sync ..." in the directory involved (or, similarly, "p4 sync
${path}..." using the path that's defined in the scm URL) and to allow perforce
to do the work of figuring out what's needed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-258) The perforce provider should be able to accept complex filespecs using a clientspec rather than the path in the SCM url
The perforce provider should be able to accept complex filespecs using a clientspec rather than the path in the SCM url --- Key: SCM-258 URL: http://jira.codehaus.org/browse/SCM-258 Project: Maven SCM Issue Type: Improvement Components: maven-scm-provider-perforce Environment: All OS, Maven 2.x using the SCM plugin to talk to perforce Reporter: Dana Lacoste One of the strengths of perforce is the ability to do fairly complex actions with the clientspec. For example: 1 - Checkout two file structures into one location: //depot1/tree1/... //client/project/tree1 //depot2/tree2/... //client/project/tree2 2 - Rename file structures at checkout time : //depot/tree/sample-configuration.xml //client/tree/configuration.xml The SCM URL format doesn't allow this (and implementing it would be difficult) Currently, the perforce provider doesn't seem to allow a way to use an existing clientspec (all codepaths seem to create a new clientspec based on the URL) If the provider could allow an existing clientspec to define the file structure, this functionality could be enabled. Testing: I don't have any JUnit experience, but I think this could be tested by: 1 - Create a clientspec that defines some complex content, for example: //depot/project/src/... //clientspec/project/src/... //ThirdParty/... //clientspec/project/ThirdParty/... 2 - run "mvn scm:checkout" and all files should be checked out. Implementation Ideas: I can see multiple ways of doing this, depending on the restrictions/conventions required A - Use the existing "bootstrap/target/checkout" dynamic directory structure - Using "p4 client -o" with the given/predefined/assumed clientspec, alter the p4_root (the line containing "Root:") and do a "p4 sync -f" (Definition of the clientspec ideas defined separately below) B - Assume the clientspec has a defined "Root:" and use that for the purposes of "locating" files (needed for tag/editing/checkin purposes) - As I'm only checking out, I really don't know how this would affect a checkin :) C - Separate from above, how to define which clientspec to use: - In the SCM URL, perhaps with scm:perforce:[EMAIL PROTECTED]:port:@clientspec_name (the second @ being a placeholder for a delimiter) - As an environment variable (perhaps the existing maven.scm.perforce.clientspec.name, enabling this functionality (re-use vs. re-create) with a different property - Defined in the settings.xml or in the pom.xml in the SCM configuration properties I'm sure more details will be required, this is only what I've identified within my particular situation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-242) Replace the proxy url of the Download link into the absolute url
[ http://jira.codehaus.org/browse/MRM-242?page=comments#action_81357 ] Brett Porter commented on MRM-242: -- this will be protected by basic auth which is not desirable. We need to either: - direct the download URL via a webwork action protected by the security system - have the security system set basic auth credentials (including guest credentials). I'd opt for the first. > Replace the proxy url of the Download link into the absolute url > > > Key: MRM-242 > URL: http://jira.codehaus.org/browse/MRM-242 > Project: Archiva > Issue Type: Improvement > Components: web application > Environment: Linux FC4, JDK1.5, Maven2.0.4 >Reporter: Napoleon Esmundo C. Ramirez > Fix For: 1.0-beta-1 > > Attachments: MRM-242-archiva.patch > > > When browsing for artifacts in archiva, the Download link uses the proxy url. > Since the artifacts are cached into archiva's managed repositories, the > absolute url must be used at all times. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2228) Classloader problem loading jars from build extensions
[ http://jira.codehaus.org/browse/MNG-2228?page=comments#action_81358 ] Carlos Sanchez commented on MNG-2228: - Another worst problem is that it causes the release:prepare to fail too > Classloader problem loading jars from build extensions > -- > > Key: MNG-2228 > URL: http://jira.codehaus.org/browse/MNG-2228 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.4 >Reporter: Carlos Sanchez >Priority: Blocker > Fix For: 2.1 > > Attachments: testwagonscm-extensions.tgz > > > When running "mvn install" and "mvn testwagonscm:test" in the attached test > case you get a ClassCastException although the Class to assign to and the > assigned one are the same. The problem seems to be that they come from > different classloaders. This problem makes the project-info-report:scm goal > fail. > Same as MNG-2225, but using build extensions instead of jars in M2_HOME -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2228) Classloader problem loading jars from build extensions
[ http://jira.codehaus.org/browse/MNG-2228?page=all ] Carlos Sanchez updated MNG-2228: Attachment: (was: testwagonscm-extensions.tgz) > Classloader problem loading jars from build extensions > -- > > Key: MNG-2228 > URL: http://jira.codehaus.org/browse/MNG-2228 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.4 >Reporter: Carlos Sanchez >Priority: Blocker > Fix For: 2.1 > > Attachments: MNG-2228.tgz > > > When running "mvn install" and "mvn testwagonscm:test" in the attached test > case you get a ClassCastException although the Class to assign to and the > assigned one are the same. The problem seems to be that they come from > different classloaders. This problem makes the project-info-report:scm goal > fail. > Same as MNG-2225, but using build extensions instead of jars in M2_HOME -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2228) Classloader problem loading jars from build extensions
[ http://jira.codehaus.org/browse/MNG-2228?page=all ] Carlos Sanchez updated MNG-2228: Attachment: MNG-2228.tgz New patch with less snapshots > Classloader problem loading jars from build extensions > -- > > Key: MNG-2228 > URL: http://jira.codehaus.org/browse/MNG-2228 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.4 >Reporter: Carlos Sanchez >Priority: Blocker > Fix For: 2.1 > > Attachments: MNG-2228.tgz > > > When running "mvn install" and "mvn testwagonscm:test" in the attached test > case you get a ClassCastException although the Class to assign to and the > assigned one are the same. The problem seems to be that they come from > different classloaders. This problem makes the project-info-report:scm goal > fail. > Same as MNG-2225, but using build extensions instead of jars in M2_HOME -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2228) Classloader problem loading jars from build extensions
[ http://jira.codehaus.org/browse/MNG-2228?page=all ] Brett Porter closed MNG-2228. - Assignee: Brett Porter Resolution: Fixed Fix Version/s: (was: 2.1) 2.0.5 > Classloader problem loading jars from build extensions > -- > > Key: MNG-2228 > URL: http://jira.codehaus.org/browse/MNG-2228 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.4 >Reporter: Carlos Sanchez > Assigned To: Brett Porter >Priority: Blocker > Fix For: 2.0.5 > > Attachments: MNG-2228.tgz > > > When running "mvn install" and "mvn testwagonscm:test" in the attached test > case you get a ClassCastException although the Class to assign to and the > assigned one are the same. The problem seems to be that they come from > different classloaders. This problem makes the project-info-report:scm goal > fail. > Same as MNG-2225, but using build extensions instead of jars in M2_HOME -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-1021) buildDefinition action returns result "input" which is not mapped in xwork.xml
buildDefinition action returns result "input" which is not mapped in xwork.xml -- Key: CONTINUUM-1021 URL: http://jira.codehaus.org/browse/CONTINUUM-1021 Project: Continuum Issue Type: Bug Components: Web - UI Affects Versions: 1.1 Reporter: Christian Gruber Priority: Critical Attachments: buildDefFix.patch buildDefinition action returns result "input" which is not mapped in xwork.xml. Simple attached fix adds the input result in xwork.xml. It might be wise to change the results declared int he class to "success", but I can't tell all the places this class is used, so I figure I'd do the shortest path. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2681) Add cli flag to set all snapshot repos to updatePolicy = never
Add cli flag to set all snapshot repos to updatePolicy = never -- Key: MNG-2681 URL: http://jira.codehaus.org/browse/MNG-2681 Project: Maven 2 Issue Type: New Feature Components: Command Line Reporter: Jason Dillon Can we get a flag to mvn, which will set all snapshot repos updatePolicy to never? I'm trying to get a build that will always use locally installed snapshots, but allow new deps to be downloaded if needed. All I can think of now is to create a new profile which redefines all of the snapshot repos with never... but that gets messy as I need to add a profile to every pom that defines a repo. Would it be hard to implement a simple cli flag, like -nsu (--no-snapshot-updates) which will just force all snap repos to never update? This would be very, very, very helpful for automated builds, when the local repo cache is known to have the right deps. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2681) Add cli flag to set all snapshot repos to updatePolicy = never
[ http://jira.codehaus.org/browse/MNG-2681?page=all ] Jason Dillon updated MNG-2681: -- Attachment: MNG-2681.diff Patch against trunk/components. Can someone validate this? > Add cli flag to set all snapshot repos to updatePolicy = never > -- > > Key: MNG-2681 > URL: http://jira.codehaus.org/browse/MNG-2681 > Project: Maven 2 > Issue Type: New Feature > Components: Command Line >Reporter: Jason Dillon > Attachments: MNG-2681.diff > > > Can we get a flag to mvn, which will set all snapshot repos updatePolicy to > never? > I'm trying to get a build that will always use locally installed snapshots, > but allow new deps to be downloaded if needed. All I can think of now is to > create a new profile which redefines all of the snapshot repos with > never... but that gets messy as I need to add a > profile to every pom that defines a repo. > Would it be hard to implement a simple cli flag, like -nsu > (--no-snapshot-updates) which will just force all snap repos to never update? > This would be very, very, very helpful for automated builds, when the local > repo cache is known to have the right deps. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
