[jira] Commented: (MANTTASKS-64) uberjar does not contain the lightweight http wagon
[ http://jira.codehaus.org/browse/MANTTASKS-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93791 ] Herve Boutemy commented on MANTTASKS-64: Subject: Re: [VOTE] Release Maven Ant Tasks 2.0.6 Date: dimanche 22 avril 2007 01:35 From: Jason van Zyl <[EMAIL PROTECTED]> To: "Maven Developers List" <[EMAIL PROTECTED]> [...] It work fine on its own, it's when it's built with the release plugin it doesn't work. I knew this but forgot to check as to why. It run to the integration-test phase but something is causing a problem with the build is done by the release plugin. Probably something simple. I'll track it down in the morning. [...] The build is fine and the jar is produced correctly. It's the release plugin causing the problem. We'll sort it out. Jason. > uberjar does not contain the lightweight http wagon > --- > > Key: MANTTASKS-64 > URL: http://jira.codehaus.org/browse/MANTTASKS-64 > Project: Maven 2.x Ant Tasks > Issue Type: Bug >Affects Versions: 2.0.6 >Reporter: Brett Porter > Attachments: MANTTASKS-64.diff > > > the new uberjar does not contain the lightweight wagon, so any use fails > unles you add a declaration to your script which was not necessary in the > previous release. > In addition, the JAR seems to be larger than before despite the omission - > was something unnecessarily included? -- 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-2715) Maven does not comply to XML rules regarding prefixes.
[
http://jira.codehaus.org/browse/MNG-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Seva Safris reopened MNG-2715:
--
It's one thing to not support namespaces, but it's another to deliberately
prevent compatibility with xml that uses prefixed names.
Maven does not need to support namespaces to be able to read xml that does.
Instead of supporting namespaces, Maven can be made to respect, but ignore
prefixes. This can be done with the existing codebase by applying a simple
modification to how maven reads the name of xml elements. It has to respect the
possible existence of a prefix by looking for the ':' character:
int prefix = nameOfElement.indexOf(':');
if(prefix != -1)
nameOfElement = nameOfElement.substring(prefix);
This bug may get promptly closed again, but I think this point is worth
mentioning nonetheless as there is a clear and simple way to resolve this bug
(and I still think it's a bug despite the fact that maven will "never support
namespaces").
> Maven does not comply to XML rules regarding prefixes.
> --
>
> Key: MNG-2715
> URL: http://jira.codehaus.org/browse/MNG-2715
> Project: Maven 2
> Issue Type: Bug
> Environment: Ubuntu 6.10
> Maven 2.0.4
>Reporter: Seva Safris
>Priority: Critical
>
> I am new to Maven and have been trying to learn how to create a simple
> project.
> Let me walk through my scenario of creating a pom.xml file:
> 1. I bind the {http://maven.apache.org/POM/4.0.0} namespace (defined at
> "http://maven.apache.org/maven-v4_0_0.xsd";) to Java classes using an XML
> Binding solution.
> 2. I use the bound classes to create a simple as one would expect
> to see in a pom.xml file.
> 3. I marshal the bound Java objects into xml and write it into pom.xml. Here
> is the xml I use:
>xmlns:ns1="http://maven.apache.org/POM/4.0.0";>
> 4.0.0
> com.myapp
> sample-project
> Sample Maven Project
> 1.0
>
>
> ssafris
> Seva Safris
>
>
>
> ${basedir}/src/java
>
>
> 4. I run mvn, and am promptly given a "Not a v4.0.0 POM." exception.
> Tracing through Maven's source, I went to the exact location of the exception
> in DefaultMavenProjectBuilder.java. On line 1297 it has:
> if ( modelSource.indexOf( "4.0.0" ) < 0 )
> {
> throw new InvalidProjectModelException( projectId, pomLocation, "Not a
> v4.0.0 POM." );
> }
> Since modelSource is checked explicitly for
> xml as shown above will fail this test because it has: This is most definitely a bug in Maven and should be fixed as soon as
> possible. The workaround is to use a
> xmlns="http://maven.apache.org/POM/4.0.0"; and define all elements without a
> prefix. However, my use of xmlns:ns1="http://maven.apache.org/POM/4.0.0";
> should not break Maven as it is not merely legal by xml conventions, but is
> also a better practice for xml documents.
> I hope you see the importance of getting this bug fixed: My use of a XML
> Binding solution to bind Maven's xml to Java allows me a strongly-typed level
> of indirection that will deterministically create proper xml that will
> validate successfully. If this bug is not fixed, then this level of
> indirection is not possible (or very very very difficult because the XML
> Binding solution would have to be hacked to use the xmlns="[...]"
> convention). I have only found this one instance of where the bug is obvious,
> but perhaps there are more locations in Maven where the same kind of error
> can occur.
> Thank you for your time, and I hope you consider this issue as seriously as I
> do.
> Sincerely,
> Seva Safris
--
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: (MAVEN-1775) Upgrade maven-eclipse-plugin to v. 1.12
[ http://jira.codehaus.org/browse/MAVEN-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MAVEN-1775: --- Summary: Upgrade maven-eclipse-plugin to v. 1.12 (was: Upgrade maven-eclipse-plugin to v. 1.11.1) > Upgrade maven-eclipse-plugin to v. 1.12 > --- > > Key: MAVEN-1775 > URL: http://jira.codehaus.org/browse/MAVEN-1775 > Project: Maven 1 > Issue Type: Sub-task > Components: planning >Affects Versions: 1.1-beta-3 >Reporter: Stephane Nicoll >Assignee: Stephane Nicoll > Fix For: 1.1-rc1 > > > http://jira.codehaus.org/browse/MPECLIPSE?report=com.atlassian.jira.plugin.system.project:roadmap-panel -- 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: (MPECLIPSE-129) Provide update-url
[ http://jira.codehaus.org/browse/MPECLIPSE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MPECLIPSE-129. - Assignee: Arnaud Heritier Resolution: Won't Fix It's not a plugin for eclipse but a plugin for maven. We don't need an update site. If you are looking for a plugin to use maven inside eclipse : Maven 1 : http://mevenide.codehaus.org/ Maven 2 : http://m2eclipse.codehaus.org/ > Provide update-url > -- > > Key: MPECLIPSE-129 > URL: http://jira.codehaus.org/browse/MPECLIPSE-129 > Project: maven-eclipse-plugin > Issue Type: Improvement >Reporter: Edwin Martin >Assignee: Arnaud Heritier >Priority: Minor > > I couldn't find any update-url for the Maven-Eclipse plugin. > The project should provide an update-url for Eclipse. > 1) It's much more user-friendly to install a pluging via an update-url. > 2) It's easier to update a plugin to a newer version. > 3) I think it's quite easy to provide an update-url. > 4) It's the current way of providing plugins. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPECLIPSE-127) Add support for wtp 1.5
[ http://jira.codehaus.org/browse/MPECLIPSE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MPECLIPSE-127. - Resolution: Fixed Fixed. Snapshot deployed > Add support for wtp 1.5 > --- > > Key: MPECLIPSE-127 > URL: http://jira.codehaus.org/browse/MPECLIPSE-127 > Project: maven-eclipse-plugin > Issue Type: Improvement >Affects Versions: 1.11 >Reporter: Arnaud Heritier >Assignee: Arnaud Heritier > Fix For: 1.12 > > > Can't we reuse some code from the m2 plugin ?? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MIDEA-88) version control setting lost on update
version control setting lost on update -- Key: MIDEA-88 URL: http://jira.codehaus.org/browse/MIDEA-88 Project: Maven 2.x Idea Plugin Issue Type: Bug Affects Versions: 2.0 Environment: idea 6.0.5 windows xp Reporter: Larry Hamel have project with version control set to cvs. change pom for a new dependency. close project. in idea mvn idea:idea open project in idea see that version control setting is lost -- 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-1484) Please upload EZMorph-1.0.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93783 ] Andres Almiray commented on MAVENUPLOAD-1484: - I've uploaded a new bundle at the same URL. Please let me know if everything is ok. > Please upload EZMorph-1.0.2 > --- > > Key: MAVENUPLOAD-1484 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1484 > Project: maven-upload-requests > Issue Type: Task >Reporter: Andres Almiray > > EZMorph is simple java library for transforming an Object to another Object. > This release covers minor bugfixes. -- 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: (MPECLIPSE-102) Running 'maven:eclipse' turns CheckStyle off for the project.
[ http://jira.codehaus.org/browse/MPECLIPSE-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MPECLIPSE-102: -- Fix Version/s: (was: 1.11.1) There's a workaround and it's not easy to fix in maven 1 because we don't read the original file. > Running 'maven:eclipse' turns CheckStyle off for the project. > - > > Key: MPECLIPSE-102 > URL: http://jira.codehaus.org/browse/MPECLIPSE-102 > Project: maven-eclipse-plugin > Issue Type: Bug >Affects Versions: 1.9 >Reporter: Jamie Bisotti >Assignee: Stephane Nicoll > > Assuming project is already setup in Eclipse 3.1 (either manually or via the > eclipse plugin) > 1. Install CheckStyle Eclispe plugin > 2. Turn it on for the project. > 3. Shutdown Eclipse > 4. Run maven eclipse on the project > 5. Restart Eclipse > 6. Notice CheckStyle is now turned off. -- 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: (MAVEN-126) Add a -logfile option
[ http://jira.codehaus.org/browse/MAVEN-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MAVEN-126: -- Assignee: (was: Arnaud Heritier) > Add a -logfile option > - > > Key: MAVEN-126 > URL: http://jira.codehaus.org/browse/MAVEN-126 > Project: Maven 1 > Issue Type: New Feature > Components: cli > Environment: Windows 98 >Reporter: Andrew Stevens >Priority: Minor > Attachments: AntProjectBuilder.java.patch, > JellyBuildListener.java.patch, MAVEN126.patch, MavenConstants.java.patch > > > One of the options I find useful in Ant is '-logfile ', which > redirects the build's output to a given file. It would be nice if I could do > the same with Maven; I've not had much success trying to use Win98's command > line redirection or paging on Maven's output. -- 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: (MAVEN-1733) Bootstrap failure: Unable to delete directory ...
[ http://jira.codehaus.org/browse/MAVEN-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MAVEN-1733: --- Assignee: (was: Arnaud Heritier) > Bootstrap failure: Unable to delete directory ... > - > > Key: MAVEN-1733 > URL: http://jira.codehaus.org/browse/MAVEN-1733 > Project: Maven 1 > Issue Type: Bug >Affects Versions: 1.1-beta-3 > Environment: Win XP, svn Checked out revision 355781. >Reporter: Jeff Jensen > Attachments: buildit.log > > > bootstrap consistently fails. Attached is log for my last run. > This is an interesting line from it: > [exec] Caused by: Unable to delete directory > C:\devroot\reference\maven\maven-1\plugins\trunk\genapp\src\plugin-test\nonStandardDirsTest\target > I completely deleted the svn dirs and got latest. The error above prior was > this: > [exec] Root cause > [exec] Unable to delete directory > C:\devroot\reference\maven\maven-1\plugins\trunk\genapp\src\plugin-test\mavenHomeLocalTemplateTest\target > And the run that failed before that one did not have an "unable to delete > dir". (I did about 6 or so bootstraps today, trying to get it to work) > They are on different plugins, such as Javadoc, Test Genapp. I have 3 of my > last logs, and a couple of them are the test genapp (not the middle run of > the 3). > I hope something helps here, and this isn't some silly chase. Thanks again > for looking into it. > I tried to determine some environment thing for me. > Oh, typing of environment, I am using JDK 1.5. Is that OK, or perhaps the > prob? -- 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: (MAVEN-1790) Fix headers sent to the repository
[ http://jira.codehaus.org/browse/MAVEN-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MAVEN-1790: --- Assignee: (was: Arnaud Heritier) > Fix headers sent to the repository > -- > > Key: MAVEN-1790 > URL: http://jira.codehaus.org/browse/MAVEN-1790 > Project: Maven 1 > Issue Type: Improvement > Components: core >Affects Versions: 1.0, 1.0.1, 1.0.2, 1.1-beta-1, 1.1-beta-2, 1.1-beta-3 >Reporter: Arnaud Heritier > > Modify the headers in the requests sent to the repositories to know the > version of maven and the OS > Perhaps it's already for the OS but we have to test it. > It will help us to track the calls in the new repo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MANTTASKS-6) ant artifact doesn't read settings.xml
[
http://jira.codehaus.org/browse/MANTTASKS-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MANTTASKS-6:
--
Attachment: MANTTASKS-6.diff
here is a patch to look for settings.xml in ant.home/etc than ${M2_HOME}/conf
> ant artifact doesn't read settings.xml
> --
>
> Key: MANTTASKS-6
> URL: http://jira.codehaus.org/browse/MANTTASKS-6
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Environment: winxp
>Reporter: Brian Fox
> Attachments: MANTTASKS-6.diff
>
>
> We are using an ant script to call maven deploy to auto deploy jar, pom and
> md5's and sh1's for 3rd party libraries to our remote repository. The maven
> deploy ant task isn't using the settings to find our mirrors or repositories
> for download. We have a parent pom that it should find, but it's not. The
> settings.xml is in maven/conf and in HOME/.m2/ and in HOME/.ant/
> The repositories are defined in our pom file, but the login information needs
> to be in the settings.xml. When we run this, it isn't finding the login
> information from settings. We also had an issue where the remote repositories
> where defined in settings and it wasn't working until we moved it to the pom.
> The underlying problem seems to be that settings isn't taken into account in
> either case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (MPJAVADOC-80) Add specifying params with alternate doclets
[ http://jira.codehaus.org/browse/MPJAVADOC-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Jensen resolved MPJAVADOC-80. -- Resolution: Fixed Fix Version/s: 1.9 Committed code and docs; staged for 1.9 release. > Add specifying params with alternate doclets > > > Key: MPJAVADOC-80 > URL: http://jira.codehaus.org/browse/MPJAVADOC-80 > Project: maven-javadoc-plugin > Issue Type: New Feature >Reporter: Jeff Jensen >Assignee: Jeff Jensen >Priority: Minor > Fix For: 1.9 > > > With using an alternate doclet, there is probably need to specify additional > parameters for that custom doclet. The M1 Javadoc plugin does not allow > that. Need to change the plugin to used the nested tag instead of > the doclet property. -- 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: (MANTTASKS-67) artifact:deploy - The name of deploying element in snapshot repository is wrong
[ http://jira.codehaus.org/browse/MANTTASKS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93766 ] Herve Boutemy commented on MANTTASKS-67: this seem to be a duplicate from MANTTASKS-23 > artifact:deploy - The name of deploying element in snapshot repository is > wrong > --- > > Key: MANTTASKS-67 > URL: http://jira.codehaus.org/browse/MANTTASKS-67 > Project: Maven 2.x Ant Tasks > Issue Type: Bug >Affects Versions: 2.0.6 >Reporter: David N'DIAYE > Attachments: testSnapshots.zip > > > The zip file contains test with Ant. > To launch it : ant test. > I try to deploy a snapshot artifact in repository > So, my pom.xml contains a version with the extension '-SNAPSHOT' > And in my build file Ant i do this : > > > > > In the repository the name of the artifact is > --SNAPSHOT. instead of > --.-- > Another problem, i try to upload 2 attachments with my artifact (javadoc and > java-source), and the buildNumber in the meta-data.xml increment by 3 instead > of 1 > > > > > > > You can test it with : ant testWithAttach -- 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] Work started: (MPJAVADOC-80) Add specifying params with alternate doclets
[ http://jira.codehaus.org/browse/MPJAVADOC-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MPJAVADOC-80 started by Jeff Jensen. > Add specifying params with alternate doclets > > > Key: MPJAVADOC-80 > URL: http://jira.codehaus.org/browse/MPJAVADOC-80 > Project: maven-javadoc-plugin > Issue Type: New Feature >Reporter: Jeff Jensen >Assignee: Jeff Jensen >Priority: Minor > > With using an alternate doclet, there is probably need to specify additional > parameters for that custom doclet. The M1 Javadoc plugin does not allow > that. Need to change the plugin to used the nested tag instead of > the doclet property. -- 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: (MPJAVADOC-80) Add specifying params with alternate doclets
Add specifying params with alternate doclets Key: MPJAVADOC-80 URL: http://jira.codehaus.org/browse/MPJAVADOC-80 Project: maven-javadoc-plugin Issue Type: New Feature Reporter: Jeff Jensen Assignee: Jeff Jensen Priority: Minor With using an alternate doclet, there is probably need to specify additional parameters for that custom doclet. The M1 Javadoc plugin does not allow that. Need to change the plugin to used the nested tag instead of the doclet property. -- 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
