[jira] (MDEP-90) stripVersion flag not functional
[
https://jira.codehaus.org/browse/MDEP-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298353#comment-298353
]
Guillaume Yziquel commented on MDEP-90:
---
This missing option in newer maven-dependency-plugin would be nice to have back
again: Unpacking resources is nice enough, but patching these resources with
maven-patch-plugin would definitely be easier if the patch could not depend on
the version... hence the usefulness of stripping versions.
> stripVersion flag not functional
>
>
> Key: MDEP-90
> URL: https://jira.codehaus.org/browse/MDEP-90
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: copy-dependencies
>Affects Versions: 2.0-alpha-2
>Reporter: Pavel Halas
>Assignee: Brian Fox
> Attachments: pom.xml
>
>
> Since {{2.0-alpha-2}} to {{2.0-alpha-4}} this option is not functional -- the
> version is a part of the filename. The {{2.0-alpha-1}} behaves the expected
> way.
--
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] (MDEPLOY-150) deploy-file does not use repository in the same way as deploy
Kai Hofmann created MDEPLOY-150:
---
Summary: deploy-file does not use repository in the same
way as deploy
Key: MDEPLOY-150
URL: https://jira.codehaus.org/browse/MDEPLOY-150
Project: Maven 2.x and 3.x Deploy Plugin
Issue Type: Bug
Components: deploy:deploy-file
Affects Versions: 2.7
Environment: Windows 7, Maven 2.2.1
Reporter: Kai Hofmann
Priority: Critical
We use an own lifecycle here which creates a zip file instead of a jar file.
So we use
org.apache.maven.plugins:maven-install-plugin:install,org.apache.maven.plugins:maven-install-plugin:install-file
which installs the zip file correctly.
Additionally I now wanted to also allow deploying of this zip file to nexus by:
org.apache.maven.plugins:maven-deploy-plugin:deploy,org.apache.maven.plugins:maven-deploy-plugin:deploy-file
in the pom I have then:
${project.build.directory}/${project.artifactId}-${project.version}.zip
org.apache.maven.plugins
maven-install-plugin
2.3.1
install-service-zip
install-file
org.apache.maven.plugins
maven-deploy-plugin
2.7
deploy-service-zip
deploy-file
as well as settings for the repositories within the maven settings.xml.
As said the install process works perfectly, but I have trouble with the
deploy-file.
When working without the deploy-file (only with the deploy) everything also
works correct for the deployment.
After adding the deploy-file as shown above I come into trouble, because beside
the property the deploy-plugin requests for the required parameter.
I wonder about this, because I assumed that the parameter will come from
the choosen repository (release vs snapshot) settings?
When I set the as property beside the property, then I can deploy
a snapshot.
But to deploying snapshot/release this will not work.
In deploy the url parameter is implicitly correctly choosen, why not in
deploy-file? this would make the url parameter optional.
So I see this as a bug/feature, because when deploy works in this way, then
deploy-file should work analogous. Or have I missed something here?
--
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] (MNG-5283) Pom import doesn't work with plugin snapshot
Pascal Le Goff created MNG-5283: --- Summary: Pom import doesn't work with plugin snapshot Key: MNG-5283 URL: https://jira.codehaus.org/browse/MNG-5283 Project: Maven 2 & 3 Issue Type: Bug Components: Profiles Affects Versions: 2.2.x (to be reviewed) Environment: windows Reporter: Pascal Le Goff To develop one plugin maven in few branch (dev0, dev1) I have some dependencies in dev0 and other dependencies in dev1 I have a super pom dev-snapshot with profiles (profile-dev0, profile-dev1) for each profile, I have a dependencymanagment with import pom file com.pom dynamic-parent 1.0.000.000-SNAPSHOT pom profile-dev0 true com.pom dynamic-profile pom dev0-SNAPSHOT import profile-dev1 com.pom dynamic-profile pom dev1-SNAPSHOT import by default, profile-dev0 is activate in the pom com.pom:dynamic-profile:pom:dev0-SNAPSHOT , I have dependencies version for dev0 and in com.pom:dynamic-profile:pom:dev0-SNAPSHOT, I have dependencies for dev1 When I compile mvn clean deploy -Pprofile-dev0, my plugin is deploy on nexus repository if I use my plugin maven on an other component, the pom com.pom:dynamic-profile:pom:dev0-SNAPSHOT my parent is com.pom dynamic-parent 1.0.000.000-SNAPSHOT my;groupid my.plugin if I do a clean install -P!profile-dev0,profile-dev1 it download the parent com.pom:dynamic-parent:1.0.000.000-SNAPSHOT but not the import file [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: com.pom:dynamic-profile Reason: POM 'com.pom:dynamic-profile' not found in repository: Unable to download the artifact from any repository com.pom:dynamic-profile:pom:dev0-SNAPSHOT from the specified remote repositories: reference-central (http://repository.all.alcatel-lucent.com/nexus/content/groups/reference-cache/) for project com.pom:dynamic-profile Thanks Pascal -- 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] (MDEP-98) The source must not be a directory
[ https://jira.codehaus.org/browse/MDEP-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298409#comment-298409 ] Emmanuel Lécharny commented on MDEP-98: --- get ready for the 5 years anniversary of this bug !!! Ok, seriously, what you guys need to get it fixed ? > The source must not be a directory > -- > > Key: MDEP-98 > URL: https://jira.codehaus.org/browse/MDEP-98 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: unpack-dependencies >Affects Versions: 2.0-alpha-4 > Environment: Windows XP Professional SP2 > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03) > Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing) >Reporter: Pablo Muñiz >Assignee: Brian Fox > Attachments: MDEP-98-ITs.patch, > mdep98-testcase-parent-with-surefire.zip, mdep98-testcase-parent.zip > > > Using maven-dependency-plugin in a multimodule project inside a module wich > has a dependency with another module in the same project the next error > ocurrs : > org.codehaus.plexus.archiver.ArchiverException: The source must not be a > directory. > at > org.codehaus.plexus.archiver.AbstractUnArchiver.validate(AbstractUnArchiver.java:98) > at > org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:84) > at > org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:232) > at > org.apache.maven.plugin.dependency.UnpackDependenciesMojo.execute(UnpackDependenciesMojo.java:72) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > 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) > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error unpacking file: > c:\D\desarrollo\proyectos\plataforma\platform-core\target\classes to: > c:\D\desarrollo\proyectos\plataforma\platform-bundle\platform-bundle-jar\target\classes > org.codehaus.plexus.archiver.ArchiverException: The source must not be a > directory. > Project structure is as follows: > plataforma > - platform-core > - platform-bundle > - platform-bundle-jar > - platform-bundle-src > and the error happens on executing any goal from parent pom. > maven-dependency-plugin seems to receive a reference to target/classes > directory for platform-core dependency instead of the URL to my local > repository where platform-core is located. -- 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] (MDEP-98) The source must not be a directory
[ https://jira.codehaus.org/browse/MDEP-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298411#comment-298411 ] Nathan Wells commented on MDEP-98: -- My solution: stop using Maven. > The source must not be a directory > -- > > Key: MDEP-98 > URL: https://jira.codehaus.org/browse/MDEP-98 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: unpack-dependencies >Affects Versions: 2.0-alpha-4 > Environment: Windows XP Professional SP2 > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03) > Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing) >Reporter: Pablo Muñiz >Assignee: Brian Fox > Attachments: MDEP-98-ITs.patch, > mdep98-testcase-parent-with-surefire.zip, mdep98-testcase-parent.zip > > > Using maven-dependency-plugin in a multimodule project inside a module wich > has a dependency with another module in the same project the next error > ocurrs : > org.codehaus.plexus.archiver.ArchiverException: The source must not be a > directory. > at > org.codehaus.plexus.archiver.AbstractUnArchiver.validate(AbstractUnArchiver.java:98) > at > org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:84) > at > org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:232) > at > org.apache.maven.plugin.dependency.UnpackDependenciesMojo.execute(UnpackDependenciesMojo.java:72) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > 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) > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error unpacking file: > c:\D\desarrollo\proyectos\plataforma\platform-core\target\classes to: > c:\D\desarrollo\proyectos\plataforma\platform-bundle\platform-bundle-jar\target\classes > org.codehaus.plexus.archiver.ArchiverException: The source must not be a > directory. > Project structure is as follows: > plataforma > - platform-core > - platform-bundle > - platform-bundle-jar > - platform-bundle-src > and the error happens on executing any goal from parent pom. > maven-dependency-plugin seems to receive a reference to target/classes > directory for platform-core dependency instead of the URL to my local > repository where platform-core is located. -- 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] (MSITE-642) An API incompatibility was encountered while executing org.apache.maven.plugins:maven-site-plugin:3.1:site: java.lang.ExceptionInInitializerError: null
[ https://jira.codehaus.org/browse/MSITE-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298421#comment-298421 ] Dennis Lundberg commented on MSITE-642: --- Hi David, Because of the bad decision by JBoss to include their own (slightly modified) copy of commons-logging in JBoss 4, adding newer versions of commons-logging in an application deployed to a JBoss 4 instance can lead to problems like this. The reason is that you end up with two incompatible versions of commons-logging (1.0.x and 1.1.x) in your applications classpath. There are two possible workarounds: 1. Use a newer version of JBoss that doesn't bundle commons-logging in a classloader that is shared with the installed applications. Sorry, but I don't know which version. 2. Try to replace the version of commons-logging that is included in JBoss. I haven't tried this but it might work. Use version 1.1.1 if possible. > An API incompatibility was encountered while executing > org.apache.maven.plugins:maven-site-plugin:3.1:site: > java.lang.ExceptionInInitializerError: null > --- > > Key: MSITE-642 > URL: https://jira.codehaus.org/browse/MSITE-642 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug >Affects Versions: 3.1 > Environment: Using Maven 3.0.4 >Reporter: David Pilato > Attachments: mavensite3.log, pom.xml, pom.xml > > > After updating maven site version from 3.0 to 3.1, I get the following error > when running mvn clean site on my project. > As far as I can see, the error come from : > Caused by: org.apache.commons.logging.LogConfigurationException: Invalid > class loader hierarchy. You have more than one version of > 'org.apache.commons.logging.Log' visible, which is not allowed. > at > org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:385) > ... 61 more > Full log is attached. > I added my parent pom.xml file and the pom.xml file for the first module > (which fails). > Hope this help. > David. -- 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] (MPIR-244) With Maven 3, "Dependency Repository Locations" in dependencies report shows my local repository manager id and url instead of public repository info
[ https://jira.codehaus.org/browse/MPIR-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MPIR-244. -- Resolution: Fixed Fix Version/s: 2.4.1 Assignee: Herve Boutemy fixed in [r1336881|http://svn.apache.org/viewvc?rev=1336881] Starting with Maven 3.0.3, the report will show the original repositories information, instead of the mirror. We can't do anything with Maven 3.0-alpha to 3.0.2 > With Maven 3, "Dependency Repository Locations" in dependencies report shows > my local repository manager id and url instead of public repository info > - > > Key: MPIR-244 > URL: https://jira.codehaus.org/browse/MPIR-244 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: dependencies >Affects Versions: 2.4 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 2.4.1 > > > With Maven 2, "Dependency Repository Locations" reports "central" references, > for example, but with maven 3, my local repository manager is shown, with it > "http://localhost:8081/xxx"; url > Added a test-case in > [r1335705|http://svn.apache.org/viewvc?rev=1335705&view=rev] -- 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] (MPH-88) [PATCH] Migration from obsolete plexus-maven-plugin to plexus-containers-component-metadata
[ https://jira.codehaus.org/browse/MPH-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MPH-88. Resolution: Fixed Fix Version/s: 2.2 Assignee: Herve Boutemy done in r1336897 thank you > [PATCH] Migration from obsolete plexus-maven-plugin to > plexus-containers-component-metadata > --- > > Key: MPH-88 > URL: https://jira.codehaus.org/browse/MPH-88 > Project: Maven 2.x Help Plugin > Issue Type: Bug >Affects Versions: 2.1.1 > Environment: fedora-rawhide >Reporter: Jaromír Cápík >Assignee: Herve Boutemy > Fix For: 2.2 > > Attachments: maven-help-plugin-migration-to-component-metadata.patch > > > The attached patch changes the pom.xml so that it requests > plexus-component-metadata instead of the obsolete plexus-maven-plugin. The > generated metadata can have swapped entries, but all of them are present. -- 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] (MPH-87) help:effective-pom uses platform encoding and garbles non-ascii characters, emits invalid XML
[
https://jira.codehaus.org/browse/MPH-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298434#comment-298434
]
Herve Boutemy commented on MPH-87:
--
yes, that's expected
if you want to use the result, you need to use output parameter to let the
plugin write the content directly to a file, with encoding support
{noformat}mvn -Doutput=effective.xml help:effective-pom{noformat}
> help:effective-pom uses platform encoding and garbles non-ascii characters,
> emits invalid XML
> -
>
> Key: MPH-87
> URL: https://jira.codehaus.org/browse/MPH-87
> Project: Maven 2.x Help Plugin
> Issue Type: Bug
>Affects Versions: 2.1.1
> Environment: Windows, MacOSX, Linux, Maven 3.0.4
>Reporter: Mirko Friedenhagen
> Attachments: mfriedenhagen-invalidpom-MPH-87-0-g42a5c31.zip
>
>
> As stated in http://www.w3.org/TR/REC-xml/#sec-guessing-no-ext-info XML files
> without a BOM and without a XML encoding declaration should read the XML as
> UTF-8.
> {{help:effective-pom}} does use the platform encoding for writing the
> effective-pom without emitting an appropriate XML encoding declaration in the
> resulting XML file.
> I have created a small sample project (available at
> https://github.com/mfriedenhagen/invalidpom, attached as ZIP) which will
> reproduce the issue.
> While the parent pom
> (https://raw.github.com/mfriedenhagen/invalidpom/master/pom.xml) has a XML
> encoding declaration,
> https://raw.github.com/mfriedenhagen/invalidpom/master/child-invalid/pom.xml
> has none.
> Now running:
> {code}
> mvn -s settings.xml -gs settings.xml clean validate
> {code}
> will produce an invalid character for the developer name "Jörg" in
> {{child-invalid}}.
> Two workarounds are:
> * to include a XML encoding declaration as done in {{child-valid}}.
> * to use {{JAVA_TOOL_OPTIONS}} on Windows as stated in
> http://stackoverflow.com/a/623036/49132
> * to use {{MAVEN_OPTS=-Dfile.encoding=utf-8 mvn -s settings.xml -gs
> settings.xml clean validate}}.
> Nonetheless I consider this a Major bug, as it clearly violates the
> recommendations of W3C.
--
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] (MPIR-245) blacklisted column in dependencies location is rendered without header
Herve Boutemy created MPIR-245: -- Summary: blacklisted column in dependencies location is rendered without header Key: MPIR-245 URL: https://jira.codehaus.org/browse/MPIR-245 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Components: dependencies Affects Versions: 2.4 Reporter: Herve Boutemy Priority: Trivial if no repository is blacklisted, the header disappears but not the content of the column -- 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] (MPIR-245) blacklisted column in dependencies location is rendered without header
[ https://jira.codehaus.org/browse/MPIR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MPIR-245. -- Resolution: Fixed Fix Version/s: 2.5 Assignee: Herve Boutemy fixed in [r1336928|http://svn.apache.org/viewvc?rev=1336928&view=rev] > blacklisted column in dependencies location is rendered without header > -- > > Key: MPIR-245 > URL: https://jira.codehaus.org/browse/MPIR-245 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: dependencies >Affects Versions: 2.4 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Trivial > Fix For: 2.5 > > > if no repository is blacklisted, the header disappears but not the content of > the column -- 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
