[jira] Closed: (MAVEN-1848) Upgrade maven-multichanges-plugin to v 1.3

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MAVEN-1848.
--

   Resolution: Fixed
Fix Version/s: 1.1-rc1

> Upgrade maven-multichanges-plugin to v 1.3
> --
>
> Key: MAVEN-1848
> URL: http://jira.codehaus.org/browse/MAVEN-1848
> Project: Maven 1
>  Issue Type: Sub-task
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
> Fix For: 1.1-rc1
>
>


-- 
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: (MAVEN-1849) Upgrade maven-plugin-plugin to v 1.7.1

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MAVEN-1849.
--

   Resolution: Fixed
Fix Version/s: 1.1-rc1

> Upgrade maven-plugin-plugin to v 1.7.1
> --
>
> Key: MAVEN-1849
> URL: http://jira.codehaus.org/browse/MAVEN-1849
> Project: Maven 1
>  Issue Type: Sub-task
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
> Fix For: 1.1-rc1
>
>


-- 
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: (MAVEN-1847) Upgrade maven-javadoc-plugin to v 1.9

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MAVEN-1847.
--

   Resolution: Fixed
Fix Version/s: 1.1-rc1

> Upgrade maven-javadoc-plugin to v 1.9
> -
>
> Key: MAVEN-1847
> URL: http://jira.codehaus.org/browse/MAVEN-1847
> Project: Maven 1
>  Issue Type: Sub-task
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
> Fix For: 1.1-rc1
>
>


-- 
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: (MAVEN-1846) Upgrade maven-jar-plugin to v 1.8.1

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MAVEN-1846.
--

   Resolution: Fixed
Fix Version/s: 1.1-rc1

> Upgrade maven-jar-plugin to v 1.8.1
> ---
>
> Key: MAVEN-1846
> URL: http://jira.codehaus.org/browse/MAVEN-1846
> Project: Maven 1
>  Issue Type: Sub-task
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
> Fix For: 1.1-rc1
>
>


-- 
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: (MAVEN-1847) Upgrade maven-javadoc-plugin to v 1.9

[Arnaud Heritier (JIRA)]

Upgrade maven-javadoc-plugin to v 1.9
-

 Key: MAVEN-1847
 URL: http://jira.codehaus.org/browse/MAVEN-1847
 Project: Maven 1
  Issue Type: Sub-task
Reporter: Arnaud Heritier
Assignee: Arnaud Heritier




-- 
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: (MAVEN-1845) Upgrade maven-jalopy-plugin to v 1.5.1

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MAVEN-1845.
--

   Resolution: Fixed
Fix Version/s: 1.1-rc1

> Upgrade maven-jalopy-plugin to v 1.5.1
> --
>
> Key: MAVEN-1845
> URL: http://jira.codehaus.org/browse/MAVEN-1845
> Project: Maven 1
>  Issue Type: Sub-task
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
> Fix For: 1.1-rc1
>
>


-- 
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: (MAVEN-1849) Upgrade maven-plugin-plugin to v 1.7.1

[Arnaud Heritier (JIRA)]

Upgrade maven-plugin-plugin to v 1.7.1
--

 Key: MAVEN-1849
 URL: http://jira.codehaus.org/browse/MAVEN-1849
 Project: Maven 1
  Issue Type: Sub-task
Reporter: Arnaud Heritier
Assignee: Arnaud Heritier




-- 
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: (MAVEN-1844) Upgrade maven-idea-plugin to v 1.7

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MAVEN-1844.
--

   Resolution: Fixed
Fix Version/s: 1.1-rc1

> Upgrade maven-idea-plugin to v 1.7
> --
>
> Key: MAVEN-1844
> URL: http://jira.codehaus.org/browse/MAVEN-1844
> Project: Maven 1
>  Issue Type: Sub-task
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
> Fix For: 1.1-rc1
>
>


-- 
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: (MAVEN-1848) Upgrade maven-multichanges-plugin to v 1.3

[Arnaud Heritier (JIRA)]

Upgrade maven-multichanges-plugin to v 1.3
--

 Key: MAVEN-1848
 URL: http://jira.codehaus.org/browse/MAVEN-1848
 Project: Maven 1
  Issue Type: Sub-task
Reporter: Arnaud Heritier
Assignee: Arnaud Heritier




-- 
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: (MAVEN-1846) Upgrade maven-jar-plugin to v 1.8.1

[Arnaud Heritier (JIRA)]

Upgrade maven-jar-plugin to v 1.8.1
---

 Key: MAVEN-1846
 URL: http://jira.codehaus.org/browse/MAVEN-1846
 Project: Maven 1
  Issue Type: Sub-task
Reporter: Arnaud Heritier
Assignee: Arnaud Heritier




-- 
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: (MAVEN-1845) Upgrade maven-jalopy-plugin to v 1.5.1

[Arnaud Heritier (JIRA)]

Upgrade maven-jalopy-plugin to v 1.5.1
--

 Key: MAVEN-1845
 URL: http://jira.codehaus.org/browse/MAVEN-1845
 Project: Maven 1
  Issue Type: Sub-task
Reporter: Arnaud Heritier
Assignee: Arnaud Heritier




-- 
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: (MAVEN-1844) Upgrade maven-idea-plugin to v 1.7

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MAVEN-1844:
---

Summary: Upgrade maven-idea-plugin to v 1.7  (was: Upgrade 
maven-idea-plugin to v1.7)

> Upgrade maven-idea-plugin to v 1.7
> --
>
> Key: MAVEN-1844
> URL: http://jira.codehaus.org/browse/MAVEN-1844
> Project: Maven 1
>  Issue Type: Sub-task
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
>


-- 
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: (MAVEN-1844) Upgrade maven-idea-plugin to v1.7

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MAVEN-1844:
---

Summary: Upgrade maven-idea-plugin to v1.7  (was: Upgrade maven-idea-plugin 
1.7)

> Upgrade maven-idea-plugin to v1.7
> -
>
> Key: MAVEN-1844
> URL: http://jira.codehaus.org/browse/MAVEN-1844
> Project: Maven 1
>  Issue Type: Sub-task
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
>


-- 
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: (MAVEN-1844) Upgrade maven-idea-plugin 1.7

[Arnaud Heritier (JIRA)]

Upgrade maven-idea-plugin 1.7
-

 Key: MAVEN-1844
 URL: http://jira.codehaus.org/browse/MAVEN-1844
 Project: Maven 1
  Issue Type: Sub-task
Reporter: Arnaud Heritier
Assignee: Arnaud Heritier




-- 
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: (MAVEN-1808) Put MAVEN_HOME in the system environment variables if the user has admin rights

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MAVEN-1808.
--

Resolution: Fixed

Already done

> Put MAVEN_HOME in the system environment variables if the user has admin 
> rights
> ---
>
> Key: MAVEN-1808
> URL: http://jira.codehaus.org/browse/MAVEN-1808
> Project: Maven 1
>  Issue Type: Improvement
>  Components: installer
>Affects Versions: 1.1-beta-3
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
> Fix For: 1.1-rc1
>
>
> On windows we often encounter different problems when this variable is set in 
> the user environment system.

-- 
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: (MAVEN-1840) java.util.ConcurrentModificationException in Goal

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MAVEN-1840.
--

   Resolution: Won't Fix
Fix Version/s: (was: 1.1-rc1)

This problem seems to be only while running maven in continuum ...

> java.util.ConcurrentModificationException in Goal
> -
>
> Key: MAVEN-1840
> URL: http://jira.codehaus.org/browse/MAVEN-1840
> Project: Maven 1
>  Issue Type: Bug
>  Components: jelly/ant integration
>Affects Versions: 1.1-beta-3
> Environment: build maven 1.1 RC 1 on continuum 1.0 on solaris with 
> jdk 1.4
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
>
> maven:run-touchstone:
> Trying to get missing dependencies (and updated snapshots) required by 
> Touchstone:
> - Checking for an update of touchstone:touchstone:SNAPSHOT:jar from 
> http://people.apache.org/repo/m1-snapshot-repository/
> Skipping download as local copy is up to date!
> - Checking for an update of touchstone:test:SNAPSHOT:war from 
> http://people.apache.org/repo/m1-snapshot-repository/
> Skipping download as local copy is up to date!
> build:start:
> clean:clean:
> xdoc:clean:
> [delete] Deleting directory 
> /export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target
> clean:
> java:prepare-filesystem:
> [mkdir] Created dir: 
> /export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/classes
> java:init:
> java:compile:
> [echo] 
> maven.dependency.classpath:
> /export/home/continuum/.maven/repository/ant/jars/ant-optional-1.5.1.jar
> /export/home/continuum/maven-1.1/lib/maven.jar
> /export/home/continuum/.maven/repository/maven/jars/maven-model-3.0.1.jar
> 
> /export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/lib/a.jar
> 
> /export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/lib/b.jar
> 
> /export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/lib/c-1.0-alpha-1-SNAPSHOT.jar
> 
> /export/home/continuum/.maven/repository/classworlds/jars/classworlds-1.0-beta-1.jar
> 
> /export/home/continuum/.maven/repository/touchstone/jars/touchstone-SNAPSHOT.jar
> 
> /export/home/continuum/.maven/repository/commons-jelly/jars/commons-jelly-tags-interaction-1.0.jar
> 
> 
> [echo] Compiling to 
> /export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/classes
> [javac] Compiling 1 source file to 
> /export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/classes
> java:jar-resources:
> Copying 1 file to 
> /export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/classes
> Copying 1 file to 
> /export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/classes/org/apache/maven/touchstone
> Copying 2 files to 
> /export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/classes
> test:test:
> java:prepare-filesystem:
> java:init:
> java:compile:
> [echo] 
> maven.dependency.classpath:
> /export/home/continuum/.maven/repository/ant/jars/ant-optional-1.5.1.jar
> /export/home/continuum/maven-1.1/lib/maven.jar
> /export/home/continuum/.maven/repository/maven/jars/maven-model-3.0.1.jar
> 
> /export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/lib/a.jar
> 
> /export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/lib/b.jar
> 
> /export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/lib/c-1.0-alpha-1-SNAPSHOT.jar
> 
> /export/home/continuum/.maven/repository/classworlds/jars/classworlds-1.0-beta-1.jar
> 
> /export/home/continuum/.maven/repository/touchstone/jars/touchstone-SNAPSHOT.jar
> 
> /export/home/continuum/.maven/repository/commons-jelly/jars/commons-jelly-tags-interaction-1.0.jar
> 
> 
> [echo] Compiling to 
> /export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/classes
> java:jar-resources:
> test:prepare-filesystem:
> [mkdir] Created dir: 
> /export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/test-classes
> [mkdir] Created dir: 
> /export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/test-reports
> test:test-resources:
> Copying 1 file to 
> /export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/test-classes/org/apache/maven/touchstone
> Copying 1 file to 
> /export/home/continuum/continuum_1.0.3

issues@maven.apache.org

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPNSIS-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MPNSIS-15.
-

Resolution: Fixed

Done

> Use MODERN_UI macros for a better L&F
> -
>
> Key: MPNSIS-15
> URL: http://jira.codehaus.org/browse/MPNSIS-15
> Project: maven-nsis-plugin
>  Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
>Priority: Minor
> Fix For: 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] Commented: (MRM-323) Managed repo in archiva cannot be accessed thru direct webdav url even with valid credentials (Archiva deployed in Tomcat)

[Arnaud Heritier (JIRA)]

[ 
http://jira.codehaus.org/browse/MRM-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94685
 ] 

Arnaud Heritier commented on MRM-323:
-

ok, Joakim,

  Thanks for your investigation. I'll try it also on the trunk (or future 
branch).
  One remark, however, load-on-startup must be an integer >= 0.

> Managed repo in archiva cannot be accessed thru direct webdav url even with 
> valid credentials (Archiva deployed in Tomcat)
> --
>
> Key: MRM-323
> URL: http://jira.codehaus.org/browse/MRM-323
> Project: Archiva
>  Issue Type: Bug
>  Components: WebDAV interface
>Affects Versions: 1.0
> Environment: - Tomcat 5.5.20
> - Linux
> - Mozilla Firefox
>Reporter: Maria Odea Ching
>
> Steps to re-create issue:
> - Deploy Archiva in Tomcat, then start tomcat
> - Access Archiva in browser and set the required configurations
> - Add A Managed Repository with the following configuration:
>   - id: snapshots
>   - name: snapshots
>   - url: snapshots (it would have the value 
> http://localhost:[PORT]/archiva/repository/snapshots)
>   - directory: snapshots
> - Go to User Management and add the Repository Observer role for the 
> 'snapshots' repo to the current user
> - Open a new tab in your browser then type the webdav URL: 
> http://localhost:[PORT]/archiva/repository/snapshots
> - Supply the user credentials for the 'snapshots' repository. You still 
> wouldn't be able to access it even if you supply the correct credentials. 
> Also, the following error shows up in the Archiva logs when you try to build 
> a Maven project with your settings.xml file configured to use the 
> repositories in archiva:
> 102476 [http-9696-Processor23] ERROR 
> org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/archiva].[RepositoryServlet]
>   - Servlet.service() for servlet RepositoryServlet threw exception
> javax.servlet.ServletException: Unable to service DAV request due to 
> unconfigured DavServerComponent for prefix [snapshots].
>   at 
> org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.service(MultiplexedWebDavServlet.java:93)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>   at 
> com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:189)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>   at 
> com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:39)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>   at 
> com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>   at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
>   at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
>   at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
>   at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
>   at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
>   at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
>   at 
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
>   at 
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
>   at 
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
>   at 
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
>   at 
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
>   at java.lang.Thread.run(Thread.java:619)

-- 
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-323) Managed repo in archiva cannot be accessed thru direct webdav url even with valid credentials (Archiva deployed in Tomcat)

[Arnaud Heritier (JIRA)]

[ 
http://jira.codehaus.org/browse/MRM-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94474
 ] 

Arnaud Heritier commented on MRM-323:
-

