[jira] Updated: (MNG-2680) refactored and improved function names of maven web ui test classes and utilities

2006-11-24 Thread Marvin King (JIRA)
 [ http://jira.codehaus.org/browse/MNG-2680?page=all ]

Marvin King updated MNG-2680:
-

Attachment: MNG2680-maven-web-ui-tests.patch

> refactored and improved function names of maven web ui test classes and 
> utilities
> -
>
> Key: MNG-2680
> URL: http://jira.codehaus.org/browse/MNG-2680
> Project: Maven 2
>  Issue Type: Test
>Reporter: Marvin King
> Attachments: MNG2680-maven-web-ui-tests.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] Created: (CONTINUUM-1013) updated function invocations to reflect changes in maven-web-ui-tests

2006-11-24 Thread Marvin King (JIRA)
updated function invocations to reflect changes in maven-web-ui-tests
-

 Key: CONTINUUM-1013
 URL: http://jira.codehaus.org/browse/CONTINUUM-1013
 Project: Continuum
  Issue Type: Test
  Components: Web - UI
Reporter: Marvin King




-- 
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-1013) updated function invocations to reflect changes in maven-web-ui-tests

2006-11-24 Thread Marvin King (JIRA)
 [ http://jira.codehaus.org/browse/CONTINUUM-1013?page=all ]

Marvin King updated CONTINUUM-1013:
---

Attachment: CONTINUUM1013-continuum-webapp-test.patch

> updated function invocations to reflect changes in maven-web-ui-tests
> -
>
> Key: CONTINUUM-1013
> URL: http://jira.codehaus.org/browse/CONTINUUM-1013
> Project: Continuum
>  Issue Type: Test
>  Components: Web - UI
>Reporter: Marvin King
> Attachments: CONTINUUM1013-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] Commented: (MAVENUPLOAD-1241) JWebUnit 1.4 RC1 available.

2006-11-24 Thread Julien HENRY (JIRA)
[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-1241?page=comments#action_80967 ] 

Julien HENRY commented on MAVENUPLOAD-1241:
---

Thanks !

> JWebUnit 1.4 RC1 available.
> ---
>
> Key: MAVENUPLOAD-1241
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1241
> Project: maven-upload-requests
>  Issue Type: New Feature
>Reporter: Julien HENRY
> Assigned To: Carlos Sanchez
>
> Hi,
> Please sync from http://jwebunit.sourceforge.net/m2-repo to get the JWebUnit 
> 1.4 RC1 release.
> Thanks
> Julien

-- 
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: (MPJDIFF-10) jdiff doclet fails with jdk 1.4

2006-11-24 Thread Lukas Theussl (JIRA)
jdiff doclet fails with jdk 1.4
---

 Key: MPJDIFF-10
 URL: http://jira.codehaus.org/browse/MPJDIFF-10
 Project: maven-jdiff-plugin
  Issue Type: Bug
Affects Versions: 1.5
Reporter: Lukas Theussl
 Fix For: 1.5.1


Running jdiff with jdk 1.4.2_10 gives the following exception:

{noformat} 
[javadoc] JDiff: doclet started ...
[javadoc] javadoc: In doclet class jdiff.JDiff,  method start has thrown an 
exception java.lang.reflect.InvocationTargetException
[javadoc] java.lang.NoClassDefFoundError: org/xml/sax/ext/Attributes2
{noformat} 

The build succeeds but there are no files generated. Note that it only happens 
with the current svn version of the plugin, it works when downgrading to the 
released maven-jdiff-plugin-1.5 . It also works with java 5 since the missing 
class is contained in the rt.jar. I fixed it by adding a dependency to 
xml-apis, but I think that should not be necessary?

-- 
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: (CONTINUUM-729) Conitnnum buids project twice when clicking on 'build now'

2006-11-24 Thread Przemyslaw Madzik (JIRA)
[ http://jira.codehaus.org/browse/CONTINUUM-729?page=comments#action_80973 
] 

Przemyslaw Madzik commented on CONTINUUM-729:
-

Same behaviour at my place with firefox under win32 and mozilla under linux. 
With IE is ok, but i get strange message in log:

8032773 [SocketListener0-4] WARN  JPOX.RDBMS.SQL  - Object with id "0" not 
found !

> Conitnnum buids project twice when clicking on 'build now'
> --
>
> Key: CONTINUUM-729
> URL: http://jira.codehaus.org/browse/CONTINUUM-729
> Project: Continuum
>  Issue Type: Bug
>  Components: Web interface
>Affects Versions: 1.0.3
> Environment: Continuum-1.0.3 / Maven-2.0.4 / JSE 1.5.0 update 06 / 
> Windows Server 2003
>Reporter: Thomas Cornet
> Fix For: 1.1
>
> Attachments: continuum-log.txt
>
>
> Whenever I click on the 'build now' link in the project list or on the 'build 
> now' button in the project info page, the selected project is build twice. If 
> I let the scheduler do its work, all is fine and build once when necessary, 
> the problem occurs only when I force the build

-- 
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-1012) added web-ui test for account security policies

