[jira] Created: (MENFORCER-117) Custom Packaging with executions fails with NullPointerException in RequirePluginVersions.java:702
Custom Packaging with executions fails with NullPointerException in
RequirePluginVersions.java:702
--
Key: MENFORCER-117
URL: https://jira.codehaus.org/browse/MENFORCER-117
Project: Maven 2.x Enforcer Plugin
Issue Type: Bug
Components: Plugin
Affects Versions: 1.0.1
Environment: Windows XP
Reporter: Barrie Treloar
Priority: Critical
Attachments: pom.xml
The pde-maven-plugin causes enforcer to NPE.
I've attached an IT pom.xml.
I haven't had time to investigate this any further than to get the IT to fail
the same as my real build.
{noformat}
zip
org.codehaus.mojo
pde-maven-plugin
1.0-alpha-1
true
example.product
clean-pde
clean
clean
...
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-592) Available languages bar
[ https://jira.codehaus.org/browse/MSITE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MSITE-592. --- Resolution: Duplicate Assignee: Lukas Theussl > Available languages bar > --- > > Key: MSITE-592 > URL: https://jira.codehaus.org/browse/MSITE-592 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: New Feature > Components: doxia integration >Affects Versions: 3.0-beta-3 >Reporter: Andres Gomez Casanova >Assignee: Lukas Theussl > Attachments: Languages.png > > > Maven does not include an easy way to integrate the different translated > sites. > I propose to have a bar showing the available languages. Something similar to > the attached image. > I did it manually, however it should exist an automatic option, that takes > the locales from the POM. > > maven-site-plugin > 3.0-beta-3 > > en,fr,es > The link to each language could be the index.html, and not the corresponding > page in other language, because sites in different languages could be > different (different version, different pages, etc), at least the index.html > is the entry point. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRELEASE-356) deprecate the automated release profile
[ https://jira.codehaus.org/browse/MRELEASE-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MRELEASE-356: -- Fix Version/s: (was: 2.2) 2.3 Punting to 2.3 as not critical now that the release profile is back in 3.0 > deprecate the automated release profile > --- > > Key: MRELEASE-356 > URL: https://jira.codehaus.org/browse/MRELEASE-356 > Project: Maven 2.x Release Plugin > Issue Type: Task > Components: perform >Reporter: Brett Porter > Fix For: 2.3 > > > the release profile is being removed from the super POM in Maven 2.1-alpha-1, > so the release plugin should pre-emptively start ensuring users do this > themselves -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-590) Images in links part could be alone without any text
[ https://jira.codehaus.org/browse/MSITE-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MSITE-590. --- Resolution: Won't Fix Assignee: Lukas Theussl This is done via the velocity template, so it depends on the skin you use. Just create your own skin and adapt the template to your needs, see http://maven.apache.org/plugins/maven-site-plugin/examples/creatingskins.html > Images in links part could be alone without any text > > > Key: MSITE-590 > URL: https://jira.codehaus.org/browse/MSITE-590 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: New Feature > Components: doxia integration, internationalization >Affects Versions: 3.0-beta-3 > Environment: Windows 7 > Maven 3 > Java 6 >Reporter: Andres Gomez Casanova >Assignee: Lukas Theussl > Attachments: Languages.png > > > In Maven, there is not an easy way to link the pages in different languages. > The site in English is completely independent to the site in French and in > Spanish. > Normally, any site in different languages has a flag indicating the available > languages. > I tried to do that with the links, by putting a flag image, but Maven site > forces to include some text besides. > I would like have just the image, but not the text. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRELEASE-591) release:update-versions: add option to do a checkin
[ https://jira.codehaus.org/browse/MRELEASE-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly closed MRELEASE-591. - Resolution: Won't Fix Rejecting this for a number of reasons. 1. In general the principal of the maven release plugin is to only committing to scm tested changes. So if update-versions were to commit, it should invoke a forked build first and only commit after such a forked build completed successfully... 2. There is a ready work-around available for people who just want to commit the changes without such a check-build: mvn release:update-versions scm:commit > release:update-versions: add option to do a checkin > --- > > Key: MRELEASE-591 > URL: https://jira.codehaus.org/browse/MRELEASE-591 > Project: Maven 2.x Release Plugin > Issue Type: Improvement >Affects Versions: 2.0 > Environment: Maven 2.2.1, Release-Plugin 2.0 >Reporter: Michael Wenig > Fix For: 2.2 > > Attachments: MRELEASE-591.patch > > > Currently release:update-versions only modifies the poms locally. > We want to run this on our hudson and expected the goal to change the version > AND do a checkin. Unfortunately it does not... > This is also unexpected as the documentation defines a scnCommentPrefix > (which is not used here): > http://maven.apache.org/plugins/maven-release-plugin/update-versions-mojo.html > I would suggest a boolean-parameter 'commitChanges' which does a checkin so > the functionality is like release:branch without creating a branch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-623) Add a configuration mode to be able to use git svn (at least for release plugin)
[ https://jira.codehaus.org/browse/SCM-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=271547#comment-271547 ] Mark Struberg commented on SCM-623: --- +1 for a new maven-scm-provider-gitsvn > Add a configuration mode to be able to use git svn (at least for release > plugin) > > > Key: SCM-623 > URL: https://jira.codehaus.org/browse/SCM-623 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-git >Affects Versions: 1.5 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 1.6 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRELEASE-571) When collecting active profiles, the active profiles from parent poms are not considered
[ https://jira.codehaus.org/browse/MRELEASE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MRELEASE-571: -- Fix Version/s: (was: 2.2) 2.3 Pushing back from target of 2.2 to 2.3 as: 1. Patch includes formatting changes. 2. Patch does not include any integration test. 3. No summary of testing results of this patch against 2.2.1 and 3.0.x to check for regression with the different profile activation mechanism between 2.x and 3.x > When collecting active profiles, the active profiles from parent poms are not > considered > > > Key: MRELEASE-571 > URL: https://jira.codehaus.org/browse/MRELEASE-571 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: perform, prepare >Affects Versions: 2.0 >Reporter: Lars Corneliussen > Fix For: 2.3 > > Attachments: 89d9799a56d46d7435d08c94ca538845d7145c9b[1].patch, > MRELEASE-571-collect-profiles.patch, profile-ignored-with-module.zip > > > MavenProject.getActiveProfiles() does not return all profiles that are > currently run, but instead only those that are run AND defined on the current > project. > This leads to preparation-builds of modules without the specified active > profiles derived from their parents. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRELEASE-682) support for git svn
[ https://jira.codehaus.org/browse/MRELEASE-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MRELEASE-682: -- Fix Version/s: (was: 2.2) 2.3 Pushing back to 2.3 as the required changes on SCM have not been released yet > support for git svn > --- > > Key: MRELEASE-682 > URL: https://jira.codehaus.org/browse/MRELEASE-682 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Components: Git >Affects Versions: 2.1 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 2.3 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRELEASE-605) when not pushing changes to remote git repo in 2.1, the release plugin fails on release:perform
[
https://jira.codehaus.org/browse/MRELEASE-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg closed MRELEASE-605.
--
Resolution: Won't Fix
Assignee: Mark Struberg
Hi James!
The issue appears to be invalid. Please use true if you
configure false.
This will make the git clone to happen from a local file:// instead of using
the upstream git:// URL.
Please note that localCheckout currently only works with non-sparse checkouts!
We are working on that in the next release.
> when not pushing changes to remote git repo in 2.1, the release plugin fails
> on release:perform
> ---
>
> Key: MRELEASE-605
> URL: https://jira.codehaus.org/browse/MRELEASE-605
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: james strachan
>Assignee: Mark Struberg
> Fix For: 2.2
>
>
> as it tries to clone the remote repo, which has not yet been pushed - so
> there's no tag in the remote repo yet.
> Ideally if pushChanges is false, it should use a value of
> {code}
>
> scm:git:file://${baseDir}
> ...
>
> {code}
> so that it clones from the current local git repo (which has everything
> inside it) rather than the remote repo which has yet to be pushed.
> BTW a great use case for not pushing is using a staging maven repo like
> Nexus; which may reject an attempt to promote a staged build, so you only
> want to push after a downstream stage works.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRELEASE-263) Interactive plugins cannot work in forked executions
[ https://jira.codehaus.org/browse/MRELEASE-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MRELEASE-263: -- Fix Version/s: (was: 2.2) 2.3 Pushing back to 2.3 as this is quite a large scope of work (at a minimum for testing) > Interactive plugins cannot work in forked executions > > > Key: MRELEASE-263 > URL: https://jira.codehaus.org/browse/MRELEASE-263 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.0-beta-6 >Reporter: Daniel Kulp >Priority: Critical > Fix For: 2.3 > > > I was looking into the problems with the GPG plugin when run from the > release plugin and the problems seem to entirely be problems of the > release plugin and Plexus utils. They are showing up in the gpg > plugin, but any plugin that tries to do anything interactively would > most likely run into the same problems. > Issues: > 1) System.in - the release manager doesn't feed anything from System.in > into the forked process. I tried adding System.in to the > CommandLineUtils.executeCommandLine call, but that just causes a hang. > CommandLineUtils will wait until the "in" stream is completely consumed > (returns -1) before returning. With System.in, that never will happen. > 2) Buffered(line style) out - the StreamPumpers use > BufferedInputStream.readLine() to pump from one stream to the other. > This won't work. Anything that does something (like the release plugin > itself) that prompts and then waits for a response on the same line will > appear to just "hang" as the prompt will never make it to the screen. > Basically, those two issues completely prevent us from being able to > un-hard code GPG passphrases from build scripts and such. (unless you > set gpg.useagent to true and use an agent) > In anycase, MGPG-9 is really a release plugin bug although part of it is > due to plexus-utils not providing the support it would need to work > properly.Most likely, we'll need to add a method in CommandLineUtils > that would just take the raw streams (in/out/err) and do straight byte > copy reads without the line buffering. (and once the process > completely, stop pumping the in stream) (of course, that would then > require another plexus-utils release and then the release plugin would > only work with Maven 2.0.6+ with the utils shaded, but that may be > minor) I'll poke around more and see if I can come up with something. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRELEASE-128) SCM properties being replaced during release:perform
[
https://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MRELEASE-128:
--
Fix Version/s: (was: 2.2)
2.3
Pushing back to 2.3 as this is a large scope of work, and there are some issues
that we want to push 2.2 out for.
> SCM properties being replaced during release:perform
>
>
> Key: MRELEASE-128
> URL: https://jira.codehaus.org/browse/MRELEASE-128
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
>Reporter: Craig Dickson
>Assignee: Brett Porter
>Priority: Critical
> Labels: properties
> Fix For: 2.3
>
> Attachments: after-release-perform-pom.xml,
> after-release-prepre-pom.xml, MNG-128-maven-release-manager.patch,
> MRELEASE-128_cvs_hack_RewritePomsForDevelopmentPhase.java.patch,
> original-pom.xml
>
>
> The section of a pom in CVS for a pom archetype project looks like this
> prior to executing release:prepare :
>
> ${base.cvs.url}:commons-maven/uber-pom
>
> ${base.cvs.url}:commons-maven/uber-pom
> ${base.viewcvs.url}/commons-maven/uber-pom
>
> Then after executing release:prepare, the pom in CVS looks like this (new
> tag is only difference):
>
> ${base.cvs.url}:commons-maven/uber-pom
>
> ${base.cvs.url}:commons-maven/uber-pom
> ${base.viewcvs.url}/commons-maven/uber-pom
> R-1_7
>
> Then after executing release:perform, the pom looks like this in CVS:
>
>
> scm:cvs:pserver:behrcvs.masco-coatings.com:/usr/cvsroot:commons-maven/uber-pom
>
> scm:cvs:pserver:behrcvs.masco-coatings.com:/usr/cvsroot:commons-maven/uber-pom
>
> http://behrcvs.masco-coatings.com/cgi-bin/viewcvs.cgi/commons-maven/uber-pom
>
> Notice that the properties that were there for the base URLs for CVS and
> ViewCVS have been replaced with literal values.
> No other properties in the POM are being replaced
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-589) Invalid image assignation in html
[ https://jira.codehaus.org/browse/MSITE-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=271555#comment-271555 ] Lukas Theussl commented on MSITE-589: - This is fixed in current snapshots (2.4 and 3.0-beta-4) with DOXIASITETOOLS-59. > Invalid image assignation in html > - > > Key: MSITE-589 > URL: https://jira.codehaus.org/browse/MSITE-589 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: doxia integration >Affects Versions: 2.1, 2.1.1, 2.2, 2.3, 3.0-beta-1, 3.0-beta-2, 3.0-beta-3 > Environment: Windows 7 > Maven 3 > Java 6 >Reporter: Andres Gomez Casanova >Priority: Critical > Attachments: NewVersion2.png, NewVersion.png, OldVersion.png > > > I have a personal website created from Maven. I have two images in the upper > part as banners, one photo and one logo. Also, I have a small logo in the > navigation section. > Before, it worked perfectly, but since I updated everything to the latest > version there are problems with the images and now I could see that the logos > are not well placed. > The source code of my website is here: > http://zemucan.svn.sourceforge.net/viewvc/zemucan/branches/angoca/ > I tested with different versions, and the bug appears since version 2.1. With > version 2.0.1 and 2.0 works perfectly. > I attached two images, the oldVersion shows how it is supposed to be. The > newVersion shows the bug, the plugin takes the second logo (rightbanner) and > put it as a poweredBy. If I delete the right banner (just the left banner and > the poweredBy) then it takes the left banner image and put as powered By. > As you can see, this is not a configuration problem because it used to work > before. I just change the new maven-site-plugin version and then it fails. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-589) Invalid image assignation in html
[ https://jira.codehaus.org/browse/MSITE-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MSITE-589. --- Resolution: Fixed Fix Version/s: 3.0-beta-4 Assignee: Lukas Theussl > Invalid image assignation in html > - > > Key: MSITE-589 > URL: https://jira.codehaus.org/browse/MSITE-589 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: doxia integration >Affects Versions: 2.1, 2.1.1, 2.2, 2.3, 3.0-beta-1, 3.0-beta-2, 3.0-beta-3 > Environment: Windows 7 > Maven 3 > Java 6 >Reporter: Andres Gomez Casanova >Assignee: Lukas Theussl >Priority: Critical > Fix For: 3.0-beta-4 > > Attachments: NewVersion2.png, NewVersion.png, OldVersion.png > > > I have a personal website created from Maven. I have two images in the upper > part as banners, one photo and one logo. Also, I have a small logo in the > navigation section. > Before, it worked perfectly, but since I updated everything to the latest > version there are problems with the images and now I could see that the logos > are not well placed. > The source code of my website is here: > http://zemucan.svn.sourceforge.net/viewvc/zemucan/branches/angoca/ > I tested with different versions, and the bug appears since version 2.1. With > version 2.0.1 and 2.0 works perfectly. > I attached two images, the oldVersion shows how it is supposed to be. The > newVersion shows the bug, the plugin takes the second logo (rightbanner) and > put it as a poweredBy. If I delete the right banner (just the left banner and > the poweredBy) then it takes the left banner image and put as powered By. > As you can see, this is not a configuration problem because it used to work > before. I just change the new maven-site-plugin version and then it fails. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MPOM-19) Cannot stage site documentation with Maven 3.0.x
Cannot stage site documentation with Maven 3.0.x Key: MPOM-19 URL: https://issues.apache.org/jira/browse/MPOM-19 Project: Maven POM Issue Type: Bug Components: maven Affects Versions: MAVEN-20 Reporter: Stephen Connolly Assignee: Stephen Connolly This is due to the ssh wagon no longer being a default extension in Maven 3.0.x We should consider pushing this up to the ASF pom as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MPOM-19) Cannot stage site documentation with Maven 3.0.x
[ https://issues.apache.org/jira/browse/MPOM-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly resolved MPOM-19. -- Resolution: Fixed Fix Version/s: MAVEN-21 http://svn.apache.org/viewvc?rev=1140082&view=rev > Cannot stage site documentation with Maven 3.0.x > > > Key: MPOM-19 > URL: https://issues.apache.org/jira/browse/MPOM-19 > Project: Maven POM > Issue Type: Bug > Components: maven >Affects Versions: MAVEN-20 >Reporter: Stephen Connolly >Assignee: Stephen Connolly > Fix For: MAVEN-21 > > > This is due to the ssh wagon no longer being a default extension in Maven > 3.0.x > We should consider pushing this up to the ASF pom as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-593) Correction in the french localization
Correction in the french localization - Key: MSITE-593 URL: https://jira.codehaus.org/browse/MSITE-593 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: localization Affects Versions: 2.3 Reporter: Guillaume Husta Priority: Trivial Attachments: site-plugin_fr.properties Here is a correction for the french localization of Maven Site Plugin. A new *site-plugin_fr.properties* is provided, according to [http://maven.apache.org/plugins/maven-site-plugin/i18n.html#Instructions_for_Translators]. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MPOM-19) Cannot stage site documentation with Maven 3.0.x
[ https://issues.apache.org/jira/browse/MPOM-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055444#comment-13055444 ] Hudson commented on MPOM-19: Integrated in maven-parent #41 (See [https://builds.apache.org/job/maven-parent/41/]) [MPOM-19] Cannot stage site documentation with Maven 3.0.x. Implemented as smallest possible fix (i.e. just adding the dependency to the site plugin when running Maven 3.0.x) stephenc : http://svn.apache.org/viewvc/?view=rev&rev=1140082 Files : * /maven/pom/trunk/maven/pom.xml > Cannot stage site documentation with Maven 3.0.x > > > Key: MPOM-19 > URL: https://issues.apache.org/jira/browse/MPOM-19 > Project: Maven POM > Issue Type: Bug > Components: maven >Affects Versions: MAVEN-20 >Reporter: Stephen Connolly >Assignee: Stephen Connolly > Fix For: MAVEN-21 > > > This is due to the ssh wagon no longer being a default extension in Maven > 3.0.x > We should consider pushing this up to the ASF pom as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MCHANGES-263) Add support for JQL introduced in JIRA 4.x
Add support for JQL introduced in JIRA 4.x -- Key: MCHANGES-263 URL: https://jira.codehaus.org/browse/MCHANGES-263 Project: Maven 2.x Changes Plugin Issue Type: New Feature Components: jira Reporter: Alan Parkinson JIRA 4 introduced a powerful SQL like query language called JQL. Supporting JQL can provide powerful ways of downloading issues; Using textual status and resolved ids instead of numeric based ids, Query by ranges of fixVersion, etc... Sample JQL: project = MCHANGES AND resolution = Fixed AND status in (Resolved, Closed) AND fixVersion <="2.6" ORDER BY fixVersion DESC -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-263) Add support for JQL introduced in JIRA 4.x
[ https://jira.codehaus.org/browse/MCHANGES-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=271571#comment-271571 ] Alan Parkinson commented on MCHANGES-263: - What is the best way to version support for JIRA functionality as JQL isn't backwards compatible with earlier JIRA versions? A new issueManagementSystems option of JIRA-JQL or JIRA4 could be added and the existing JIRA option used for backwards compatibility. > Add support for JQL introduced in JIRA 4.x > -- > > Key: MCHANGES-263 > URL: https://jira.codehaus.org/browse/MCHANGES-263 > Project: Maven 2.x Changes Plugin > Issue Type: New Feature > Components: jira >Reporter: Alan Parkinson > > JIRA 4 introduced a powerful SQL like query language called JQL. Supporting > JQL can provide powerful ways of downloading issues; Using textual status and > resolved ids instead of numeric based ids, Query by ranges of fixVersion, > etc... > Sample JQL: > project = MCHANGES AND resolution = Fixed AND status in (Resolved, Closed) > AND fixVersion <="2.6" ORDER BY fixVersion DESC -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-255) fixVersionIds supports human readable display versions in JIRA 4
[ https://jira.codehaus.org/browse/MCHANGES-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=271572#comment-271572 ] Alan Parkinson commented on MCHANGES-255: - Created MCHANGES-263 > fixVersionIds supports human readable display versions in JIRA 4 > > > Key: MCHANGES-255 > URL: https://jira.codehaus.org/browse/MCHANGES-255 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.5 >Reporter: SebbASF > > http://maven.apache.org/plugins/maven-changes-plugin/jira-report-mojo.html#fixVersionIds > says > bq. Sets the fix version id(s) that you want to limit your report to include. > These are JIRA's internal version ids, NOT the human readable display ones. > This may be true for JIRA 3, but for JIRA 4, AFAICT one can use the human > readable versions. > It would be helpful to document how to obtain the internal version ids, if > these are still supported or needed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCHANGES-261) Mail sender specification pointlessly difficult
[ https://jira.codehaus.org/browse/MCHANGES-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MCHANGES-261. - Resolution: Fixed Fix Version/s: 2.7 /Users/benson/asf/mvn/plugins/maven-changes-plugin svn log -r1140150 r1140150 | bimargulies | 2011-06-27 09:15:01 -0400 (Mon, 27 Jun 2011) | 2 lines [MCHANGES-261]: Allow -Dchange.sender for the from address. > Mail sender specification pointlessly difficult > --- > > Key: MCHANGES-261 > URL: https://jira.codehaus.org/browse/MCHANGES-261 > Project: Maven 2.x Changes Plugin > Issue Type: Bug >Affects Versions: 2.5, 2.6 >Reporter: Benson Margulies >Assignee: Benson Margulies > Fix For: 2.7 > > > THe mail sender in the pom is a complex data structure, inaccessible from -D. > There's no good reason for this; it wouldn't be hard to write a tiny parser > to allow someone not listed as a 'developer' to send email. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DOXIASITETOOLS-61) Publish decoration-1.1.0.xsd
[ https://jira.codehaus.org/browse/DOXIASITETOOLS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated DOXIASITETOOLS-61: -- Assignee: Dennis Lundberg Issue Type: Task (was: Bug) Summary: Publish decoration-1.1.0.xsd (was: decoration-1.1.0.xsd) > Publish decoration-1.1.0.xsd > > > Key: DOXIASITETOOLS-61 > URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-61 > Project: Maven Doxia Sitetools > Issue Type: Task > Components: Doc renderer > Environment: Windows 7 >Reporter: Andres Gomez Casanova >Assignee: Dennis Lundberg > > I was creating a site.xml, and I was looking for the documentation. I found > the xsd for the version 1.1.0, however, this version is still not supported > when executing mvn site. > The documentation is here: > http://maven.apache.org/doxia/doxia-sitetools/doxia-decoration-model/decoration.html > and options like Google Analytics are new but not supported for normal plugin. > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:2.0.1:site (default-site) on > project site: SiteToolException: Error parsing site descriptor: Unrecognised > tag: 'googleAnalyticsAccountId' (position: START_TAG seen > ...\r\n ... @16:29) - [Help 1] > Even, the address for the xsd is not valid: > http://maven.apache.org/xsd/decoration-1.1.0.xsd > The only versions there are 1.0.0 and 1.0.1. > I think this documentation is for tests, but was published in production. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIASITETOOLS-61) Publish decoration-1.1.0.xsd
[ https://jira.codehaus.org/browse/DOXIASITETOOLS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=271613#comment-271613 ] Dennis Lundberg commented on DOXIASITETOOLS-61: --- The error you are getting is because you are not using the correct version of the Site Plugin. These features was added in Doxia Sitetools 1.2, which is used by Maven Site Plugin 2.3. > Publish decoration-1.1.0.xsd > > > Key: DOXIASITETOOLS-61 > URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-61 > Project: Maven Doxia Sitetools > Issue Type: Task > Components: Doc renderer > Environment: Windows 7 >Reporter: Andres Gomez Casanova >Assignee: Dennis Lundberg > > I was creating a site.xml, and I was looking for the documentation. I found > the xsd for the version 1.1.0, however, this version is still not supported > when executing mvn site. > The documentation is here: > http://maven.apache.org/doxia/doxia-sitetools/doxia-decoration-model/decoration.html > and options like Google Analytics are new but not supported for normal plugin. > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:2.0.1:site (default-site) on > project site: SiteToolException: Error parsing site descriptor: Unrecognised > tag: 'googleAnalyticsAccountId' (position: START_TAG seen > ...\r\n ... @16:29) - [Help 1] > Even, the address for the xsd is not valid: > http://maven.apache.org/xsd/decoration-1.1.0.xsd > The only versions there are 1.0.0 and 1.0.1. > I think this documentation is for tests, but was published in production. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DOXIASITETOOLS-61) Publish decoration-1.1.0.xsd
[ https://jira.codehaus.org/browse/DOXIASITETOOLS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed DOXIASITETOOLS-61. - Resolution: Fixed The new 1.1.0 version of the xsd file was not published when the site for doxia-sitetools 1.2 was deployed. I have now deployed the 1.1.0 version of the xsd. It will be available when the sie is synched into production. > Publish decoration-1.1.0.xsd > > > Key: DOXIASITETOOLS-61 > URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-61 > Project: Maven Doxia Sitetools > Issue Type: Task > Components: Doc renderer > Environment: Windows 7 >Reporter: Andres Gomez Casanova >Assignee: Dennis Lundberg > > I was creating a site.xml, and I was looking for the documentation. I found > the xsd for the version 1.1.0, however, this version is still not supported > when executing mvn site. > The documentation is here: > http://maven.apache.org/doxia/doxia-sitetools/doxia-decoration-model/decoration.html > and options like Google Analytics are new but not supported for normal plugin. > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:2.0.1:site (default-site) on > project site: SiteToolException: Error parsing site descriptor: Unrecognised > tag: 'googleAnalyticsAccountId' (position: START_TAG seen > ...\r\n ... @16:29) - [Help 1] > Even, the address for the xsd is not valid: > http://maven.apache.org/xsd/decoration-1.1.0.xsd > The only versions there are 1.0.0 and 1.0.1. > I think this documentation is for tests, but was published in production. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-751) Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/
[ https://jira.codehaus.org/browse/SUREFIRE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=271620#comment-271620 ] Olivier Lamy commented on SUREFIRE-751: --- sources here : https://github.com/kohsuke/maven-junit-plugin > Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/ > -- > > Key: SUREFIRE-751 > URL: https://jira.codehaus.org/browse/SUREFIRE-751 > Project: Maven Surefire > Issue Type: New Feature >Affects Versions: 2.9 >Reporter: Stephen Connolly >Assignee: Kristian Rosenvold > Fix For: 3.0 > > > The current parallel execution spawns one thread _per_class_ > When there is a large disparity between the number of tests in different > classes, this can result in a longer execution time. This can often happen in > GUI testing, where a couple of classes will contain a lot of long running > (but low cpu) test cases, and the remaining classes run fast. > See http://maven-junit-plugin.kenai.com/ for an attempt at solving this -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-688) Release a project and all its snapshot dependencies, without an aggregator
Release a project and all its snapshot dependencies, without an aggregator
--
Key: MRELEASE-688
URL: https://jira.codehaus.org/browse/MRELEASE-688
Project: Maven 2.x Release Plugin
Issue Type: Improvement
Components: perform, prepare
Affects Versions: 2.1
Reporter: Maxime Lemanissier
Hi all,
We are looking for a way to perform a release on a project and all its snapshot
dependencies (internal dependencies only).
Using a pom aggregator and ${project.version} in dependencyMgmt for all
internal dependencies allows such a release in "one click", but the drawback is
we have to regroup projects within this aggregator, according to the dependency
graph.
We would like to be able to do the same thing, but without having to use an
aggregator, that in some way add another link between projects than their
dependencies.
The process would be the same than with an aggregator, but instead of building
a maven reactor with modules, it would be done among snapshot dependencies.
Scm element is set in each dependency's pom, so maven-release-plugin could find
where sources are, and release them.
Could maven-release-plugin manage this with a new parameter ?
(releaseSnapshotDependencies=true for example)
We already had some posts here:
http://maven.40175.n5.nabble.com/Relesa-a-project-and-all-its-snapshot-dependencies-without-an-aggregator-td4527536.html
Thx
Maxime
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-681) Bug while using addVersionToProjectName property
[ https://jira.codehaus.org/browse/MECLIPSE-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean Helou updated MECLIPSE-681: Attachment: MECLIPSE-681.zip I hit this problem at work with a corporate parent pom I can't change. Attached in MECLIPSE-681.zip is a self contained reproduction of the bug. Complete with a parent pom and failing .project and .classpath For anyone hitting this, know that using projectNameTemplate allows you to work around the problem. > Bug while using addVersionToProjectName property > > > Key: MECLIPSE-681 > URL: https://jira.codehaus.org/browse/MECLIPSE-681 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug >Affects Versions: 2.8 > Environment: Unbuntu 10.4, JDK-1.6.0_24, Eclipse Helios Service > Release 1 >Reporter: Ulrich Vachon > Attachments: MECLIPSE-681.zip, pom-all.xml, project > > > I had a side effect when I wanted to set to false the > "addVersionToProjectName" plugin property. In fact, if the property is set to > false, my Eclipse projects doesn't contains the version in project name, but > the projects referenced contains the version. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MINDEXER-33) Noncanonical Jenkins URL
Noncanonical Jenkins URL
Key: MINDEXER-33
URL: https://jira.codehaus.org/browse/MINDEXER-33
Project: Maven Indexer
Issue Type: Bug
Reporter: Jesse Glick
Priority: Trivial
https://svn.apache.org/repos/asf/maven/indexer/trunk/pom.xml has
https://builds.apache.org/hudson/job/maven-indexer/ for {{ciManagement.url}}
but this should probably be https://builds.apache.org/job/maven-indexer/
instead.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MPOM-7) Apache Parent Pom should be properly documented
[ https://issues.apache.org/jira/browse/MPOM-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056182#comment-13056182 ] Hudson commented on MPOM-7: --- Integrated in ASF Parent Pom #22 (See [https://builds.apache.org/job/ASF%20Parent%20Pom/22/]) [MPOM-7] added separate pom and site directory for pom documentation hboutemy : Files : * /maven/pom/trunk/asf/src/site-docs/apt * /maven/pom/trunk/asf/src/site/apt * /maven/pom/trunk/asf/src/site-docs/site.xml * /maven/pom/trunk/asf/src/site/site.xml * /maven/pom/trunk/asf/site-pom.xml * /maven/pom/trunk/asf/src/site-docs/apt/index.apt * /maven/pom/trunk/asf/src/site-docs * /maven/pom/trunk/asf/pom.xml > Apache Parent Pom should be properly documented > --- > > Key: MPOM-7 > URL: https://issues.apache.org/jira/browse/MPOM-7 > Project: Maven POM > Issue Type: Improvement > Components: asf >Reporter: Sebb >Assignee: Olivier Lamy > Fix For: ASF-10 > > Attachments: asf-pom.patch > > > There does not appear to be any documentation on the Apache Parent Pom. > Please can the following be added to the next release: > * how to report issues > * where to find the source > Ideally there should be a page on the Maven web-site that documents it as > well. > In which case please link to that from the POM as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5064) mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds)
[
https://jira.codehaus.org/browse/MNG-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=271653#comment-271653
]
Benson Margulies commented on MNG-5064:
---
/Users/benson/asf/mvn/core-integration-testing/core-it-suite svn log -r1140365
r1140365 | bimargulies | 2011-06-27 19:17:28 -0400 (Mon, 27 Jun 2011) | 2 lines
[MNG-5064]: add a test that seems to prove that this problem does not, in fact,
exist.
> mvn -nsu (--no-snapshot-updates) should not download snapshots (and break
> local builds)
> ---
>
> Key: MNG-5064
> URL: https://jira.codehaus.org/browse/MNG-5064
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.0.3
>Reporter: Geoffrey De Smet
>Assignee: Benson Margulies
>Priority: Critical
>
> Here's the command I ran (on a fresh morning, because our update policy is
> daily and our SNAPSHOTs are deployed by Hudson at night, with maven 3.0.3):
> {code}
> $ mvn -nsu clean install -DskipTests
> [INFO] Scanning for projects...
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/droolsjbpm-parent/5.2.0-SNAPSHOT/maven-metadata.xml
> ...
> [INFO]
>
> [INFO] Building Drools Planner core 5.2.0-SNAPSHOT
> [INFO]
>
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/maven-metadata.xml
> Downloaded:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/maven-metadata.xml
> (2 KB at 1.8 KB/sec)
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.pom
> Downloaded:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.pom
> (6 KB at 6.0 KB/sec)
> ...
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.jar
> ...
> {code}
> Despite that I added "-nsu" (also known as "--no-snapshot-updates"), it
> downloaded snapshots.
> This is a pretty bad thing, because if I hadn't pulled in days (and just
> wanted to test my local changes before merging in remote changes),
> this would have broke my build, for example:
> - because the parent pom in downloaded SNAPSHOT had a dependency removed
> which my local pom was still using (because I hadn't pulled the changes yet)
> - because the downloaded knowledge-api changed a non-released method
> signature (and I hadn't pulled the changes to deal with that yet).
> - ...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5064) mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds)
[
https://jira.codehaus.org/browse/MNG-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=271652#comment-271652
]
Benson Margulies commented on MNG-5064:
---
I just added an integration test to maven that does the right thing (doesn't
download snapshots). It passes.
Perhaps you could offer some additional thought as to what might be going on
here?
> mvn -nsu (--no-snapshot-updates) should not download snapshots (and break
> local builds)
> ---
>
> Key: MNG-5064
> URL: https://jira.codehaus.org/browse/MNG-5064
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.0.3
>Reporter: Geoffrey De Smet
>Assignee: Benson Margulies
>Priority: Critical
>
> Here's the command I ran (on a fresh morning, because our update policy is
> daily and our SNAPSHOTs are deployed by Hudson at night, with maven 3.0.3):
> {code}
> $ mvn -nsu clean install -DskipTests
> [INFO] Scanning for projects...
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/droolsjbpm-parent/5.2.0-SNAPSHOT/maven-metadata.xml
> ...
> [INFO]
>
> [INFO] Building Drools Planner core 5.2.0-SNAPSHOT
> [INFO]
>
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/maven-metadata.xml
> Downloaded:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/maven-metadata.xml
> (2 KB at 1.8 KB/sec)
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.pom
> Downloaded:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.pom
> (6 KB at 6.0 KB/sec)
> ...
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.jar
> ...
> {code}
> Despite that I added "-nsu" (also known as "--no-snapshot-updates"), it
> downloaded snapshots.
> This is a pretty bad thing, because if I hadn't pulled in days (and just
> wanted to test my local changes before merging in remote changes),
> this would have broke my build, for example:
> - because the parent pom in downloaded SNAPSHOT had a dependency removed
> which my local pom was still using (because I hadn't pulled the changes yet)
> - because the downloaded knowledge-api changed a non-released method
> signature (and I hadn't pulled the changes to deal with that yet).
> - ...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2743) Dependency poms not timely merged with parents
[
https://jira.codehaus.org/browse/MNG-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=271656#comment-271656
]
Benson Margulies commented on MNG-2743:
---
This issue has been sitting for a long time with no test case. If no one can
provide one in a week or two, I will close it.
> Dependency poms not timely merged with parents
> --
>
> Key: MNG-2743
> URL: https://jira.codehaus.org/browse/MNG-2743
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies
>Affects Versions: 2.0.4, 2.0.6
>Reporter: Kenney Westerhof
>Priority: Blocker
> Fix For: Issues to be reviewed for 3.x
>
>
> POM's of dependencies are not properly merged with their parents.
> It could be that they're not merged at all, or only partly. Since the code to
> merge poms is the same
> everywhere, and tags are merged for local poms, I fear that
> they're not merged at all.
> With this setup:
> * local workspace:
> ** project A
> *** depends on remote artifact B, residing in 'central'
> * repository central:
> ** artifact B (cocoon-core)
> *** has parent P (cocoon), also here at central
> *** declares a dependency on D, residing in repo R (not a standard repository)
> ** pom P, declares repository R
> * repository R:
> ** artifact D (avalon-framework-impl)
> *** declares dependency on lib L, also here at repository R
> ** artifact L (avalon-framework-api)
> When running mvn install on local project A, observe the following log:
> {noformat}
>
> // cocoon-core has been resolved, now it's dependency poms are resolved:
> [DEBUG] Trying repository central
> Downloading:
> http://repo1.maven.org/maven2/org/apache/avalon/framework/avalon-framework-impl/4.3/avalon-framework-impl-4.3.pom
> [WARNING] Unable to get resource from repository central
> (http://repo1.maven.org/maven2)
> [DEBUG] Artifact not found - using stub model: Unable to download the
> artifact from any repository
>
> org.apache.avalon.framework:avalon-framework-impl:pom:4.3
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
>
> [DEBUG] Using defaults for missing POM
> org.apache.avalon.framework:avalon-framework-impl:pom:4.3:compile
> // note: above, the parent of cocoon-core (B) (which is cocoon (P)), is not
> merged, as the repo R is not
> // visible in B to resolve D
>
> // now, the artifacts themselves are downloaded
>
> [DEBUG] Trying repository central
> Downloading:
> http://repo1.maven.org/maven2/org/apache/avalon/framework/avalon-framework-impl/4.3/avalon-framework-impl-4.3.jar
> [WARNING] Unable to get resource from repository central
> (http://repo1.maven.org/maven2)
> // Here, repo R _is_ used to search, which means that the parent P is merged
> with B and the repo is available
> [DEBUG] Trying repository apache.snapshot
> Downloading:
> http://people.apache.org/maven-snapshot-repository/org/apache/avalon/framework/avalon-framework-impl/4.3/avalon-framework
> -impl-4.3.jar
> 2/56K^M3/56K^M7/56K^M8/56K^M9/56K^M13/56K^M17/56K^M19/56K^M20/56K^M24/56K^M28/56K^M32/56K^M36/56K^M40/56K^M42/56K^M43/56K^M44/56K^M46/
> 56K^M47/56K^M49/56K^M50/56K^M52/56K^M53/56K^M54/56K^M56/56K^M56K downloaded
> [DEBUG] Artifact resolved
> {noformat}
> The problem here is that the jar is now available in the local repo, but the
> pom is not, and the dependencies of D aren't downloaded.
> It seems pom B is only merged with P _after_ all dependency poms for B have
> been resolved.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIASITETOOLS-61) Publish decoration-1.1.0.xsd
[ https://jira.codehaus.org/browse/DOXIASITETOOLS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=271678#comment-271678 ] Andres Gomez Casanova commented on DOXIASITETOOLS-61: - I was not talking about the plugin itself, I was talking about the documentation in the official Maven page. Have you seen this page: http://maven.apache.org/doxia/doxia-sitetools/doxia-decoration-model/decoration.html Well, this is the documentation for xsd v1.1.0, not for the current available version 1.0.1 I think you should only publish the documentation for the new version when the new plugin version will be release. At this moment, the current documentation is not compatible with the latest released version. > Publish decoration-1.1.0.xsd > > > Key: DOXIASITETOOLS-61 > URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-61 > Project: Maven Doxia Sitetools > Issue Type: Task > Components: Doc renderer > Environment: Windows 7 >Reporter: Andres Gomez Casanova >Assignee: Dennis Lundberg > > I was creating a site.xml, and I was looking for the documentation. I found > the xsd for the version 1.1.0, however, this version is still not supported > when executing mvn site. > The documentation is here: > http://maven.apache.org/doxia/doxia-sitetools/doxia-decoration-model/decoration.html > and options like Google Analytics are new but not supported for normal plugin. > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:2.0.1:site (default-site) on > project site: SiteToolException: Error parsing site descriptor: Unrecognised > tag: 'googleAnalyticsAccountId' (position: START_TAG seen > ...\r\n ... @16:29) - [Help 1] > Even, the address for the xsd is not valid: > http://maven.apache.org/xsd/decoration-1.1.0.xsd > The only versions there are 1.0.0 and 1.0.1. > I think this documentation is for tests, but was published in production. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (DOXIASITETOOLS-61) Publish decoration-1.1.0.xsd
[ https://jira.codehaus.org/browse/DOXIASITETOOLS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andres Gomez Casanova reopened DOXIASITETOOLS-61: - The ticket is not about the plugin itself, it is about the documentation (html files published in Maven site) > Publish decoration-1.1.0.xsd > > > Key: DOXIASITETOOLS-61 > URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-61 > Project: Maven Doxia Sitetools > Issue Type: Task > Components: Doc renderer > Environment: Windows 7 >Reporter: Andres Gomez Casanova >Assignee: Dennis Lundberg > > I was creating a site.xml, and I was looking for the documentation. I found > the xsd for the version 1.1.0, however, this version is still not supported > when executing mvn site. > The documentation is here: > http://maven.apache.org/doxia/doxia-sitetools/doxia-decoration-model/decoration.html > and options like Google Analytics are new but not supported for normal plugin. > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:2.0.1:site (default-site) on > project site: SiteToolException: Error parsing site descriptor: Unrecognised > tag: 'googleAnalyticsAccountId' (position: START_TAG seen > ...\r\n ... @16:29) - [Help 1] > Even, the address for the xsd is not valid: > http://maven.apache.org/xsd/decoration-1.1.0.xsd > The only versions there are 1.0.0 and 1.0.1. > I think this documentation is for tests, but was published in production. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIASITETOOLS-61) Publish decoration-1.1.0.xsd
[ https://jira.codehaus.org/browse/DOXIASITETOOLS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=271689#comment-271689 ] Dennis Lundberg commented on DOXIASITETOOLS-61: --- Version 1.2 of doxia sitetools, which uses version 1.1.0 of the xsd is the released version. Which documentation do you feel is wrong or missing > Publish decoration-1.1.0.xsd > > > Key: DOXIASITETOOLS-61 > URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-61 > Project: Maven Doxia Sitetools > Issue Type: Task > Components: Doc renderer > Environment: Windows 7 >Reporter: Andres Gomez Casanova >Assignee: Dennis Lundberg > > I was creating a site.xml, and I was looking for the documentation. I found > the xsd for the version 1.1.0, however, this version is still not supported > when executing mvn site. > The documentation is here: > http://maven.apache.org/doxia/doxia-sitetools/doxia-decoration-model/decoration.html > and options like Google Analytics are new but not supported for normal plugin. > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:2.0.1:site (default-site) on > project site: SiteToolException: Error parsing site descriptor: Unrecognised > tag: 'googleAnalyticsAccountId' (position: START_TAG seen > ...\r\n ... @16:29) - [Help 1] > Even, the address for the xsd is not valid: > http://maven.apache.org/xsd/decoration-1.1.0.xsd > The only versions there are 1.0.0 and 1.0.1. > I think this documentation is for tests, but was published in production. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
