[jira] (MASSEMBLY-449) Permissions on directories in a zipped archive incorrect
[
https://jira.codehaus.org/browse/MASSEMBLY-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286810#comment-286810
]
Silvestrov Ilya commented on MASSEMBLY-449:
---
This problem still exist for 2.2.2 version.
@Andreas, thanks for you workaround, it solves a problem.
> Permissions on directories in a zipped archive incorrect
>
>
> Key: MASSEMBLY-449
> URL: https://jira.codehaus.org/browse/MASSEMBLY-449
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2-beta-4
>Reporter: James Kavanagh
>
> Using the following assembly plugin:
> {code:xml}
>
> target-packaged
>
> zip
>
> false
>
>
>
> *:core-env
>
>
> env
> false
> true
>
>
>
>
> *:data-bridge
>
>
> target
> false
> true
>
>
>
>
> *:web
>
>
> web
> false
> true
>
>
>
>
> {code}
> When unzipping the result on a Linux host all the directory permissions have
> been set to 777.
> If I revert the plugin version to 2.2-beta-3 the issue goes away.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2502) mvn package does not work on J2EE multi module build
[
http://jira.codehaus.org/browse/MNG-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Silvestrov Ilya updated MNG-2502:
-
Attachment: maven_multimodule_ejb.zip
A simple test case attached.
When second/pom.xml has
${groupId}
first
${version}
ejb
it works.
With ejb-client it fails.
C:\Ilya\test_projects\maven_multimodule_ejb\second>mvn -v
Maven version: 2.0.9
Java version: 1.5.0_10
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> mvn package does not work on J2EE multi module build
>
>
> Key: MNG-2502
> URL: http://jira.codehaus.org/browse/MNG-2502
> Project: Maven 2
> Issue Type: Bug
> Components: Reactor and workspace
>Affects Versions: 2.0.4
> Environment: Linux, J2SE 1.4
>Reporter: Heinrich Nirschl
> Fix For: 2.0.x
>
> Attachments: maven_multimodule_ejb.zip
>
>
> In a multi module build consisting of an ejb.jar (with an ejb-client.jar), a
> war, and an ear where the war depends on the ejb-client.jar and the ear
> depends on the ejb.jar and the war, a reactor build with
> mvn package
> fails. The war build tries to download the ejb-client.jar from the repository
> instead of using the just built version.
> If I first run 'mvn install' in the ejb module the following multi module
> 'mvn package' succeeds.
> This issue causes also problems for the realease plugin since the sub build
> fails.
--
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: (MIDEA-75) mvn idea:idea fails with StringIndexOutOfBoundsException (toRelative method) when adding resource to base project
mvn idea:idea fails with StringIndexOutOfBoundsException (toRelative method)
when adding resource to base project
-
Key: MIDEA-75
URL: http://jira.codehaus.org/browse/MIDEA-75
Project: Maven 2.x Idea Plugin
Issue Type: Bug
Affects Versions: 2.0
Reporter: Silvestrov Ilya
Attachments: ideaPluginBug.zip
I want a base project to handle special resource which is located in not
default location.
Example: I want all my projects to pack file history.txt located in project
basedir into jar.
So, this resource is mentioned in parent project:
${basedir}
history.txt
When I package child project it works well. But when I try to run idea:idea (or
idea:module) it fails with following stacktrace:
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1444)
at java.lang.String.substring(String.java:1411)
at
org.apache.maven.plugin.idea.AbstractIdeaMojo.toRelative(AbstractIdeaMojo.java:217)
at
org.apache.maven.plugin.idea.IdeaModuleMojo.getModuleFileUrl(IdeaModuleMojo.java:777)
at
org.apache.maven.plugin.idea.IdeaModuleMojo.getModuleFileUrl(IdeaModuleMojo.java:782)
at
org.apache.maven.plugin.idea.IdeaModuleMojo.addSourceFolder(IdeaModuleMojo.java:797)
at
org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteModule(IdeaModuleMojo.java:278)
at
org.apache.maven.plugin.idea.IdeaMojo.rewriteModule(IdeaMojo.java:205)
at org.apache.maven.plugin.idea.IdeaMojo.execute(IdeaMojo.java:185)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
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:324)
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)
parent and child project examples are attached.
--
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