2006-11-24 Thread Marvin King (JIRA)
 [ http://jira.codehaus.org/browse/CONTINUUM-1012?page=all ]

Marvin King updated CONTINUUM-1012:
---

Attachment: CONTINUUM1012-continuum-webapp-test-11242006-2.patch

> added web-ui test for account security policies
> ---
>
> Key: CONTINUUM-1012
> URL: http://jira.codehaus.org/browse/CONTINUUM-1012
> Project: Continuum
>  Issue Type: Test
>  Components: Web - Security
>Reporter: Marvin King
> Attachments: CONTINUUM1012-continuum-webapp-test-11242006-2.patch, 
> CONTINUUM1012-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] Created: (CONTINUUM-1014) Add remaining changes from continuum-acegi branch, and project group editing enhancements

2006-11-24 Thread Lester Ecarma (JIRA)
Add remaining changes from continuum-acegi branch, and project group editing 
enhancements
-

 Key: CONTINUUM-1014
 URL: http://jira.codehaus.org/browse/CONTINUUM-1014
 Project: Continuum
  Issue Type: Task
Reporter: Lester Ecarma




-- 
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-1014) Add remaining changes from continuum-acegi branch, and project group editing enhancements

2006-11-24 Thread Lester Ecarma (JIRA)
 [ http://jira.codehaus.org/browse/CONTINUUM-1014?page=all ]

Lester Ecarma updated CONTINUUM-1014:
-

Attachment: continuum-acegi-merge.patch

Attached patch should bring in the changes made to continuum-acegi branch, as 
well as some enhancements made to provide project group editing 

> Add remaining changes from continuum-acegi branch, and project group editing 
> enhancements
> -
>
> Key: CONTINUUM-1014
> URL: http://jira.codehaus.org/browse/CONTINUUM-1014
> Project: Continuum
>  Issue Type: Task
>Reporter: Lester Ecarma
> Attachments: continuum-acegi-merge.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: (MNG-870) Make plugin discovery reactor aware

2006-11-24 Thread Kenney Westerhof (JIRA)
[ http://jira.codehaus.org/browse/MNG-870?page=comments#action_80983 ] 

Kenney Westerhof commented on MNG-870:
--

Hm, stupid jira.. ;)

I've created a new issue at MNG-2677.

> Make plugin discovery reactor aware
> ---
>
> Key: MNG-870
> URL: http://jira.codehaus.org/browse/MNG-870
> Project: Maven 2
>  Issue Type: New Feature
>  Components: Plugins and Lifecycle
>Reporter: Kenney Westerhof
> Assigned To: Brett Porter
> Fix For: 2.0-beta-2
>
> Attachments: MNG-870.diff
>
>   Original Estimate: 1 hour
>  Time Spent: 1 hour
>  Remaining Estimate: 0 minutes
>
> If plugin discovery is reactor aware, plugins that are part of a reactor 
> build and are used to aid the build
> can be used in one go. Else first the plugin should be installed, and then 
> the rest of the project can
> be built.
> But mainly this aids in integration testing for plugins: the maven-it-plugin 
> in sandbox can't add the current plugin
> + artifact to the lifecycle without making some methods public. If the plugin 
> were to be discovered using the reactor,
> those methods can remain private.

-- 
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-2680) refactored and improved function names of maven web ui test classes and utilities