Don't you think that it can be due to the contextPath that we have in tomcat 
and not in plexus ?? Otherwise I don't see !

> Managed repo in archiva cannot be accessed thru direct webdav url even with 
> valid credentials (Archiva deployed in Tomcat)
> --
>
> Key: MRM-323
> URL: http://jira.codehaus.org/browse/MRM-323
> Project: Archiva
>  Issue Type: Bug
>  Components: WebDAV interface
>Affects Versions: 1.0
> Environment: - Tomcat 5.5.20
> - Linux
> - Mozilla Firefox
>Reporter: Maria Odea Ching
>
> Steps to re-create issue:
> - Deploy Archiva in Tomcat, then start tomcat
> - Access Archiva in browser and set the required configurations
> - Add A Managed Repository with the following configuration:
>   - id: snapshots
>   - name: snapshots
>   - url: snapshots (it would have the value 
> http://localhost:[PORT]/archiva/repository/snapshots)
>   - directory: snapshots
> - Go to User Management and add the Repository Observer role for the 
> 'snapshots' repo to the current user
> - Open a new tab in your browser then type the webdav URL: 
> http://localhost:[PORT]/archiva/repository/snapshots
> - Supply the user credentials for the 'snapshots' repository. You still 
> wouldn't be able to access it even if you supply the correct credentials. 
> Also, the following error shows up in the Archiva logs when you try to build 
> a Maven project with your settings.xml file configured to use the 
> repositories in archiva:
> 102476 [http-9696-Processor23] ERROR 
> org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/archiva].[RepositoryServlet]
>   - Servlet.service() for servlet RepositoryServlet threw exception
> javax.servlet.ServletException: Unable to service DAV request due to 
> unconfigured DavServerComponent for prefix [snapshots].
>   at 
> org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.service(MultiplexedWebDavServlet.java:93)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>   at 
> com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:189)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>   at 
> com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:39)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>   at 
> com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>   at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
>   at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
>   at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
>   at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
>   at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
>   at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
>   at 
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
>   at 
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
>   at 
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
>   at 
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
>   at 
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
>   at java.lang.Thread.run(Thread.java:619)

-- 
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-323) Managed repo in archiva cannot be accessed thru direct webdav url even with valid credentials (Archiva deployed in Tomcat)

[Arnaud Heritier (JIRA)]

[ 
http://jira.codehaus.org/browse/MRM-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94468
 ] 

Arnaud Heritier commented on MRM-323:
-

same thing with tomcat 5.0 on windows 2003 server

> Managed repo in archiva cannot be accessed thru direct webdav url even with 
> valid credentials (Archiva deployed in Tomcat)
> --
>
> Key: MRM-323
> URL: http://jira.codehaus.org/browse/MRM-323
> Project: Archiva
>  Issue Type: Bug
>  Components: WebDAV interface
>Affects Versions: 1.0
> Environment: - Tomcat 5.5.20
> - Linux
> - Mozilla Firefox
>Reporter: Maria Odea Ching
>
> Steps to re-create issue:
> - Deploy Archiva in Tomcat, then start tomcat
> - Access Archiva in browser and set the required configurations
> - Add A Managed Repository with the following configuration:
>   - id: snapshots
>   - name: snapshots
>   - url: snapshots (it would have the value 
> http://localhost:[PORT]/archiva/repository/snapshots)
>   - directory: snapshots
> - Go to User Management and add the Repository Observer role for the 
> 'snapshots' repo to the current user
> - Open a new tab in your browser then type the webdav URL: 
> http://localhost:[PORT]/archiva/repository/snapshots
> - Supply the user credentials for the 'snapshots' repository. You still 
> wouldn't be able to access it even if you supply the correct credentials. 
> Also, the following error shows up in the Archiva logs when you try to build 
> a Maven project with your settings.xml file configured to use the 
> repositories in archiva:
> 102476 [http-9696-Processor23] ERROR 
> org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/archiva].[RepositoryServlet]
>   - Servlet.service() for servlet RepositoryServlet threw exception
> javax.servlet.ServletException: Unable to service DAV request due to 
> unconfigured DavServerComponent for prefix [snapshots].
>   at 
> org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.service(MultiplexedWebDavServlet.java:93)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>   at 
> com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:189)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>   at 
> com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:39)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>   at 
> com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>   at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
>   at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
>   at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
>   at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
>   at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
>   at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
>   at 
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
>   at 
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
>   at 
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
>   at 
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
>   at 
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
>   at java.lang.Thread.run(Thread.java:619)

-- 
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: (MAVEN-1755) Backward Incompability : Usage of xml entities in the POM doesn't work in maven 1.1 beta 1 & 2

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MAVEN-1755.
--

Resolution: Fixed

Fixed with maven-model 3.0.2

> Backward Incompability : Usage of xml entities in the POM doesn't work in 
> maven 1.1 beta 1 & 2
> --
>
> Key: MAVEN-1755
> URL: http://jira.codehaus.org/browse/MAVEN-1755
> Project: Maven 1
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.1-beta-1, 1.1-beta-2, 1.1-beta-3
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
>Priority: Critical
> Fix For: 1.1-rc1
>
> Attachments: project-entities.zip
>
>
> In maven 1.0.X it was possible to use entities in the POM.
> It was used for example to share some elements like the organization, ...

-- 
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: (MPIDEA-41) A new property where I can set a comma separated list of excluded directories

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPIDEA-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MPIDEA-41:
--

Fix Version/s: (was: 1.7)

> A new property where I can set a comma separated list of excluded directories
> -
>
> Key: MPIDEA-41
> URL: http://jira.codehaus.org/browse/MPIDEA-41
> Project: maven-idea-plugin
>  Issue Type: New Feature
>Affects Versions: 1.6
>Reporter: Ross Mason
>
> This is usful for for exculding things like xdoc and lib dirs

-- 
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: (MPPLUGIN-30) Plugins on a per-user basis

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPPLUGIN-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MPPLUGIN-30:


Fix Version/s: (was: 1.7.1)

> Plugins on a per-user basis
> ---
>
> Key: MPPLUGIN-30
> URL: http://jira.codehaus.org/browse/MPPLUGIN-30
> Project: maven-plugin-plugin
>  Issue Type: Bug
>Affects Versions: 1.5
> Environment: Linux (Debian), Maven 1.1
>Reporter: Rodrigo S. de Castro
> Attachments: maven-plugin-plugin-installation.patch
>
>
> Problem:
> When I try to compile Geronimo, it fails when trying to install its plugin 
> into the $MAVEN_HOME directory, since it is a shared installation in 
> /usr/local/maven-1.1. It does not install the plugins on a per-user basis to 
> my maven local directory (~/.maven). Is this the intended behaviour?
> Analysis:
> In the org.apache.maven.plugin.PluginManager class, which is called for 
> plugin:install-now, the plugin is installed in the user plugins dir, as we 
> may check through the following code:
>   if ( cache )
>   {
>FileUtils.copyFileToDirectory( file, userPluginsDir );
>cacheManager.registerPlugin( pluginName, housing );
>housing.parse( cacheManager );
>cacheManager.saveCache( unpackedPluginsDir );
>   }
> Since I am not sure if the behaviour was intentional, I would like to know 
> your opinion about that. 
> From the point of view that there is an inconsistent behaviour, I will attach 
> a patch that changes plugin:install to do the same as plugin:install-now: 
> install in the user directory. With this patch, current repository version of 
> Apache Geronimo works properly.
> Concerning plugin removal, the code already check both directories (global 
> and user), as you may check here (plugin/plugin.jelly):
> 
>   
> 
>   
> 
> 
>   
> 
>   
> Thank you!

-- 
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: (MAVEN-1775) Upgrade maven-eclipse-plugin to v. 1.12

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MAVEN-1775:
---

Summary: Upgrade maven-eclipse-plugin to v. 1.12  (was: Upgrade 
maven-eclipse-plugin to v. 1.11.1)

> Upgrade maven-eclipse-plugin to v. 1.12
> ---
>
> Key: MAVEN-1775
> URL: http://jira.codehaus.org/browse/MAVEN-1775
> Project: Maven 1
>  Issue Type: Sub-task
>  Components: planning
>Affects Versions: 1.1-beta-3
>Reporter: Stephane Nicoll
>Assignee: Stephane Nicoll
> Fix For: 1.1-rc1
>
>
> http://jira.codehaus.org/browse/MPECLIPSE?report=com.atlassian.jira.plugin.system.project:roadmap-panel

-- 
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: (MPECLIPSE-129) Provide update-url

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPECLIPSE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MPECLIPSE-129.
-

  Assignee: Arnaud Heritier
Resolution: Won't Fix

It's not a plugin for eclipse but a plugin for maven. We don't need an update 
site.
If you are looking for a plugin to use maven inside eclipse :
Maven 1 : http://mevenide.codehaus.org/
Maven 2 : http://m2eclipse.codehaus.org/

> Provide update-url
> --
>
> Key: MPECLIPSE-129
> URL: http://jira.codehaus.org/browse/MPECLIPSE-129
> Project: maven-eclipse-plugin
>  Issue Type: Improvement
>Reporter: Edwin Martin
>Assignee: Arnaud Heritier
>Priority: Minor
>
> I couldn't find any update-url for the Maven-Eclipse plugin.
> The project should provide an update-url for Eclipse.
> 1) It's much more user-friendly to install a pluging via an update-url.
> 2) It's easier to update a plugin to a newer version.
> 3) I think it's quite easy to provide an update-url.
> 4) It's the current way of providing plugins.

-- 
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: (MPECLIPSE-127) Add support for wtp 1.5

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPECLIPSE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MPECLIPSE-127.
-

Resolution: Fixed

Fixed. Snapshot deployed

> Add support for wtp 1.5
> ---
>
> Key: MPECLIPSE-127
> URL: http://jira.codehaus.org/browse/MPECLIPSE-127
> Project: maven-eclipse-plugin
>  Issue Type: Improvement
>Affects Versions: 1.11
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
> Fix For: 1.12
>
>
> Can't we reuse some code from the m2 plugin ??

-- 
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: (MPECLIPSE-102) Running 'maven:eclipse' turns CheckStyle off for the project.

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPECLIPSE-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MPECLIPSE-102:
--

Fix Version/s: (was: 1.11.1)

There's a workaround and it's not easy to fix in maven 1 because we don't read 
the original file.

> Running 'maven:eclipse' turns CheckStyle off for the project.
> -
>
> Key: MPECLIPSE-102
> URL: http://jira.codehaus.org/browse/MPECLIPSE-102
> Project: maven-eclipse-plugin
>  Issue Type: Bug
>Affects Versions: 1.9
>Reporter: Jamie Bisotti
>Assignee: Stephane Nicoll
>
> Assuming project is already setup in Eclipse 3.1 (either manually or via the 
> eclipse plugin)
> 1. Install CheckStyle Eclispe plugin
> 2. Turn it on for the project.
> 3. Shutdown Eclipse
> 4. Run maven eclipse on the project
> 5. Restart Eclipse
> 6. Notice CheckStyle is now turned off.

-- 
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: (MAVEN-126) Add a -logfile option

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MAVEN-126:
--

Assignee: (was: Arnaud Heritier)

> Add a -logfile option
> -
>
> Key: MAVEN-126
> URL: http://jira.codehaus.org/browse/MAVEN-126
> Project: Maven 1
>  Issue Type: New Feature
>  Components: cli
> Environment: Windows 98
>Reporter: Andrew Stevens
>Priority: Minor
> Attachments: AntProjectBuilder.java.patch, 
> JellyBuildListener.java.patch, MAVEN126.patch, MavenConstants.java.patch
>
>
> One of the options I find useful in Ant is '-logfile ', which 
> redirects the build's output to a given file. It would be nice if I could do 
> the same with Maven; I've not had much success trying to use Win98's command 
> line redirection or paging on Maven's output.

-- 
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: (MAVEN-1733) Bootstrap failure: Unable to delete directory ...

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MAVEN-1733:
---

Assignee: (was: Arnaud Heritier)

> Bootstrap failure: Unable to delete directory ...
> -
>
> Key: MAVEN-1733
> URL: http://jira.codehaus.org/browse/MAVEN-1733
> Project: Maven 1
>  Issue Type: Bug
>Affects Versions: 1.1-beta-3
> Environment: Win XP, svn Checked out revision 355781.
>Reporter: Jeff Jensen
> Attachments: buildit.log
>
>
> bootstrap consistently fails.  Attached is log for my last run.
> This is an interesting line from it:
>  [exec] Caused by: Unable to delete directory 
> C:\devroot\reference\maven\maven-1\plugins\trunk\genapp\src\plugin-test\nonStandardDirsTest\target
> I completely deleted the svn dirs and got latest.  The error above prior was 
> this:
>  [exec] Root cause
>  [exec] Unable to delete directory 
> C:\devroot\reference\maven\maven-1\plugins\trunk\genapp\src\plugin-test\mavenHomeLocalTemplateTest\target
> And the run that failed before that one did not have an "unable to delete 
> dir". (I did about 6 or so bootstraps today, trying to get it to work)
> They are on different plugins, such as Javadoc, Test Genapp.  I have 3 of my 
> last logs, and a couple of them are the test genapp (not the middle run of 
> the 3).
> I hope something helps here, and this isn't some silly chase.  Thanks again 
> for looking into it.
> I tried to determine some environment thing for me.
> Oh, typing of environment, I am using JDK 1.5.  Is that OK, or perhaps the 
> prob?

-- 
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: (MAVEN-1790) Fix headers sent to the repository

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MAVEN-1790:
---

Assignee: (was: Arnaud Heritier)

> Fix headers sent to the repository
> --
>
> Key: MAVEN-1790
> URL: http://jira.codehaus.org/browse/MAVEN-1790
> Project: Maven 1
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 1.0, 1.0.1, 1.0.2, 1.1-beta-1, 1.1-beta-2, 1.1-beta-3
>Reporter: Arnaud Heritier
>
> Modify the headers in the requests sent to the repositories to know the 
> version of maven and the OS
> Perhaps it's already for the OS but we have to test it.
> It will help us to track the calls in the new repo.

