[jira] Commented: (MSITE-383) Problem using "super pom" as parent in multi module project
[ http://jira.codehaus.org/browse/MSITE-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165216#action_165216 ] Per Lindfors commented on MSITE-383: Sorry, didn't see MSITE-129. > Problem using "super pom" as parent in multi module project > --- > > Key: MSITE-383 > URL: http://jira.codehaus.org/browse/MSITE-383 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: multi module >Affects Versions: 2.0-beta-7 > Environment: Windows XP SP_2 > JDK 1.5 > Maven 2.0.9 >Reporter: Per Lindfors > Attachments: MyProj.zip, super-poms.zip > > > I'm trying to generate a site for my multimodule project with mvn site-deploy > and with the following layout: > MyProj >| >- myproj-bl >| >- myproj-pl >| >- myproj-ear > In the case where each module refere to MyProj as , everything works > fine, the module-links are listed in the index page for MyProj. But when I > use the desired layout, where each module refere to a "super pom" as > , the resulting site structure is different and the links to the > modules are missing. > To me this is a bug when I dont find information saying that a module can > have parent not beeing the "multimodule project" > To reproduce, use attched projects. > 1. Unpack and build super-poms to your local repo. > 2. Unpack and build myproj with mvn install site-deploy. The site will be > deployed at c:/arkiv/proj/maven-site se root/pom.xml in super poms -- 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: (MAVENUPLOAD-2355) Upload mime-util library
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165211#action_165211 ] Davide Simonetti commented on MAVENUPLOAD-2355: --- To speed up the upload process i created another bundle with the group id net.sf.mime-util that matches the sourceforge website of the project. http://io-tools.googlecode.com/files/mime-util-1.2-bundle%28net.sf.mime-util%29.jar Thanks in advance. Davide. > Upload mime-util library > > > Key: MAVENUPLOAD-2355 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2355 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Davide Simonetti > > Please upload the mime-util library. > It's an Apache software license project already built with Maven. > I filed an upload request in their issue control management but at the moment > i didn't get any answer. > Since i'm not a developer i left the original group id, because in any case i > can't prove my ownership. Tell me if you need i change it in > "net.sf.mime-utils". > Best regards. > Davide -- 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-3553) cannot resolve dependency with scope import
[
http://jira.codehaus.org/browse/MNG-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165210#action_165210
]
Jacques Morel commented on MNG-3553:
Do you need me to provide another test case?
We would really appreciate an eta on when someone could start to look at this.
Thanks in advance.
> cannot resolve dependency with scope import
> ---
>
> Key: MNG-3553
> URL: http://jira.codehaus.org/browse/MNG-3553
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.0.9
>Reporter: Thomas Diesler
> Fix For: 2.0.11
>
> Attachments: mng-3553.zip
>
>
> This pom when added as a dependency of another project does not see
> repository http://snapshots.jboss.org/maven2
>
>
>
>
> org.jboss.jbossas
> jboss-as-component-matrix
> ${jboss.version}
> pom
> import
>
>
>
> with effective settings
> [tdies...@tddell trunk]$ mvn help:effective-settings
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] JBoss Web Services - Stack CXF
> [INFO] JBoss Web Services - Stack CXF Management
> [INFO] JBoss Web Services - Stack CXF Runtime Server
> [INFO] JBoss Web Services - Stack CXF Runtime Client
> [INFO] Searching repository for plugin with prefix: 'help'.
> [INFO]
>
> [INFO] Building JBoss Web Services - Stack CXF
> [INFO]task-segment: [help:effective-settings] (aggregator-style)
> [INFO]
>
> [INFO] [help:effective-settings]
> [INFO]
> Effective settings:
>
> /home/tdiesler/.m2/repository
>
>
>
>
> !jboss.repository.off
>
>
>
>
>
> snapshots.jboss.org
> http://snapshots.jboss.org/maven2
>
>
>
> false
>
> repository.jboss.org
> http://repository.jboss.org/maven2
>
>
> jboss.repository
>
>
>
> user-profile
>
>
> org.jboss.maven.plugins
>
>
--
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
ORA-12705: Cannot access NLS data files or invalid environment specified
Hi to all,
I have an Ubuntu running 8.10. I use maven2 for my projects. The Oracle 10g
database is located remotely. I already pinged the Oracle database and it
works fine.
But when I try to run "mvn jetty:run" an error appeared says:
+ Error stacktraces are turned on.
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your
local
repository will be inaccessible.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'jetty'.
[INFO]
[INFO] Building PSE Website
[INFO]task-segment: [jetty:run]
[INFO]
[INFO] Preparing jetty:run
[INFO] [aspectj:compile {execution: default}]
[INFO] [native2ascii:native2ascii {execution: native2ascii-utf8}]
[INFO] [native2ascii:native2ascii {execution: native2ascii-8859_1}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] Preparing hibernate3:hbm2ddl
[WARNING] Removing: hbm2ddl from forked lifecycle, to prevent recursive
invocation.
[INFO] [aspectj:compile {execution: default}]
[INFO] [native2ascii:native2ascii {execution: native2ascii-utf8}]
[INFO] [native2ascii:native2ascii {execution: native2ascii-8859_1}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[WARNING] POM for 'org.hibernate:jtidy:pom:r8-20060801:runtime' is invalid.
It will be ignored for artifact resolution. Reason: Parse error reading POM.
Reason: TEXT must be immediately followed by END_TAG and not START_TAG
(position: START_TAG seen ...\n\t\t\t... @12:13) for project
org.hibernate:jtidy at
/home/tristan/.m2/repository/org/hibernate/jtidy/r8-20060801/jtidy-r8-20060801.pom
[INFO] [hibernate3:hbm2ddl {execution: default}]
[INFO] Configuration XML file loaded:
file:/home/tristan/workspace/com.dagitab.pse/src/main/resources/hibernate.cfg.xml
[INFO] Configuration XML file loaded:
file:/home/tristan/workspace/com.dagitab.pse/src/main/resources/hibernate.cfg.xml
[INFO] Configuration Properties file loaded:
/home/tristan/workspace/com.dagitab.pse/target/classes/jdbc.properties
ERROR [main] SchemaExport.execute(202) | schema export unsuccessful
java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-12705: Cannot access NLS data files or invalid environment specified
at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:283)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:278)
at
oracle.jdbc.driver.T4CTTIoauthenticate.receiveOauth(T4CTTIoauthenticate.java:785)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:362)
at oracle.jdbc.driver.PhysicalConnection.(PhysicalConnection.java:414)
at oracle.jdbc.driver.T4CConnection.(T4CConnection.java:165)
at
oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)
at java.sql.DriverManager.getConnection(DriverManager.java:582)
at java.sql.DriverManager.getConnection(DriverManager.java:154)
at
org.hibernate.connection.DriverManagerConnectionProvider.getConnection(DriverManagerConnectionProvider.java:110)
at
org.hibernate.tool.hbm2ddl.ManagedProviderConnectionHelper.prepare(ManagedProviderConnectionHelper.java:28)
at
org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:180)
at org.hibernate.tool.hbm2ddl.SchemaExport.create(SchemaExport.java:133)
at
org.codehaus.mojo.hibernate3.exporter.Hbm2DDLExporterMojo.doExecute(Hbm2DDLExporterMojo.java:112)
at
org.codehaus.mojo.hibernate3.HibernateExporterMojo.execute(HibernateExporterMojo.java:140)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoa
[jira] Closed: (MERCURY-63) Fix case-sensitive string comparisons to be locale independent
[ http://jira.codehaus.org/browse/MERCURY-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov closed MERCURY-63. --- Resolution: Fixed Fix Version/s: 1.0-alpha-6 fixed > Fix case-sensitive string comparisons to be locale independent > -- > > Key: MERCURY-63 > URL: http://jira.codehaus.org/browse/MERCURY-63 > Project: Mercury > Issue Type: Bug > Components: Misc/All >Affects Versions: 1.0.0-alpha-2 >Reporter: Benjamin Bentmann >Assignee: Oleg Gusakov >Priority: Minor > Fix For: 1.0-alpha-6 > > Attachments: locale-independence.patch > > > cf. [Handling Strings > Case-insensitively|http://maven.apache.org/plugin-developers/common-bugs.html#Handling_Strings_Case-insensitively]. -- 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-4031) Release plexus-ant-factory 1.0-alpha-2.1 to enable enhanced ant-mojo support
[ http://jira.codehaus.org/browse/MNG-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MNG-4031: Fix Version/s: 2.1.0 > Release plexus-ant-factory 1.0-alpha-2.1 to enable enhanced ant-mojo support > - > > Key: MNG-4031 > URL: http://jira.codehaus.org/browse/MNG-4031 > Project: Maven 2 > Issue Type: Task >Reporter: John Casey >Assignee: John Casey >Priority: Blocker > Fix For: 2.1.0 > > > This is for MNG-3971. > SVN: > https://svn.codehaus.org/plexus/plexus-component-factories/branches/plexus-ant-factory-1.0-alpha-2.x -- 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-4031) Release plexus-ant-factory 1.0-alpha-2.1 to enable enhanced ant-mojo support
Release plexus-ant-factory 1.0-alpha-2.1 to enable enhanced ant-mojo support - Key: MNG-4031 URL: http://jira.codehaus.org/browse/MNG-4031 Project: Maven 2 Issue Type: Task Reporter: John Casey Priority: Blocker Fix For: 2.1.0 This is for MNG-3971. SVN: https://svn.codehaus.org/plexus/plexus-component-factories/branches/plexus-ant-factory-1.0-alpha-2.x -- 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-4030) Release maven-plugin-tools 2.4.4/2.5 to enable enhanced ant-mojo support
[ http://jira.codehaus.org/browse/MNG-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MNG-4030: Fix Version/s: 2.1.0 > Release maven-plugin-tools 2.4.4/2.5 to enable enhanced ant-mojo support > > > Key: MNG-4030 > URL: http://jira.codehaus.org/browse/MNG-4030 > Project: Maven 2 > Issue Type: Task >Reporter: John Casey >Assignee: John Casey >Priority: Blocker > Fix For: 2.1.0 > > > This is necessary for MNG-3971. -- 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-4030) Release maven-plugin-tools 2.4.4/2.5 to enable enhanced ant-mojo support
Release maven-plugin-tools 2.4.4/2.5 to enable enhanced ant-mojo support Key: MNG-4030 URL: http://jira.codehaus.org/browse/MNG-4030 Project: Maven 2 Issue Type: Task Reporter: John Casey Priority: Blocker Fix For: 2.1.0 This is necessary for MNG-3971. -- 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-3971) Provide parity in features between native ant-mojo support and antrun plugin
[ http://jira.codehaus.org/browse/MNG-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MNG-3971. --- Resolution: Fixed This will require releases of: * plexus-ant-factory 1.0-alpha-2.1 (https://svn.codehaus.org/plexus/plexus-component-factories/branches/plexus-ant-factory-1.0-alpha-2.x) * maven-plugin-tools 2.4.4 (or, maybe 2.5 for this sort of change) (https://svn.apache.org/repos/asf/maven/plugin-tools/trunk) > Provide parity in features between native ant-mojo support and antrun plugin > > > Key: MNG-3971 > URL: http://jira.codehaus.org/browse/MNG-3971 > Project: Maven 2 > Issue Type: Improvement > Components: Plugin API, Plugins and Lifecycle >Affects Versions: 2.0.9, 2.1.0-M1 >Reporter: John Casey >Assignee: John Casey > Fix For: 2.1.0 > > > In particular, we need to make sure classpaths, etc. that are available in > the antrun plugin are made available in the ant-mojo support. Going forward, > it'd be nice to find a way to use a common module for the two ways of using > Ant inside Maven. > The features available in the Antrun Plugin are often confused with those > available in the ant-mojo support, so this feature parity is critical to make > Ant usage in Maven more intuitive. -- 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: (MRELEASE-220) Add property to keep released versions for dependencies
[ http://jira.codehaus.org/browse/MRELEASE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165167#action_165167 ] Peter Liljenberg commented on MRELEASE-220: --- I've just tested this with 2.0-beta-8 and I don't think it works. I have 2 projects: proj1 proj2 proj2 dependes on proj1. If I have a SNAPSHOT dependency in proj2 to proj1 and executes: mvn release:prepare -DupdateDependencies=false mvn release:perform The resulting pom for proj2 will look like this after the release: ... nu.sunfire proj1 1.1-SNAPSHOT ... I would expect the version to be 1.0 During the prepare work, I get the question of which the next development version for proj1 should be, and nothing but a SNAPSHOT version can be entered? > Add property to keep released versions for dependencies > --- > > Key: MRELEASE-220 > URL: http://jira.codehaus.org/browse/MRELEASE-220 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Components: prepare >Affects Versions: 2.0-beta-4 >Reporter: Daniel Beland >Assignee: Emmanuel Venisse > > When I release a project with many modules with internal dependencies. > I would like those dependencies to keep the released version rather than the > next development version. > ie: I only release some modules at a time (those that were changed only since > last release). > So when my webapp is released, I want it to become SNAPSHOT again(as it is > done already) but want the internal dependencies to keep the released version. > I want to update them manually whenever I change one. -- 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: (SUREFIRE-537) Rason for the Ignored/Skipped testcases is not reported
Rason for the Ignored/Skipped testcases is not reported
---
Key: SUREFIRE-537
URL: http://jira.codehaus.org/browse/SUREFIRE-537
Project: Maven Surefire
Issue Type: Bug
Components: Junit 4.x support, report plugin, xml generation
Affects Versions: 2.4.3
Environment: Windows XP, junit 4.4
Reporter: Rakesh Arora
Tests that are skipped with a @Ignore("Test doesn't work") annotation only
appear in the report as an increment in the "Skipped" column. Name of the
skipped testcases is also reported. However, the reason (i.e. "Test doesn't
work") is not reported.
Quick look at the source code, it seems that it is not implemented:
In class: org.apache.maven.plugins.surefire.report.TestSuiteXmlParser
else if ( "skipped".equals( qName ) )
{
testCase.addFailure( "skipped", "skipped" ); // TODO extract
real reasons
currentSuite.setNumberOfSkipped( 1 +
currentSuite.getNumberOfSkipped() );
}
--
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-4029) Import of pom dependencies incorrectly scopes dependencies as runtime
Import of pom dependencies incorrectly scopes dependencies as runtime - Key: MNG-4029 URL: http://jira.codehaus.org/browse/MNG-4029 Project: Maven 2 Issue Type: Bug Components: Dependencies Affects Versions: 2.0.9 Reporter: Alex Deschapelles Attachments: testparent.tar.gz When dependencies are imported from a pom, they are resolved as runtime dependencies in the importing project. To test 1) Extract the attached project 2) cd into the testparent directory 3) mvn install 4) cd subparent/projectx 5) mvn dependency:resolve This will bring back : [INFO] The following files have been resolved: [INFO]antlr:antlr:jar:2.7.6:runtime [INFO]asm:asm:jar:1.5.3:runtime [INFO]asm:asm-attrs:jar:1.5.3:runtime [INFO]cglib:cglib:jar:2.1_3:runtime [INFO]com.test:hibernate-deps:pom:0.0.1-SNAPSHOT:import [INFO]com.test:spring-deps:pom:0.0.1-SNAPSHOT:import [INFO]commons-collections:commons-collections:jar:2.1.1:runtime [INFO]commons-logging:commons-logging:jar:1.1.1:runtime [INFO]dom4j:dom4j:jar:1.6.1:runtime [INFO]javax.transaction:jta:jar:1.0.1B:runtime [INFO]junit:junit:jar:4.5:test [INFO]net.sf.ehcache:ehcache:jar:1.2.3:runtime [INFO]org.hibernate:hibernate:jar:3.2.6.ga:runtime [INFO]org.springframework:spring:jar:2.5.6:runtime It would be more appropriate if the resolved scopes matched what is in the pom that defines them. -- 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: (MINVOKER-76) Have invoker:run generate report files to allow reporting on the results of running invoker
[
http://jira.codehaus.org/browse/MINVOKER-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MINVOKER-76.
-
Resolution: Fixed
Added parameter {{disableReports}} in
[r743489|http://svn.eu.apache.org/viewvc?view=rev&revision=743489].
> Have invoker:run generate report files to allow reporting on the results of
> running invoker
> ---
>
> Key: MINVOKER-76
> URL: http://jira.codehaus.org/browse/MINVOKER-76
> Project: Maven 2.x Invoker Plugin
> Issue Type: Improvement
>Reporter: Stephen Connolly
>Assignee: Olivier Lamy
> Fix For: 1.4
>
> Attachments: new-patch.diff, new-patch.diff, patch.diff
>
>
> The attached patch will adds generation of basic XML reports for each invoker
> run. This will allow other tools to report on the trends and the number of
> successes / failures. If this patch gets picked up I'll have a Hudson plugin
> to read these reports and I can also write a Maven reporting plugin to
> integrate with site.
--
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: (MWAR-126) It is not possible to package empty war.
[ http://jira.codehaus.org/browse/MWAR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165138#action_165138 ] Stephane Nicoll commented on MWAR-126: -- Actually I fixed it a while back but I forgot to resolve the issue. > It is not possible to package empty war. > > > Key: MWAR-126 > URL: http://jira.codehaus.org/browse/MWAR-126 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.0.2 >Reporter: Libor Kramolis > Attachments: MWAR-126.zip, war-bug.txt > > > If there is no java sources and no resources (src/main/java and > src/main/resources does not exist) it is not possible to package war > application. > But if I do NOT user classifier of war plugin there is no problem while > war:war goal. > -- > org.apache.maven.lifecycle.LifecycleExecutionException: Error installing > artifact: File > d:\work\tutor\development\tutorialproject-war_ws\target\classes does not exist > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) > 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) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error installing > artifact: File > d:\work\tutor\development\tutorialproject-war_ws\target\classes does not exist > at > org.apache.maven.plugin.install.InstallMojo.execute(InstallMojo.java:143) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > ... 16 more > Caused by: org.apache.maven.artifact.installer.ArtifactInstallationException: > Error installing artifact: File > d:\work\tutor\development\tutorialproject-war_ws\target\classes does not exist > at > org.apache.maven.artifact.installer.DefaultArtifactInstaller.install(DefaultArtifactInstaller.java:87) > at > org.apache.maven.plugin.install.InstallMojo.execute(InstallMojo.java:105) > ... 18 more > Caused by: java.io.IOException: File > d:\work\tutor\development\tutorialproject-war_ws\target\classes does not exist > at > hidden.org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:845) > at > org.apache.maven.artifact.installer.DefaultArtifactInstaller.install(DefaultArtifactInstaller.java:73) > ... 19 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-3641) Lack of error checks on profiles
[
http://jira.codehaus.org/browse/MNG-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Torben S. Giesselmann updated MNG-3641:
---
Attachment: MNG-3641-maven-project.patch
This patch will have Maven print a warning if a profile which should have been
explicitely activated has in fact not been activated.
It's just a warning message, therefore I didn't write a test case. But just out
of curiosity: how _would_ I test whether a warning with a specific message was
logged or not? Is there a pattern for that?
> Lack of error checks on profiles
>
>
> Key: MNG-3641
> URL: http://jira.codehaus.org/browse/MNG-3641
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 2.0.9
>Reporter: Kohsuke Kawaguchi
> Fix For: 2.0.11
>
> Attachments: MNG-3641-maven-project.patch
>
>
> DefaultProfileManager performs no error checks on the profile IDs So If I
> specify bogus profile IDs from plugins (like {{mvn -P no-such-profile}}),
> Maven doesn't complain, and it just runs as if nothing was specified. This is
> very error prone.
> Also, I've seen some documentation that says deactivating a profile is "-P
> !profile". As far as I can tell from the code, this is wrong, but because of
> the lack of error check, such usage just gets ignored, and the user is left
> confused as to why the profile isn't deactivated.
--
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] Reopened: (MINVOKER-76) Have invoker:run generate report files to allow reporting on the results of running invoker
[ http://jira.codehaus.org/browse/MINVOKER-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann reopened MINVOKER-76: --- We also need an option to turn the reports off, e.g. for invocations that are not meants as tests. > Have invoker:run generate report files to allow reporting on the results of > running invoker > --- > > Key: MINVOKER-76 > URL: http://jira.codehaus.org/browse/MINVOKER-76 > Project: Maven 2.x Invoker Plugin > Issue Type: Improvement >Reporter: Stephen Connolly >Assignee: Olivier Lamy > Fix For: 1.4 > > Attachments: new-patch.diff, new-patch.diff, patch.diff > > > The attached patch will adds generation of basic XML reports for each invoker > run. This will allow other tools to report on the trends and the number of > successes / failures. If this patch gets picked up I'll have a Hudson plugin > to read these reports and I can also write a Maven reporting plugin to > integrate with site. -- 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-112) The package RELEASE version of jar files are named jarname-RELEASE.jar
[ http://jira.codehaus.org/browse/MWAR-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MWAR-112. Resolution: Cannot Reproduce > The package RELEASE version of jar files are named jarname-RELEASE.jar > -- > > Key: MWAR-112 > URL: http://jira.codehaus.org/browse/MWAR-112 > Project: Maven 2.x War Plugin > Issue Type: Bug > Environment: Maven version: 2.0.7 > Java version: 1.5.0_11 > OS name: "windows xp" version: "5.1" arch: "x86" >Reporter: Chandra Patni >Priority: Minor > Attachments: MWAR-112.zip > > > Suppose, I have dependency > > mygroup > mylib > RELEASE > > In a war packaging, if I run mvn package, the war file contains > mylib-RELEASE.jar > Similarly, if you run mvn clean compile war:exploded, the exploded dir > contains mylib-RELEASE.jar > It packages dereferenced value of RELEASE if I do, > mvn clean compile > mvn war:exploded -- 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: (MWAR-112) The package RELEASE version of jar files are named jarname-RELEASE.jar
[ http://jira.codehaus.org/browse/MWAR-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MWAR-112: - Attachment: MWAR-112.zip Attaching a project that shows that this is not a problem. I tried with versions 2.0.2, 2.1-alpha-1 and 2.1-alpha-2. > The package RELEASE version of jar files are named jarname-RELEASE.jar > -- > > Key: MWAR-112 > URL: http://jira.codehaus.org/browse/MWAR-112 > Project: Maven 2.x War Plugin > Issue Type: Bug > Environment: Maven version: 2.0.7 > Java version: 1.5.0_11 > OS name: "windows xp" version: "5.1" arch: "x86" >Reporter: Chandra Patni >Priority: Minor > Attachments: MWAR-112.zip > > > Suppose, I have dependency > > mygroup > mylib > RELEASE > > In a war packaging, if I run mvn package, the war file contains > mylib-RELEASE.jar > Similarly, if you run mvn clean compile war:exploded, the exploded dir > contains mylib-RELEASE.jar > It packages dereferenced value of RELEASE if I do, > mvn clean compile > mvn war:exploded -- 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-126) It is not possible to package empty war.
[ http://jira.codehaus.org/browse/MWAR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MWAR-126. Resolution: Cannot Reproduce > It is not possible to package empty war. > > > Key: MWAR-126 > URL: http://jira.codehaus.org/browse/MWAR-126 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.0.2 >Reporter: Libor Kramolis > Attachments: MWAR-126.zip, war-bug.txt > > > If there is no java sources and no resources (src/main/java and > src/main/resources does not exist) it is not possible to package war > application. > But if I do NOT user classifier of war plugin there is no problem while > war:war goal. > -- > org.apache.maven.lifecycle.LifecycleExecutionException: Error installing > artifact: File > d:\work\tutor\development\tutorialproject-war_ws\target\classes does not exist > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) > 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) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error installing > artifact: File > d:\work\tutor\development\tutorialproject-war_ws\target\classes does not exist > at > org.apache.maven.plugin.install.InstallMojo.execute(InstallMojo.java:143) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > ... 16 more > Caused by: org.apache.maven.artifact.installer.ArtifactInstallationException: > Error installing artifact: File > d:\work\tutor\development\tutorialproject-war_ws\target\classes does not exist > at > org.apache.maven.artifact.installer.DefaultArtifactInstaller.install(DefaultArtifactInstaller.java:87) > at > org.apache.maven.plugin.install.InstallMojo.execute(InstallMojo.java:105) > ... 18 more > Caused by: java.io.IOException: File > d:\work\tutor\development\tutorialproject-war_ws\target\classes does not exist > at > hidden.org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:845) > at > org.apache.maven.artifact.installer.DefaultArtifactInstaller.install(DefaultArtifactInstaller.java:73) > ... 19 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: (MWAR-126) It is not possible to package empty war.
[ http://jira.codehaus.org/browse/MWAR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MWAR-126: - Attachment: MWAR-126.zip Attaching a test project that shows that there is no problem using a classifier for the WAR plugin. > It is not possible to package empty war. > > > Key: MWAR-126 > URL: http://jira.codehaus.org/browse/MWAR-126 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.0.2 >Reporter: Libor Kramolis > Attachments: MWAR-126.zip, war-bug.txt > > > If there is no java sources and no resources (src/main/java and > src/main/resources does not exist) it is not possible to package war > application. > But if I do NOT user classifier of war plugin there is no problem while > war:war goal. > -- > org.apache.maven.lifecycle.LifecycleExecutionException: Error installing > artifact: File > d:\work\tutor\development\tutorialproject-war_ws\target\classes does not exist > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) > 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) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error installing > artifact: File > d:\work\tutor\development\tutorialproject-war_ws\target\classes does not exist > at > org.apache.maven.plugin.install.InstallMojo.execute(InstallMojo.java:143) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > ... 16 more > Caused by: org.apache.maven.artifact.installer.ArtifactInstallationException: > Error installing artifact: File > d:\work\tutor\development\tutorialproject-war_ws\target\classes does not exist > at > org.apache.maven.artifact.installer.DefaultArtifactInstaller.install(DefaultArtifactInstaller.java:87) > at > org.apache.maven.plugin.install.InstallMojo.execute(InstallMojo.java:105) > ... 18 more > Caused by: java.io.IOException: File > d:\work\tutor\development\tutorialproject-war_ws\target\classes does not exist > at > hidden.org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:845) > at > org.apache.maven.artifact.installer.DefaultArtifactInstaller.install(DefaultArtifactInstaller.java:73) > ... 19 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: (MWAR-148) containerConfigXML option doesn`t include context.xml from external directory
[
http://jira.codehaus.org/browse/MWAR-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MWAR-148.
Resolution: Fixed
Fix Version/s: 2.1-alpha-2
Thanks for the test project. I tested this with 2.1-alpha-1 and that version is
broken like you reported. Upgrading to 2.1-alpha-2 solved the problem.
> containerConfigXML option doesn`t include context.xml from external directory
> -
>
> Key: MWAR-148
> URL: http://jira.codehaus.org/browse/MWAR-148
> Project: Maven 2.x War Plugin
> Issue Type: Bug
>Affects Versions: 2.1-alpha-1
>Reporter: Dmytro Seredenko
> Fix For: 2.1-alpha-2
>
> Attachments: context-bug.zip
>
>
> My task is to include different {{context.xml}} to the {{META-INF}} directory
> of the resulting war file.
> I provide default {{context.xml}} in the {{/src/main/webapp/META-INF}} and
> another in the {{/resources}} where "/" relates to the root of the project.
> Example of directory structure and {{pom.xml}} in the attached
> [^context-bug.zip]
> POM snippet with maven-war-plugin configuration:
> {code:xml}
>
>org.apache.maven.plugins
>maven-war-plugin
>
>
> ${basedir}/resources/context.xml
>
>
> {code}
> Debug output of the {{mvn war:war}}:
> {normat}
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-war-plugin:2.1-alpha-1:war' -->
> [DEBUG] (s) archiveClasses = false
> [DEBUG] (s) cacheFile =
> E:\Work\Downloader\downloader-web\target\war\work\webapp-cache.xml
> [DEBUG] (s) classesDirectory =
> E:\Work\Downloader\downloader-web\target\classes
> [DEBUG] (s) containerConfigXML =
> E:\Work\Downloader\downloader-web\resources\context.xml
> [DEBUG] (s) filters = []
> [DEBUG] (f) outputDirectory = E:\Work\Downloader\downloader-web\target
> [DEBUG] (f) primaryArtifact = true
> [DEBUG] (s) project = MavenProject: ru.kck.downloader:downloader-web:1.0 @
> E:\Work\Downloader\downloader-web\pom.xml
> [DEBUG] (s) useCache = true
> [DEBUG] (f) warName = downloader-web
> [DEBUG] (s) warSourceDirectory =
> E:\Work\Downloader\downloader-web\src\main\webapp
> [DEBUG] (s) webappDirectory =
> E:\Work\Downloader\downloader-web\target\downloader-web
> [DEBUG] (s) workDirectory =
> E:\Work\Downloader\downloader-web\target\war\work
> [DEBUG] -- end configuration --
> [INFO] [war:war]
> [INFO] Packaging webapp
> [INFO] Assembling webapp[downloader-web] in
> [E:\Work\Downloader\downloader-web\target\downloader-web]
> {normat}
> And last note: {{/resources/context.xml}} copied to the {{META-INF}} of the
> {{target}} directory, but war file created without any context.xml in it`s
> own META-INF
--
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-153) Resource filtering breaks when run from parent POM.
[
http://jira.codehaus.org/browse/MWAR-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MWAR-153.
Resolution: Fixed
Fix Version/s: 2.1-alpha-1
I tried this with Maven WAR Plugin 2.0.2 and I get the same error that the
reprter got.
When I used version 2.1-alpha-1 it works as expected. It also works with latest
trunk.
> Resource filtering breaks when run from parent POM.
>
>
> Key: MWAR-153
> URL: http://jira.codehaus.org/browse/MWAR-153
> Project: Maven 2.x War Plugin
> Issue Type: Bug
>Affects Versions: 2.0.2
> Environment: maven 2.08
> Windows and solaris
>Reporter: Keith Ganger
> Fix For: 2.1-alpha-1
>
> Attachments: test.zip
>
>
> breaks when run from a parent pom.
> When you define a resource directory for filtering, you must define it
> relative to the POM. When run from the war project's pom eveything works.
> When run from the parent you get an error
> {quote}
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] basedir src\main\webapp\WEB-INF does not exist
> [INFO]
>
> [DEBUG] Trace
> {quote}
> This is of course because the directory is relative to the child pom, where
> the plugin configuration was defined, not relative to the parent pom.
> I have attached an example project that demonstrates the bug.
> To repoduce
> * Run mvn package from the child my-app project everything works.
> * run mvn pacakge from the parent directory you will get the error.
--
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-3057) properties not expanded in generated POMs when building A/B/C nested projects
[
http://jira.codehaus.org/browse/MNG-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MNG-3057:
Fix Version/s: (was: 2.2.0-M1)
2.1.0
moving back into 2.1.0 bucket for discussions related to MDEPLOY-94, etc. Maybe
we should take a shot at this and start climbing the learning curve now in
terms of use cases.
> properties not expanded in generated POMs when building A/B/C nested projects
> -
>
> Key: MNG-3057
> URL: http://jira.codehaus.org/browse/MNG-3057
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 2.0.7
>Reporter: George Armhold
>Assignee: John Casey
> Fix For: 2.1.0
>
> Attachments: example.tar.gz, generated-poms.tar.gz,
> InstallMojo.java.patch, InstallMojo.java.patch,
> InstallMojo.quoteReplacement.patch, maven-install-parent.patch
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Using Maven version: 2.0.8-SNAPSHOT, svn r547427.
> I checked out and built 2.0.8 because I was interested in Jason van Zyl's
> patch for MNG-2619- "building from the middle pom of a
> (parent,child,grandchild) heirarchy fails". The fix works for the most part,
> but there still seems to be a problem with the poms that get generated during
> the install goal. The poms that get installed into .m2/repository do not
> have properties interpolated. If I run maven like:
>$ mvn install -Dglobal-version=1.0.0
> I get poms with the string "${global-version}" embedded in the resulting poms
> rather than what I specify on the command line (or in settings.xml). The
> build works properly aside from this, and if I do "mvn help:effective-pom"
> the properties are correctly interpolated.
> I've attached a tarfile with an example A/B/C build structure that exhibits
> this behavior, as well as the generated poms.
> Many thanks for your attention.
--
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-163) The outputFilenameMapping does not apply to the artifact of the current project
[ http://jira.codehaus.org/browse/MWAR-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MWAR-163. Assignee: Dennis Lundberg Resolution: Fixed Fix Version/s: 2.1 I have applied the patch with some minor changes: * Needed to catch an exception, that wasn't handled by the patch * Reformated the code to our style Thank you very much! > The outputFilenameMapping does not apply to the artifact of the current > project > --- > > Key: MWAR-163 > URL: http://jira.codehaus.org/browse/MWAR-163 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.1-alpha-1 > Environment: All >Reporter: Michael McCallum >Assignee: Dennis Lundberg > Fix For: 2.1 > > Attachments: artifact-factory-for-rename.patch > > > When packaging classes up into the war, the name for the created jar does not > use the outputFileNameMapping > Attached is a patch that uses the artifact factry to generate the artifact > name and uses the final name method to figure out the final name of the jar > in the 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] Commented: (MDEPLOY-94) Variables in the version element in pom.xml need to be expanded before deployment
[
http://jira.codehaus.org/browse/MDEPLOY-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165112#action_165112
]
John Casey commented on MDEPLOY-94:
---
I've added a link to MNG-3057 as this is basically the same issue. I'll take a
look at how we can revisit these issues for 2.1.0 as soon as I'm done with
another issue that I'm testing at the moment. You might have some luck doing
what Brian proposed on the maven dev list, and prepend the path to your jar
into the m2.conf file in $(maven.home)/bin.
If you have a patch that will interpolate all versions in the POM, can you post
it?
> Variables in the version element in pom.xml need to be expanded before
> deployment
> -
>
> Key: MDEPLOY-94
> URL: http://jira.codehaus.org/browse/MDEPLOY-94
> Project: Maven 2.x Deploy Plugin
> Issue Type: Bug
>Reporter: Brian Jackson
>
> We use an external tool to manage our releases (instead of
> maven-release-plugin). The version in our pom.xml is declared as:
> ${build.number}
> The actual version number is passed in during a release deployment on the
> command line "mvn deploy -Dbuild.number=1.2.3"
> The pom.xml is deployed literally without the variable replaced with the
> actual value. This causes problems, in particular multi-module releases are
> impossible since the parent pom can't be resolved properly as well as this
> issue with Nexus https://issues.sonatype.org/browse/NEXUS-1552
> I started digging into the code and see deployment is deferred to the
> DefaultArtifactDeployer
> http://maven.apache.org/ref/current/xref/org/apache/maven/artifact/deployer/DefaultArtifactDeployer.html
> Can I somehow install a custom ArtifactTransformation that expands these
> variables before deployment? How would I install it in my builds? Would I
> build it as a Plexus component and add it as a plugin dependency of
> maven-deploy-plugin? If someone could give me a little guidance I'd be happy
> to implement it, test it and submit a patch.
--
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-160) Strange behaviour of org.apache.maven.plugin.war.util.WarUtils.dependencyEquals(Dependency, Dependency)
[
http://jira.codehaus.org/browse/MWAR-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MWAR-160.
Assignee: Dennis Lundberg
Resolution: Fixed
Fix Version/s: 2.1
Fixed in r743348 including tests.
> Strange behaviour of
> org.apache.maven.plugin.war.util.WarUtils.dependencyEquals(Dependency,
> Dependency)
> ---
>
> Key: MWAR-160
> URL: http://jira.codehaus.org/browse/MWAR-160
> Project: Maven 2.x War Plugin
> Issue Type: Bug
> Environment: all
>Reporter: Grzegorz Grzybek
>Assignee: Dennis Lundberg
> Fix For: 2.1
>
>
> Maybe I have a bad day, but it seems that
> {code:java}
> if ( !!StringUtils.equals( first.getArtifactId(), second.getArtifactId() ) )
> {
>return false;
> }
> {code}
> has too many ! marks...
> am I wrong?
> with best regards
> Grzegorz Grzybek
--
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: (MWAR-165) Finiky filter include expressions to filter web.xml
[ http://jira.codehaus.org/browse/MWAR-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165097#action_165097 ] Dennis Lundberg commented on MWAR-165: -- I you only want to filter web.xml you can use the filteringDeploymentDescriptors parameter that was introduced in 2.1-alpha-2. > Finiky filter include expressions to filter web.xml > > > Key: MWAR-165 > URL: http://jira.codehaus.org/browse/MWAR-165 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.1-alpha-1 > Environment: Ubuntu 8.04 Linux, JDK 1.6_07 >Reporter: Alex Karasulu > > Include expressions which directly reference the WEB-INF in tag > does not match the web.xml file to filter it. If you go one step up and then > wild card down for XML files it works. For example this did not work: > src/main/webapp/WEB-INF > > web.xml > > The following include pattern variations do not work either: >*.xml >**/*.xml >*/*.xml >*/web.xml >**/web.xml > But this does work: > src/main/webapp > > **/web.xml > > as well as **/*.xml etc. -- 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-175) Separate targets for copying everything to target dir and for packing war.
[
http://jira.codehaus.org/browse/MWAR-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MWAR-175.
Resolution: Not A Bug
There is a goal for this already. Simply run:
{noformat}
mvn war:exploded
{noformat}
> Separate targets for copying everything to target dir and for packing war.
> --
>
> Key: MWAR-175
> URL: http://jira.codehaus.org/browse/MWAR-175
> Project: Maven 2.x War Plugin
> Issue Type: Wish
> Environment: apache-maven-2.0.9
>Reporter: Chei
>Priority: Minor
>
> Splitting the collecting and compressing of required project files would
> speed up the development cycle when Tomcat is configured to read the
> uncompressed webapp files from /target.
> I have the following configuration in
> apache-tomcat-6.0.18\conf\Catalina\localhost\helloworld.xml: path="/helloworld" docBase="d:\dev\ helloworld\target\ helloworld"
> What I regulary do is change the code and then invoke the maven:package to
> make the changes visible in Tomcat. Having the war file repackaged is not
> necessary for this, but as far as I know currently there is no way to update
> the contents of d:\dev\ helloworld\target\ helloworld without the lengthy
> process of compressing the war file.
> I think it would make sense to introduce a separate target for copying all
> the required files without invoking a compression on them.
--
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-181) warSourceExcludes does not work in 2.1-alpha-2
[
http://jira.codehaus.org/browse/MWAR-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MWAR-181.
Resolution: Duplicate
> warSourceExcludes does not work in 2.1-alpha-2
> --
>
> Key: MWAR-181
> URL: http://jira.codehaus.org/browse/MWAR-181
> Project: Maven 2.x War Plugin
> Issue Type: Bug
>Affects Versions: 2.1-alpha-2
>Reporter: Petr Kozelka
>Priority: Critical
>
> we use following configuration to produce jar-less war artifacts, in order to
> embed them to EAR:
> {{WEB-INF/lib/*.jar}}
> This does not work with release 2.1-alpha-2.
> Switching to 2.1-alpha-1 solves the problem.
--
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: (MWAR-182) warSourceExcludes no longer works
[ http://jira.codehaus.org/browse/MWAR-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MWAR-182: - Description: The element no longer seems to work, as of 2.1-alpha-2. It does seem to work in 2.1-alpha-1. I am attaching a pom.xml file which will demonstrate the problem when used as follows: 1) From the directory containing the pom.xml, create a web.xml, because otherwise it fails (setting failsOnMissingWebXml didn't seem to do the trick): mkdir -p src/main/webapp/WEB-INF touch src/main/webapp/WEB-INF/web.xml 2) Build with the 2.1-alpha-1 plugin mvn clean install -Dwar.plugin.version=2.1-alpha-1 3) Dump out the jar contents to verify that only commons-logging and the web.xml were packaged, as requested [warsourceexample]$ jar -tf target/example-war-0.1-SNAPSHOT.war META-INF/ META-INF/MANIFEST.MF WEB-INF/ WEB-INF/web.xml WEB-INF/lib/ WEB-INF/lib/commons-logging-1.1.jar META-INF/maven/ META-INF/maven/example/ META-INF/maven/example/example-war/ META-INF/maven/example/example-war/pom.xml META-INF/maven/example/example-war/pom.properties 4) Now build using the 2.1-alpha-2 plugin version: mvn clean install -Dwar.plugin.version=2.1-alpha-2 5) Dump out the jar contents and notice that warSourceIncludes was ignored this time: [warsourceexample]$ jar -tf target/example-war-0.1-SNAPSHOT.war META-INF/ META-INF/MANIFEST.MF WEB-INF/ WEB-INF/classes/ WEB-INF/lib/ WEB-INF/web.xml WEB-INF/lib/commons-logging-1.1.jar WEB-INF/lib/log4j-1.2.12.jar WEB-INF/lib/logkit-1.0.1.jar WEB-INF/lib/avalon-framework-4.1.3.jar WEB-INF/lib/servlet-api-2.3.jar META-INF/maven/ META-INF/maven/example/ META-INF/maven/example/example-war/ META-INF/maven/example/example-war/pom.xml META-INF/maven/example/example-war/pom.properties was: The element no longer seems to work, as of 2.1-alpha-2. It does seem to work in 2.1-alpha-1. I am attaching a pom.xml file which will demonstrate the problem when used as follows: 1) From the directory containing the pom.xml, create a web.xml, because otherwise it fails (setting failsOnMissingWebXml didn't seem to do the trick): mkdir -p src/main/webapp/WEB-INF touch src/main/webapp/WEB-INF/web.xml 2) Build with the 2.1-alpha-1 plugin mvn clean install -Dwar.plugin.version=2.1-alpha-1 3) Dump out the jar contents to verify that only commons-logging and the web.xml were packaged, as requested [warsourceexample]$ jar -tf target/example-war-0.1-SNAPSHOT.war META-INF/ META-INF/MANIFEST.MF WEB-INF/ WEB-INF/web.xml WEB-INF/lib/ WEB-INF/lib/commons-logging-1.1.jar META-INF/maven/ META-INF/maven/example/ META-INF/maven/example/example-war/ META-INF/maven/example/example-war/pom.xml META-INF/maven/example/example-war/pom.properties 4) Now build using the 2.1-alpha-2 plugin version: mvn clean install -Dwar.plugin.version=2.1-alpha-1 5) Dump out the jar contents and notice that warSourceIncludes was ignored this time: [warsourceexample]$ jar -tf target/example-war-0.1-SNAPSHOT.war META-INF/ META-INF/MANIFEST.MF WEB-INF/ WEB-INF/classes/ WEB-INF/lib/ WEB-INF/web.xml WEB-INF/lib/commons-logging-1.1.jar WEB-INF/lib/log4j-1.2.12.jar WEB-INF/lib/logkit-1.0.1.jar WEB-INF/lib/avalon-framework-4.1.3.jar WEB-INF/lib/servlet-api-2.3.jar META-INF/maven/ META-INF/maven/example/ META-INF/maven/example/example-war/ META-INF/maven/example/example-war/pom.xml META-INF/maven/example/example-war/pom.properties Summary: warSourceExcludes no longer works (was: warSourceIncludes no longer works) > warSourceExcludes no longer works > - > > Key: MWAR-182 > URL: http://jira.codehaus.org/browse/MWAR-182 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.1-alpha-2 > Environment: RHEL 3 >Reporter: Bryan Loofbourrow > Attachments: pom.xml > > > The element no longer seems to work, as of 2.1-alpha-2. > It does seem to work in 2.1-alpha-1. I am attaching a pom.xml file which will > demonstrate the problem when used as follows: > 1) From the directory containing the pom.xml, create a web.xml, because > otherwise it fails (setting failsOnMissingWebXml didn't seem to do the trick): > mkdir -p src/main/webapp/WEB-INF > touch src/main/webapp/WEB-INF/web.xml > 2) Build with the 2.1-alpha-1 plugin > mvn clean install -Dwar.plugin.version=2.1-alpha-1 > 3) Dump out the jar contents to verify that only commons-logging and the > web.xml were packaged, as requested > [warsourceexample]$ jar -tf target/example-war-0.1-SNAPSHOT.war > META-INF/ > META-INF/MANIFEST.MF > WEB-INF/ > WEB-INF/web.xml > WEB-INF/lib/ > WEB-INF/lib/commons-logging-1.1.jar > META-INF/maven/ > META-INF/maven/example/ > META-INF/maven/example/example-war/ > META-INF/maven/example/example-war/pom.xml > META-INF/maven/example/example-war/pom.prop
[jira] Updated: (MWAR-31) Support needed to allow use of custom manifest file
[ http://jira.codehaus.org/browse/MWAR-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MWAR-31: Fix Version/s: (was: 2.1) > Support needed to allow use of custom manifest file > --- > > Key: MWAR-31 > URL: http://jira.codehaus.org/browse/MWAR-31 > Project: Maven 2.x War Plugin > Issue Type: Improvement >Reporter: Mang Lau >Assignee: Dennis Lundberg >Priority: Minor > > Related to [MPWAR-22|http://jira.codehaus.org/browse/MPWAR-22] that was fixed > for Maven 1 and is not present in Maven 2. We should be able to specify the > path to our own custom manifest file when building a war, just like the > tag in the maven-ear-plugin. -- 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-31) Support needed to allow use of custom manifest file
[ http://jira.codehaus.org/browse/MWAR-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MWAR-31. --- Assignee: Dennis Lundberg (was: Olivier Lamy) Resolution: Not A Bug I tested this with Maven WAR Plugin 2.1-alpha-2 and it works just fine. > Support needed to allow use of custom manifest file > --- > > Key: MWAR-31 > URL: http://jira.codehaus.org/browse/MWAR-31 > Project: Maven 2.x War Plugin > Issue Type: Improvement >Reporter: Mang Lau >Assignee: Dennis Lundberg >Priority: Minor > Fix For: 2.1 > > > Related to [MPWAR-22|http://jira.codehaus.org/browse/MPWAR-22] that was fixed > for Maven 1 and is not present in Maven 2. We should be able to specify the > path to our own custom manifest file when building a war, just like the > tag in the maven-ear-plugin. -- 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-183) filteringDeploymentDescriptors should honor the encoding specified in web.xml
[ http://jira.codehaus.org/browse/MWAR-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MWAR-183. Assignee: Dennis Lundberg Resolution: Fixed Fix Version/s: 2.1 > filteringDeploymentDescriptors should honor the encoding specified in web.xml > - > > Key: MWAR-183 > URL: http://jira.codehaus.org/browse/MWAR-183 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.1-alpha-2 >Reporter: Dennis Lundberg >Assignee: Dennis Lundberg > Fix For: 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: (MNG-4028) Maven 2 still absolutely does not work
[ http://jira.codehaus.org/browse/MNG-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165072#action_165072 ] Brett Porter commented on MNG-4028: --- it should only require port 80 for java.exe > Maven 2 still absolutely does not work > -- > > Key: MNG-4028 > URL: http://jira.codehaus.org/browse/MNG-4028 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.1.0-M1 > Environment: Intel Windows XP 2G Ram >Reporter: Richard Katz >Assignee: Brett Porter > Attachments: screenshot-1.jpg, settings.xml > > > I originally reported this on Maven 2.0.9 and it was marked as closed. > But the problem still exists in Maven 2.1.0. I have tried the following > 1. Delete the .m2 directory and all its contents. > 2. Use the -U option > 3. Use the -e option. > 4. Run the create Archtype > mvn -e archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app > (and mvn -e -U archetype:create -DgroupId=com.mycompany.app > -DartifactId=my-app) > It simply does not work. > It fails with the same error as I always get in Maven 2.0.9 : > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid > version could be found > Here is the entire trace: > C:\Documents and Settings\Richard Katz>mvn -e -U archetype:create > -DgroupId=com.mycompany.app -DartifactId=my-app > + Error stacktraces are turned on. > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'archetype'. > [INFO] org.apache.maven.plugins: checking for updates from central > [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be > retrieved from repository: central due to an > error: Error transferring file > [INFO] Repository 'central' will be blacklisted > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not > exist or no valid version could be found > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > 'org.apache.maven.plugins:maven-archetype-plugin' doe > s not exist or no valid version could be found > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1303) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1542) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecuto > r.java:405) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > 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.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) > Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: > The plugin 'org.apache.maven.plugins:maven-ar > chetype-plugin' does not exist or no valid version could be found > at > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager. > java:229) > at > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager. > java:91) > at > org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:171) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274) > ... 14 more > [INFO] > > [INFO] Total time: 2 seconds > [INFO] Finished at: Tue Feb 10 21:40:41 PST 2009 > [INFO] Final Memory: 1M/4M > [INFO] > > C:\Documents and Settings\Richard Katz> > Questions: > 1. Is t
[jira] Closed: (MNG-4028) Maven 2 still absolutely does not work
[ http://jira.codehaus.org/browse/MNG-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Katz closed MNG-4028. - Resolution: Fixed OK. I found it. I got it to work. I just need one thing. What setting should be changed in a personal firewall (not a proxy but a personal firewall) such as Norton Internet Security to get Maven 2 to work? See: http://mail-archives.apache.org/mod_mbox/maven-users/200705.mbox/%3c464729c6.2030...@alltel.net%3e There are about 5 copies of this floating around. Was there a resolution (such as "turn on port xxx" for Java/Maven/etc...). If not, that's OK too. Thanks for your fast responses. Sincerely, Rich > Maven 2 still absolutely does not work > -- > > Key: MNG-4028 > URL: http://jira.codehaus.org/browse/MNG-4028 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.1.0-M1 > Environment: Intel Windows XP 2G Ram >Reporter: Richard Katz >Assignee: Brett Porter > Attachments: screenshot-1.jpg, settings.xml > > > I originally reported this on Maven 2.0.9 and it was marked as closed. > But the problem still exists in Maven 2.1.0. I have tried the following > 1. Delete the .m2 directory and all its contents. > 2. Use the -U option > 3. Use the -e option. > 4. Run the create Archtype > mvn -e archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app > (and mvn -e -U archetype:create -DgroupId=com.mycompany.app > -DartifactId=my-app) > It simply does not work. > It fails with the same error as I always get in Maven 2.0.9 : > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid > version could be found > Here is the entire trace: > C:\Documents and Settings\Richard Katz>mvn -e -U archetype:create > -DgroupId=com.mycompany.app -DartifactId=my-app > + Error stacktraces are turned on. > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'archetype'. > [INFO] org.apache.maven.plugins: checking for updates from central > [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be > retrieved from repository: central due to an > error: Error transferring file > [INFO] Repository 'central' will be blacklisted > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not > exist or no valid version could be found > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > 'org.apache.maven.plugins:maven-archetype-plugin' doe > s not exist or no valid version could be found > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1303) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1542) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecuto > r.java:405) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > 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.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) > Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: > The plugin 'org.apache.maven.plugins:maven-ar > chetype-plugin' does not exist or no valid version could be found > at > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager. > java:229) > at > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager. > java:91) > at > org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:171) > at > org.apache.maven.lif
[jira] Updated: (MNG-4028) Maven 2 still absolutely does not work
[ http://jira.codehaus.org/browse/MNG-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Katz updated MNG-4028: -- Attachment: screenshot-1.jpg Browsing to the directory named in settings.xml - works! > Maven 2 still absolutely does not work > -- > > Key: MNG-4028 > URL: http://jira.codehaus.org/browse/MNG-4028 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.1.0-M1 > Environment: Intel Windows XP 2G Ram >Reporter: Richard Katz >Assignee: Brett Porter > Attachments: screenshot-1.jpg, settings.xml > > > I originally reported this on Maven 2.0.9 and it was marked as closed. > But the problem still exists in Maven 2.1.0. I have tried the following > 1. Delete the .m2 directory and all its contents. > 2. Use the -U option > 3. Use the -e option. > 4. Run the create Archtype > mvn -e archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app > (and mvn -e -U archetype:create -DgroupId=com.mycompany.app > -DartifactId=my-app) > It simply does not work. > It fails with the same error as I always get in Maven 2.0.9 : > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid > version could be found > Here is the entire trace: > C:\Documents and Settings\Richard Katz>mvn -e -U archetype:create > -DgroupId=com.mycompany.app -DartifactId=my-app > + Error stacktraces are turned on. > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'archetype'. > [INFO] org.apache.maven.plugins: checking for updates from central > [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be > retrieved from repository: central due to an > error: Error transferring file > [INFO] Repository 'central' will be blacklisted > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not > exist or no valid version could be found > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > 'org.apache.maven.plugins:maven-archetype-plugin' doe > s not exist or no valid version could be found > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1303) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1542) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecuto > r.java:405) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > 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.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) > Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: > The plugin 'org.apache.maven.plugins:maven-ar > chetype-plugin' does not exist or no valid version could be found > at > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager. > java:229) > at > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager. > java:91) > at > org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:171) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274) > ... 14 more > [INFO] > > [INFO] Total time: 2 seconds > [INFO] Finished at: Tue Feb 10 21:40:41 PST 2009 > [INFO] Final Memory: 1M/4M > [INFO] > > C:\Documents and Settings\Richard Katz> > Questions: > 1. Is this
[jira] Commented: (MNG-4028) Maven 2 still absolutely does not work
[ http://jira.codehaus.org/browse/MNG-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165064#action_165064 ] Brett Porter commented on MNG-4028: --- does your browser use a proxy setting that you have not configured for maven, per the link shared earlier? > Maven 2 still absolutely does not work > -- > > Key: MNG-4028 > URL: http://jira.codehaus.org/browse/MNG-4028 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.1.0-M1 > Environment: Intel Windows XP 2G Ram >Reporter: Richard Katz >Assignee: Brett Porter > Attachments: settings.xml > > > I originally reported this on Maven 2.0.9 and it was marked as closed. > But the problem still exists in Maven 2.1.0. I have tried the following > 1. Delete the .m2 directory and all its contents. > 2. Use the -U option > 3. Use the -e option. > 4. Run the create Archtype > mvn -e archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app > (and mvn -e -U archetype:create -DgroupId=com.mycompany.app > -DartifactId=my-app) > It simply does not work. > It fails with the same error as I always get in Maven 2.0.9 : > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid > version could be found > Here is the entire trace: > C:\Documents and Settings\Richard Katz>mvn -e -U archetype:create > -DgroupId=com.mycompany.app -DartifactId=my-app > + Error stacktraces are turned on. > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'archetype'. > [INFO] org.apache.maven.plugins: checking for updates from central > [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be > retrieved from repository: central due to an > error: Error transferring file > [INFO] Repository 'central' will be blacklisted > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not > exist or no valid version could be found > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > 'org.apache.maven.plugins:maven-archetype-plugin' doe > s not exist or no valid version could be found > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1303) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1542) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecuto > r.java:405) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > 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.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) > Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: > The plugin 'org.apache.maven.plugins:maven-ar > chetype-plugin' does not exist or no valid version could be found > at > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager. > java:229) > at > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager. > java:91) > at > org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:171) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274) > ... 14 more > [INFO] > > [INFO] Total time: 2 seconds > [INFO] Finished at: Tue Feb 10 21:40:41 PST 2009 > [INFO] Final Memory: 1M/4M > [INFO] > > C:\Documents and
[jira] Commented: (MNG-4028) Maven 2 still absolutely does not work
[ http://jira.codehaus.org/browse/MNG-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165063#action_165063 ] Richard Katz commented on MNG-4028: --- "Caused by: java.net.UnknownHostException: mirrors.ibiblio.org" You're machine cannot reach mirrors.ibiblio.org Yes it can!! http://mirrors.ibiblio.org/ Index of / Icon NameLast modified Size Description[DIR] pub/ 23-May-2007 14:59- Apache Server at mirrors.ibiblio.org Port 80 > Maven 2 still absolutely does not work > -- > > Key: MNG-4028 > URL: http://jira.codehaus.org/browse/MNG-4028 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.1.0-M1 > Environment: Intel Windows XP 2G Ram >Reporter: Richard Katz >Assignee: Brett Porter > Attachments: settings.xml > > > I originally reported this on Maven 2.0.9 and it was marked as closed. > But the problem still exists in Maven 2.1.0. I have tried the following > 1. Delete the .m2 directory and all its contents. > 2. Use the -U option > 3. Use the -e option. > 4. Run the create Archtype > mvn -e archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app > (and mvn -e -U archetype:create -DgroupId=com.mycompany.app > -DartifactId=my-app) > It simply does not work. > It fails with the same error as I always get in Maven 2.0.9 : > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid > version could be found > Here is the entire trace: > C:\Documents and Settings\Richard Katz>mvn -e -U archetype:create > -DgroupId=com.mycompany.app -DartifactId=my-app > + Error stacktraces are turned on. > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'archetype'. > [INFO] org.apache.maven.plugins: checking for updates from central > [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be > retrieved from repository: central due to an > error: Error transferring file > [INFO] Repository 'central' will be blacklisted > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not > exist or no valid version could be found > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > 'org.apache.maven.plugins:maven-archetype-plugin' doe > s not exist or no valid version could be found > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1303) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1542) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecuto > r.java:405) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > 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.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) > Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: > The plugin 'org.apache.maven.plugins:maven-ar > chetype-plugin' does not exist or no valid version could be found > at > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager. > java:229) > at > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager. > java:91) > at > org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:171) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274) > ... 14 more > [INFO] > -
[jira] Commented: (MNG-4028) Maven 2 still absolutely does not work
[ http://jira.codehaus.org/browse/MNG-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165061#action_165061 ] Richard Katz commented on MNG-4028: --- Is this an e-mail address I am supposed to send to? Richard, I suggest you utilise us...@maven.apache.org where you can get better interactive help. You'll need to supply the -X output surrounding the line I quoted above. > Maven 2 still absolutely does not work > -- > > Key: MNG-4028 > URL: http://jira.codehaus.org/browse/MNG-4028 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.1.0-M1 > Environment: Intel Windows XP 2G Ram >Reporter: Richard Katz >Assignee: Brett Porter > Attachments: settings.xml > > > I originally reported this on Maven 2.0.9 and it was marked as closed. > But the problem still exists in Maven 2.1.0. I have tried the following > 1. Delete the .m2 directory and all its contents. > 2. Use the -U option > 3. Use the -e option. > 4. Run the create Archtype > mvn -e archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app > (and mvn -e -U archetype:create -DgroupId=com.mycompany.app > -DartifactId=my-app) > It simply does not work. > It fails with the same error as I always get in Maven 2.0.9 : > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid > version could be found > Here is the entire trace: > C:\Documents and Settings\Richard Katz>mvn -e -U archetype:create > -DgroupId=com.mycompany.app -DartifactId=my-app > + Error stacktraces are turned on. > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'archetype'. > [INFO] org.apache.maven.plugins: checking for updates from central > [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be > retrieved from repository: central due to an > error: Error transferring file > [INFO] Repository 'central' will be blacklisted > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not > exist or no valid version could be found > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > 'org.apache.maven.plugins:maven-archetype-plugin' doe > s not exist or no valid version could be found > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1303) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1542) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecuto > r.java:405) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > 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.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) > Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: > The plugin 'org.apache.maven.plugins:maven-ar > chetype-plugin' does not exist or no valid version could be found > at > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager. > java:229) > at > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager. > java:91) > at > org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:171) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274) > ... 14 more > [INFO] > > [INFO] Total time: 2 seconds > [INFO] Finished at: Tue Feb 10 21:40:41 PST 2009 > [INFO] Final
[jira] Commented: (MNG-4028) Maven 2 still absolutely does not work
[ http://jira.codehaus.org/browse/MNG-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165059#action_165059 ] Richard Katz commented on MNG-4028: --- Please tell me what exactly how I get around a Maven wagon Transfer exception or exactly what I am supposed to observe from either the -U and -X options? http://docs.codehaus.org/display/MAVENUSER/FAQs-1#FAQs-1-novalidversion) I had already tried the -U option and have now tried the -X option as shown below. Here is the result of the -X option: = C:\Documents and Settings\Richard Katz>mvn -X -U -e archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app + Error stacktraces are turned on. Maven version: 2.1.0-M1 Java version: 1.6.0_01 Default locale: en_US, platform encoding: Cp1252 OS name: "windows xp" version: "5.1" arch: "x86" family: "windows" [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\Richard Katz\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'C:\cygwin\usr\local\maven\apache-maven-2.1.0-M1\conf\plugin-r egistry.xml' [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins [INFO] org.apache.maven.plugins: checking for updates from central [DEBUG] Using mirror: http://mirrors.ibiblio.org/pub/mirrors/maven2 (id: ibiblio.org) [DEBUG] Checking for pre-existing User-Agent configuration. [DEBUG] Adding User-Agent configuration. [DEBUG] Connecting to repository: 'ibiblio.org' with url: 'http://mirrors.ibiblio.org/pub/mirrors/maven2'. [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retrieved from repository: central due to an error: Error transferring file [DEBUG] Exception org.apache.maven.wagon.TransferFailedException: Error transferring file at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:136) at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116) at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61) at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:492) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:389) at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetad ataManager.java:97) at org.apache.maven.plugin.DefaultPluginMappingManager.loadPluginMappings(DefaultPluginMappingManager.java:103) at org.apache.maven.plugin.DefaultPluginMappingManager.loadPluginMappings(DefaultPluginMappingManager.java:87) at org.apache.maven.plugin.DefaultPluginMappingManager.getByPrefix(DefaultPluginMappingManager.java:61) at org.apache.maven.plugin.DefaultPluginManager.getPluginDefinitionForPrefix(DefaultPluginManager.java:159) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1718) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecuto r.java:444) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:176) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) 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.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) Caused by: java.net.UnknownHostException: mirrors.ibiblio.org at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177) at java.net.Socket.connect(Socket.java:519) at java.net.Socket.connect(Socket.java:469) at sun.net.NetworkClient.doConnect(NetworkClient.java:157) at sun.net.www.http.HttpClient.openServer(HttpClient.java:388) at sun.net.www.http.HttpClient.openServer(HttpClient.java:515) at sun.net.www.http.HttpClient.(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpClient.java:306) at sun.net.www.http.HttpClient.New(HttpClient.java:318) at sun.ne
[jira] Commented: (MNG-4028) Maven 2 still absolutely does not work
[ http://jira.codehaus.org/browse/MNG-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165058#action_165058 ] Brett Porter commented on MNG-4028: --- "Caused by: java.net.UnknownHostException: mirrors.ibiblio.org" You're machine cannot reach mirrors.ibiblio.org > Maven 2 still absolutely does not work > -- > > Key: MNG-4028 > URL: http://jira.codehaus.org/browse/MNG-4028 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.1.0-M1 > Environment: Intel Windows XP 2G Ram >Reporter: Richard Katz >Assignee: Brett Porter > Attachments: settings.xml > > > I originally reported this on Maven 2.0.9 and it was marked as closed. > But the problem still exists in Maven 2.1.0. I have tried the following > 1. Delete the .m2 directory and all its contents. > 2. Use the -U option > 3. Use the -e option. > 4. Run the create Archtype > mvn -e archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app > (and mvn -e -U archetype:create -DgroupId=com.mycompany.app > -DartifactId=my-app) > It simply does not work. > It fails with the same error as I always get in Maven 2.0.9 : > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid > version could be found > Here is the entire trace: > C:\Documents and Settings\Richard Katz>mvn -e -U archetype:create > -DgroupId=com.mycompany.app -DartifactId=my-app > + Error stacktraces are turned on. > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'archetype'. > [INFO] org.apache.maven.plugins: checking for updates from central > [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be > retrieved from repository: central due to an > error: Error transferring file > [INFO] Repository 'central' will be blacklisted > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not > exist or no valid version could be found > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > 'org.apache.maven.plugins:maven-archetype-plugin' doe > s not exist or no valid version could be found > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1303) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1542) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecuto > r.java:405) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > 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.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) > Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: > The plugin 'org.apache.maven.plugins:maven-ar > chetype-plugin' does not exist or no valid version could be found > at > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager. > java:229) > at > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager. > java:91) > at > org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:171) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274) > ... 14 more > [INFO] > > [INFO] Total time: 2 seconds > [INFO] Finished at: Tue Feb 10 21:40:41 PST 2009 > [INFO] Final Memory: 1M/4M > [INFO] > > C:\Docume
[jira] Reopened: (MNG-4028) Maven 2 still absolutely does not work
[ http://jira.codehaus.org/browse/MNG-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Katz reopened MNG-4028: --- Please tell me what exactly I supposed to observe from the -U and -X options? http://docs.codehaus.org/display/MAVENUSER/FAQs-1#FAQs-1-novalidversion) I had already tried the -U option and have now tried the -X option as shown below. This is really important. Could you express in one or two sentences how to get around this problem? Here is the result of the -X option: = C:\Documents and Settings\Richard Katz>mvn -X -U -e archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app + Error stacktraces are turned on. Maven version: 2.1.0-M1 Java version: 1.6.0_01 Default locale: en_US, platform encoding: Cp1252 OS name: "windows xp" version: "5.1" arch: "x86" family: "windows" [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\Richard Katz\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'C:\cygwin\usr\local\maven\apache-maven-2.1.0-M1\conf\plugin-r egistry.xml' [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins [INFO] org.apache.maven.plugins: checking for updates from central [DEBUG] Using mirror: http://mirrors.ibiblio.org/pub/mirrors/maven2 (id: ibiblio.org) [DEBUG] Checking for pre-existing User-Agent configuration. [DEBUG] Adding User-Agent configuration. [DEBUG] Connecting to repository: 'ibiblio.org' with url: 'http://mirrors.ibiblio.org/pub/mirrors/maven2'. [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retrieved from repository: central due to an error: Error transferring file [DEBUG] Exception org.apache.maven.wagon.TransferFailedException: Error transferring file at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:136) at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116) at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61) at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:492) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:389) at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetad ataManager.java:97) at org.apache.maven.plugin.DefaultPluginMappingManager.loadPluginMappings(DefaultPluginMappingManager.java:103) at org.apache.maven.plugin.DefaultPluginMappingManager.loadPluginMappings(DefaultPluginMappingManager.java:87) at org.apache.maven.plugin.DefaultPluginMappingManager.getByPrefix(DefaultPluginMappingManager.java:61) at org.apache.maven.plugin.DefaultPluginManager.getPluginDefinitionForPrefix(DefaultPluginManager.java:159) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1718) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecuto r.java:444) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:176) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) 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.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) Caused by: java.net.UnknownHostException: mirrors.ibiblio.org at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177) at java.net.Socket.connect(Socket.java:519) at java.net.Socket.connect(Socket.java:469) at sun.net.NetworkClient.doConnect(NetworkClient.java:157) at sun.net.www.http.HttpClient.openServer(HttpClient.java:388) at sun.net.www.http.HttpClient.openServer(HttpClient.java:515) at sun.net.www.http.HttpClient.(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpClient.java:306) at sun.net.www.http.HttpClient.New(HttpClient.java:318) at sun.net.www.protocol.http.HttpURLCo