2006-11-24 Thread Emmanuel Venisse (JIRA)
 [ http://jira.codehaus.org/browse/MNG-2680?page=all ]

Emmanuel Venisse closed MNG-2680.
-

  Assignee: Emmanuel Venisse
Resolution: Fixed

Applied.

> refactored and improved function names of maven web ui test classes and 
> utilities
> -
>
> Key: MNG-2680
> URL: http://jira.codehaus.org/browse/MNG-2680
> Project: Maven 2
>  Issue Type: Test
>Reporter: Marvin King
> Assigned To: Emmanuel Venisse
> Attachments: MNG2680-maven-web-ui-tests.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-179) Create a branch instead of a tag

2006-11-24 Thread Franck HUGOT (JIRA)
[ http://jira.codehaus.org/browse/MRELEASE-179?page=comments#action_80986 ] 

Franck HUGOT commented on MRELEASE-179:
---

I think this is not a lot of modification in this plugin becaue branching does 
the same work than tagging in svn.
Does somebody can give an overview about when this feature will be planned?



> Create a branch instead of a tag
> 
>
> Key: MRELEASE-179
> URL: http://jira.codehaus.org/browse/MRELEASE-179
> Project: Maven 2.x Release Plugin
>  Issue Type: Improvement
>Affects Versions: 2.0-beta-4
> Environment: Debian JDK 1.5
>Reporter: Franck HUGOT
>
> When I release I first create a branch instead of a tag.
> Can you add this feature?  I would like to choose when I prepare a release.
> Thanks in advance.

-- 
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-1012) added web-ui test for account security policies

2006-11-24 Thread Emmanuel Venisse (JIRA)
 [ http://jira.codehaus.org/browse/CONTINUUM-1012?page=all ]

Emmanuel Venisse closed CONTINUUM-1012.
---

 Assignee: Emmanuel Venisse
   Resolution: Fixed
Fix Version/s: 1.1

Applied. Thanks.

> added web-ui test for account security policies
> ---
>
> Key: CONTINUUM-1012
> URL: http://jira.codehaus.org/browse/CONTINUUM-1012
> Project: Continuum
>  Issue Type: Test
>  Components: Web - Security
>Reporter: Marvin King
> Assigned To: Emmanuel Venisse
> Fix For: 1.1
>
> Attachments: CONTINUUM1012-continuum-webapp-test-11242006-2.patch, 
> CONTINUUM1012-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] Closed: (CONTINUUM-1013) updated function invocations to reflect changes in maven-web-ui-tests