-- 
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: (MAVEN-1839) Add maven-modello-plugin v 1.0

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MAVEN-1839.
--

   Resolution: Fixed
Fix Version/s: 1.1-rc1

Done

> Add maven-modello-plugin v 1.0
> --
>
> Key: MAVEN-1839
> URL: http://jira.codehaus.org/browse/MAVEN-1839
> Project: Maven 1.x
>  Issue Type: Sub-task
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
> Fix For: 1.1-rc1
>
>


-- 
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: (MAVEN-1829) Upgrade maven-site-plugin to v 1.7.2

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MAVEN-1829.
--

Resolution: Fixed

Done

> Upgrade maven-site-plugin to v 1.7.2
> 
>
> Key: MAVEN-1829
> URL: http://jira.codehaus.org/browse/MAVEN-1829
> Project: Maven 1.x
>  Issue Type: Sub-task
>Affects Versions: 1.1-beta-3
>Reporter: Lukas Theussl
>Assignee: Arnaud Heritier
> Fix For: 1.1-rc1
>
>
> http://jira.codehaus.org/browse/MPSITE?report=com.atlassian.jira.plugin.system.project:roadmap-panel

-- 
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: (MAVEN-1841) Upgrade maven-announcement-plugin to v 1.4.1

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MAVEN-1841.
--

   Resolution: Fixed
Fix Version/s: 1.1-rc1

Done

> Upgrade maven-announcement-plugin to v 1.4.1
> 
>
> Key: MAVEN-1841
> URL: http://jira.codehaus.org/browse/MAVEN-1841
> Project: Maven 1.x
>  Issue Type: Sub-task
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
> Fix For: 1.1-rc1
>
>


-- 
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: (MAVEN-1843) Upgrade maven-file-activity-plugin to v 1.6.1

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MAVEN-1843.
--

   Resolution: Fixed
Fix Version/s: 1.1-rc1

done

> Upgrade maven-file-activity-plugin to v 1.6.1
> -
>
> Key: MAVEN-1843
> URL: http://jira.codehaus.org/browse/MAVEN-1843
> Project: Maven 1.x
>  Issue Type: Sub-task
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
> Fix For: 1.1-rc1
>
>


-- 
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: (MAVEN-1842) Upgrade maven-developer-activity-plugin to v 1.6.1

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MAVEN-1842.
--

   Resolution: Fixed
Fix Version/s: 1.1-rc1

Done

> Upgrade maven-developer-activity-plugin to v 1.6.1
> --
>
> Key: MAVEN-1842
> URL: http://jira.codehaus.org/browse/MAVEN-1842
> Project: Maven 1.x
>  Issue Type: Sub-task
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
> Fix For: 1.1-rc1
>
>


-- 
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-441) ConcurrentModificationException when doing build (maven1, multiproject:install)

[Arnaud Heritier (JIRA)]

[ 
http://jira.codehaus.org/browse/CONTINUUM-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93018
 ] 

Arnaud Heritier commented on CONTINUUM-441:
---

Sure ?
We have regularly a similar error :
http://maven.zones.apache.org:8180/continuum/servlet/continuum/target/ProjectBuild.vm?view=ProjectBuild&buildId=247&id=6

> ConcurrentModificationException when doing build (maven1, 
> multiproject:install)
> ---
>
> Key: CONTINUUM-441
> URL: http://jira.codehaus.org/browse/CONTINUUM-441
> Project: Continuum
>  Issue Type: Bug
>  Components: Core system
>Affects Versions: 1.0
>Reporter: Chris lutje Spelberg
>Assignee: Emmanuel Venisse
> Fix For: 1.0.2
>
>
> I get this exception when trying to build.
> java.util.ConcurrentModificationException
>   at 
> java.util.AbstractList$Itr.checkForComodification(AbstractList.java:448)
>   at java.util.AbstractList$Itr.next(AbstractList.java:419)
>   at 
> org.apache.maven.continuum.execution.maven.m1.DefaultMavenOneMetadataHelper.mapMetadata(DefaultMavenOneMetadataHelper.java:309)
>   at 
> org.apache.maven.continuum.execution.maven.m1.MavenOneBuildExecutor.updateProjectFromCheckOut(MavenOneBuildExecutor.java:84)
>   at 
> org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectoryContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction.java:59)
>   at 
> org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:168)
>   at 
> org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:53)
>   at 
> org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103)
>   at java.lang.Thread.run(Thread.java:534)
> My project.xml:
> 
> 
>   3
>   Project name
>   mygroupid
>   myartifactid
>   SNAPSHOT
>   
> Organization
> http://www/
>   
>   2005
>   my.package
>   My Short Description
>   
>   
> scm:cvs:pserver:[EMAIL PROTECTED]:/cvs/project:myartifact
> 
> scm:cvs:pserver:[EMAIL 
> PROTECTED]:/cvs/project:myartifact
> 
>   
>   
>   
> http://jira.codehaus.org/secure/BrowseProject.jspa?id=12345
> 

-- 
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: (MAVEN-1103) improve "goal not found" reporting

[Arnaud Heritier (JIRA)]

[ 
http://jira.codehaus.org/browse/MAVEN-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92986
 ] 

Arnaud Heritier commented on MAVEN-1103:


Ok, I'll check.
Sorry
I'm finishing my work on log I began several months ago.
It's quite ready, I'll commit it in some hours.
Thanks for your vigilance

> improve "goal not found" reporting
> --
>
> Key: MAVEN-1103
> URL: http://jira.codehaus.org/browse/MAVEN-1103
> Project: Maven 1.x
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 1.0-rc1
>Reporter: Brett Porter
>Assignee: Arnaud Heritier
>Priority: Minor
> Fix For: 1.1-rc1
>
>
> - goal not found should be an error message, not an exception when leaving 
> maven
> - goals that are not found should be reported before any building is done

-- 
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: (MAVEN-1843) Upgrade maven-file-activity-plugin to v 1.6.1

[Arnaud Heritier (JIRA)]

Upgrade maven-file-activity-plugin to v 1.6.1
-

 Key: MAVEN-1843
 URL: http://jira.codehaus.org/browse/MAVEN-1843
 Project: Maven 1.x
  Issue Type: Sub-task
Reporter: Arnaud Heritier




-- 
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: (MAVEN-1842) Upgrade maven-developer-activity-plugin to v 1.6.1

[Arnaud Heritier (JIRA)]

Upgrade maven-developer-activity-plugin to v 1.6.1
--

 Key: MAVEN-1842
 URL: http://jira.codehaus.org/browse/MAVEN-1842
 Project: Maven 1.x
  Issue Type: Sub-task
Reporter: Arnaud Heritier
Assignee: Arnaud Heritier




-- 
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: (MAVEN-1841) Upgrade maven-announcement-plugin to v 1.4.1

[Arnaud Heritier (JIRA)]

Upgrade maven-announcement-plugin to v 1.4.1


 Key: MAVEN-1841
 URL: http://jira.codehaus.org/browse/MAVEN-1841
 Project: Maven 1.x
  Issue Type: Sub-task
Reporter: Arnaud Heritier
Assignee: Arnaud Heritier




-- 
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: (MAVEN-1829) Upgrade maven-site-plugin to v 1.7.2

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MAVEN-1829:
---

Summary: Upgrade maven-site-plugin to v 1.7.2  (was: Upgrade 
maven-site-plugin to v 1.7.1)

> Upgrade maven-site-plugin to v 1.7.2
> 
>
> Key: MAVEN-1829
> URL: http://jira.codehaus.org/browse/MAVEN-1829
> Project: Maven 1.x
>  Issue Type: Sub-task
>Affects Versions: 1.1-beta-3
>Reporter: Lukas Theussl
>Assignee: Arnaud Heritier
> Fix For: 1.1-rc1
>
>
> http://jira.codehaus.org/browse/MPSITE?report=com.atlassian.jira.plugin.system.project:roadmap-panel

-- 
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] Reopened: (MAVEN-1829) Upgrade maven-site-plugin to v 1.7.1

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier reopened MAVEN-1829:



Release 1.7.2 to fix some problems with rsync feature

> Upgrade maven-site-plugin to v 1.7.1
> 
>
> Key: MAVEN-1829
> URL: http://jira.codehaus.org/browse/MAVEN-1829
> Project: Maven 1.x
>  Issue Type: Sub-task
>Affects Versions: 1.1-beta-3
>Reporter: Lukas Theussl
>Assignee: Lukas Theussl
> Fix For: 1.1-rc1
>
>
> http://jira.codehaus.org/browse/MPSITE?report=com.atlassian.jira.plugin.system.project:roadmap-panel

-- 
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: (MPA-87) Create a Jira Project for Modello plugin for maven 1.X

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPA-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MPA-87.
--

   Resolution: Fixed
Fix Version/s: 2007-q2

Done

> Create a Jira Project for Modello plugin for maven 1.X
> --
>
> Key: MPA-87
> URL: http://jira.codehaus.org/browse/MPA-87
> Project: Maven Project Administration
>  Issue Type: Task
>  Components: Issue Management
>Affects Versions: 2007-q2
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
> Fix For: 2007-q2
>
>
> Project: maven-modello-plugin
> Key: MPMODELLO
> URL: http://maven.apache.org/maven-1.x/plugins/modello/
> Project Lead: Arnaud Heritier
> Notification Scheme: Maven
> Permission Scheme: maven
> Project Category: Maven 1 Plugins

-- 
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: (MPA-33) turn off maven1 sync/uploads

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPA-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MPA-33:
---

Fix Version/s: (was: 2006-q4)

> turn off maven1 sync/uploads
> 
>
> Key: MPA-33
> URL: http://jira.codehaus.org/browse/MPA-33
> Project: Maven Project Administration
>  Issue Type: Sub-task
>  Components: repository management
>Affects Versions: 2006-q3
>Reporter: Brett Porter
>
> we need to stop uploading new artifacts to the maven1 repo, and stop syncing 
> outwards to ibiblio (we still need to sync in from other sources, however, 
> but this will soon be taken care of by the repo application).

-- 
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: (MPA-87) Create a Jira Project for Modello plugin for maven 1.X

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPA-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MPA-87:
---

Affects Version/s: (was: 2007-q1)
   2007-q2

> Create a Jira Project for Modello plugin for maven 1.X
> --
>
> Key: MPA-87
> URL: http://jira.codehaus.org/browse/MPA-87
> Project: Maven Project Administration
>  Issue Type: Task
>  Components: Issue Management
>Affects Versions: 2007-q2
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
>
> Project: maven-modello-plugin
> Key: MPMODELLO
> URL: http://maven.apache.org/maven-1.x/plugins/modello/
> Project Lead: Arnaud Heritier
> Notification Scheme: Maven
> Permission Scheme: maven
> Project Category: Maven 1 Plugins

-- 
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: (MPA-80) Open a staging sites area at http://maven.zones.apache.org/staging/

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPA-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MPA-80:
---

Fix Version/s: (was: 2006-q4)

> Open a staging sites area at http://maven.zones.apache.org/staging/
> ---
>
> Key: MPA-80
> URL: http://jira.codehaus.org/browse/MPA-80
> Project: Maven Project Administration
>  Issue Type: Task
>  Components: sites
>Affects Versions: 2006-q3
>Reporter: Arnaud Heritier
>Assignee: Jason van Zyl
>Priority: Minor
>
> As discussed here [1] it could be interesting for us to have a common staging 
> area to deploy our documentations (instead of using our accounts on 
> people.apache.org).
> Brett proposed to use the zone for that :
> http://maven.zones.apache.org/staging/ (maven 2)
> http://maven.zones.apache.org/staging/maven-1.x/ (maven 1 ie, following live 
> site structure).
> I think that all committers must have the rights to deploy the web sites here.
> [1] 
> http://www.nabble.com/CI-for-M1-%3A-Can-I-use-a-continuum-instance-somewhere---tf2051570.html

-- 
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: (MPA-57) migrate all Maven projects to the Basic Issue Creation Scheme in JIRA

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPA-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MPA-57:
---

Fix Version/s: (was: 2006-q4)

> migrate all Maven projects to the Basic Issue Creation Scheme in JIRA
> -
>
> Key: MPA-57
> URL: http://jira.codehaus.org/browse/MPA-57
> Project: Maven Project Administration
>  Issue Type: Task
>  Components: Issue Management
>Affects Versions: 2006-q3
>Reporter: Brett Porter
>


-- 
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: (MPA-29) Create mod_rewrite rules to divert m1 repository requests to the m2 repository

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPA-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MPA-29:
---

Fix Version/s: (was: 2006-q4)

> Create mod_rewrite rules to divert m1 repository requests to the m2 repository
> --
>
> Key: MPA-29
> URL: http://jira.codehaus.org/browse/MPA-29
> Project: Maven Project Administration
>  Issue Type: Task
>  Components: repository management
>Affects Versions: 2006-q3
>Reporter: Jason van Zyl
>Assignee: Brett Porter
>
> It is possible for us not to have to convert the repositories by turning an 
> m1 repository request into an m2 style request and direct it at the m2 
> repository. This would allow us to maintain the one canonical repository.

-- 
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: (MPA-32) make suitable arrangements with other maven mirrors

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPA-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MPA-32:
---

Fix Version/s: (was: 2006-q4)

> make suitable arrangements with other maven mirrors
> ---
>
> Key: MPA-32
> URL: http://jira.codehaus.org/browse/MPA-32
> Project: Maven Project Administration
>  Issue Type: Sub-task
>  Components: repository management
>Affects Versions: 2006-q3
>Reporter: Brett Porter
>
> once we turn off the additional syncing of maven1 content, then the other 
> mirrors will not get updated. We should see if they can map the content using 
> mod_rewrite as well

-- 
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: (MPA-78) add license text to confluence wikis

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPA-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MPA-78:
---

Fix Version/s: (was: 2006-q4)

