[jira] Commented: (MECLIPSE-196) Project "Could not publish to server"
[ http://jira.codehaus.org/browse/MECLIPSE-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137178#action_137178 ] Guillaume commented on MECLIPSE-196: Hello, I am currently restructuring some projets (own lib, webApp, entApp) to be Maven 2 compliant. I use RAD 7 and WebSphere 6.1 appSrv. The projects were already existing within RAD, I just got back the famous application.xml, retrieved the commands / natures / facets configured in RAD configuration files to include them in the POM. And @publishing time I exactly get the same issue: !ENTRY com.ibm.ws.ast.st.v61.core 4 0 2008-06-03 09:13:49.014 !MESSAGE Could not publish to the server. !STACK 0 org.eclipse.emf.common.util.BasicEList$BasicIndexOutOfBoundsException: index=0, size=0 at org.eclipse.emf.common.util.BasicEList.get(Unknown Source) at org.eclipse.jst.j2ee.componentcore.EnterpriseArtifactEdit.getDeploymentDescriptorRoot(Unknown Source) at org.eclipse.jst.j2ee.componentcore.util.EARArtifactEdit.getApplication(Unknown Source) at org.eclipse.jst.j2ee.componentcore.util.EARArtifactEdit.getUtilityModuleReferences(Unknown Source) at com.ibm.etools.wrd.websphere.internal.operations.LooseConfigUpdateOperation.addLooseApplicationContents(Unknown Source) If needed I can attach the pom from the web application and the one from the enterprise app. Thanx & Best Regards, Guillaume. > Project "Could not publish to server" > - > > Key: MECLIPSE-196 > URL: http://jira.codehaus.org/browse/MECLIPSE-196 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.3 > Environment: Eclipse 3.2.1 and WTP 1.5.2, JBoss AS 4.0.4.GA, J2EE > appliaction comprized of an EJB and Web module, all bundled withing an EAR > module. >Reporter: Srepfler Srgjan > > After I modify the EAR project configuration in order to remove problems on > the EAR project (the plugin adds the Java project facet and I must modify by > hand the org.eclipse.wst.common.project.facet.core.xml file in order the > remove it,this should be a separate JIRA I think) my project can get built > (no red decorators on the projects). However, I add the server definition and > when I try to publish the project I get an error "Could not publish to the > server." with the following Exception Stack Trace: > Error > Thu Nov 23 20:56:58 CET 2006 > Could not publish to the server. > org.eclipse.emf.common.util.BasicEList$BasicIndexOutOfBoundsException: > index=0, size=0 > at org.eclipse.emf.common.util.BasicEList.get(BasicEList.java:512) > at > org.eclipse.jst.j2ee.componentcore.EnterpriseArtifactEdit.getDeploymentDescriptorRoot(EnterpriseArtifactEdit.java:154) > at > org.eclipse.jst.j2ee.componentcore.util.EARArtifactEdit.getApplication(EARArtifactEdit.java:291) > at > org.eclipse.jst.j2ee.internal.deployables.J2EEFlexProjDeployable.isNestedJ2EEModule(J2EEFlexProjDeployable.java:528) > at > org.eclipse.jst.j2ee.internal.deployables.J2EEFlexProjDeployable.shouldIncludeUtilityComponent(J2EEFlexProjDeployable.java:135) > at > org.eclipse.wst.web.internal.deployables.ComponentDeployable.addUtilMembers(ComponentDeployable.java:347) > at > org.eclipse.jst.j2ee.internal.deployables.J2EEFlexProjDeployable.members(J2EEFlexProjDeployable.java:193) > at > org.eclipse.jst.server.generic.core.internal.publishers.AbstractModuleAssembler.copyModule(AbstractModuleAssembler.java:160) > at > org.eclipse.jst.server.generic.core.internal.publishers.EarModuleAssembler.assemble(EarModuleAssembler.java:36) > at > org.eclipse.jst.server.generic.core.internal.publishers.AntPublisher.assembleModule(AntPublisher.java:124) > at > org.eclipse.jst.server.generic.core.internal.publishers.AntPublisher.publish(AntPublisher.java:109) > at > org.eclipse.jst.server.generic.core.internal.GenericServerBehaviour.publishModule(GenericServerBehaviour.java:91) > at > org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:676) > at > org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:756) > at > org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:611) > at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:862) > at org.eclipse.wst.server.core.internal.Server.publish(Server.java:850) > at > org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:142) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58) > I don't see people complaining so perhaps it's my fault. Any ideas? If more > info is needed please ask. > I can start the server with no problems and it's on a path with no spaces. > Thanks Srgjan -- This message is automatically generated
[jira] Created: (SCM-383) SVN Tag does not use includes/excludes parameters
SVN Tag does not use includes/excludes parameters
-
Key: SCM-383
URL: http://jira.codehaus.org/browse/SCM-383
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-provider-svn
Affects Versions: 1.1
Reporter: Nils Winkler
The SVN tag command does not use the includes/excludes parameters, instead of
this, fixed patterns ("**", "**/.svn/**") are applied:
https://svn.apache.org/repos/asf/maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnTagCommand.java
{code}
try
{
files = FileUtils.getFiles( fileSet.getBasedir(), "**",
"**/.svn/**", false );
}
catch ( IOException e )
{
throw new ScmException( "Error while executing command.", e );
}
{code}
Desired behavior: The provided includes/excludes patterns should be used
(probably in addition to the default excludes pattern).
--
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: (MSITE-332) Unable to load parent project from a relative path: Could not find the model file '/pom.xml'. for project unknown
[
http://jira.codehaus.org/browse/MSITE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137177#action_137177
]
Lukas Theussl commented on MSITE-332:
-
You probably also have to specify the site plugin version:
{code:xml}
org.apache.maven.plugins
maven-site-plugin
2.0-beta-7-SNAPSHOT
{code}
> Unable to load parent project from a relative path: Could not find the model
> file '/pom.xml'. for project unknown
> --
>
> Key: MSITE-332
> URL: http://jira.codehaus.org/browse/MSITE-332
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site descriptor
>Affects Versions: 2.0-beta-7
>Reporter: Michael Stevens
>Assignee: Dennis Lundberg
> Fix For: 2.0-beta-7
>
>
> Execute site:site
> The plugin seems to look for a pom file in the directory above the project
> directory.
> This started occurring last night for us, using
> maven-site-plugin:2.0-beta-7-SNAPSHOT.
> Note that the project in question uses a parent POM, but does not specify a
> relative path.
> Here is the stack trace:
> [INFO] Unable to load parent project from a relative path: Could not find the
> model file 'c:\workdir\projects\pom.xml'. for project unknown
> [INFO] Parent project loaded from repository.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] SiteToolException: Error reading default site descriptor:
> ${OUTPUTENCODING}
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:230)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
> 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.doxia.tools.SiteToolException: Error reading
> default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:527)
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:226)
> ... 20 more
> Caused by: java.io.UnsupportedEncodingException: ${OUTPUTENCODING}
> at sun.io.Converters.getConverterClass(Converters.java:218)
> at sun.io.Converters.newConverter(Converters.java:251)
> at
> sun.io.ByteToCharConverter.getConverter(ByteToCharConverter
[jira] Created: (MEV-589) Bad checksums on repo1.maven.org
Bad checksums on repo1.maven.org Key: MEV-589 URL: http://jira.codehaus.org/browse/MEV-589 Project: Maven Evangelism Issue Type: Bug Reporter: Laurent Pereira The following artifacts have bad checksums on repo1.maven.org : org/apache/ws/commons/axiom/axiom-dom/1.2.7/axiom-dom-1.2.7.jar org/apache/ws/commons/axiom/axiom-impl/1.2.7/axiom-impl-1.2.7.jar org/apache/ws/commons/axiom/axiom-api/1.2.7/axiom-api-1.2.7.jar -- 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-131) Ability to deploy the content of WEB-INF/classes as a classified artifact
[ http://jira.codehaus.org/browse/MWAR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137205#action_137205 ] Mark Struberg commented on MWAR-131: There was a similar discussion back in early 2006 (related to MWAR-73). Imho, there are 3 different situations which may occur: 1.) We get a WAR file as a dependency which is *not* built with maven and contains all needed dependencies in WEB-INF/lib. In this case, we must not evaluate and use the transitive dependencies we get from this WAR (usually this WAR will not have transitive dependencies at all) This is the current behavior of the maven-war-plugin 2.) We get a WAR file as a dependency which is built with maven and does *not* contain transitive dependencies in WEB-INF/lib. So we could easily take all transitive dependencies and tie them together in the freshly packaged WEB-INF/lib 3.) A mixture between 1.) and 2.) We get a WAR file as a dependency which is built with maven and contains all needed dependencies in WEB-INF/lib In this case, there should be a switch to enable transitive dependency resolution and automatically ignoring all jars in WEB-INF/lib which fits any of the dependencies (otherwise we would end up having different versions of the same jar in WEB-INF/lib). If we find any depending WAR having an attached classes artifact (as of this Jira), we should skip the WEB-INF/classes of those WARs in the war:overlay > Ability to deploy the content of WEB-INF/classes as a classified artifact > - > > Key: MWAR-131 > URL: http://jira.codehaus.org/browse/MWAR-131 > Project: Maven 2.x War Plugin > Issue Type: Improvement >Affects Versions: 2.1-alpha-1 >Reporter: Stephane Nicoll >Assignee: Stephane Nicoll > Fix For: 2.1-alpha-2 > > > If the server-side code of a war project need to be reused somewhere, we need > to deploy the content of the WEB-INF/classes to be able to use it as a > dependency -- 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] Issue Comment Edited: (MNG-3546) command line cannot overwrite pom properties
[ http://jira.codehaus.org/browse/MNG-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137197#action_137197 ] mikosz edited comment on MNG-3546 at 6/3/08 6:11 AM: - > Why is it not ok for system properties to take preference over pom ones? They definitely should, they always did (at least as long as I've been using maven). This is a horrible bug. If someone has a patch for it I'd be really grateful for posting it. Moreover, I'd change the priority of this issue to 'blocker' from 'major' as it changes the logic of builds a lot. was (Author: mikosz): > Why is it not ok for system properties to take preference over pom ones? They definitely should, they always did (at least as long as I've been using maven). This is a horrible bug. If someone has a patch for it I'd be really grateful for posting it. > command line cannot overwrite pom properties > > > Key: MNG-3546 > URL: http://jira.codehaus.org/browse/MNG-3546 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.0.9 >Reporter: Thomas Diesler > > With a pom like this > > localhost > > and a command line like this > mvn -Pjboss422 -Djboss.bind.address=foo clean test-compilecxf.xml > I get a filtered resource like this >address='http://localhost:8080/jaxws-cxf-descriptor' > > implementor='org.jboss.test.ws.jaxws.cxf.descriptor.DescriptorEndpointImpl'> > > > > > > > Note, the bind address is localhost -- 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-3546) command line cannot overwrite pom properties
[ http://jira.codehaus.org/browse/MNG-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137197#action_137197 ] Mikolaj Radwan commented on MNG-3546: - > Why is it not ok for system properties to take preference over pom ones? They definitely should, they always did (at least as long as I've been using maven). This is a horrible bug. If someone has a patch for it I'd be really grateful for posting it. > command line cannot overwrite pom properties > > > Key: MNG-3546 > URL: http://jira.codehaus.org/browse/MNG-3546 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.0.9 >Reporter: Thomas Diesler > > With a pom like this > > localhost > > and a command line like this > mvn -Pjboss422 -Djboss.bind.address=foo clean test-compilecxf.xml > I get a filtered resource like this >address='http://localhost:8080/jaxws-cxf-descriptor' > > implementor='org.jboss.test.ws.jaxws.cxf.descriptor.DescriptorEndpointImpl'> > > > > > > > Note, the bind address is localhost -- 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-3226) Developers and Contributors information is not being inherited
[ http://jira.codehaus.org/browse/MNG-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137211#action_137211 ] Ruth Ziegler commented on MNG-3226: --- I've been running into this issue today while I wanted to set up an organizational POM. Since we have internal and external developers working on a project I wanted to split up the developers into the organizational and project POM. The organizational POM shall include the internal developers who work on several projects. The external developers however shouldn't be part of the organizational POM since they only work on a project-basis. Therefore I included these developers in the relevant project POM. I'm using Maven 2.0.9 and this issue still seems to be unfixed. Is there any chance it will be fixed soon? > Developers and Contributors information is not being inherited > -- > > Key: MNG-3226 > URL: http://jira.codehaus.org/browse/MNG-3226 > Project: Maven 2 > Issue Type: Bug > Components: Inheritance and Interpolation >Affects Versions: 2.0.7 >Reporter: Brad Szabo > Fix For: 2.0.x > > > The developers and contributors information is not being merged into the > effective POM of child projects. > According to the Project Inheritance section of the following two POM > references, this info should be merged. > http://maven.apache.org/guides/introduction/introduction-to-the-pom.html > http://maven.apache.org/pom.html#Inheritance -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MASSEMBLY-285) regression: duplicate files added to the assembly
[ http://jira.codehaus.org/browse/MASSEMBLY-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137228#action_137228 ] Andrei Solntsev commented on MASSEMBLY-285: --- I have a project with several submodules, each of them creates a ZIP during build. When I build submodules one by one, they produce correct ZIPs. But when i build the entire project with all submodules, their ZIPs contain duplicated entries. > regression: duplicate files added to the assembly > - > > Key: MASSEMBLY-285 > URL: http://jira.codehaus.org/browse/MASSEMBLY-285 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-1 >Reporter: Brett Porter >Priority: Blocker > Fix For: 2.2-beta-3 > > > I found that it was possible to add a file twice to the assembly through > different filesets (a zip file) so that when it extracted it prompted for > overwrite. > It should error out or collapse the entries (as 2.1 did). -- 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-3422) [regression] deploy:deploy-file does not work
[
http://jira.codehaus.org/browse/MNG-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137242#action_137242
]
Adam Leggett commented on MNG-3422:
---
I discovered the same issue when using 2.1-20080302.021203-37 of the embedder.
Seems to me that the injected repositoryLayouts in DeployFileMojo does not
contain any valid layouts.
Short term fix for us was to bring the plugin inhouse and instanciate a default
layout within execute():
ArtifactRepositoryLayout layout;
layout = ( ArtifactRepositoryLayout ) repositoryLayouts.get( repositoryLayout );
//
//FIX: issue when using maven-artifact-3.0-SNAPSHOT
//The plexus injected repositoryLayouts does not contain any valid layouts
//
if( layout == null )
{
layout = new DefaultRepositoryLayout();
}
> [regression] deploy:deploy-file does not work
> -
>
> Key: MNG-3422
> URL: http://jira.codehaus.org/browse/MNG-3422
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.1-alpha-1
>Reporter: Brett Porter
> Fix For: 2.1-alpha-1
>
>
> mvn deploy:deploy-file -Dfile=test.sh -DrepositoryId=testing
> -DartifactId=artifactId -DgroupId=groupId -Dversion=1.0 -Dpackaging=jar
> -Durl=http://vesuvius.devzuz.com/private/devzuz/releases
> [INFO] Searching repository for plugin with prefix: 'deploy'.
> [INFO] Attempting to resolve a version for plugin:
> org.apache.maven.plugins:maven-deploy-plugin using meta-version: LATEST
> [INFO] Using version: 2.3 of plugin:
> org.apache.maven.plugins:maven-deploy-plugin
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Building Maven Default Project
> [INFO]
> [INFO] Id: org.apache.maven:super-pom:jar:2.1
> [INFO] task-segment: [deploy:deploy-file] (aggregator-style)
> [INFO]
>
> [INFO] [deploy:deploy-file]
> [INFO] artifact groupId:artifactId: checking for updates from testing
> ---
> constituent[0]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/aspectjrt-1.5.3.jar
> constituent[1]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/backport-util-concurrent-3.0.jar
> constituent[2]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/commons-cli-1.0.jar
> constituent[3]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/doxia-sink-api-1.0-alpha-9.jar
> constituent[4]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/jsch-0.1.27.jar
> constituent[5]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/jtidy-4aug2000r7-dev.jar
> constituent[6]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-artifact-3.0-SNAPSHOT.jar
> constituent[7]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-core-2.1-SNAPSHOT.jar
> constituent[8]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-embedder-2.1-SNAPSHOT.jar
> constituent[9]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-lifecycle-2.1-SNAPSHOT.jar
> constituent[10]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-model-2.1-SNAPSHOT.jar
> constituent[11]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-plugin-api-2.1-SNAPSHOT.jar
> constituent[12]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-profile-2.1-SNAPSHOT.jar
> constituent[13]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-project-2.1-SNAPSHOT.jar
> constituent[14]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-reporting-api-2.1-SNAPSHOT.jar
> constituent[15]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/plexus-container-default-1.0-alpha-44.jar
> constituent[16]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/plexus-interactivity-api-1.0-alpha-6.jar
> constituent[17]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/plexus-utils-1.5.1.jar
> constituent[18]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/retrotranslator-runtime-1.2.1.jar
> constituent[19]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-file-1.0-beta-2.jar
> constituent[20]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-http-lightweight-1.0-beta-2.jar
> constituent[21]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-http-shared-1.0-beta-2.jar
> constituent[22]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-provider-api-1.0-beta-2.jar
> constituent[23]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh-1.0-beta-2.jar
> constituent[24]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh-common-1.0-beta-2.jar
> constituent[25]:
> file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh-external-1.0-beta-2.
[jira] Created: (MNG-3612) property in settings.xml not interpolated when resolving parent POM from remote repository
property in settings.xml not interpolated when resolving parent POM from remote
repository
--
Key: MNG-3612
URL: http://jira.codehaus.org/browse/MNG-3612
Project: Maven 2
Issue Type: Bug
Components: Inheritance and Interpolation
Affects Versions: 2.0.9
Environment: Java 1.5.0_11, Windows XP
Reporter: Pat Podenski
Attachments: pom.xml, pom.xml, settings.xml
The objective was to use a property in the settings.xml within a profile. This
property represents the remote repository host/port number. This is so that
multiple entries of the host/port in the settings.xml profiles do not need to
be edited when the host/port value changes.
When working in a project whose parent POM is not installed in the local
repository, download of the parent POM from the remote repository fails. If the
host/port literal value is substituted in the repository element contained in
the settings.xml profile, the download succeeds.
If the parent POM is installed in the local repository resolution succeeds (of
course we don't need the remote repository in this case unless trying to update
the SNAPSHOT).
Attached example files.
1 - settings.xml file used in ~/.m2/
2 - pom.xml for base-pom
3 - pom.xml for child
To reproduce this problem:
1) deploy parent POM to remote repository (I use Artifactory which has an
upload utility, so I didn't need to install parent POM in the local repository)
2) verify that parent POM is not in the local repository
3) try a 'mvn clean' or similar command in the child project - this operation
fails (see below)
4) If the literal host/port value is put into the settings.xml repository
element instead of ${repo-host}, the operation will succeed
[INFO] Scanning for projects...
[INFO] snapshot com.foo:base-pom:1-SNAPSHOT: checking for updates from central
[WARNING] repository metadata for: 'snapshot com.foo:base-pom:1-SNAPSHOT' could
not be retrieved
from repository: central due to an error: Error transferring file
[INFO] Repository 'central' will be blacklisted
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Failed to resolve artifact.
GroupId: com.foo
ArtifactId: base-pom
Version: 1-SNAPSHOT
Reason: Unable to download the artifact from any repository
com.foo:base-pom:pom:1-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO]
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
com.foo:base-pom for project:
com.bar:child:jar:0.0.1-SNAPSHOT for project com.bar:child:jar:0.0.1-SNAPSHOT
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
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: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.project.ProjectBuildingException: Cannot find
parent: com.foo:base-pom f
or project: com.bar:child:jar:0.0.1-SNAPSHOT for project
com.bar:child:jar:0.0.1-SNAPSHOT
at
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBu
ilder.java:1370)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuil
der.java:821)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMa
venProjectBuilder.java:506)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java
:198)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
... 11 more
Caused by: org.apache.maven.project.ProjectBuildingException: POM
'com.foo:base-pom' not found in re
pository: Unable to download the artifact from any repository
com.foo:base-pom:pom:1-SNAPSHOT
from the specified remote repositories:
centra
[jira] Commented: (MNG-3314) offline build not running, when having SNAPSHOT dependencies
[ http://jira.codehaus.org/browse/MNG-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137258#action_137258 ] John Casey commented on MNG-3314: - I've added an integration test to the Maven suite, to try to capture this failure so I can debug/fix it. However, the test case doesn't fail with either 2.0.7 or 2.0.9... The test case is here: http://svn.apache.org/repos/asf/maven/core-integration-testing/trunk/core-integration-tests/src/test/resources/mng-3314-offlineSnapshots and the JUnit controller class is here: http://svn.apache.org/repos/asf/maven/core-integration-testing/trunk/core-integration-tests/src/test/java/org/apache/maven/integrationtests/MavenITmng3314OfflineSnapshotsTest.java Can someone please let me know what I'm doing wrong here? In the comment two above this one, that output would seem to be correct, if the dependency weren't present in the local repository, and nobody else has given any concrete detail for this error in terms of console output or test-case projects. Without more information, I'm going to close this bug as CANNOT_REPRODUCE. > offline build not running, when having SNAPSHOT dependencies > > > Key: MNG-3314 > URL: http://jira.codehaus.org/browse/MNG-3314 > Project: Maven 2 > Issue Type: Bug > Components: General >Affects Versions: 2.0.7 >Reporter: Matthias Weßendorf >Priority: Critical > Fix For: 2.0.10 > > > am having troubles with > mvn ... -o > (with maven 2.0.7) > says not able to download (but, really, the file is in my local repo) > The dependency is a -SNAPSHOT (for what's worth) > Luckily, when traveling by train, I had maven 2.0.4 on my box as well. > A change to use 2.0.4 works fine. > So, is this an already know bug in 2.0.7 ? > To my understanding it is a bug, since offline just shouldn't try to get a > newer > SNAPSHOT, perhaps I am wrong. > I know that relying on SNAPSHOTs can be dangerous, but from -o I would expect > just not checking for new stuff. > and... for some reasons, sometimes, > it just downloads a new SNAPSHOT. > That is a pain, when you are "maintaining" the same snapshot on your > box, but the build just goes ahead and actually downloads a version. -- 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: (MAVENUPLOAD-2093) RabbitMQ Java Client For AMQP
RabbitMQ Java Client For AMQP - Key: MAVENUPLOAD-2093 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2093 Project: Maven Upload Requests Issue Type: Wish Reporter: Ben Hood "com.rabbitmq","[EMAIL PROTECTED]:/home/maven/rabbitmq-java-client/","rsync_ssh","Ben Hood","[EMAIL PROTECTED]" I am a developer at LShift who is the company that maintains RabbitMQ (http://www.rabbitmq.com/), which you can see on the site. Please note that we do not have any links to the development team on the site, but you can see from whois that our infrastructure manager Stuart Mottram is the domain owner (http://www.whois.net/whois_new.cgi?d=rabbitmq&tld=com). I have set up the rsync server with your public key. Please let me know if you need any further identification. -- 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: (ARCHETYPE-135) add a variabl containing package in a path format
[ http://jira.codehaus.org/browse/ARCHETYPE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raphaël Piéroni closed ARCHETYPE-135. - Resolution: Cannot Reproduce This was inadvertently reopen > add a variabl containing package in a path format > - > > Key: ARCHETYPE-135 > URL: http://jira.codehaus.org/browse/ARCHETYPE-135 > Project: Maven Archetype > Issue Type: Improvement >Affects Versions: 2.0-alpha-2 >Reporter: Dominique Jean-Prost > > Actually, there is a variable "package" than can be used in the file during > generation. > It could be great if there was another variable than contained the package in > a path format. Example : > package = com.foo > packageInPathFormat=com/foo > This new variable could be used in resources path. -- 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: (ARCHETYPE-168) CLONE -Unable to locate custom archetypes : archetype repository not resolved.
[ http://jira.codehaus.org/browse/ARCHETYPE-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raphaël Piéroni closed ARCHETYPE-168. - Resolution: Cannot Reproduce I tried the command Milos described. It worked fine. François, if you are still interrested in this issue, please open a new describing your problem. > CLONE -Unable to locate custom archetypes : archetype repository not resolved. > -- > > Key: ARCHETYPE-168 > URL: http://jira.codehaus.org/browse/ARCHETYPE-168 > Project: Maven Archetype > Issue Type: Bug > Components: Creator >Affects Versions: 2.0-alpha-1 > Environment: Linux Fedora 8, JDK 1.5, Maven 2.0.7 >Reporter: Francois Le Droff >Assignee: Milos Kleint > > When the following command is issued: > mvn archetype:create -DarchetypeGroupId=org.apache.cocoon > -DarchetypeArtifactId=cocoon-22-archetype-block > -DarchetypeVersion=1.0.0-RC2 -DgroupId=org.cocoondev -DartifactId=geoid-core > Maven 2.0.7 reports this error: > [INFO] [archetype:create] > [WARNING] No archetype repository found. > [WARNING] Specified archetype not found. > Choose archetype: > 1: internal -> appfuse-basic-jsf (AppFuse archetype for creating a web > application with Hibernate, Spring and JSF) > ... > This was solved by specifying use of the 1.0-alpha-7 archetype version in > command line: > org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create .. -- 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: (ARCHETYPE-178) omitting the package in the prompts leaves an unhelpful error message
[ http://jira.codehaus.org/browse/ARCHETYPE-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raphaël Piéroni closed ARCHETYPE-178. - Resolution: Fixed Fix Version/s: 2.0-alpha-4 Fixed since revision 662853 > omitting the package in the prompts leaves an unhelpful error message > - > > Key: ARCHETYPE-178 > URL: http://jira.codehaus.org/browse/ARCHETYPE-178 > Project: Maven Archetype > Issue Type: Bug > Components: Generator >Affects Versions: 2.0-alpha-3 >Reporter: Brett Porter > Fix For: 2.0-alpha-4 > > > Define value for package: : > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] : > org.apache.maven.archetype.exception.ArchetypeGenerationConfigurationFailure: > The archetype generation must be configured here > The archetype generation must be configured here > The archetype generation must be configured here > I believe > - the error message should be better, and prompt again > - the package should be defaulting to groupId? -- 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: (ARCHETYPE-177) NullPointerException generating archetype when mirrors are in settings.xml
[ http://jira.codehaus.org/browse/ARCHETYPE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raphaël Piéroni closed ARCHETYPE-177. - Resolution: Not A Bug In the settings.xml file, when a mirror is defined, the child element mirrorOf seems to be mandatory > NullPointerException generating archetype when mirrors are in settings.xml > -- > > Key: ARCHETYPE-177 > URL: http://jira.codehaus.org/browse/ARCHETYPE-177 > Project: Maven Archetype > Issue Type: Bug > Components: Archetypes, Generator > Environment: Windows XP Pro >Reporter: Frank Adcock > > When attempting to generate any archetype from the mvn archetype:generate > command I get a null pointer exception thrown if I have mirrors defined in my > settings.xml file. I believe there is a related issue where mvn package will > also get a null pointer exception if a repository specified in the project > pom does not have a matching mirror id in the settings.xml. However, the > stack trace for the archetype generation is: > Choose a number: > (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/19/20/21/22/23/2 > 4/25/26/27/28/29/30/31/32/33/34/35/36/37/38/39/40/41/42/43/44) 15: : 6 > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] : java.lang.NullPointerException > null > [INFO] > > [INFO] Trace > org.apache.maven.BuildFailureException > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:579) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone > Goal(DefaultLifecycleExecutor.java:512) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > ltLifecycleExecutor.java:482) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > dleFailures(DefaultLifecycleExecutor.java:330) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > ts(DefaultLifecycleExecutor.java:227) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > fecycleExecutor.java:142) > 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(DelegatingMethodAcces > sorImpl.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.MojoFailureException > at > org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execu > te(CreateProjectFromArchetypeMojo.java:202) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > nManager.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:558) > ... 16 more > [INFO] > > [INFO] Total time: 7 seconds > [INFO] Finished at: Wed May 28 17:49:39 EST 2008 > [INFO] Final Memory: 8M/14M > [INFO] > > C:\Documents and Settings\frank\My Documents\Development\Sandbox>mvn -v > Maven version: 2.0.9 > Java version: 1.5.0_08 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" > The mirrored settings from the settings.xml file are: > > > public-snapshots > public-snapshots > > http://maven.ho.bushlife.com.au:8081/nexus/content/groups/public-snapshots > > > nexus-central > > http://maven.ho.bushlife.com.au:8081/nexus/content/groups/public > central > > > nexus-maven-repo > > http://maven.ho.bushlife.com.au:8081/nexus/content/groups/public > maven-repo > > >
[jira] Closed: (ARCHETYPE-59) archetype plugin doesn't use private plugin repository configured in /conf/settings.xml
[ http://jira.codehaus.org/browse/ARCHETYPE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raphaël Piéroni closed ARCHETYPE-59. Resolution: Fixed Closed as from user comment (bouiaw). Please reopen with up to date information if this issue still appear in latest version of the archetype plugin > archetype plugin doesn't use private plugin repository configured in > /conf/settings.xml > --- > > Key: ARCHETYPE-59 > URL: http://jira.codehaus.org/browse/ARCHETYPE-59 > Project: Maven Archetype > Issue Type: Bug > Components: Archetypes >Affects Versions: 1.0-alpha-4 > Environment: windows xp > jdk 1.5.0_09-b01 >Reporter: Martin Testrot > > I configured the file /conf/settings to use a local, private > plugin repository to prevent uncontrolled download from the official central > repository at http://repo1.maven.org/maven2. This works fine except in the > case I call the archetype plugin (archetype:create). In this case the > settings.xml is ignored and all plugins are downloaded from the central > repository at maven.org. > I observed the same when calling mvn help:active-profiles in a directory that > doesn't contain a pom.xml file. > If I place a dummy pom.xml file in this directory the settings.xml are used > and everything is fine. But if I use this trick with the archetype plugin the > newly created project (creation via archetype) is configured as a child of my > dummy pom (pom.xml contains parent section with dummy pom). I the case of a > dummy pom this is not intended. > So i would be nice if you can fix the archtype plugin to use the configured > settings.xml. I really would like to use this plugin, because it would help a > lot to standardize a common project layout for our developers. This is a > majour reason for choosing maven2. > Greetings, > Martin > Here is the relevant section of my settings.xml: > ... > > > > private-repo > > > > central > private plugin repository > > http://localserver/mvn-repos/maven-plugin > > true > > daily > > > false > > > > > > > > private-repo > > ... -- 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: (ARCHETYPE-35) Possibility to change the resource destination names
[ http://jira.codehaus.org/browse/ARCHETYPE-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raphaël Piéroni closed ARCHETYPE-35. Resolution: Cannot Reproduce This issue appears to be fixed since at least the version 2.0-alpha-3 of the archetype plugin. Please reopen with fresher data if this issue is still a problem. > Possibility to change the resource destination names > > > Key: ARCHETYPE-35 > URL: http://jira.codehaus.org/browse/ARCHETYPE-35 > Project: Maven Archetype > Issue Type: New Feature >Reporter: Alexandre Poitras > Attachments: MNG-35-archetype.patch > > > It would be useful to be able to specify new destionation names to the copied > resources so their name can be determined dynamically. For instance, let's > may my archetype produce a multi-modules project. I name my project myproject > (original, eh?). Now this project have a children that I would like to be > call myproject-presentation and not only presentation. > I think it's not doable at the moment. -- 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: (ARCHETYPE-176) Cannot use "-DarchetypeRepository" if you have * in your settings.xml file
[ http://jira.codehaus.org/browse/ARCHETYPE-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raphaël Piéroni closed ARCHETYPE-176. - Resolution: Not A Bug Using "mirrorOf central " in my settings.xml and pointing to my nexus, I had the following behaviour, which is intended. Maven downloads from the intended repository. C:\Devs\integration-tests\proficio-usage>mvn archetype:generate -DarchetypeRepository=http://somewhere.net -DarchetypeGroupId=ogr.aze.rez -DarchetypeArtifactId=aqd -DarchetypeVersion=5 [INFO] [archetype:generate] [INFO] Generating project in Interactive mode [INFO] Archetype defined by properties Downloading: http://somewhere.net/ogr/aze/rez/aqd/5/aqd-5.jar 57K downloaded [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '8f1f4c7559e3edc224cac5bd3c4f7fc55d308101'; remote = 'http://somewhere.net/ogr/aze/rez/aqd/5/aqd-5.jar 57K downloaded [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'fae62c29661cf18998c443c0c05ae2be365cadb8'; remote = 'mvn archetype:generate -DarchetypeRepository=http://somewhere.net -DarchetypeGroupId=ogr.aze.rez -DarchetypeArtifactId=456aqd -DarchetypeVersion=556 [INFO] [archetype:generate] [INFO] Generating project in Interactive mode [INFO] Archetype defined by properties Downloading: http://localhost:8081/nexus/content/groups/public/ogr/aze/rez/456aqd/556/456aqd-556.jar Downloading: http://localhost:8081/nexus/content/groups/public/ogr/aze/rez/456aqd/556/456aqd-556.jar [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] : org.apache.maven.archetype.exception.UnknownArchetype: The desired archetype does not exist (ogr.aze.rez:456aqd:556) As a conclusion one could think "mirrorOf *" is over zealous. Maybe by selecting the mirrors and which repositories are proxied in nexus this problem could be avoided. > Cannot use "-DarchetypeRepository" if you have * in your > settings.xml file > > > Key: ARCHETYPE-176 > URL: http://jira.codehaus.org/browse/ARCHETYPE-176 > Project: Maven Archetype > Issue Type: Bug > Components: Creator, Generator >Affects Versions: 2.0-alpha-3 > Environment: Java 6 > Maven 2.0.9 >Reporter: Jeff Campbell > > I'm using the following command to create a new project from a custom > archetype from a 3rd party Maven repo (only > the relevant portion of the command is below): > mvn archetype:generate -DarchetypeRepository=http://somehost.com/mvnrepo > .(other -D params for thecustom archetype)... > But, because I have the following in my settings.xml file, I cannot > access the repository specified by the "-DarchetypeRepository": > > > my.nexus > Nexus Mirror > http://somehost:8081/nexus/content/groups/public > * > > > Work around(s): > 1. Don't use section all together in the settings.xml file. > 2. List every single possible maven repo site mirror, in Nexus, that I can > possibly think of to hopefully cover every possible custom archetype that > will ever be used? (yikes!) -- 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: (ARCHETYPE-89) archetypeng:create doesn't use configured repos to find artifacts
[
http://jira.codehaus.org/browse/ARCHETYPE-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raphaël Piéroni closed ARCHETYPE-89.
Resolution: Incomplete
This issue is no longer accurate.
Brett, can you please create a new issue with your particular problem,
if this is still a problem. Thanks.
> archetypeng:create doesn't use configured repos to find artifacts
> -
>
> Key: ARCHETYPE-89
> URL: http://jira.codehaus.org/browse/ARCHETYPE-89
> Project: Maven Archetype
> Issue Type: Bug
>Affects Versions: 2.0-alpha-2
>Reporter: Brian Fox
>Assignee: Raphaël Piéroni
>
> I deployed a snapshot of the archetype and create isn't finding it even
> though i have the maven-snapshot repo in my settings. A secondary problem is
> that if nothing is found, you get into an infinite loop where it asks you to
> pick a number that isn't there.
> {noformat}
> $ mvn.bat archetypeng:create
> Using maven.home=c:\Program Files\maven2\bin\\..
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'archetypeng'.
> [INFO]
>
> [INFO] Building Maven Default Project
> [INFO]task-segment: [archetypeng:create] (aggregator-style)
> [INFO]
>
> [INFO] Preparing archetypeng:create
> [INFO] [archetypeng:select-archetype]
> Choose group:
> 1: org.apache.maven.archetypes
> 2: org.codehaus.mojo.archetypes
> 3: org.apache.maven.its
> Choose a number: (1/2/3): 3
> [INFO] org.apache.maven.its: checking for updates from central
> Choose archetype:
> Choose a number: :
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (ARCHETYPE-179) repo1 is hardcoded into internal catalog
repo1 is hardcoded into internal catalog Key: ARCHETYPE-179 URL: http://jira.codehaus.org/browse/ARCHETYPE-179 Project: Maven Archetype Issue Type: Bug Components: Generator Reporter: Brett Porter The repository URL should not be hardcoded into the internal catalog - it is looking at repo1, when really it should be looking at the repository defined by central (ie, the one in my settings file that points to my internal repository proxy). So, it needs to honour settings. I believe the catalog should specify an id and a url - and if the id exists use that instead (and if not, fall back to the URL). -- 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-3612) property in settings.xml not interpolated when resolving parent POM from remote repository
[
http://jira.codehaus.org/browse/MNG-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pat Podenski updated MNG-3612:
--
Attachment: parent-and-child.zip
The two projects: base-pom and child in a zip file for convenience.
Use the separately attached settings.xml file in conjunction with these two
projects to reproduce this problem.
> property in settings.xml not interpolated when resolving parent POM from
> remote repository
> --
>
> Key: MNG-3612
> URL: http://jira.codehaus.org/browse/MNG-3612
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 2.0.9
> Environment: Java 1.5.0_11, Windows XP
>Reporter: Pat Podenski
> Attachments: parent-and-child.zip, pom.xml, pom.xml, settings.xml
>
>
> The objective was to use a property in the settings.xml within a profile.
> This property represents the remote repository host/port number. This is so
> that multiple entries of the host/port in the settings.xml profiles do not
> need to be edited when the host/port value changes.
> When working in a project whose parent POM is not installed in the local
> repository, download of the parent POM from the remote repository fails. If
> the host/port literal value is substituted in the repository element
> contained in the settings.xml profile, the download succeeds.
> If the parent POM is installed in the local repository resolution succeeds
> (of course we don't need the remote repository in this case unless trying to
> update the SNAPSHOT).
> Attached example files.
> 1 - settings.xml file used in ~/.m2/
> 2 - pom.xml for base-pom
> 3 - pom.xml for child
> To reproduce this problem:
> 1) deploy parent POM to remote repository (I use Artifactory which has an
> upload utility, so I didn't need to install parent POM in the local
> repository)
> 2) verify that parent POM is not in the local repository
> 3) try a 'mvn clean' or similar command in the child project - this operation
> fails (see below)
> 4) If the literal host/port value is put into the settings.xml repository
> element instead of ${repo-host}, the operation will succeed
> [INFO] Scanning for projects...
> [INFO] snapshot com.foo:base-pom:1-SNAPSHOT: checking for updates from central
> [WARNING] repository metadata for: 'snapshot com.foo:base-pom:1-SNAPSHOT'
> could not be retrieved
> from repository: central due to an error: Error transferring file
> [INFO] Repository 'central' will be blacklisted
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] Failed to resolve artifact.
> GroupId: com.foo
> ArtifactId: base-pom
> Version: 1-SNAPSHOT
> Reason: Unable to download the artifact from any repository
> com.foo:base-pom:pom:1-SNAPSHOT
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> [INFO]
>
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
> com.foo:base-pom for project:
> com.bar:child:jar:0.0.1-SNAPSHOT for project com.bar:child:jar:0.0.1-SNAPSHOT
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
> 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: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.project.ProjectBuildingException: Cannot find
> parent: com.foo:base-pom f
> or project: com.bar:child:jar:0.0.1-SNAPSHOT for project
> com.bar:child:jar:0.0.1-SNAPSHOT
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBu
> ilder.java:1370)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuil
> der.java:821)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMa
> venProjectBuilder.java:506)
> at
>
[jira] Commented: (MNG-2695) -o makes build fail for snapshot plugins
[
http://jira.codehaus.org/browse/MNG-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137279#action_137279
]
John Casey commented on MNG-2695:
-
I've just added an integration test to Maven's suite that attempts to capture
this failure condition, but I haven't been able to reproduce the problem yet.
I've tried mainly with 2.0.9 and 2.0.7.
The integration test projects are here:
http://svn.apache.org/repos/asf/maven/core-integration-testing/trunk/core-integration-tests/src/test/resources/mng-2695-offlinePluginSnapshots
And the JUnit TestCase controller is here:
http://svn.apache.org/repos/asf/maven/core-integration-testing/trunk/core-integration-tests/src/test/java/org/apache/maven/integrationtests/MavenITmng2695OfflinePluginSnapshotsTest.java
If this is still a problem, can someone post a sample project that will
reproduce the problem, along with any specific details about expressing it? If
not, I'm going to close this CANNOT_REPRODUCE, as I feel like this integration
test does a decent job of covering the basic use case surrounding plugin
snapshots and offline mode.
> -o makes build fail for snapshot plugins
>
>
> Key: MNG-2695
> URL: http://jira.codehaus.org/browse/MNG-2695
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 2.0-alpha-1
>Reporter: Kenney Westerhof
> Fix For: 2.1
>
>
> I've set the maven-eclipse-plugin version to 2.3-SNAPSHOT in my root pom.
> When I run without -o, the build works fine. All 100 non-deployed
> snapshot artifacts are resolved 100 times from all of my 10 remote
> repo's so the build takes ages.
> After a succesful build, I run with -o and the build fails:
> {noformat}
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Failed to resolve artifact.
> GroupId: org.apache.maven.plugins
> ArtifactId: maven-eclipse-plugin
> Version: 2.3-SNAPSHOT
> Reason: System is offline.
> org.apache.maven.plugins:maven-eclipse-plugin:pom:2.3-SNAPSHOT
> NOTE: Maven is executing in offline mode. Any artifacts not already in your
> local
> repository will be inaccessible.
> [INFO]
>
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Unable to build
> project for plugin 'org.apache.maven.plugins:maven-eclipse-plugin': POM
> 'org.apache.maven.
> plugins:maven-eclipse-plugin' not found in repository: System is offline.
> org.apache.maven.plugins:maven-eclipse-plugin:pom:2.3-SNAPSHOT
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1269)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1517)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:381)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:135)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:393)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:182)
> at
> org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:746)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:394)
> 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.InvalidPluginException: Unable to build
> project for plugin 'org.apache.maven.plugins:maven-eclipse-plugin': POM
> 'org.apache.mav
> en.plugins:maven-eclipse-plugin' not found in repository: System is offline.
> org.apache.maven.plugins:maven-eclipse-plugin:pom:2.3-SNAPSHOT
> at
> org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:266)
> at
> org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:184)
> at
> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:164)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1252)
>
[jira] Commented: (MSITE-332) Unable to load parent project from a relative path: Could not find the model file '/pom.xml'. for project unknown
[
http://jira.codehaus.org/browse/MSITE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137280#action_137280
]
Michael Stevens commented on MSITE-332:
---
I did indeed try that.. I tried several previous beta versions of the site
plugin and the project info plugin. But, regardless of the site plugin version
beta-1 through beta-6, and the project info plugin version 2.0 or 2.0.1, I
either saw the doxia/logging classpath problem, or another complicated error
message I didn't want to dig into (sorry).
What I am seeing is that when the dependency for
org.apache.maven.doxia:doxia-logging-api:1.0-beta-1-SNAPSHOT is resolved, maven
doesn't seem to care about the jar file, only the pom.
If I remove doxia-logging-api artifacts from my local repository, only the pom
is retrieved (e.g. doxia-logging-api-1.0-beta-1-20080531.193054-6.pom), not the
jar file (doxia-logging-api-1.0-beta-1-20080531.193054-6.jar). Even if I
manually put the matching snapshot jar in place with the downloaded pom in my
repo, the NoClassDef problem still occurs.
Assuming no one else can reproduce the problem (it occurs with a generic
project created with the archetype:create goal), I'm guessing there's something
weird happening in my environment.
> Unable to load parent project from a relative path: Could not find the model
> file '/pom.xml'. for project unknown
> --
>
> Key: MSITE-332
> URL: http://jira.codehaus.org/browse/MSITE-332
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site descriptor
>Affects Versions: 2.0-beta-7
>Reporter: Michael Stevens
>Assignee: Dennis Lundberg
> Fix For: 2.0-beta-7
>
>
> Execute site:site
> The plugin seems to look for a pom file in the directory above the project
> directory.
> This started occurring last night for us, using
> maven-site-plugin:2.0-beta-7-SNAPSHOT.
> Note that the project in question uses a parent POM, but does not specify a
> relative path.
> Here is the stack trace:
> [INFO] Unable to load parent project from a relative path: Could not find the
> model file 'c:\workdir\projects\pom.xml'. for project unknown
> [INFO] Parent project loaded from repository.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] SiteToolException: Error reading default site descriptor:
> ${OUTPUTENCODING}
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:230)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
>
[jira] Created: (MNG-3613) JSTL 1.2 not installed in repo correctly
JSTL 1.2 not installed in repo correctly Key: MNG-3613 URL: http://jira.codehaus.org/browse/MNG-3613 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Reporter: Frank Adcock JSTL 1.2 is located at http://repo1.maven.org/maven2/javax/servlet/jstl/1.2 It is not referenced in the maven metadata information for the directory http://repo1.maven.org/maven2/javax/servlet/jstl/ It does not have any metadata information in the 1.2 directory. There is no link to the top level jstl directory http://repo1.maven.org/maven2/jstl/ It appears as if it was not installed correctly into the repo. Apologies if this is filed against the wrong project or category. -- 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: (ARCHETYPE-177) NullPointerException generating archetype when mirrors are in settings.xml
[ http://jira.codehaus.org/browse/ARCHETYPE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frank Adcock reopened ARCHETYPE-177: Why is this not a defect. As a user you receive a null pointer exception because of something missing in the settings.xml file. At the very least you should receive an error message indicating the problem. If you can have a situation where the mirrorOf setting is optional, then it should not be throwing a null pointer exception but handling it better. To my mind there is a problem, whether the priority needs to be adjusted to suit the impact, but certainly the way it is it takes a considerable amount of time to figure out what the problem is, and it is not necessarily obvious that the mirrorOf field is the problem. > NullPointerException generating archetype when mirrors are in settings.xml > -- > > Key: ARCHETYPE-177 > URL: http://jira.codehaus.org/browse/ARCHETYPE-177 > Project: Maven Archetype > Issue Type: Bug > Components: Archetypes, Generator > Environment: Windows XP Pro >Reporter: Frank Adcock > > When attempting to generate any archetype from the mvn archetype:generate > command I get a null pointer exception thrown if I have mirrors defined in my > settings.xml file. I believe there is a related issue where mvn package will > also get a null pointer exception if a repository specified in the project > pom does not have a matching mirror id in the settings.xml. However, the > stack trace for the archetype generation is: > Choose a number: > (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/19/20/21/22/23/2 > 4/25/26/27/28/29/30/31/32/33/34/35/36/37/38/39/40/41/42/43/44) 15: : 6 > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] : java.lang.NullPointerException > null > [INFO] > > [INFO] Trace > org.apache.maven.BuildFailureException > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:579) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone > Goal(DefaultLifecycleExecutor.java:512) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > ltLifecycleExecutor.java:482) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > dleFailures(DefaultLifecycleExecutor.java:330) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > ts(DefaultLifecycleExecutor.java:227) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > fecycleExecutor.java:142) > 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(DelegatingMethodAcces > sorImpl.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.MojoFailureException > at > org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execu > te(CreateProjectFromArchetypeMojo.java:202) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > nManager.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:558) > ... 16 more > [INFO] > > [INFO] Total time: 7 seconds > [INFO] Finished at: Wed May 28 17:49:39 EST 2008 > [INFO] Final Memory: 8M/14M > [INFO] > > C:\Documents and Settings\frank\My Documents\Development\Sandbox>mvn -v > Maven version: 2.0.9 > Java version: 1.5.0_08 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" > The mirrored settings from the settings.xml file are: > > > public-snapshots > public-snapshots > > http://maven.ho.bushli
[jira] Moved: (MEV-590) JSTL 1.2 not installed in repo correctly
[ http://jira.codehaus.org/browse/MEV-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy moved MNG-3613 to MEV-590: --- Component/s: (was: Artifacts and Repositories) Workflow: jira (was: Maven New) Key: MEV-590 (was: MNG-3613) Project: Maven Evangelism (was: Maven 2) > JSTL 1.2 not installed in repo correctly > > > Key: MEV-590 > URL: http://jira.codehaus.org/browse/MEV-590 > Project: Maven Evangelism > Issue Type: Bug >Reporter: Frank Adcock > > JSTL 1.2 is located at http://repo1.maven.org/maven2/javax/servlet/jstl/1.2 > It is not referenced in the maven metadata information for the directory > http://repo1.maven.org/maven2/javax/servlet/jstl/ > It does not have any metadata information in the 1.2 directory. > There is no link to the top level jstl directory > http://repo1.maven.org/maven2/jstl/ > It appears as if it was not installed correctly into the repo. > Apologies if this is filed against the wrong project or category. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEV-590) JSTL 1.2 not installed in repo correctly
[
http://jira.codehaus.org/browse/MEV-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137283#action_137283
]
Olivier Lamy commented on MEV-590:
--
this artifact is here
http://download.java.net/maven/1/javax.servlet.jsp.jstl/jars/
You can configure this repo in your pom or settings :
{code:xml}
maven1-repository.dev.java.net
Java.net Repository for Maven 1
http://download.java.net/maven/1/
legacy
true
false
{code}
It it's fine please close the issue.
Thanks!
> JSTL 1.2 not installed in repo correctly
>
>
> Key: MEV-590
> URL: http://jira.codehaus.org/browse/MEV-590
> Project: Maven Evangelism
> Issue Type: Bug
>Reporter: Frank Adcock
>
> JSTL 1.2 is located at http://repo1.maven.org/maven2/javax/servlet/jstl/1.2
> It is not referenced in the maven metadata information for the directory
> http://repo1.maven.org/maven2/javax/servlet/jstl/
> It does not have any metadata information in the 1.2 directory.
> There is no link to the top level jstl directory
> http://repo1.maven.org/maven2/jstl/
> It appears as if it was not installed correctly into the repo.
> Apologies if this is filed against the wrong project or category.
--
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-3373) Maven 2 says host in unavailable while in browser I can download from that repository
[ http://jira.codehaus.org/browse/MNG-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137286#action_137286 ] John Casey commented on MNG-3373: - org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'javax.resource:conn ector-api:jar': Cannot find parent: org.glassfish.api:api for project: javax.res ource:connector-api:jar:1.5 for project javax.resource:connector-api:jar:1.5 javax.resource:connector-api:jar:1.5 -- Actually, it looks to me like it's getting caught while trying to resolve javax.resource:connector-api:1.5, specifically because the parent: org.glassfish.api:api can't be resolved for some reason. When I checked just now, javax.resource:connector-api:1.5 specified a parent version of 10.0-SNAPSHOT for the glassfish api parent-POM. 'm a little stumped as to why that would be the case, since it's in the java.net repository and that repository is obviously reachable from Maven, but that's definitely the sticking point: Cannot find parent: org.glassfish.api:api for project: javax.resource:connector-api:jar:1.5 Maybe if you execute the build with the -X flag and capture the output to a file (`mvn -X clean install > build.log` or similar) it would shed more light on why it cannot download that parent POM. > Maven 2 says host in unavailable while in browser I can download from that > repository > - > > Key: MNG-3373 > URL: http://jira.codehaus.org/browse/MNG-3373 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.8 >Reporter: Markus KARG >Priority: Blocker > > I am using the offical Glassfish repository on java.net. > Maven tells me that it cannot resolve one of the references pointing into > that repository. The stack trace tells me that the host is not available (see > below). > In fact, when I go to that same URL in the browser, it downloads the artifact > without any problem! > Also that worked for weeks and now is broken, but my POM didn't change! > So I assume a bug in WAGON. > Here is the POM excerpt, below the POM is the stack trace. > > > glassfish-repository.dev.java.net > Java.net Repository for Glassfish > http://download.java.net/maven/glassfish > > > > > javax.resource > connector-api > 1.5 > provided > > > org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get > dependency > information: Unable to read the metadata file for artifact > 'javax.resource:conn > ector-api:jar': Cannot find parent: org.glassfish.api:api for project: > javax.res > ource:connector-api:jar:1.5 for project javax.resource:connector-api:jar:1.5 > javax.resource:connector-api:jar:1.5 > from the specified remote repositories: > central (http://repo1.maven.org/maven2), > glassfish-repository.dev.java.net (http://download.java.net/maven/glassfish) > Path to dependency: > 1) net.sourceforge.rafc:rafc:jar:1.1.1 > ... > Caused by: java.net.UnknownHostException: download.java.net > 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:394) > at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) > 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:323) > at > sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLC > onnection.java:788) > at > sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConne > ction.java:729) > at > sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection > .java:654) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon > nection.java:977) > at > org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputD > ata(LightweightHttpWagon.java:83) > ... 33 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-3373) Maven 2 says host in unavailable while in browser I can download from that repository
[ http://jira.codehaus.org/browse/MNG-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MNG-3373: Priority: Critical (was: Blocker) Fix Version/s: 2.0.10 Also, can you verify that this is still broken in 2.0.9? > Maven 2 says host in unavailable while in browser I can download from that > repository > - > > Key: MNG-3373 > URL: http://jira.codehaus.org/browse/MNG-3373 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.8 >Reporter: Markus KARG >Priority: Critical > Fix For: 2.0.10 > > > I am using the offical Glassfish repository on java.net. > Maven tells me that it cannot resolve one of the references pointing into > that repository. The stack trace tells me that the host is not available (see > below). > In fact, when I go to that same URL in the browser, it downloads the artifact > without any problem! > Also that worked for weeks and now is broken, but my POM didn't change! > So I assume a bug in WAGON. > Here is the POM excerpt, below the POM is the stack trace. > > > glassfish-repository.dev.java.net > Java.net Repository for Glassfish > http://download.java.net/maven/glassfish > > > > > javax.resource > connector-api > 1.5 > provided > > > org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get > dependency > information: Unable to read the metadata file for artifact > 'javax.resource:conn > ector-api:jar': Cannot find parent: org.glassfish.api:api for project: > javax.res > ource:connector-api:jar:1.5 for project javax.resource:connector-api:jar:1.5 > javax.resource:connector-api:jar:1.5 > from the specified remote repositories: > central (http://repo1.maven.org/maven2), > glassfish-repository.dev.java.net (http://download.java.net/maven/glassfish) > Path to dependency: > 1) net.sourceforge.rafc:rafc:jar:1.1.1 > ... > Caused by: java.net.UnknownHostException: download.java.net > 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:394) > at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) > 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:323) > at > sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLC > onnection.java:788) > at > sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConne > ction.java:729) > at > sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection > .java:654) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon > nection.java:977) > at > org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputD > ata(LightweightHttpWagon.java:83) > ... 33 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-3052) Transitive Dependency not found when repo is not listed
[ http://jira.codehaus.org/browse/MNG-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MNG-3052: Fix Version/s: 2.0.10 Need to incorporate an integration test for this issue to verify that it's fixed. > Transitive Dependency not found when repo is not listed > --- > > Key: MNG-3052 > URL: http://jira.codehaus.org/browse/MNG-3052 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.5 >Reporter: Micah Whitacre >Priority: Critical > Fix For: 2.0.10 > > Attachments: InheritLegacyRepo.zip, mng_3052.zip > > > I have seen the situation where a build fails because a project has a > transitive dependency that only exists in a repository not listed by my > project. An example of this is I have Projects A, B, and C. Where A depends > on B, and B on C. B has been released to remote repo 1, and C has been > released to remote repo 2. Since A just directly depends on B it only lists > remote repo 1 in its POM. However when I try to build project A the build > fail because it can't resolve its transitive dependency C in any of the > dependencies it is checking (repo 1 only). > It is my understanding that for project A I shouldn't have to list the remote > repos to resolve transitive dependencies. I should only have to list the > repos to get to B and Maven then should use the POM of B to resolve C. > Is that not correct? -- 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-3375) Repository entries with same id are ignored
[ http://jira.codehaus.org/browse/MNG-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MNG-3375: Fix Version/s: 2.0.11 > Repository entries with same id are ignored > --- > > Key: MNG-3375 > URL: http://jira.codehaus.org/browse/MNG-3375 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Carlos Sanchez >Priority: Critical > Fix For: 2.0.11 > > > If two entries have the same id one of them is ignored with no > warning or error. > IIRC this worked with previous versions of maven, giving the same id allowed > you to share the configuration in the settings.xml file (it may have been for > deployment only though) -- 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: (NMAVEN-136) References added using Visual Studio controls (Add Reference) do not update the pom
References added using Visual Studio controls (Add Reference) do not update the pom Key: NMAVEN-136 URL: http://jira.codehaus.org/browse/NMAVEN-136 Project: NMaven Issue Type: New Feature Affects Versions: 0.14 (Unreleased) Reporter: jan ancajas adding of references from the GAC using Visual Studio controls (Add Reference) should also reflect in the pom -- 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: (MARTIFACT-20) Introduce the use of a SAT solver
[ http://jira.codehaus.org/browse/MARTIFACT-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MARTIFACT-20: -- Attachment: patch-mercury-2008-06-04_21-37_PST.txt I think I've nailed it, but I have been wrong before. Testing, testing, testing ... > Introduce the use of a SAT solver > - > > Key: MARTIFACT-20 > URL: http://jira.codehaus.org/browse/MARTIFACT-20 > Project: Maven Artifact > Issue Type: New Feature >Reporter: Jason van Zyl > Attachments: patch-mercury-2008-06-01_10-42_PST.txt, > patch-mercury-2008-06-01_20-14_PST.txt, patch-mercury-2008-06-04_21-37_PST.txt > > > Try using the same SAT solver that p2 is using to resolve ranges of > dependencies. -- 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