2006-11-24 Thread Emmanuel Venisse (JIRA)
 [ http://jira.codehaus.org/browse/CONTINUUM-1013?page=all ]

Emmanuel Venisse closed CONTINUUM-1013.
---

 Assignee: Emmanuel Venisse
   Resolution: Fixed
Fix Version/s: 1.1

Applied.

> updated function invocations to reflect changes in maven-web-ui-tests
> -
>
> Key: CONTINUUM-1013
> URL: http://jira.codehaus.org/browse/CONTINUUM-1013
> Project: Continuum
>  Issue Type: Test
>  Components: Web - UI
>Reporter: Marvin King
> Assigned To: Emmanuel Venisse
> Fix For: 1.1
>
> Attachments: CONTINUUM1013-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: (MRM-186) rename "depended on by" to "used by"

2006-11-24 Thread Emmanuel Venisse (JIRA)
 [ http://jira.codehaus.org/browse/MRM-186?page=all ]

Emmanuel Venisse updated MRM-186:
-

 Fix Version/s: (was: 1.0)
1.0-beta-1
Patch attached: Yes

> rename "depended on by" to "used by"
> 
>
> Key: MRM-186
> URL: http://jira.codehaus.org/browse/MRM-186
> Project: Archiva
>  Issue Type: Improvement
>  Components: web application
>Reporter: Brett Porter
> Fix For: 1.0-beta-1
>
> Attachments: MRM-186.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] Closed: (MRM-183) Archiva Plexus Runtime works only when copying tools.jar to the core directory

2006-11-24 Thread Emmanuel Venisse (JIRA)
 [ http://jira.codehaus.org/browse/MRM-183?page=all ]

Emmanuel Venisse closed MRM-183.


 Assignee: Emmanuel Venisse
   Resolution: Fixed
Fix Version/s: 1.0-beta-1

Already fixed.

> Archiva Plexus Runtime works only when copying tools.jar to the core directory
> --
>
> Key: MRM-183
> URL: http://jira.codehaus.org/browse/MRM-183
> Project: Archiva
>  Issue Type: Bug
>  Components: web application
>Reporter: Wilfred Springer
> Assigned To: Emmanuel Venisse
> Fix For: 1.0-beta-1
>
>
> Archiva Plexus Runtime works only when copying tools.jar to the core 
> directory. Othwerwise it will complain about the fact that is unable to find 
> the compiler classes from the JDK, and suggests to set JAVA_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: (MRM-209) plexus.sh must include tools.jar on the classpath

2006-11-24 Thread Emmanuel Venisse (JIRA)
 [ http://jira.codehaus.org/browse/MRM-209?page=all ]

Emmanuel Venisse closed MRM-209.


 Assignee: Emmanuel Venisse
   Resolution: Fixed
Fix Version/s: 1.0-beta-1

> plexus.sh must include tools.jar on the classpath
> -
>
> Key: MRM-209
> URL: http://jira.codehaus.org/browse/MRM-209
> Project: Archiva
>  Issue Type: Bug
>  Components: web application
>Reporter: Dirk Olmes
> Assigned To: Emmanuel Venisse
> Fix For: 1.0-beta-1
>
>
> The plexush.sh that's generated in the archiva-plexus-runtime model does not 
> include tools.jar to the classpath of the JVM that is started. This causes 
> error messages when first accessing the web application about being unable to 
> compile JSPs.
> The last line of plexus.sh currently looks like this:
> {code}
> exec "$JAVACMD" \
>   $PLEXUS_OPTS \
>   -classpath "${PLEXUS_HOME}"/core/boot/classworlds-*.jar \
> {code}
> 
> but should have $TOOLS_JAR included in the -classpath argument's parameter.

-- 
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: (MRM-230) A standard error message should display anytime an incorrect User ID or password is entered

2006-11-24 Thread Emmanuel Venisse (JIRA)
 [ http://jira.codehaus.org/browse/MRM-230?page=all ]

Emmanuel Venisse closed MRM-230.


   Resolution: Fixed
Fix Version/s: 1.0-beta-1

> A standard error message should display anytime an incorrect User ID or 
> password is entered
> ---
>
> Key: MRM-230
> URL: http://jira.codehaus.org/browse/MRM-230
> Project: Archiva
>  Issue Type: Task
>Reporter: Maria Odea Ching
> Assigned To: Maria Odea Ching
> Fix For: 1.0-beta-1
>
>
> The error message should be:
> "You have entered an incorrect username and/or password"

-- 
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-235) Change button text to "Update Repository" on the edit repository page

2006-11-24 Thread Emmanuel Venisse (JIRA)
 [ http://jira.codehaus.org/browse/MRM-235?page=all ]

Emmanuel Venisse updated MRM-235:
-

 Assignee: Emmanuel Venisse
  Description: 
On Administration -> Edit Repository, the submit button text is "Change 
Repository".

It should be "Update Repository" for consistency with "Update User" in user 
management, and to avoid confusion.



  was:

On Administration -> Edit Repository, the submit button text is "Change 
Repository".

It should be "Update Repository" for consistency with "Update User" in user 
management, and to avoid confusion.



Affects Version/s: (was: 1.0)
   1.0-beta-1
Fix Version/s: 1.0-beta-1

> Change button text to "Update Repository" on the edit repository page
> -
>
> Key: MRM-235
> URL: http://jira.codehaus.org/browse/MRM-235
> Project: Archiva
>  Issue Type: Improvement
>  Components: web application
>Affects Versions: 1.0-beta-1
>Reporter: Wendy Smoak
> Assigned To: Emmanuel Venisse
> Fix For: 1.0-beta-1
>
>
> On Administration -> Edit Repository, the submit button text is "Change 
> Repository".
> It should be "Update Repository" for consistency with "Update User" in user 
> management, and to avoid confusion.

-- 
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-202) Change the top-left logo to be an Archiva logo that goes to the front page of the instance

2006-11-24 Thread Emmanuel Venisse (JIRA)
 [ http://jira.codehaus.org/browse/MRM-202?page=all ]

Emmanuel Venisse updated MRM-202:
-

Fix Version/s: 1.0-beta-1

> Change the top-left logo to be an Archiva logo that goes to the front page of 
> the instance
> --
>
> Key: MRM-202
> URL: http://jira.codehaus.org/browse/MRM-202
> Project: Archiva
>  Issue Type: Wish
>  Components: web application
>Reporter: Henri Yandell
>Priority: Minor
> Fix For: 1.0-beta-1
>
>
> It's very jarring to click on the Maven link in the top left and be taken to 
> the Maven website. In other apps this would take me to the front page for the 
> app. 
> I'd also wish for it to be customisable, rather than having to show an 
> Archiva logo.

-- 
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-228) Archiva Client Configuration Howto

2006-11-24 Thread Emmanuel Venisse (JIRA)
 [ http://jira.codehaus.org/browse/MRM-228?page=all ]

Emmanuel Venisse updated MRM-228:
-

Fix Version/s: 1.0-beta-1

> Archiva Client Configuration Howto
> --
>
> Key: MRM-228
> URL: http://jira.codehaus.org/browse/MRM-228
> Project: Archiva
>  Issue Type: Improvement
>Affects Versions: 1.0-beta-1
> Environment: Archiva Running on Tomcat 5.5.17
>Reporter: Daniel Mohni
>Priority: Trivial
> Fix For: 1.0-beta-1
>
> Attachments: archiva_client_config.patch
>
>
> I created a Client Configuration Page where I discribe how the Client should 
> be configured to use archiva as maven proxy

-- 
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

2006-11-24 Thread Francois Le Fevre (JIRA)
[ http://jira.codehaus.org/browse/MCHANGES-58?page=comments#action_80994 ] 

Francois Le Fevre commented on MCHANGES-58:
---

I totally agree, JIRA is a commercial bugzilla!!

> 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: (MAVENUPLOAD-1225) Upload Stripes 1.4.2 to IBiblio repository (please)

2006-11-24 Thread Tim Fennell (JIRA)
[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-1225?page=comments#action_80998 ] 

Tim Fennell commented on MAVENUPLOAD-1225:
--

I've updated our POM for the next release, but if you could upload the linked 
bundle as-is, that'd be great.  Thanks.

> Upload Stripes 1.4.2 to IBiblio repository (please)
> ---
>
> Key: MAVENUPLOAD-1225
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1225
> Project: maven-upload-requests
>  Issue Type: Task
>Reporter: Tim Fennell
>
> Please upload Stripes 1.4.2 to IBiblio.

-- 
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-235) Change button text to "Update Repository" on the edit repository page

2006-11-24 Thread Wendy Smoak (JIRA)
 [ http://jira.codehaus.org/browse/MRM-235?page=all ]

Wendy Smoak updated MRM-235:


Attachment: MRM-235-wsmoak.diff

The same button text is used when editing proxied repositories. 

The patch (rooted at archiva-webapp) changes both buttons.

> Change button text to "Update Repository" on the edit repository page
> -
>
> Key: MRM-235
> URL: http://jira.codehaus.org/browse/MRM-235
> Project: Archiva
>  Issue Type: Improvement
>  Components: web application
>Affects Versions: 1.0-beta-1
>Reporter: Wendy Smoak
> Assigned To: Emmanuel Venisse
> Fix For: 1.0-beta-1
>
> Attachments: MRM-235-wsmoak.diff
>
>
> On Administration -> Edit Repository, the submit button text is "Change 
> Repository".
> It should be "Update Repository" for consistency with "Update User" in user 
> management, and to avoid confusion.

-- 
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-235) Change button text to "Update Repository" on the edit repository page

2006-11-24 Thread Emmanuel Venisse (JIRA)
 [ http://jira.codehaus.org/browse/MRM-235?page=all ]

Emmanuel Venisse updated MRM-235:
-

Patch attached: Yes

> Change button text to "Update Repository" on the edit repository page
> -
>
> Key: MRM-235
> URL: http://jira.codehaus.org/browse/MRM-235
> Project: Archiva
>  Issue Type: Improvement
>  Components: web application
>Affects Versions: 1.0-beta-1
>Reporter: Wendy Smoak
> Assigned To: Emmanuel Venisse
> Fix For: 1.0-beta-1
>
> Attachments: MRM-235-wsmoak.diff
>
>
> On Administration -> Edit Repository, the submit button text is "Change 
> Repository".
> It should be "Update Repository" for consistency with "Update User" in user 
> management, and to avoid confusion.

-- 
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: (MRM-236) Unable to 'proxy through' more than one managed repo

2006-11-24 Thread Wendy Smoak (JIRA)
Unable to 'proxy through' more than one managed repo


 Key: MRM-236
 URL: http://jira.codehaus.org/browse/MRM-236
 Project: Archiva
  Issue Type: Bug
  Components: web application
Affects Versions: 1.0
 Environment: Affects r478814 1.0-SNAPSHOT
Reporter: Wendy Smoak


On Proxied Repositories -> Add or Edit, only the 'first' managed repository 
added to the system is listed in the 'Proxied through' select list.

It should allow you to choose any of the managed repositories. 



-- 
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-236) Unable to 'proxy through' more than one managed repo

2006-11-24 Thread Arnaud Heritier (JIRA)
[ http://jira.codehaus.org/browse/MRM-236?page=comments#action_81003 ] 

Arnaud Heritier commented on MRM-236:
-

I also saw this bug. In fact the list is updated if you restart your 
webapp/server.

> Unable to 'proxy through' more than one managed repo
> 
>
> Key: MRM-236
> URL: http://jira.codehaus.org/browse/MRM-236
> Project: Archiva
>  Issue Type: Bug
>  Components: web application
>Affects Versions: 1.0
> Environment: Affects r478814 1.0-SNAPSHOT
>Reporter: Wendy Smoak
>
> On Proxied Repositories -> Add or Edit, only the 'first' managed repository 
> added to the system is listed in the 'Proxied through' select list.
> It should allow you to choose any of the managed repositories. 

-- 
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: (MEV-462) Bad checksum pattern for archetype plugin?

2006-11-24 Thread Wendy Smoak (JIRA)
Bad checksum pattern for archetype plugin?
--

 Key: MEV-462
 URL: http://jira.codehaus.org/browse/MEV-462
 Project: Maven Evangelism
  Issue Type: Bug
Reporter: Wendy Smoak


Archiva as a proxy for central is complaining about this checksum:

2006-11-24 12:34:32,218 [btpool0-15] WARN  ProxyRequestHandler- The
checksum was invalid: org/apache/maven/archetype/maven-archetype/1.0-alpha-4/mav
en-archetype-1.0-alpha-4.pom.md5: Supplied checksum does not match checksum patt
ern
2006-11-24 12:34:32,218 [btpool0-15] WARN  ProxyRequestHandler- Skip
ping repository Maven Central: Checksum failures occurred while downloading org/
apache/maven/archetype/maven-archetype/1.0-alpha-4/maven-archetype-1.0-alpha-4.p
om


-- 
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-186) rename "depended on by" to "used by"

2006-11-24 Thread Henri Yandell (JIRA)
[ http://jira.codehaus.org/browse/MRM-186?page=comments#action_81008 ] 

Henri Yandell commented on MRM-186:
---

Me? Surely not. Who would be foolish enough to do such a thing.

There are no 'depended on by's in the code references. There are lots of 
'dependees'; but the obvious change for them would be 'users' and that'll be 
too confusing.

> rename "depended on by" to "used by"
> 
>
> Key: MRM-186
> URL: http://jira.codehaus.org/browse/MRM-186
> Project: Archiva
>  Issue Type: Improvement
>  Components: web application
>Reporter: Brett Porter
> Fix For: 1.0-beta-1
>
> Attachments: MRM-186.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: (MRM-186) rename "depended on by" to "used by"

2006-11-24 Thread Henri Yandell (JIRA)
[ http://jira.codehaus.org/browse/MRM-186?page=comments#action_81009 ] 

Henri Yandell commented on MRM-186:
---

 svn ci -m "Changing 'Dependend on by' to 'Used by' as per #MRM-186. Code isn't 
changed yet as it's the word 'dependees' and I don't have a good replacement 
for that" archiva-webapp

Sending
archiva-webapp/src/main/java/org/apache/maven/archiva/web/mapper/RepositoryActionMapper.java
Sendingarchiva-webapp/src/main/webapp/WEB-INF/jsp/showArtifact.jsp
Transmitting file data ..
Committed revision 478968.

> rename "depended on by" to "used by"
> 
>
> Key: MRM-186
> URL: http://jira.codehaus.org/browse/MRM-186
> Project: Archiva
>  Issue Type: Improvement
>  Components: web application
>Reporter: Brett Porter
> Fix For: 1.0-beta-1
>
> Attachments: MRM-186.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] Created: (MEV-463) bad version MD in commons-dbutils

2006-11-24 Thread Steve Loughran (JIRA)
bad version MD in commons-dbutils
-

 Key: MEV-463
 URL: http://jira.codehaus.org/browse/MEV-463
 Project: Maven Evangelism
  Issue Type: Bug
  Components: Invalid POM
Reporter: Steve Loughran


It is meant to be 1.0:
http://www.ibiblio.org/maven2/commons-dbutils/commons-dbutils/1.0/commons-dbutils-1.0.pom

but as well as declaring its dependency on junit as non optional
(sigh), its declared version is 1.0-RC1

I dont know what m1/m2 does with this, but Ivy refuses to touch the
file on account of its inconsistencies.

Either there's an artifact that's been accidentally pre-released, or
the wrong version tag is in the MD.

-- 
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: (MRM-228) Archiva Client Configuration Howto

2006-11-24 Thread Henri Yandell (JIRA)
 [ http://jira.codehaus.org/browse/MRM-228?page=all ]

Henri Yandell closed MRM-228.
-

Resolution: Fixed

svn ci -m "Applying Daniel Mohni's excellent documentation on using Archiva 
from Maven. "

Adding src/site/apt/guides/getting-started/maven-configuration.apt
Sendingsrc/site/site.xml
Transmitting file data ..
Committed revision 479011.

I edited it a chunk, so feel free to re-open if I butchered anything.

> Archiva Client Configuration Howto
> --
>
> Key: MRM-228
> URL: http://jira.codehaus.org/browse/MRM-228
> Project: Archiva
>  Issue Type: Improvement
>Affects Versions: 1.0-beta-1
> Environment: Archiva Running on Tomcat 5.5.17
>Reporter: Daniel Mohni
>Priority: Trivial
> Fix For: 1.0-beta-1
>
> Attachments: archiva_client_config.patch
>
>
> I created a Client Configuration Page where I discribe how the Client should 
> be configured to use archiva as maven proxy

-- 
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