> add license text to confluence wikis
> 
>
> Key: MPA-78
> URL: http://jira.codehaus.org/browse/MPA-78
> Project: Maven Project Administration
>  Issue Type: Task
>  Components: sites
>Reporter: Brett Porter
>
> we should add a notice to the wiki (perhaps in the footer?) that indicates to 
> users and contributors what the license for submitted content is (presumably, 
> ASL)

-- 
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: (MPA-72) Please make "sources" jar available to Maven1 users

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPA-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MPA-72:
---

Fix Version/s: (was: 2006-q4)

> Please make "sources" jar available to Maven1 users
> ---
>
> Key: MPA-72
> URL: http://jira.codehaus.org/browse/MPA-72
> Project: Maven Project Administration
>  Issue Type: Bug
>  Components: repository management
>Reporter: Emmanuel Venisse
>Assignee: Brett Porter
>
> Hello guys,
> From a previous post I know Maven1 repo is a redirect to maven2 repository 
> content, with path transcripted to match maven2 hierarchy.
> commons-collection (as an example) has sources jar in maven2 repo 
> (http://www.ibiblio.org/maven2/commons-collections/commons-collections/3.1/commons-collections-3.1-sources.jar),
>  but I cannot get them using maven1 from 
> http://www.ibiblio.org/maven/commons-collections/java-sources/commons-collections-3.1-sources.jar
> Maybe a new Apache rewrite rule may be required for this.
> I would also be very interested if someone can give me the rewrite rule used 
> on ibiblio to convert m1 dependency path to m2 repo hierarchy.
> Nicolas De Loof

-- 
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: (MPA-31) have ibiblio convert .htaccess rules to httpd.conf

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPA-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MPA-31:
---

Fix Version/s: (was: 2006-q4)

> have ibiblio convert .htaccess rules to httpd.conf
> --
>
> Key: MPA-31
> URL: http://jira.codehaus.org/browse/MPA-31
> Project: Maven Project Administration
>  Issue Type: Sub-task
>  Components: repository management
>Affects Versions: 2006-q3
>Reporter: Brett Porter
>
> after a sufficient period of testing, ibiblio has requested that the rules be 
> moved to httpd.conf as its performance will be better than in .htaccess

-- 
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: (MPA-51) Create a New JIRA Project for Maven Site

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPA-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MPA-51:
---

Fix Version/s: (was: 2006-q4)

> Create a New JIRA Project for Maven Site
> 
>
> Key: MPA-51
> URL: http://jira.codehaus.org/browse/MPA-51
> Project: Maven Project Administration
>  Issue Type: Task
>Reporter: Carlos Sanchez
>
> The Maven site itself needs a new JIRA project to capture problems, needs, 
> and tasks related to Maven site improvment.
> Hmmm, group_id, artifact_id and version.  Left 'em blank.

-- 
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: (MPA-46) Remove or change m1 plugins leaders

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPA-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MPA-46:
---

Fix Version/s: (was: 2006-q4)

> Remove or change m1 plugins leaders
> ---
>
> Key: MPA-46
> URL: http://jira.codehaus.org/browse/MPA-46
> Project: Maven Project Administration
>  Issue Type: Task
>  Components: Issue Management
>Reporter: Arnaud Heritier
>Priority: Minor
>
> The list of leaders for m1 plugins is no more revelant.
> Users can suppose that there are a lot of guys working on them whereas we are 
> only 3 (actually).
> I think it's not possible to not have a leader for a project but perhaps we 
> could create a generic account for the maven team.
> WDYT?

-- 
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: (MPA-43) rename m1 plugins in JIRA

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPA-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MPA-43:
---

Fix Version/s: (was: 2006-q4)

> rename m1 plugins in JIRA
> -
>
> Key: MPA-43
> URL: http://jira.codehaus.org/browse/MPA-43
> Project: Maven Project Administration
>  Issue Type: Improvement
>  Components: Issue Management
>Affects Versions: 2006-q3
>Reporter: Brett Porter
>
> can we bulk change the name of the JIRA projects for the maven 1 plugins to 
> be Maven 1.x XXX like the Maven 2 equivalents to reduce 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: (MPA-9) Create top-level Maven site

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPA-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MPA-9:
--

Fix Version/s: (was: 2006-q4)

> Create top-level Maven site
> ---
>
> Key: MPA-9
> URL: http://jira.codehaus.org/browse/MPA-9
> Project: Maven Project Administration
>  Issue Type: Task
>  Components: sites
>Affects Versions: 2006-q3
>Reporter: Jason van Zyl
>Assignee: Brett Porter
>
> Create top-level Maven site using db.apache.org as a template.

-- 
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: (MAVEN-1103) improve "goal not found" reporting

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MAVEN-1103.
--

 Assignee: Arnaud Heritier
   Resolution: Fixed
Fix Version/s: 1.1-rc1

$ maven foo
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.1-RC1-SNAPSHOT

Trying to get missing dependencies (and updated snapshots) required by Maven:
- Checking for an update of maven:maven-model:3.0.2-SNAPSHOT:jar from 
http://people.apache.org/repo/m1-snapshot-repository/
Skipping download as local copy is up to date!
---
BUILD FAILED
>> Goal 'foo' does not exist in this project.
---
Total time   : 2 seconds
Finished at  : Saturday, April 14, 2007 1:59:56 AM CEST
Final Memory : 2M/3M
---

> improve "goal not found" reporting
> --
>
> Key: MAVEN-1103
> URL: http://jira.codehaus.org/browse/MAVEN-1103
> Project: Maven 1.x
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 1.0-rc1
>Reporter: Brett Porter
>Assignee: Arnaud Heritier
>Priority: Minor
> Fix For: 1.1-rc1
>
>
> - goal not found should be an error message, not an exception when leaving 
> maven
> - goals that are not found should be reported before any building is done

-- 
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: (MAVEN-1840) java.util.ConcurrentModificationException in Goal

[Arnaud Heritier (JIRA)]

java.util.ConcurrentModificationException in Goal
-

 Key: MAVEN-1840
 URL: http://jira.codehaus.org/browse/MAVEN-1840
 Project: Maven 1.x
  Issue Type: Bug
  Components: jelly/ant integration
Affects Versions: 1.1-beta-3
 Environment: build maven 1.1 RC 1 on continuum 1.0 on solaris with jdk 
1.4
Reporter: Arnaud Heritier
 Fix For: 1.1-rc1


maven:run-touchstone:
Trying to get missing dependencies (and updated snapshots) required by 
Touchstone:
- Checking for an update of touchstone:touchstone:SNAPSHOT:jar from 
http://people.apache.org/repo/m1-snapshot-repository/
Skipping download as local copy is up to date!
- Checking for an update of touchstone:test:SNAPSHOT:war from 
http://people.apache.org/repo/m1-snapshot-repository/
Skipping download as local copy is up to date!
build:start:

clean:clean:
xdoc:clean:

[delete] Deleting directory 
/export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target

clean:

java:prepare-filesystem:
[mkdir] Created dir: 
/export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/classes

java:init:

java:compile:
[echo] 
maven.dependency.classpath:
/export/home/continuum/.maven/repository/ant/jars/ant-optional-1.5.1.jar
/export/home/continuum/maven-1.1/lib/maven.jar
/export/home/continuum/.maven/repository/maven/jars/maven-model-3.0.1.jar

/export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/lib/a.jar

/export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/lib/b.jar

/export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/lib/c-1.0-alpha-1-SNAPSHOT.jar

/export/home/continuum/.maven/repository/classworlds/jars/classworlds-1.0-beta-1.jar

/export/home/continuum/.maven/repository/touchstone/jars/touchstone-SNAPSHOT.jar

/export/home/continuum/.maven/repository/commons-jelly/jars/commons-jelly-tags-interaction-1.0.jar


[echo] Compiling to 
/export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/classes
[javac] Compiling 1 source file to 
/export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/classes

java:jar-resources:
Copying 1 file to 
/export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/classes
Copying 1 file to 
/export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/classes/org/apache/maven/touchstone
Copying 2 files to 
/export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/classes

test:test:
java:prepare-filesystem:

java:init:

java:compile:
[echo] 
maven.dependency.classpath:
/export/home/continuum/.maven/repository/ant/jars/ant-optional-1.5.1.jar
/export/home/continuum/maven-1.1/lib/maven.jar
/export/home/continuum/.maven/repository/maven/jars/maven-model-3.0.1.jar

/export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/lib/a.jar

/export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/lib/b.jar

/export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/lib/c-1.0-alpha-1-SNAPSHOT.jar

/export/home/continuum/.maven/repository/classworlds/jars/classworlds-1.0-beta-1.jar

/export/home/continuum/.maven/repository/touchstone/jars/touchstone-SNAPSHOT.jar

/export/home/continuum/.maven/repository/commons-jelly/jars/commons-jelly-tags-interaction-1.0.jar


[echo] Compiling to 
/export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/classes

java:jar-resources:

test:prepare-filesystem:
[mkdir] Created dir: 
/export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/test-classes
[mkdir] Created dir: 
/export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/test-reports

test:test-resources:
Copying 1 file to 
/export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/test-classes/org/apache/maven/touchstone
Copying 1 file to 
/export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/test-classes

test:compile:
[javac] Compiling 1 source file to 
/export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/test-classes


jar:jar:
[jar] Building jar: 
/export/home/continuum/continuum_1.0.3_data/working-directory/6/src/test/touchstone-build/target/touchstone-1.0.jar

touchstone-tests:
xdoc:init-i18n:
[echo] Init the i18n support

xdoc:init:
[echo] Generates the directory struct

[jira] Closed: (MPARTIFACT-75) Allow to sign artifacts to deploy

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPARTIFACT-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MPARTIFACT-75.
-

Resolution: Fixed

Done

> Allow to sign artifacts to deploy
> -
>
> Key: MPARTIFACT-75
> URL: http://jira.codehaus.org/browse/MPARTIFACT-75
> Project: maven-artifact-plugin
>  Issue Type: New Feature
>Affects Versions: 1.8
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
>Priority: Critical
> Fix For: 1.9
>
>
> It's important for us to ease the release of 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] Created: (MAVEN-1839) Add maven-modello-plugin v 1.0

[Arnaud Heritier (JIRA)]

Add maven-modello-plugin v 1.0
--

 Key: MAVEN-1839
 URL: http://jira.codehaus.org/browse/MAVEN-1839
 Project: Maven 1.x
  Issue Type: Sub-task
Reporter: Arnaud Heritier
Assignee: Arnaud Heritier




-- 
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: (MAVEN-1836) Upgrade maven-clover-plugin to v 1.11.2

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MAVEN-1836.
--

  Assignee: Lukas Theussl
Resolution: Fixed

Released on March 29th

> Upgrade maven-clover-plugin to v 1.11.2
> ---
>
> Key: MAVEN-1836
> URL: http://jira.codehaus.org/browse/MAVEN-1836
> Project: Maven 1.x
>  Issue Type: Sub-task
>Affects Versions: 1.1-beta-3
>Reporter: Lukas Theussl
>Assignee: Lukas Theussl
> Fix For: 1.1-rc1
>
>
> http://jira.codehaus.org/browse/MPCLOVER?report=com.atlassian.jira.plugin.system.project:roadmap-panel

-- 
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: (MAVEN-1782) Upgrade maven-jdiff-plugin to v. 1.5.1

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MAVEN-1782.
--

  Assignee: Lukas Theussl
Resolution: Fixed

Released on March 29th

> Upgrade maven-jdiff-plugin to v. 1.5.1
> --
>
> Key: MAVEN-1782
> URL: http://jira.codehaus.org/browse/MAVEN-1782
> Project: Maven 1.x
>  Issue Type: Sub-task
>  Components: planning
>Affects Versions: 1.1-beta-3
>Reporter: Lukas Theussl
>Assignee: Lukas Theussl
> Fix For: 1.1-rc1
>
>
> http://jira.codehaus.org/browse/MPJDIFF?report=com.atlassian.jira.plugin.system.project:roadmap-panel

-- 
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: (MAVEN-1809) Upgrade maven-pdf-plugin to v 2.5.1

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MAVEN-1809.
--

Resolution: Fixed

Released on March 29th

> Upgrade maven-pdf-plugin to v 2.5.1
> ---
>
> Key: MAVEN-1809
> URL: http://jira.codehaus.org/browse/MAVEN-1809
> Project: Maven 1.x
>  Issue Type: Sub-task
>  Components: planning
>Affects Versions: 1.1-beta-3
>Reporter: Arnaud Heritier
>Assignee: Lukas Theussl
> Fix For: 1.1-rc1
>
>
> http://jira.codehaus.org/browse/MPPDF?report=com.atlassian.jira.plugin.system.project:roadmap-panel

-- 
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: (MAVEN-1838) Upgrade maven-pmd-plugin to v 1.10

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MAVEN-1838.
--

Resolution: Fixed

Released on March 29th

> Upgrade maven-pmd-plugin to v  1.10
> ---
>
> Key: MAVEN-1838
> URL: http://jira.codehaus.org/browse/MAVEN-1838
> Project: Maven 1.x
>  Issue Type: Sub-task
>Affects Versions: 1.1-beta-3
>Reporter: Lukas Theussl
>Assignee: Lukas Theussl
> Fix For: 1.1-rc1
>
>
> http://jira.codehaus.org/browse/MPPMD?report=com.atlassian.jira.plugin.system.project:roadmap-panel

-- 
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: (MAVEN-1828) Upgrade maven-scm-plugin to v 1.6.1

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MAVEN-1828.
--

Resolution: Fixed

Released on Mar 29th

> Upgrade maven-scm-plugin to v 1.6.1
> ---
>
> Key: MAVEN-1828
> URL: http://jira.codehaus.org/browse/MAVEN-1828
> Project: Maven 1.x
>  Issue Type: Sub-task
>Affects Versions: 1.1-beta-3
>Reporter: Lukas Theussl
>Assignee: Lukas Theussl
> Fix For: 1.1-rc1
>
>
> http://jira.codehaus.org/browse/MPSCM?report=com.atlassian.jira.plugin.system.project:roadmap-panel

-- 
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: (MAVEN-1829) Upgrade maven-site-plugin to v 1.7.1

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MAVEN-1829.
--

Resolution: Fixed

Released on Mar 29th

> Upgrade maven-site-plugin to v 1.7.1
> 
>
> Key: MAVEN-1829
> URL: http://jira.codehaus.org/browse/MAVEN-1829
> Project: Maven 1.x
>  Issue Type: Sub-task
>Affects Versions: 1.1-beta-3
>Reporter: Lukas Theussl
>Assignee: Lukas Theussl
> Fix For: 1.1-rc1
>
>
> http://jira.codehaus.org/browse/MPSITE?report=com.atlassian.jira.plugin.system.project:roadmap-panel

-- 
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: (MAVEN-1777) Upgrade maven-artifact-plugin to v 1.9

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVEN-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MAVEN-1777:
---

Summary: Upgrade maven-artifact-plugin to v 1.9  (was: Upgrade 
maven-artifact-plugin to v 1.8.1)

> Upgrade maven-artifact-plugin to v 1.9
> --
>
> Key: MAVEN-1777
> URL: http://jira.codehaus.org/browse/MAVEN-1777
> Project: Maven 1.x
>  Issue Type: Sub-task
>  Components: planning
>Affects Versions: 1.1-beta-3
>Reporter: Arnaud Heritier
> Fix For: 1.1-rc1
>
>
> http://jira.codehaus.org/browse/MPARTIFACT?report=com.atlassian.jira.plugin.system.project:roadmap-panel

-- 
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: (MPARTIFACT-75) Allow to sign artifacts to deploy

[Arnaud Heritier (JIRA)]

Allow to sign artifacts to deploy
-

 Key: MPARTIFACT-75
 URL: http://jira.codehaus.org/browse/MPARTIFACT-75
 Project: maven-artifact-plugin
  Issue Type: New Feature
Affects Versions: 1.8
Reporter: Arnaud Heritier
Assignee: Arnaud Heritier
Priority: Critical
 Fix For: 1.9


It's important for us to ease the release of 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: (MPARTIFACT-61) scpexe is a noop

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPARTIFACT-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MPARTIFACT-61.
-

  Assignee: Arnaud Heritier
Resolution: Won't Fix

It will not be fixed for maven 1.0.x. Sorry.

> scpexe is a noop
> 
>
> Key: MPARTIFACT-61
> URL: http://jira.codehaus.org/browse/MPARTIFACT-61
> Project: maven-artifact-plugin
>  Issue Type: Bug
>Affects Versions: 1.5.2
> Environment: Windows / Cygwin / Maven 1.0.2 / JDK 1.4.2
>Reporter: Joerg Schaible
>Assignee: Arnaud Heritier
>Priority: Blocker
>
> Unfortunatel scpexe protocoll seems a noop in version 1.5.2. The executable 
> is not called, but Maven is reporting happily that it has deployed:
> jar:deploy:
> [echo] Deploying...
> Using userBuildPropertiesFile: C:\Dokumente und 
> Einstellungen\jos\build.properties
> Using projectPropertiesFile: C:\Work\Projects\commons\lang\project.properties
> Using projectBuildPropertiesFile: 
> C:\Work\Projects\commons\lang\build.properties
> Will deploy to 1 repository(ies): elsag
> Deploying to repository: elsag
> Uploading to elsag-commons/poms/elsag-lang-1.2-SNAPSHOT.pom: 
>  (7K)
> Uploading to elsag-commons/poms/elsag-lang-snapshot-version: 
>  (0K)
> Uploading to elsag-commons/poms/elsag-lang-1.2-20051011.091919.pom: 
>  (7K)
> Will deploy to 1 repository(ies): elsag
> Deploying to repository: elsag
> Uploading to elsag-commons/jars/elsag-lang-1.2-SNAPSHOT.jar: 
>  (64K)
> Uploading to elsag-commons/jars/elsag-lang-snapshot-version: 
>  (0K)
> Uploading to elsag-commons/jars/elsag-lang-1.2-20051011.091940.jar: 
>  (64K)
> attaining goal build:end
> I can even remove any scp.exe and ssh.exe or set maven.repo.X.scp.executable 
> to any not existing file, the output of Maven is the same. Setting the 
> scp.executable property to a batch file that writes something into a file 
> proves, that the "executable" is definately not called. All this works with 
> 1.4.1 though delivered with the M102 installation, the artifacts are really 
> delpoyed.
> This is a real blocker for me, since I am stuck to 1.0.2 because of extensive 
> entitiy usage and I wanted to use 1.5.2 to write self-contained POMs into the 
> repository to prepare a M2 transition at a later time.
> Note, that the scp protocol does not work either for me, I always get despite 
> any settings for private key and passphrase:
> Root cause
> org.apache.maven.MavenException: Unable to deploy to any repositories
> at 
> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy(DefaultArtifactDeployer.java:338)
> at 
> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleDeploy(DefaultArtifactDeployer.java:131)
> at 
> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:102)
> at 
> org.apache.maven.artifact.deployer.DeployBean.deploy(DeployBean.java:142)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at 
> org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:230)
> at 
> org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:145)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
> at org.apache.commons.jelly.impl.DynamicTag.doTag(DynamicTag.java:125)
> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
> at 
> org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79)
> at 
> org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110)
> at com.werken.werkz.Goal.fire(Goal.java:639)
> at com.werken.werkz.Goal.attain(Goal.java:575)
> at 
> org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:671)
> at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263)
> at org.apache.maven.cli.App.doMain(App.java:488)
> at org.apache.maven.cli.App.main(App.java:1239)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at com.werken.for

