[jira] Commented: (MSITE-10) add rsync deploy to site
[ http://jira.codehaus.org/browse/MSITE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128494#action_128494 ] Kay Grosskop commented on MSITE-10: --- why would this feature be desirable? I am curious about Brett's initial motivation to report the issue and wether it is still needed. We had a pretty heavy site and a slow connection to our webserver. So I was looking for a way to copy over only artifacts that have changed since the last deploy. Moreover, resources that were deleted from the new build where still accessible on the webserver because the deployment dit not clean up old installations of the site. > add rsync deploy to site > > > Key: MSITE-10 > URL: http://jira.codehaus.org/browse/MSITE-10 > Project: Maven 2.x Site Plugin > Issue Type: New Feature > Components: site:deploy >Reporter: Brett Porter > -- 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: (MECLIPSE-266) plugin applies java facet to ear project
[ http://jira.codehaus.org/browse/MECLIPSE-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128496#action_128496 ] Stefan Bley commented on MECLIPSE-266: -- Although there is a patch, this issue is still marked "open". Why is that? Is it resolved in versions 2.4 and 2.5? > plugin applies java facet to ear project > > > Key: MECLIPSE-266 > URL: http://jira.codehaus.org/browse/MECLIPSE-266 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.3 > Environment: Windows XP >Reporter: Srepfler Srgjan > Attachments: MECLIPSE-266-maven-eclipse-plugin.patch, > MECLIPSE-266.patch > > > In .settings/org.eclipse.wst.common.project.facet.core.xml of the EAR module > I'm getting this: > > > > > > > This is a wrong facet on a EAR module and I can't compile if I don't edit > this file manually (I can't do it from the project properties - facets dialog) -- 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: (MECLIPSE-266) plugin applies java facet to ear project
[ http://jira.codehaus.org/browse/MECLIPSE-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128496#action_128496 ] stevy edited comment on MECLIPSE-266 at 3/25/08 3:36 AM: --- Although there is a patch, this issue is still marked "open". Why is that? Is it resolved in versions 2.4 and 2.5? Edit: Looking through version 2.5 of org.apache.maven.plugin.eclipse.writers.wtp.EclipseWtpFacetsWriter I see that the Java facet is again assigned to all types of WTP projects (war, ejb and also ear). Would you please take care NOT to assign the Java facet to EAR projects. Stefan was (Author: stevy): Although there is a patch, this issue is still marked "open". Why is that? Is it resolved in versions 2.4 and 2.5? > plugin applies java facet to ear project > > > Key: MECLIPSE-266 > URL: http://jira.codehaus.org/browse/MECLIPSE-266 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.3 > Environment: Windows XP >Reporter: Srepfler Srgjan > Attachments: MECLIPSE-266-maven-eclipse-plugin.patch, > MECLIPSE-266.patch > > > In .settings/org.eclipse.wst.common.project.facet.core.xml of the EAR module > I'm getting this: > > > > > > > This is a wrong facet on a EAR module and I can't compile if I don't edit > this file manually (I can't do it from the project properties - facets dialog) -- 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-10) add rsync deploy to site
[ http://jira.codehaus.org/browse/MSITE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128502#action_128502 ] Andreas Schildbach commented on MSITE-10: - You have answered your question yourself. Additionally, it would be nice to have another upload protocol that is easy for firewalls. FTP is a pain. > add rsync deploy to site > > > Key: MSITE-10 > URL: http://jira.codehaus.org/browse/MSITE-10 > Project: Maven 2.x Site Plugin > Issue Type: New Feature > Components: site:deploy >Reporter: Brett Porter > -- 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: (MECLIPSE-266) plugin applies java facet to ear project
[ http://jira.codehaus.org/browse/MECLIPSE-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bley updated MECLIPSE-266: - Attachment: MECLIPSE-266-2.5.patch Patch for version 2.5 > plugin applies java facet to ear project > > > Key: MECLIPSE-266 > URL: http://jira.codehaus.org/browse/MECLIPSE-266 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.3 > Environment: Windows XP >Reporter: Srepfler Srgjan > Attachments: MECLIPSE-266-2.5.patch, > MECLIPSE-266-maven-eclipse-plugin.patch, MECLIPSE-266.patch > > > In .settings/org.eclipse.wst.common.project.facet.core.xml of the EAR module > I'm getting this: > > > > > > > This is a wrong facet on a EAR module and I can't compile if I don't edit > this file manually (I can't do it from the project properties - facets dialog) -- 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-1982) Please sync net.sf.hibernate4gwt groupId with central
Please sync net.sf.hibernate4gwt groupId with central - Key: MAVENUPLOAD-1982 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1982 Project: maven-upload-requests Issue Type: Wish Reporter: nicolas de loof -- 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-1973) Upload of maven-deployment-package-plugin
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128526#action_128526 ] Siamak Haschemi commented on MAVENUPLOAD-1973: -- I renamed the project to osgi-deployment-maven-project. Please forget the uploaded file and add me into your automatic rsync: "net.sourceforge.mvn-dp-plugin","[EMAIL PROTECTED]:/home/groups/m/mv/mvn-dp-plugin/htdocs/repository/releases","rsync_ssh","Siamak Haschemi","[EMAIL PROTECTED]",, Kind regards, Siamak Haschemi > Upload of maven-deployment-package-plugin > - > > Key: MAVENUPLOAD-1973 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1973 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Siamak Haschemi > > http://kent.dl.sourceforge.net/sourceforge/mvn-dp-plugin/maven-deployment-package-plugin-0.1.0-bundle.jar > https://sourceforge.net/projects/mvn-dp-plugin/ > https://sourceforge.net/project/memberlist.php?group_id=221773 > I'm a developer in maven-deployment-package-plugin, please upload! -- 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: (MAVENUPLOAD-1971) Please sync com.capgemini.platina groupId with central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof reopened MAVENUPLOAD-1971: -- I receive warning from the sync process : Seems the groupId directory should not have a trailing "/" Can you fix this please ? --- Some repositories were not synchronized --- groupId: com.capgemini.platina Error: /bin/sh: line 1: /com/capgemini/platina/: No such file or directory Error synchronizing metadata. Exit code: 127 This is an automated email, do not respond.Contact the owners at [EMAIL PROTECTED] > Please sync com.capgemini.platina groupId with central > -- > > Key: MAVENUPLOAD-1971 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1971 > Project: maven-upload-requests > Issue Type: Wish >Reporter: nicolas de loof >Assignee: Carlos Sanchez > Attachments: platina.sh > > > I've created for my company (capgemini) some maven components and corporate > POM. > They're distributed under apache license, so I'd like them to get deployed on > central. -- 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: (MRM-664) Cannot download a strut-module artifact in a Legacy repository
[ http://jira.codehaus.org/browse/MRM-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-664. Assignee: Brett Porter Resolution: Fixed Fix Version/s: (was: 1.0.x) 1.0.2 > Cannot download a strut-module artifact in a Legacy repository > -- > > Key: MRM-664 > URL: http://jira.codehaus.org/browse/MRM-664 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0 >Reporter: Daniel Beland >Assignee: Brett Porter >Priority: Critical > Fix For: 1.0.2 > > > I still have legacy Maven 1.1 projects which uses the struts-module plugin. > I was using maven-proxy until now but decided to switch to archiva. > However when I try to download a struts-module in my Maven 1.X repository, I > get the following exception: > org.apache.maven.archiva.repository.layout.LayoutException: Invalid path to > Artifact: mismatch on extension [dule] and layout specified type > [struts-modules] (which maps to extension: [struts.module]) on path > [WebPortal/struts-modules/eventsDB-1.2.3.struts-module] > at > org.apache.maven.archiva.repository.content.LegacyPathParser.toArtifactReference(LegacyPathParser.java:154) > at > org.apache.maven.archiva.repository.content.RepositoryRequest.toArtifactReference(RepositoryRequest.java:125) > at > org.apache.maven.archiva.repository.content.RepositoryRequest.toNativePath(RepositoryRequest.java:271) > at > org.apache.maven.archiva.web.repository.ProxiedDavServer.process(ProxiedDavServer.java:193) > at > org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.service(MultiplexedWebDavServlet.java:119) > at > org.apache.maven.archiva.web.repository.RepositoryServlet.service(RepositoryServlet.java:155) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428) > at > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830) > at > com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:189) > at > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) > at > com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:39) > at > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) > at > com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88) > at > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) > at > org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568) > at org.mortbay.http.HttpContext.handle(HttpContext.java:1530) > at > org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633) > at org.mortbay.http.HttpContext.handle(HttpContext.java:1482) > at org.mortbay.http.HttpServer.service(HttpServer.java:909) > at org.mortbay.http.HttpConnection.service(HttpConnection.java:816) > at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982) > at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833) > at > org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244) > at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) > at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) > The file WebPortal/struts-modules/eventsDB-1.2.3.struts-module does exist > (and would be returned correctly by maven-proxy), but it seems as it archiva > is looking for WebPortal/struts-modules/eventsDB-1.2.3.struts.module which > does not exist. (replacing the dash by a dot in the extension) -- 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: (MAVENUPLOAD-1973) Upload of maven-deployment-package-plugin
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128526#action_128526 ] siamak.haschemi edited comment on MAVENUPLOAD-1973 at 3/25/08 9:53 AM: --- I renamed the project to osgi-deployment-maven-plugin. Please forget the uploaded file and add me into your automatic rsync: "net.sourceforge.mvn-dp-plugin","[EMAIL PROTECTED]:/home/groups/m/mv/mvn-dp-plugin/htdocs/repository/releases","rsync_ssh","Siamak Haschemi","[EMAIL PROTECTED]",, Kind regards, Siamak Haschemi was (Author: siamak.haschemi): I renamed the project to osgi-deployment-maven-project. Please forget the uploaded file and add me into your automatic rsync: "net.sourceforge.mvn-dp-plugin","[EMAIL PROTECTED]:/home/groups/m/mv/mvn-dp-plugin/htdocs/repository/releases","rsync_ssh","Siamak Haschemi","[EMAIL PROTECTED]",, Kind regards, Siamak Haschemi > Upload of maven-deployment-package-plugin > - > > Key: MAVENUPLOAD-1973 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1973 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Siamak Haschemi > > http://kent.dl.sourceforge.net/sourceforge/mvn-dp-plugin/maven-deployment-package-plugin-0.1.0-bundle.jar > https://sourceforge.net/projects/mvn-dp-plugin/ > https://sourceforge.net/project/memberlist.php?group_id=221773 > I'm a developer in maven-deployment-package-plugin, please upload! -- 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: (MRM-740) Archiva documentation needs a page that explains why you should use a repository manager
[ http://jira.codehaus.org/browse/MRM-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128538#action_128538 ] Wendy Smoak commented on MRM-740: - Consider contributing the general information to: http://maven.apache.org/repository-management.html > Archiva documentation needs a page that explains why you should use a > repository manager > > > Key: MRM-740 > URL: http://jira.codehaus.org/browse/MRM-740 > Project: Archiva > Issue Type: Bug > Components: documentation >Affects Versions: 1.0.1 >Reporter: Brett Porter > Fix For: 1.x > > > This can be more general about repository managers, but why choose Archiva > may be a part of it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSHADE-23) ${basedir} is wrong after running shade plugin
${basedir} is wrong after running shade plugin
--
Key: MSHADE-23
URL: http://jira.codehaus.org/browse/MSHADE-23
Project: Maven 2.x Shade Plugin
Issue Type: Bug
Environment: Maven version: 2.0.8
Java version: 1.5.0_06
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
Reporter: Andreas Schouten
After the shade plugin has run, the ${basedir} points to target.
--
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-211) assembly plugin and jar plugin disagree about whether to use uniqueVersion snapshot names
[
http://jira.codehaus.org/browse/MASSEMBLY-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128541#action_128541
]
John Casey commented on MASSEMBLY-211:
--
Can you attach an assembly descriptor that creates the erroneous result? It
looks like your problem might be solved by using ${artifact.baseVersion}
instead of ${artifact.version} in the outputFileNameMapping, which is probably
what the jar plugin is doing when it creates the Class-Path manifest entry.
I'll look into how the jar plugin handles this, but we need to provide
flexibility to do both, IMO.
> assembly plugin and jar plugin disagree about whether to use uniqueVersion
> snapshot names
> -
>
> Key: MASSEMBLY-211
> URL: http://jira.codehaus.org/browse/MASSEMBLY-211
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2-beta-1
>Reporter: Max Bowsher
>Priority: Blocker
> Fix For: 2.2-beta-3
>
> Attachments: CSMDirectoryListingOfJars.txt, CSMJarManifest.txt
>
>
> Background: Consider the following setup:
> jar-plugin configured with addClasspath=true, writing list of dependency jar
> file names into manifest of project jar.
> assembly-plugin configured with a dependencySet pulling all dependencies into
> a single directory.
> Result: application is runnable with with "java -jar mainartifact.jar"
> There has long been a problem (i.e. with assembly-plugin 2.1) that when
> deployed snapshot jars were in use, the jar and assembly plugins would
> disagree in whether the uniqueVersion name was used, and this is MNG-2456.
> However, assembly-plugin 2.2-beta-1 has introduced further complications to
> the situation by not using the lifecycle's default set of resolved artifacts,
> but by running a manual resolution of its own. This has made the two plugins
> disagree in more scenarios than before, and broke the workaround patch that I
> posted in MNG-2456.
> At the root of these problems is some very peculiar handling of the 'file',
> 'baseVersion' and 'version' fields of Artifact objects, two notable instances
> of which are the DefaultArtifact.isSnapshot method, which despite being an
> accessor, actually changes the state of the object, and the
> DefaultArtifactResolver.resolve method, which contains some rather bizarre
> manipulation of the 'file' field (more detail may comments in MNG-2456).
> An interim fix to this issue might involve workarounds in both the jar and
> assembly plugins to get them to agree. A true fix probably also involves
> fixing Maven core classes.
--
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: (MRELEASE-335) release:branch commits changes to tags/ directory
release:branch commits changes to tags/ directory - Key: MRELEASE-335 URL: http://jira.codehaus.org/browse/MRELEASE-335 Project: Maven 2.x Release Plugin Issue Type: Bug Components: scm Affects Versions: 2.0-beta-7 Reporter: Alex B It should be possible to create a branch from a tag using the release plugin without comitting changes to the tags/ directory in subversion. If this cannot be automated, then perhaps it should be possible to set the versions and scm urls etc after making the copy from the tag to the branch manually -- 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-211) assembly plugin and jar plugin disagree about whether to use uniqueVersion snapshot names
[ http://jira.codehaus.org/browse/MASSEMBLY-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128546#action_128546 ] Max Bowsher commented on MASSEMBLY-211: --- At best, using baseVersion would be a workaround only. If I use a deployed snapshot, the uniqueVersion naming is metadata that should be allowed to persist into the assembly, to identify the exact version of the dependency being used. > assembly plugin and jar plugin disagree about whether to use uniqueVersion > snapshot names > - > > Key: MASSEMBLY-211 > URL: http://jira.codehaus.org/browse/MASSEMBLY-211 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-1 >Reporter: Max Bowsher >Priority: Blocker > Fix For: 2.2-beta-3 > > Attachments: CSMDirectoryListingOfJars.txt, CSMJarManifest.txt > > > Background: Consider the following setup: > jar-plugin configured with addClasspath=true, writing list of dependency jar > file names into manifest of project jar. > assembly-plugin configured with a dependencySet pulling all dependencies into > a single directory. > Result: application is runnable with with "java -jar mainartifact.jar" > There has long been a problem (i.e. with assembly-plugin 2.1) that when > deployed snapshot jars were in use, the jar and assembly plugins would > disagree in whether the uniqueVersion name was used, and this is MNG-2456. > However, assembly-plugin 2.2-beta-1 has introduced further complications to > the situation by not using the lifecycle's default set of resolved artifacts, > but by running a manual resolution of its own. This has made the two plugins > disagree in more scenarios than before, and broke the workaround patch that I > posted in MNG-2456. > At the root of these problems is some very peculiar handling of the 'file', > 'baseVersion' and 'version' fields of Artifact objects, two notable instances > of which are the DefaultArtifact.isSnapshot method, which despite being an > accessor, actually changes the state of the object, and the > DefaultArtifactResolver.resolve method, which contains some rather bizarre > manipulation of the 'file' field (more detail may comments in MNG-2456). > An interim fix to this issue might involve workarounds in both the jar and > assembly plugins to get them to agree. A true fix probably also involves > fixing Maven core classes. -- 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-270) Assembly does not resolved managed dependencies correctly
[ http://jira.codehaus.org/browse/MASSEMBLY-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128551#action_128551 ] Brian Jackson commented on MASSEMBLY-270: - Thanks John, I have confirmed that it is fixed in 2.2-beta-2 as well. > Assembly does not resolved managed dependencies correctly > - > > Key: MASSEMBLY-270 > URL: http://jira.codehaus.org/browse/MASSEMBLY-270 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-1 >Reporter: Brian Jackson >Assignee: John Casey > Fix For: 2.2-beta-3 > > Attachments: dependency-bug.zip > > > The assembly plugin does not resolve the version number correctly for a > managed transitive dependency. The result is the jar-with-dependencies > assembly will include a different version of the transitive dependency than > the version that is reported dependency and project-info-reports plugins > report. > Steps to reproduce bug > -- > 1) Extract the dependencybug.zip > 2) cd dependencybug-c > 3) mvn install > 4) open the pom.xml and change the version to 2.0 > 5) mvn install > 6) cd ../dependencybug-b > 7) mvn install > 8) cd ../dependencybug-a > Now within the dependencybug-a project compare the results of: > == > mvn dependency:resolve > -- > Resolves dependencybug-c to version 2.0 > -- > [INFO] [dependency:resolve] > [INFO] > [INFO] The following files have been resolved: > ... > [INFO]com.espn.test.dependencybug:dependencybug-c:jar:2.0 (scope = > compile) > ... > == > mvn org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-5-SNAPSHOT:tree > -- > Resolves dependencybug-c to version 2.0 > -- > [INFO] [dependency:tree] > [INFO] com.espn.test.dependencybug:dependencybug-a:jar:1.0-SNAPSHOT > [INFO] +- com.espn.test.dependencybug:dependencybug-b:jar:1.0-SNAPSHOT:compile > [INFO] | \- com.espn.test.dependencybug:dependencybug-c:jar:2.0:compile > (version managed from 1.0) > ... > == > mvn project-info-reports:dependencies > -- > Resolves dependencybug-c to version 2.0 > -- > target/site/dependencies.html: > ... > GroupId ArtifactId Version Classifier Type Optional > com.espn.test.dependencybug dependencybug-c 2.0 - jar > > == > mvn assembly:assembly > -- > Resolves dependencybug-c to version 1.0 > -- > [INFO] [jar:jar] > [INFO] Building jar: C:\Documents and Settings\jacksbrr\My > Documents\Projects\dependency-bug\dependencybug-a\target\dependencybug-a-1.0-SNAPSHOT.jar > [INFO] [assembly:assembly] > [INFO] Processing DependencySet (output=) > [INFO] Expanding: C:\Documents and > Settings\jacksbrr\.m2\repository\com\espn\test\dependencybug\dependencybug-b\1.0-SNAPSHOT\dependencybug-b-1.0-SNAPSHOT.jar > into C:\DOCUME~1\jacksbrr\LOCALS~1\Temp\archived-file-set.1539373911.tmp > [INFO] Expanding: C:\Documents and > Settings\jacksbrr\.m2\repository\com\espn\test\dependencybug\dependencybug-c\1.0\dependencybug-c-1.0.jar > into C:\DOCUME~1\jacksbrr\LOCALS~1\Temp\archived-file-set.148071824.tmp > [INFO] Building jar: C:\Documents and Settings\jacksbrr\My > Documents\Projects\dependency-bug\dependencybug-a\target\dependencybug-a-1.0-SNAPSHOT-jar-with-dependencies.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] Created: (MECLIPSE-409) Build path omits generated test resources
Build path omits generated test resources - Key: MECLIPSE-409 URL: http://jira.codehaus.org/browse/MECLIPSE-409 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: Core : Dependencies resolution and build path Affects Versions: 2.5 Reporter: Mark Hobson eclipse:eclipse only executes up to the generate-resources phase, hence any generated test resources are not included in the build path. This means that tests that rely on these generated test resources will fail in the IDE. -- 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: (MECLIPSE-409) Build path omits generated test resources
[ http://jira.codehaus.org/browse/MECLIPSE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hobson updated MECLIPSE-409: - Attachment: MECLIPSE-409.patch Attached patch changes eclipse:eclipse to execute up to generate-test-resources. The current tests fail in a stack overflow for me, so haven't been able to check for side-effects. Not sure if any other goals will also need this change. > Build path omits generated test resources > - > > Key: MECLIPSE-409 > URL: http://jira.codehaus.org/browse/MECLIPSE-409 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Dependencies resolution and build path >Affects Versions: 2.5 >Reporter: Mark Hobson > Attachments: MECLIPSE-409.patch > > > eclipse:eclipse only executes up to the generate-resources phase, hence any > generated test resources are not included in the build path. This means that > tests that rely on these generated test resources will fail in the IDE. -- 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: (MRESOURCES-61) PluginDescriptor not found
[ http://jira.codehaus.org/browse/MRESOURCES-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128563#action_128563 ] Brill Pappin commented on MRESOURCES-61: Ok, got the stack trace. This is the same exception I've been getting for month on various machines including Mac, Linux and Windows of various versions. It seem to only be after a day has gone by and maven thinks it needs to update the plugin. Now, in this particular case (which is not always the case) the artifact is being downloaded from an Archiva repository... however if it was unable to check for a new version of the plugin, I should at *most* be getting a warning only, my build that worked yesterday should not be failing today just because it couldn't check for an update to a plugin (in this case it's actually Archiva that's getting the error and passing it back). Also, it's *ALWAYS* the resources plugin... any other plugin and I know I may have a configuration issue, but this particular problem seems to be limited to the resources plugin consistently. == Full output follow == $ mvn -U -e deploy + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] snapshot com.empirical:empirical:1.0.0-SNAPSHOT: checking for updates from internal [WARNING] repository metadata for: 'snapshot com.empirical:empirical:1.0.0-SNAPSHOT' could not be retrieved from repository: internal due to an error: GET request of: com/empirical/empirical/1.0.0-SNAPSHOT/maven-metadata.xml from internal failed [INFO] Repository 'internal' will be blacklisted WAGON_VERSION: 1.0-beta-1 [INFO] [INFO] Building NetSuite Web Services [INFO]task-segment: [deploy] [INFO] [INFO] artifact org.apache.maven.plugins:maven-resources-plugin: checking for updates from central [WARNING] repository metadata for: 'artifact org.apache.maven.plugins:maven-resources-plugin' could not be retrieved from repository: central due to an error: GET request of: org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml from internal-central failed [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-resources-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-resources-plugin' does not exist or no valid version could be found at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1286) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1522) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1016) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:980) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458) 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:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) 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-resources-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
[jira] Commented: (MRESOURCES-61) PluginDescriptor not found
[ http://jira.codehaus.org/browse/MRESOURCES-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128565#action_128565 ] Olivier Lamy commented on MRESOURCES-61: Have a look at the stack trace. It says "Repository 'central' will be blacklisted" (and Repository 'internal' will be blacklisted). This means you don't have internet access ! > PluginDescriptor not found > -- > > Key: MRESOURCES-61 > URL: http://jira.codehaus.org/browse/MRESOURCES-61 > Project: Maven 2.x Resources Plugin > Issue Type: Bug >Reporter: Brill Pappin > > The following error, every time I run a build has been ongoing for quite some > time now. > 3/21/08 3:34:06 PM EDT: Build error for /aleixo-console/pom.xml; > java.lang.IllegalStateException: The PluginDescriptor for the plugin > org.apache.maven.plugins:maven-resources-plugin was not found > It seems to go away if I run with a -U to update the plugins but comes back > regularly. > Can somebody please fix whatever issue is causing this to occur? -- 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: (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 ] Micah Whitacre reopened MNG-3052: - reopening because I provided a complete example that illustrates the issues we are seeing. > 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 > 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-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 ] Micah Whitacre updated MNG-3052: Attachment: mng_3052.zip I hacked up Dirk's example (thanks for giving me a starting point) and created an example that illustrates my point. Inside the zip file you will find three projects, foo, bar, and wombat. Wombat depends on Bar which depends on Foo. Using the projects in the zip file, run "mvn clean deploy" on foo and then bar. After that is completed clear out your local repository and try and run "mvn clean compile" on wombat. It will have an issue being able to resolve foo and I get the following output: Missing: -- 1) org.mule:mule-foo:jar:1.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.mule -DartifactId=mule-foo -Dversio n=1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.mule -DartifactId=mule-foo -Dversion= 1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id ] Path to dependency: 1) org.mule:mule-wombat:jar:1.0-SNAPSHOT 2) org.mule:mule-bar:jar:1.0-SNAPSHOT 3) org.mule:mule-foo:jar:1.0-SNAPSHOT -- 1 required artifact is missing. for artifact: org.mule:mule-wombat:jar:1.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), example2-repo (file://c:/test/repo2) You'll notice that it never lists example1-repo as a repository it checked to find foo. > 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 > 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: (MASSEMBLY-190) Problem with dependency conflict resolution on multi-module project
[ http://jira.codehaus.org/browse/MASSEMBLY-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MASSEMBLY-190: - Affects Version/s: (was: 2.2) 2.2-beta-3 Fix Version/s: (was: 2.2) 2.2-beta-3 dependencySets need to be resolved all at once, by somehow aggregating all of the sets' include/exclude logic and applying it to the direct dependencies...then, after the project's dependencies are resolved, no further calls to resolve should be made. Instead, the actual dependencySets should each filter the single resolved set of artifacts according to their own rules to produce the output configured. This is just a note so I can come back and reference the issue before I start implementing this logical change. This sort of change should allow the standard conflict-resolution strategies to be used, while still allowing certain direct dependencies (like, say, with scope == test or similar) to be entirely excluded from those resolved for the assembly construction. > Problem with dependency conflict resolution on multi-module project > --- > > Key: MASSEMBLY-190 > URL: http://jira.codehaus.org/browse/MASSEMBLY-190 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-3 > Environment: Using maven 2.0.5 and assembly 2.2-SNAPSHOT >Reporter: Frédéric ESNAULT > Fix For: 2.2-beta-3 > > > Hi, > I'm trying to use the assembly plugin to gather all the jars of my project, > including all dependencies. > As the project is composed of several modules, I use a descriptor which looks > like this : > > bin > > zip > > false > > > > / > false > true > > > > > It seems to work fine at first sight - it creates a zip containing all the > jar files. However, I find in the archive several instances of the same > dependency with differents versions, for instance asm-1.5.3 and asm-2.2.3. > This is a surprise as maven is supposed to take care of conflict resolution. > When I look at a detailed trace, it appears that conflict resolution is done > but on each module independently. But my modules are intended to work > together and I expect to get an assembly with only one version of each > dependency found on the whole set of mudules. It seems to me that conflict > resolution is not managed properly in this use case. -- 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-211) assembly plugin and jar plugin disagree about whether to use uniqueVersion snapshot names
[ http://jira.codehaus.org/browse/MASSEMBLY-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128579#action_128579 ] John Casey commented on MASSEMBLY-211: -- artifact-path handling needs to be consolidated somehow between the assembly plugin and the component used to generate manifest files. This includes formatting of the file names (or, determining when to use the 'native' file path vs. a formatted one that would result from the file being copied to the formatted location), but it also includes support for mapping artifacts to specific subpaths within a directory structure, such as would be needed if all dependencies were archived in the /lib directory of a jar whose Class-Path manifest attribute attempted to reference them. The mappings and formats need to then be made available to all plugins that generate manifests. In the case of an assembly that consists of the project's main jar with its dependencies listed in the /lib subpath, the jar:jar mojo needs to know about this subpath when it generates the manifest, so its actions are coordinated with those of the assembly plugin. I would therefore propose a new plugin that will generate jar manifest files. The manifest files will then be available for use in any plugin that supports the MavenArchiveConfiguration from maven-archiver. In order to take advantage of existing configurations, the plugin should also support providers that can generate a Class-Path or other attribute based on some other configuration in the project - with the first example being the dependencySets section of an assembly descriptor. With an assembly provider, the assembly descriptor can be read in order to determine to which path each artifact included should be mapped. > assembly plugin and jar plugin disagree about whether to use uniqueVersion > snapshot names > - > > Key: MASSEMBLY-211 > URL: http://jira.codehaus.org/browse/MASSEMBLY-211 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-1 >Reporter: Max Bowsher >Priority: Blocker > Fix For: 2.2-beta-3 > > Attachments: CSMDirectoryListingOfJars.txt, CSMJarManifest.txt > > > Background: Consider the following setup: > jar-plugin configured with addClasspath=true, writing list of dependency jar > file names into manifest of project jar. > assembly-plugin configured with a dependencySet pulling all dependencies into > a single directory. > Result: application is runnable with with "java -jar mainartifact.jar" > There has long been a problem (i.e. with assembly-plugin 2.1) that when > deployed snapshot jars were in use, the jar and assembly plugins would > disagree in whether the uniqueVersion name was used, and this is MNG-2456. > However, assembly-plugin 2.2-beta-1 has introduced further complications to > the situation by not using the lifecycle's default set of resolved artifacts, > but by running a manual resolution of its own. This has made the two plugins > disagree in more scenarios than before, and broke the workaround patch that I > posted in MNG-2456. > At the root of these problems is some very peculiar handling of the 'file', > 'baseVersion' and 'version' fields of Artifact objects, two notable instances > of which are the DefaultArtifact.isSnapshot method, which despite being an > accessor, actually changes the state of the object, and the > DefaultArtifactResolver.resolve method, which contains some rather bizarre > manipulation of the 'file' field (more detail may comments in MNG-2456). > An interim fix to this issue might involve workarounds in both the jar and > assembly plugins to get them to agree. A true fix probably also involves > fixing Maven core classes. -- 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-478) Specifying true plus an results in an empty surefire-report.html file
Specifying true plus an results in an empty surefire-report.html file -- Key: SUREFIRE-478 URL: http://jira.codehaus.org/browse/SUREFIRE-478 Project: Maven Surefire Issue Type: Bug Components: report plugin Affects Versions: 2.4.2 Environment: Windows XP SP2; jdk1.5.0_14; Maven 2.0.8 Reporter: Robert Shanahan The following configuration snippet, from the parent pom of a multi-module project, results in an empty surefire-report.html file. Using default output directory works just fine with aggregate set to true. Setting aggregate to false with a specified output directory has the same result as specifying no output directory and aggregate to false, i.e. a non-empty surefire-report.html file is created, but it has no test results since it is the top level pom. org.apache.maven.plugins maven-surefire-plugin org.apache.maven.plugins maven-surefire-report-plugin /data/reports true test report-only -- 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: (MECLIPSE-410) Installation failure for RAD7,requires plug-in "org.eclipse.mylar.tasks.ui"
Installation failure for RAD7,requires plug-in "org.eclipse.mylar.tasks.ui" Key: MECLIPSE-410 URL: http://jira.codehaus.org/browse/MECLIPSE-410 Project: Maven 2.x Eclipse Plugin Issue Type: Wish Components: RAD support Environment: RAD7 Windows XP Reporter: Palmer Priority: Minor When I install the Maven Integration for Eclipse by using the following update site from within Eclipse: http://m2eclipse.sonatype.org/update/ if I try to select the check box of "Maven Integration for MyIar 0.0.11.20070603-1200", it report : Requested operation cannot be performed because it would invalidate the current configuration. Maven Integration for Mylar (0.0.11.20070603-1200) requires plug-in "org.eclipse.mylar.tasks.ui (2.0.0.v20070221-0830)", or later 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] Commented: (SUREFIRE-478) Specifying true plus an results in an empty surefire-report.html file
[ http://jira.codehaus.org/browse/SUREFIRE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128585#action_128585 ] Benjamin Bentmann commented on SUREFIRE-478: bq. /data/reports Possibly a misconfiguration: The leading slash indicates an absolute path on Unix systems. Even though you are running on Windows (where the path will be interpreted a drive-relative), Maven's internal logic will not resolve this path to the project base directory. What if you simply drop the leading slash? > Specifying true plus an results in > an empty surefire-report.html file > -- > > Key: SUREFIRE-478 > URL: http://jira.codehaus.org/browse/SUREFIRE-478 > Project: Maven Surefire > Issue Type: Bug > Components: report plugin >Affects Versions: 2.4.2 > Environment: Windows XP SP2; jdk1.5.0_14; Maven 2.0.8 >Reporter: Robert Shanahan > > The following configuration snippet, from the parent pom of a multi-module > project, results in an empty surefire-report.html file. Using default output > directory works just fine with aggregate set to true. Setting aggregate to > false with a specified output directory has the same result as specifying no > output directory and aggregate to false, i.e. a non-empty > surefire-report.html file is created, but it has no test results since it is > the top level pom. > > > > org.apache.maven.plugins > maven-surefire-plugin > > > org.apache.maven.plugins > maven-surefire-report-plugin > > /data/reports > true > > > > test > > report-only > > > > > > -- 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: (MECLIPSE-410) Installation failure for RAD7,requires plug-in "org.eclipse.mylar.tasks.ui"
[ http://jira.codehaus.org/browse/MECLIPSE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128586#action_128586 ] Palmer commented on MECLIPSE-410: - Sorry, it is confusing. It is from http://m2eclipse.codehaus.org/update-dev/ or http://m2eclipse.sonatype.org/update/ And now It reports NullPointerException. > Installation failure for RAD7,requires plug-in "org.eclipse.mylar.tasks.ui" > > > Key: MECLIPSE-410 > URL: http://jira.codehaus.org/browse/MECLIPSE-410 > Project: Maven 2.x Eclipse Plugin > Issue Type: Wish > Components: RAD support > Environment: RAD7 Windows XP >Reporter: Palmer >Priority: Minor > > When I install the Maven Integration for Eclipse by using the following > update site from within Eclipse: > http://m2eclipse.sonatype.org/update/ > if I try to select the check box of "Maven Integration for MyIar > 0.0.11.20070603-1200", > it report : > Requested operation cannot be performed because it would invalidate the > current configuration. > Maven Integration for Mylar (0.0.11.20070603-1200) requires plug-in > "org.eclipse.mylar.tasks.ui (2.0.0.v20070221-0830)", or later 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: (MPATCH-2) Make command line invocation of patch tool platform-dependent
Make command line invocation of patch tool platform-dependent - Key: MPATCH-2 URL: http://jira.codehaus.org/browse/MPATCH-2 Project: Maven 2.x Patch Plugin Issue Type: Bug Reporter: Benjamin Bentmann Priority: Critical The code is hard-coded to use the Bourne shell for invocation of the patch tool. However, the shell needs to be selected according to the underlying operating system, e.g. use "command.com" or "cmd.exe" on Windows boxes. -- 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: (MPATCH-2) Make command line invocation of patch tool platform-dependent
[ http://jira.codehaus.org/browse/MPATCH-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MPATCH-2. -- Assignee: Benjamin Bentmann Resolution: Fixed Fixed in [r640484|http://svn.apache.org/viewvc?view=rev&revision=640484]. > Make command line invocation of patch tool platform-dependent > - > > Key: MPATCH-2 > URL: http://jira.codehaus.org/browse/MPATCH-2 > Project: Maven 2.x Patch Plugin > Issue Type: Bug >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann >Priority: Critical > > The code is hard-coded to use the Bourne shell for invocation of the patch > tool. However, the shell needs to be selected according to the underlying > operating system, e.g. use "command.com" or "cmd.exe" on Windows boxes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-478) Specifying true plus an results in an empty surefire-report.html file
[ http://jira.codehaus.org/browse/SUREFIRE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128588#action_128588 ] Robert Shanahan commented on SUREFIRE-478: -- None of c:/data/reports, c:\data\reports or c:\\data\\reports works. Each creates an empty surefire-report.html file, so clearly the path is reachable. > Specifying true plus an results in > an empty surefire-report.html file > -- > > Key: SUREFIRE-478 > URL: http://jira.codehaus.org/browse/SUREFIRE-478 > Project: Maven Surefire > Issue Type: Bug > Components: report plugin >Affects Versions: 2.4.2 > Environment: Windows XP SP2; jdk1.5.0_14; Maven 2.0.8 >Reporter: Robert Shanahan > > The following configuration snippet, from the parent pom of a multi-module > project, results in an empty surefire-report.html file. Using default output > directory works just fine with aggregate set to true. Setting aggregate to > false with a specified output directory has the same result as specifying no > output directory and aggregate to false, i.e. a non-empty > surefire-report.html file is created, but it has no test results since it is > the top level pom. > > > > org.apache.maven.plugins > maven-surefire-plugin > > > org.apache.maven.plugins > maven-surefire-report-plugin > > /data/reports > true > > > > test > > report-only > > > > > > -- 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: (MPATCH-1) Support deletion of empty files after the patches have been applied
[ http://jira.codehaus.org/browse/MPATCH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MPATCH-1: --- Affects Version/s: 1.0 > Support deletion of empty files after the patches have been applied > --- > > Key: MPATCH-1 > URL: http://jira.codehaus.org/browse/MPATCH-1 > Project: Maven 2.x Patch Plugin > Issue Type: New Feature >Affects Versions: 1.0 >Reporter: Napoleon Esmundo C. Ramirez >Priority: Minor > Attachments: MPATCH-1.patch > > > By default, the patch command does not delete empty files after the patches > have been applied. Compilation breaks on empty java sources. According to > the man pages, as a workaround, the to be deleted could be compared to an > empty file dated the Epoch (1970-01-01 00:00:00 UTC) if it conforms to POSIX. > Or better yet, use the -E or --remove-empty-files option to be sure. -- 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: (MPATCH-2) Make command line invocation of patch tool platform-dependent
[ http://jira.codehaus.org/browse/MPATCH-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MPATCH-2: --- Affects Version/s: 1.0 Fix Version/s: 1.1 > Make command line invocation of patch tool platform-dependent > - > > Key: MPATCH-2 > URL: http://jira.codehaus.org/browse/MPATCH-2 > Project: Maven 2.x Patch Plugin > Issue Type: Bug >Affects Versions: 1.0 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann >Priority: Critical > Fix For: 1.1 > > > The code is hard-coded to use the Bourne shell for invocation of the patch > tool. However, the shell needs to be selected according to the underlying > operating system, e.g. use "command.com" or "cmd.exe" on Windows boxes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-478) Specifying true plus an results in an empty surefire-report.html file
[
http://jira.codehaus.org/browse/SUREFIRE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128591#action_128591
]
Benjamin Bentmann commented on SUREFIRE-478:
Just for clarity: I suggested to use
{code:xml}
data/reports
{code}
i.e. a portable relative path, not absolute paths.
Also, I now notice that you have misconfigured the Surefire Report Plugin: It's
a reporting plugin (unlike maven-surefire-plugin, which does the major work),
so it needs to be configured unter the {{}} section of the POM. See
also its [usage
guide|http://maven.apache.org/plugins/maven-surefire-report-plugin/usage.html].
> Specifying true plus an results in
> an empty surefire-report.html file
> --
>
> Key: SUREFIRE-478
> URL: http://jira.codehaus.org/browse/SUREFIRE-478
> Project: Maven Surefire
> Issue Type: Bug
> Components: report plugin
>Affects Versions: 2.4.2
> Environment: Windows XP SP2; jdk1.5.0_14; Maven 2.0.8
>Reporter: Robert Shanahan
>
> The following configuration snippet, from the parent pom of a multi-module
> project, results in an empty surefire-report.html file. Using default output
> directory works just fine with aggregate set to true. Setting aggregate to
> false with a specified output directory has the same result as specifying no
> output directory and aggregate to false, i.e. a non-empty
> surefire-report.html file is created, but it has no test results since it is
> the top level pom.
>
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
>
>
> org.apache.maven.plugins
> maven-surefire-report-plugin
>
> /data/reports
> true
>
>
>
> test
>
> report-only
>
>
>
>
>
>
--
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: (SUREFIRE-478) Specifying true plus an results in an empty surefire-report.html file
[ http://jira.codehaus.org/browse/SUREFIRE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128588#action_128588 ] rshan edited comment on SUREFIRE-478 at 3/25/08 5:22 PM: --- None of data/reports, c:/data/reports, c:\data\reports or c:\\data\\reports works. Each creates an empty surefire-report.html file, so clearly the path is reachable. was (Author: rshan): None of c:/data/reports, c:\data\reports or c:\\data\\reports works. Each creates an empty surefire-report.html file, so clearly the path is reachable. > Specifying true plus an results in > an empty surefire-report.html file > -- > > Key: SUREFIRE-478 > URL: http://jira.codehaus.org/browse/SUREFIRE-478 > Project: Maven Surefire > Issue Type: Bug > Components: report plugin >Affects Versions: 2.4.2 > Environment: Windows XP SP2; jdk1.5.0_14; Maven 2.0.8 >Reporter: Robert Shanahan > > The following configuration snippet, from the parent pom of a multi-module > project, results in an empty surefire-report.html file. Using default output > directory works just fine with aggregate set to true. Setting aggregate to > false with a specified output directory has the same result as specifying no > output directory and aggregate to false, i.e. a non-empty > surefire-report.html file is created, but it has no test results since it is > the top level pom. > > > > org.apache.maven.plugins > maven-surefire-plugin > > > org.apache.maven.plugins > maven-surefire-report-plugin > > /data/reports > true > > > > test > > report-only > > > > > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-478) Specifying true plus an results in an empty surefire-report.html file
[ http://jira.codehaus.org/browse/SUREFIRE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128596#action_128596 ] Robert Shanahan commented on SUREFIRE-478: -- I tried data/reports and that didn't work either. I also tried configuring this under the section and got exactly the same results. > Specifying true plus an results in > an empty surefire-report.html file > -- > > Key: SUREFIRE-478 > URL: http://jira.codehaus.org/browse/SUREFIRE-478 > Project: Maven Surefire > Issue Type: Bug > Components: report plugin >Affects Versions: 2.4.2 > Environment: Windows XP SP2; jdk1.5.0_14; Maven 2.0.8 >Reporter: Robert Shanahan > > The following configuration snippet, from the parent pom of a multi-module > project, results in an empty surefire-report.html file. Using default output > directory works just fine with aggregate set to true. Setting aggregate to > false with a specified output directory has the same result as specifying no > output directory and aggregate to false, i.e. a non-empty > surefire-report.html file is created, but it has no test results since it is > the top level pom. > > > > org.apache.maven.plugins > maven-surefire-plugin > > > org.apache.maven.plugins > maven-surefire-report-plugin > > /data/reports > true > > > > test > > report-only > > > > > > -- 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: (SUREFIRE-478) Specifying true plus an results in an empty surefire-report.html file
[ http://jira.codehaus.org/browse/SUREFIRE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128596#action_128596 ] rshan edited comment on SUREFIRE-478 at 3/25/08 5:47 PM: --- I tried data/reports and that didn't work either. I also tried configuring this under the section and got exactly the same results. org.apache.maven.plugins maven-surefire-report-plugin /data/reports true was (Author: rshan): I tried data/reports and that didn't work either. I also tried configuring this under the section and got exactly the same results. > Specifying true plus an results in > an empty surefire-report.html file > -- > > Key: SUREFIRE-478 > URL: http://jira.codehaus.org/browse/SUREFIRE-478 > Project: Maven Surefire > Issue Type: Bug > Components: report plugin >Affects Versions: 2.4.2 > Environment: Windows XP SP2; jdk1.5.0_14; Maven 2.0.8 >Reporter: Robert Shanahan > > The following configuration snippet, from the parent pom of a multi-module > project, results in an empty surefire-report.html file. Using default output > directory works just fine with aggregate set to true. Setting aggregate to > false with a specified output directory has the same result as specifying no > output directory and aggregate to false, i.e. a non-empty > surefire-report.html file is created, but it has no test results since it is > the top level pom. > > > > org.apache.maven.plugins > maven-surefire-plugin > > > org.apache.maven.plugins > maven-surefire-report-plugin > > /data/reports > true > > > > test > > report-only > > > > > > -- 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: (SUREFIRE-478) Specifying true plus an results in an empty surefire-report.html file
[ http://jira.codehaus.org/browse/SUREFIRE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128596#action_128596 ] rshan edited comment on SUREFIRE-478 at 3/25/08 5:48 PM: --- I tried data/reports and that didn't work either. I also tried configuring this under the section and got exactly the same results. org.apache.maven.plugins maven-surefire-report-plugin /data/reports true was (Author: rshan): I tried data/reports and that didn't work either. I also tried configuring this under the section and got exactly the same results. org.apache.maven.plugins maven-surefire-report-plugin /data/reports true > Specifying true plus an results in > an empty surefire-report.html file > -- > > Key: SUREFIRE-478 > URL: http://jira.codehaus.org/browse/SUREFIRE-478 > Project: Maven Surefire > Issue Type: Bug > Components: report plugin >Affects Versions: 2.4.2 > Environment: Windows XP SP2; jdk1.5.0_14; Maven 2.0.8 >Reporter: Robert Shanahan > > The following configuration snippet, from the parent pom of a multi-module > project, results in an empty surefire-report.html file. Using default output > directory works just fine with aggregate set to true. Setting aggregate to > false with a specified output directory has the same result as specifying no > output directory and aggregate to false, i.e. a non-empty > surefire-report.html file is created, but it has no test results since it is > the top level pom. > > > > org.apache.maven.plugins > maven-surefire-plugin > > > org.apache.maven.plugins > maven-surefire-report-plugin > > /data/reports > true > > > > test > > report-only > > > > > > -- 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: (SUREFIRE-478) Specifying true plus an results in an empty surefire-report.html file
[
http://jira.codehaus.org/browse/SUREFIRE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128596#action_128596
]
rshan edited comment on SUREFIRE-478 at 3/25/08 5:52 PM:
---
I tried data/reports and that didn't work either.
I also tried configuring this under the section and got exactly the
same results.
{code:xml}
org.apache.maven.plugins
maven-surefire-report-plugin
/data/reports
true
{code}
was (Author: rshan):
I tried data/reports and that didn't work either.
I also tried configuring this under the section and got exactly the
same results.
org.apache.maven.plugins
maven-surefire-report-plugin
/data/reports
true
> Specifying true plus an results in
> an empty surefire-report.html file
> --
>
> Key: SUREFIRE-478
> URL: http://jira.codehaus.org/browse/SUREFIRE-478
> Project: Maven Surefire
> Issue Type: Bug
> Components: report plugin
>Affects Versions: 2.4.2
> Environment: Windows XP SP2; jdk1.5.0_14; Maven 2.0.8
>Reporter: Robert Shanahan
>
> The following configuration snippet, from the parent pom of a multi-module
> project, results in an empty surefire-report.html file. Using default output
> directory works just fine with aggregate set to true. Setting aggregate to
> false with a specified output directory has the same result as specifying no
> output directory and aggregate to false, i.e. a non-empty
> surefire-report.html file is created, but it has no test results since it is
> the top level pom.
>
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
>
>
> org.apache.maven.plugins
> maven-surefire-report-plugin
>
> /data/reports
> true
>
>
>
> test
>
> report-only
>
>
>
>
>
>
--
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: (SUREFIRE-478) Specifying true plus an results in an empty surefire-report.html file
[
http://jira.codehaus.org/browse/SUREFIRE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128596#action_128596
]
rshan edited comment on SUREFIRE-478 at 3/25/08 5:53 PM:
---
I tried data/reports and that didn't work either.
I also tried configuring this under the section and got exactly the
same results.
{code:xml}
org.apache.maven.plugins
maven-surefire-report-plugin
/data/reports
true
{code}
was (Author: rshan):
I tried data/reports and that didn't work either.
I also tried configuring this under the section and got exactly the
same results.
{code:xml}
org.apache.maven.plugins
maven-surefire-report-plugin
/data/reports
true
{code}
> Specifying true plus an results in
> an empty surefire-report.html file
> --
>
> Key: SUREFIRE-478
> URL: http://jira.codehaus.org/browse/SUREFIRE-478
> Project: Maven Surefire
> Issue Type: Bug
> Components: report plugin
>Affects Versions: 2.4.2
> Environment: Windows XP SP2; jdk1.5.0_14; Maven 2.0.8
>Reporter: Robert Shanahan
>
> The following configuration snippet, from the parent pom of a multi-module
> project, results in an empty surefire-report.html file. Using default output
> directory works just fine with aggregate set to true. Setting aggregate to
> false with a specified output directory has the same result as specifying no
> output directory and aggregate to false, i.e. a non-empty
> surefire-report.html file is created, but it has no test results since it is
> the top level pom.
>
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
>
>
> org.apache.maven.plugins
> maven-surefire-report-plugin
>
> /data/reports
> true
>
>
>
> test
>
> report-only
>
>
>
>
>
>
--
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: (MRESOURCES-61) PluginDescriptor not found
[ http://jira.codehaus.org/browse/MRESOURCES-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128626#action_128626 ] Brill Pappin commented on MRESOURCES-61: Yes, in that case I needed a VPN up... however my build should still not fail. > PluginDescriptor not found > -- > > Key: MRESOURCES-61 > URL: http://jira.codehaus.org/browse/MRESOURCES-61 > Project: Maven 2.x Resources Plugin > Issue Type: Bug >Reporter: Brill Pappin > > The following error, every time I run a build has been ongoing for quite some > time now. > 3/21/08 3:34:06 PM EDT: Build error for /aleixo-console/pom.xml; > java.lang.IllegalStateException: The PluginDescriptor for the plugin > org.apache.maven.plugins:maven-resources-plugin was not found > It seems to go away if I run with a -U to update the plugins but comes back > regularly. > Can somebody please fix whatever issue is causing this to occur? -- 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: (MRESOURCES-61) PluginDescriptor not found
[ http://jira.codehaus.org/browse/MRESOURCES-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brill Pappin updated MRESOURCES-61: --- Attachment: maven-eclipse-integration-plugin.txt This evening I have another one for you. different machine, different OS, different network etc but the same problem. This one is from the Maven Eclipse Integration plugin, with debug turned on. I'm including all the output int he hope that it will give you guys a clue however the relevant portion is: 3/25/08 8:49:19 PM EDT: [DEBUG] Using the following artifacts for classpath of: org.apache.maven.plugins:maven-resources-plugin:maven-plugin:2.3-SNAPSHOT: [org.codehaus.plexus:plexus-utils:jar:1.1:runtime] 3/25/08 8:49:19 PM EDT: [DEBUG] Retrieving realm for plugin with id: /plugins/org.apache.maven.plugins:maven-resources-plugin:[EMAIL PROTECTED] 3/25/08 8:49:19 PM EDT: [DEBUG] Creating realm for plugin with id: /plugins/org.apache.maven.plugins:maven-resources-plugin:[EMAIL PROTECTED] 3/25/08 8:49:19 PM EDT: [DEBUG] Created realm: ClassRealm[/plugins/org.apache.maven.plugins:maven-resources-plugin:[EMAIL PROTECTED], parent: null] for plugin: org.apache.maven.plugins:maven-resources-plugin 3/25/08 8:49:19 PM EDT: [DEBUG] Discovering components in realm: ClassRealm[/plugins/org.apache.maven.plugins:maven-resources-plugin:[EMAIL PROTECTED], parent: null] 3/25/08 8:49:19 PM EDT: [DEBUG] Checking for plugin descriptor for: org.apache.maven.plugins:maven-resources-plugin with version: 2.3-20060725.131549-1 in collector: [EMAIL PROTECTED] 3/25/08 8:49:19 PM EDT: Build error for /sgutility/pom.xml; java.lang.IllegalStateException: The PluginDescriptor for the plugin org.apache.maven.plugins:maven-resources-plugin was not found > PluginDescriptor not found > -- > > Key: MRESOURCES-61 > URL: http://jira.codehaus.org/browse/MRESOURCES-61 > Project: Maven 2.x Resources Plugin > Issue Type: Bug >Reporter: Brill Pappin > Attachments: maven-eclipse-integration-plugin.txt > > > The following error, every time I run a build has been ongoing for quite some > time now. > 3/21/08 3:34:06 PM EDT: Build error for /aleixo-console/pom.xml; > java.lang.IllegalStateException: The PluginDescriptor for the plugin > org.apache.maven.plugins:maven-resources-plugin was not found > It seems to go away if I run with a -U to update the plugins but comes back > regularly. > Can somebody please fix whatever issue is causing this to occur? -- 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: (MRESOURCES-61) PluginDescriptor not found
[ http://jira.codehaus.org/browse/MRESOURCES-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128628#action_128628 ] Olivier Lamy commented on MRESOURCES-61: lock plugin versions in your pom ! > PluginDescriptor not found > -- > > Key: MRESOURCES-61 > URL: http://jira.codehaus.org/browse/MRESOURCES-61 > Project: Maven 2.x Resources Plugin > Issue Type: Bug >Reporter: Brill Pappin > Attachments: maven-eclipse-integration-plugin.txt > > > The following error, every time I run a build has been ongoing for quite some > time now. > 3/21/08 3:34:06 PM EDT: Build error for /aleixo-console/pom.xml; > java.lang.IllegalStateException: The PluginDescriptor for the plugin > org.apache.maven.plugins:maven-resources-plugin was not found > It seems to go away if I run with a -U to update the plugins but comes back > regularly. > Can somebody please fix whatever issue is causing this to occur? -- 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: (MRESOURCES-61) PluginDescriptor not found
[ http://jira.codehaus.org/browse/MRESOURCES-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128626#action_128626 ] brill edited comment on MRESOURCES-61 at 3/25/08 8:00 PM: - Yes, in that case I needed a VPN up... however my build should still not fail. The fact is that the plugin is already in my local repo... verified and checked. was (Author: brill): Yes, in that case I needed a VPN up... however my build should still not fail. > PluginDescriptor not found > -- > > Key: MRESOURCES-61 > URL: http://jira.codehaus.org/browse/MRESOURCES-61 > Project: Maven 2.x Resources Plugin > Issue Type: Bug >Reporter: Brill Pappin > Attachments: maven-eclipse-integration-plugin.txt > > > The following error, every time I run a build has been ongoing for quite some > time now. > 3/21/08 3:34:06 PM EDT: Build error for /aleixo-console/pom.xml; > java.lang.IllegalStateException: The PluginDescriptor for the plugin > org.apache.maven.plugins:maven-resources-plugin was not found > It seems to go away if I run with a -U to update the plugins but comes back > regularly. > Can somebody please fix whatever issue is causing this to occur? -- 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: (MRESOURCES-61) PluginDescriptor not found
[ http://jira.codehaus.org/browse/MRESOURCES-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128629#action_128629 ] Brill Pappin commented on MRESOURCES-61: Yes I can do that, but I shouldn't have to... every other plugin works just fine. The point of *not* locking it is that you get updates (like when this issue gets some respect) :) > PluginDescriptor not found > -- > > Key: MRESOURCES-61 > URL: http://jira.codehaus.org/browse/MRESOURCES-61 > Project: Maven 2.x Resources Plugin > Issue Type: Bug >Reporter: Brill Pappin > Attachments: maven-eclipse-integration-plugin.txt > > > The following error, every time I run a build has been ongoing for quite some > time now. > 3/21/08 3:34:06 PM EDT: Build error for /aleixo-console/pom.xml; > java.lang.IllegalStateException: The PluginDescriptor for the plugin > org.apache.maven.plugins:maven-resources-plugin was not found > It seems to go away if I run with a -U to update the plugins but comes back > regularly. > Can somebody please fix whatever issue is causing this to occur? -- 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-1983) Upload ZK 3.0.4 to the central repository
Upload ZK 3.0.4 to the central repository - Key: MAVENUPLOAD-1983 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1983 Project: maven-upload-requests Issue Type: Task Reporter: Tom M. Yeh http://www.zkoss.org/maven/bundles/3.0.4/zcommon-3.0.4-bundle.jar http://www.zkoss.org/maven/bundles/3.0.4/zweb-3.0.4-bundle.jar http://www.zkoss.org/maven/bundles/3.0.4/zk-3.0.4-bundle.jar http://www.zkoss.org/maven/bundles/3.0.4/zul-3.0.4-bundle.jar http://www.zkoss.org/maven/bundles/3.0.4/zhtml-3.0.4-bundle.jar http://www.zkoss.org/maven/bundles/3.0.4/zml-3.0.4-bundle.jar http://www.zkoss.org/maven/bundles/3.0.4/zkex-3.0.4-bundle.jar http://www.zkoss.org/maven/bundles/3.0.4/zkmax-3.0.4-bundle.jar http://www.zkoss.org/maven/bundles/3.0.4/zkplus-3.0.4-bundle.jar http://www.zkoss.org http://sourceforge.net/users/tomyeh/ ZK is an open-source Ajax Web framework that enables rich user interface for Web applications with no JavaScript and little programming. -- 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
