[jira] Commented: (MINVOKER-107) mvn deploy of SNAPSHOT failed with maven3 when invoker:run look for current build dependency
[
https://jira.codehaus.org/browse/MINVOKER-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284809#comment-284809
]
Robert Scholte commented on MINVOKER-107:
-
Tony, I've tried to reproduce this issue and somehow I can't anymore. Are you
still having this issue?
> mvn deploy of SNAPSHOT failed with maven3 when invoker:run look for current
> build dependency
>
>
> Key: MINVOKER-107
> URL: https://jira.codehaus.org/browse/MINVOKER-107
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.5
> Environment: Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200)
> Java version: 1.6.0_22
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.32-25-generic-pae" arch: "i386" Family: "unix"
>Reporter: ludovic
> Attachments: MINVOKER-107.diff
>
>
> When I build
> http://code.google.com/p/mycila/source/browse/mycila-testing/trunk?r=1448 on
> revision 1448, the build failed. r1449 is a workaround.
> the maven command is : mvn clean deploy
> the build failed when running plugin invoker:run with maven3 BUT succeed with
> maven2
> the failure is due of a missing artifact in the its local repository, the
> searched version is a SNAPSHOT, the present version is a timestamped SNAPSHOT
> the dependency com.mycila.testing:mycila-testing-api:jar:2.6-SNAPSHOT is not
> found because the invoker:install copy the SNAPSHOT with the timestamp during
> deploy. And then after during the test, the dependency could not be found.
> The reason is because maven3 always deploy using a timestamped version.
> @see
> https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-NonuniqueSnapshotDeployments
> ! workaround
> remove
> ${project.build.directory}/local-repo
> from the invoker configuration
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MPOM-34) I cannot compile mixing modules and dependencies
I cannot compile mixing modules and dependencies
Key: MPOM-34
URL: https://issues.apache.org/jira/browse/MPOM-34
Project: Maven POMs
Issue Type: Bug
Components: maven
Environment: maven 3.0.3
Reporter: Luca Stancapiano
I have three two simple projects:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
prova
Mioframework
0.4.0-SNAPSHOT
../pom.xml
4.0.0
my-mioprogetto
Mio progetto
${project.groupId}
my-mioprogetto2
${project.version}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
prova
Mioframework
0.4.0-SNAPSHOT
../pom.xml
4.0.0
my-mioprogetto2
Mio progetto 2
and one parent project:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
prova
Mioframework
0.4.0-SNAPSHOT
Mioframework
pom
mioprogetto
mioprogetto2
mioprogetto as mioprogetto2 as dependency. Mioframework has the two projects as
modules.
If I compile mioframework I have no problems.
If I compile only mioprogetto2 I have no problems.
If I compile only mioprogetto I have problems because the dependency is not
matched. Here the error:
[ERROR] Failed to execute goal on project my-mioprogetto: Could not resolve
dependencies for project prova:my-mioprogetto:jar:0.4.0-SNAPSHOT: Could not
find artifact prova:my-mioprogetto2:jar:0.4.0-SNAPSHOT in myrepo-xxx
(http://repository.x) -> [Help 1]
I attach the complete example test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MPOM-34) I cannot compile mixing modules and dependencies
[
https://issues.apache.org/jira/browse/MPOM-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Stancapiano updated MPOM-34:
-
Attachment: exampletest.zip
This zip file contains the three projects descrived before
> I cannot compile mixing modules and dependencies
>
>
> Key: MPOM-34
> URL: https://issues.apache.org/jira/browse/MPOM-34
> Project: Maven POMs
> Issue Type: Bug
> Components: maven
> Environment: maven 3.0.3
>Reporter: Luca Stancapiano
> Attachments: exampletest.zip
>
>
> I have three two simple projects:
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
>
> prova
> Mioframework
> 0.4.0-SNAPSHOT
> ../pom.xml
>
> 4.0.0
> my-mioprogetto
> Mio progetto
>
>
>
> ${project.groupId}
> my-mioprogetto2
> ${project.version}
>
>
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
>
> prova
> Mioframework
> 0.4.0-SNAPSHOT
> ../pom.xml
>
> 4.0.0
> my-mioprogetto2
> Mio progetto 2
>
> and one parent project:
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
> prova
> Mioframework
> 0.4.0-SNAPSHOT
> Mioframework
> pom
>
> mioprogetto
> mioprogetto2
>
>
> mioprogetto as mioprogetto2 as dependency. Mioframework has the two projects
> as modules.
> If I compile mioframework I have no problems.
> If I compile only mioprogetto2 I have no problems.
> If I compile only mioprogetto I have problems because the dependency is not
> matched. Here the error:
> [ERROR] Failed to execute goal on project my-mioprogetto: Could not resolve
> dependencies for project prova:my-mioprogetto:jar:0.4.0-SNAPSHOT: Could not
> find artifact prova:my-mioprogetto2:jar:0.4.0-SNAPSHOT in myrepo-xxx
> (http://repository.x) -> [Help 1]
> I attach the complete example test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MANTTASKS-175) Dependencies ignoring user defined repo location and reverting to central
[
https://jira.codehaus.org/browse/MANTTASKS-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284818#comment-284818
]
Alexander Lehmann commented on MANTTASKS-175:
-
I noticed a similar problem when using the maven-ant task for
jbehave-distribution, this fails to resolve artifacts on alternate repositories.
It turns out that it works if the pom task loads the settings, but it doesn't
if the dependencies task loads the settings.
(the same pom.xml works when using maven however).
> Dependencies ignoring user defined repo location and reverting to central
> -
>
> Key: MANTTASKS-175
> URL: https://jira.codehaus.org/browse/MANTTASKS-175
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Components: dependencies task
>Affects Versions: 2.1.0
> Environment: Windows XP
>Reporter: Paul WIlliams
> Attachments: wagonManagerInit.patch
>
>
> I have a very simple dependencies declaration:
> {code:xml} settingsFile="${app.mavenSettings}">
> version="2.0.0"/>
> {code}
> I have 2 mirrors set up:
> {code:xml}
>
> all_mirror
> Nexus All
> http://maven-proxy.mycompany.com/content/groups/all
> *,!central
>
>
> central_mirror
> Nexus Releases
>
> http://maven-proxy.mycompany.com/content/groups/public
> central
>
> {code}
> When I instruct Maven to retreive the dependency it gets the pom file
> correctly, which contains a 2nd dependency, which is retrieved. These are
> both retrieved from the correct repo. But the 2nd pom then defines another
> dependency. But this 3rd dependency is searched for at central, where it
> doesnt exist (all artifacts are internal libraries).
> {noformat}
> Downloading: com/mycompany/myartifact1/version1/artifact1-version1.pom from
> repository central_mirror at http://mycompany.com/content/groups/public
> Transferring 4K from central_mirror
> Downloading: com/mycompany/myartifact2/version2/artifact2-version2.pom from
> repository central_mirror at http://mycompany.com/content/groups/public
> Transferring 24K from central_mirror
> Downloading: com/mycompany/myartifact3/version3/artifact3-version3.pom from
> repository central at http://repo1.maven.org/maven2
> Error transferring file: Connection timed out: connect
> {noformat}
> So the first 2 are resolved and d/loaded fine, but the 3rd suddenly reverts
> to looking in central, when it is present and correct in the central_mirror
> repo.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSKINS-15) With sidebar and no topbar external links should be rendered as menu
[
https://jira.codehaus.org/browse/MSKINS-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284831#comment-284831
]
Simone Tripodi commented on MSKINS-15:
--
thanks a lot for your patch Mirko! it has bee applied on {{trunk}}, see
[r1210036|https://svn.apache.org/viewvc?view=revision&revision=1210036].
Thanks again, very appreciated!
> With sidebar and no topbar external links should be rendered as menu
>
>
> Key: MSKINS-15
> URL: https://jira.codehaus.org/browse/MSKINS-15
> Project: Maven Skins
> Issue Type: Improvement
> Components: Fluido Skin
>Affects Versions: fluido-1.0, fluido-1.1
> Environment: {code}
> mvn --version
> Apache Maven 3.0.4 (r1209000; 2011-12-01 09:49:38+0100)
> Maven home: /usr/local/Cellar/maven/current/libexec
> Java version: 1.6.0_29, vendor: Apple Inc.
> Java home:
> /Library/Java/JavaVirtualMachines/1.6.0_29-b11-402.jdk/Contents/Home
> Default locale: de_DE, platform encoding: MacRoman
> OS name: "mac os x", version: "10.7.2", arch: "x86_64", family: "mac"
> {code}
>Reporter: Mirko Friedenhagen
> Attachments: enable-external-links-for-sidebar-when-no-topbar.patch
>
>
> External links specified in {{//project/body/links}} of the {{site.xml}} are
> only rendered as dropdown menu when the topbar is enabled.
> When only the sidebar is enabled these links are missing completely. I have
> attached a patch against revision 1206640 of
> http://svn.apache.org/repos/asf/maven/skins/trunk/maven-fluido-skin, which
> will render these links as additional menu in the sidebar when
> {{topbarEnabled==false}} and {{sidebarEnabled==true}}.
> Example output might be found at http://mojo.codehaus.org/fluido-preview/ for
> the ckjm-maven-plugin.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPLUGIN-39) adding package-info.java breaks build
[
https://jira.codehaus.org/browse/MPLUGIN-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MPLUGIN-39:
-
Description:
As soon as I add a package-info.java file to the package of my mojo, the build
breaks with the following output:
{noformat}[INFO] [plugin:descriptor]
[INFO] Using 2 extractors.
[INFO] Applying extractor for language: java
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] 0
[INFO]
[DEBUG] Trace
java.lang.ArrayIndexOutOfBoundsException: 0
at
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.getJavaClass(JavaMojoDescriptorExtractor.java:534)
at
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:553)
at
org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:84)
at
org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:135)
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.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
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:280)
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]
[INFO] Total time: 2 seconds
[INFO] Finished at: Wed Oct 17 11:48:52 CEST 2007
[INFO] Final Memory: 4M/1016M
[INFO]
{noformat}
was:
As soon as I add a package-info.java file to the package of my mojo, the build
breaks with the following output:
[INFO] [plugin:descriptor]
[INFO] Using 2 extractors.
[INFO] Applying extractor for language: java
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] 0
[INFO]
[DEBUG] Trace
java.lang.ArrayIndexOutOfBoundsException: 0
at
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.getJavaClass(JavaMojoDescriptorExtractor.java:534)
at
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:553)
at
org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:84)
at
org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:135)
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.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
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:
