[jira] Commented: (MECLIPSE-94) Allow eclipse:eclipse to work on pom (and other) projects
[ http://jira.codehaus.org/browse/MECLIPSE-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108938 ] Frank Cornelis commented on MECLIPSE-94: As Vincent commented, generating a .project file for POM projects that do not have leaf projects is indeed quite useful. I have several POM leaf project: - documentation projects, i.e., they only contain sites. - assembly projects, i.e. they package things into ZIP files via the maven-assembly-plugin The boring thing is that these projects are not visible from within Eclipse right now. For my documentation projects the simple workaround is to change the artifact type to JAR. This makes the project to generate an empty JAR but at least it's visible/editable from within Eclipse. As for the assembly projects, there is no easy way around here... so I cannot access these easily from within Eclipse. > Allow eclipse:eclipse to work on pom (and other) projects > - > > Key: MECLIPSE-94 > URL: http://jira.codehaus.org/browse/MECLIPSE-94 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Felipe Leme > > I'm creating a Java EE project based on the m2book (which I was reviewing; > it's not available yet...) and one of the projects is a pom-packaging project > used for integration tests. According to Vincent, currently this project must > be a pom (in fact, I tried to set it as jar, but then the test phase would be > run anyway, which would cause the tests to fail), as it doesn't produces a > jar. But as it has java files (on the src/main/it/java directory), I tried to > call eclipse:eclipse but it fails, saying that "Not running eclipse plugin > goal for pom project". > For these scenarios, I think a propery would be enough. At first I thought > something about a 'force' or 'forceGeneration' property, would enough, which > the code change being from: > if ( "pom".equals( packaging ) && eclipseProjectDir == null ) > to: > if ( "pom".equals( packaging ) && eclipseProjectDir == null && > !forceGeneration ) > Then I realized there is other place where the pom nature is checked: > if ( "pom".equals( packaging ) && eclipseProjectDir == null && > !forceGeneration ) > So, I think a better name for the property would be 'javaProject' and the > change would be: > final boolean isJavaProjectProperty = // read property; defaults to false... > if ( "pom".equals( packaging ) && eclipseProjectDir == null && > !isJavaProjectProperty ) > isJavaProject = isJavaProjectProperty || !"ear".equals( packaging ) && > !"pom".equals( packaging ); > If nobody objects and someone is willing to apply the changes, I can provide > such patch (with the proper test cases). > -- Felipe > PS: I'm assigning it to Vincent for now, as he 'dreamed' that such features > already existed :-) -- 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-1507) Build are always done when it exists several build definitions for the same project group
Build are always done when it exists several build definitions for the same project group - Key: CONTINUUM-1507 URL: http://jira.codehaus.org/browse/CONTINUUM-1507 Project: Continuum Issue Type: Bug Affects Versions: 1.1-beta-3, 1.1-beta-2 Reporter: Damien Lecan Priority: Critical Based on this discussion http://www.nabble.com/When-builds-are-done-in-multi-module-projects---tf4508232.html Continuum doesn't handle correctly previous build results when several build definitions are enabled for the same project group. As Emmanuel said : After to check scm changes, Continuum look at dependencies changes. To do that, it look only at dependencies that are continuum project too. For them, a new version is detected if the latest build result of the dependency/project is more recent than the latest build result of the current build definition. In case on more than one build def, we can't know if all build def of the dependency generate an artifact or not, we know only if a new build was done and we add it in dependencies changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-1507) Build are always done when it exists several build definitions for the same project group
[ http://jira.codehaus.org/browse/CONTINUUM-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1507: Fix Version/s: To Sort > Build are always done when it exists several build definitions for the same > project group > - > > Key: CONTINUUM-1507 > URL: http://jira.codehaus.org/browse/CONTINUUM-1507 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-beta-2, 1.1-beta-3 >Reporter: Damien Lecan >Priority: Critical > Fix For: To Sort > > > Based on this discussion > http://www.nabble.com/When-builds-are-done-in-multi-module-projects---tf4508232.html > Continuum doesn't handle correctly previous build results when several build > definitions are enabled for the same project group. > As Emmanuel said : > After to check scm changes, Continuum look at dependencies changes. To do > that, it look only at dependencies that are continuum project too. For them, > a new version is detected if the latest build result of the > dependency/project is more recent than the latest build result of the current > build definition. In case on more than one build def, we can't know if all > build def of the dependency generate an artifact or not, we know only if a > new build was done and we add it in dependencies changes. -- 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: (MASSEMBLY-243) Support for patching
Support for patching Key: MASSEMBLY-243 URL: http://jira.codehaus.org/browse/MASSEMBLY-243 Project: Maven 2.x Assembly Plugin Issue Type: New Feature Affects Versions: 2.1 Reporter: Frank Cornelis What I'm still missing from Ant is the ability to apply patches to assemblies that you're creating via the maven-assembly-plugin. In our project we're using JBoss AS bundled as a ZIP. To create a final distribution of the product we unpack and then have to change quite some configuration files within the JBoss AS tree. The problem right now is that for every JBoss AS update we have to re-patch the configuration files manually. It would be great if the maven-assembly-plugin would have inherent support for patches. That way it's also more clear what configuration section you're changing exactly. See also: http://ant.apache.org/manual/CoreTasks/patch.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] Created: (MSHADE-2) Make prefix configurable in SimpleRelocator
Make prefix configurable in SimpleRelocator --- Key: MSHADE-2 URL: http://jira.codehaus.org/browse/MSHADE-2 Project: Maven 2.x Shade Plugin Issue Type: Improvement Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Currency SimpleRelocator prefixes class name with "hidden". This behaviour, while adeguate as default, should be configurable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-1466) Project name accepts blank spaces when edited in Project Summary > Members Tab > Edit Project
[ http://jira.codehaus.org/browse/CONTINUUM-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed CONTINUUM-1466. --- Resolution: Fixed svn rev 581703 > Project name accepts blank spaces when edited in Project Summary > Members > Tab > Edit Project > - > > Key: CONTINUUM-1466 > URL: http://jira.codehaus.org/browse/CONTINUUM-1466 > Project: Continuum > Issue Type: Bug > Components: Web - UI >Affects Versions: 1.1-beta-1, 1.1-beta-2, 1.1-beta-3 > Environment: firefox 2, ubuntu >Reporter: jan ancajas >Assignee: Olivier Lamy >Priority: Trivial > Fix For: 1.1-beta-4 > > > Steps: > 1. Login as admin > 2. Add a Maven Two Project with project group defined by pom > 3. In the group summary page, click the project group of the project you've > just added > 4. When the project group summary page is loaded, click on the Members tab > 5. In the Project Group Members page, click the Edit Project icon of the > project that you've just added > 6. Once in the Edit Project page, replace the project name with empty spaces > and click the Save button > 7. You will be redirected to the Project Information page, and you will see > that the project name is now 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] Commented: (MSHADE-2) Make prefix configurable in SimpleRelocator
[ http://jira.codehaus.org/browse/MSHADE-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108954 ] Paul Hammant commented on MSHADE-2: --- Would love it to be sophisticated : org.objectweb.asm.* goes to : org.myproject.asm.* for classes in that dir, and recursive. -ph > Make prefix configurable in SimpleRelocator > --- > > Key: MSHADE-2 > URL: http://jira.codehaus.org/browse/MSHADE-2 > Project: Maven 2.x Shade Plugin > Issue Type: Improvement >Reporter: Mauro Talevi >Assignee: Mauro Talevi >Priority: Minor > > Currency SimpleRelocator prefixes class name with "hidden". This behaviour, > while adeguate as default, should be configurable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1743) Sync blammo.sourceforge.net/repository
Sync blammo.sourceforge.net/repository -- Key: MAVENUPLOAD-1743 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1743 Project: maven-upload-requests Issue Type: Task Reporter: Wilfred Springer Attachments: com.agilejava.blammo.sh Please synchronize the blammo.sourceforge.net/repository with the central maven 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] Closed: (MSHADE-2) Make prefix configurable in SimpleRelocator
[ http://jira.codehaus.org/browse/MSHADE-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi closed MSHADE-2. - Resolution: Fixed Done. Shaded package configurable as org.codehaus.plexus.util org.shaded.plexus.util org.codehaus.plexus.util.xml.Xpp3Dom org.codehaus.plexus.util.xml.pull.* > Make prefix configurable in SimpleRelocator > --- > > Key: MSHADE-2 > URL: http://jira.codehaus.org/browse/MSHADE-2 > Project: Maven 2.x Shade Plugin > Issue Type: Improvement >Reporter: Mauro Talevi >Assignee: Mauro Talevi >Priority: Minor > > Currency SimpleRelocator prefixes class name with "hidden". This behaviour, > while adeguate as default, should be configurable. -- 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: (MSHADE-3) Add plugin site documentation
Add plugin site documentation - Key: MSHADE-3 URL: http://jira.codehaus.org/browse/MSHADE-3 Project: Maven 2.x Shade Plugin Issue Type: Task Reporter: Mauro Talevi Plugin is missing site docs. Document major features and test cases - taking ITs as example and deploy site. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPEAR-46) Unknown artifact type[java-source]
[
http://jira.codehaus.org/browse/MPEAR-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108962
]
Brian Topping commented on MPEAR-46:
Actually, it turns out this is the correct behavior. If your ear has a
dependency that is scoped appropriately, it should be included.
provided would also work around having the dependency without
including it.
On the other hand, if you do want to include it, the way to do so is documented
at http://maven.apache.org/plugins/maven-ear-plugin/introduction.html. In your
case, you would want to use:
{code}
org.apache.maven.plugins
maven-ear-plugin
{code}
> Unknown artifact type[java-source]
> ---
>
> Key: MPEAR-46
> URL: http://jira.codehaus.org/browse/MPEAR-46
> Project: Maven 1.x Ear Plugin
> Issue Type: Bug
> Environment: Windows
> Eclipse 3.1
>Reporter: Tom Bollwitt
>Priority: Trivial
> Fix For: 1.9.1
>
>
> When a POM (parent or dependency) includes java source jar dependencies they
> are not ignored and an error is thrown.
>
> mygroup
> artifact2
> 1.0
> java-source
>
> When running 'package' or ear:ear I am getting the following error:
> [INFO] [ear:generate-application-xml]
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Failed to initialize ear modules
> Embedded error: Unknown artifact type[java-source]
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to initialize
> ear modules
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> 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)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to
> initialize ear modules
> at
> org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:151)
> at
> org.apache.maven.plugin.ear.GenerateApplicationXmlMojo.execute(GenerateApplicationXmlMojo.java:110)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> ... 16 more
> Caused by: org.apache.maven.plugin.ear.UnknownArtifactTypeException: Unknown
> artifact type[java-source]
> at
> org.apache.maven.plugin.ear.ArtifactTypeMappingService.getStandardType(ArtifactTypeMappingService.java:153)
> at
> org.apache.maven.plugin.ear.EarModuleFactory.newEarModule(EarModuleFactory.java:60)
> at
> org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:144)
> ... 19 more
> [INFO]
>
> [INFO] Total time: 2 seconds
> [INFO] Finished at: Wed Aug 30 11:49:59 CDT 2006
> [INFO] Final Memory: 4M/7M
> I added test to the java-source dependency and was able to
> work around this issue. The scope is missleading and therefore the desired
> behavior would be to not require scoping the java-source dependency.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of t
[jira] Closed: (CONTINUUM-1487) should not be allowed to delete a build result that is still executing
[ http://jira.codehaus.org/browse/CONTINUUM-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed CONTINUUM-1487. --- Assignee: Olivier Lamy Resolution: Fixed add confirmation page before delete buildResult(s) (svn rev 581740) > should not be allowed to delete a build result that is still executing > -- > > Key: CONTINUUM-1487 > URL: http://jira.codehaus.org/browse/CONTINUUM-1487 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-beta-3 >Reporter: Brett Porter >Assignee: Olivier Lamy > Fix For: 1.1-beta-4 > > > note that deleting the build result from on the build result page also seems > to skip confirmation. All I did was hit the space bar... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1743) Sync blammo.sourceforge.net/repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1743. --- Assignee: Carlos Sanchez Resolution: Fixed > Sync blammo.sourceforge.net/repository > -- > > Key: MAVENUPLOAD-1743 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1743 > Project: maven-upload-requests > Issue Type: Task >Reporter: Wilfred Springer >Assignee: Carlos Sanchez > Attachments: com.agilejava.blammo.sh > > > Please synchronize the blammo.sourceforge.net/repository with the central > maven 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] Closed: (MAVENUPLOAD-1742) please upload rhino javascript engine modified by the Dojo team
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1742. --- Assignee: Carlos Sanchez Resolution: Fixed > please upload rhino javascript engine modified by the Dojo team > --- > > Key: MAVENUPLOAD-1742 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1742 > Project: maven-upload-requests > Issue Type: Improvement >Reporter: nicolas de loof >Assignee: Carlos Sanchez > > dojotoolkit use a customized rhino engine for javascript compression -- 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-1734) Timingframework 1.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108966 ] Carlos Sanchez commented on MAVENUPLOAD-1734: - unless the project is available under jdesktop.org the groupId should be net.java.dev.timingframework > Timingframework 1.0 > --- > > Key: MAVENUPLOAD-1734 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1734 > Project: maven-upload-requests > Issue Type: Task >Reporter: Wim Deblauwe > > The Timing Framework is a library for making Java animation and timing-based > control easier. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1739) New version of XINS for Maven2 repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1739. --- Assignee: Carlos Sanchez Resolution: Fixed > New version of XINS for Maven2 repository > - > > Key: MAVENUPLOAD-1739 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1739 > Project: maven-upload-requests > Issue Type: Task >Reporter: Anthony Goubard >Assignee: Carlos Sanchez > > Hi, > Here are new JAR file that I'd like to have uploaded in Maven: > http://xins.sourceforge.net/maven/xins-server-2.1.jar > http://xins.sourceforge.net/maven/xins-common-2.1.jar > http://xins.sourceforge.net/maven/xins-client-2.1.jar > http://xins.sourceforge.net/maven/logdoc-2.1.jar > Kind regards, > Anthony -- 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-1508) NullPointerException when adding an empty installation to a profile
NullPointerException when adding an empty installation to a profile
---
Key: CONTINUUM-1508
URL: http://jira.codehaus.org/browse/CONTINUUM-1508
Project: Continuum
Issue Type: Bug
Components: Web interface
Affects Versions: 1.1-beta-3
Reporter: George Gastaldi
Priority: Minor
Steps to reproduce the problem:
1) Install Continuum;
2) Go to "Profiles"
3) Create a new profile
4) Click the "Add" button (is empty, no installation defined).
BTW, Profiles must be enabled only when an installation exist
StackTrace:
{code}
java.lang.NullPointerException
at
org.apache.maven.continuum.profile.DefaultProfileService.addInstallationInProfile(DefaultProfileService.java:180)
at
org.apache.maven.continuum.web.action.admin.ProfileAction.addInstallation(ProfileAction.java:155)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:358)
at
com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:218)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:192)
at
org.codehaus.plexus.xwork.interceptor.PlexusReleaseComponentInterceptor.intercept(PlexusReleaseComponentInterceptor.java:69)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:175)
at
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
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:190)
at
org.apache.maven.continuum.web.interceptor.ForceContinuumConfigurationInterceptor.intercept(ForceContinuumConfigurationInterceptor.java:72)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
org.codehaus.plexus.redback.xwork.interceptor.PolicyEnforcementInterceptor.intercept(PolicyEnforcementInterceptor.java:118)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
org.codehaus.plexus.redback.xwork.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.java:159)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
org.codehaus.plexus.xwork.interceptor.ExceptionMappingInterceptor.intercept(ExceptionMappingInterceptor.java:58)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:175)
at
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
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:190)
at
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.webwork.interceptor.FileUploadInterceptor.intercept(FileUploadInterceptor.java:174)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
at
com.opensymphony.xwork.De
[jira] Commented: (MNG-3024) Missing artifact error text improvement
[ http://jira.codehaus.org/browse/MNG-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108971 ] Oleksandr Maksymchuk commented on MNG-3024: --- I also support putting command into one line as for Windows users '\' need to be stripped manually. > Missing artifact error text improvement > --- > > Key: MNG-3024 > URL: http://jira.codehaus.org/browse/MNG-3024 > Project: Maven 2 > Issue Type: Improvement > Components: Artifacts and Repositories >Affects Versions: 2.0.6 >Reporter: Patrick Lightbody >Assignee: Jason van Zyl >Priority: Minor > Fix For: 2.0.8 > > Attachments: screenshot-1.jpg > > > I love how when an artifact can't be found, a nice error explains how to > install it locally. This is a great technique for onboarding new maven users > who might otherwise be frustrated, thinking that they can't use things no in > the public repo. Kudos to whoever did this initial work. > Now I suggest you take it a step further by including instructions for > deploying the file to a personal repo. For example: > Caused by: Missing: > -- > 1) j2ssh:j2ssh-core:jar:0.2.9 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=j2ssh -DartifactId=j2ssh-core \ > -Dversion=0.2.9 -Dpackaging=jar -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=j2ssh -DartifactId=j2ssh-core \ > -Dversion=0.2.9 -Dpackaging=jar -Dfile=/path/to/file > -Durl=... -DrepositoryId=... > Path to dependency: > 1) com.hostedqa:hostedqa-anywhere-server:jar:1.7.4-SNAPSHOT > 2) j2ssh:j2ssh-core:jar:0.2.9 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1744) jTDS 1.2.2 Upload
jTDS 1.2.2 Upload - Key: MAVENUPLOAD-1744 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1744 Project: maven-upload-requests Issue Type: Bug Reporter: Dan Tran Latest JDBC Driver for SQL Server and Sybase Database Server from http://jtds.sourceforge.net -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3229) Active by default profile is ignored when another is specified explicitly.
Active by default profile is ignored when another is specified explicitly. --- Key: MNG-3229 URL: http://jira.codehaus.org/browse/MNG-3229 Project: Maven 2 Issue Type: Bug Components: Profiles Affects Versions: 2.0.7 Reporter: Oleksandr Maksymchuk When default profile is added its used only when there is no another profile specified to be used on command line via -P option. So in the pom containig: default true dev default profile is used only when running command without -P dev mvn but not used when running: mvn -P dev Expected: should be used in both variants as per doc. -- 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-1734) Timingframework 1.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108978 ] Wim Deblauwe commented on MAVENUPLOAD-1734: --- I have updated the groupId and re-uploaded the bundle (to the same location). > Timingframework 1.0 > --- > > Key: MAVENUPLOAD-1734 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1734 > Project: maven-upload-requests > Issue Type: Task >Reporter: Wim Deblauwe > > The Timing Framework is a library for making Java animation and timing-based > control easier. -- 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: (MWAR-104) handle zip dependencies in war plugin
[ http://jira.codehaus.org/browse/MWAR-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108979 ] Stephane Nicoll commented on MWAR-104: -- sure. Overlay will have now a targetPath parameter that will be ignored if the overlay is a war. > handle zip dependencies in war plugin > - > > Key: MWAR-104 > URL: http://jira.codehaus.org/browse/MWAR-104 > Project: Maven 2.x War Plugin > Issue Type: Improvement > Environment: all >Reporter: Olivier Lamy >Assignee: Stephane Nicoll > Fix For: 2.1-alpha-1 > > Attachments: foobar.zip, MWAR-104 > > > As MNG-1683 has been applied, the zip artifact must be handled in the war > 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
