[jira] Created: (MNG-5076) Improve SEO of documentation of lifecycle.xml
Improve SEO of documentation of lifecycle.xml - Key: MNG-5076 URL: http://jira.codehaus.org/browse/MNG-5076 Project: Maven 2 & 3 Issue Type: Improvement Components: Plugins and Lifecycle Affects Versions: 2.2.1 Reporter: Benson Margulies I will attach a patch. If someone tells me the corresponding mdo file for 3.x, I'll get that too. -- 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-5076) Improve SEO of documentation of lifecycle.xml
[ http://jira.codehaus.org/browse/MNG-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MNG-5076: -- Attachment: MNG-5076.patch Improvement to description to make google more likely to find it. > Improve SEO of documentation of lifecycle.xml > - > > Key: MNG-5076 > URL: http://jira.codehaus.org/browse/MNG-5076 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: Plugins and Lifecycle >Affects Versions: 2.2.1 >Reporter: Benson Margulies > Attachments: MNG-5076.patch > > > I will attach a patch. If someone tells me the corresponding mdo file for > 3.x, I'll get that too. -- 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-104) Error installing artifact's metadata
[ http://jira.codehaus.org/browse/MINVOKER-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=264544#action_264544 ] John Sipher commented on MINVOKER-104: -- I understand the point about the recommended practice, but... The proposed fix - adding maven-metadata-local.xml.lock - seems pretty simple. Why not go ahead and fix it and save people like me the trouble of researching the problem and figuring out a workaround? I think there are probably a lot of Maven users like me that just want to use the tool without making a career out of understanding all the ins and outs. That's possible because great tools like Maven "will run with sensible defaults" (see http://maven.apache.org/run-maven/index.html#Quick_Start for quote). In this case Maven doesn't run (at least not reliably) with the default behavior, and I'm using up a good chunk of my Sunday trying to figure out a workaround that won't break something else. > Error installing artifact's metadata > > > Key: MINVOKER-104 > URL: http://jira.codehaus.org/browse/MINVOKER-104 > Project: Maven 2.x Invoker Plugin > Issue Type: Bug >Reporter: Geoff Simpson >Priority: Critical > Attachments: minstall-54-error-install-artifact.patch > > > Error installing artifact's metadata: Error installing metadata: Error > updating group repository metadata > end tag not allowed in epilog but got / (position: END_TAG seen ...\n > Looks like there might be an issue with updates to maven-metadata-local.xml > during the mvn install task. we have a build server that is multi threaded. > we often see this in the > > > > maven-metadata-local.xml. > maybe a solution is to add maven-metadata-local.xml.lock to ensure two > threads don't update the file at the same time -- 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-5076) Improve SEO of documentation of lifecycle.xml
[ http://jira.codehaus.org/browse/MNG-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNG-5076. -- Resolution: Fixed Fix Version/s: 3.0.4 2.2.2 Assignee: Herve Boutemy applied with modifications in r1096335 for 2.2 branch and r1096338 in trunk thank you > Improve SEO of documentation of lifecycle.xml > - > > Key: MNG-5076 > URL: http://jira.codehaus.org/browse/MNG-5076 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: Plugins and Lifecycle >Affects Versions: 2.2.1 >Reporter: Benson Margulies >Assignee: Herve Boutemy > Fix For: 2.2.2, 3.0.4 > > Attachments: MNG-5076.patch > > > I will attach a patch. If someone tells me the corresponding mdo file for > 3.x, I'll get that too. -- 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-5076) Improve SEO of documentation of lifecycle.xml
[ http://jira.codehaus.org/browse/MNG-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=264546#action_264546 ] Herve Boutemy edited comment on MNG-5076 at 4/24/11 11:01 AM: -- applied with modifications in [r1096335|http://svn.apache.org/viewvc?rev=1096335&view=rev] for 2.2 branch and [r1096338|http://svn.apache.org/viewvc?rev=1096338&view=rev] in trunk thank you was (Author: hboutemy): applied with modifications in r1096335 for 2.2 branch and r1096338 in trunk thank you > Improve SEO of documentation of lifecycle.xml > - > > Key: MNG-5076 > URL: http://jira.codehaus.org/browse/MNG-5076 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: Plugins and Lifecycle >Affects Versions: 2.2.1 >Reporter: Benson Margulies >Assignee: Herve Boutemy > Fix For: 2.2.2, 3.0.4 > > Attachments: MNG-5076.patch > > > I will attach a patch. If someone tells me the corresponding mdo file for > 3.x, I'll get that too. -- 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-5076) Improve SEO of documentation of lifecycle.xml
[ http://jira.codehaus.org/browse/MNG-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=264548#action_264548 ] Benson Margulies commented on MNG-5076: --- Hmm. Do you think Google does the right thing if you search for 'lifecycle.xml' if the occurrence on the page is /a/b/c/lifecycle.xml? Is there any way in the mdo file to add to the meta keywords? > Improve SEO of documentation of lifecycle.xml > - > > Key: MNG-5076 > URL: http://jira.codehaus.org/browse/MNG-5076 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: Plugins and Lifecycle >Affects Versions: 2.2.1 >Reporter: Benson Margulies >Assignee: Herve Boutemy > Fix For: 2.2.2, 3.0.4 > > Attachments: MNG-5076.patch > > > I will attach a patch. If someone tells me the corresponding mdo file for > 3.x, I'll get that too. -- 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-5077) Performance of StringSearchModelInterpolator could be much better
Performance of StringSearchModelInterpolator could be much better - Key: MNG-5077 URL: http://jira.codehaus.org/browse/MNG-5077 Project: Maven 2 & 3 Issue Type: Improvement Components: Inheritance and Interpolation Affects Versions: 3.0.3 Environment: Maven 3.0.3 trunk Reporter: Jörg Waßmer Priority: Minor Currently I am investigating performance problems with the large project trees (100+ projects). The main cause is the Netbeans Maven Plugin, but I also found and fixed a bottleneck in Maven itself, in class org.apache.maven.model.interpolation.StringSearchModelInterpolator. I created a patch against the today's Maven 3 trunk, https://svn.apache.org/repos/asf/maven/maven-3/trunk. It does following: - don't use AccessController if no SecurityManager is active. - don't call java.lang.reflect.Field.setAccessible(false). It is not necessary, because the Field object are never exposed to outside the class. - getFields(Class) now determines which fields are qualified for interpolation, instead of determining it again on each call to traverseObjectWithParents(). The behaviour is exactly the same as before. The performance is much better. Formerly about 12500 ms for all projects, now about 4500, where most of the CPU time is consumed by StringSearchModelInterpolator.interpolateInternal(). -- 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-5077) Performance of StringSearchModelInterpolator could be much better
[ http://jira.codehaus.org/browse/MNG-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Waßmer updated MNG-5077: - Attachment: MNG-5077-maven-model-builder.patch Attached patch. > Performance of StringSearchModelInterpolator could be much better > - > > Key: MNG-5077 > URL: http://jira.codehaus.org/browse/MNG-5077 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: Inheritance and Interpolation >Affects Versions: 3.0.3 > Environment: Maven 3.0.3 trunk >Reporter: Jörg Waßmer >Priority: Minor > Attachments: MNG-5077-maven-model-builder.patch > > > Currently I am investigating performance problems with the large project > trees (100+ projects). > The main cause is the Netbeans Maven Plugin, but I also found and fixed a > bottleneck in Maven itself, in class > org.apache.maven.model.interpolation.StringSearchModelInterpolator. > I created a patch against the today's Maven 3 trunk, > https://svn.apache.org/repos/asf/maven/maven-3/trunk. > It does following: > - don't use AccessController if no SecurityManager is active. > - don't call java.lang.reflect.Field.setAccessible(false). It is not > necessary, because the Field object are never exposed to outside the class. > - getFields(Class) now determines which fields are qualified for > interpolation, instead of determining it again on each call to > traverseObjectWithParents(). > The behaviour is exactly the same as before. The performance is much better. > Formerly about 12500 ms for all projects, now about > 4500, where most of the CPU time is consumed by > StringSearchModelInterpolator.interpolateInternal(). -- 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: (MJARSIGNER-12) It should be possible to save the keystore in one location for multi module projects
[ http://jira.codehaus.org/browse/MJARSIGNER-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=264573#action_264573 ] Christian Schulte commented on MJARSIGNER-12: - Did you try using an URL for the keystore parameter (http://your.keystore.location/your.keystore.resource) ? I think the jarsigner tool already supports keystore URLs. > It should be possible to save the keystore in one location for multi module > projects > > > Key: MJARSIGNER-12 > URL: http://jira.codehaus.org/browse/MJARSIGNER-12 > Project: Maven 2.x Jar Signer Plugin > Issue Type: New Feature >Reporter: Sven Kirmess > > We have a multi module maven setup. The problem is that this plugin requires > us to have the keystore either in the same location on all machines or in the > source code along each and every pom.xml file. > I would like to have one of the following: > - Save the file on one location in Subversion and use something like >svn://svn.example.com/trunk/keystore >and the plugin would have to take care to check out the keystore into > every project as needed. > or > - Put the keystore into a JAR file and save that JAR file on the Nexus > server. Then make the jarsigner plugin depend on this JAR file, download it > for every project and extract the keystore from there. This would be like > what the assembly plugin can do for its descriptors. > http://docs.codehaus.org/display/MAVENUSER/Assembly+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] Commented: (MNG-2971) Variables are not replaced into installed pom file
[
http://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=264576#action_264576
]
Andreas Pieber commented on MNG-2971:
-
Hey Luke, would you mind sharing the antrun configuration section of your pom
with us? :)
> Variables are not replaced into installed pom file
> --
>
> Key: MNG-2971
> URL: http://jira.codehaus.org/browse/MNG-2971
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Deployment, Inheritance and Interpolation
> Environment: Windows, Solaris
> Maven version 2.0.4
>Reporter: Laurent Dauvilaire
>Assignee: Ralph Goers
> Fix For: Issues to be reviewed for 3.x
>
>
> Variables are not replaced into installed pom file.
> Here is a sample pom file
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.xxx.root
> root
> pom
> ${prop.version}
> My Project
> ...
>
> 3.0.20
>
>
> The installed pom is into
> ${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
> is the same as the project pom file but the version referenced into the
> installed pom file is ${prop.version} instead of 3.0.20
> which creates problem to artifacts depending of this one.
> Thanks in advance
--
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