[jira] Created: (MPA-87) Create a Jira Project for Modello plugin for maven 1.X

[Arnaud Heritier (JIRA)]

Create a Jira Project for Modello plugin for maven 1.X
--

 Key: MPA-87
 URL: http://jira.codehaus.org/browse/MPA-87
 Project: Maven Project Administration
  Issue Type: Task
  Components: Issue Management
Affects Versions: 2007-q1
Reporter: Arnaud Heritier
Assignee: Jason van Zyl


Project: maven-modello-plugin
Key: MPMODELLO
URL: http://maven.apache.org/maven-1.x/plugins/modello/
Project Lead: Arnaud Heritier
Notification Scheme: Maven
Permission Scheme: maven
Project Category: Maven 1 Plugins

-- 
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: (MPIR-59) Site generation exception for french language, error with simple quote in translation "S'inscrire" for mailing list

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPIR-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MPIR-59.
---

 Assignee: Arnaud Heritier
   Resolution: Fixed
Fix Version/s: 2.1

Patch applied. Snapshot deployed (2.1-20070401.230737-6).
I replaced all ' characters by \u0092.

> Site generation exception for french language, error with simple quote in  
> translation "S'inscrire" for mailing list
> 
>
> Key: MPIR-59
> URL: http://jira.codehaus.org/browse/MPIR-59
> Project: Maven 2.x Project Info Reports Plugin
>  Issue Type: Bug
>Affects Versions: 2.0.1
> Environment: linux Debian sarge
> jdk 1.6
> maven 2.0.4
>Reporter: Benjamin POUSSIN
> Assigned To: Arnaud Heritier
>Priority: Blocker
> Fix For: 2.1
>
> Attachments: MPIR-french-translation.patch
>
>
> When we try to generate site in french  fr in site plugin 
> we have exception:
> [ERROR] FATAL ERROR
> [INFO] 
> 
> [INFO] Unmatched braces in the pattern in '{S'incrire, 
> http://lists.labs.libre-entreprise.org/mailman/listinfo/lutinutil-cvscommit}'
> [INFO] 
> 
> [INFO] Trace
> java.lang.IllegalArgumentException: Unmatched braces in the pattern.
> at 
> org.apache.maven.reporting.AbstractMavenReportRenderer.applyPattern(AbstractMavenReportRenderer.java:619)
> at 
> org.apache.maven.reporting.AbstractMavenReportRenderer.linkPatternedText(AbstractMavenReportRenderer.java:353)
> at 
> org.apache.maven.reporting.AbstractMavenReportRenderer.tableCell(AbstractMavenReportRenderer.java:213)
> at 
> org.apache.maven.reporting.AbstractMavenReportRenderer.tableCell(AbstractMavenReportRenderer.java:193)
> at 
> org.apache.maven.reporting.AbstractMavenReportRenderer.tableRow(AbstractMavenReportRenderer.java:225)
> at 
> org.apache.maven.report.projectinfo.MailingListsReport$MailingListsRenderer.renderBody(MailingListsReport.java:238)
> at 
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65)
> at 
> org.apache.maven.report.projectinfo.MailingListsReport.executeReport(MailingListsReport.java:65)
> at 
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101)
> ...
> in applyPattern some test is done to know if simple quote \' are opened but 
> this test is not good for some translation as: 
> report.mailing-lists.column.subscribe = S'incrire
> because this become:
> {S'incrire, 
> http://lists.labs.libre-entreprise.org/mailman/listinfo/lutinutil-cvscommit}
> and applyPattern method think that quote is nether close.
> quick fix is to put two simple quote: S''incrire
> but this render two simple quote in html page.
> I think applyPattern must be rewritten to correct this problem

-- 
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-1230) org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest fails with cygwin

[Arnaud Heritier (JIRA)]

org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest fails with 
cygwin
--

 Key: CONTINUUM-1230
 URL: http://jira.codehaus.org/browse/CONTINUUM-1230
 Project: Continuum
  Issue Type: Bug
  Components: Release
Affects Versions: 1.1-alpha-1
 Environment: Windows XP
Reporter: Arnaud Heritier


Have a look at the path in svn commands 

{code}
[ERROR] org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable 
to commit files
Provider message:
The svn command failed.
Command output:
svn: 
'/cygdrive/e/OSS/m2-trunks/continuum/continuum-release/target/test-classes/work-dir/e:/OSS/m2-trunks/continuum/continuum-release/target/test-classes/work-dir'
 is not a working copy
svn: Can't open file 
'/cygdrive/e/OSS/m2-trunks/continuum/continuum-release/target/test-classes/work-dir/e:/OSS/m2-trunks/continuum/continuum-release/target/test-classes/work-dir/.svn/entries':
 No such file or directory

at 
org.apache.maven.shared.release.phase.ScmCommitPhase.execute(ScmCommitPhase.java:105)
at 
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:205)
at 
org.apache.maven.shared.release.DefaultReleaseManager.prepareWithResult(DefaultReleaseManager.java:118)
at 
org.apache.maven.continuum.release.executors.PrepareReleaseTaskExecutor.execute(PrepareReleaseTaskExecutor.java:43)
at 
org.apache.maven.continuum.release.executors.AbstractReleaseTaskExecutor.executeTask(AbstractReleaseTaskExecutor.java:67)
at 
org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest.doPrepareWithNoError(ReleaseTaskExecutorTest.java:224)
at 
org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest.releaseSimpleProject(ReleaseTaskExecutorTest.java:112)
at 
org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest.testReleases(ReleaseTaskExecutorTest.java:128)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at 
org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at 
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290)
at 
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818)


at junit.framework.Assert.fail(Assert.java:47)
at 
org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest.doPrepareWithNoError(ReleaseTaskExecutorTest.java:229)
at 
org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest.releaseSimpleProject(ReleaseTaskExecutorTest.java:112)
at 
org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest.testReleases(ReleaseTaskExecutorTest.java:128)
at 
org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest.testReleases(ReleaseTaskExecutorTest.java:128)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.

[jira] Created: (CONTINUUM-1229) com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Invalid default value for 'SCM_USE_CACHE'

[Arnaud Heritier (JIRA)]

com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Invalid default value for 
'SCM_USE_CACHE'
--

 Key: CONTINUUM-1229
 URL: http://jira.codehaus.org/browse/CONTINUUM-1229
 Project: Continuum
  Issue Type: Bug
  Components: Database
Affects Versions: 1.1-alpha-1
 Environment: Windows XP / JDK 1.5.0_10-b03 / Tomcat 5.5.20 / MySQL 
5.0.27
Reporter: Arnaud Heritier
 Attachments: stdout_20070328.log

The change in the model (r507778) creates the error described in the subject 
and in the attached logs if I use continuum with MySQL.
If I remove jpox.nullValue="default" for the field scmUseCache, the tests in 
the core fail.

-- 
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-2319) strange issue when trying to generate a site which uses the multi project and assembly stuff

[Arnaud Heritier (JIRA)]

[ 
http://jira.codehaus.org/browse/MNG-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91205
 ] 

Arnaud Heritier commented on MNG-2319:
--

I reproduced it with maven 2.0.5
For example in plexus you can launch : mvn clean eclipse:eclipse idea:idea 
install
But if you launch each phase/goal separately, the problem doesn't occur.
You can reproduce it in others projects like archiva, continuum, ...

> strange issue when trying to generate a site which uses the multi project and 
> assembly stuff
> 
>
> Key: MNG-2319
> URL: http://jira.codehaus.org/browse/MNG-2319
> Project: Maven 2
>  Issue Type: Bug
>  Components: Artifacts and Repositories
>Affects Versions: 2.0.4
>Reporter: james strachan
> Fix For: 2.1.x
>
>
> Grab a checkout of ActiveMQ and try
> mvn clean install site:site -Dmaven.test.skip=true  
> And you get this - which seems to be related to maven's insistence on 
> rebuilding everything again when it tries to build the 'assembly' module.
> [INFO] Preparing assembly:assembly
> [INFO] 
> 
> [INFO] Building ActiveMQ
> [INFO] 
> 
> [INFO] Skipping missing optional mojo: 
> org.apache.maven.plugins:maven-site-plugin:attach-descriptor
> [INFO] No goals needed for project - skipping
> [INFO] 
> 
> [INFO] Building ActiveMQ :: JAAS
> [INFO] 
> 
> [INFO] 
> 
> [ERROR] FATAL ERROR
> [INFO] 
> 
> [INFO] null
> [INFO] 
> 
> [INFO] Trace
> java.lang.NullPointerException
> at 
> org.apache.maven.artifact.ArtifactUtils.copyArtifact(ArtifactUtils.java:109)
> at org.apache.maven.project.MavenProject.(MavenProject.java:251)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:886)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:729)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:505)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO] -
> If you try just to make the site via
> mvn clean  site:site -Dmaven.test.skip=true  
> then you get...
> [INFO] 
> 
> [INFO] Building ActiveMQ :: Assembly
> [INFO]task-segment: [clean, site:site]
> [INFO] 
> 
> [INFO] snapshot incubator-activemq:maven-bundle-plugin:4.0-SNAPSHOT: checking 
> for updates from codehaus.snapshots
> [INFO] snapshot incubator-activemq:maven-bundle-plugin:4.0-SNAPSHOT: checking 
> for updates from maven-csharp-plugins
> [WARNING] *** CHECKSUM FAILED - Invalid checksum file - RETRYING
> [WARNING] *** CHECKSUM FAILED - Invalid checksum file - IGNORING
> 

[jira] Closed: (MPLINKCHECK-27) The report is incomplete if one or more files has errors in them

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MPLINKCHECK-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MPLINKCHECK-27.
--

Resolution: Fixed

File parsed to check if it is valid

> The report is incomplete if one or more files has errors in them
> 
>
> Key: MPLINKCHECK-27
> URL: http://jira.codehaus.org/browse/MPLINKCHECK-27
> Project: maven-linkcheck-plugin
>  Issue Type: Bug
>Affects Versions: 1.4
> Environment: Maven 1.0.2, Windows XP
>Reporter: Dennis Lundberg
> Assigned To: Arnaud Heritier
> Fix For: 1.4.1
>
> Attachments: MPLINKCHECK-27-testcase.zip, MPLINKCHECK-27.patch
>
>
> If you run linkcheck on a project and there is more than zero files with 
> errors, then the resulting report is incomplete. The table that shows which 
> files have errors and warnings is not shown. The reason for this is a bug in 
> linkcheck.jsl and the jelly syntax. Testcase and patch coming soon.
> This link was helpful in finding the reason for the failure:
> http://mail-archives.apache.org/mod_mbox/maven-users/200506.mbox/[EMAIL 
> PROTECTED]
> Here's the stack trace I get:
> Links checked.
> Caught exception evaluating: [EMAIL PROTECTED] Reason: java.lang.Exception: 
> Invalid comparison : GT
> java.lang.Exception: Invalid comparison : GT
> at org.apache.commons.jexl.parser.ASTGTNode.value(ASTGTNode.java:104)
> at 
> org.apache.commons.jexl.parser.ASTExpression.value(ASTExpression.java:85)
> at 
> org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:123)
> at 
> org.apache.commons.jelly.expression.jexl.JexlExpression.evaluate(JexlExpression.java:115)
> at 
> org.apache.commons.jelly.expression.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:106)
> at 
> org.apache.commons.jelly.expression.ExpressionSupport.evaluateAsBoolean(ExpressionSupport.java:116)
> at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:87)
> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
> at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
> at org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:111)
> at 
> org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:145)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
> at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
> at org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:111)
> at 
> org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:145)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
> at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
> at org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:111)
> at 
> org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:145)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
> at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
> at 
> org.apache.commons.jelly.tags.jsl.TemplateTag$1.run(TemplateTag.java:160)
> at org.dom4j.rule.Mode.fireRule(Mode.java:51)
> at org.dom4j.rule.Mode.applyTemplates(Mode.java:71)
> at org.dom4j.rule.RuleManager$1.run(RuleManager.java:148)
> at org.dom4j.rule.Mode.fireRule(Mode.java:51)
> at org.dom4j.rule.Stylesheet.run(Stylesheet.java:73)
> at org.dom4j.rule.Stylesheet.run(Stylesheet.java:65)
> at org.dom4j.rule.Stylesheet.run(Stylesheet.java:57)
> at 
> org.apache.commons.jelly.tags.jsl.StylesheetTag.doTag(StylesheetTag.java:124)
> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
> at 
> org.apache.commons.jelly.JellyContext.runScript(JellyContext.java:634)
> at 
> org.apache.commons.jelly.JellyContext.runScript(JellyContext.java:584)
> at 
> org.apache.commons.jelly.tags.core.IncludeTag.doTag(IncludeTag.java:143)
> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
> at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
> at 
> org.apache.commons.jelly.tags.core.FileTag.writeBody(FileTag.java:207)
> at org.apache.commons.jelly.tags.core.FileTag.doTag(FileTag.java:103)
> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
> at org.apache.commons.jelly.impl.DynamicTag.doTag(DynamicTag.ja

[jira] Commented: (MNG-2664) Add native support for webdav

[Arnaud Heritier (JIRA)]

[ 
http://jira.codehaus.org/browse/MNG-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91011
 ] 

Arnaud Heritier commented on MNG-2664:
--

It's what I'm doing for now. Thanks for this explanation in the documentation. 
I didn't see it some weeks ago.

> Add native support for webdav
> -
>
> Key: MNG-2664
> URL: http://jira.codehaus.org/browse/MNG-2664
> Project: Maven 2
>  Issue Type: New Feature
>  Components: Artifacts and Repositories
>Affects Versions: 2.0.4
>Reporter: Arnaud Heritier
> Fix For: 2.1.x
>
> Attachments: MNG-2664.patch
>
>
> Actually with maven 2.0.4 we can't use the deploy:deploy-file goal to add an 
> artifact on a remote repository with webdav.
> This is really annoying for archiva which supports webdav for uploads.

-- 
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-307) CSS declarations don't support Reverse-proxy

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MRM-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MRM-307.
---

   Resolution: Fixed
Fix Version/s: 1.0

I just replaced them by this syntax :
  " 
type="text/css" media="all"/>
  " 
type="text/css" media="all"/>
  " 
type="text/css" media="all"/>
  " type="text/css" 
media="all"/>


> CSS declarations don't support Reverse-proxy
> 
>
> Key: MRM-307
> URL: http://jira.codehaus.org/browse/MRM-307
> Project: Archiva
>  Issue Type: Improvement
>  Components: web application
>Affects Versions: 1.0
>Reporter: Arnaud Heritier
> Assigned To: Arnaud Heritier
> Fix For: 1.0
>
>
> I'm using a reverse proxy to see archiva like http://repositories.myserver 
> instead of http://myserver:8080/archiva
> Actually to load CSS we have the following syntax :
>   
> @import url( "" );
> @import url( "" );
> @import url( "" );
> @import url( "" );
>   
> But these urls aren't rewritten (because it's not in a href)

-- 
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-307) CSS declarations don't support Reverse-proxy

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MRM-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MRM-307:


Summary: CSS declarations don't support Reverse-proxy  (was: CSS 
declarations doesn't support Reverse-proxy)

> CSS declarations don't support Reverse-proxy
> 
>
> Key: MRM-307
> URL: http://jira.codehaus.org/browse/MRM-307
> Project: Archiva
>  Issue Type: Improvement
>  Components: web application
>Affects Versions: 1.0
>Reporter: Arnaud Heritier
> Fix For: 1.0
>
>
> I'm using a reverse proxy to see archiva like http://repositories.myserver 
> instead of http://myserver:8080/archiva
> Actually to load CSS we have the following syntax :
>   
> @import url( "" );
> @import url( "" );
> @import url( "" );
> @import url( "" );
>   
> But these urls aren't rewritten (because it's not in a href)

-- 
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-307) CSS declarations doesn't support Reverse-proxy

[Arnaud Heritier (JIRA)]

CSS declarations doesn't support Reverse-proxy
--

 Key: MRM-307
 URL: http://jira.codehaus.org/browse/MRM-307
 Project: Archiva
  Issue Type: Improvement
  Components: web application
Affects Versions: 1.0
Reporter: Arnaud Heritier


I'm using a reverse proxy to see archiva like http://repositories.myserver 
instead of http://myserver:8080/archiva

Actually to load CSS we have the following syntax :
  
@import url( "" );
@import url( "" );
@import url( "" );
@import url( "" );
  

But these urls aren't rewritten (because it's not in a href)

-- 
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-306) The default Cron expression is invalid

[Arnaud Heritier (JIRA)]

The default Cron expression is invalid
--

 Key: MRM-306
 URL: http://jira.codehaus.org/browse/MRM-306
 Project: Archiva
  Issue Type: Bug
  Components: scheduling, web application
Affects Versions: 1.0
Reporter: Arnaud Heritier


The default cron expression is invalid when when you setup archiva. You have to 
add the * in the year field.

-- 
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-288) Error on startup: NPE, configuration can not be null

[Arnaud Heritier (JIRA)]

[ 
http://jira.codehaus.org/browse/MRM-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90622
 ] 

Arnaud Heritier commented on MRM-288:
-

To fix it we also have to create an archiva.xml file with the content :  
.

> Error on startup: NPE, configuration can not be null
> 
>
> Key: MRM-288
> URL: http://jira.codehaus.org/browse/MRM-288
> Project: Archiva
>  Issue Type: Bug
> Environment: r510897
>Reporter: Lester Ecarma
> Assigned To: Brett Porter
> Fix For: 1.0
>
>
> 2007-02-23 18:11:34.480::WARN:  Failed startup of context [EMAIL 
> PROTECTED]/,/home/lecarma/workspace/mergere/OSS/apache/archiva/trunk/archiva-webapp/src/main/webapp}
> java.lang.NullPointerException: configuration can not be null
> at 
> org.codehaus.plexus.registry.commons.CommonsConfigurationRegistry.(CommonsConfigurationRegistry.java:89)
> at 
> org.codehaus.plexus.registry.commons.CommonsConfigurationRegistry.getSection(CommonsConfigurationRegistry.java:422)
> at 
> org.apache.maven.archiva.configuration.DefaultArchivaConfiguration.addChangeListener(DefaultArchivaConfiguration.java:86)
> at 
> org.apache.maven.archiva.scheduler.DefaultRepositoryTaskScheduler.start(DefaultRepositoryTaskScheduler.java:91)
> at 
> org.codehaus.plexus.personality.plexus.lifecycle.phase.StartPhase.execute(StartPhase.java:33)
> at 
> org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:130)
> at 
> org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:143)
> at 
> org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:133)
> at 
> org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:87)
> at 
> org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:101)
> at 
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:313)
> at 
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:291)
> at 
> org.codehaus.plexus.container.initialization.StartLoadOnStartComponentsPhase.execute(StartLoadOnStartComponentsPhase.java:54)
> at 
> org.codehaus.plexus.DefaultPlexusContainer.initializePhases(DefaultPlexusContainer.java:928)
> at 
> org.codehaus.plexus.DefaultPlexusContainer.initialize(DefaultPlexusContainer.java:876)
> at 
> org.codehaus.plexus.DefaultPlexusContainer.construct(DefaultPlexusContainer.java:853)
> at 
> org.codehaus.plexus.DefaultPlexusContainer.(DefaultPlexusContainer.java:222)
> at 
> org.codehaus.plexus.DefaultPlexusContainer.(DefaultPlexusContainer.java:236)
> at 
> org.codehaus.plexus.xwork.PlexusLifecycleListener.contextInitialized(PlexusLifecycleListener.java:76)
> at 
> org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:511)
> at org.mortbay.jetty.servlet.Context.startContext(Context.java:135)
> at 
> org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1191)
> at 
> org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:481)
> at 
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:434)
> at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
> at 
> org.mortbay.jetty.plugin.Jetty6PluginWebApplication.start(Jetty6PluginWebApplication.java:147)
> at 
> org.mortbay.jetty.plugin.AbstractJettyRunMojo$1.changesDetected(AbstractJettyRunMojo.java:372)
> at org.mortbay.jetty.plugin.util.Scanner.run(Scanner.java:159)
> This causes a 404

-- 
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-216) Upload (deploy) artifacts to a repository

[Arnaud Heritier (JIRA)]

[ 
http://jira.codehaus.org/browse/MRM-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90551
 ] 

Arnaud Heritier commented on MRM-216:
-

It's not sufficient because to use the webdav with maven 2.0.X we have to be in 
a directory where maven 2 can find a pom with the webdav extension. It's really 
annoying for our users who are trying by default to do it from where the jar 
is. I agree with the need of the bundle but we can certainly begin with 
something really simple :
- pom
- pom + artifact
- artifactId + groupId + version + type + artifact
With this 3 cases with certainly cover the majority of the needs.

> Upload (deploy) artifacts to a repository
> -
>
> Key: MRM-216
> URL: http://jira.codehaus.org/browse/MRM-216
> Project: Archiva
>  Issue Type: New Feature
>  Components: web application
>Reporter: Oliver Fink
> Assigned To: John Tolentino
> Fix For: Future
>
>
> The web interface should allow to upload artifacts to the repository. For M1 
> one could just ftp the artifacts as neededm but with M2 having to go through 
> the file:deploy plugin is a pain. Archiva could help a lot here

-- 
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] Reopened: (MRM-288) Error on startup: NPE, configuration can not be null

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MRM-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier reopened MRM-288:
-


