[jira] Commented: (MASSEMBLY-189) plugin not correctly interpolating POM variables like project.build.directory

2007-04-29 Thread Phil Steitz (JIRA)

[ 
http://jira.codehaus.org/browse/MASSEMBLY-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94439
 ] 

Phil Steitz commented on MASSEMBLY-189:
---

I had a similar problem trying to get ${project.build.finalName} interpolated 
so I could set the baseDirectory of my source distro to 
${project.build.finalName}-src.  This can be worked around by using 
${artifactId}-${version}-src instead; but the first interpolation should work.

 plugin not correctly interpolating POM variables like project.build.directory
 -

 Key: MASSEMBLY-189
 URL: http://jira.codehaus.org/browse/MASSEMBLY-189
 Project: Maven 2.x Assembly Plugin
  Issue Type: Bug
Affects Versions: 2.1
 Environment: I used both released version 2.1 and also 2.2-SNAPSHOT
Reporter: Ray Suliteanu
Priority: Critical

 I have a assembly descriptor file with ${project.build.directory} in the 
 source element of a file. I get an error Failed to create assembly: File 
 to filter not found because the file path has ${project.build.directory} 
 rather than the value of ${project.build.directory}.
 I have traced the problem to AssemblyInterpolator.interpolateElementValue(). 
 It tries to look up build.directory in ReflectionValueExtractor.evaluate() 
 rather than project.build.directory, and it can't evaluate build.directory. A 
 hack workaround is ...
   if (value == null)
   {
 try
 {
   value = ReflectionValueExtractor.evaluate(realExpr, project);
   if (value == null)
   {
 // HACK: strip ${ and } and retry
 wholeExpr = wholeExpr.substring(2, wholeExpr.length() - 1);
 value = ReflectionValueExtractor.evaluate(wholeExpr, project);
   }
 }

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (MAVENUPLOAD-1461) Request to upload hamcrest api 1.0 bundle

2007-04-29 Thread Jason van Zyl (JIRA)

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94447
 ] 

Jason van Zyl commented on MAVENUPLOAD-1461:


It's owned for my Joe Walnes. I vouch for Joe (Sitemesh, QDox, Pico) as does 
Mauro Talevi.

 Request to upload hamcrest api 1.0 bundle
 -

 Key: MAVENUPLOAD-1461
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1461
 Project: maven-upload-requests
  Issue Type: Task
Reporter: Joe Walnes



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

2007-04-29 Thread 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] Commented: (MRM-323) Managed repo in archiva cannot be accessed thru direct webdav url even with valid credentials (Archiva deployed in Tomcat)

2007-04-29 Thread 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] Created: (MECLIPSE-263) Project Facet 'Java' set to 1.4 instead of 5.0 in a Java 5.0 project

2007-04-29 Thread Geir Pettersen (JIRA)
Project Facet 'Java' set to 1.4 instead of 5.0 in a Java 5.0 project


 Key: MECLIPSE-263
 URL: http://jira.codehaus.org/browse/MECLIPSE-263
 Project: Maven 2.x Eclipse Plugin
  Issue Type: Bug
  Components: WTP support
 Environment: WinXP, Eclipse 3.2 + WTP 1.5, Maven 2.0.5
Reporter: Geir Pettersen


In pom.xml the source configuration is set to Java 1.5 however mvn 
-Dwtpversion=1.5 eclipse:eclipse sets the Project Facet Java to 1.4 
instead of 5.0. This has to be set manually after executing the plugin and 
refreshing eclipse project.

pom.xml configuration to use java 5.0 source level:
build
pluginManagement
plugins
plugin

artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
/plugin
/plugins
/pluginManagement
/build

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Created: (MECLIPSE-264) Support for WTP2.0

2007-04-29 Thread Geir Pettersen (JIRA)
Support for WTP2.0
--

 Key: MECLIPSE-264
 URL: http://jira.codehaus.org/browse/MECLIPSE-264
 Project: Maven 2.x Eclipse Plugin
  Issue Type: Improvement
Reporter: Geir Pettersen


As far as I can see this plugin only supports WTP version 1.0 and 1.5. while 
WTP 2.0 is already released in milestone 6

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