Re: ApacheCon/OSSummit roll call!
I will be at Apache Con in Atlanta. See you all there. Scott Ryan CTO Soaring Eagle L.L.C. Denver, Co. 80129 www.soaringeagleco.com www.theryansplace.com (303) 263-3044 [EMAIL PROTECTED] On Oct 29, 2007, at 11:15 PM, Brett Porter wrote: I know several folks are presenting and will definitely be there, but I thought it might be good to send a shout out and see who is coming along? Hopefully we'll get some opportunities for getting together around the hackathon/code-a-ramas. I'm also interested in organising a Maven project BOF at each. Any thoughts? [ ] I'll be at ApacheCon US in Atlanta [ ] I'll be at OSSummit Asia in Hong Kong I'm planning to be at both with bells on. Cheers, Brett -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Terracotta Maven plugin(s), anyone?
I would love to work with you on developing the plugin. I heard about their presentation at the Denver Java User's Group and would love to look at their technology deeper. I have developed some plugins already for weblogic and appfuse. Scott Ryan [EMAIL PROTECTED] On Feb 18, 2007, at 1:08 PM, Jim Bethancourt wrote: Hi all, I was wondering if anyone would be interested in developing a Maven 2 plugin / plugins that would allow for developers to apply Terracotta bytecode enhancement to their Java code through Maven. I've only worked through the Terracotta DSO tutorial, but it seems like a Maven plugin would make a lot of sense to automate the bytecode enhancement through the Maven build life cycle. I can email the Terracotta folks and ask them if they would be able to post the Terracotta files on Ibiblio since Maven 2.0.5 now supports different licenses. I've dabbled in plugin authoring before as well, but I don't know exactly what all it would entail in this case. Please write back and let me know 1) If you would find the plugin useful and/or 2) If you would be interested in helping develop such a plugin Thanks, Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
New Weblogic 2.8.0 and 2.9.0 snapshot code in SVN
I have checked in the code for new snapshots for both versions of the plugins. This code fixes a number of issues but mainly; Classpath incorrect with APPC and Clientgen Remote deployment does not work on 9.0 I have also removed or renamed some of the configuration parameters to make them more clear and have removed some unused parameters. At this time I am not able to push up the snapshot due to some authentication issues. You can find the 2.9.0 code in the sandbox trunk and the 2.8.0 code is in the branch if you want to build it until I can push up the snapshot. I would appreciate any input on problems, fixes or additional features you would like. I will be porting this new code over to the Cargo plugin next week. I will be converting the 2.9.0 plugin over to use JSR-88 deployment over the next few weeks as well. Let me know how I can help. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Latest code is missing some missing imports from reporting package and will not build
I am trying to build the latest version of the source. I deleted my maven repository and started from scratch to make sure all my snapshots were clean. In the archiva-web project I am getting an issue with the file ShowArtifactAction.java as it is not able to resolve the following imports: import org.apache.maven.report.projectinfo.dependencies.Dependencies; import org.apache.maven.report.projectinfo.dependencies.ReportResolutionListener; If I comment out the code that uses those imports the application will not deploy on Tomcat. This is my first installation on Tomcat so I am not sure what version of Tomcat this has been tested on or if anyone has had luck with the latest code on Tomcat. The imports appear to be from the plugin maven-project-info-reports-plugin however the two classes are not in the 2.1-SNAPSHOT that I have downloaded from the repositories pointed to in the pom. Any pointers would be appreciated. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044
Help Needed?
I am very interested in this project and want to see it move forward. I am involved in many Open Source projects as a committer and contributor but would like to take some time to help out here and understand the technology so that I can add things that we might need at our company and would benefit the community as a whole. Is there any area that I can help out and do you want my help. I think a place to start might be documentation such as an install and configuration guide (separate guides). Also beefing up the information on the site to include more information about what the project does and the roadmap. Eventually I would love to add more reporting features as I love some of the things that are available on the http://www.mvnregistry.com/search/ site including the top 25 and can think of lots of other things that would be useful. Like all of you I am busy with a job and contributing to a number of projects however there is plenty of time here in Denver between 2 and 3 AM in the morning. Let me know if you would want some help and where I might begin to look to help out. Just as an FYI the projects I am currently working on include Maven Mojo, Beehive, Cargo, AppFuse, Eclipse,WTFIGO etc. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044
RE: Status of Security features
So here is my scenario so I can see if it makes sense and might be supported at this point? Scenario 1 I have 3 managed repositories. One has a proxy out to the Maven type repositories and holds all of our open source and maven related stuff. The second repository holds all of our licensed software and the third holds our internal build artifacts/applications. All users access the combined repositories via the proxy so for example http://localhost:8080/archiva/proxy . We would like to control on a group or perhaps artifact/version level who can use which things from the repository. For example you would need permission to use one of the licensed artifacts or perhaps we are just testing the latest version of Hibernate or Spring and don't want everyone to have access or perhaps there is a specific license that we deem risky and we want to limit the number of people using artifacts of that license (Initially by artifact or group but eventually it would be nice to have a record of license types to report on from within the repo). Scenario 2 We have an SCM team and we have repositories for each environment dev, qa, stage, train, prod. We only want members of the SCM team to be able to upload and download artifacts from that repository. Even though all of this is done via the proxy (except for the upload I believe). I know that some of this might be beyond what is there today or planned but those are some scenarios we are trying to support enterprise wide. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Jesse McConnell [mailto:[EMAIL PROTECTED] Sent: Friday, October 20, 2006 8:39 PM To: archiva-dev@maven.apache.org; [EMAIL PROTECTED] Subject: Re: Status of Security features its in and on the trunk. at the moment the permission assignments are static but with the next iteration of the plexus-security integration we'll have more dynamic permission creation for assigning to roles. I think we need to come up with some more stories about how archiva will be used in practice by different 'jobs' but there is a pretty decent first pass in place right now I think. feedback is of course, more then welcome :) jesse On 10/20/06, Scott Ryan [EMAIL PROTECTED] wrote: I noticed a detailed discussion on rbac security and the roles and actions associated with it. That looks like a very powerful feature. What is the status of implementing this into Archiva? Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -- jesse mcconnell [EMAIL PROTECTED]
RE: JSP precompiling with Weblogic 8.1
You can use the weblogic plugin and the appc mojo to pre compile your jsp's.
You can find the weblogic plugin at codehaus.
http://mojo.codehaus.org/weblogic-maven-plugin/
Scott Ryan
Chief Technology Officer
Soaring Eagle L.L.C.
[EMAIL PROTECTED]
www.soaringeagleco.com
(303) 263-3044
-Original Message-
From: Marc Chételat ML [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 07, 2006 5:20 AM
To: dev@maven.apache.org
Subject: JSP precompiling with Weblogic 8.1
Hello all,
First of all, I m using maven 2.0.4.
After several days searching on the Web, I found nothing interesting
about JSPs precompilation for Weblogic 8.1.
Of course, we have the plugin jspc-maven-plugin, but unfortunately it
compiles only jsps for tomcat... with a dependency to tomcat 5.5. I
checked the plugin sources and it calls the JspC class from jasper.
First question, does there exist a weblogic.jspc plugin ? Or it is
planned for jspc-maven-plugin to support the weblogic ?
Other solution is to use an external ant task from maven like :
configuration
tasks
echo message=Precompiling JSPs... /
echo message=-d
${project.build.directory}/${project.build.finalName}/WEB-INF/classes -k
-g -compileAll -webapp
${project.build.directory}/${project.build.finalName} /
java failonerror=true classname=weblogic.jspc fork=yes
arg line=-d
${project.build.directory}/${project.build.finalName}/WEB-INF/classes -k
-g -compileAll -webapp
${project.build.directory}/${project.build.finalName} /
classpath
path refid=maven.test.classpath /
path refid=maven.plugin.classpath /
/classpath
/java
echo message=... done /
/tasks
/configuration
Second question, using standard directory layout what is the best way to
compile jsps with this external task? Currently jsps are under
/src/main/webapp/ with others files like images or html pages. But
should I move jsps under another directory, compile them with the ant
task and then copy them under /target folder ? Can somebody provide me
an example with folders used during the jsp precompiling process?
Thanks in advance for help!
Regards,
ML
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Trying to deploy a sandbox plugin to the mojo repository
Are there any process instructions on how to deploy new versions of a plugin to the mojo sandbox repository? I used to be able to run mvn:deploy but now I get a connection refused error authentication failure trying to deploy the weblogic and appfuse plugins. Is it possible that my key is no longer valid? Are there setup instructions on how to activate a key to be able to deploy to the sandbox repository? I also want to update the master site to include the entry for the new appfuse plugin. Any pointers to existing documentation or some basic instructions would be appreciated. The exception is listed below: Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEV-353) I need to have these 4 pom's posted to reference some bea 3rd party artifacts to support the weblogic plugin
[ http://jira.codehaus.org/browse/MEV-353?page=comments#action_59899 ] Scott Ryan commented on MEV-353: The jars are collections of everything under the sun and make up the weblogic runtime. The classes I use in the various jars and plugins are as follows: Weblogic 8.1 weblogic.jar weblogic.management.runtime.DeployerRuntimeMBean weblogic.management.deploy.DeployerRuntime weblogic.management.ManagementException webservices.jar weblogic.appc Weblogic 9.0 weblogic.jar weblogic.deploy.api.spi.WebLogicTargetModuleID webservices.jar weblogic.appc I was not sure where to place the jars to resolve the pom lookup despite not being able to put the jars on a hosted site but I figured having the poms up there like javax does would allow people to keep up with pom changes and manually install the jars based on instructions I give them. Maybe if it is based on package name then they should go under weblogic at the root. I just wanted to stay away from the root but am more than happy to update the poms to be placed weblogic if that makes more sense based on standards and package names. Let me know. I need to have these 4 pom's posted to reference some bea 3rd party artifacts to support the weblogic plugin Key: MEV-353 URL: http://jira.codehaus.org/browse/MEV-353 Project: Maven Evangelism Type: Task Components: Missing POM Reporter: Scott Ryan Attachments: weblogic-8.1.pom, weblogic-9.0.pom, webservices-8.1.pom, webservices-9.0.pom I am attaching 4 pom files to support the weblogic plugin. These will allow local installation of the 3rd party jars and still support clean builds with the weblogic plugin. Please feel free to correct me or ask any additional questions needed to get this done. thanks -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-353) I need to have these 4 pom's posted to reference some bea 3rd party artifacts to support the weblogic plugin
[ http://jira.codehaus.org/browse/MEV-353?page=all ] Scott Ryan updated MEV-353: --- Attachment: weblogic-9.0.pom.txt webservices-8.1.pom.txt weblogic-8.1.pom.txt I need to have these 4 pom's posted to reference some bea 3rd party artifacts to support the weblogic plugin Key: MEV-353 URL: http://jira.codehaus.org/browse/MEV-353 Project: Maven Evangelism Type: Task Components: Missing POM Reporter: Scott Ryan Attachments: weblogic-8.1.pom, weblogic-8.1.pom.txt, weblogic-9.0.pom, weblogic-9.0.pom.txt, webservices-8.1.pom, webservices-8.1.pom.txt, webservices-9.0.pom, webservices-9.0.pom.txt I am attaching 4 pom files to support the weblogic plugin. These will allow local installation of the 3rd party jars and still support clean builds with the weblogic plugin. Please feel free to correct me or ask any additional questions needed to get this done. thanks -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-353) I need to have these 4 pom's posted to reference some bea 3rd party artifacts to support the weblogic plugin
[ http://jira.codehaus.org/browse/MEV-353?page=all ] Scott Ryan updated MEV-353: --- Attachment: webservices-9.0.pom.txt I need to have these 4 pom's posted to reference some bea 3rd party artifacts to support the weblogic plugin Key: MEV-353 URL: http://jira.codehaus.org/browse/MEV-353 Project: Maven Evangelism Type: Task Components: Missing POM Reporter: Scott Ryan Attachments: weblogic-8.1.pom, weblogic-8.1.pom.txt, weblogic-9.0.pom, weblogic-9.0.pom.txt, webservices-8.1.pom, webservices-8.1.pom.txt, webservices-9.0.pom, webservices-9.0.pom.txt I am attaching 4 pom files to support the weblogic plugin. These will allow local installation of the 3rd party jars and still support clean builds with the weblogic plugin. Please feel free to correct me or ask any additional questions needed to get this done. thanks -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEV-353) I need to have these 4 pom's posted to reference some bea 3rd party artifacts to support the weblogic plugin
[ http://jira.codehaus.org/browse/MEV-353?page=comments#action_59903 ] Scott Ryan commented on MEV-353: I have updated and uploaded new pom files with the groupid changed from com.bea.wlserver to weblogic to reflect the package structure within the jars. I need to have these 4 pom's posted to reference some bea 3rd party artifacts to support the weblogic plugin Key: MEV-353 URL: http://jira.codehaus.org/browse/MEV-353 Project: Maven Evangelism Type: Task Components: Missing POM Reporter: Scott Ryan Attachments: weblogic-8.1.pom, weblogic-8.1.pom.txt, weblogic-9.0.pom, weblogic-9.0.pom.txt, webservices-8.1.pom, webservices-8.1.pom.txt, webservices-9.0.pom, webservices-9.0.pom.txt I am attaching 4 pom files to support the weblogic plugin. These will allow local installation of the 3rd party jars and still support clean builds with the weblogic plugin. Please feel free to correct me or ask any additional questions needed to get this done. thanks -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-353) I need to have these 4 pom's posted to reference some bea 3rd party artifacts to support the weblogic plugin
I need to have these 4 pom's posted to reference some bea 3rd party artifacts to support the weblogic plugin Key: MEV-353 URL: http://jira.codehaus.org/browse/MEV-353 Project: Maven Evangelism Type: Task Components: Missing POM Reporter: Scott Ryan Attachments: weblogic-8.1.pom, weblogic-9.0.pom, webservices-8.1.pom, webservices-9.0.pom I am attaching 4 pom files to support the weblogic plugin. These will allow local installation of the 3rd party jars and still support clean builds with the weblogic plugin. Please feel free to correct me or ask any additional questions needed to get this done. thanks -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-353) I need to have these 4 pom's posted to reference some bea 3rd party artifacts to support the weblogic plugin
[ http://jira.codehaus.org/browse/MEV-353?page=all ] Scott Ryan updated MEV-353: --- Attachment: webservices-8.1.pom weblogic-9.0.pom weblogic-8.1.pom I need to have these 4 pom's posted to reference some bea 3rd party artifacts to support the weblogic plugin Key: MEV-353 URL: http://jira.codehaus.org/browse/MEV-353 Project: Maven Evangelism Type: Task Components: Missing POM Reporter: Scott Ryan Attachments: weblogic-8.1.pom, weblogic-9.0.pom, webservices-8.1.pom, webservices-9.0.pom I am attaching 4 pom files to support the weblogic plugin. These will allow local installation of the 3rd party jars and still support clean builds with the weblogic plugin. Please feel free to correct me or ask any additional questions needed to get this done. thanks -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-353) I need to have these 4 pom's posted to reference some bea 3rd party artifacts to support the weblogic plugin
[ http://jira.codehaus.org/browse/MEV-353?page=all ] Scott Ryan updated MEV-353: --- Attachment: webservices-9.0.pom I need to have these 4 pom's posted to reference some bea 3rd party artifacts to support the weblogic plugin Key: MEV-353 URL: http://jira.codehaus.org/browse/MEV-353 Project: Maven Evangelism Type: Task Components: Missing POM Reporter: Scott Ryan Attachments: weblogic-8.1.pom, weblogic-9.0.pom, webservices-8.1.pom, webservices-9.0.pom I am attaching 4 pom files to support the weblogic plugin. These will allow local installation of the 3rd party jars and still support clean builds with the weblogic plugin. Please feel free to correct me or ask any additional questions needed to get this done. thanks -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (CONTINUUM-604) Failure to remove working directory when deleteing project on Windows
Failure to remove working directory when deleteing project on Windows - Key: CONTINUUM-604 URL: http://jira.codehaus.org/browse/CONTINUUM-604 Project: Continuum Type: Bug Components: Core system Versions: 1.0.2 Environment: Windows Server 2003 Reporter: Scott Ryan When I try to delete a project I get the following stack trace ognl.MethodFailedException: Method removeProject failed for object [EMAIL PROTECTED] [org.apache.maven.continuum.ContinuumException: Error while deleting project working directory.] at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:796) at ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61) at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819) at ognl.ASTMethod.getValueBody(ASTMethod.java:75) at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170) at ognl.SimpleNode.getValue(SimpleNode.java:210) at ognl.Ognl.getValue(Ognl.java:333) at ognl.Ognl.getValue(Ognl.java:378) at ognl.Ognl.getValue(Ognl.java:357) at org.codehaus.plexus.formica.action.DeleteEntity.uponSuccessfulValidation(DeleteEntity.java:57) at org.codehaus.plexus.formica.action.DeleteEntity.execute(DeleteEntity.java:47) at org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve.java:68) at org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipeline.java:70) at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54) at org.codehaus.plexus.summit.Summit.doPost(Summit.java:108) at javax.servlet.http.HttpServlet.service(HttpServlet.java:615) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1807) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525) at org.mortbay.http.HttpContext.handle(HttpContext.java:1757) at org.mortbay.http.HttpServer.service(HttpServer.java:879) at org.mortbay.http.HttpConnection.service(HttpConnection.java:789) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:806) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:331) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:520) /-- Encapsulated exception \ org.apache.maven.continuum.ContinuumException: Error while deleting project working directory. at org.apache.maven.continuum.DefaultContinuum.logAndCreateException(DefaultContinuum.java:1834) at org.apache.maven.continuum.DefaultContinuum.removeProject(DefaultContinuum.java:265) 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 ognl.OgnlRuntime.invokeMethod(OgnlRuntime.java:491) at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:785) at ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61) at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819) at ognl.ASTMethod.getValueBody(ASTMethod.java:75) at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170) at ognl.SimpleNode.getValue(SimpleNode.java:210) at ognl.Ognl.getValue(Ognl.java:333) at ognl.Ognl.getValue(Ognl.java:378) at ognl.Ognl.getValue(Ognl.java:357) at org.codehaus.plexus.formica.action.DeleteEntity.uponSuccessfulValidation(DeleteEntity.java:57) at org.codehaus.plexus.formica.action.DeleteEntity.execute(DeleteEntity.java:47) at org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve.java:68) at org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipeline.java:70) at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54) at org.codehaus.plexus.summit.Summit.doPost(Summit.java:108) at javax.servlet.http.HttpServlet.service(HttpServlet.java:615) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294
[jira] Closed: (CONTINUUM-604) Failure to remove working directory when deleteing project on Windows
[ http://jira.codehaus.org/browse/CONTINUUM-604?page=all ] Scott Ryan closed CONTINUUM-604: Resolution: Fixed It looks like since continuum was running as a service it had locked the directory at the top. A restart and retest with several other projects fixed the issue. Failure to remove working directory when deleteing project on Windows - Key: CONTINUUM-604 URL: http://jira.codehaus.org/browse/CONTINUUM-604 Project: Continuum Type: Bug Components: Core system Versions: 1.0.2 Environment: Windows Server 2003 Reporter: Scott Ryan When I try to delete a project I get the following stack trace ognl.MethodFailedException: Method removeProject failed for object [EMAIL PROTECTED] [org.apache.maven.continuum.ContinuumException: Error while deleting project working directory.] at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:796) at ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61) at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819) at ognl.ASTMethod.getValueBody(ASTMethod.java:75) at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170) at ognl.SimpleNode.getValue(SimpleNode.java:210) at ognl.Ognl.getValue(Ognl.java:333) at ognl.Ognl.getValue(Ognl.java:378) at ognl.Ognl.getValue(Ognl.java:357) at org.codehaus.plexus.formica.action.DeleteEntity.uponSuccessfulValidation(DeleteEntity.java:57) at org.codehaus.plexus.formica.action.DeleteEntity.execute(DeleteEntity.java:47) at org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve.java:68) at org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipeline.java:70) at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54) at org.codehaus.plexus.summit.Summit.doPost(Summit.java:108) at javax.servlet.http.HttpServlet.service(HttpServlet.java:615) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1807) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525) at org.mortbay.http.HttpContext.handle(HttpContext.java:1757) at org.mortbay.http.HttpServer.service(HttpServer.java:879) at org.mortbay.http.HttpConnection.service(HttpConnection.java:789) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:806) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:331) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:520) /-- Encapsulated exception \ org.apache.maven.continuum.ContinuumException: Error while deleting project working directory. at org.apache.maven.continuum.DefaultContinuum.logAndCreateException(DefaultContinuum.java:1834) at org.apache.maven.continuum.DefaultContinuum.removeProject(DefaultContinuum.java:265) 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 ognl.OgnlRuntime.invokeMethod(OgnlRuntime.java:491) at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:785) at ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61) at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819) at ognl.ASTMethod.getValueBody(ASTMethod.java:75) at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170) at ognl.SimpleNode.getValue(SimpleNode.java:210) at ognl.Ognl.getValue(Ognl.java:333) at ognl.Ognl.getValue(Ognl.java:378) at ognl.Ognl.getValue(Ognl.java:357) at org.codehaus.plexus.formica.action.DeleteEntity.uponSuccessfulValidation(DeleteEntity.java:57) at org.codehaus.plexus.formica.action.DeleteEntity.execute(DeleteEntity.java:47) at org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve.java:68) at org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipeline.java:70) at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54) at org.codehaus.plexus.summit.Summit.doPost(Summit.java:108
RE: sending JIRA mail to commits@maven.apache.org
I vote a big +1 Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 21, 2006 7:11 PM To: Maven Developers List Subject: sending JIRA mail to commits@maven.apache.org What do folks think of doing this to make the dev traffic a bit friendlier to the people just reading the messages? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to store and access plugin resources in maven 2
In Maven 1 there was a way to store resources with your plugin that you could easily access inside the plugin to copy out the resources etc. I used this for delivering templates etc. I accessed the directory via the plugin-resources parameter and it worked very well. Is there such a parameter available in Maven 2. I have a need to deliver some based java classes with my plugin and the archetype structure does not allow me the flexibility to deliver the files I need. I am looking for a way to package some files within my plugin and access those files from within the plugin. The alternative would be to understand how to make the archetype structure support complex java trees. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Using archetypes to deeply nest java files
I am trying to build out an archetype in support of an appfuse plugin that I am building for Maven 2.0. I have the following structure src/main/java/service/packagename.../service/Manager.java src/main/java/service/packagename.../service/impl/ManagerImpl.java I set up my archetype-resources as so: /src/main/java/service/Manager.java with $package in the package name /src/main/java/service/impl/ManagerImpl.java with $package in the package name. When I ran the archetype with package name com.examplepackage the result was: /src/main/java/service/com/examplepackage/Manager.java /src/main/java/service/impl/com/examplepackage/ManagerImpl.java both had the package name com.examplepackage I also tried to use $package.service and $package.service.impl in the base java files and no substitution took place at all. I would also like to update any dependencies within the files with the proper package name for example if the Impl relies on the base then I would like the following to work: FILE 1: Manager.java package $package.service; FILE 2: ManagerImpl.java package $package.service.impl import $package.service.Manager; and have the files placed in the proper location. Is this possible? If not does it make sense to place this code in my plugin and just move and package the files during a setup step? Thanks for all you help and I hope to publish the appfuse plugin soon. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JIRA projects for m2 plugins?
I am ready to check in the Weblogic Plugin. I think it makes sense to create new projects for these plugins since the structure will be quite different. This also allows us to keep maintaining the version 1.0 plugins as well. I woiuld prefer that we start with 2.0 for a number of reasons since I want to keep maintaining the 1.0 plugin for a while as well. I plan on having an alpha and beta version since I am discovering some new ideas with the advent of the native Java option as well as new interaction with the container. Do we want one main maven2 project with sub projects under that or should we create a maven2 directory under each project? I too would like to get my code into the repository ASAP. Looking forward to everyone's input. Scott D. Ryan Chief Technology Officer Soaring Eagle LLC. 9742 S. Whitecliff Place Highlands Ranch, Co. 80129 (303) 263-3044 [EMAIL PROTECTED] www.soaringeagleco.com -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 15, 2005 1:58 AM To: 'Maven Developers List' Subject: JIRA projects for m2 plugins? So what's the status on this? - Have we decided to create separate JIRA projects for m2 plugins? - Can I create a Clover JIRA project the m2 clover plugin? I'd like to get moving on this. - Is there any recommendation for versioning the plugins? Should we start at 2.0 and simply increase the minor? Do plugins have to go through alphas, betas, rcs or is it left at the discretion of the plugin contributors in general? Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to configure multiple parameters in the pom.xml for a Maven 2 plugin
I am trying to modify my plugin to accept multiple parameters as a String array or an ArrayList. In my mojo I have configured the following: /** * An array of names of servers to deploy the target onto. the deployment. * * @parameter */ private String[] serverName; with getters and setters to support the type. In my pom.xml I have the following configured for the parameters in the plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-sample-plugin/artifactId configuration serverNamemyserver/serverName /configuration /plugin When I run the plugin I get the following error message: (found static expression: 'myserver' which may act as a default value). Cause: Cannot assign configuration entry 'serverName' to 'class [Ljava.lang.String;' from 'myserver, which is of type class java.lang.String I read the documentation on handling multiple parameters but did not seem to understand the hints that were given. Can anyone suggest what I am doing wrong. I am sure it is somewhere in my definition of the parameter in the pom.xml. Also any hints as to how to handle a List as well would be appreciated. Thanks Scott D. Ryan Chief Technology Officer Soaring Eagle LLC. 9742 S. Whitecliff Place Highlands Ranch, Co. 80129 (303) 263-3044 [EMAIL PROTECTED] www.soaringeagleco.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
