[jira] (MNG-5545) NoClassDefFoundError: org/sonatype/aether/resolution/ArtifactResolutionException
[ https://jira.codehaus.org/browse/MNG-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=337167#comment-337167 ] Sascha Vujevic commented on MNG-5545: - Thank you for the reply, but i think this is not a satisfying answer. I have looked at the maven-dependency-plugin, but i don't understand, why the plugin is not using the org.sonatype.aether of the plugin.xml ? It is searching the org.eclipse.aether of the maven installation instead. How does this mechanism work ? Sorry for the further question and thank you for your patience. NoClassDefFoundError: org/sonatype/aether/resolution/ArtifactResolutionException Key: MNG-5545 URL: https://jira.codehaus.org/browse/MNG-5545 Project: Maven 2 3 Issue Type: Bug Components: Dependencies, Plugin API, POM Affects Versions: 3.1.0 Environment: Windows XP Reporter: Sascha Vujevic Assignee: Robert Scholte Attachments: build.log, examplemojo.zip, mojocaller.zip Hello maven-developers, i hope this is the right tracker. I am implementing a mojo which uses classes from org.sonatype.aether. With maven 3.0.x the build succeeds, with maven 3.1.0 it breaks with error shown in the log-file. My question is, why the maven-build uses the org.eclipse.aether (still milestone) from the maven-installation (where org.sonatype.aether is not included) instead of useing it from the pluging.xml. The parameter @requiresDependencyResolution runtime seems not to work. I have attached the log-file and 2 projects, examplemojo is the mojo and mojocaller is the caller. Just install examplemojo and call mvn call package on mojocaller. Thank you for your help. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-69) REGRESSION: reporting section titles are not enough visible (was better in previous version)
[ https://jira.codehaus.org/browse/MSKINS-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSKINS-69: - Fix Version/s: (was: fluido-1.3.1) REGRESSION: reporting section titles are not enough visible (was better in previous version) Key: MSKINS-69 URL: https://jira.codehaus.org/browse/MSKINS-69 Project: Maven Skins Issue Type: Bug Components: Fluido Skin Affects Versions: fluido-1.3.0 Reporter: Herve Boutemy Priority: Critical Attachments: fluido-1.2.png, fluido-1.3.0.png see attachements to compare Fluido 1.2 and Fluido 1.3.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (ARCHETYPE-453) problem with ${package} in java file
[
https://jira.codehaus.org/browse/ARCHETYPE-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=337200#comment-337200
]
prabal kumar commented on ARCHETYPE-453:
I further looked into this problem and came to know that template is created by
appending escaping variables at the top of the java file. For example,
${package} is being converted to ${symbol_dollar}{package}. Hence, it is not
being replaced at the time of end project creation. If I manually change
${symbol_dollar}{package} to ${package} in the target folder, the value is
being replaced successfully.
How to avoid this situation? How can I make sure that template is not appending
these extra lines at the top?
problem with ${package} in java file
Key: ARCHETYPE-453
URL: https://jira.codehaus.org/browse/ARCHETYPE-453
Project: Maven Archetype
Issue Type: Bug
Reporter: prabal kumar
I am using ${package} in my java file and it is not being replaced after
using mvn archetype:generate -DarchetypeCatalog=local command and providing
all the properties. However, __packageInPathInfo__ is creating correct
desired directory structure.
Am I missing something?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (ARCHETYPE-453) problem with ${package} in java file
[
https://jira.codehaus.org/browse/ARCHETYPE-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
prabal kumar updated ARCHETYPE-453:
---
Description:
I am using ${package} in my java file and it is not being replaced after using
mvn archetype:generate -DarchetypeCatalog=local command and providing all the
properties. However, __packageInPathFormat__ is creating correct desired
directory structure.
Am I missing something?
was:
I am using ${package} in my java file and it is not being replaced after using
mvn archetype:generate -DarchetypeCatalog=local command and providing all the
properties. However, __packageInPathInfo__ is creating correct desired
directory structure.
Am I missing something?
problem with ${package} in java file
Key: ARCHETYPE-453
URL: https://jira.codehaus.org/browse/ARCHETYPE-453
Project: Maven Archetype
Issue Type: Bug
Reporter: prabal kumar
I am using ${package} in my java file and it is not being replaced after
using mvn archetype:generate -DarchetypeCatalog=local command and providing
all the properties. However, __packageInPathFormat__ is creating correct
desired directory structure.
Am I missing something?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
