[jira] Commented: (MECLIPSE-697) Delete deprecated code
[ https://jira.codehaus.org/browse/MECLIPSE-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280010#comment-280010 ] Barrie Treloar commented on MECLIPSE-697: - http://maven.40175.n5.nabble.com/maven-eclipse-plugin-pde-support-and-OSGiManifest-writer-tp4832480p4832480.html Two +1 to remove pde mode. Should this bump the version from 2.9 to 3.0? Delete deprecated code -- Key: MECLIPSE-697 URL: https://jira.codehaus.org/browse/MECLIPSE-697 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Reporter: Barrie Treloar Assignee: Barrie Treloar Fix For: 2.9 There are deprecated classes that have been there for a while. As part of cleaning up, its time for them to go. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-604) Properties from settings.xml are not recognized in site distribution management
[
https://jira.codehaus.org/browse/MSITE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl updated MSITE-604:
Fix Version/s: 3.1
Properties from settings.xml are not recognized in site distribution
management
Key: MSITE-604
URL: https://jira.codehaus.org/browse/MSITE-604
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Components: site:deploy
Affects Versions: 3.0
Environment: Apache Maven 2.2.1 and 3.0.3
Reporter: Marcin Kuthan
Fix For: 3.1
My distribution management section looks like:
{code}
distributionManagement
site
id${acme-corporate-pom.siteRepositoryId}/id
url${acme-corporate-pom.siteRepositoryUrl}/url
/site
/distributionManagement
{code}
Where the default property values are defined in the pom:
{code}
properties
acme-corporate-pom.siteRepositoryIdacme-site/acme-corporate-pom.siteRepositoryId
acme-corporate-pom.siteRepositoryUrlscp://sites.intranet.acme.com/var/www/acme-corporate-pom.siteRepositoryUrl
/properties
{code}
I'm able redefine properties from command line, the provided repository is
used instead default one:
{code}
mvn site:site site:deploy
-Dacme-corporate-pom.siteRepositoryUrl=scp://somehost/var/www/sites
-Dacme-corporate-pom.siteRepositoryId=somehost
{code}
But when I redefine properties in the profile in {{settings.xml}}, they are
ignored. The profile is activated in {{activeProfiles}} element.
It looks, than only m-site-p ignores properties defined in the
{{settings.xml}} file. m-deploy-p recognizes properties as I expected
(distribution management section for articats deployment is configured in
similar way to site deployment).
--
Marcin Kuthan
Maven For Enterprise - http://code.google.com/p/m4enterprise/
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-611) property interpolation in systemPath during site build is not working
[ https://jira.codehaus.org/browse/MSITE-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated MSITE-611: Fix Version/s: 3.1 property interpolation in systemPath during site build is not working - Key: MSITE-611 URL: https://jira.codehaus.org/browse/MSITE-611 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: multi module, property interpolation Affects Versions: 3.0 Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: /home/marcel/apache-maven-3.0.3 Java version: 1.6.0_24, vendor: Sun Microsystems Inc. Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: de_DE, platform encoding: UTF-8 OS name: linux, version: 2.6.32-5-amd64, arch: amd64, family: unix Reporter: Marcel Patzlaff Fix For: 3.1 Attachments: output-3.0-beta-3.log, output.log, testproject.tar.gz, test-settings.xml I have specified a property in my settings.xml (see attachment test-settings.xml) that points to a directory. This property is used to specify the systemPath of a system dependency in my child module. Everything works (compilation, packaging, etc) except building the site. Calling mvn clean site on the parent project results in an error (see attachment output.log). Invoking the same line in the child project still gives the error message but the site-build itself succeeds. Please find the working project tree attached in testproject.tar.gz. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-610) No doc for reportPlugins in main goal docs
[ https://jira.codehaus.org/browse/MSITE-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated MSITE-610: Fix Version/s: 3.1 Assignee: Olivier Lamy There is a rudimentary comment in AbstractSiteRenderingMojo now, but it is not clear still how to use this. Olivier: is this really supposed to be user-settable? If yes, please provide an example. No doc for reportPlugins in main goal docs -- Key: MSITE-610 URL: https://jira.codehaus.org/browse/MSITE-610 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: documentation Affects Versions: 3.0 Reporter: Benson Margulies Assignee: Olivier Lamy Fix For: 3.1 Under site:site, 'reportPlugins' is content-free. I'd recommend at least a link to the page http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-608) aggregating breadcrumb behavior disappears in the presence of a menu in the parent
[
https://jira.codehaus.org/browse/MSITE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl updated MSITE-608:
Fix Version/s: 3.1
aggregating breadcrumb behavior disappears in the presence of a menu in the
parent
--
Key: MSITE-608
URL: https://jira.codehaus.org/browse/MSITE-608
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Components: multi module
Affects Versions: 3.0
Reporter: Benson Margulies
Fix For: 3.1
Attachments: site-breadcrumb-inheritance.jar
This may turn out to belong in Doxia. I don't know.
The attached project consists of an aggregating project and its module. The
breadcrumbs in the module are, I claim, wrong -- they lack the breadcrumb to
visit the parent.
If you remove this menu:
{code}
menu name=tc
item name=Home href=index.html/
/menu
{code}
from the parent's src/site/site.xml, all is well. Once it's here, the
parent-level breadcrumb is omitted.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-607) no documentation for breadcrumbs in the doc of site.xml
[ https://jira.codehaus.org/browse/MSITE-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated MSITE-607: Fix Version/s: 3.1 no documentation for breadcrumbs in the doc of site.xml --- Key: MSITE-607 URL: https://jira.codehaus.org/browse/MSITE-607 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: documentation Affects Versions: 3.0 Reporter: Benson Margulies Fix For: 3.1 Some information from http://www.sonatype.com/books/mvnref-book/reference/site-generation-sect-tips-tricks.html#site-generation-add-breadcumbs should be on http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-603) ClassNotFoundException on site:site when validating XML input documents
[
https://jira.codehaus.org/browse/MSITE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl updated MSITE-603:
Fix Version/s: 3.1
Assignee: Lukas Theussl
ClassNotFoundException on site:site when validating XML input documents
---
Key: MSITE-603
URL: https://jira.codehaus.org/browse/MSITE-603
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Affects Versions: 3.0
Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
Java version: 1.6.0_20, vendor: Sun Microsystems Inc.
Default locale: en_CA, platform encoding: UTF-8
OS name: linux, version: 2.6.32-33-generic, arch: i386, family: unix
Reporter: Andreas Sewe
Assignee: Lukas Theussl
Fix For: 3.1
Attachments: testcase.tar.gz
When setting {{validate}} to {{true}} the 3.0 release of the
{{maven-site-plugin}} fails with a {{ClassNotFoundException}} (sample
project included):
{quote}
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:125)
... 20 more
Caused by: java.lang.NoClassDefFoundError:
org/apache/commons/logging/LogFactory
at
org.apache.http.impl.client.AbstractHttpClient.init(AbstractHttpClient.java:159)
at
org.apache.http.impl.client.DefaultHttpClient.init(DefaultHttpClient.java:178)
at
org.apache.maven.doxia.parser.AbstractXmlParser$CachedFileEntityResolver.toByteArray(AbstractXmlParser.java:796)
at
org.apache.maven.doxia.parser.AbstractXmlParser$CachedFileEntityResolver.resolveEntity(AbstractXmlParser.java:738)
at org.apache.xerces.util.EntityResolverWrapper.resolveEntity(Unknown
Source)
at org.apache.xerces.impl.XMLEntityManager.resolveEntity(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaLoader.resolveDocument(Unknown
Source)
at
org.apache.xerces.impl.xs.XMLSchemaValidator.findSchemaGrammar(Unknown Source)
at
org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown
Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at
org.apache.maven.doxia.util.XmlValidator.validate(XmlValidator.java:108)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.validate(DefaultSiteRenderer.java:831)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:365)
at
org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:317)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 20 more
Caused by: java.lang.ClassNotFoundException:
org.apache.commons.logging.LogFactory
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230)
... 47 more
{quote}
This problem only shows up if there are XML input documents (FML, XDoc)
present to be validated.
It doesn't occur with 3.0-beta-3 instead of 3.0.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-602) The staged site is deployed to the wrong place
[
https://jira.codehaus.org/browse/MSITE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl updated MSITE-602:
Fix Version/s: 3.1
The staged site is deployed to the wrong place
--
Key: MSITE-602
URL: https://jira.codehaus.org/browse/MSITE-602
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Components: site:stage(-deploy)
Affects Versions: 2.3, 3.0
Reporter: Dennis Lundberg
Assignee: Dennis Lundberg
Fix For: 3.1
When running 'mvn site:stage-deploy' the site is deployed to the wrong place.
Below is the output from a test run performed on the Checkstyle Plugin
project.
{noformat}
[INFO] --- maven-site-plugin:3.0:stage-deploy (default-cli) @
maven-checkstyle-plugin ---
[INFO] Using this server ID for stage deploy: apache.website
[INFO] Using this base URL for stage deploy:
scp://people.apache.org/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT
[INFO] Parent project loaded from repository:
org.apache.maven.plugins:maven-plugins:pom:21
[INFO] Parent project loaded from repository:
org.apache.maven:maven-parent:pom:20
[INFO] Parent project loaded from repository: org.apache:apache:pom:9
: Keyboard interactive required, supplied password is ignored
Password: :
scp://people.apache.org/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/
- Session: Opened
[INFO] Pushing
G:\apache\maven\trunks\plugins\maven-checkstyle-plugin\target\site
[INFO] to
scp://people.apache.org/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/plugins/maven-checkstyle-plugin
Executing command: mkdir -p
/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/plugins/maven-checkstyle-plugin
Executing command: mkdir -p
/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/plugins/maven-checkstyle-plugin
Executing command: scp -t
/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/plugins/maven-checkstyle-plugin/wagon592489540427231356.zip
Uploading: plugins/maven-checkstyle-plugin/wagon592489540427231356.zip to
scp://people.apache.org/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/
###
Transfer finished. 224640 bytes copied in 1.699 seconds
Executing command: cd
/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/plugins/maven-checkstyle-plugin;
unzip -q -o wagon592489540427231356.zip; rm -f wagon592489540427231356.zip
Executing command: chmod -Rf g+w,a+rX
/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/
scp://people.apache.org/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/
- Session: Disconnecting
scp://people.apache.org/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/
- Session: Disconnected
{noformat}
Notice how it gets deployed to
{noformat}
/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/plugins/maven-checkstyle-plugin/
{noformat}
instead of
{noformat}
/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-601) Period added to URL prevents proper cloning with Mercurial
[
https://jira.codehaus.org/browse/MSITE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl updated MSITE-601:
Fix Version/s: 3.1
Period added to URL prevents proper cloning with Mercurial
--
Key: MSITE-601
URL: https://jira.codehaus.org/browse/MSITE-601
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Components: site:deploy
Affects Versions: 3.0-beta-3
Environment: Javac 7 on Fedora Linux 15, Mercurial 1.9
Reporter: Leon Blakey
Priority: Critical
Fix For: 3.1
I deploy my Maven site over Mercurial on Google Code. I use this configuration
{code:xml}distributionManagement
!--Site deploy repository--
site
idMYPROJECT.googlecode.com/id
urlscm:hg:https://code.google.com/p/MYPROJECT.site//url
/site
/distributionManagement{code}
And a standard server in settings.xml
{code:xml}servers
server
idMYPROJECT.googlecode.com/id
usernameUSERNAME/username
passwordPASSWORD/password
/server
/servers{code}
However when running site:deploy it decides that it should add a dot to the
URL, meaning it tries to execute this command
EXECUTING: /bin/sh -c cd /tmp hg clone -r tip
https://USERNAME:passw...@code.google.com/p/MYPROJECT.site//.
/tmp/wagon-scm1348091978.checkout
Which on Google and other repositories gives a 404 since the file . (look at
the end of the URL) doesn't exist. Why is that period there? Is it coming
from Maven Site or the Mercurial plugin (I'm assuming here)? Can it get
removed
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-600) site plugin 3.0 does not permit a child to fully override parent site deployment URL
[ https://jira.codehaus.org/browse/MSITE-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280015#comment-280015 ] Lukas Theussl commented on MSITE-600: - Jenkins seems happy now, so I'm closing this. I also merged the fix back to the 2.4 branch ([r1176233|http://svn.apache.org/viewvc?rev=1176233view=rev]) and deployed a snapshot, if someone wants to test. site plugin 3.0 does not permit a child to fully override parent site deployment URL Key: MSITE-600 URL: https://jira.codehaus.org/browse/MSITE-600 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: site:deploy Affects Versions: 2.3, 3.0 Reporter: Benson Margulies Assignee: Lukas Theussl Fix For: 2.4, 3.1 Attachments: child-pom.xml, muddle.tar, parent-pom.xml The test cases here has a parent with a a distributionManagement/site/url, and then a child which overrides it with an absolute URL. Except that the override does not work ... or, at least, looks quite peculiar. the parent is file:///tmp/bloop the child is scp://localhost:/tmp/blop and the result is [INFO] Error uploading site Embedded error: Could not make directory '/tmp/bloop/../../Users/benson/asf/mvn/site-interp-muddle/child/scp:/localhost:/tmp/blop'. [INFO] --- -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-600) site plugin 3.0 does not permit a child to fully override parent site deployment URL
[ https://jira.codehaus.org/browse/MSITE-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MSITE-600. --- Resolution: Fixed site plugin 3.0 does not permit a child to fully override parent site deployment URL Key: MSITE-600 URL: https://jira.codehaus.org/browse/MSITE-600 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: site:deploy Affects Versions: 2.3, 3.0 Reporter: Benson Margulies Assignee: Lukas Theussl Fix For: 3.1 Attachments: child-pom.xml, muddle.tar, parent-pom.xml The test cases here has a parent with a a distributionManagement/site/url, and then a child which overrides it with an absolute URL. Except that the override does not work ... or, at least, looks quite peculiar. the parent is file:///tmp/bloop the child is scp://localhost:/tmp/blop and the result is [INFO] Error uploading site Embedded error: Could not make directory '/tmp/bloop/../../Users/benson/asf/mvn/site-interp-muddle/child/scp:/localhost:/tmp/blop'. [INFO] --- -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-600) site plugin 3.0 does not permit a child to fully override parent site deployment URL
[ https://jira.codehaus.org/browse/MSITE-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated MSITE-600: Fix Version/s: 2.4 site plugin 3.0 does not permit a child to fully override parent site deployment URL Key: MSITE-600 URL: https://jira.codehaus.org/browse/MSITE-600 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: site:deploy Affects Versions: 2.3, 3.0 Reporter: Benson Margulies Assignee: Lukas Theussl Fix For: 2.4, 3.1 Attachments: child-pom.xml, muddle.tar, parent-pom.xml The test cases here has a parent with a a distributionManagement/site/url, and then a child which overrides it with an absolute URL. Except that the override does not work ... or, at least, looks quite peculiar. the parent is file:///tmp/bloop the child is scp://localhost:/tmp/blop and the result is [INFO] Error uploading site Embedded error: Could not make directory '/tmp/bloop/../../Users/benson/asf/mvn/site-interp-muddle/child/scp:/localhost:/tmp/blop'. [INFO] --- -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-596) inheritedReports IT fails
[ https://jira.codehaus.org/browse/MSITE-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated MSITE-596: Fix Version/s: 3.1 If this cannot get fixed for 3.1, we need to document the different behaviour. inheritedReports IT fails - Key: MSITE-596 URL: https://jira.codehaus.org/browse/MSITE-596 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: inheritance, Maven 3 Affects Versions: 3.0-beta-3 Reporter: Herve Boutemy Fix For: 3.1 as discovered in MSITE-595: - with M2, each report is added: child has 2 reports generated = index+summary - with M3, each report replaces previous one: child has 1 report = summary What is the expected behaviour? I'd say M2 is buggy, since POM inheritance logic usually replaces instead adding Should we try to stick with M2 behaviour? (if feasible, I still didn't check) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MWAR-263) filteringDeploymentDescriptors does not filter all deployment descriptors
filteringDeploymentDescriptors does not filter all deployment descriptors - Key: MWAR-263 URL: https://jira.codehaus.org/browse/MWAR-263 Project: Maven 2.x WAR Plugin Issue Type: Bug Affects Versions: 2.1.1 Reporter: Xin Zoo I have set the optional configuration parameter filteringDeploymentDescriptors to true. It only filters web.xml. But i believe it should also filter the provider specific descriptors like jboss-web.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-607) no documentation for breadcrumbs in the doc of site.xml
[ https://jira.codehaus.org/browse/MSITE-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MSITE-607. --- Resolution: Fixed Assignee: Lukas Theussl Done in [r1176301|http://svn.apache.org/viewvc?rev=1176301view=rev]. no documentation for breadcrumbs in the doc of site.xml --- Key: MSITE-607 URL: https://jira.codehaus.org/browse/MSITE-607 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: documentation Affects Versions: 3.0 Reporter: Benson Margulies Assignee: Lukas Theussl Fix For: 3.1 Some information from http://www.sonatype.com/books/mvnref-book/reference/site-generation-sect-tips-tricks.html#site-generation-add-breadcumbs should be on http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-603) ClassNotFoundException on site:site when validating XML input documents
[
https://jira.codehaus.org/browse/MSITE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280040#comment-280040
]
Lukas Theussl commented on MSITE-603:
-
This was introduced with
[r991009|http://svn.apache.org/viewvc?view=revisionrevision=991009], not sure
why the commons-logging exclusion was needed.
ClassNotFoundException on site:site when validating XML input documents
---
Key: MSITE-603
URL: https://jira.codehaus.org/browse/MSITE-603
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Affects Versions: 3.0
Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
Java version: 1.6.0_20, vendor: Sun Microsystems Inc.
Default locale: en_CA, platform encoding: UTF-8
OS name: linux, version: 2.6.32-33-generic, arch: i386, family: unix
Reporter: Andreas Sewe
Assignee: Lukas Theussl
Fix For: 3.1
Attachments: testcase.tar.gz
When setting {{validate}} to {{true}} the 3.0 release of the
{{maven-site-plugin}} fails with a {{ClassNotFoundException}} (sample
project included):
{quote}
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:125)
... 20 more
Caused by: java.lang.NoClassDefFoundError:
org/apache/commons/logging/LogFactory
at
org.apache.http.impl.client.AbstractHttpClient.init(AbstractHttpClient.java:159)
at
org.apache.http.impl.client.DefaultHttpClient.init(DefaultHttpClient.java:178)
at
org.apache.maven.doxia.parser.AbstractXmlParser$CachedFileEntityResolver.toByteArray(AbstractXmlParser.java:796)
at
org.apache.maven.doxia.parser.AbstractXmlParser$CachedFileEntityResolver.resolveEntity(AbstractXmlParser.java:738)
at org.apache.xerces.util.EntityResolverWrapper.resolveEntity(Unknown
Source)
at org.apache.xerces.impl.XMLEntityManager.resolveEntity(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaLoader.resolveDocument(Unknown
Source)
at
org.apache.xerces.impl.xs.XMLSchemaValidator.findSchemaGrammar(Unknown Source)
at
org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown
Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at
org.apache.maven.doxia.util.XmlValidator.validate(XmlValidator.java:108)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.validate(DefaultSiteRenderer.java:831)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:365)
at
org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:317)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 20 more
Caused by: java.lang.ClassNotFoundException:
org.apache.commons.logging.LogFactory
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230)
... 47 more
{quote}
This problem only shows up if there are XML input documents (FML, XDoc)
present to be validated.
It doesn't occur with 3.0-beta-3 instead of 3.0.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-603) ClassNotFoundException on site:site when validating XML input documents
[
https://jira.codehaus.org/browse/MSITE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl closed MSITE-603.
---
Resolution: Fixed
Fixed: [r1176337|http://svn.apache.org/viewvc?rev=1176337view=rev]
ClassNotFoundException on site:site when validating XML input documents
---
Key: MSITE-603
URL: https://jira.codehaus.org/browse/MSITE-603
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Affects Versions: 3.0
Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
Java version: 1.6.0_20, vendor: Sun Microsystems Inc.
Default locale: en_CA, platform encoding: UTF-8
OS name: linux, version: 2.6.32-33-generic, arch: i386, family: unix
Reporter: Andreas Sewe
Assignee: Lukas Theussl
Fix For: 3.1
Attachments: testcase.tar.gz
When setting {{validate}} to {{true}} the 3.0 release of the
{{maven-site-plugin}} fails with a {{ClassNotFoundException}} (sample
project included):
{quote}
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:125)
... 20 more
Caused by: java.lang.NoClassDefFoundError:
org/apache/commons/logging/LogFactory
at
org.apache.http.impl.client.AbstractHttpClient.init(AbstractHttpClient.java:159)
at
org.apache.http.impl.client.DefaultHttpClient.init(DefaultHttpClient.java:178)
at
org.apache.maven.doxia.parser.AbstractXmlParser$CachedFileEntityResolver.toByteArray(AbstractXmlParser.java:796)
at
org.apache.maven.doxia.parser.AbstractXmlParser$CachedFileEntityResolver.resolveEntity(AbstractXmlParser.java:738)
at org.apache.xerces.util.EntityResolverWrapper.resolveEntity(Unknown
Source)
at org.apache.xerces.impl.XMLEntityManager.resolveEntity(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaLoader.resolveDocument(Unknown
Source)
at
org.apache.xerces.impl.xs.XMLSchemaValidator.findSchemaGrammar(Unknown Source)
at
org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown
Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at
org.apache.maven.doxia.util.XmlValidator.validate(XmlValidator.java:108)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.validate(DefaultSiteRenderer.java:831)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:365)
at
org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:317)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 20 more
Caused by: java.lang.ClassNotFoundException:
org.apache.commons.logging.LogFactory
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230)
... 47 more
{quote}
This problem only shows up if there are XML input documents (FML, XDoc)
present to be validated.
It doesn't occur with 3.0-beta-3 instead of 3.0.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DOXIATOOLS-15) snippet macro with file reference cause editor failure
[
https://jira.codehaus.org/browse/DOXIATOOLS-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed DOXIATOOLS-15.
-
Resolution: Fixed
Assignee: Vincent Siveton
Fixed in r1176346
you need to add ${project.basedir}/src... or ${basedir}/src...
snippet macro with file reference cause editor failure
--
Key: DOXIATOOLS-15
URL: https://jira.codehaus.org/browse/DOXIATOOLS-15
Project: Maven Doxia Tools
Issue Type: Bug
Components: Doxia Eclipse Editor
Reporter: Herve Boutemy
Assignee: Vincent Siveton
Priority: Minor
if you open following APT file:
http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-core/src/site/apt/lifecycles.apt?revision=1169931view=markup
you'll see the editing error marker.
And it is not possible to View the rendering: Doxia Converter Exception:
ParseException: Unable to execute macro in the APT document
It seems that relative path calculation is not done the same way in the
editor than when run with mvn CLI
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-602) The staged site is deployed to the wrong place
[
https://jira.codehaus.org/browse/MSITE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280044#comment-280044
]
Lukas Theussl commented on MSITE-602:
-
I will review this, there might be an easier fix. It would help to have a test
case as none of our ITs have caught this.
The staged site is deployed to the wrong place
--
Key: MSITE-602
URL: https://jira.codehaus.org/browse/MSITE-602
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Components: site:stage(-deploy)
Affects Versions: 2.3, 3.0
Reporter: Dennis Lundberg
Assignee: Dennis Lundberg
Fix For: 3.1
When running 'mvn site:stage-deploy' the site is deployed to the wrong place.
Below is the output from a test run performed on the Checkstyle Plugin
project.
{noformat}
[INFO] --- maven-site-plugin:3.0:stage-deploy (default-cli) @
maven-checkstyle-plugin ---
[INFO] Using this server ID for stage deploy: apache.website
[INFO] Using this base URL for stage deploy:
scp://people.apache.org/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT
[INFO] Parent project loaded from repository:
org.apache.maven.plugins:maven-plugins:pom:21
[INFO] Parent project loaded from repository:
org.apache.maven:maven-parent:pom:20
[INFO] Parent project loaded from repository: org.apache:apache:pom:9
: Keyboard interactive required, supplied password is ignored
Password: :
scp://people.apache.org/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/
- Session: Opened
[INFO] Pushing
G:\apache\maven\trunks\plugins\maven-checkstyle-plugin\target\site
[INFO] to
scp://people.apache.org/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/plugins/maven-checkstyle-plugin
Executing command: mkdir -p
/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/plugins/maven-checkstyle-plugin
Executing command: mkdir -p
/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/plugins/maven-checkstyle-plugin
Executing command: scp -t
/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/plugins/maven-checkstyle-plugin/wagon592489540427231356.zip
Uploading: plugins/maven-checkstyle-plugin/wagon592489540427231356.zip to
scp://people.apache.org/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/
###
Transfer finished. 224640 bytes copied in 1.699 seconds
Executing command: cd
/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/plugins/maven-checkstyle-plugin;
unzip -q -o wagon592489540427231356.zip; rm -f wagon592489540427231356.zip
Executing command: chmod -Rf g+w,a+rX
/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/
scp://people.apache.org/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/
- Session: Disconnecting
scp://people.apache.org/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/
- Session: Disconnected
{noformat}
Notice how it gets deployed to
{noformat}
/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/plugins/maven-checkstyle-plugin/
{noformat}
instead of
{noformat}
/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions
[ https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280051#comment-280051 ] Frank Ulbricht commented on MNG-3092: - After converting our complete release process to Maven we have stumbled over this problem. Because of the sheer number of dependencies we are forced to use version ranges. But now some projects refering to SNAPSHOTs and we are not able to release anything without touching all the POMs. So whatever solution you prefer, it will be welcome. But it seems the problem is to agree on a solution. So let me add a vote for the [1.0.0,1.2.0-SNAPSHOT) approach... Version ranges with non-snapshot bounds can contain snapshot versions - Key: MNG-3092 URL: https://jira.codehaus.org/browse/MNG-3092 Project: Maven 2 3 Issue Type: Bug Components: Dependencies Reporter: Mark Hobson Attachments: MNG-3092.patch Contrary to the 2.0 design docs: Resolution of dependency ranges should not resolve to a snapshot (development version) unless it is included as an explicit boundary. -- from http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-Incorporating%7B%7BSNAPSHOT%7D%7Dversionsintothespecification The following is equates to true: VersionRange.createFromVersionSpec( [1.0,1.1] ).containsVersion( new DefaultArtifactVersion( 1.1-SNAPSHOT ) ) The attached patch only allows snapshot versions to be contained in a range if they are equal to one of the boundaries. Note that this is a strict equality, so [1.0,1.2-SNAPSHOT] will not contain 1.1-SNAPSHOT. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-5073) ProjectBuilder.build(File,ProjectBuildingRequest) returns null project if dependency version info is missing
[
https://jira.codehaus.org/browse/MNG-5073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-5073.
--
Resolution: Fixed
Fix Version/s: 3.0.4
Assignee: Benjamin Bentmann
Fixed in
[r1176414|http://svn.apache.org/viewvc?view=revisionrevision=1176414]. The
{{ProjectBuildingException}} can now be queried for the partial
{{ProjectBuildingResult}} and its {{MavenProject}}.
ProjectBuilder.build(File,ProjectBuildingRequest) returns null project if
dependency version info is missing
Key: MNG-5073
URL: https://jira.codehaus.org/browse/MNG-5073
Project: Maven 2 3
Issue Type: Improvement
Components: Embedding
Affects Versions: 3.0.2
Reporter: Igor Fedorenko
Assignee: Benjamin Bentmann
Fix For: 3.0.4
ProjectBuilder.build(File,ProjectBuildingRequest) returns null MavenProject
instance for the following pom.xml even when using
ModelBuildingRequest.VALIDATION_LEVEL_MINIMAL. Expected/desired behaviour is
to return MavenProject instance populated with all good/resolved dependencies
and information about all bad/missing dependencies in
MavenExecutionResult.getExceptions and/or
MavenExecutionResult.getDependencyResolutionResult.
{noformat}
project
modelVersion4.0.0/modelVersion
groupIdxxx/groupId
artifactIdm01/artifactId
version0.0.1-SNAPSHOT/version
dependencies
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
/dependency
/dependencies
/project
{noformat}
Original m2e bugreport https://bugs.eclipse.org/bugs/show_bug.cgi?id=343568
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCHECKSTYLE-62) Support aggregated reports in a multi-modules project
[ https://jira.codehaus.org/browse/MCHECKSTYLE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Petrelli updated MCHECKSTYLE-62: Attachment: checkstyle-aggregate.diff This is a fast implementation of the aggregate parameter. It was written in a hurry so no test. WDYT? Support aggregated reports in a multi-modules project - Key: MCHECKSTYLE-62 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-62 Project: Maven 2.x Checkstyle Plugin Issue Type: New Feature Reporter: Damien Lecan Attachments: checkstyle-aggregate.diff It would be nice if checkstyle plugin could build just one report in a multi-modules project. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-613) Regression in 3.0 - site:stage Could not resolve dependencies for project on multi-module project
Regression in 3.0 - site:stage Could not resolve dependencies for project on multi-module project --- Key: MSITE-613 URL: https://jira.codehaus.org/browse/MSITE-613 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: multi module Affects Versions: 3.0 Reporter: Miguel Almeida Attachments: parentA.zip Running the attached testcase, which has: parentA:| |module1 |module2 1) Run: mvn site:site 2) Run mvn site:stage 2) fails with [ERROR] Failed to execute goal on project module2: Could not resolve dependencies for project org.example:module2:jar:1.0.0-SNAPSHOT: Failure to find org.example:module1:jar:1.0.0-SNAPSHOT in http://192.178.1.120:8082/archiva/repository/my-internal/ was cached in the local repository, resolution will not be reattempted until the update interval of my-internal has elapsed or updates are forced 3) Change plugin version to 3.0-beta-3 4) Repeat 1 and 2 site:stage will run successfully -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-613) Regression in 3.0 - site:stage Could not resolve dependencies for project on multi-module project
[ https://jira.codehaus.org/browse/MSITE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280084#comment-280084 ] Miguel Almeida commented on MSITE-613: -- The 2nd issue is, on the same test case: After 4 (site:stage with 3.0-beta3): EXPECTED: The aggregate result of cobertura in parentA (ie, cobertura report with the aggregate reports of module1 and module2) ACTUAL: No report and the staging link points to file:///home/user/workspaces/impo/parentA/target/staging/localhost/home/user/mysite/cobertura/index.html You can compare this the result of running the mvn cobertura:cobertura goal on parentA: you get a site/cobertura directory in the target with the correct report. Is this an incompatibility of versions? Feel free to move this 2nd issue to a separate bug. Regression in 3.0 - site:stage Could not resolve dependencies for project on multi-module project --- Key: MSITE-613 URL: https://jira.codehaus.org/browse/MSITE-613 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: multi module Affects Versions: 3.0 Reporter: Miguel Almeida Attachments: parentA.zip Running the attached testcase, which has: parentA:| |module1 |module2 1) Run: mvn site:site 2) Run mvn site:stage 2) fails with [ERROR] Failed to execute goal on project module2: Could not resolve dependencies for project org.example:module2:jar:1.0.0-SNAPSHOT: Failure to find org.example:module1:jar:1.0.0-SNAPSHOT in http://192.178.1.120:8082/archiva/repository/my-internal/ was cached in the local repository, resolution will not be reattempted until the update interval of my-internal has elapsed or updates are forced 3) Change plugin version to 3.0-beta-3 4) Repeat 1 and 2 site:stage will run successfully -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-613) Regression in 3.0 - site:stage Could not resolve dependencies for project on multi-module project
[ https://jira.codehaus.org/browse/MSITE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280085#comment-280085 ] Miguel Almeida commented on MSITE-613: -- Maven version: 3.0.3 Regression in 3.0 - site:stage Could not resolve dependencies for project on multi-module project --- Key: MSITE-613 URL: https://jira.codehaus.org/browse/MSITE-613 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: multi module Affects Versions: 3.0 Reporter: Miguel Almeida Attachments: parentA.zip Running the attached testcase, which has: parentA:| |module1 |module2 1) Run: mvn site:site 2) Run mvn site:stage 2) fails with [ERROR] Failed to execute goal on project module2: Could not resolve dependencies for project org.example:module2:jar:1.0.0-SNAPSHOT: Failure to find org.example:module1:jar:1.0.0-SNAPSHOT in http://192.178.1.120:8082/archiva/repository/my-internal/ was cached in the local repository, resolution will not be reattempted until the update interval of my-internal has elapsed or updates are forced 3) Change plugin version to 3.0-beta-3 4) Repeat 1 and 2 site:stage will run successfully -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-5178) Substitute environment variable M2_HOME by M3_HOME
Substitute environment variable M2_HOME by M3_HOME
--
Key: MNG-5178
URL: https://jira.codehaus.org/browse/MNG-5178
Project: Maven 2 3
Issue Type: Wish
Components: Command Line
Reporter: Oliver B. Fischer
Priority: Minor
Maven 3 uses the environment variable {{M2_HOME}} to point to it's installation
directory. This variable should be replaced by {{M3_HOME}} to allow users to
have parallel installations of Maven 2 and Maven 3 without any special handling
of the environment variable {{M2_HOME}}.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (ARCHETYPE-384) support for multi-module projects modules are part of profiles
support for multi-module projects modules are part of profiles
--
Key: ARCHETYPE-384
URL: https://jira.codehaus.org/browse/ARCHETYPE-384
Project: Maven Archetype
Issue Type: New Feature
Components: Creator
Affects Versions: 2.1
Environment: Windows
Reporter: tanmoy banerjee
My project structure is shown as below:
{code:xml}
project
modules
modulesample-domain/module
modulesample-data/module
/modules
profiles
profileidit/id
modules
modulesample-it/modules
/modules
/profile
profiles
/project
{code}
the idea is to have the module sample-it only when it is built with When this
is the scenario, and i run the command create-from-project, the
archetype-metadata.xml does not include the sample-it module, nor it filters
the files in that module.
archetype-metadata.xml
{code:xml}
archetype-descriptor
modules
module id=${rootArtifactId}-domain dir=__rootArtifactId__-domain
name=${rootArtifactId}-domain/module
module id=${rootArtifactId}-data dir=__rootArtifactId__-data
name=${rootArtifactId}-data/module
/modules
/archetype-descriptor
{code}
The sample-it module is not inluded in this, and it satys in the pom as is...
and none of the files in the module is filtered. Is this my configuration
issue, and what is the configuration to do this. Otherwise, it will be a great
feature to have this feature.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (ARCHETYPE-385) support for multi-module projects modules which are part of profiles
support for multi-module projects modules which are part of profiles
Key: ARCHETYPE-385
URL: https://jira.codehaus.org/browse/ARCHETYPE-385
Project: Maven Archetype
Issue Type: New Feature
Components: Creator
Affects Versions: 2.1
Environment: Windows
Reporter: tanmoy banerjee
My project structure is shown as below:
{code:xml}
project
modules
modulesample-domain/module
modulesample-data/module
/modules
profiles
profileidit/id
modules
modulesample-it/modules
/modules
/profile
profiles
/project
{code}
the idea is to have the module sample-it only when it is built with When this
is the scenario, and i run the command create-from-project, the
archetype-metadata.xml does not include the sample-it module, nor it filters
the files in that module.
archetype-metadata.xml
{code:xml}
archetype-descriptor
modules
module id=${rootArtifactId}-domain dir=__rootArtifactId__-domain
name=${rootArtifactId}-domain/module
module id=${rootArtifactId}-data dir=__rootArtifactId__-data
name=${rootArtifactId}-data/module
/modules
/archetype-descriptor
{code}
The sample-it module is not inluded in this, and it satys in the pom as is...
and none of the files in the module is filtered. Is this my configuration
issue, and what is the configuration to do this. Otherwise, it will be a great
feature to have this feature.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (ARCHETYPE-384) support for multi-module projects modules are part of profiles
[
https://jira.codehaus.org/browse/ARCHETYPE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
tanmoy banerjee closed ARCHETYPE-384.
-
Resolution: Duplicate
updated the title and duplicated it
support for multi-module projects modules are part of profiles
--
Key: ARCHETYPE-384
URL: https://jira.codehaus.org/browse/ARCHETYPE-384
Project: Maven Archetype
Issue Type: New Feature
Components: Creator
Affects Versions: 2.1
Environment: Windows
Reporter: tanmoy banerjee
My project structure is shown as below:
{code:xml}
project
modules
modulesample-domain/module
modulesample-data/module
/modules
profiles
profileidit/id
modules
modulesample-it/modules
/modules
/profile
profiles
/project
{code}
the idea is to have the module sample-it only when it is built with When
this is the scenario, and i run the command create-from-project, the
archetype-metadata.xml does not include the sample-it module, nor it filters
the files in that module.
archetype-metadata.xml
{code:xml}
archetype-descriptor
modules
module id=${rootArtifactId}-domain dir=__rootArtifactId__-domain
name=${rootArtifactId}-domain/module
module id=${rootArtifactId}-data dir=__rootArtifactId__-data
name=${rootArtifactId}-data/module
/modules
/archetype-descriptor
{code}
The sample-it module is not inluded in this, and it satys in the pom as is...
and none of the files in the module is filtered. Is this my configuration
issue, and what is the configuration to do this. Otherwise, it will be a
great feature to have this feature.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MDEP-327) Quiet mode for downloads of artifacts
Quiet mode for downloads of artifacts - Key: MDEP-327 URL: https://jira.codehaus.org/browse/MDEP-327 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Components: resolve Reporter: Paul Hammant Assignee: Brian Fox Priority: Minor Especially for Build-Machines, could we have less noise on the output of downloaded artifacts: 1K downloaded (json-20080701.pom) Downloading: http://mynexus:8080/nexus/content/groups/public/org/apache/httpcomponents/httpclient/4.0.2/httpclient-4.0.2.pom 4/7K 7/7K 7K downloaded (httpclient-4.0.2.pom) Downloading: http://mynexus:8080/nexus/content/groups/public/org/apache/httpcomponents/httpcomponents-client/4.0.2/httpcomponents-client-4.0.2.pom 4/8K 8/8K 8/8K 8K downloaded (httpcomponents-client-4.0.2.pom) Downloading: http://mynexus:8080/nexus/content/groups/public/org/apache/httpcomponents/project/4.1/project-4.1.pom 4/15K 8/15K 12/15K 15/15K -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEP-327) Quiet mode for downloads of artifacts
[ https://jira.codehaus.org/browse/MDEP-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280109#comment-280109 ] Brett Porter commented on MDEP-327: --- if you run Maven with the --batch-mode (or -B) argument the progress indicator will be omitted. Quiet mode for downloads of artifacts - Key: MDEP-327 URL: https://jira.codehaus.org/browse/MDEP-327 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Components: resolve Reporter: Paul Hammant Assignee: Brian Fox Priority: Minor Especially for Build-Machines, could we have less noise on the output of downloaded artifacts: 1K downloaded (json-20080701.pom) Downloading: http://mynexus:8080/nexus/content/groups/public/org/apache/httpcomponents/httpclient/4.0.2/httpclient-4.0.2.pom 4/7K 7/7K 7K downloaded (httpclient-4.0.2.pom) Downloading: http://mynexus:8080/nexus/content/groups/public/org/apache/httpcomponents/httpcomponents-client/4.0.2/httpcomponents-client-4.0.2.pom 4/8K 8/8K 8/8K 8K downloaded (httpcomponents-client-4.0.2.pom) Downloading: http://mynexus:8080/nexus/content/groups/public/org/apache/httpcomponents/project/4.1/project-4.1.pom 4/15K 8/15K 12/15K 15/15K -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEAR-143) Plugin does not respect transitive dependency scopes properly
Plugin does not respect transitive dependency scopes properly
-
Key: MEAR-143
URL: https://jira.codehaus.org/browse/MEAR-143
Project: Maven 2.x Ear Plugin
Issue Type: Bug
Affects Versions: 2.6
Reporter: Laird Nelson
The [Introduction to the Dependency Mechanism
page|http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope]
has a handy table for deciding what to do with transitive dependencies and
various scopes. The Maven ear plugin does not honor it in all cases.
Suppose I have a {{.jar}} file. Its name is {{b.jar}}. It declares a
{{runtime}} dependency on {{a.jar}}.
Suppose now I have an {{.ear}} project. It declares a {{compile}} scope
dependency on {{b.jar}}.
By the rules of the chart, {{a.jar}} should end up being a {{runtime}}
dependency (transitively) of the {{.ear}}, and should be included in the
{{lib}} directory. It is not.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
