[jira] Commented: (MAVENUPLOAD-1107) upload jguard v1.00-beta-1 jars
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1107?page=comments#action_73874 ] charles gay commented on MAVENUPLOAD-1107: -- i've added the required parent pom in the same directory at this url: http://jguard.sourceforge.net/v1.00/1.00-beta-1/pom.xml about creating a repository at sf can raise a space quota issue because our project space is limited to 100 mo. it will be full in 2 or 3 releases cheers, Charles GAY. > upload jguard v1.00-beta-1 jars > --- > > Key: MAVENUPLOAD-1107 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1107 > Project: maven-upload-requests > Issue Type: Task >Reporter: charles gay > > http://jguard.sourceforge.net/v1.00/1.00-beta-1/jguard-core-1.00-beta-1-bundle.jar > http://jguard.sourceforge.net/v1.00/1.00-beta-1/jguard-ext-1.00-beta-1-bundle.jar > http://jguard.sourceforge.net/v1.00/1.00-beta-1/jguard-jee-1.00-beta-1-bundle.jar > http://jguard.sourceforge.net/v1.00/1.00-beta-1/jguard-struts-example-1.00-beta-1-bundle.jar > http://jguard.sourceforge.net/v1.00/1.00-beta-1/jguard-swing-example-1.00-beta-1-bundle.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-34) Goals to build eclipse plugin/feature and site
[ http://jira.codehaus.org/browse/MECLIPSE-34?page=comments#action_73875 ] Sharma, Jaikumar commented on MECLIPSE-34: -- It would be very helpful for eclipse plugin developers to build eclipse plugins using Maven, if this improvement / issue is resolve as soon as possible, becuase, I do not find any other way to build plugins using Maven 2, except after this improvement is implemented. Thanks. > Goals to build eclipse plugin/feature and site > -- > > Key: MECLIPSE-34 > URL: http://jira.codehaus.org/browse/MECLIPSE-34 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: PDE support >Affects Versions: 2.0 >Reporter: Eugene Kuleshov > > Please provide new goals to build eclipse plugin/feature and site using > Eclipse's builder. > See following articles on the topic: > Build and Test Automation for plug-ins and features > http://eclipse.org/articles/Article-PDE-Automation/automation.html > Followup article - Building features and plugins with Ant > http://eclipse.techforge.com/index.php/articles/188 > So, plugin can issue command like this: > set ECLIPSE_HOME=D:\eclipse\eclipse-3.0.2 > java -cp %ECLIPSE_HOME%\startup.jar org.eclipse.core.launcher.Main > -application org.eclipse.ant.core.antRunner -buildfile build.xml > -Dcomponent=sdk.examples -Dconfigs="*,*,*" -Dbaseos=win32 -Dbasews=win32 > -Dbasearch=x86 -Djavacfailonerror=true > -Dpde.build.scripts=%ECLIPSE_HOME%/plugins/org.eclipse.pde.build_3.0.1/scripts > -DbaseLocation=%ECLIPSE_HOME% > It will sort of run ant under the hood, but nobody will see 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] Closed: (MAVEN-1786) Performance Optimization of the Reactor
[ http://jira.codehaus.org/browse/MAVEN-1786?page=all ] Arnaud Heritier closed MAVEN-1786. -- Resolution: Fixed Fix Version/s: 1.1-rc1 It's working fine. Your algorithm is better and allow us to not create a new instance each time in the loop. > Performance Optimization of the Reactor > --- > > Key: MAVEN-1786 > URL: http://jira.codehaus.org/browse/MAVEN-1786 > Project: Maven > Issue Type: Improvement >Affects Versions: 1.1-beta-2 > Environment: OS windows xp, JVM sun 1.4.2 >Reporter: Emmanuel Renaud > Assigned To: Arnaud Heritier > Fix For: 1.1-rc1 > > Attachments: Goal.java, reactor-jprofiler.GIF > > > The Goal.checkForCycle method is a hotspot as the reactor starts. > Most of the time is spent in creating HashSets and filling them (see attached > screen shot). > Instead of creating a new HasSet each time, reusing the same improves the > performance of dependency analysis (see attached file Goal.java). > Due to security policy in my company I can't checkout the sources and run > non-regression tests, at least it works fine on our project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MJAVADOC-88) Copyright null if no organization name was specified
Copyright null if no organization name was specified
Key: MJAVADOC-88
URL: http://jira.codehaus.org/browse/MJAVADOC-88
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.1
Reporter: Vincent Siveton
For instance, the output is
{noformat}
Copyright © 2006 null. All Rights Reserved.
{noformat}
should be
{noformat}
Copyright © 2006. All Rights Reserved.
{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MJAVADOC-88) Copyright null if no organization name was specified
[ http://jira.codehaus.org/browse/MJAVADOC-88?page=all ]
Vincent Siveton closed MJAVADOC-88.
---
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 2.1
fixed
> Copyright null if no organization name was specified
>
>
> Key: MJAVADOC-88
> URL: http://jira.codehaus.org/browse/MJAVADOC-88
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Vincent Siveton
> Assigned To: Vincent Siveton
> Fix For: 2.1
>
>
> For instance, the output is
> {noformat}
> Copyright © 2006 null. All Rights Reserved.
> {noformat}
> should be
> {noformat}
> Copyright © 2006. All Rights Reserved.
> {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: (MCHECKSTYLE-54) checkstyle:check does not see provided scope dependencies
checkstyle:check does not see provided scope dependencies - Key: MCHECKSTYLE-54 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-54 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.1 Reporter: Stephen Duncan Jr Priority: Critical Running checkstyle:check against a project that uses Exceptions from dependencies that are provided scope causes checktyle errors such as the following: These errors go away when the scope is changed to compile. This does not happen for checkstyle:checkstyle; the report correct indicates no checkstyle errors. This is preventing us from using the checkstyle plugin to enforce checkstyle rules. -- 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: (MJAVADOC-86) Coma in are replaced by -group
[ http://jira.codehaus.org/browse/MJAVADOC-86?page=all ]
Vincent Siveton closed MJAVADOC-86.
---
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 2.1
Replaced comma with HTML entity
> Coma in are replaced by -group
> -
>
> Key: MJAVADOC-86
> URL: http://jira.codehaus.org/browse/MJAVADOC-86
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Martin Desruisseaux
> Assigned To: Vincent Siveton
> Fix For: 2.1
>
>
> Configuration similar to the one below:
> {code}
>
>
> XML and derivatives (GML, SVG)
> org.geotools.xml*:org.geotools.gml*:org.geotools.svg*
>
>
> {code}
> result in the following group title in the HTML generated pages:
> {quote}
> XML and derivatives (GML -group SVG)
> {quote}
> Same seems to apply to every title containing a coma: the coma is replaced by
> {{-group}}. Its look like a remascence of the way {{}} was implemented
> in some previous {{maven-javadoc-plugin}} version (it was a coma-separated
> list a while ago).
--
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: (MAVEN-1787) Maven is not working properly
Maven is not working properly - Key: MAVEN-1787 URL: http://jira.codehaus.org/browse/MAVEN-1787 Project: Maven Issue Type: Task Components: installer Affects Versions: 1.0.2 Environment: Windows XP Prof, Java1.5 Reporter: Niamul Sanjavi I have installed Maven 1.0.2 in the following directory : C:\Maven\Maven1.0.2 and set the MAVEN_HOME acordingly. My Java version is 1.5 and it is installed in the directory C:\Program Files\Java\jdk1.5.0_07 and the JAVA_HOME is set accordingly. But when I run the maven.bat the following error occcurs : --- Plugin cache will be regenerated Fatal Error [line 23, row 23]: XML document structures must start and end within the same entity. org.apache.maven.MavenException: Error parsing plugin script at org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.j ava:165) at org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.j ava:177) at org.apache.maven.plugin.PluginManager.loadUncachedPlugins(PluginManag er.java:239) at org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:3 04) at org.apache.maven.MavenSession.initializePluginManager(MavenSession.ja va:204) at org.apache.maven.MavenSession.initialize(MavenSession.java:171) at org.apache.maven.cli.App.doMain(App.java:475) at org.apache.maven.cli.App.main(App.java:1239) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) --- Nested Exception --- org.xml.sax.SAXParseException: XML document structures must start and end within the same entity. at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(Unknown Source) at org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.j ava:157) at org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.j ava:177) at org.apache.maven.plugin.PluginManager.loadUncachedPlugins(PluginManag er.java:239) at org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:3 04) at org.apache.maven.MavenSession.initializePluginManager(MavenSession.ja va:204) at org.apache.maven.MavenSession.initialize(MavenSession.java:171) at org.apache.maven.cli.App.doMain(App.java:475) at org.apache.maven.cli.App.main(App.java:1239) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) You have encountered an unknown error running Maven. Please help us to correct this problem by following these simple steps: - read the Maven FAQ at http://maven.apache.org/faq.html - run the same command again with the '-e' parameter, eg maven -e jar - search the maven-user archives for the error at http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED] - post the output of maven -e to JIRA at http://jira.codehaus.org/BrowseProject.jspa?id=10030 (you must sign up first) - run 'maven --info' and post the output as the environment to the bug above - I can't find the reason for this type of error. Could you please suggest me the solution for this error? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MCHECKSTYLE-55) Wrong rules summary for GenericIllegalRegexp when message contains a quote
Wrong rules summary for GenericIllegalRegexp when message contains a quote -- Key: MCHECKSTYLE-55 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-55 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.1 Environment: Windows XP - Maven 2.0.4 Reporter: Olivier Vierlinck Priority: Minor Attachments: MavenCheckstyleReportBug.zip if a GenericIllegalRegexp check is defined and its 'message' property contains a quote, the check is executed ok and failures are listed in the Details part of the HTML report. But the Rules summary part is wrong: it show the rules with 0 violations. For example, this check will no be reported as violated in the rules summary (but the message text is show correctly) But will be listed in the errors on the file (but with the quote removed from the message ;-) ) See checkstyle.xml and target/site/checkstyle.html in attachment (and sample code in src\main\java\MCTest\App.java) -- 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: (MPTEST-39) MPTEST-25 fix side effect: test failure doesn't halt execution
[ http://jira.codehaus.org/browse/MPTEST-39?page=comments#action_73896 ] Pascal Grange commented on MPTEST-39: - It seems that the maven.test.failure.ignore property has been used to specify junit to stop test execution at the first encountered failure. This means that it is no more possible to fail maven build when test fails but still executing *ALL* the tests. This is a bug. > MPTEST-25 fix side effect: test failure doesn't halt execution > -- > > Key: MPTEST-39 > URL: http://jira.codehaus.org/browse/MPTEST-39 > Project: maven-test-plugin > Issue Type: Bug >Reporter: Sebastien Sahuc > Assigned To: Lukas Theussl > Fix For: 1.8 > > > The fix for MPTEST-25 has a behavioral side effect that I consider as a bug. > Before the fix, any test failure would halt the whole testing process, unless > the failure.ignore was specified. Now, no matter what you do, the complete > test suite will run eventhough you want it to stop at the first error it > encounters. > http://jira.codehaus.org/browse/MPTEST-25 > Thanks, > Seb -- 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: (MPTEST-71) maven test stops the build at the first test failure
maven test stops the build at the first test failure Key: MPTEST-71 URL: http://jira.codehaus.org/browse/MPTEST-71 Project: maven-test-plugin Issue Type: Bug Reporter: Pascal Grange Assigned To: Lukas Theussl Fix For: 1.8 The fix for MPTEST-25 has a behavioral side effect that I consider as a bug. Before the fix, any test failure would halt the whole testing process, unless the failure.ignore was specified. Now, no matter what you do, the complete test suite will run eventhough you want it to stop at the first error it encounters. http://jira.codehaus.org/browse/MPTEST-25 Thanks, Seb -- 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: (MAVEN-1787) Maven is not working properly
[ http://jira.codehaus.org/browse/MAVEN-1787?page=comments#action_73898 ] Arnaud Heritier commented on MAVEN-1787: Do you have a POM in the directory where you launch maven ? This POM is valid in XML ? > Maven is not working properly > - > > Key: MAVEN-1787 > URL: http://jira.codehaus.org/browse/MAVEN-1787 > Project: Maven > Issue Type: Task > Components: installer >Affects Versions: 1.0.2 > Environment: Windows XP Prof, Java1.5 >Reporter: Niamul Sanjavi > > I have installed Maven 1.0.2 in the following directory : C:\Maven\Maven1.0.2 > and set the MAVEN_HOME acordingly. > My Java version is 1.5 and it is installed in the directory C:\Program > Files\Java\jdk1.5.0_07 and the JAVA_HOME is set accordingly. > But when I run the maven.bat the following error occcurs : > --- > Plugin cache will be regenerated > Fatal Error [line 23, row 23]: XML document structures must start and end > within > the same entity. > org.apache.maven.MavenException: Error parsing plugin script > at > org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.j > ava:165) > at > org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.j > ava:177) > at > org.apache.maven.plugin.PluginManager.loadUncachedPlugins(PluginManag > er.java:239) > at > org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:3 > 04) > at > org.apache.maven.MavenSession.initializePluginManager(MavenSession.ja > va:204) > at org.apache.maven.MavenSession.initialize(MavenSession.java:171) > at org.apache.maven.cli.App.doMain(App.java:475) > at org.apache.maven.cli.App.main(App.java:1239) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at com.werken.forehead.Forehead.run(Forehead.java:551) > at com.werken.forehead.Forehead.main(Forehead.java:581) > --- Nested Exception --- > org.xml.sax.SAXParseException: XML document structures must start and end > within > the same entity. > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) > at javax.xml.parsers.SAXParser.parse(Unknown Source) > at > org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.j > ava:157) > at > org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.j > ava:177) > at > org.apache.maven.plugin.PluginManager.loadUncachedPlugins(PluginManag > er.java:239) > at > org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:3 > 04) > at > org.apache.maven.MavenSession.initializePluginManager(MavenSession.ja > va:204) > at org.apache.maven.MavenSession.initialize(MavenSession.java:171) > at org.apache.maven.cli.App.doMain(App.java:475) > at org.apache.maven.cli.App.main(App.java:1239) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at com.werken.forehead.Forehead.run(Forehead.java:551) > at com.werken.forehead.Forehead.main(Forehead.java:581) > You have encountered an unknown error running Maven. Please help us to correct > this problem by following these simple steps: > - read the Maven FAQ at http://maven.apache.org/faq.html > - run the same command again with the '-e' parameter, eg maven -e jar > - search the maven-user archives for the error at > http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED] > - post the output of maven -e to JIRA at > http://jira.codehaus.org/BrowseProject.jspa?id=10030 (you must sign up first) > - run 'maven --info' and post the output as the environment to the bug above > - > I can't find the reason for this type of error. > Could you please suggest me the solution for this error? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPTEST-71) maven test stops the build at the first test failure
[ http://jira.codehaus.org/browse/MPTEST-71?page=comments#action_73899 ] Pascal Grange commented on MPTEST-71: - It seems that the maven.test.failure.ignore property has been used to specify junit to stop test execution at the first encountered failure. This means that it is no more possible to fail maven build when test fails but still execute *ALL* the tests. This is a bug. This is essential to be able to run all the tests unconditionally when you build test reports, for instance. And we still need the build to fail after *ALL* the tests have been run if one of them ended on failure. It would be a good idea to propose a separate property such as maven.test.haltonfailure or maven.test.haltonerror to specify junit to stop at the first failure or error. This property must be set to false by default to comply with maven-test-plugin behaviour before version 1.8. See http://jira.codehaus.org/browse/MPTEST-39 > maven test stops the build at the first test failure > > > Key: MPTEST-71 > URL: http://jira.codehaus.org/browse/MPTEST-71 > Project: maven-test-plugin > Issue Type: Bug >Reporter: Pascal Grange > Assigned To: Lukas Theussl > Fix For: 1.8 > > > The fix for MPTEST-25 has a behavioral side effect that I consider as a bug. > Before the fix, any test failure would halt the whole testing process, unless > the failure.ignore was specified. Now, no matter what you do, the complete > test suite will run eventhough you want it to stop at the first error it > encounters. > http://jira.codehaus.org/browse/MPTEST-25 > Thanks, > Seb -- 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-2408) Improve handling of "no plugin version found" error after intermittent errors
[ http://jira.codehaus.org/browse/MNG-2408?page=all ] John Casey closed MNG-2408. --- Assignee: John Casey Resolution: Fixed Resolved in trunk (2.1-snapshot), and 2.0.5-snapshot merge should be complete shortly. I added code to the update method in AbstractRepositoryMetadata to avoid writing the metadata to the local repo if the main version was either RELEASE or LATEST, since these are only meta-versions, and should never exist in the repo as main versions. Also added a unit test to maven-artifact-manager to check for this. > Improve handling of "no plugin version found" error after intermittent errors > - > > Key: MNG-2408 > URL: http://jira.codehaus.org/browse/MNG-2408 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, Documentation: Guides, > Artifacts >Affects Versions: 2.0.4 >Reporter: Graham Leggett > Assigned To: John Casey >Priority: Blocker > Fix For: 2.0.5 > > > If you follow the instructions at > http://maven.apache.org/guides/getting-started/index.html#How%20do%20I%20make%20my%20first%20Maven%20project? > to use the archetype plugin to create a new project skeleton, the suggested > command line fails as below. > It seems there is a typo of some kind in the suggested command line, I am not > familiar enough with maven 2 to know for sure. > Graham-Leggetts-Computer:~/src/standard/alchemy/maven minfrin$ mvn > archetype:create -DgroupId=za.co.standardbank.alchemy > -DartifactId=alchemy-trader > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'archetype'. > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not > exist or no valid version could be found > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 1 second > [INFO] Finished at: Tue Jun 27 09:43:14 SAST 2006 > [INFO] Final Memory: 1M/2M > [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] Updated: (MEAR-36) Add classifier fonctionnality to Maven EAR Plugin
[ http://jira.codehaus.org/browse/MEAR-36?page=all ]
Eric Bernstein updated MEAR-36:
---
Attachment: MEAR-36-maven-ear-plugin.patch
Attaching a patch that fixes this issue.
I know the issue says in progress but I needed the fix today and wrote it out.
The fix was taken from the maven-jar-plugin implementation and should function
identically.
> Add classifier fonctionnality to Maven EAR Plugin
> -
>
> Key: MEAR-36
> URL: http://jira.codehaus.org/browse/MEAR-36
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.2
> Environment: Any
>Reporter: Mathieu Rozieres
> Assigned To: Stephane Nicoll
> Fix For: 2.3
>
> Attachments: MEAR-36-maven-ear-plugin.patch
>
>
> The tag is not implemented into Maven EAR Plugin.
> For example, while using this configuration :
>
>org.apache.maven.plugins
>maven-ear-plugin
>
> dev
>
>
> The artefact produced is still named ${pom.artifactId}-${pom.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: (MEV-20) clean up bad IDs in the repository
[ http://jira.codehaus.org/browse/MEV-20?page=comments#action_73904 ] Tomasz Pik commented on MEV-20: --- What about rhino : js, shouldn't it be org.mozilla.javascript : js ? > clean up bad IDs in the repository > -- > > Key: MEV-20 > URL: http://jira.codehaus.org/browse/MEV-20 > Project: Maven Evangelism > Issue Type: Task >Reporter: Brett Porter > > some projects seem to have been filed with the wrong/multiple artifact and > group IDs. > This is to track what they are and get them in order. Document correct IDs, > but leave the old ones alone so as not to break builds. A richer repository > may later be able to give deprecation warnings on requesting the old JARs. > This will also assist in making a future transition to a new layout easier. -- 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: (MAVEN-1787) Maven is not working properly
[ http://jira.codehaus.org/browse/MAVEN-1787?page=all ] Niamul Sanjavi closed MAVEN-1787. - Resolution: Fixed Fix Version/s: 1.0.2 Thanks for your concern. The problem is solved. The problem was that maven was taking value of some plug-ins from cache. > Maven is not working properly > - > > Key: MAVEN-1787 > URL: http://jira.codehaus.org/browse/MAVEN-1787 > Project: Maven > Issue Type: Task > Components: installer >Affects Versions: 1.0.2 > Environment: Windows XP Prof, Java1.5 >Reporter: Niamul Sanjavi > Fix For: 1.0.2 > > > I have installed Maven 1.0.2 in the following directory : C:\Maven\Maven1.0.2 > and set the MAVEN_HOME acordingly. > My Java version is 1.5 and it is installed in the directory C:\Program > Files\Java\jdk1.5.0_07 and the JAVA_HOME is set accordingly. > But when I run the maven.bat the following error occcurs : > --- > Plugin cache will be regenerated > Fatal Error [line 23, row 23]: XML document structures must start and end > within > the same entity. > org.apache.maven.MavenException: Error parsing plugin script > at > org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.j > ava:165) > at > org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.j > ava:177) > at > org.apache.maven.plugin.PluginManager.loadUncachedPlugins(PluginManag > er.java:239) > at > org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:3 > 04) > at > org.apache.maven.MavenSession.initializePluginManager(MavenSession.ja > va:204) > at org.apache.maven.MavenSession.initialize(MavenSession.java:171) > at org.apache.maven.cli.App.doMain(App.java:475) > at org.apache.maven.cli.App.main(App.java:1239) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at com.werken.forehead.Forehead.run(Forehead.java:551) > at com.werken.forehead.Forehead.main(Forehead.java:581) > --- Nested Exception --- > org.xml.sax.SAXParseException: XML document structures must start and end > within > the same entity. > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) > at javax.xml.parsers.SAXParser.parse(Unknown Source) > at > org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.j > ava:157) > at > org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.j > ava:177) > at > org.apache.maven.plugin.PluginManager.loadUncachedPlugins(PluginManag > er.java:239) > at > org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:3 > 04) > at > org.apache.maven.MavenSession.initializePluginManager(MavenSession.ja > va:204) > at org.apache.maven.MavenSession.initialize(MavenSession.java:171) > at org.apache.maven.cli.App.doMain(App.java:475) > at org.apache.maven.cli.App.main(App.java:1239) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at com.werken.forehead.Forehead.run(Forehead.java:551) > at com.werken.forehead.Forehead.main(Forehead.java:581) > You have encountered an unknown error running Maven. Please help us to correct > this problem by following these simple steps: > - read the Maven FAQ at http://maven.apache.org/faq.html > - run the same command again with the '-e' parameter, eg maven -e jar > - search the maven-user archives for the error at > http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED] > - post the output of maven -e to JIRA at > http://jira.codehaus.org/BrowseProject.jspa?id=10030 (you must sign up first) > - run 'maven --info' and post the output as the environment to the bug above > - > I can't find the reason for this type of error. > Could you please suggest me the solution for this error? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1108) Upload Spring 2.0 rc3
Upload Spring 2.0 rc3 - Key: MAVENUPLOAD-1108 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1108 Project: maven-upload-requests Issue Type: Wish Reporter: Matt Raible Can you please upload this bundle? It's spring-2.0-rc3.jar. I know you'd rather have all the child POMs/JARs, but it's s much easier to just do one. ;-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1108) Upload Spring 2.0 rc3
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1108?page=comments#action_73916 ] Matt Raible commented on MAVENUPLOAD-1108: -- Here's another one: http://static.raibledesigns.com/downloads/spring-mock-2.0-rc3-bundle.jar > Upload Spring 2.0 rc3 > - > > Key: MAVENUPLOAD-1108 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1108 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Matt Raible > > Can you please upload this bundle? It's spring-2.0-rc3.jar. I know you'd > rather have all the child POMs/JARs, but it's s much easier to just do > one. ;-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-830) Use redirect after post instead of forward when page refresh is common but could cause re-triggering
[ http://jira.codehaus.org/browse/CONTINUUM-830?page=comments#action_73920 ] Jesse McConnell commented on CONTINUUM-830: --- looks like this ought to be able to be addressed by using ww:token and the TokenInterceptor..just putting that here so we don't forget about it > Use redirect after post instead of forward when page refresh is common but > could cause re-triggering > > > Key: CONTINUUM-830 > URL: http://jira.codehaus.org/browse/CONTINUUM-830 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Affects Versions: 1.0.3 >Reporter: John Casey > Fix For: 1.1 > > > When I force a build, Continuum simply forwards me to the summary page, > instead of redirecting. This means that if I use the browser's refresh > function, I'll force another build, since the URL is the one used to trigger > the build. If you're doing many things at once, it means you have to look at > the URL before you punch reload, or you may wind up rebuilding again. > It'd be nice to simply redirect the user to the summary page, so reloads of > the page wouldn't trigger fresh builds. -- 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: (MEAR-36) Add classifier fonctionnality to Maven EAR Plugin
[ http://jira.codehaus.org/browse/MEAR-36?page=comments#action_73921 ]
Eric Bernstein commented on MEAR-36:
One note on the patch: Like the jar plugin, it expects to build ears with
classifiers as attachments to the ear w/out the classifier. I wasn't sure
that's what was desired, but I figured there was a good reason the jar plugin
did it as such, and it met my reqs, so I did the ear patch the same way.
> Add classifier fonctionnality to Maven EAR Plugin
> -
>
> Key: MEAR-36
> URL: http://jira.codehaus.org/browse/MEAR-36
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.2
> Environment: Any
>Reporter: Mathieu Rozieres
> Assigned To: Stephane Nicoll
> Fix For: 2.3
>
> Attachments: MEAR-36-maven-ear-plugin.patch
>
>
> The tag is not implemented into Maven EAR Plugin.
> For example, while using this configuration :
>
>org.apache.maven.plugins
>maven-ear-plugin
>
> dev
>
>
> The artefact produced is still named ${pom.artifactId}-${pom.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: (MPMD-39) Target JDK should default to configuration of the compiler plugin
Target JDK should default to configuration of the compiler plugin - Key: MPMD-39 URL: http://jira.codehaus.org/browse/MPMD-39 Project: Maven 2.x Pmd Plugin Issue Type: Improvement Reporter: Eric Bernstein It seems unnecessary to configure the target jdk twice; once for the compiler, and once for pmd. -- 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
