[jira] Issue Comment Edited: (MNG-3688) Not activating profiles correctly
[ http://jira.codehaus.org/browse/MNG-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143432#action_143432 ] magne.n edited comment on MNG-3688 at 7/29/08 1:45 AM: --- I have tested the issue against a build of the NB61FCS branch (2.1-SNAPSHOT lastUpdated: 20080729060013). Issue exists there aswell. was (Author: magne.n): I have tested the issue against a build of the NB61FCS branch (Built 2008-07-29T08:15:99 ). Issue exists there aswell. > Not activating profiles correctly > - > > Key: MNG-3688 > URL: http://jira.codehaus.org/browse/MNG-3688 > Project: Maven 2 > Issue Type: Bug > Components: Embedding, IDEs >Affects Versions: 2.1 >Reporter: Magne Nordtveit > Attachments: profilereprod.tar.gz > > > Mevenide doesn't properly load profiles based on . More > correctly, it doesn't properly not activate a profile when > > > some.file > > > is specified. The profile is activated regardless when running from netbeans. > maven 2.0.9 console: > Activated Profiles: > test-active > maven 2.1-SNAPSHOT console: > Activated Profiles: > test-active > mevenide 3.1.3 (NB61FCS branch): > Activated Profiles > test-active > test-not-active > test-not-active should only be activated when pom.xml is missing. > Test project attached. -- 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-3688) Not activating profiles correctly
[ http://jira.codehaus.org/browse/MNG-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143432#action_143432 ] magne.n edited comment on MNG-3688 at 7/29/08 1:42 AM: --- I have tested the issue against a build of the NB61FCS branch (Built 2008-07-29T08:15:99 ). Issue exists there aswell. was (Author: magne.n): I have tested the issue against a build of the NB61FCS branch. Issue exists there aswell. > Not activating profiles correctly > - > > Key: MNG-3688 > URL: http://jira.codehaus.org/browse/MNG-3688 > Project: Maven 2 > Issue Type: Bug > Components: Embedding, IDEs >Affects Versions: 2.1 >Reporter: Magne Nordtveit > Attachments: profilereprod.tar.gz > > > Mevenide doesn't properly load profiles based on . More > correctly, it doesn't properly not activate a profile when > > > some.file > > > is specified. The profile is activated regardless when running from netbeans. > maven 2.0.9 console: > Activated Profiles: > test-active > maven 2.1-SNAPSHOT console: > Activated Profiles: > test-active > mevenide 3.1.3 (NB61FCS branch): > Activated Profiles > test-active > test-not-active > test-not-active should only be activated when pom.xml is missing. > Test project attached. -- 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-3688) Not activating profiles correctly
[ http://jira.codehaus.org/browse/MNG-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143432#action_143432 ] Magne Nordtveit commented on MNG-3688: -- I have tested the issue against a build of the NB61FCS branch. Issue exists there aswell. > Not activating profiles correctly > - > > Key: MNG-3688 > URL: http://jira.codehaus.org/browse/MNG-3688 > Project: Maven 2 > Issue Type: Bug > Components: Embedding, IDEs >Affects Versions: 2.1 >Reporter: Magne Nordtveit > Attachments: profilereprod.tar.gz > > > Mevenide doesn't properly load profiles based on . More > correctly, it doesn't properly not activate a profile when > > > some.file > > > is specified. The profile is activated regardless when running from netbeans. > maven 2.0.9 console: > Activated Profiles: > test-active > maven 2.1-SNAPSHOT console: > Activated Profiles: > test-active > mevenide 3.1.3 (NB61FCS branch): > Activated Profiles > test-active > test-not-active > test-not-active should only be activated when pom.xml is missing. > Test project attached. -- 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-3688) Not activating profiles correctly
[ http://jira.codehaus.org/browse/MNG-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143431#action_143431 ] Milos Kleint commented on MNG-3688: --- the netbeans integration is using 2.1-SNAPSHOT maven embedder. The version bundled with 3.1.3 is 20080522. > Not activating profiles correctly > - > > Key: MNG-3688 > URL: http://jira.codehaus.org/browse/MNG-3688 > Project: Maven 2 > Issue Type: Bug > Components: Embedding, IDEs >Affects Versions: 2.1 >Reporter: Magne Nordtveit > Attachments: profilereprod.tar.gz > > > Mevenide doesn't properly load profiles based on . More > correctly, it doesn't properly not activate a profile when > > > some.file > > > is specified. The profile is activated regardless when running from netbeans. > maven 2.0.9 console: > Activated Profiles: > test-active > maven 2.1-SNAPSHOT console: > Activated Profiles: > test-active > mevenide 3.1.3 (NB61FCS branch): > Activated Profiles > test-active > test-not-active > test-not-active should only be activated when pom.xml is missing. > Test project attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MNG-3688) Not activating profiles correctly
[ http://jira.codehaus.org/browse/MNG-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milos Kleint moved MEVENIDE-652 to MNG-3688: Assignee: (was: Anuradha Gunasekara) Affects Version/s: (was: NB_3.1) 2.1 Component/s: (was: mevenide2-netbeans) IDEs Embedding Complexity: Intermediate Workflow: Maven New (was: jira) Key: MNG-3688 (was: MEVENIDE-652) Project: Maven 2 (was: mevenide) > Not activating profiles correctly > - > > Key: MNG-3688 > URL: http://jira.codehaus.org/browse/MNG-3688 > Project: Maven 2 > Issue Type: Bug > Components: Embedding, IDEs >Affects Versions: 2.1 >Reporter: Magne Nordtveit > Attachments: profilereprod.tar.gz > > > Mevenide doesn't properly load profiles based on . More > correctly, it doesn't properly not activate a profile when > > > some.file > > > is specified. The profile is activated regardless when running from netbeans. > maven 2.0.9 console: > Activated Profiles: > test-active > maven 2.1-SNAPSHOT console: > Activated Profiles: > test-active > mevenide 3.1.3 (NB61FCS branch): > Activated Profiles > test-active > test-not-active > test-not-active should only be activated when pom.xml is missing. > Test project attached. -- 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: (MENFORCER-42) Maven-Enforcer-Plugin fails in multimodule project when artifacts not in repository
[
http://jira.codehaus.org/browse/MENFORCER-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143426#action_143426
]
Jörg Hohwiller commented on MENFORCER-42:
-
I am having the same problem no matter if I use enforce-once or enforce. E.g.
If I do "mvn eclipse:eclipse" the build fails if some reactor-dependency is NOT
already installed in the local repository. When I remove the enforcer-plugin
from my toplevel POM everything works well. This makes the enforcer-plugin
useless since it causes more harm than it helps.
> Maven-Enforcer-Plugin fails in multimodule project when artifacts not in
> repository
> ---
>
> Key: MENFORCER-42
> URL: http://jira.codehaus.org/browse/MENFORCER-42
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 1.0-alpha-3, 1.0
> Environment: Tested with Maven 2.0.7 and 2.0.8 on Linux with Java 1.5
>Reporter: Martin Höller
>Assignee: Brian Fox
> Attachments: enforcer-test.tar.gz
>
>
> Create a new simple multimodule-project and call {{mvn validate}} at the
> toplevel. This leads to a build failure if none of the multimodule-artifacts
> are in your local repository.
> Attached is a simple test project for reproducing this bug.
--
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-3599) webdav does not set http-proxy correctly
[ http://jira.codehaus.org/browse/MNG-3599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-3599: -- Fix Version/s: 2.1-alpha-1 > webdav does not set http-proxy correctly > > > Key: MNG-3599 > URL: http://jira.codehaus.org/browse/MNG-3599 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.9 >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 2.0.11, 2.1-alpha-1 > > Attachments: MNG-3599.patch > > > patch is attached to WAGON-82 > (0001-Make-the-artifact-manager-using-wagons-ProxyInfoProv.patch), utilising > the new APIs in beta-3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3599) webdav does not set http-proxy correctly
[ http://jira.codehaus.org/browse/MNG-3599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-3599. - Resolution: Fixed Fix Version/s: (was: 2.1-alpha-2) 2.0.11 > webdav does not set http-proxy correctly > > > Key: MNG-3599 > URL: http://jira.codehaus.org/browse/MNG-3599 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.9 >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 2.0.11 > > Attachments: MNG-3599.patch > > > patch is attached to WAGON-82 > (0001-Make-the-artifact-manager-using-wagons-ProxyInfoProv.patch), utilising > the new APIs in beta-3 -- 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-111) Additional webResources are not added to the component list when using WTP projects generation
[
http://jira.codehaus.org/browse/MECLIPSE-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Baker updated MECLIPSE-111:
-
Attachment: eclipse_dot_component_web_resources.patch
Here is a rewritten patch based on the original written by Alexandre Poitras.
It is based off svn tag maven-eclipse-plugin-2.5.1.
It only modifies one method in one file and as far as I can tell uses current
code conventions.
Could someone please take a look at it?
> Additional webResources are not added to the component list when using WTP
> projects generation
> --
>
> Key: MECLIPSE-111
> URL: http://jira.codehaus.org/browse/MECLIPSE-111
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: WTP support
>Affects Versions: 2.2
>Reporter: Renaud Julienne
> Attachments: eclipse_dot_component_web_resources.patch,
> MECLIPSE-111-patch.txt
>
>
> I have a war project, with the standard layout :
> + project
> + src
> + main
> + java
> + resources
> + webapp
> But my project is also relying on a common web application framework,
> containing web resources I must add to my project.
> So in the pom.xml, for the maven-war-plugin configuration, I have additional
> webResources declared :
>
> maven-war-plugin
>
>
>
> ${project.build.directory}/fwk
>
>
>
>
> When I generate the eclipse project, with WTP activated, the .component
> generated does not include the wb-resource element corresponding to my
> webResource. It should contain :
>
--
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: (MCHANGES-120) announcement:generate mojo should warn, not fail if the changes file doesn't exist.
[ http://jira.codehaus.org/browse/MCHANGES-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143412#action_143412 ] Justin Edelson commented on MCHANGES-120: - Is the 2.1 release contingent upon Maven 2.1 being released? > announcement:generate mojo should warn, not fail if the changes file doesn't > exist. > --- > > Key: MCHANGES-120 > URL: http://jira.codehaus.org/browse/MCHANGES-120 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: announcement >Affects Versions: 2.0 >Reporter: Justin Edelson >Assignee: Olivier Lamy > Fix For: 2.1 > > Attachments: changes-nofail.patch > > > Trying to use the changes plugin in a multi-module project where not all the > modules have changes files. IMHO, this shouldn't cause the build to fail, > just spit out a warning. -- 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: (MCHANGES-86) Create a changes-validate mojo
[ http://jira.codehaus.org/browse/MCHANGES-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MCHANGES-86. Resolution: Fixed fixed in rev 680563. > Create a changes-validate mojo > -- > > Key: MCHANGES-86 > URL: http://jira.codehaus.org/browse/MCHANGES-86 > Project: Maven 2.x Changes Plugin > Issue Type: New Feature > Components: changes-report >Reporter: Dennis Lundberg >Assignee: Olivier Lamy > Fix For: 2.1 > > > This mojo should validate the changes.xml file, and report any errors to the > user in an easy to understand format. -- 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: (MCHANGES-121) Incorrect Component value in report for multi-component JIRA issue
Incorrect Component value in report for multi-component JIRA issue -- Key: MCHANGES-121 URL: http://jira.codehaus.org/browse/MCHANGES-121 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: jira-report Reporter: David Rauschenbach Priority: Minor I have a JIRA issue that has a multi-valued component value (eg "Component-A, Component-B, Component-C"). I run a jira-report from my pom file with a filter on Component-C only. The report displays the first component of a multi-component JIRA issue, even when the displayed component does not match one of the components in the component filter. -- 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-111) Additional webResources are not added to the component list when using WTP projects generation
[ http://jira.codehaus.org/browse/MECLIPSE-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143409#action_143409 ] Steve Baker commented on MECLIPSE-111: -- We too have a great need for this feature. Our web projects have different overlay directories for different local development configurations. At the very least could someone review the current patch and provide feedback on what the next step might be? To get overlays working within WTP we've had to resort to writing ant tasklets to patch .component as per the following snippet: org.apache.maven.plugins maven-antrun-plugin patch_dot_component initialize run source-path="src/webapp/www" source-path="src/webapp/www"/>Additional webResources are not added to the component list when using WTP > projects generation > -- > > Key: MECLIPSE-111 > URL: http://jira.codehaus.org/browse/MECLIPSE-111 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.2 >Reporter: Renaud Julienne > Attachments: MECLIPSE-111-patch.txt > > > I have a war project, with the standard layout : > + project > + src > + main > + java > + resources > + webapp > But my project is also relying on a common web application framework, > containing web resources I must add to my project. > So in the pom.xml, for the maven-war-plugin configuration, I have additional > webResources declared : > > maven-war-plugin > > > > ${project.build.directory}/fwk > > > > > When I generate the eclipse project, with WTP activated, the .component > generated does not include the wb-resource element corresponding to my > webResource. It should contain : > -- 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-1991) Can't get transitive dependencies from a war pom when this war is added as a depdency of a project
[ http://jira.codehaus.org/browse/MNG-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143407#action_143407 ] Brent N Atkinson commented on MNG-1991: --- I believe the J2EE/JavaEE specifications designate packaging to an 'assembler' role for good reason. The code for web module and resource adapters (a real connector, not simply a configured JDBC pool) are managed well as plain jars. Dependencies are satisfied by external jars, and you have fine grained control over reuse. IMHO, making wars, rars, and ears first-class maven citizens seems a bit strange. The way you package them changes on the environment, Appserver, et cetera. The compiled code doesn't change. I have used the rar, ear and war plugins to build both skinny and full-fledged components. I can appreciate why you would want to package the full fledged components (at least war and rar) because they are reusable components much like the jar. They are intended to be boxed up and reused. However, these components imply configuration and repackaging (Class-Path entries in the manifests of modules, moving jars to ear-level, changing init-params, configuring security, adding appserver specific descriptors, etc). This seems to indicate that they are not artifacts in the traditional maven sense. They are not static like jars, so storing them as such doesn't make much sense. It may not make sense to store them with the jar dependencies bundled; this is like storing uberjars all over the place. Perhaps the realization of an war/ear with dependencies is better deferred? Wars and rars are ideally treated as components. So it may make sense to store them with their external dependencies. However, I believe dependency meta data could be used. This would perhaps be something like a dependency scope 'aggregate'? It would imply that transitivity blocks at the artifact that aggregates them. Unfortunately, if dependency meta data isn't available to dependent artifacts you can no longer identify or resolve conflicts, et cetera. If you could use this meta data, then you could perhaps control the ultimate fate of the dependencies through something like dependencyManagement. It may be enough information for an intelligent assembly plugin to realize the aggregate dependencies and patch up bundled modules with Class-Path manifest entries, et cetera. > Can't get transitive dependencies from a war pom when this war is added as a > depdency of a project > -- > > Key: MNG-1991 > URL: http://jira.codehaus.org/browse/MNG-1991 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.2 >Reporter: Emmanuel Venisse > Fix For: 2.1 > > > I have a project (continuum-core-it) that need to use all transitive > dependencies of a war (continuum-webapp). If i add the war as a dependency of > the project with packaging war, war dependencies aren't shown by project, > maven doesn't try to resolve them and doesn't add them in classpath. > If if replace packaging from war to pom, all dependencies are resolved and > added to classpath. -- 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: (MCHANGES-120) announcement:generate mojo should warn, not fail if the changes file doesn't exist.
[ http://jira.codehaus.org/browse/MCHANGES-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MCHANGES-120. - Resolution: Fixed Fixed in rev 680485. Thanks! > announcement:generate mojo should warn, not fail if the changes file doesn't > exist. > --- > > Key: MCHANGES-120 > URL: http://jira.codehaus.org/browse/MCHANGES-120 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: announcement >Affects Versions: 2.0 >Reporter: Justin Edelson >Assignee: Olivier Lamy > Fix For: 2.1 > > Attachments: changes-nofail.patch > > > Trying to use the changes plugin in a multi-module project where not all the > modules have changes files. IMHO, this shouldn't cause the build to fail, > just spit out a warning. -- 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-3622) upgrade to wagon beta-3
[ http://jira.codehaus.org/browse/MNG-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey reopened MNG-3622: - rolling back to -beta-2 due to lack of proxy support. I'll use this issue to track the other JIRAs related to this change that will be reopened/pushed until we can let a correcting release soak for a period of time in the community. > upgrade to wagon beta-3 > --- > > Key: MNG-3622 > URL: http://jira.codehaus.org/browse/MNG-3622 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.9 >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 2.0.10 > > > I am scheduling this for 2.1-alpha-1, but I will also look into the > possibility of including it in 2.0.10 after consulting the dev list -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2739) Repository entries are not validated and NPE will occur
[ http://jira.codehaus.org/browse/MNG-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MNG-2739. --- Resolution: Fixed fixed in 2.0.10 branch, will port/merge over to 2.0.x and trunk branches now. > Repository entries are not validated and NPE will occur > --- > > Key: MNG-2739 > URL: http://jira.codehaus.org/browse/MNG-2739 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Reporter: Jason van Zyl >Assignee: John Casey > Fix For: 2.0.10, 2.1-alpha-1 > > > Using something like the following has no id and an incorrect file url: > > cbuilds > > > > /Users/jvanzyl/js/org/codehaus/mojo/trunk/mojo/mojo-sandbox/c-builds/test-cpkg/m2-repo > > > > java.lang.NullPointerException > at > org.apache.maven.wagon.repository.Repository.hashCode(Repository.java:239) > at java.util.HashMap.hash(HashMap.java:264) > at java.util.HashMap.put(HashMap.java:382) > at java.util.HashSet.add(HashSet.java:194) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:665) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:416) > at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:192) > at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) > at > org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) > at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > 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) -- 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-2739) Repository entries are not validated and NPE will occur
[ http://jira.codehaus.org/browse/MNG-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143396#action_143396 ] John Casey commented on MNG-2739: - See MODELLO-44 > Repository entries are not validated and NPE will occur > --- > > Key: MNG-2739 > URL: http://jira.codehaus.org/browse/MNG-2739 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Reporter: Jason van Zyl >Assignee: John Casey > Fix For: 2.0.10, 2.1-alpha-1 > > > Using something like the following has no id and an incorrect file url: > > cbuilds > > > > /Users/jvanzyl/js/org/codehaus/mojo/trunk/mojo/mojo-sandbox/c-builds/test-cpkg/m2-repo > > > > java.lang.NullPointerException > at > org.apache.maven.wagon.repository.Repository.hashCode(Repository.java:239) > at java.util.HashMap.hash(HashMap.java:264) > at java.util.HashMap.put(HashMap.java:382) > at java.util.HashSet.add(HashSet.java:194) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:665) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:416) > at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:192) > at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) > at > org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) > at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > 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) -- 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: (MCHANGES-120) announcement:generate mojo should warn, not fail if the changes file doesn't exist.
[ http://jira.codehaus.org/browse/MCHANGES-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MCHANGES-120: -- Assignee: Olivier Lamy Fix Version/s: 2.1 > announcement:generate mojo should warn, not fail if the changes file doesn't > exist. > --- > > Key: MCHANGES-120 > URL: http://jira.codehaus.org/browse/MCHANGES-120 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: announcement >Affects Versions: 2.0 >Reporter: Justin Edelson >Assignee: Olivier Lamy > Fix For: 2.1 > > Attachments: changes-nofail.patch > > > Trying to use the changes plugin in a multi-module project where not all the > modules have changes files. IMHO, this shouldn't cause the build to fail, > just spit out a warning. -- 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: (MCHANGES-120) announcement:generate mojo should warn, not fail if the changes file doesn't exist.
[ http://jira.codehaus.org/browse/MCHANGES-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated MCHANGES-120: Attachment: changes-nofail.patch Here's a patch against trunk. I'm using a patched version of 2.0 for now. > announcement:generate mojo should warn, not fail if the changes file doesn't > exist. > --- > > Key: MCHANGES-120 > URL: http://jira.codehaus.org/browse/MCHANGES-120 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: announcement >Affects Versions: 2.0 >Reporter: Justin Edelson > Attachments: changes-nofail.patch > > > Trying to use the changes plugin in a multi-module project where not all the > modules have changes files. IMHO, this shouldn't cause the build to fail, > just spit out a warning. -- 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-2156) Mockito 1.5 upload request
Mockito 1.5 upload request -- Key: MAVENUPLOAD-2156 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2156 Project: Maven Upload Requests Issue Type: Wish Reporter: Igor Czechowski http://mockito.googlecode.com/svn/branches/1.5/maven/mockito-core-1.5-bundle.jar http://mockito.googlecode.com/svn/branches/1.5/maven/mockito-all-1.5-bundle.jar http://code.google.com/p/mockito/ http://code.google.com/u/iczechowski/ I'm a project member in Mockito, please upload these two bundles. -- 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: (MCHANGES-120) announcement:generate mojo should warn, not fail if the changes file doesn't exist.
announcement:generate mojo should warn, not fail if the changes file doesn't exist. --- Key: MCHANGES-120 URL: http://jira.codehaus.org/browse/MCHANGES-120 Project: Maven 2.x Changes Plugin Issue Type: Improvement Components: announcement Affects Versions: 2.0 Reporter: Justin Edelson Trying to use the changes plugin in a multi-module project where not all the modules have changes files. IMHO, this shouldn't cause the build to fail, just spit out a warning. -- 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: (WAGON-231) PathUtils.toRelative() throws SIOOBE if supplied arguments specify the same directory
[
http://jira.codehaus.org/browse/WAGON-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143376#action_143376
]
Benjamin Bentmann commented on WAGON-231:
-
Forgot to mention: It is unclear what the return value should be for this case.
Could be empty string or "." as used in patch.
> PathUtils.toRelative() throws SIOOBE if supplied arguments specify the same
> directory
> -
>
> Key: WAGON-231
> URL: http://jira.codehaus.org/browse/WAGON-231
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-provider-api
>Affects Versions: 1.0-beta-3
>Reporter: Benjamin Bentmann
> Attachments: to-relative.patch
>
>
> i.e. {{PathUtils.toRelative( new File( "foo" ).getAbsoluteFile(), new File(
> "foo" ).getAbsolutePath() )}} fails.
--
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: (WAGON-231) PathUtils.toRelative() throws SIOOBE if supplied arguments specify the same directory
PathUtils.toRelative() throws SIOOBE if supplied arguments specify the same
directory
-
Key: WAGON-231
URL: http://jira.codehaus.org/browse/WAGON-231
Project: Maven Wagon
Issue Type: Bug
Components: wagon-provider-api
Affects Versions: 1.0-beta-3
Reporter: Benjamin Bentmann
Attachments: to-relative.patch
i.e. {{PathUtils.toRelative( new File( "foo" ).getAbsoluteFile(), new File(
"foo" ).getAbsolutePath() )}} fails.
--
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: (MANT-46) mvn ant:ant throws a StringIndexOutOfBoundsException
[
http://jira.codehaus.org/browse/MANT-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143373#action_143373
]
Emmanuel Bourg commented on MANT-46:
I'm not sure to know how to add a test case for a Maven plugin. The easiest way
to reproduce this I guess is to check out the Commons CLI project and issue the
mvn ant:ant command. The SVN repository is located there:
http://svn.apache.org/repos/asf/commons/proper/cli/branches/cli-1.x
> mvn ant:ant throws a StringIndexOutOfBoundsException
>
>
> Key: MANT-46
> URL: http://jira.codehaus.org/browse/MANT-46
> Project: Maven 2.x Ant Plugin
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Emmanuel Bourg
>
> I'm trying to generate a Ant build from the Maven 2 POM of Commons CLI but I
> get a StringIndexOutOfBoundsException. I don't know what this is supposed to
> mean.
> Here is the trace:
> {noformat}
> [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-ant-plugin:2.1:ant'
> -->
> [DEBUG] (f) localRepository = [local] -> file://C:\Documents and
> Settings\Smanux\.m2\repository
> [DEBUG] (f) overwrite = true
> [DEBUG] (f) project = MavenProject: commons-cli:commons-cli:1.2-SNAPSHOT @
> C:\dev\jakarta\cli\pom.xml
> [DEBUG] (f) remoteRepositories = [[apache.snapshots] ->
> http://people.apache.org/repo/m2-snapshot-repository, [central] ->
> http://repo1.maven.org/maven2]
> [DEBUG] (f) settings = [EMAIL PROTECTED]
> [DEBUG] -- end configuration --
> [INFO] [ant:ant]
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] String index out of range: -1
> [INFO]
>
> [DEBUG] Trace
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1768)
> at java.lang.String.substring(String.java:1735)
> at org.apache.maven.wagon.PathUtils.toRelative(PathUtils.java:434)
> at
> org.apache.maven.plugin.ant.AntBuildWriter.writeProperties(AntBuildWriter.java:464)
> at
> org.apache.maven.plugin.ant.AntBuildWriter.writeGeneratedBuildXml(AntBuildWriter.java:266)
> at
> org.apache.maven.plugin.ant.AntBuildWriter.writeBuildXmls(AntBuildWriter.java:113)
> at org.apache.maven.plugin.ant.AntMojo.execute(AntMojo.java:112)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.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)
> {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] Commented: (MANT-46) mvn ant:ant throws a StringIndexOutOfBoundsException
[
http://jira.codehaus.org/browse/MANT-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143370#action_143370
]
Vincent Siveton commented on MANT-46:
-
Could you add a test case?
> mvn ant:ant throws a StringIndexOutOfBoundsException
>
>
> Key: MANT-46
> URL: http://jira.codehaus.org/browse/MANT-46
> Project: Maven 2.x Ant Plugin
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Emmanuel Bourg
>
> I'm trying to generate a Ant build from the Maven 2 POM of Commons CLI but I
> get a StringIndexOutOfBoundsException. I don't know what this is supposed to
> mean.
> Here is the trace:
> {noformat}
> [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-ant-plugin:2.1:ant'
> -->
> [DEBUG] (f) localRepository = [local] -> file://C:\Documents and
> Settings\Smanux\.m2\repository
> [DEBUG] (f) overwrite = true
> [DEBUG] (f) project = MavenProject: commons-cli:commons-cli:1.2-SNAPSHOT @
> C:\dev\jakarta\cli\pom.xml
> [DEBUG] (f) remoteRepositories = [[apache.snapshots] ->
> http://people.apache.org/repo/m2-snapshot-repository, [central] ->
> http://repo1.maven.org/maven2]
> [DEBUG] (f) settings = [EMAIL PROTECTED]
> [DEBUG] -- end configuration --
> [INFO] [ant:ant]
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] String index out of range: -1
> [INFO]
>
> [DEBUG] Trace
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1768)
> at java.lang.String.substring(String.java:1735)
> at org.apache.maven.wagon.PathUtils.toRelative(PathUtils.java:434)
> at
> org.apache.maven.plugin.ant.AntBuildWriter.writeProperties(AntBuildWriter.java:464)
> at
> org.apache.maven.plugin.ant.AntBuildWriter.writeGeneratedBuildXml(AntBuildWriter.java:266)
> at
> org.apache.maven.plugin.ant.AntBuildWriter.writeBuildXmls(AntBuildWriter.java:113)
> at org.apache.maven.plugin.ant.AntMojo.execute(AntMojo.java:112)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.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)
> {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: (MANT-46) mvn ant:ant throws a StringIndexOutOfBoundsException
mvn ant:ant throws a StringIndexOutOfBoundsException
Key: MANT-46
URL: http://jira.codehaus.org/browse/MANT-46
Project: Maven 2.x Ant Plugin
Issue Type: Bug
Affects Versions: 2.1
Reporter: Emmanuel Bourg
I'm trying to generate a Ant build from the Maven 2 POM of Commons CLI but I
get a StringIndexOutOfBoundsException. I don't know what this is supposed to
mean.
Here is the trace:
{noformat}
[DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-ant-plugin:2.1:ant' -->
[DEBUG] (f) localRepository = [local] -> file://C:\Documents and
Settings\Smanux\.m2\repository
[DEBUG] (f) overwrite = true
[DEBUG] (f) project = MavenProject: commons-cli:commons-cli:1.2-SNAPSHOT @
C:\dev\jakarta\cli\pom.xml
[DEBUG] (f) remoteRepositories = [[apache.snapshots] ->
http://people.apache.org/repo/m2-snapshot-repository, [central] ->
http://repo1.maven.org/maven2]
[DEBUG] (f) settings = [EMAIL PROTECTED]
[DEBUG] -- end configuration --
[INFO] [ant:ant]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] String index out of range: -1
[INFO]
[DEBUG] Trace
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1768)
at java.lang.String.substring(String.java:1735)
at org.apache.maven.wagon.PathUtils.toRelative(PathUtils.java:434)
at
org.apache.maven.plugin.ant.AntBuildWriter.writeProperties(AntBuildWriter.java:464)
at
org.apache.maven.plugin.ant.AntBuildWriter.writeGeneratedBuildXml(AntBuildWriter.java:266)
at
org.apache.maven.plugin.ant.AntBuildWriter.writeBuildXmls(AntBuildWriter.java:113)
at org.apache.maven.plugin.ant.AntMojo.execute(AntMojo.java:112)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.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)
{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] Updated: (MSTAGE-7) Unable to use archiva as http source with maven-stage-plugin
[ http://jira.codehaus.org/browse/MSTAGE-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated MSTAGE-7: -- Attachment: MSTAGE-7.patch attached is the patch which will work without changes in archiva > Unable to use archiva as http source with maven-stage-plugin > > > Key: MSTAGE-7 > URL: http://jira.codehaus.org/browse/MSTAGE-7 > Project: Maven 2.x Stage Plugin > Issue Type: Bug >Affects Versions: 1.0-alpha-1 >Reporter: Dan Tran > Attachments: MSTAGE-7.patch > > > http-wagon-beta-2 currently not able to parse the archiva page ( > http://jira.codehaus.org/browse/MRM-891 ). > however with the fix from http://jira.codehaus.org/browse/MRM-893 and upgrade > to wagon-beta-3 will solve the problem > without change in stage plugin source code. -- 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
Next maven release plugin release?
Hi, I'm using 2.0-beta-7 of the maven release plugin, but I could really use the new support for accepting releaseVersion, developmentVersion, etc... from -D properties. Is the release of 2.0-beta-8 expected to happen soon, or should I roll my own version of 2.0-beta-7.1 or something? Thanks, Mat
[jira] Commented: (MSITE-234) Maven skin / version as plugin parameters
[
http://jira.codehaus.org/browse/MSITE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143361#action_143361
]
Stefano Bagnara commented on MSITE-234:
---
Dennis: I'm not an m2 guru, but that's what I expected. It's the same of having
a dependency between the 2 modules. Currently the "direct" dependency would be
updated while the skin dependency is ignored.
> Maven skin / version as plugin parameters
> -
>
> Key: MSITE-234
> URL: http://jira.codehaus.org/browse/MSITE-234
> Project: Maven 2.x Site Plugin
> Issue Type: Improvement
>Affects Versions: 2.0-beta-5
>Reporter: Stefano Bagnara
>
> I have an m2 reactor project where one of the modules is the skin used
> by one of the other modules (and every of its children).
> {noformat}
> root
> |- maven-skin
> '- module1 (using maven-skin)
> {noformat}
> The problem is that module1 declare the skin in its site.xml file and
> this way the version is not updated when I use the release:prepare to
> update my poms.
> So I checked the site plugin searching for a way to declare the skin in
> the plugin configuration instead of the site.xml descriptor but there is
> no such option.
> I think that a good solution would be to use something like the remote
> resource plugin (used for LICENSE/NOTICE) also for the skin declaration.
--
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-509) NoClassDefFoundError: org/apache/maven/surefire/booter/SurefireBooter with Java 1.3
NoClassDefFoundError: org/apache/maven/surefire/booter/SurefireBooter with Java
1.3
---
Key: SUREFIRE-509
URL: http://jira.codehaus.org/browse/SUREFIRE-509
Project: Maven Surefire
Issue Type: Bug
Affects Versions: 2.4.3
Environment: Windows XP, Sun JDK 1.3.1_20
Reporter: Emmanuel Bourg
Surefire fails to launch the tests with a 1.3 JVM, it returns a
NoClassDefFoundError on SurefireBooter.
I tried to run manually the surefirebooter.jar file created in the temp
directory, it worked with Java 5 but failed with Java 1.3 with the same error.
Here is the manifest of the jar:
{noformat}
Manifest-Version: 1.0
Class-Path: file:/C:/Documents%20and%20Settings/Smanux/.m2/repository/
org/apache/maven/surefire/surefire-booter/2.4.3/surefire-booter-2.4.3
.jar file:/C:/Documents%20and%20Settings/Smanux/.m2/repository/org/ap
ache/maven/surefire/surefire-api/2.4.3/surefire-api-2.4.3.jar file:/C
:/dev/jakarta/cli/target/test-classes/ file:/C:/dev/jakarta/cli/targe
t/classes/ file:/C:/Documents%20and%20Settings/Smanux/.m2/repository/
junit/junit/3.8.1/junit-3.8.1.jar
Main-Class: org.apache.maven.surefire.booter.SurefireBooter
{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] Commented: (SCM-182) git provider
[
http://jira.codehaus.org/browse/SCM-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143354#action_143354
]
Eugene Kuleshov commented on SCM-182:
-
Don, please read my comment. You don't need to release, just lock the version.
And again, if it works, why didn't you ask for release in the Maven dev list?
> git provider
>
>
> Key: SCM-182
> URL: http://jira.codehaus.org/browse/SCM-182
> Project: Maven SCM
> Issue Type: New Feature
> Components: maven-scm-provider-git
> Environment: Developed on Mac OS X 10.3.9 with git 1.2.4
>Reporter: Dominik Winter
>Assignee: Jason van Zyl
> Fix For: 1.1
>
> Attachments: git.patch, git.tar.bz2, SCM-182.patch, update1.patch.bz2
>
>
> Please find the git provider as attachment.
> Usefulness:
> I used the git provider together with
> [http://maven.apache.org/plugins/maven-release-plugin|maven-release-plugin],
> it works fine for that use case.
> Open issues:
> - the JUnit tests are "proprietary", not yet TCK. I'll fix that.
> If you want to run the tests, you must have git installed and it must be in
> your {{PATH}}.
> To run git:
> - on *Windows*: use [Cygwin|http://www.cygwin.com] and install the binutils,
> openssh, openssl, rsync, curl
> than you are able to compile and install git
> - on Linux: there are packages somewhere
> - on Mac OS X: use the [DarwinPorts|http://www.darwinports.org/]
--
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: (MINVOKER-43) Sync repository identifier of custom IT repo with identifier of real local repository
[
http://jira.codehaus.org/browse/MINVOKER-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143353#action_143353
]
Benjamin Bentmann commented on MINVOKER-43:
---
Possible workaround (at least for single module builds): Instead of
{{invoker:install}}, use the {{install:install-file}} goal and be sure to set
its
[localRepositoryId|http://maven.apache.org/plugins/maven-install-plugin/install-file-mojo.html#localRepositoryId]
parameter to "local".
> Sync repository identifier of custom IT repo with identifier of real local
> repository
> -
>
> Key: MINVOKER-43
> URL: http://jira.codehaus.org/browse/MINVOKER-43
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.2
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
> Fix For: 1.3
>
>
> If the user specifies a custom location for the IT repo, the plugin is
> currently using the identifier "it-repo" for this repository. However, the
> real local repo has the identifier "local". As a result, the metadata files
> created for the staged artifacts have a wrong file name, i.e.
> {{maven-metadata-it-repo.xml}} instead of {{maven-metadata-local.xml}} as
> expected by Maven for a local repository.
> This gives rise to odd test failures: When the IT builds run, Maven will
> (expectedly) ignore the badly named metadata files. Since the local repo
> metadata can't be found, Maven will then query the remote repos for updates
> of the artifacts under test. This in turn can make Maven use out-dated
> snapshots and *not* the artifact versions that have just been built locally.
--
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: (MINVOKER-43) Sync repository identifier of custom IT repo with identifier of real local repository
[
http://jira.codehaus.org/browse/MINVOKER-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MINVOKER-43:
--
Priority: Major (was: Minor)
Description:
If the user specifies a custom location for the IT repo, the plugin is
currently using the identifier "it-repo" for this repository. However, the real
local repo has the identifier "local". As a result, the metadata files created
for the staged artifacts have a wrong file name, i.e.
{{maven-metadata-it-repo.xml}} instead of {{maven-metadata-local.xml}} as
expected by Maven for a local repository.
This gives rise to odd test failures: When the IT builds run, Maven will
(expectedly) ignore the badly named metadata files. Since the local repo
metadata can't be found, Maven will then query the remote repos for updates of
the artifacts under test. This in turn can make Maven use out-dated snapshots
and *not* the artifact versions that have just been built locally.
was:If the user specified a custom location for the IT repo, the plugin is
currently using the identifier "it-repo" for this repository. However, the real
local repo has the identifier "local". This makes it in principal possible for
a component under test to tell these repositories apart, potentially causing
different behavior during integration testing than in real world. For example,
the repository identifier is used in construction of the repository metadata
files, e.g. {{maven-metadata-local.xml}}.
Issue Type: Bug (was: Improvement)
> Sync repository identifier of custom IT repo with identifier of real local
> repository
> -
>
> Key: MINVOKER-43
> URL: http://jira.codehaus.org/browse/MINVOKER-43
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.2
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
> Fix For: 1.3
>
>
> If the user specifies a custom location for the IT repo, the plugin is
> currently using the identifier "it-repo" for this repository. However, the
> real local repo has the identifier "local". As a result, the metadata files
> created for the staged artifacts have a wrong file name, i.e.
> {{maven-metadata-it-repo.xml}} instead of {{maven-metadata-local.xml}} as
> expected by Maven for a local repository.
> This gives rise to odd test failures: When the IT builds run, Maven will
> (expectedly) ignore the badly named metadata files. Since the local repo
> metadata can't be found, Maven will then query the remote repos for updates
> of the artifacts under test. This in turn can make Maven use out-dated
> snapshots and *not* the artifact versions that have just been built locally.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-182) git provider
[
http://jira.codehaus.org/browse/SCM-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143352#action_143352
]
Don Brown commented on SCM-182:
---
How, in any way, is this screwing with the community? First of all, having a
separate version of the scm 1.1 provider prevents you from having to modify the
release plugin in order to pull in the scm plugin, and second, the code works
so why not have a tagged release today for those of us that don't want to wait
for Maven 1.1?
Open Source is about the freedom to be able to scratch your itch and share the
solution with others; not about some ivory tower club dictating what the masses
use. My branch is freely available in the Maven sandbox, so if you see
something you'd like to merge back or even contribute, please feel free.
> git provider
>
>
> Key: SCM-182
> URL: http://jira.codehaus.org/browse/SCM-182
> Project: Maven SCM
> Issue Type: New Feature
> Components: maven-scm-provider-git
> Environment: Developed on Mac OS X 10.3.9 with git 1.2.4
>Reporter: Dominik Winter
>Assignee: Jason van Zyl
> Fix For: 1.1
>
> Attachments: git.patch, git.tar.bz2, SCM-182.patch, update1.patch.bz2
>
>
> Please find the git provider as attachment.
> Usefulness:
> I used the git provider together with
> [http://maven.apache.org/plugins/maven-release-plugin|maven-release-plugin],
> it works fine for that use case.
> Open issues:
> - the JUnit tests are "proprietary", not yet TCK. I'll fix that.
> If you want to run the tests, you must have git installed and it must be in
> your {{PATH}}.
> To run git:
> - on *Windows*: use [Cygwin|http://www.cygwin.com] and install the binutils,
> openssh, openssl, rsync, curl
> than you are able to compile and install git
> - on Linux: there are packages somewhere
> - on Mac OS X: use the [DarwinPorts|http://www.darwinports.org/]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-182) git provider
[
http://jira.codehaus.org/browse/SCM-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143346#action_143346
]
Eugene Kuleshov commented on SCM-182:
-
Don, you don't really need to branch, fork or release plugin in order to pass
by release plugin restrictions. You just need to lock snapshot version, e.g.
1.1-20080622.233710-32 from Sonatype repository at
http://repository.sonatype.org/content/repositories/maven.snapshots/
Also, I think it would worth to first ask in the Maven developers list about
scm release instead of screwing with the community.
> git provider
>
>
> Key: SCM-182
> URL: http://jira.codehaus.org/browse/SCM-182
> Project: Maven SCM
> Issue Type: New Feature
> Components: maven-scm-provider-git
> Environment: Developed on Mac OS X 10.3.9 with git 1.2.4
>Reporter: Dominik Winter
>Assignee: Jason van Zyl
> Fix For: 1.1
>
> Attachments: git.patch, git.tar.bz2, SCM-182.patch, update1.patch.bz2
>
>
> Please find the git provider as attachment.
> Usefulness:
> I used the git provider together with
> [http://maven.apache.org/plugins/maven-release-plugin|maven-release-plugin],
> it works fine for that use case.
> Open issues:
> - the JUnit tests are "proprietary", not yet TCK. I'll fix that.
> If you want to run the tests, you must have git installed and it must be in
> your {{PATH}}.
> To run git:
> - on *Windows*: use [Cygwin|http://www.cygwin.com] and install the binutils,
> openssh, openssl, rsync, curl
> than you are able to compile and install git
> - on Linux: there are packages somewhere
> - on Mac OS X: use the [DarwinPorts|http://www.darwinports.org/]
--
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: (SUREFIRE-507) Not able to get a surefire report with failed Junit Tests
[ http://jira.codehaus.org/browse/SUREFIRE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Behrend closed SUREFIRE-507. -- Resolution: Not A Bug Ok. org.apache.maven.plugins maven-surefire-plugin 2.4.3 true > Not able to get a surefire report with failed Junit Tests > - > > Key: SUREFIRE-507 > URL: http://jira.codehaus.org/browse/SUREFIRE-507 > Project: Maven Surefire > Issue Type: Bug > Components: JUnit 3.x support >Affects Versions: 2.4.3 > Environment: Ubuntu 8.04, Maven 2.0.9, Surefire Report plugin 2.4.3 >Reporter: Alexander Behrend > > First of all I set up an example Maven Project from quickstart archetype and > wrote some JUnit 3 Testdummy methods. One of these dummy test methods is set > to fail. > After integration of the surefire-report-plugin version 2.4.3 into pom.xml it > produces an Maven Build failure. > The surefire report-site has a table of statistics with failed tests and > successful test. So it makes no sense when Maven (Goal site:site or site:run) > fails and reports are shown only if everything was tested successful. > Is this a bug or how can I configure my pom correctly to resolve this > problem? > Failure output: > [...] > [INFO] [surefire:test] > [INFO] Surefire report directory: > /home/alexanderbehrend/workspaceJava/junitlesson/target/surefire-reports > --- > T E S T S > --- > Running codersdoc.junitlesson.TemperatureCalculatorTest > Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec <<< > FAILURE! > Results : > Failed tests: > testDummyFailure(codersdoc.junitlesson.TemperatureCalculatorTest) > Tests run: 5, Failures: 1, Errors: 0, Skipped: 0 > [ERROR] > Mojo: > org.apache.maven.plugins:maven-surefire-plugin:2.4.2:test > FAILED for project: > codersdoc:junitlesson:jar:0.0.1-SNAPSHOT > Reason: > There are test failures. > Please refer to > /home/alexanderbehrend/workspaceJava/junitlesson/target/surefire-reports for > the individual test results. > [INFO] > > [INFO] For more information, run with the -e flag > [INFO] > > [INFO] BUILD FAILED > [INFO] > > [INFO] Total time: 7 seconds > [INFO] Finished at: Fri Jul 25 11:12:01 CEST 2008 > [INFO] Final Memory: 5M/25M > [INFO] > -- 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: (MNGSITE-60) Invalid links on Maven web site (Continuous Integration)
[ http://jira.codehaus.org/browse/MNGSITE-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNGSITE-60. --- Assignee: Brett Porter Resolution: Fixed > Invalid links on Maven web site (Continuous Integration) > > > Key: MNGSITE-60 > URL: http://jira.codehaus.org/browse/MNGSITE-60 > Project: Maven 2 Project Web Site > Issue Type: Bug >Reporter: Julien HENRY >Assignee: Brett Porter > > On this page: http://maven.apache.org/integration.html > The two links are invalid. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MNGSITE-60) Invalid links on Maven web site (Continuous Integration)
[ http://jira.codehaus.org/browse/MNGSITE-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MNG-3687 to MNGSITE-60: -- Component/s: (was: Documentation: General) Key: MNGSITE-60 (was: MNG-3687) Project: Maven 2 Project Web Site (was: Maven 2) > Invalid links on Maven web site (Continuous Integration) > > > Key: MNGSITE-60 > URL: http://jira.codehaus.org/browse/MNGSITE-60 > Project: Maven 2 Project Web Site > Issue Type: Bug >Reporter: Julien HENRY > > On this page: http://maven.apache.org/integration.html > The two links are invalid. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3687) Invalid links on Maven web site (Continuous Integration)
Invalid links on Maven web site (Continuous Integration) Key: MNG-3687 URL: http://jira.codehaus.org/browse/MNG-3687 Project: Maven 2 Issue Type: Bug Components: Documentation: General Reporter: Julien HENRY On this page: http://maven.apache.org/integration.html The two links are invalid. -- 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-3614) settings.xml active profiles executed AFTER project profiles have been loaded and activated/not activated
[ http://jira.codehaus.org/browse/MNG-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143332#action_143332 ] Aaron Digulla commented on MNG-3614: I have a similar issue: I have defined a property in the settings.xml with the version of the parent POM. Unfortunately, maven tries to validate the POM before loading the settings, so this doesn't work. I would also expect that maven reads the settings file first, activate all profiles in there which should be active and then check again if the POM of the project defines more properties which influence the active profiles. > settings.xml active profiles executed AFTER project profiles have been loaded > and activated/not activated > - > > Key: MNG-3614 > URL: http://jira.codehaus.org/browse/MNG-3614 > Project: Maven 2 > Issue Type: Bug > Components: Inheritance and Interpolation, Profiles, Settings >Affects Versions: 2.0.9 > Environment: Solaris 5.10, ubuntu hardy x64 >Reporter: Donald Abrams >Priority: Minor > Fix For: 2.0.x > > > If you have the following settings.xml in ~/.m2: > > > > > userSettings > > > > > true > > > > > userSettings > > > and another child pom.xml somewhere down the line has a profile with an > activation like this: > http://maven.apache.org/POM/4.0.0";> > 4.0.0 > > > with-something > > false > > someproperty > true > > > > > > During run-time, the profile with-something will load before userSettings. > This causes with-something to be incorrectly not activated (as the property > someproperty does not exist). This can be seen with mvn help:active-profiles. > I know why this is true, but it is non-intuitive and one would expect > settings.xml profiles to be loaded before anything else. -- 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: (MCHANGES-61) Provide DTD/XSD for changes.xml
[
http://jira.codehaus.org/browse/MCHANGES-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MCHANGES-61:
-
Note using the Xpp3Reader has the following side effect.
People must add
{code:xml}
Whereas the following format was supported before :
Add foo in the bean .
{code}
I will see if I can find a solution in modello if not I will add note in the
release note.
> Provide DTD/XSD for changes.xml
> ---
>
> Key: MCHANGES-61
> URL: http://jira.codehaus.org/browse/MCHANGES-61
> Project: Maven 2.x Changes Plugin
> Issue Type: Improvement
> Components: changes-report
>Affects Versions: 2.0-beta-2
>Reporter: Mark Hobson
>Assignee: Olivier Lamy
> Fix For: 2.1
>
>
> A DTD/XSD for changes.xml would be extremely useful for IDE auto-completion.
> It should be hosted on the apache site.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCHANGES-119) Add the changes xsd file http://maven.apache.org/xsd/ after the 2.1 release
[ http://jira.codehaus.org/browse/MCHANGES-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MCHANGES-119: -- Assignee: Olivier Lamy Fix Version/s: 2.1 Summary: Add the changes xsd file http://maven.apache.org/xsd/ after the 2.1 release (was: Add the changes xsd file http://maven.apache.org/xsd/ after the project release) > Add the changes xsd file http://maven.apache.org/xsd/ after the 2.1 release > --- > > Key: MCHANGES-119 > URL: http://jira.codehaus.org/browse/MCHANGES-119 > Project: Maven 2.x Changes Plugin > Issue Type: Task >Affects Versions: 2.1 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 2.1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MCHANGES-119) Add the changes xsd file http://maven.apache.org/xsd/ after the project release
Add the changes xsd file http://maven.apache.org/xsd/ after the project release --- Key: MCHANGES-119 URL: http://jira.codehaus.org/browse/MCHANGES-119 Project: Maven 2.x Changes Plugin Issue Type: Task Affects Versions: 2.1 Reporter: Olivier Lamy -- 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: (MCHANGES-61) Provide DTD/XSD for changes.xml
[ http://jira.codehaus.org/browse/MCHANGES-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143329#action_143329 ] Olivier Lamy commented on MCHANGES-61: -- Yep good idea ! It will included in the site generation too. > Provide DTD/XSD for changes.xml > --- > > Key: MCHANGES-61 > URL: http://jira.codehaus.org/browse/MCHANGES-61 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: changes-report >Affects Versions: 2.0-beta-2 >Reporter: Mark Hobson >Assignee: Olivier Lamy > Fix For: 2.1 > > > A DTD/XSD for changes.xml would be extremely useful for IDE auto-completion. > It should be hosted on the apache site. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-61) Provide DTD/XSD for changes.xml
[ http://jira.codehaus.org/browse/MCHANGES-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143328#action_143328 ] Milos Kleint commented on MCHANGES-61: -- will the xsd be uploaded to http://maven.apache.org/xsd/ or will it be elsewhere? > Provide DTD/XSD for changes.xml > --- > > Key: MCHANGES-61 > URL: http://jira.codehaus.org/browse/MCHANGES-61 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: changes-report >Affects Versions: 2.0-beta-2 >Reporter: Mark Hobson >Assignee: Olivier Lamy > Fix For: 2.1 > > > A DTD/XSD for changes.xml would be extremely useful for IDE auto-completion. > It should be hosted on the apache site. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCHANGES-61) Provide DTD/XSD for changes.xml
[ http://jira.codehaus.org/browse/MCHANGES-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MCHANGES-61. Resolution: Fixed fixed in rev 680301. > Provide DTD/XSD for changes.xml > --- > > Key: MCHANGES-61 > URL: http://jira.codehaus.org/browse/MCHANGES-61 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: changes-report >Affects Versions: 2.0-beta-2 >Reporter: Mark Hobson >Assignee: Olivier Lamy > Fix For: 2.1 > > > A DTD/XSD for changes.xml would be extremely useful for IDE auto-completion. > It should be hosted on the apache site. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-182) git provider
[
http://jira.codehaus.org/browse/SCM-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143322#action_143322
]
Don Brown commented on SCM-182:
---
All I did was branch the git provider in trunk so that I could release it
against scm 1.0. Therefore, whenever scm 1.1 is released and included in a
Maven release, this branch will no longer be necessary.
> git provider
>
>
> Key: SCM-182
> URL: http://jira.codehaus.org/browse/SCM-182
> Project: Maven SCM
> Issue Type: New Feature
> Components: maven-scm-provider-git
> Environment: Developed on Mac OS X 10.3.9 with git 1.2.4
>Reporter: Dominik Winter
>Assignee: Jason van Zyl
> Fix For: 1.1
>
> Attachments: git.patch, git.tar.bz2, SCM-182.patch, update1.patch.bz2
>
>
> Please find the git provider as attachment.
> Usefulness:
> I used the git provider together with
> [http://maven.apache.org/plugins/maven-release-plugin|maven-release-plugin],
> it works fine for that use case.
> Open issues:
> - the JUnit tests are "proprietary", not yet TCK. I'll fix that.
> If you want to run the tests, you must have git installed and it must be in
> your {{PATH}}.
> To run git:
> - on *Windows*: use [Cygwin|http://www.cygwin.com] and install the binutils,
> openssh, openssl, rsync, curl
> than you are able to compile and install git
> - on Linux: there are packages somewhere
> - on Mac OS X: use the [DarwinPorts|http://www.darwinports.org/]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-182) git provider
[
http://jira.codehaus.org/browse/SCM-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143321#action_143321
]
Olivier Lamy commented on SCM-182:
--
Can this branch replace the current git provider in trunk ?
> git provider
>
>
> Key: SCM-182
> URL: http://jira.codehaus.org/browse/SCM-182
> Project: Maven SCM
> Issue Type: New Feature
> Components: maven-scm-provider-git
> Environment: Developed on Mac OS X 10.3.9 with git 1.2.4
>Reporter: Dominik Winter
>Assignee: Jason van Zyl
> Fix For: 1.1
>
> Attachments: git.patch, git.tar.bz2, SCM-182.patch, update1.patch.bz2
>
>
> Please find the git provider as attachment.
> Usefulness:
> I used the git provider together with
> [http://maven.apache.org/plugins/maven-release-plugin|maven-release-plugin],
> it works fine for that use case.
> Open issues:
> - the JUnit tests are "proprietary", not yet TCK. I'll fix that.
> If you want to run the tests, you must have git installed and it must be in
> your {{PATH}}.
> To run git:
> - on *Windows*: use [Cygwin|http://www.cygwin.com] and install the binutils,
> openssh, openssl, rsync, curl
> than you are able to compile and install git
> - on Linux: there are packages somewhere
> - on Mac OS X: use the [DarwinPorts|http://www.darwinports.org/]
--
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: (MDEP-174) mvn dependency:resolve-plugins look for plugins in standard dependency repositories
mvn dependency:resolve-plugins look for plugins in standard dependency repositories --- Key: MDEP-174 URL: http://jira.codehaus.org/browse/MDEP-174 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: resolve-plugins Affects Versions: 2.0 Reporter: Stefano Bagnara Assignee: Brian Fox I have a very strict list containing only my direct dependencies. A standard build correctly download plugins from other repositories and the project dependencies from my repository. If I use dependency:resolve the artifact from my repository is copied to the local repository. If I use dependency:resolve-plugins it looks in my repository instead of the plugin repository <--- WRONG. -- 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-508) cannot run GWTTestCases with surefire
cannot run GWTTestCases with surefire - Key: SUREFIRE-508 URL: http://jira.codehaus.org/browse/SUREFIRE-508 Project: Maven Surefire Issue Type: Bug Components: classloading Affects Versions: 2.4.3 Reporter: nicolas de loof GWTTestCase require some complex setup, as tje GWT compiler requires acces to the java sources, and classpath scanning for available jars at runtime : maven-surefire-plugin src/main/java src/test/java target/generated-sources/gwt false gwt.args -out target/www-test -Xmx256M Even with this configuration, the test fails with a tomcat ClassCastException "GWTShellServlet is not a Servlet" I may be wrong, but it seems the useManifestOnlyJar=false mode still uses the tmp file classpath elements to build it's classpath, and not the system classpath. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-182) git provider
[
http://jira.codehaus.org/browse/SCM-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143318#action_143318
]
Don Brown commented on SCM-182:
---
For those that can't wait, I branched trunk and created a 1.1-db-1 release of
the git provider, which works like a charm. No need to fork any of the maven
plugins. For more information, see
http://www.jroller.com/mrdon/entry/maven_enabled_project_hosting_with
> git provider
>
>
> Key: SCM-182
> URL: http://jira.codehaus.org/browse/SCM-182
> Project: Maven SCM
> Issue Type: New Feature
> Components: maven-scm-provider-git
> Environment: Developed on Mac OS X 10.3.9 with git 1.2.4
>Reporter: Dominik Winter
>Assignee: Jason van Zyl
> Fix For: 1.1
>
> Attachments: git.patch, git.tar.bz2, SCM-182.patch, update1.patch.bz2
>
>
> Please find the git provider as attachment.
> Usefulness:
> I used the git provider together with
> [http://maven.apache.org/plugins/maven-release-plugin|maven-release-plugin],
> it works fine for that use case.
> Open issues:
> - the JUnit tests are "proprietary", not yet TCK. I'll fix that.
> If you want to run the tests, you must have git installed and it must be in
> your {{PATH}}.
> To run git:
> - on *Windows*: use [Cygwin|http://www.cygwin.com] and install the binutils,
> openssh, openssl, rsync, curl
> than you are able to compile and install git
> - on Linux: there are packages somewhere
> - on Mac OS X: use the [DarwinPorts|http://www.darwinports.org/]
--
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
