[jira] Commented: (MJARSIGNER-21) jars signed using Java 7 have "invalid SHA1 signature"

[ https://jira.codehaus.org/browse/MJARSIGNER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=281458#comment-281458 ] Mike Calmus commented on MJARSIGNER-21: --- That takes care of the issue. Some documenta

[jira] Commented: (MJARSIGNER-21) jars signed using Java 7 have "invalid SHA1 signature"

[ https://jira.codehaus.org/browse/MJARSIGNER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=281450#comment-281450 ] Mike Calmus commented on MJARSIGNER-21: --- The applet is giving the following error whe

[jira] Created: (MJARSIGNER-21) jars signed using Java 7 have "invalid SHA1 signature"

Type: Bug Affects Versions: 1.2 Environment: Java 7, Maven 2.2.1 Reporter: Mike Calmus Priority: Critical Using the plugin with Java 6 works fine. When I use it with Java 7, my applet won't load because the SHA1 signatures are invalid. -- This message i

creating a small non-primary war

I am trying to create a non-primary war that includes an applet jar and its dependencies. This war is then merged into a larger war. When I try to do this, though I get an error from the Maven Install plugin indicating no primary artificat was created. The error returend is somewhat different depe

[jira] Reopened: (MINSTALL-80) Errors installing very minimal war

[ http://jira.codehaus.org/browse/MINSTALL-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Calmus reopened MINSTALL-80: - Please take a look at the additional information posted. This is still causing an issue for us

[jira] Commented: (MINSTALL-80) Errors installing very minimal war

[ http://jira.codehaus.org/browse/MINSTALL-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250824#action_250824 ] Mike Calmus commented on MINSTALL-80: - The attached pom was a simplified test cas

[jira] Commented: (MINSTALL-80) Errors installing very minimal war

[ http://jira.codehaus.org/browse/MINSTALL-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250825#action_250825 ] Mike Calmus commented on MINSTALL-80: - Here is the plugin piece that is

[jira] Created: (MINSTALL-80) Errors installing very minimal war

Versions: 2.3.1, 2.3, 2.2 Reporter: Mike Calmus Attachments: pom.xml When certain directories don't exist in a war project, install fails. The failure is somewhat different depending upon the maven-install-plugin version used. The included pom.xml illustrates the behavior

[jira] Reopened: (MWAR-243) Error when no artifacts copied to classes directory

[ http://jira.codehaus.org/browse/MWAR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Calmus reopened MWAR-243: -- The second pom attached was incorrect. The third illustrates the issue. > Error when no artifacts copied

[jira] Updated: (MWAR-243) Error when no artifacts copied to classes directory

[ http://jira.codehaus.org/browse/MWAR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Calmus updated MWAR-243: - Attachment: pom.xml This IS a bug. I removed a little too much from the first POM. This one shows it. > Er

[jira] Commented: (MWAR-244) Provide a mechanism for not including or having an empty webapp directory

[ http://jira.codehaus.org/browse/MWAR-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=246623#action_246623 ] Mike Calmus commented on MWAR-244: -- I do blame the parent pom. However, an empty webResrouces b

[jira] Updated: (MWAR-243) Error when no artifacts copied to classes directory

[ http://jira.codehaus.org/browse/MWAR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Calmus updated MWAR-243: - Attachment: pom.xml You can see it even with this very simple pom.xml. > Error when no artifacts copied

[jira] Commented: (MWAR-244) Provide a mechanism for not including or having an empty webapp directory

[ http://jira.codehaus.org/browse/MWAR-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=246612#action_246612 ] Mike Calmus commented on MWAR-244: -- This is occurring because a webResources block is set up

[jira] Updated: (MWAR-243) Error when no artifacts copied to classes directory

[ http://jira.codehaus.org/browse/MWAR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Calmus updated MWAR-243: - Attachment: pom.xml Running install with the attached pom.xml in an otherwise empty directory will demonstrate

[jira] Created: (MWAR-244) Provide a mechanism for not including or having an empty webapp directory

Issue Type: Improvement Affects Versions: 2.1.1 Reporter: Mike Calmus Priority: Minor If the configured (or default) webapp directory does not exist, the plugin throws an IllegalArgumentException saying the directory does not exist. There should be a way to proceed

[jira] Created: (MWAR-243) Error when no artifacts copied to classes directory

Reporter: Mike Calmus When no classes are created or copied to the classes directory the plugin blows up saying the directory does not exist: [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error installing artifact: File D:\mydir\target\classes does not exist

[jira] Commented: (MCOMPILER-59) Compilation fails on warning messages from javac (Java 6)

[ http://jira.codehaus.org/browse/MCOMPILER-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170845#action_170845 ] Mike Calmus commented on MCOMPILER-59: -- Should this be working now in Maven 2.1.0? I