I have a similar error with a version built today. When I save the 
configuration for the initial setup I receive a NPE :
java.lang.NullPointerException
at 
org.apache.maven.archiva.configuration.io.registry.ConfigurationRegistryWriter.writeConfiguration(ConfigurationRegistryWriter.java:36)
at 
org.apache.maven.archiva.configuration.io.registry.ConfigurationRegistryWriter.write(ConfigurationRegistryWriter.java:26)
at 
org.apache.maven.archiva.configuration.DefaultArchivaConfiguration.save(DefaultArchivaConfiguration.java:86)
at 
org.apache.maven.archiva.web.action.admin.AbstractConfigureRepositoryAction.saveConfiguration(AbstractConfigureRepositoryAction.java:110)
at 
org.apache.maven.archiva.web.action.admin.AbstractConfigureRepositoryAction.add(AbstractConfigureRepositoryAction.java:87)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at 
com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:364)
at 
com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:216)
at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at 
org.codehaus.plexus.security.ui.web.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.java:155)
at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
at 
org.codehaus.plexus.security.ui.web.interceptor.PolicyEnforcementInterceptor.intercept(PolicyEnforcementInterceptor.java:102)
at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
at 
org.codehaus.plexus.security.ui.web.interceptor.AutoLoginInterceptor.intercept(AutoLoginInterceptor.java:152)
at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
at 
org.codehaus.plexus.security.ui.web.interceptor.ForceAdminUserInterceptor.intercept(ForceAdminUserInterceptor.java:62)
at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
at 
org.codehaus.plexus.security.ui.web.interceptor.EnvironmentCheckInterceptor.intercept(EnvironmentCheckInterceptor.java:121)
at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
at 
com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:168)
at 
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
at 
com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
at 
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
at 
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
at 
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
at 
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
at 
com.opensymphony.webwork.interceptor.FileUploadInterceptor.intercept(FileUploadInterceptor.java:171)
at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
at 
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
at 
com.opensymphony.webwork.interceptor.debugging.DebuggingInterceptor.intercept(DebuggingInterceptor.java:147)
at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
at 
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188)
at 
com.opensymphony.xwork.interceptor.I18nInterceptor.intercept(I

[jira] Commented: (MECLIPSE-107) Dependency Version Incorrectly Taken from DependencyManagement

[Arnaud Heritier (JIRA)]

[ 
http://jira.codehaus.org/browse/MECLIPSE-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90253
 ] 

Arnaud Heritier commented on MECLIPSE-107:
--

ok, thanks for your feedback. I'll add your test case in our tests and I'll fix 
it this WE.

> Dependency Version Incorrectly Taken from DependencyManagement
> --
>
> Key: MECLIPSE-107
> URL: http://jira.codehaus.org/browse/MECLIPSE-107
> Project: Maven 2.x Eclipse Plugin
>  Issue Type: Bug
>  Components: dependency resolution
>Affects Versions: 2.2
>Reporter: Stephen Duncan Jr
>Priority: Critical
> Attachments: dmtest.zip, 
> MECLIPSE-107-maven-eclipse-plugin-20061211-1200.patch
>
>
> The version used when generating .classpath is taken from 
> dependencyManagement even though the child pom sets the dependency version, 
> which should override what is in dependencyManagement.  This is a regression 
> from the correct behaviour in 2.1.
> The attached project demonstrates the problem.  The .classpath file generated 
> for the "child" project should specify log4j-1.2.13, but instead specifies 
> 1.28.

-- 
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: (MECLIPSE-107) Dependency Version Incorrectly Taken from DependencyManagement

[Arnaud Heritier (JIRA)]

[ 
http://jira.codehaus.org/browse/MECLIPSE-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90215
 ] 

Arnaud Heritier commented on MECLIPSE-107:
--

The snapshot I just deployed should have fixed this bug. Can you verify please ?

> Dependency Version Incorrectly Taken from DependencyManagement
> --
>
> Key: MECLIPSE-107
> URL: http://jira.codehaus.org/browse/MECLIPSE-107
> Project: Maven 2.x Eclipse Plugin
>  Issue Type: Bug
>  Components: dependency resolution
>Affects Versions: 2.2
>Reporter: Stephen Duncan Jr
>Priority: Critical
> Attachments: dmtest.zip, 
> MECLIPSE-107-maven-eclipse-plugin-20061211-1200.patch
>
>
> The version used when generating .classpath is taken from 
> dependencyManagement even though the child pom sets the dependency version, 
> which should override what is in dependencyManagement.  This is a regression 
> from the correct behaviour in 2.1.
> The attached project demonstrates the problem.  The .classpath file generated 
> for the "child" project should specify log4j-1.2.13, but instead specifies 
> 1.28.

-- 
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: (MECLIPSE-243) The last 2.4 SNAPSHOT forbid Apache Directory Server to be built

[Arnaud Heritier (JIRA)]

[ 
http://jira.codehaus.org/browse/MECLIPSE-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90214
 ] 

Arnaud Heritier commented on MECLIPSE-243:
--

I had the same error yesterday.
It's a problem with the build of this plugin. We use this test version, in 
theory, only for our tests
But it's not the case actually.
It should be fixed actually. I redeployed it (and I skip tests)

> The last 2.4 SNAPSHOT forbid Apache Directory Server to be built
> 
>
> Key: MECLIPSE-243
> URL: http://jira.codehaus.org/browse/MECLIPSE-243
> Project: Maven 2.x Eclipse Plugin
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Emmanuel Lécharny
>Priority: Blocker
> Fix For: 2.4
>
>
> We can't anymore build ADS since a new version (SNAPSHOT-2.4) has been pushed 
> on the http://people.apache.org/repo/m2-snapshot-repository repo. 
> If I switch the version to 2.3 by declaring it in the PluginManagement, 
> everything is fine. I'm using Maven 2.0.5
> Here is the log :
> [EMAIL PROTECTED] apacheds-trunks]$ mvn -X eclipse:eclipse
> + Error stacktraces are turned on.
> Maven version: 2.0.5
> [DEBUG] Building Maven user-level plugin registry from: 
> '/home/elecharny/.m2/plugin-registry.xml'
> [DEBUG] Building Maven global-level plugin registry from: 
> '/opt/maven-2.0.5/conf/plugin-registry.xml'
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO]   Apache Directory Build
> [INFO]   Apache Directory Shared
> [INFO]   Apache Directory ASN.1 Shared
> [INFO]   Apache Directory Protocol Ldap Shared
> [INFO]   ApacheDS
> [INFO]   ApacheDS Constants
> [INFO]   ApacheDS Core Shared
> [INFO]   ApacheDS Schema Registries
> [INFO]   ApacheDS BTree Base
> [INFO]   ApacheDS JDBM Store
> [INFO]   ApacheDS Utils
> [INFO]   ApacheDS Core Plugin (Maven 2)
> [INFO]   ApacheDS Bootstrap Schemas
> [INFO]   ApacheDS Extra Schemas
> [INFO]   ApacheDS Bootstrap Plugin
> [INFO]   ApacheDS Bootstrap Partition
> [INFO]   ApacheDS Core
> [INFO]   ApacheDS Core Unit
> [INFO]   ApacheDS Protocol Shared
> [INFO]   ApacheDS Protocol Ntp
> [INFO]   Apache Directory MINA ASN.1 Codec Shared
> [INFO]   ApacheDS Protocol Ldap
> [INFO]   ApacheDS Protocol Kerberos Shared
> [INFO]   ApacheDS Protocol Kerberos
> [INFO]   ApacheDS Protocol Dhcp
> [INFO]   ApacheDS Protocol Dns
> [INFO]   ApacheDS Protocol Change Password
> [INFO]   ApacheDS Server JNDI
> [INFO]   ApacheDS Server Unit
> [INFO]   ApacheDS Server SSL
> [INFO]   Apache Directory Daemon
> [INFO]   Apache Directory Daemon Bootstrappers
> [INFO]   ApacheDS Server Main
> [INFO]   ApacheDS Server Tools
> [INFO]   ApacheDS replication
> [INFO]   ApacheDS Server Replication Service
> [INFO]   Apache Directory Protocol Ldap Converters
> [INFO]   Apache Directory Daemon Plugin (Maven 2)
> [INFO] Searching repository for plugin with prefix: 'eclipse'.
> [DEBUG] maven-eclipse-plugin: resolved to version 2.4-SNAPSHOT from 
> repository central
> [DEBUG] Skipping disabled repository central
> [DEBUG] maven-eclipse-plugin: resolved to version 2.4-20070315.175923-5 from 
> repository apache.snapshots
> [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::8 for 
> project: 
> org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:2.4-SNAPSHOT from 
> the repository.
> [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::5 for project: 
> org.apache.maven.plugins:maven-plugins:pom:8 from the repository.
> [DEBUG] Retrieving parent-POM: org.apache:apache::3 for project: 
> org.apache.maven:maven-parent:pom:5 from the repository.
> [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::8 for 
> project: 
> org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:2.4-SNAPSHOT from 
> the repository.
> [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::5 for project: 
> org.apache.maven.plugins:maven-plugins:pom:8 from the repository.
> [DEBUG] Retrieving parent-POM: org.apache:apache::3 for project: 
> org.apache.maven:maven-parent:pom:5 from the repository.
> [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::8 for 
> project: 
> org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:2.4-SNAPSHOT from 
> the repository.
> [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::5 for project: 
> org.apache.maven.plugins:maven-plugins:pom:8 from the repository.
> [DEBUG] Retrieving parent-POM: org.apache:apache::3 for project: 
> org.apache.maven:maven-parent:pom:5 from the repository.
> [INFO] 
> 
> [INFO] Building Apache Directory Build
> [INFO]task-segment: [eclipse:eclipse]
> [INFO] 
> 
> [INFO] Preparing eclipse:eclipse
> [DEBUG] Sk

[jira] Closed: (MECLIPSE-215) WTP 1.5 Documentation

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MECLIPSE-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MECLIPSE-215.


   Resolution: Fixed
Fix Version/s: 2.4

Fixed. Will be updated in the next site deployment

> WTP 1.5 Documentation
> -
>
> Key: MECLIPSE-215
> URL: http://jira.codehaus.org/browse/MECLIPSE-215
> Project: Maven 2.x Eclipse Plugin
>  Issue Type: Bug
>  Components: WTP support
>Affects Versions: 2.3
>Reporter: Shelley L
> Assigned To: Arnaud Heritier
>Priority: Minor
> Fix For: 2.4
>
>
> The maven-eclipse-plugin mojo documentation should be updated to mention WTP 
> 1.5 support.  Currently, the wtpversion parameter description states that the 
> only supported versions are "R7" and "1.0."
> http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html

-- 
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] Work started: (MECLIPSE-215) WTP 1.5 Documentation

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MECLIPSE-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on MECLIPSE-215 started by Arnaud Heritier.

> WTP 1.5 Documentation
> -
>
> Key: MECLIPSE-215
> URL: http://jira.codehaus.org/browse/MECLIPSE-215
> Project: Maven 2.x Eclipse Plugin
>  Issue Type: Bug
>  Components: WTP support
>Affects Versions: 2.3
>Reporter: Shelley L
> Assigned To: Arnaud Heritier
>Priority: Minor
> Fix For: 2.4
>
>
> The maven-eclipse-plugin mojo documentation should be updated to mention WTP 
> 1.5 support.  Currently, the wtpversion parameter description states that the 
> only supported versions are "R7" and "1.0."
> http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html

-- 
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: (MECLIPSE-241) Compiler settings in pluginManagement aren't used in wtp facet

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MECLIPSE-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MECLIPSE-241.


Resolution: Fixed

Fixed

> Compiler settings in pluginManagement aren't used in wtp facet
> --
>
> Key: MECLIPSE-241
> URL: http://jira.codehaus.org/browse/MECLIPSE-241
> Project: Maven 2.x Eclipse Plugin
>  Issue Type: Bug
>  Components: WTP support
>Affects Versions: 2.3
> Environment: maven 2.0.4 / maven 2.0.5
>Reporter: Arnaud Heritier
> Assigned To: Arnaud Heritier
>Priority: Minor
> Fix For: 2.4
>
> Attachments: project-28.zip
>
>
> In a parent POM I have in the pluginManagement part :
> {code:xml}
> 
>   org.apache.maven.plugins
>   maven-compiler-plugin
>   
> 1.5
> 1.5
>   
> 
> {code}
> And I have a submodule (a war) configure to generate wtp 1.5 settings :
> {code:xml}
> 
>   org.apache.maven.plugins
>   maven-eclipse-plugin
>   
> 1.5
>   
> 
> {code}
> After running eclipse:eclipse I have the following in my 
> org.eclipse.wst.common.project.facet.core.xml :
> {code:xml}
> 
>   
>   
>   
>   
> 
> {code}
> And not
> {code:xml}
> 
>   
>   
>   
>   
> 
> {code}

-- 
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: (MECLIPSE-241) Compiler settings in pluginManagement aren't used in wtp facet

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MECLIPSE-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier updated MECLIPSE-241:
-

Description: 
In a parent POM I have in the pluginManagement part :
{code:xml}

  org.apache.maven.plugins
  maven-compiler-plugin
  
1.5
1.5
  

{code}
And I have a submodule (a war) configure to generate wtp 1.5 settings :
{code:xml}

  org.apache.maven.plugins
  maven-eclipse-plugin
  
1.5
  

{code}
After running eclipse:eclipse I have the following in my 
org.eclipse.wst.common.project.facet.core.xml :
{code:xml}

  
  
  
  

{code}
And not
{code:xml}

  
  
  
  

{code}

  was:
In a parent POM I have :
{code:xml}

  org.apache.maven.plugins
  maven-compiler-plugin
  
1.5
1.5
  

{code}
And I have a submodule (a war) configure to generate wtp 1.5 settings :
{code:xml}

  org.apache.maven.plugins
  maven-eclipse-plugin
  
1.5
  

{code}
After running eclipse:eclipse I have the following in my 
org.eclipse.wst.common.project.facet.core.xml :
{code:xml}

  
  
  
  

{code}
And not
{code:xml}

  
  
  
  

{code}

Summary: Compiler settings in pluginManagement aren't used in wtp facet 
 (was: Compiler settings from parent project aren't used in wtp facet)

> Compiler settings in pluginManagement aren't used in wtp facet
> --
>
> Key: MECLIPSE-241
> URL: http://jira.codehaus.org/browse/MECLIPSE-241
> Project: Maven 2.x Eclipse Plugin
>  Issue Type: Bug
>  Components: WTP support
>Affects Versions: 2.3
> Environment: maven 2.0.4 / maven 2.0.5
>Reporter: Arnaud Heritier
> Assigned To: Arnaud Heritier
>Priority: Minor
> Fix For: 2.4
>
> Attachments: project-28.zip
>
>
> In a parent POM I have in the pluginManagement part :
> {code:xml}
> 
>   org.apache.maven.plugins
>   maven-compiler-plugin
>   
> 1.5
> 1.5
>   
> 
> {code}
> And I have a submodule (a war) configure to generate wtp 1.5 settings :
> {code:xml}
> 
>   org.apache.maven.plugins
>   maven-eclipse-plugin
>   
> 1.5
>   
> 
> {code}
> After running eclipse:eclipse I have the following in my 
> org.eclipse.wst.common.project.facet.core.xml :
> {code:xml}
> 
>   
>   
>   
>   
> 
> {code}
> And not
> {code:xml}
> 
>   
>   
>   
>   
> 
> {code}

-- 
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] Reopened: (MECLIPSE-241) Compiler settings from parent project aren't used in wtp facet

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MECLIPSE-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier reopened MECLIPSE-241:
--


The problem is different. It's because compiler settings are defined in the 
pluginManagement par in the pom

> Compiler settings from parent project aren't used in wtp facet
> --
>
> Key: MECLIPSE-241
> URL: http://jira.codehaus.org/browse/MECLIPSE-241
> Project: Maven 2.x Eclipse Plugin
>  Issue Type: Bug
>  Components: WTP support
>Affects Versions: 2.3
> Environment: maven 2.0.4 / maven 2.0.5
>Reporter: Arnaud Heritier
> Assigned To: Arnaud Heritier
>Priority: Minor
> Fix For: 2.4
>
> Attachments: project-28.zip
>
>
> In a parent POM I have :
> {code:xml}
> 
>   org.apache.maven.plugins
>   maven-compiler-plugin
>   
> 1.5
> 1.5
>   
> 
> {code}
> And I have a submodule (a war) configure to generate wtp 1.5 settings :
> {code:xml}
> 
>   org.apache.maven.plugins
>   maven-eclipse-plugin
>   
> 1.5
>   
> 
> {code}
> After running eclipse:eclipse I have the following in my 
> org.eclipse.wst.common.project.facet.core.xml :
> {code:xml}
> 
>   
>   
>   
>   
> 
> {code}
> And not
> {code:xml}
> 
>   
>   
>   
>   
> 
> {code}

-- 
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: (MECLIPSE-220) Incorrect eclipse facet information when doing mvn eclipse:eclipse for war and ejb projects.

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MECLIPSE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MECLIPSE-220.


   Resolution: Fixed
Fix Version/s: 2.4

Patch reviewed and applied. Thx. Issue Fixed. SNAPSHOT deployed.

> Incorrect eclipse facet information when doing mvn eclipse:eclipse for war 
> and ejb projects.
> 
>
> Key: MECLIPSE-220
> URL: http://jira.codehaus.org/browse/MECLIPSE-220
> Project: Maven 2.x Eclipse Plugin
>  Issue Type: Bug
>  Components: WTP support
>Affects Versions: 2.3
> Environment: maven 2.0.4
> maven-eclipse-plugin 2.3
>Reporter: Minto van der Sluis
> Assigned To: Arnaud Heritier
> Fix For: 2.4
>
> Attachments: proper-facet.patch
>
>
> When running 'mvn eclipse:eclipse' the results do not take the proper 
> servlet-api en ejb-api into account.
> ejb version is not taken into account (see 
> http://jira.codehaus.org/browse/MECLIPSE-198)
> servlet api version is not taken into account (see 
> http://jira.codehaus.org/browse/MECLIPSE-108)
> I have fixed these problems locally, but looking at MECLIPSE-108 is wonder if 
> what I did is correct . Still my solution works for me. I wonder what the 
> difference is between config.getProject().getArtifacts() and 
> config.getProject().getDependencies() . Why in the existing implementation is 
> resolveServletVersion using getArtifacts() and resolveJ2eeVersion using 
> getDependencies() ? My solutions uses getDependencies() only and works for 
> me. 
> What I actually did is the following:
> - I switched the 2 loops in getDependencyVersion. I think the order of 
> ids/names being looked up is more important than the order of the 
> dependencies. So first look for servlet-api then for servletapi then for 
> geronimo-spec-servlet. (something alike for ejb).
> - When no servlet version was found use the J2EE version (resolveJ2eeVersion) 
> to determine the servlet version to be used.
> - Implemented resolveEjbVersion along the lines of resolveServletVersion.
> - Changed resolveJ2eeVersion to work along the line of resolveServletVersion.
> - Fixed a glitch in resolveJavaVersion, where the getCompilerSourceVersion 
> was retrieved but not used.
> Hope my efforts are usefull for others. ;-)
> regards,
> misl

-- 
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: (MECLIPSE-198) EJB version is not resloved

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MECLIPSE-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MECLIPSE-198.


   Resolution: Fixed
Fix Version/s: 2.4

Fixed. SNAPSHOT deployed.

> 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
> Assigned To: Arnaud Heritier
> Fix For: 2.4
>
>
> 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] Closed: (MECLIPSE-108) .wtpmodules with version 2.4 for javax.servlet:servlet-api:2.3

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MECLIPSE-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MECLIPSE-108.


   Resolution: Fixed
Fix Version/s: 2.4

Fixed. SNAPSHOT deployed.

> .wtpmodules with version 2.4 for javax.servlet:servlet-api:2.3
> --
>
> Key: MECLIPSE-108
> URL: http://jira.codehaus.org/browse/MECLIPSE-108
> Project: Maven 2.x Eclipse Plugin
>  Issue Type: Bug
>  Components: WTP support
>Affects Versions: 2.2
>Reporter: Daniel Schulz
> Assigned To: Arnaud Heritier
> Fix For: 2.4
>
> Attachments: MECLIPSE-108-maven-eclipse-plugin.patch
>
>
> specified the following dependency:
> 
>   
>   servlet-api
>   javax.servlet
>   2.3
>   
> mvn eclipse:clean eclipse:eclipse produces the following .wtpmodules snippet:
>  
>   2.4
>   
> 
> think, it should be  2.3.  looks like it was the intention 
> of the plugin to detect the servlet-api version by processing the dependency 
> list. there is a method resolveServletVersion() in 
> org.apache.maven.plugin.eclipse.writers.AbstractWtpResourceWriter.

-- 
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: (MECLIPSE-241) Compiler settings from parent project aren't used in wtp facet

[Arnaud Heritier (JIRA)]

 [ 
http://jira.codehaus.org/browse/MECLIPSE-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MECLIPSE-241.


   Resolution: Fixed
Fix Version/s: 2.4

Fixed. SNAPSHOT deployed.

> Compiler settings from parent project aren't used in wtp facet
> --
>
> Key: MECLIPSE-241
> URL: http://jira.codehaus.org/browse/MECLIPSE-241
> Project: Maven 2.x Eclipse Plugin
>  Issue Type: Bug
>  Components: WTP support
>Affects Versions: 2.3
> Environment: maven 2.0.4 / maven 2.0.5
>Reporter: Arnaud Heritier
> Assigned To: Arnaud Heritier
>Priority: Minor
> Fix For: 2.4
>
> Attachments: project-28.zip
>
>
> In a parent POM I have :
> {code:xml}
> 
>   org.apache.maven.plugins
>   maven-compiler-plugin
>   
> 1.5
> 1.5
>   
> 
> {code}
> And I have a submodule (a war) configure to generate wtp 1.5 settings :
> {code:xml}
> 
>   org.apache.maven.plugins
>   maven-eclipse-plugin
>   
> 1.5
>   
> 
> {code}
> After running eclipse:eclipse I have the following in my 
> org.eclipse.wst.common.project.facet.core.xml :
> {code:xml}
> 
>   
>   
>   
>   
> 
> {code}
> And not
> {code:xml}
> 
>   
>   
>   
>   
> 
> {code}

-- 
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-241) Compiler settings from parent project aren't used in wtp facet

[Arnaud Heritier (JIRA)]

Compiler settings from parent project aren't used in wtp facet
--

 Key: MECLIPSE-241
 URL: http://jira.codehaus.org/browse/MECLIPSE-241
 Project: Maven 2.x Eclipse Plugin
  Issue Type: Bug
  Components: WTP support
Affects Versions: 2.3
 Environment: maven 2.0.4 / maven 2.0.5
Reporter: Arnaud Heritier
Priority: Minor
 Attachments: project-28.zip

In a parent POM I have :
{code:xml}

  org.apache.maven.plugins
  maven-compiler-plugin
  
1.5
1.5
  

{code}
And I have a submodule (a war) configure to generate wtp 1.5 settings :
{code:xml}

  org.apache.maven.plugins
  maven-eclipse-plugin
  
1.5
  

{code}
After running eclipse:eclipse I have the following in my 
org.eclipse.wst.common.project.facet.core.xml :
{code:xml}

  
  
  
  

{code}
And not
{code:xml}

  
  
  
  

{code}

-- 
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: (MECLIPSE-235) Eclipse Maven plugin has its own Classpath Container that conflicts with generated class paths when enabled.

[Arnaud Heritier (JIRA)]

[ 
http://jira.codehaus.org/browse/MECLIPSE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90070
 ] 

Arnaud Heritier commented on MECLIPSE-235:
--

Very interesting feature, but can you also provide some tests and the 
documentation. Thx.

> Eclipse Maven plugin has its own Classpath Container that conflicts with 
> generated class paths when enabled.
> 
>
> Key: MECLIPSE-235
> URL: http://jira.codehaus.org/browse/MECLIPSE-235
> Project: Maven 2.x Eclipse Plugin
>  Issue Type: New Feature
> Environment: Should be OK for ALL
>Reporter: Hasan Ceylan
> Fix For: 2.4
>
> Attachments: eclipseM2Plugin.diff
>
>
> When we create eclipse projects using the maven-eclipse-plugin, all the class 
> path entries for the dependent libraries are added to the .classpath.
> For those like me who has eclipse maven plugin, enabling maven2 for the 
> generated project creates duplicate libraries as maven also introduces its 
> own container based on the information in the pom.xml.
> I took the liberty to modify the head, and introduced the 
> "eclipse.withM2Plugin" parameter. If this parameter is true in the runtime,
> 1) In EclipsePlugin.setup()
> a) If "org.maven.ide.eclipse.maven2Nature" nature is not added in the 
> configuration, it is added automatically.
> b) If "org.maven.ide.eclipse.maven2Builder" builder is not added in the 
> configuration, it is added automatically.
> c) If "org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER" container is added 
> automatically.
> 2) In config
> introduced the method hasMaven2Nature() which indicates if Maven2 nature is 
> available
> 3) M2_REPO's skipped in EclipseClasspathWriter if config returns true for 
> hasMaven2Nature()
> Hope you like the patch...
> Regards,
> Hasan Ceylan

