[jira] Created: (MDEP-293) excludeArtifactIds parameter not processed in go-offline mojo for previous projects
excludeArtifactIds parameter not processed in go-offline mojo for previous projects --- Key: MDEP-293 URL: http://jira.codehaus.org/browse/MDEP-293 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: go-offline Affects Versions: 2.0 Environment: Windows XP Reporter: Sourajit Basak Assignee: Brian Fox go-offline mojo is overlooking the excluded artifacts specified like mvn dependency:2.1:go-offline -DexcludeArtifactIds=artifact-id This happens if the artifact-id is the output of a preceding project. -- 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] Commented: (SCM-580) Maven SCM plugin configuration ignored if executions are used.
[
http://jira.codehaus.org/browse/SCM-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=243507#action_243507
]
H.-C. Gürsoy commented on SCM-580:
--
Dear Lee,
it's sad but true: it's a maven feature ;-)
I've fighted myself with this feature, see these issues:
http://jira.codehaus.org/browse/MNG-3425
http://jira.codehaus.org/browse/MNG-3401
and
http://jira.codehaus.org/browse/MSQL-65 (the last one is exactly the same
usecase).
Best regards
Halil
Maven SCM plugin configuration ignored if executions are used.
--
Key: SCM-580
URL: http://jira.codehaus.org/browse/SCM-580
Project: Maven SCM
Issue Type: Bug
Affects Versions: 1.4
Environment: Windows
Reporter: Lee Fox
When utilizing the embedded configuration tag, everything is perfect.
However, once I try to use executions, the plugin fails to recognize the
settings specified in within the execution tag. Here is the portion of my
pom file that doesn't work:
profile
idbootstrap-all/id
activation
activeByDefaulttrue/activeByDefault
/activation
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-plugin/artifactId
version1.4/version
configuration
skipCheckoutIfExists/
/configuration
executions
execution
idcheckout_a/id
configuration
connectionUrlscm:svn:https://svnserver/svn/prod/java/aws-core-webutils/trunk//connectionUrl
checkoutDirectory${basedir}..\aws-core-webutils/checkoutDirectory
/configuration
phaseprocess-resources/phase
goals
goalcheckout/goal
/goals
/execution
/executions
/plugin
/plugins
/build
/profile
However, this does work:
profile
idbootstrap-all/id
activation
activeByDefaulttrue/activeByDefault
/activation
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-plugin/artifactId
version1.4/version
configuration
skipCheckoutIfExists/
connectionUrlscm:svn:https://svnserver/svn/prod/java/aws-core-webutils/trunk//connectionUrl
checkoutDirectory${basedir}\..\aws-core-webutils/checkoutDirectory
/configuration
/plugin
/plugins
/build
/profile
--
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] Commented: (MDEP-293) excludeArtifactIds parameter not processed in go-offline mojo for previous projects
[ http://jira.codehaus.org/browse/MDEP-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=243508#action_243508 ] Sourajit Basak commented on MDEP-293: - Attaching a test case to demonstrate this behavior. To reproduce - 1) Unzip the attached zip (I used WinZip for packing) 2) It should create a project structure like pom.xml project1 +-- pom.xml +-- src/main/java/Project1.java project2 +-- pom.xml +-- src/main/... 3) Go to the top level directory and execute - C:\SRC\bugmvn org.apache.maven.plugins:maven-dependency-plugin:2.1:go-offline -DexcludeArtifactIds=project1 It will fail with the following Missing: -- 1) com.ibm.websphere.bpm:project1:jar:1.0.0 Try downloading the file manually from the project website. Why is it trying to download this artifact ? Even -DexcludeGroupIds=com.ibm doesn't work. excludeArtifactIds parameter not processed in go-offline mojo for previous projects --- Key: MDEP-293 URL: http://jira.codehaus.org/browse/MDEP-293 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: go-offline Affects Versions: 2.0 Environment: Windows XP Reporter: Sourajit Basak Assignee: Brian Fox go-offline mojo is overlooking the excluded artifacts specified like mvn dependency:2.1:go-offline -DexcludeArtifactIds=artifact-id This happens if the artifact-id is the output of a preceding project. -- 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] Updated: (MDEP-293) excludeArtifactIds parameter not processed in go-offline mojo for previous projects
[ http://jira.codehaus.org/browse/MDEP-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sourajit Basak updated MDEP-293: Attachment: bug.zip Test case excludeArtifactIds parameter not processed in go-offline mojo for previous projects --- Key: MDEP-293 URL: http://jira.codehaus.org/browse/MDEP-293 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: go-offline Affects Versions: 2.0 Environment: Windows XP Reporter: Sourajit Basak Assignee: Brian Fox Attachments: bug.zip go-offline mojo is overlooking the excluded artifacts specified like mvn dependency:2.1:go-offline -DexcludeArtifactIds=artifact-id This happens if the artifact-id is the output of a preceding project. -- 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] Moved: (MJAVADOC-303) Project reports label for JavaDocs contains pom property name instead.
[ http://jira.codehaus.org/browse/MJAVADOC-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MPIR-192 to MJAVADOC-303: --- Affects Version/s: (was: 2.1.2) 2.7 Key: MJAVADOC-303 (was: MPIR-192) Project: Maven 2.x Javadoc Plugin (was: Maven 2.x Project Info Reports Plugin) Project reports label for JavaDocs contains pom property name instead. -- Key: MJAVADOC-303 URL: http://jira.codehaus.org/browse/MJAVADOC-303 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.7 Environment: Windows XPSP2, Maven 2.2.1, Java 1.6u18 Reporter: David Biesack Priority: Minor Attachments: pom.xml When a pom.xml defines a property, such as properties namejava.language.version/namevalue1.6/value /properties then the project info reports uses the property name for the 'Document' label of the Javadoc report in site/project-reports.html i.e. the generated HTML is file:///U:/dev/maven-bugs/MPIR-javadoc/target/site/apidocs/index.html tr class=btda href=apidocs/index.htmljava.language.version/a/td tdJavaDoc API documentation./td See attached pom.xml -- 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] Closed: (MNG-4900) Unresolveable build extension when using shade plugin and repositories in profile
[
http://jira.codehaus.org/browse/MNG-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4900.
--
Resolution: Fixed
Fix Version/s: 3.0.1
Assignee: Benjamin Bentmann
Fixed in [r1036433|http://svn.apache.org/viewvc?view=revisionrevision=1036433].
The Shade Plugin invokes {{MavenProjectBuilder.build(File, ArtifactRepository,
ProfileManager)}}, passing in {{null}} for the profile manager argument. This
makes it effectively build a project instance without active profiles, thereby
loosing repos, dependencies etc. from those profiles. And the local repo impl
used by Maven 3.0 doesn't serve files which aren't available from the declared
remote repos. I was close to moving this issue to the Shade Plugin itself but
had to realize that there is apparently no way to fix it using the Maven 2.x
APIs, oh well.
Unresolveable build extension when using shade plugin and repositories in
profile
---
Key: MNG-4900
URL: http://jira.codehaus.org/browse/MNG-4900
Project: Maven 2 3
Issue Type: Bug
Components: Dependencies, Settings
Affects Versions: 3.0
Environment: This problem does not occur in Maven 3.0-beta-2 and
earlier. It only occurs in Maven 3.0-beta-3 and Maven 3.0
Reporter: Paul Gier
Assignee: Benjamin Bentmann
Fix For: 3.0.1
Attachments: build.log, pom.xml
There seems to be a problem when the shade plugin tries to resolve plugin
extensions using a repository specified in a profile (either in the pom or
settings.xml). It only tries to resolve from central. I attached a sample
pom to reproduce the problem, and the build output.
The problem can be seen by running the package goal in Maven 3.0.
{noformat}mvn clean package -Pjboss-public{noformat}
--
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] Closed: (MPIR-199) ProjectInfoReportUtils.java : Avoid using blocking call [ url.openStream() ] while opening stream from an URL
[
http://jira.codehaus.org/browse/MPIR-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MPIR-199.
Resolution: Fixed
Fix Version/s: 2.3
Assignee: Vincent Siveton
fixed in r1036439, snapshot deployed
ProjectInfoReportUtils.java : Avoid using blocking call [ url.openStream() ]
while opening stream from an URL
-
Key: MPIR-199
URL: http://jira.codehaus.org/browse/MPIR-199
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Bug
Components: dependencies
Affects Versions: 2.1.1, 2.1.2, 2.2
Environment: any, with no internet connectivity [=~ intranet , behind
proxy etc.. ]
Reporter: Prashant Bhate
Assignee: Vincent Siveton
Fix For: 2.3
This issue is related to http://jira.codehaus.org/browse/MPIR-150
it would be nice if {{url.openStream();}}
from
{code:title=ProjectInfoReportUtils.java|borderStyle=solid}
InputStream in =null;
try
{
in = url.openStream();
{code}
can be replaced with
{code}
//Define constant TIMEOUT with pre set timeout
InputStream in =null;
try
{
URLConnection conn = url.openConnection();
conn.setConnectTimeout(TIMEOUT);
conn.setReadTimeout(TIMEOUT);
in = conn.getInputStream();
{code}
{{url.openStream();}} is a blocking call that makes caller wait forever and
eventually timeouts at the end
--
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] Closed: (MPIR-132) Dependency report fails on system-scope dependencies
[
http://jira.codehaus.org/browse/MPIR-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MPIR-132.
Resolution: Cannot Reproduce
Unable to reproduce it
Dependency report fails on system-scope dependencies
Key: MPIR-132
URL: http://jira.codehaus.org/browse/MPIR-132
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Bug
Components: dependencies
Affects Versions: 2.1
Reporter: Kohsuke Kawaguchi
Attachments: MPIR-132-test.patch
If a project includes a dependency to the system-scope artifact (such as
tools.jar), the dependency report generation fails with NPE.
MPIR-37 is probably the same issue, but I couldn't reopen it.
{noformat}
java.lang.NullPointerException
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:92)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:73)
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:526)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:234)
at
org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository(RepositoryUtils.java:316)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyRepositoryLocations(DependenciesRenderer.java:623)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:274)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65)
at
org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:239)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133)
at
org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
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: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)
{noformat}
The essence of the problem is as follows.
DependenciesRenderer has the following code to build POM out of all
dependencies, so that it can generate transitive dependency tree:
{noformat}
populateRepositoryMap( repoMap,
repoUtils.getRemoteArtifactRepositories() );
for ( Iterator it = alldeps.iterator(); it.hasNext(); )
{
Artifact artifact = (Artifact) it.next();
try
{
[jira] Created: (MNG-4901) WAR Packaging creates mulitple web.xml's in WEB-INF directory
WAR Packaging creates mulitple web.xml's in WEB-INF directory - Key: MNG-4901 URL: http://jira.codehaus.org/browse/MNG-4901 Project: Maven 2 3 Issue Type: Bug Components: Deployment Affects Versions: 3.0 Environment: Java version: 1.6.0_18 Java home: C:...\jdk6_18\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows Reporter: Steve Schmidt Here are the steps to reproduce issue; the first example creates a proper WAR with 1 /WEB-INF/web.xml. The second scenario creates 2 web.xml's - or at least 2 entries in the WAR catalog. The project WAR will then not deploy. From a Windows XP command window: set M2_HOME=C:\apache-maven\apache-maven-2.2.1 set PATH=%PATH%;%M2_HOME%\bin mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-webapp -DarchetypeArtifactId=maven-archetype-webapp mvn -version Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400) Java version: 1.6.0_18 Java home: C:...\jdk6_18\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows mvn package 1 web.xml To reproduce error set M2_HOME=C:\apache-maven\apache-maven-3.0 set PATH=%PATH%;%M2_HOME%\bin mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-webapp -DarchetypeArtifactId=maven-archetype-webapp mvn -version Apache Maven 3.0 (r1004208; 2010-10-04 07:50:56-0400) Java version: 1.6.0_18 Java home: C:...\jdk6_18\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows mvn package 2 web.xml's in /WEB-INF WAR. -- 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] Closed: (MWAR-242) WAR Packaging creates mulitple web.xml's in WEB-INF directory
[ http://jira.codehaus.org/browse/MWAR-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MWAR-242. -- Resolution: Duplicate Assignee: Benjamin Bentmann The generated project doesn't specify the plugin version, and as such is subject to the default plugin version and any of its bugs. WAR Packaging creates mulitple web.xml's in WEB-INF directory - Key: MWAR-242 URL: http://jira.codehaus.org/browse/MWAR-242 Project: Maven 2.x WAR Plugin Issue Type: Bug Affects Versions: 2.1 Environment: Java version: 1.6.0_18 Java home: C:...\jdk6_18\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows Reporter: Steve Schmidt Assignee: Benjamin Bentmann Here are the steps to reproduce issue; the first example creates a proper WAR with 1 /WEB-INF/web.xml. The second scenario creates 2 web.xml's - or at least 2 entries in the WAR catalog. The project WAR will then not deploy. From a Windows XP command window: set M2_HOME=C:\apache-maven\apache-maven-2.2.1 set PATH=%PATH%;%M2_HOME%\bin mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-webapp -DarchetypeArtifactId=maven-archetype-webapp mvn -version Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400) Java version: 1.6.0_18 Java home: C:...\jdk6_18\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows mvn package 1 web.xml To reproduce error set M2_HOME=C:\apache-maven\apache-maven-3.0 set PATH=%PATH%;%M2_HOME%\bin mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-webapp -DarchetypeArtifactId=maven-archetype-webapp mvn -version Apache Maven 3.0 (r1004208; 2010-10-04 07:50:56-0400) Java version: 1.6.0_18 Java home: C:...\jdk6_18\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows mvn package 2 web.xml's in /WEB-INF WAR. -- 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] Moved: (MWAR-242) WAR Packaging creates mulitple web.xml's in WEB-INF directory
[ http://jira.codehaus.org/browse/MWAR-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-4901 to MWAR-242: - Complexity: (was: Intermediate) Component/s: (was: Deployment) Affects Version/s: (was: 3.0) 2.1 Key: MWAR-242 (was: MNG-4901) Project: Maven 2.x WAR Plugin (was: Maven 2 3) WAR Packaging creates mulitple web.xml's in WEB-INF directory - Key: MWAR-242 URL: http://jira.codehaus.org/browse/MWAR-242 Project: Maven 2.x WAR Plugin Issue Type: Bug Affects Versions: 2.1 Environment: Java version: 1.6.0_18 Java home: C:...\jdk6_18\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows Reporter: Steve Schmidt Here are the steps to reproduce issue; the first example creates a proper WAR with 1 /WEB-INF/web.xml. The second scenario creates 2 web.xml's - or at least 2 entries in the WAR catalog. The project WAR will then not deploy. From a Windows XP command window: set M2_HOME=C:\apache-maven\apache-maven-2.2.1 set PATH=%PATH%;%M2_HOME%\bin mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-webapp -DarchetypeArtifactId=maven-archetype-webapp mvn -version Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400) Java version: 1.6.0_18 Java home: C:...\jdk6_18\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows mvn package 1 web.xml To reproduce error set M2_HOME=C:\apache-maven\apache-maven-3.0 set PATH=%PATH%;%M2_HOME%\bin mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-webapp -DarchetypeArtifactId=maven-archetype-webapp mvn -version Apache Maven 3.0 (r1004208; 2010-10-04 07:50:56-0400) Java version: 1.6.0_18 Java home: C:...\jdk6_18\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows mvn package 2 web.xml's in /WEB-INF WAR. -- 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: (MNG-4902) Update default plugin versions
Update default plugin versions -- Key: MNG-4902 URL: http://jira.codehaus.org/browse/MNG-4902 Project: Maven 2 3 Issue Type: Task Components: Plugins and Lifecycle Affects Versions: 3.0 Reporter: Benjamin Bentmann Priority: Trivial The WAR Plugin version 2.1 currently used by default is broken and should be updated. -- 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] Closed: (MNG-4902) Update default plugin versions
[ http://jira.codehaus.org/browse/MNG-4902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4902. -- Resolution: Fixed Fix Version/s: 3.0.1 Assignee: Benjamin Bentmann Done in [r1036506|http://svn.apache.org/viewvc?view=revisionrevision=1036506]. Update default plugin versions -- Key: MNG-4902 URL: http://jira.codehaus.org/browse/MNG-4902 Project: Maven 2 3 Issue Type: Task Components: Plugins and Lifecycle Affects Versions: 3.0 Reporter: Benjamin Bentmann Assignee: Benjamin Bentmann Priority: Trivial Fix For: 3.0.1 The WAR Plugin version 2.1 currently used by default is broken and should be updated. -- 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] Commented: (MNG-3939) dependencyManagement does not inherit imported dependencies
[ http://jira.codehaus.org/browse/MNG-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=243541#action_243541 ] Sebastian Paul commented on MNG-3939: - I tried to reproduce this. First, I added typepom/type, because Maven complained. Then I installed the dependency-pom. Checking with 'mvn help:effective-pom' shows that the parent contains the correct dependencyManagement and that the child contains the correct dependency to junit. I think the issue can be closed. dependencyManagement does not inherit imported dependencies --- Key: MNG-3939 URL: http://jira.codehaus.org/browse/MNG-3939 Project: Maven 2 3 Issue Type: Bug Components: Dependencies Affects Versions: 2.0.9 Reporter: Ben Dean Fix For: Issues to be reviewed for 3.x Attachments: console_output.txt, maven-dependency-inherited-import.not-working.zip, maven-dependency-inherited-import.working.zip I've attached a zip that has two versions of the same multi-module project. In the first version there is a parent-pom which defines a dependencyManagement section with one dependency (junit 4.4). I child project then inherits from the parent-pom and inherits the dependency management section including the version number for junit. Then then child project can have a dependency for junit and not care about the version number which is managed by the dependencyManagement inherited from the parent. In the second version, the dependencyManagement of the parent has been moved to a dependency-pom. This makes sense because the dependencyManagement section for a multi-module project could get huge and it would be nice to keep the parent-pom small and clean and just import dependencyManagement as needed. The problem is that the child project does not inherit these imported dependencies. It seems to me that imported dependencyManagement sections should be inherited too. This is the error given when the child doesn't what version of junit to use: Project ID: maven.dependency.example:child POM Location: C:\sandbox\eclipse\default\maven example\child\pom.xml Validation Messages: [0] 'dependencies.dependency.version' is missing for junit:junit This is somewhat related (maybe only tangentially) to the following issues: http://jira.codehaus.org/browse/MNG-3553 http://jira.codehaus.org/browse/MNG-2314 http://jira.codehaus.org/browse/MNG-3537 maybe more ... However, all those other issues seem to involve a more complex example than this issue. This issue is just dependencyManagement, import and inheritance. -- 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] Commented: (MNG-3939) dependencyManagement does not inherit imported dependencies
[ http://jira.codehaus.org/browse/MNG-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=243542#action_243542 ] Sebastian Paul commented on MNG-3939: - I forgot to mention that I used Maven 2.2.1 dependencyManagement does not inherit imported dependencies --- Key: MNG-3939 URL: http://jira.codehaus.org/browse/MNG-3939 Project: Maven 2 3 Issue Type: Bug Components: Dependencies Affects Versions: 2.0.9 Reporter: Ben Dean Fix For: Issues to be reviewed for 3.x Attachments: console_output.txt, maven-dependency-inherited-import.not-working.zip, maven-dependency-inherited-import.working.zip I've attached a zip that has two versions of the same multi-module project. In the first version there is a parent-pom which defines a dependencyManagement section with one dependency (junit 4.4). I child project then inherits from the parent-pom and inherits the dependency management section including the version number for junit. Then then child project can have a dependency for junit and not care about the version number which is managed by the dependencyManagement inherited from the parent. In the second version, the dependencyManagement of the parent has been moved to a dependency-pom. This makes sense because the dependencyManagement section for a multi-module project could get huge and it would be nice to keep the parent-pom small and clean and just import dependencyManagement as needed. The problem is that the child project does not inherit these imported dependencies. It seems to me that imported dependencyManagement sections should be inherited too. This is the error given when the child doesn't what version of junit to use: Project ID: maven.dependency.example:child POM Location: C:\sandbox\eclipse\default\maven example\child\pom.xml Validation Messages: [0] 'dependencies.dependency.version' is missing for junit:junit This is somewhat related (maybe only tangentially) to the following issues: http://jira.codehaus.org/browse/MNG-3553 http://jira.codehaus.org/browse/MNG-2314 http://jira.codehaus.org/browse/MNG-3537 maybe more ... However, all those other issues seem to involve a more complex example than this issue. This issue is just dependencyManagement, import and inheritance. -- 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: (MNG-4903) Update to Wagon 1.0-beta-7
Update to Wagon 1.0-beta-7 -- Key: MNG-4903 URL: http://jira.codehaus.org/browse/MNG-4903 Project: Maven 2 3 Issue Type: Task Affects Versions: 3.0, 2.2.1 Reporter: Dennis Lundberg -- 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] Commented: (MNG-4903) Update to Wagon 1.0-beta-7
[ http://jira.codehaus.org/browse/MNG-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=243551#action_243551 ] Dennis Lundberg commented on MNG-4903: -- Fixed in [r1036563|http://svn.apache.org/viewvc?view=revisionrevision=1036563] for 2.2.2. Update to Wagon 1.0-beta-7 -- Key: MNG-4903 URL: http://jira.codehaus.org/browse/MNG-4903 Project: Maven 2 3 Issue Type: Task Affects Versions: 2.2.1, 3.0 Reporter: Dennis Lundberg Assignee: Dennis Lundberg -- 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] Commented: (MNG-4903) Update to Wagon 1.0-beta-7
[ http://jira.codehaus.org/browse/MNG-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=243552#action_243552 ] Dennis Lundberg commented on MNG-4903: -- Fixed in [r1036567|http://svn.apache.org/viewvc?view=revisionrevision=1036567] for 3.0.1. Update to Wagon 1.0-beta-7 -- Key: MNG-4903 URL: http://jira.codehaus.org/browse/MNG-4903 Project: Maven 2 3 Issue Type: Task Affects Versions: 2.2.1, 3.0 Reporter: Dennis Lundberg Assignee: Dennis Lundberg -- 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] Closed: (MNG-4903) Update to Wagon 1.0-beta-7
[ http://jira.codehaus.org/browse/MNG-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MNG-4903. Resolution: Fixed Fix Version/s: 3.0.1 2.2.2 Update to Wagon 1.0-beta-7 -- Key: MNG-4903 URL: http://jira.codehaus.org/browse/MNG-4903 Project: Maven 2 3 Issue Type: Task Affects Versions: 2.2.1, 3.0 Reporter: Dennis Lundberg Assignee: Dennis Lundberg Fix For: 2.2.2, 3.0.1 -- 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] Closed: (MRELEASE-613) Add a parameter that tells the plugin to wait for X seconds before tagging
[ http://jira.codehaus.org/browse/MRELEASE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MRELEASE-613. Resolution: Fixed Fix Version/s: 2.2 Assignee: Dennis Lundberg Fixed in [r1036568|http://svn.apache.org/viewvc?view=revisionrevision=1036568]. Add a parameter that tells the plugin to wait for X seconds before tagging -- Key: MRELEASE-613 URL: http://jira.codehaus.org/browse/MRELEASE-613 Project: Maven 2.x Release Plugin Issue Type: New Feature Components: prepare Affects Versions: 2.1 Reporter: Dennis Lundberg Assignee: Dennis Lundberg Fix For: 2.2 Attachments: waitBeforeTagging.patch Doing releases at the ASF using the Release Plugin is a pain in you are in Europe, because of the svn-sync and geo-ip mapping that is used. The attached patch adds a new parameter waitBeforeTagging that takes the number of seconds to wait before tagging. I'd appreciate some more eyes on the patch, in particular whether my approach is thread-safe. -- 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: (MNG-4904) Make MavenExecutionResult.getTopologicallySortedProjects() return empty list instead of null
Make MavenExecutionResult.getTopologicallySortedProjects() return empty list instead of null Key: MNG-4904 URL: http://jira.codehaus.org/browse/MNG-4904 Project: Maven 2 3 Issue Type: Improvement Reporter: Basil James Whitehouse III MavenExecutionResult.getTopologicallySortedProjects() returns null when there are no projects forcing consumers to perform null checks. Consider returning an empty collection instead. -- 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] Updated: (MNG-4904) Make MavenExecutionResult.getTopologicallySortedProjects() return empty list instead of null
[ http://jira.codehaus.org/browse/MNG-4904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Basil James Whitehouse III updated MNG-4904: Attachment: MNG-4904.patch Git patch based on git://github.com/apache/maven-3.git . Test and javadoc supplied. Make MavenExecutionResult.getTopologicallySortedProjects() return empty list instead of null Key: MNG-4904 URL: http://jira.codehaus.org/browse/MNG-4904 Project: Maven 2 3 Issue Type: Improvement Reporter: Basil James Whitehouse III Attachments: MNG-4904.patch MavenExecutionResult.getTopologicallySortedProjects() returns null when there are no projects forcing consumers to perform null checks. Consider returning an empty collection instead. -- 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] Closed: (MNG-4904) Make MavenExecutionResult.getTopologicallySortedProjects() return empty list instead of null
[ http://jira.codehaus.org/browse/MNG-4904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4904. -- Resolution: Fixed Fix Version/s: 3.0.1 Assignee: Benjamin Bentmann Applied in [r1036585|http://svn.apache.org/viewvc?view=revisionrevision=1036585], thanks! Make MavenExecutionResult.getTopologicallySortedProjects() return empty list instead of null Key: MNG-4904 URL: http://jira.codehaus.org/browse/MNG-4904 Project: Maven 2 3 Issue Type: Improvement Affects Versions: 3.0 Reporter: Basil James Whitehouse III Assignee: Benjamin Bentmann Fix For: 3.0.1 Attachments: MNG-4904.patch MavenExecutionResult.getTopologicallySortedProjects() returns null when there are no projects forcing consumers to perform null checks. Consider returning an empty collection instead. -- 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] Updated: (MNG-4904) Make MavenExecutionResult.getTopologicallySortedProjects() return empty list instead of null
[ http://jira.codehaus.org/browse/MNG-4904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-4904: --- Affects Version/s: 3.0 Make MavenExecutionResult.getTopologicallySortedProjects() return empty list instead of null Key: MNG-4904 URL: http://jira.codehaus.org/browse/MNG-4904 Project: Maven 2 3 Issue Type: Improvement Affects Versions: 3.0 Reporter: Basil James Whitehouse III Assignee: Benjamin Bentmann Fix For: 3.0.1 Attachments: MNG-4904.patch MavenExecutionResult.getTopologicallySortedProjects() returns null when there are no projects forcing consumers to perform null checks. Consider returning an empty collection instead. -- 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: (MNG-4905) Active profiles defined in parent pom are not inherited in children pom
Active profiles defined in parent pom are not inherited in children pom --- Key: MNG-4905 URL: http://jira.codehaus.org/browse/MNG-4905 Project: Maven 2 3 Issue Type: Bug Components: Apache or Maven Parent poms Affects Versions: 3.0 Environment: Windows XP 32 bits SP2 Reporter: Benoît Berthonneau I've a parent pom which contains 2 profiles based on the OS (eg windows and not windows). The activation tag i used to determine this and works fine in this pom. I've a child pom (eg a module of the parent pom) where I'd like to use the active profile to tune my build goal. But in this child pom I could not get the active profile. If I launch mvn -P myProfile compile it works fine everywhere (parent and child). I'd like to have the inheritance of the active profiles defined in a parent pom in all its children modules. Easy to reproduce but could give a test case if needed. -- 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: (MNG-4906) maven3+tycho build fails: can't find plugin with name plugin_name_null
maven3+tycho build fails: can't find plugin with name plugin_name_null -- Key: MNG-4906 URL: http://jira.codehaus.org/browse/MNG-4906 Project: Maven 2 3 Issue Type: Bug Affects Versions: 3.0 Reporter: ask Priority: Critical Attachments: debug.log tried building my project with last Maven 3.0 + Tycho. build failed with a weird error: [INFO] Resolving target platform for project MavenProject: org.alskor.taskconverter:org.alskor.mspsync.rcp:1.0.0-SNAPSHOT @ C:\mspsync\org.alskor.msps ync.rcp\pom.xml [ERROR] Internal error: java.lang.RuntimeException: Could not resolve plugin org.alskor.mspsync.rcp_null; Path to dependency: - [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not resolve plugin org.alskor.mspsync.rcp_null; Path to dep endency: at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:163) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168) at org.apache.maven.cli.MavenCli.main(MavenCli.java:132) 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:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: java.lang.RuntimeException: Could not resolve plugin org.alskor.mspsync.rcp_null; Path to dependency: at org.codehaus.tycho.ArtifactDependencyVisitor.newRuntimeException(ArtifactDependencyVisitor.java:38) at org.codehaus.tycho.ArtifactDependencyVisitor.missingPlugin(ArtifactDependencyVisitor.java:27) at org.codehaus.tycho.osgitools.AbstractArtifactDependencyWalker.traversePlugin(AbstractArtifactDependencyWalker.java:240) at org.codehaus.tycho.osgitools.AbstractArtifactDependencyWalker.traverseProduct(AbstractArtifactDependencyWalker.java:115) at org.codehaus.tycho.osgitools.AbstractArtifactDependencyWalker.traverseProduct(AbstractArtifactDependencyWalker.java:98) at org.codehaus.tycho.osgitools.EclipseApplicationProject$1.walk(EclipseApplicationProject.java:28) at org.codehaus.tycho.osgitools.AbstractArtifactBasedProject.resolve(AbstractArtifactBasedProject.java:43) at org.codehaus.tycho.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:80) at org.codehaus.tycho.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:94) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:268) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151) ... 11 more -- 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] Updated: (MNG-4906) maven3+tycho build fails: can't find plugin with name plugin_name_null
[ http://jira.codehaus.org/browse/MNG-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ask updated MNG-4906: - Attachment: pom.xml the parent POM.xml file maven3+tycho build fails: can't find plugin with name plugin_name_null -- Key: MNG-4906 URL: http://jira.codehaus.org/browse/MNG-4906 Project: Maven 2 3 Issue Type: Bug Affects Versions: 3.0 Reporter: ask Priority: Critical Attachments: debug.log, pom.xml, pom.xml tried building my project with last Maven 3.0 + Tycho. build failed with a weird error: [INFO] Resolving target platform for project MavenProject: org.alskor.taskconverter:org.alskor.mspsync.rcp:1.0.0-SNAPSHOT @ C:\mspsync\org.alskor.msps ync.rcp\pom.xml [ERROR] Internal error: java.lang.RuntimeException: Could not resolve plugin org.alskor.mspsync.rcp_null; Path to dependency: - [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not resolve plugin org.alskor.mspsync.rcp_null; Path to dep endency: at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:163) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168) at org.apache.maven.cli.MavenCli.main(MavenCli.java:132) 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:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: java.lang.RuntimeException: Could not resolve plugin org.alskor.mspsync.rcp_null; Path to dependency: at org.codehaus.tycho.ArtifactDependencyVisitor.newRuntimeException(ArtifactDependencyVisitor.java:38) at org.codehaus.tycho.ArtifactDependencyVisitor.missingPlugin(ArtifactDependencyVisitor.java:27) at org.codehaus.tycho.osgitools.AbstractArtifactDependencyWalker.traversePlugin(AbstractArtifactDependencyWalker.java:240) at org.codehaus.tycho.osgitools.AbstractArtifactDependencyWalker.traverseProduct(AbstractArtifactDependencyWalker.java:115) at org.codehaus.tycho.osgitools.AbstractArtifactDependencyWalker.traverseProduct(AbstractArtifactDependencyWalker.java:98) at org.codehaus.tycho.osgitools.EclipseApplicationProject$1.walk(EclipseApplicationProject.java:28) at org.codehaus.tycho.osgitools.AbstractArtifactBasedProject.resolve(AbstractArtifactBasedProject.java:43) at org.codehaus.tycho.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:80) at org.codehaus.tycho.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:94) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:268) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151) ... 11 more -- 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] Updated: (MNG-4906) maven3+tycho build fails: can't find plugin with name plugin_name_null
[ http://jira.codehaus.org/browse/MNG-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ask updated MNG-4906: - Attachment: pom.xml org.alskor.mspsync.rcp\pom.xml file maven3+tycho build fails: can't find plugin with name plugin_name_null -- Key: MNG-4906 URL: http://jira.codehaus.org/browse/MNG-4906 Project: Maven 2 3 Issue Type: Bug Affects Versions: 3.0 Reporter: ask Priority: Critical Attachments: debug.log, pom.xml, pom.xml tried building my project with last Maven 3.0 + Tycho. build failed with a weird error: [INFO] Resolving target platform for project MavenProject: org.alskor.taskconverter:org.alskor.mspsync.rcp:1.0.0-SNAPSHOT @ C:\mspsync\org.alskor.msps ync.rcp\pom.xml [ERROR] Internal error: java.lang.RuntimeException: Could not resolve plugin org.alskor.mspsync.rcp_null; Path to dependency: - [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not resolve plugin org.alskor.mspsync.rcp_null; Path to dep endency: at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:163) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168) at org.apache.maven.cli.MavenCli.main(MavenCli.java:132) 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:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: java.lang.RuntimeException: Could not resolve plugin org.alskor.mspsync.rcp_null; Path to dependency: at org.codehaus.tycho.ArtifactDependencyVisitor.newRuntimeException(ArtifactDependencyVisitor.java:38) at org.codehaus.tycho.ArtifactDependencyVisitor.missingPlugin(ArtifactDependencyVisitor.java:27) at org.codehaus.tycho.osgitools.AbstractArtifactDependencyWalker.traversePlugin(AbstractArtifactDependencyWalker.java:240) at org.codehaus.tycho.osgitools.AbstractArtifactDependencyWalker.traverseProduct(AbstractArtifactDependencyWalker.java:115) at org.codehaus.tycho.osgitools.AbstractArtifactDependencyWalker.traverseProduct(AbstractArtifactDependencyWalker.java:98) at org.codehaus.tycho.osgitools.EclipseApplicationProject$1.walk(EclipseApplicationProject.java:28) at org.codehaus.tycho.osgitools.AbstractArtifactBasedProject.resolve(AbstractArtifactBasedProject.java:43) at org.codehaus.tycho.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:80) at org.codehaus.tycho.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:94) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:268) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151) ... 11 more -- 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] Closed: (MNG-4906) maven3+tycho build fails: can't find plugin with name plugin_name_null
[ http://jira.codehaus.org/browse/MNG-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4906. -- Resolution: Not A Bug Assignee: Benjamin Bentmann Please report this at https://issues.sonatype.org/browse/TYCHO. maven3+tycho build fails: can't find plugin with name plugin_name_null -- Key: MNG-4906 URL: http://jira.codehaus.org/browse/MNG-4906 Project: Maven 2 3 Issue Type: Bug Affects Versions: 3.0 Reporter: ask Assignee: Benjamin Bentmann Priority: Critical Attachments: debug.log, pom.xml, pom.xml tried building my project with last Maven 3.0 + Tycho. build failed with a weird error: [INFO] Resolving target platform for project MavenProject: org.alskor.taskconverter:org.alskor.mspsync.rcp:1.0.0-SNAPSHOT @ C:\mspsync\org.alskor.msps ync.rcp\pom.xml [ERROR] Internal error: java.lang.RuntimeException: Could not resolve plugin org.alskor.mspsync.rcp_null; Path to dependency: - [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not resolve plugin org.alskor.mspsync.rcp_null; Path to dep endency: at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:163) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168) at org.apache.maven.cli.MavenCli.main(MavenCli.java:132) 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:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: java.lang.RuntimeException: Could not resolve plugin org.alskor.mspsync.rcp_null; Path to dependency: at org.codehaus.tycho.ArtifactDependencyVisitor.newRuntimeException(ArtifactDependencyVisitor.java:38) at org.codehaus.tycho.ArtifactDependencyVisitor.missingPlugin(ArtifactDependencyVisitor.java:27) at org.codehaus.tycho.osgitools.AbstractArtifactDependencyWalker.traversePlugin(AbstractArtifactDependencyWalker.java:240) at org.codehaus.tycho.osgitools.AbstractArtifactDependencyWalker.traverseProduct(AbstractArtifactDependencyWalker.java:115) at org.codehaus.tycho.osgitools.AbstractArtifactDependencyWalker.traverseProduct(AbstractArtifactDependencyWalker.java:98) at org.codehaus.tycho.osgitools.EclipseApplicationProject$1.walk(EclipseApplicationProject.java:28) at org.codehaus.tycho.osgitools.AbstractArtifactBasedProject.resolve(AbstractArtifactBasedProject.java:43) at org.codehaus.tycho.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:80) at org.codehaus.tycho.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:94) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:268) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151) ... 11 more -- 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] Commented: (MNG-4906) maven3+tycho build fails: can't find plugin with name plugin_name_null
[ http://jira.codehaus.org/browse/MNG-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=243578#action_243578 ] ask commented on MNG-4906: -- the problem disappears if I remove org.alskor.mspsync.rcp from the build: !--moduleorg.alskor.mspsync.rcp/module-- maven3+tycho build fails: can't find plugin with name plugin_name_null -- Key: MNG-4906 URL: http://jira.codehaus.org/browse/MNG-4906 Project: Maven 2 3 Issue Type: Bug Affects Versions: 3.0 Reporter: ask Assignee: Benjamin Bentmann Priority: Critical Attachments: debug.log, pom.xml, pom.xml tried building my project with last Maven 3.0 + Tycho. build failed with a weird error: [INFO] Resolving target platform for project MavenProject: org.alskor.taskconverter:org.alskor.mspsync.rcp:1.0.0-SNAPSHOT @ C:\mspsync\org.alskor.msps ync.rcp\pom.xml [ERROR] Internal error: java.lang.RuntimeException: Could not resolve plugin org.alskor.mspsync.rcp_null; Path to dependency: - [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not resolve plugin org.alskor.mspsync.rcp_null; Path to dep endency: at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:163) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168) at org.apache.maven.cli.MavenCli.main(MavenCli.java:132) 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:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: java.lang.RuntimeException: Could not resolve plugin org.alskor.mspsync.rcp_null; Path to dependency: at org.codehaus.tycho.ArtifactDependencyVisitor.newRuntimeException(ArtifactDependencyVisitor.java:38) at org.codehaus.tycho.ArtifactDependencyVisitor.missingPlugin(ArtifactDependencyVisitor.java:27) at org.codehaus.tycho.osgitools.AbstractArtifactDependencyWalker.traversePlugin(AbstractArtifactDependencyWalker.java:240) at org.codehaus.tycho.osgitools.AbstractArtifactDependencyWalker.traverseProduct(AbstractArtifactDependencyWalker.java:115) at org.codehaus.tycho.osgitools.AbstractArtifactDependencyWalker.traverseProduct(AbstractArtifactDependencyWalker.java:98) at org.codehaus.tycho.osgitools.EclipseApplicationProject$1.walk(EclipseApplicationProject.java:28) at org.codehaus.tycho.osgitools.AbstractArtifactBasedProject.resolve(AbstractArtifactBasedProject.java:43) at org.codehaus.tycho.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:80) at org.codehaus.tycho.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:94) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:268) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151) ... 11 more -- 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] Commented: (MNG-4906) maven3+tycho build fails: can't find plugin with name plugin_name_null
[ http://jira.codehaus.org/browse/MNG-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=243579#action_243579 ] ask commented on MNG-4906: -- oh Tried to register at their website too, and got runtime exception from their Jira. maven3+tycho build fails: can't find plugin with name plugin_name_null -- Key: MNG-4906 URL: http://jira.codehaus.org/browse/MNG-4906 Project: Maven 2 3 Issue Type: Bug Affects Versions: 3.0 Reporter: ask Assignee: Benjamin Bentmann Priority: Critical Attachments: debug.log, pom.xml, pom.xml tried building my project with last Maven 3.0 + Tycho. build failed with a weird error: [INFO] Resolving target platform for project MavenProject: org.alskor.taskconverter:org.alskor.mspsync.rcp:1.0.0-SNAPSHOT @ C:\mspsync\org.alskor.msps ync.rcp\pom.xml [ERROR] Internal error: java.lang.RuntimeException: Could not resolve plugin org.alskor.mspsync.rcp_null; Path to dependency: - [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not resolve plugin org.alskor.mspsync.rcp_null; Path to dep endency: at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:163) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168) at org.apache.maven.cli.MavenCli.main(MavenCli.java:132) 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:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: java.lang.RuntimeException: Could not resolve plugin org.alskor.mspsync.rcp_null; Path to dependency: at org.codehaus.tycho.ArtifactDependencyVisitor.newRuntimeException(ArtifactDependencyVisitor.java:38) at org.codehaus.tycho.ArtifactDependencyVisitor.missingPlugin(ArtifactDependencyVisitor.java:27) at org.codehaus.tycho.osgitools.AbstractArtifactDependencyWalker.traversePlugin(AbstractArtifactDependencyWalker.java:240) at org.codehaus.tycho.osgitools.AbstractArtifactDependencyWalker.traverseProduct(AbstractArtifactDependencyWalker.java:115) at org.codehaus.tycho.osgitools.AbstractArtifactDependencyWalker.traverseProduct(AbstractArtifactDependencyWalker.java:98) at org.codehaus.tycho.osgitools.EclipseApplicationProject$1.walk(EclipseApplicationProject.java:28) at org.codehaus.tycho.osgitools.AbstractArtifactBasedProject.resolve(AbstractArtifactBasedProject.java:43) at org.codehaus.tycho.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:80) at org.codehaus.tycho.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:94) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:268) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151) ... 11 more -- 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] Commented: (MEV-673) Incorrect hashes in http://repo1.maven.org/maven2/org/apache/httpcomponents/project/4.1/
[ http://jira.codehaus.org/browse/MEV-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=243633#action_243633 ] J. David Beutel commented on MEV-673: - It doesn't seem like anyone is supporting Maven Central here. Should this issue be posted at https://issues.sonatype.org/browse/MVNCENTRAL instead? Incorrect hashes in http://repo1.maven.org/maven2/org/apache/httpcomponents/project/4.1/ Key: MEV-673 URL: http://jira.codehaus.org/browse/MEV-673 Project: Maven Evangelism Issue Type: Bug Components: Checksum Failure Reporter: SebbASF See: https://issues.apache.org/jira/browse/HTTPCLIENT-1017 We have reset the hashes on Nexus, and the Maven metadata has been updated, but the updated files have not been replicated. Please could you resynch the hashes? -- 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] Commented: (SUREFIRE-587) Doesn't run tests if they don't end with Test
[ http://jira.codehaus.org/browse/SUREFIRE-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=243640#action_243640 ] Greg Symons commented on SUREFIRE-587: -- I've hit this problem on pure JUnit4 tests as well. Doesn't run tests if they don't end with Test - Key: SUREFIRE-587 URL: http://jira.codehaus.org/browse/SUREFIRE-587 Project: Maven Surefire Issue Type: Bug Components: JUnit 3.x support, Junit 4.x support Affects Versions: 2.4.3 Environment: N/A Reporter: David J. M. Karlsen Priority: Critical We have a mix of test - some purely junit4 (e.g. not extending anything and annotating with @Test) - and some which extends TestCase. I've discovered that the ones extending TestCase won't run if the classname doesn't end with Test - so that the class CommonsAttributesParserTests won't get included (notice the ending s). -- 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] Updated: (ARCHETYPE-303) Externalize Archetype Catalog model into separate module
[ http://jira.codehaus.org/browse/ARCHETYPE-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák updated ARCHETYPE-303: -- Attachment: archetype-303.patch Complete patch for resolving this issue, made against https://svn.apache.org/repos/asf/maven/archetype/trunk @ 1036655 Externalize Archetype Catalog model into separate module Key: ARCHETYPE-303 URL: http://jira.codehaus.org/browse/ARCHETYPE-303 Project: Maven Archetype Issue Type: Improvement Reporter: Tamás Cservenák Attachments: archetype-303.patch Externalize Archetype Catalog model into separate module (ideally, without any dependency). This model would be likely reused by 3rd parties, but without dragging all the dependencies and other classes in archetype-common module. Typical example is Nexus's ArchetypePlugin, that publishes the archetype catalog, but from Nexus Index. Currently, that plugin _copied_ (rev668260) of Modello model to be able to publish. This obviously may lead to problems later. -- 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] Closed: (MNG-4883) [regression] Dependency resolution does not fail for artifact with over-constrained version ranges
[ http://jira.codehaus.org/browse/MNG-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4883. -- Resolution: Fixed Fix Version/s: 3.0.1 Assignee: Benjamin Bentmann Fixed in [r1036663|http://svn.apache.org/viewvc?view=revisionrevision=1036663]. [regression] Dependency resolution does not fail for artifact with over-constrained version ranges -- Key: MNG-4883 URL: http://jira.codehaus.org/browse/MNG-4883 Project: Maven 2 3 Issue Type: Bug Components: Dependencies Affects Versions: 3.0 Reporter: David Trott Assignee: Benjamin Bentmann Fix For: 3.0.1 Attachments: maven-samples.zip The sample project shows a usage of build ranges that should result in a build failure when you try to build project D. Because project D transitively depends on two different versions of project A 1.0 and 1.1. These versions are called out absolutely (using ranges) hence maven should not be able to build the project. This fails correctly in maven 2.2.1 However the project builds successfully in maven 3.0 Maven 3.0 should also fail to build. Note: I have included two copies of the pom file for project A so that you can build both of them without needing to edit the version. Build order is: A-1.0, A-1.1, B, C, D -- 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] Closed: (MNG-4884) Guice provision errors
[ http://jira.codehaus.org/browse/MNG-4884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4884. -- Resolution: Fixed Fix Version/s: 3.0.1 Assignee: Benjamin Bentmann Fixed in [r1036674|http://svn.apache.org/viewvc?view=revisionrevision=1036674]. Guice provision errors -- Key: MNG-4884 URL: http://jira.codehaus.org/browse/MNG-4884 Project: Maven 2 3 Issue Type: Bug Affects Versions: 3.0 Environment: windows vista sp2 32 bits on a hp dv5 laptop Reporter: Ricardo Assignee: Benjamin Bentmann Fix For: 3.0.1 Attachments: debug.log Please find attached the debug log as requested by the url presented on the error itself -- 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] Closed: (MNG-4850) [regression] several elements of server configuration in settings.xml are not honoured
[ http://jira.codehaus.org/browse/MNG-4850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4850. -- Resolution: Fixed Assignee: Benjamin Bentmann Fixed in [r1036677|http://svn.apache.org/viewvc?view=revisionrevision=1036677]. [regression] several elements of server configuration in settings.xml are not honoured -- Key: MNG-4850 URL: http://jira.codehaus.org/browse/MNG-4850 Project: Maven 2 3 Issue Type: Bug Components: Settings Affects Versions: 3.0-beta-3 Reporter: Brett Porter Assignee: Benjamin Bentmann Priority: Minor Fix For: 3.0.1 The IT MavenITmng3600DeploymentModeDefaultsTest.testitMNG3600ModesSet is currently failing for all versions of Maven 3. Correspondingly, when using Maven 3 with an SSH wagon listed as an extension, it deploys successfully but ignores the above settings, using default file and directory modes. -- 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: (MSHADE-90) Warn or error for signature files
Warn or error for signature files - Key: MSHADE-90 URL: http://jira.codehaus.org/browse/MSHADE-90 Project: Maven 2.x Shade Plugin Issue Type: Improvement Affects Versions: 1.4 Reporter: Benson Margulies If you shade a signed jar, the .SF files travel into the shaded jar. And then signature verification fails, and everyone gets consternated. It seems to me that shade should, by default, error when it hits one of these, and have a configuration option to strip them out. -- 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] Commented: (MEV-673) Incorrect hashes in http://repo1.maven.org/maven2/org/apache/httpcomponents/project/4.1/
[ http://jira.codehaus.org/browse/MEV-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=243664#action_243664 ] SebbASF commented on MEV-673: - OK. It looks like |MEV is being phased out. But if there was an announcement, I missed it. Incorrect hashes in http://repo1.maven.org/maven2/org/apache/httpcomponents/project/4.1/ Key: MEV-673 URL: http://jira.codehaus.org/browse/MEV-673 Project: Maven Evangelism Issue Type: Bug Components: Checksum Failure Reporter: SebbASF See: https://issues.apache.org/jira/browse/HTTPCLIENT-1017 We have reset the hashes on Nexus, and the Maven metadata has been updated, but the updated files have not been replicated. Please could you resynch the hashes? -- 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] Closed: (MEV-673) Incorrect hashes in http://repo1.maven.org/maven2/org/apache/httpcomponents/project/4.1/
[ http://jira.codehaus.org/browse/MEV-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SebbASF closed MEV-673. --- Incorrect hashes in http://repo1.maven.org/maven2/org/apache/httpcomponents/project/4.1/ Key: MEV-673 URL: http://jira.codehaus.org/browse/MEV-673 Project: Maven Evangelism Issue Type: Bug Components: Checksum Failure Reporter: SebbASF See: https://issues.apache.org/jira/browse/HTTPCLIENT-1017 We have reset the hashes on Nexus, and the Maven metadata has been updated, but the updated files have not been replicated. Please could you resynch the hashes? -- 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] Resolved: (MEV-673) Incorrect hashes in http://repo1.maven.org/maven2/org/apache/httpcomponents/project/4.1/
[ http://jira.codehaus.org/browse/MEV-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SebbASF resolved MEV-673. - Resolution: Fixed Let's see if the following issue does the trick: https://issues.sonatype.org/browse/MVNCENTRAL-14 Incorrect hashes in http://repo1.maven.org/maven2/org/apache/httpcomponents/project/4.1/ Key: MEV-673 URL: http://jira.codehaus.org/browse/MEV-673 Project: Maven Evangelism Issue Type: Bug Components: Checksum Failure Reporter: SebbASF See: https://issues.apache.org/jira/browse/HTTPCLIENT-1017 We have reset the hashes on Nexus, and the Maven metadata has been updated, but the updated files have not been replicated. Please could you resynch the hashes? -- 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] Commented: (MCOMPILER-114) Setting the debug option to false still compiles the code with line numbers resulting in increased class file.
[
http://jira.codehaus.org/browse/MCOMPILER-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=243670#action_243670
]
David H Vree commented on MCOMPILER-114:
I just tried the debug=true, debuglevel=none approach. As near as I can tell
the line number table is STILL in the class file.
Setting the debug option to false still compiles the code with line numbers
resulting in increased class file.
--
Key: MCOMPILER-114
URL: http://jira.codehaus.org/browse/MCOMPILER-114
Project: Maven 2.x Compiler Plugin
Issue Type: Bug
Affects Versions: 2.1
Environment: Windows XP Professional Version 5.1.2600 Service Pack 3
Build 2600, Dell OptiPlex GX280, Total Physical Memory 4,096.00 MB
Reporter: Grzegorz Solecki
Attachments: TestApp.zip
Given the following example:
{code:title=Bar.java|borderStyle=solid}
public class Main {
public static void main(String[] args) {
for (StackTraceElement stackTraceElement :
Thread.currentThread().getStackTrace())
System.out.println(stackTraceElement);
}
}
{code}
and pom.xml
{code:xml}
project xmlns=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/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.greg/groupId
artifactIdTestApp/artifactId
version1/version
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
debugnone/debug
source1.5/source
target1.5/target
/configuration
/plugin
/plugins
/build
/project
{code}
after compiling and running we get:
{panel:title=cmd}
{noformat}
{TestApp}\target\classesdir Main.class
05/02/2010 XX:XX 564 Main.class
{TestApp}\target\classesjava -cp . Main
java.lang.Thread.dumpThreads(Native Method)
java.lang.Thread.getStackTrace(Thread.java:1383)
Main.main(Main.java:3)
{noformat}
{panel}
*NOTE !!!: the number of line (Main.java:3) has been shown*
However when you compile the same java code using the javac we get:
{panel:title=cmd}
{noformat}
{TestApp}\src\main\javajavac -g:none -source 1.5 -target 1.5 Main.java
{TestApp}\src\main\javadir Main.class
05/02/2010 XX:XX 477 Main.class
{TestApp}\src\main\javajava -cp . Main
java.lang.Thread.dumpThreads(Native Method)
java.lang.Thread.getStackTrace(Thread.java:1383)
Main.main(Unknown Source){noformat}
{panel}
*NOTE !!!: the number of line has not been shown*
Please find the whole sample project in Eclipse that uses m2eclipse plugin,
that is configured for using external maven 2.2.1
--
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] Commented: (MEV-673) Incorrect hashes in http://repo1.maven.org/maven2/org/apache/httpcomponents/project/4.1/
[ http://jira.codehaus.org/browse/MEV-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=243677#action_243677 ] J. David Beutel commented on MEV-673: - I tried to look at that issue, but Sonatype's JIRA seems to be broken. First it said Login Required, although I can see other issues, like MVNCENTRAL-12. Not remembering whether I had already registered there, I tried logging in, but it didn't work, so I tried registering. That gave me a stack trace: org.codehaus.xfire.XFireRuntimeException: Could not invoke service.. Nested exception is org.codehaus.xfire.fault.XFireFault: [LDAP: error code 20 - modify/add: sn: value #0 already exists]; nested exception is javax.naming.directory.AttributeInUseException: [LDAP: error code 20 - modify/add: sn: value #0 already exists]; remaining name 'cn=david_beutel,ou=people,dc=sonatype,dc=org' Now I seem to be in some kind of Sonatype JIRA limbo. When I tried logging in again, it said I don't have permission to log in. But I seem to be logged in, because it shows my email address in the upper right corner now instead of the Log In link. When I try to look at MVNCENTRAL-14 now, it says permission violation. I would have told them about their JIRA problem, but I don't see any way to post issues on their JIRA. I even looked at their main web sites for a way to let them know, but couldn't find any support email or system, just a contact us web form for sales. So, I posted here. I guess Sonatype has its hands full. Incorrect hashes in http://repo1.maven.org/maven2/org/apache/httpcomponents/project/4.1/ Key: MEV-673 URL: http://jira.codehaus.org/browse/MEV-673 Project: Maven Evangelism Issue Type: Bug Components: Checksum Failure Reporter: SebbASF See: https://issues.apache.org/jira/browse/HTTPCLIENT-1017 We have reset the hashes on Nexus, and the Maven metadata has been updated, but the updated files have not been replicated. Please could you resynch the hashes? -- 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] Commented: (MEV-673) Incorrect hashes in http://repo1.maven.org/maven2/org/apache/httpcomponents/project/4.1/
[ http://jira.codehaus.org/browse/MEV-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=243678#action_243678 ] SebbASF commented on MEV-673: - Sorry, I may have chosen the wrong security level. Incorrect hashes in http://repo1.maven.org/maven2/org/apache/httpcomponents/project/4.1/ Key: MEV-673 URL: http://jira.codehaus.org/browse/MEV-673 Project: Maven Evangelism Issue Type: Bug Components: Checksum Failure Reporter: SebbASF See: https://issues.apache.org/jira/browse/HTTPCLIENT-1017 We have reset the hashes on Nexus, and the Maven metadata has been updated, but the updated files have not been replicated. Please could you resynch the hashes? -- 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