-- 
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-212) configure checksum policy for proxied repository

[Arnaud Heritier (JIRA)]

[ 
http://jira.codehaus.org/browse/MRM-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89716
 ] 

Arnaud Heritier commented on MRM-212:
-

With the recent refactoring, we have xcertainly to review our patch. I'll try 
to do it in some days because I want to update my archiva release and I need 
this , I'll commit it directly to be sure that we'll not loose it.

> configure checksum policy for proxied repository
> 
>
> Key: MRM-212
> URL: http://jira.codehaus.org/browse/MRM-212
> Project: Archiva
>  Issue Type: Improvement
>  Components: remote proxy
>Reporter: nicolas de loof
>Priority: Critical
> Fix For: 1.0
>
> Attachments: 2006-10-26-checksum-policy.patch, MRM-212.patch
>
>
> Some artifact on repo1.maven.org have bad checksum. This need fix, but this 
> also make archiva not usable as a replacement for maven-proxy.
> As maven itself allow to configure a checksum policy, a new configuration 
> parameter on proxied repo would be nice.

-- 
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: (MPARTIFACT-74) artifact-install fails when maven-xdoc-plugin 1.10 is installed

[Arnaud Heritier (JIRA)]

[ 
http://jira.codehaus.org/browse/MPARTIFACT-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85827
 ] 

Arnaud Heritier commented on MPARTIFACT-74:
---

I'm not sure but I think that this version of the xdoc plugin works only with 
maven 1.1
I'll have a look at it because I don't find this information in the 
documentation :-(

> artifact-install fails when maven-xdoc-plugin 1.10 is installed
> ---
>
> Key: MPARTIFACT-74
> URL: http://jira.codehaus.org/browse/MPARTIFACT-74
> Project: maven-artifact-plugin
>  Issue Type: Bug
>Affects Versions: 1.5.2
> Environment: Linux, jdk 1.5, maven 1.0.2
>Reporter: Philippe Sevestre
>Priority: Minor
>
> After upgrading maven-xdoc-plugin from 1.9 to 1.10, jar:install goals fail 
> with the following message:
> /home/phil/.maven/cache/maven-artifact-plugin-1.5.2/plugin.jelly:62:9: 
>  Error getting the project as a string
> Going back to maven-xdoc-plugin 1.9 solves this problem...
> Not sure if this belongs to here or xdoc, but I think it worths reporting.
> Running with debug messages enabled shows another nested exception 
> complaining about a unknown "artifactDirectory" tag somewhere.

-- 
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: (MPCHANGES-33) Make it possible to configure the location of the changes.xml file

[Arnaud Heritier (JIRA)]

[ http://jira.codehaus.org/browse/MPCHANGES-33?page=comments#action_85111 ] 

Arnaud Heritier commented on MPCHANGES-33:
--

Yes, the name of the property you proposed is fine for me.
You can use this issue in others plugins (for the issue # in the changes file).
You can also add on these plugins a constraint like :

{code:xml}
  


{code}

> Make it possible to configure the location of the changes.xml file
> --
>
> Key: MPCHANGES-33
> URL: http://jira.codehaus.org/browse/MPCHANGES-33
> Project: maven-changes-plugin
>  Issue Type: New Feature
>Affects Versions: 1.7
>Reporter: Dennis Lundberg
> Fix For: 1.7.1
>
> Attachments: MPCHANGES-33.patch
>
>
> It is useful for people that are in a transition from Maven 1 to Maven 2 to 
> be able to move the changes.xml file to another location that the default 
> one. The attached patch introduces a new property "maven.changes.file" that 
> can be used to configure the location of the file. The default value is the 
> same as what has been used in the previous versions.

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