[jira] Commented: (MNG-3269) Different builds for ejb-client optional with parent
[ http://jira.codehaus.org/browse/MNG-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112695 ] Stephane Nicoll commented on MNG-3269: -- Are you happy if I provide a way to build the manifest in a more elegant way? Declaring the dependency as provided+optional is such as mess ... I was more thinking of a declarative way of doing this in the war plugin itself, a la ArtifactItem of the dependency plugin. WDYT? > Different builds for ejb-client optional with parent > > > Key: MNG-3269 > URL: http://jira.codehaus.org/browse/MNG-3269 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Tim Reilly > Attachments: MWAR114-maven-war-plugin-2.0.2.patch, > MWAR114-maven-war-plugin-2.0.2.patch, > MWAR114-maven-war-plugin-2.1-alpha-1.patch, mytime.zip > > > When trying to package a j2ee project's ejb-client artifact in the ear /lib > directory the war plugin's optional attribute is ignored if building from the > parent app project. If you build from the parent project you get the > ejb-client packaged in the web-inf/lib directory. If you build the ejb, war, > and ear independently you get the ejb-client packaged in the ear /lib > directory. It seems when run from the parent project the dependency/artifact > doesn't have the optional attribute set. > Perhaps this is b/c the artifact is a project artifact that was attached from > the ejb plugin it is not resolved as optional when the dependency is resolved > from the war project. > Attaching Geronimo's mytime sample with modifications to reproduce the > behavior. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-262) site.xml not inherited if build run from parent
[ http://jira.codehaus.org/browse/MSITE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112702 ] Dennis Lundberg commented on MSITE-262: --- Can you provide us with an example of this? Preferably a complete project with pom.xml and site.xml files. > site.xml not inherited if build run from parent > --- > > Key: MSITE-262 > URL: http://jira.codehaus.org/browse/MSITE-262 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Reporter: Cameron Jones > > I've seen that the site.xml is not being inherited in a module when the build > is run from the parent - when run from the module itself the inheritance > works correctly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-253) NoClassDefFoundError for org/codehaus/plexus/util/xml/XmlStreamReader
[ http://jira.codehaus.org/browse/MSITE-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-253. - Assignee: Dennis Lundberg Resolution: Cannot Reproduce > NoClassDefFoundError for org/codehaus/plexus/util/xml/XmlStreamReader > - > > Key: MSITE-253 > URL: http://jira.codehaus.org/browse/MSITE-253 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 > Environment: Maven version: 2.0.7 > Java version: 1.5.0_11 > OS name: "linux" version: "2.6.20-16-generic" arch: "i386" >Reporter: Ben Tomasini >Assignee: Dennis Lundberg > > When executing mvn site, the build fails with the following error (stack > traces turned on): > [ERROR] BUILD ERROR > [INFO] > > [INFO] Internal error in the plugin manager executing goal > 'org.apache.maven.plugins:maven-site-plugin:2.0-beta-6-SNAPSHOT:site': Unable > to find the mojo > 'org.apache.maven.plugins:maven-site-plugin:2.0-beta-6-SNAPSHOT:site' in the > plugin 'org.apache.maven.plugins:maven-site-plugin' > org/codehaus/plexus/util/xml/XmlStreamReader > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the > plugin manager executing goal > 'org.apache.maven.plugins:maven-site-plugin:2.0-beta-6-SNAPSHOT:site': Unable > to find the mojo > 'org.apache.maven.plugins:maven-site-plugin:2.0-beta-6-SNAPSHOT:site' in the > plugin 'org.apache.maven.plugins:maven-site-plugin' > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:543) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the > mojo 'org.apache.maven.plugins:maven-site-plugin:2.0-beta-6-SNAPSHOT:site' in > the plugin 'org.apache.maven.plugins:maven-site-plugin' > at > org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:571) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:421) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > ... 16 more > Caused by: > org.codehaus.plexus.component.repository.exception.ComponentLookupException: > Unable to lookup component > 'org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-site-plugin:2.0-beta-6-SNAPSHOT:site', > it could not be started > at > org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:339) > at > org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) > at > org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:562) > ... 18 more > Caused by: > org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: > Error starting component > at > org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:109) > at > org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:95) > at > org.codehaus.plexus.component.manage
[jira] Closed: (MSITE-264) Property names with periods are not resolved
[
http://jira.codehaus.org/browse/MSITE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MSITE-264.
-
Assignee: Dennis Lundberg
Resolution: Won't Fix
This will not work because Velocity is used to do the filtering. I have added a
section to the usage documentation about this.
> Property names with periods are not resolved
>
>
> Key: MSITE-264
> URL: http://jira.codehaus.org/browse/MSITE-264
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
>Reporter: Cameron Jones
>Assignee: Dennis Lundberg
>
> I've been trying to get property filtering to work over the site documents as
> specified in http://maven.apache.org/plugins/maven-site-plugin/usage.html by
> appending the '.vm' extension to the appropriate files. The problem is that
> the property filtering doesn't seem to work when the property names contain
> periods for breaking up the context words, for example:
> The works:
> ${currentVersion}
> This doesn't:
> ${current.version}
> For some reason the default maven properties which are always available do
> work even if they have periods, for example this is resolved correctly:
> ${project.version}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1795) upload bundle org.eclipse.jdt:core:3.3.0.771
upload bundle org.eclipse.jdt:core:3.3.0.771 Key: MAVENUPLOAD-1795 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1795 Project: maven-upload-requests Issue Type: Wish Reporter: David Bernard I start previous pom.xml, upgrade the version (and the jar), and inherit from org.eclipse:parent:1. Thanks for your usefull job -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-263) NullPointerException if build run from a module and no url defined in module or parent
[ http://jira.codehaus.org/browse/MSITE-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-263: -- Attachment: MSITE-263.zip I have created a small project that is supposed to reproduce this issue, but it doesn't. I have used version 2.0-beta-6-SNAPSHOT for the test. Please test this in you environment and let us know if it works or not. > NullPointerException if build run from a module and no url defined in module > or parent > -- > > Key: MSITE-263 > URL: http://jira.codehaus.org/browse/MSITE-263 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Reporter: Cameron Jones >Priority: Trivial > Attachments: MSITE-263.zip > > > i've found that you get a null pointer exception if there is no defined > on a module or on it's parent pom. If the build is run from the parent it > works but gives a warning that urls will not be decorated. Adding the > back to the parent fixes the issue. Here's the stacktrace: > java.lang.NullPointerException > at > org.apache.maven.doxia.site.decoration.inheritance.PathUtils.getRelativePath(PathUtils.java:83) > at > org.apache.maven.doxia.site.decoration.inheritance.PathUtils.convertPath(PathUtils.java:43) > at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.convertPath(DefaultDecorationModelInheritanceAssembler.java:334) > at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.resolveLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:255) > at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:277) > at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:192) > at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:83) > at > org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:251) > at > org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:525) > at > org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:464) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:114) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:97) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-146) Version not printing in strapline
[ http://jira.codehaus.org/browse/MSITE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-146. - Assignee: Dennis Lundberg Resolution: Won't Fix > Version not printing in strapline > - > > Key: MSITE-146 > URL: http://jira.codehaus.org/browse/MSITE-146 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-4 > Environment: linux and XP >Reporter: Tim Pizey >Assignee: Dennis Lundberg > > The maven-site.vm has a missing #else, such that the publishDate macro fails > to print the version. > #if ( $version ) > #if ( $version.position ) > #set ( $versionPosition = $version.position ) > #else > #set ( $versionPosition = "left" ) > #end > #end > could become: > #if ( $version ) > #if ( $version.position ) > #set ( $versionPosition = $version.position ) > #else > #set ( $versionPosition = "left" ) > #end > #else > #set ( $version = "unset version" ) > #set ( $versionPosition = "left" ) > #end > which fixes for me. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MNG-3271) does not seem to work
[
http://jira.codehaus.org/browse/MNG-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg moved MSITE-148 to MNG-3271:
Description:
As far as I understand, adding
true
in thesection of my pom should have the same effect as
{code}
org.apache.maven.plugins
maven-project-info-reports-plugin
{code}
... but only that latter had any effect.
(I was mainly trying to disable the dependencies report, because I have many
dependencies build with m1 which don't have a proper m2 pom)
was:
As far as I understand, adding
true
in thesection of my pom should have the same effect as
org.apache.maven.plugins
maven-project-info-reports-plugin
... but only that latter had any effect.
(I was mainly trying to disable the dependencies report, because I have many
dependencies build with m1 which don't have a proper m2 pom)
Key: MNG-3271 (was: MSITE-148)
Project: Maven 2 (was: Maven 2.x Site Plugin)
> does not seem to work
> ---
>
> Key: MNG-3271
> URL: http://jira.codehaus.org/browse/MNG-3271
> Project: Maven 2
> Issue Type: Bug
>Reporter: Grégory Joseph
>
> As far as I understand, adding
> true
> in thesection of my pom should have the same effect as
> {code}
>
> org.apache.maven.plugins
> maven-project-info-reports-plugin
>
>
>
>
> {code}
> ... but only that latter had any effect.
> (I was mainly trying to disable the dependencies report, because I have many
> dependencies build with m1 which don't have a proper m2 pom)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3271) does not seem to work
[
http://jira.codehaus.org/browse/MNG-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MNG-3271:
-
Affects Version/s: 2.0.7
Component/s: POM
Seems to have something to do with reading the pom.
> does not seem to work
> ---
>
> Key: MNG-3271
> URL: http://jira.codehaus.org/browse/MNG-3271
> Project: Maven 2
> Issue Type: Bug
> Components: POM
>Affects Versions: 2.0.7
>Reporter: Grégory Joseph
>
> As far as I understand, adding
> true
> in thesection of my pom should have the same effect as
> {code}
>
> org.apache.maven.plugins
> maven-project-info-reports-plugin
>
>
>
>
> {code}
> ... but only that latter had any effect.
> (I was mainly trying to disable the dependencies report, because I have many
> dependencies build with m1 which don't have a proper m2 pom)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPLUGIN-61) NPE in plugin site when a mojo has no configuration injection
[ http://jira.codehaus.org/browse/MPLUGIN-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MPLUGIN-61: --- Component/s: Plugin Plugin > NPE in plugin site when a mojo has no configuration injection > - > > Key: MPLUGIN-61 > URL: http://jira.codehaus.org/browse/MPLUGIN-61 > Project: Maven 2.x Plugin Tools > Issue Type: Bug > Components: Plugin Plugin > Environment: xp >Reporter: Dan Tran > Attachments: site.log > > > When a plugin has a mojo with no configuration injection like the one at > https://svn.codehaus.org/mojo/tags/maven-native-1.0-alpha-1/native-maven-plugin/src/main/java/org/codehaus/mojo/natives/plugin/NativeInitializeMojo.java > mvn site throws NPE. See attached log -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MPLUGIN-61) NPE in plugin site when a mojo has no configuration injection
[ http://jira.codehaus.org/browse/MPLUGIN-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg moved MSITE-152 to MPLUGIN-61: -- Affects Version/s: (was: 2.0-beta-5) Fix Version/s: (was: 2.0-beta-7) Key: MPLUGIN-61 (was: MSITE-152) Project: Maven 2.x Plugin Tools (was: Maven 2.x Site Plugin) > NPE in plugin site when a mojo has no configuration injection > - > > Key: MPLUGIN-61 > URL: http://jira.codehaus.org/browse/MPLUGIN-61 > Project: Maven 2.x Plugin Tools > Issue Type: Bug > Components: Plugin Plugin > Environment: xp >Reporter: Dan Tran > Attachments: site.log > > > When a plugin has a mojo with no configuration injection like the one at > https://svn.codehaus.org/mojo/tags/maven-native-1.0-alpha-1/native-maven-plugin/src/main/java/org/codehaus/mojo/natives/plugin/NativeInitializeMojo.java > mvn site throws NPE. See attached log -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-166) Banner images or text missing from printed site output
[ http://jira.codehaus.org/browse/MSITE-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112708 ] Dennis Lundberg commented on MSITE-166: --- I agree with Brett, that such images should not be included when printing a page. One thing we could do is use the bannerLeft.name and bannerRight.name and print those in a fairly large font size. > Banner images or text missing from printed site output > -- > > Key: MSITE-166 > URL: http://jira.codehaus.org/browse/MSITE-166 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 >Reporter: Wendy Smoak > > If you print a page from the generated website, the banner images and text at > the top of the page are not included. > Compare printouts of >http://struts.apache.org/1.2.9/(based on the Jakarta/Anakia stylesheet) > and >http://struts.apache.org/ (Maven 2, maven-site-plugin) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-228) Try and unable to resolve org.apache.maven.skins:maven-default-skin:jar:RELEASE when another skin is specified
[
http://jira.codehaus.org/browse/MSITE-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112709
]
Dennis Lundberg commented on MSITE-228:
---
The "Unable to determine the release version" part might have something to do
with the fact that your local "stage" repository is using a a legacy layout.
Such a layout doesn't have the metadata files that an M2 repo has. Perhaps
this is what is causing the site-plugin to not find the release version.
> Try and unable to resolve
> org.apache.maven.skins:maven-default-skin:jar:RELEASE when another skin is
> specified
> --
>
> Key: MSITE-228
> URL: http://jira.codehaus.org/browse/MSITE-228
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-5
>Reporter: Stefano Bagnara
>
> 1) My project does not use external repositories for dependencies but only
> for plugins.
> 2) For dependencies I have a "stage" folder that is a "legacy structured"
> local repository I reference this way:
> {code}
> local-james-stage-m1
> Local James stage repository
> file://c:/lab/void/projects/server-trunk-modular/stage
> legacy
>
> true
> ignore
>
>
> true
> ignore
>
> {code}
> 3) in my site.xml I have this:
> {code}
> org.apache.james
> maven-skin
> 1.1-SNAPSHOT
> {code}
> 4) and in my local stage repository I have the
> org.apache.james/poms/maven-skin-1.1-SNAPSHOT.pom and
> org.apache.james/jars/maven-skin-1.1-SNAPSHOT.jar files.
> If I try to build the project, package it, run tests and everything else it
> works, but when I try to build "mvn site" if fails with this error:
> {code}
> [DEBUG] maven-default-skin: using locally installed snapshot
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] The skin does not exist: Unable to determine the release version
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.maven.skins
> -DartifactId=maven-default-skin \
> -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file
> org.apache.maven.skins:maven-default-skin:jar:RELEASE
> [INFO]
>
> [DEBUG] Trace
> org.apache.maven.BuildFailureException: The skin does not exist: Unable to
> determine the release version
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.maven.skins
> -DartifactId=maven-default-skin \
> -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file
> org.apache.maven.skins:maven-default-skin:jar:RELEASE
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:560)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoFailureException: The skin does not
> exist: Unable to determine the release version
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.maven.skins
> -DartifactI
[jira] Commented: (MSITE-255) Executing the site-site goal fails prior to executing the site-deploy goal on a clean maven install (Could be due to dependencies)
[
http://jira.codehaus.org/browse/MSITE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112710
]
Dennis Lundberg commented on MSITE-255:
---
The stacktrace indicates that there is something wrong when working on an .fml
file. That is the FAQ format that the site-plugin supports. Could you provide
us with a sample project that exhibits the problem described. Please include
the pom.xml, site.xml and all the files under /src/site.
Also could you please try this using the 2.0-beta-6-SNAPSHOT version of the
site-plugin. A lot of bug fixes has gone into that version, so this might have
been solved already.
> Executing the site-site goal fails prior to executing the site-deploy goal on
> a clean maven install (Could be due to dependencies)
> --
>
> Key: MSITE-255
> URL: http://jira.codehaus.org/browse/MSITE-255
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-5
> Environment: Windows XP, Java 1.5, Intel Pentium 4
>Reporter: Sahand
>
> When running {{mvn site:site}} from a clean maven install I get FATAL ERROR
> caused by a NullPointerException. (*Trace log below*)
> This was resolved by running {{mvn site:deploy}} which seemed to retrieve a
> series of dependent libraries. After which, running {{mvn site:site}} would
> execute successfully.
> I will test it again when I get the time to narrow down the dependency that
> is required for execution and is not being retrieved.
> {quote}
> [ERROR] FATAL ERROR
> [INFO]
> -
> ---
> [INFO] null
> [INFO]
> -
> ---
> [INFO] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.doxia.module.fml.FmlParser.createSink(FmlParser.java
> :270)
> at
> org.apache.maven.doxia.module.fml.FmlParser.parse(FmlParser.java:61)
> at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:52)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocumen
> t(DefaultSiteRenderer.java:264)
> at
> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocum
> ent(DoxiaDocumentRenderer.java:43)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(
> DefaultSiteRenderer.java:239)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(Defaul
> tSiteRenderer.java:115)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:124
> )
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:539)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:480)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:459)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO]
> -
> ---
> [INFO] Total time: 26 seconds
> [INFO] Finished at: Wed Aug 29 12:49:50 EST 2007
> [INFO] Final Memory: 25M/44M
> [INFO]
> -
> {quote}
--
This message is automatically generated by JIRA.
-
If you th
[jira] Updated: (DOXIA-181) Confluence ParagraphBlockParser does not offer lines to other parsers
[
http://jira.codehaus.org/browse/DOXIA-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Syer updated DOXIA-181:
Attachment: paragraph-delegation-patch.txt
Attached a patch for paragraph broken by list (paragraph-delegation). Also
deals with paragraph broken by heading and by figure. Other possibilities
exist (e.g. broken by verbatim), but these would seem to be the most useful.
(Also fixes an unreported bug with list items carried over multiple lines,
since this is a related problem, and DOXIA-181 couldn't be fixed without fixing
that one.)
> Confluence ParagraphBlockParser does not offer lines to other parsers
> -
>
> Key: DOXIA-181
> URL: http://jira.codehaus.org/browse/DOXIA-181
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Confluence
>Affects Versions: 1.0-alpha-9
>Reporter: Dave Syer
> Fix For: 1.0-beta-1
>
> Attachments: mylyn-context.zip, paragraph-delegation-patch.txt
>
>
> Confluence ParagraphBlockParser does not offer lines to other parsers. There
> is a TODO in the source code. Test cases would include
> {code}
> {anchor:before}
> h1. Section Title
> {code}
> should render the anchor in a separate paragraph, and
> {code}
> A paragraph
> * with nested list
> * items
> should render as a list
> {code}
> A paragraph
> * with nested list
> * items
> should render as a list
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DOXIA-181) Confluence ParagraphBlockParser does not offer lines to other parsers
[
http://jira.codehaus.org/browse/DOXIA-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Syer updated DOXIA-181:
Attachment: mylyn-context.zip
> Confluence ParagraphBlockParser does not offer lines to other parsers
> -
>
> Key: DOXIA-181
> URL: http://jira.codehaus.org/browse/DOXIA-181
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Confluence
>Affects Versions: 1.0-alpha-9
>Reporter: Dave Syer
> Fix For: 1.0-beta-1
>
> Attachments: mylyn-context.zip, paragraph-delegation-patch.txt
>
>
> Confluence ParagraphBlockParser does not offer lines to other parsers. There
> is a TODO in the source code. Test cases would include
> {code}
> {anchor:before}
> h1. Section Title
> {code}
> should render the anchor in a separate paragraph, and
> {code}
> A paragraph
> * with nested list
> * items
> should render as a list
> {code}
> A paragraph
> * with nested list
> * items
> should render as a list
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-269) Urls rewritten when they contain the project urls' hostname
[ http://jira.codehaus.org/browse/MSITE-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-269. - Assignee: Dennis Lundberg Resolution: Won't Fix The rewriting of URLs is intended. However the links do *not* contain the deploy location. If you have a look at the source of the generated html files you will see that the URLs have been rewritten so that they are relative. > Urls rewritten when they contain the project urls' hostname > --- > > Key: MSITE-269 > URL: http://jira.codehaus.org/browse/MSITE-269 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Reporter: Cameron Jones >Assignee: Dennis Lundberg > Attachments: pom.xml, site.xml > > > Urls in the site.xml file are being rewritten if they contain the hostname of > the project url. For example: > pom.xml: > http://208.75.85.243 > ... > > test.site > file:///srv/www/test/site > > ... > site.xml: > http://208.75.85.243/index.html"; /> > Results in the following link for the About page which is incorrect and > includes the deployment location instead of the url: > http://208.75.85.243/test/site/index.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-212) Catalan Language
[ http://jira.codehaus.org/browse/MSITE-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-212: -- Patch Submitted: [Yes] > Catalan Language > > > Key: MSITE-212 > URL: http://jira.codehaus.org/browse/MSITE-212 > Project: Maven 2.x Site Plugin > Issue Type: New Feature > Components: localization >Reporter: Javier de Ros > Attachments: site-plugin_ca.properties > > > That's the Catalan language properties for the maven site plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MNG-2734) Collect all Settings build stuff into the embedder
[ http://jira.codehaus.org/browse/MNG-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl reopened MNG-2734: > Collect all Settings build stuff into the embedder > -- > > Key: MNG-2734 > URL: http://jira.codehaus.org/browse/MNG-2734 > Project: Maven 2 > Issue Type: Task > Components: Embedding >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: Reviewed Pending Version Assignment > > > There is code in SettingsBuilder, MavenTools that can be shored up and > simplified -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2734) Collect all Settings build stuff into the embedder
[ http://jira.codehaus.org/browse/MNG-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2734. -- Resolution: Fixed > Collect all Settings build stuff into the embedder > -- > > Key: MNG-2734 > URL: http://jira.codehaus.org/browse/MNG-2734 > Project: Maven 2 > Issue Type: Task > Components: Embedding >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > > There is code in SettingsBuilder, MavenTools that can be shored up and > simplified -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MNG-3270) The MavenMetadataSource determine metadata requirements
[ http://jira.codehaus.org/browse/MNG-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl reopened MNG-3270: Assignee: Jason van Zyl > The MavenMetadataSource determine metadata requirements > --- > > Key: MNG-3270 > URL: http://jira.codehaus.org/browse/MNG-3270 > Project: Maven 2 > Issue Type: Bug >Reporter: Jason van Zyl >Assignee: Jason van Zyl > > The MetadataSource should determine if a particular piece of metadata should > exist or not. I've place a boolean in the metadata source and set it to false > right now which means we are still allowing projects not to have POMs, or > have invalid POMs but at least the decisions is captured here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2734) Collect all Settings build stuff into the embedder
[ http://jira.codehaus.org/browse/MNG-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2734: --- Fix Version/s: (was: Reviewed Pending Version Assignment) 2.1-alpha-1 > Collect all Settings build stuff into the embedder > -- > > Key: MNG-2734 > URL: http://jira.codehaus.org/browse/MNG-2734 > Project: Maven 2 > Issue Type: Task > Components: Embedding >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > > There is code in SettingsBuilder, MavenTools that can be shored up and > simplified -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3270) The MavenMetadataSource determine metadata requirements
[ http://jira.codehaus.org/browse/MNG-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-3270. -- Resolution: Fixed Fix Version/s: 2.1-alpha-1 > The MavenMetadataSource determine metadata requirements > --- > > Key: MNG-3270 > URL: http://jira.codehaus.org/browse/MNG-3270 > Project: Maven 2 > Issue Type: Bug >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > > The MetadataSource should determine if a particular piece of metadata should > exist or not. I've place a boolean in the metadata source and set it to false > right now which means we are still allowing projects not to have POMs, or > have invalid POMs but at least the decisions is captured here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MNG-3170) DefaultRepositoryMetadataManager caches metadata without eviction policy
[ http://jira.codehaus.org/browse/MNG-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl reopened MNG-3170: > DefaultRepositoryMetadataManager caches metadata without eviction policy > > > Key: MNG-3170 > URL: http://jira.codehaus.org/browse/MNG-3170 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 2.1-alpha-1 >Reporter: Carlos Sanchez >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > > DefaultRepositoryMetadataManager.cachedMetadata ignores changes in the local > repo as the metadata is cached forever in an embedded environment -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3170) DefaultRepositoryMetadataManager caches metadata without eviction policy
[ http://jira.codehaus.org/browse/MNG-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-3170. -- Resolution: Fixed Fix Version/s: (was: 2.1) 2.1-alpha-1 > DefaultRepositoryMetadataManager caches metadata without eviction policy > > > Key: MNG-3170 > URL: http://jira.codehaus.org/browse/MNG-3170 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 2.1-alpha-1 >Reporter: Carlos Sanchez >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > > DefaultRepositoryMetadataManager.cachedMetadata ignores changes in the local > repo as the metadata is cached forever in an embedded environment -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2443) Don't download pom if artifact is already in the local repository
[ http://jira.codehaus.org/browse/MNG-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112732 ] Jason van Zyl commented on MNG-2443: That an artifact having been incorrectly deployed without a POM doesn't mean that a POM should not be added in the future. I just hit this with Velocity View Tools where there is no POM but I ask them to correct it. A POM simply should not be deployed without a POM in the first place but we assume that it may be corrected in the future, not that it will never be corrected. We really need to correct the projects without POMs, always make the attempt in the background, but not show this constant downloading to the user. Once a POM is present it will never to downloaded again, but as long as this annoying message is not in your face all the time. A silent attempt in the background probably won't do much harm and is the safest approach with attempting but not annoying the user with the output. > Don't download pom if artifact is already in the local repository > - > > Key: MNG-2443 > URL: http://jira.codehaus.org/browse/MNG-2443 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.4 >Reporter: Carsten Ziegeler > Fix For: 2.1 > > > There are many projects out there just providing their artifact without a pom > (whether this is good or not is a different question). Now in this case m2 > always tries to download a pom for those artifacts, even if the artifact > itself is already in the local repository. And if you have several of those > artifacts combined with more than one repository configured, then there are a > lot of unnecessary download attempts. > I think this falls into the same category as changing a pom in the repository > (which should be forbidden) - so if for the first time the artifact is > downloaded no pom available, then there will never be a pom for this specific > artifact. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-259) Bump to new release of jetty
[ http://jira.codehaus.org/browse/MSITE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-259. - Assignee: Brett Porter Resolution: Fixed Fix Version/s: 2.0-beta-6 Fixed by Brett in r589486. > Bump to new release of jetty > > > Key: MSITE-259 > URL: http://jira.codehaus.org/browse/MSITE-259 > Project: Maven 2.x Site Plugin > Issue Type: Improvement > Components: site:run >Affects Versions: 2.0-beta-6 >Reporter: Vincent Siveton >Assignee: Brett Porter > Fix For: 2.0-beta-6 > > > site plugin uses a RC version of jetty. Should better to have an official > release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-232) Deploy multi module site to windows share
[ http://jira.codehaus.org/browse/MSITE-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-232. - Assignee: Dennis Lundberg Resolution: Won't Fix > Deploy multi module site to windows share > - > > Key: MSITE-232 > URL: http://jira.codehaus.org/browse/MSITE-232 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: site:deploy >Affects Versions: 2.0-beta-4, 2.0-beta-5 > Environment: windows xp sp 2 >Reporter: Yves Van Steen >Assignee: Dennis Lundberg > > I was unable to deploy the sites of my submodules to my windows share. the > windows share is one that is under a web path to my apache webserver. > For the record some other posted bugs on the JIRA about deploy to windows > share did'nt expect this kind of behaviour (the double backslash way, > file:\\\...). I did. Don't really find it odd. > It only works when you have a single module build. When you have a reactor > build (pom with modules) it only deploys the root (or top pom) but sub > projects don't get deployed because maven starts to use slashes and not > backslashes. > Example : > Deploy top = file://\\vam7225\repo\www\orbisbe (=> works) > Deploy subproject = file://\\vam7225\repo\www\orbisbe/component1 (=> No > deploy) > Deploy subproject = file://\\vam7225\repo\www\orbisbe/component2 (=> No > deploy) > But It does NOT report a failure on the sub projects. And you can see the use > of the normal slash above. > Is there a fix available for this ?? > Thanx for any help -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-258) Deployment on network drive for multi-modules fails for modules sites
[ http://jira.codehaus.org/browse/MSITE-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112735 ] Dennis Lundberg commented on MSITE-258: --- How would you write the path of your network drive (i.e. the windows path), that corresponds to the url you specified in distributionManagement? > Deployment on network drive for multi-modules fails for modules sites > - > > Key: MSITE-258 > URL: http://jira.codehaus.org/browse/MSITE-258 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: inheritance, multi module, site:deploy >Affects Versions: 2.0-beta-5 > Environment: Windows, Maven 2.0.5, site plugin version 2.0-beta-5 >Reporter: Romain Linsolas >Priority: Minor > > I work on a project with several modules, for example : > myproject > + commons > + business > + ... > (myproject is also the parent project for all modules) > In the parent pom.xml, I define the distribution management in order to > deploy my whole site on a network drive (which is not mapped): > > > website > file://yyy/sites/my-site > > > When I deploy the whole site (command mvn site-deploy run on the parent > directory), the "core" site is correctly deployed on my network drive, but > all modules are deployed on my C: drive (in the directory > C:\\y\sites\my-site\...). > As the core site is correctly deployed, I think the problem is that the > deployment URL is not correctly given to all project children. Maybe it is a > Maven bug, not a Site Plugin problem? > The only way to make the deployment works correctly is to redefine, for each > modules, the distributionManagement! > Note that this problem does not occur if the network drive is mapped (for > example if the distribution URL is something like "F:/sites/my-site/"). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEP-118) Resolving dependencies with the same JDK specified by the Compiler plugin
[ http://jira.codehaus.org/browse/MDEP-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112734 ] Brian Fox commented on MDEP-118: I still don't understand, sorry. Resolving the dependencies has nothing to do with the JDK, unless of course you mean things that have JDK classifiers like TestNG. If that's the case, you can already do that by specifying the classifier. Can you provide an example? > Resolving dependencies with the same JDK specified by the Compiler plugin > - > > Key: MDEP-118 > URL: http://jira.codehaus.org/browse/MDEP-118 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: resolve >Affects Versions: 2.0-alpha-4 >Reporter: Claudio Di Vita >Assignee: Brian Fox > > The dependencies have to be resolved with the same JDK specified by the > Compiler plugin, not with the version used by Maven scripts. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-258) Deployment on network drive for multi-modules fails for modules sites
[ http://jira.codehaus.org/browse/MSITE-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112736 ] Dennis Lundberg commented on MSITE-258: --- This might be related to MSITE-232. > Deployment on network drive for multi-modules fails for modules sites > - > > Key: MSITE-258 > URL: http://jira.codehaus.org/browse/MSITE-258 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: inheritance, multi module, site:deploy >Affects Versions: 2.0-beta-5 > Environment: Windows, Maven 2.0.5, site plugin version 2.0-beta-5 >Reporter: Romain Linsolas >Priority: Minor > > I work on a project with several modules, for example : > myproject > + commons > + business > + ... > (myproject is also the parent project for all modules) > In the parent pom.xml, I define the distribution management in order to > deploy my whole site on a network drive (which is not mapped): > > > website > file://yyy/sites/my-site > > > When I deploy the whole site (command mvn site-deploy run on the parent > directory), the "core" site is correctly deployed on my network drive, but > all modules are deployed on my C: drive (in the directory > C:\\y\sites\my-site\...). > As the core site is correctly deployed, I think the problem is that the > deployment URL is not correctly given to all project children. Maybe it is a > Maven bug, not a Site Plugin problem? > The only way to make the deployment works correctly is to redefine, for each > modules, the distributionManagement! > Note that this problem does not occur if the network drive is mapped (for > example if the distribution URL is something like "F:/sites/my-site/"). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-254) Error when using an absolute URL in a menu item in site.xml
[ http://jira.codehaus.org/browse/MSITE-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-254. - Assignee: Dennis Lundberg Resolution: Duplicate This is the current behavior of the site-plugin. > Error when using an absolute URL in a menu item in site.xml > > > Key: MSITE-254 > URL: http://jira.codehaus.org/browse/MSITE-254 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: relative links >Reporter: Alexander Hars >Assignee: Dennis Lundberg > > When defining the following menu item in site.xml, then the last menu item is > not rendered properly as an absolute URL. > Its href is empty: > > > > > http://maven.apache.org/maven2/"/> > > The problem seems to be rooted somewhere in $decoration.body.menus. > The problem does not occur for links! > Steps to reproduce: > - Create a new maven project using the site Archetype. > - Modify the menu section in the site.xml as shown above by adding an > absolute URL. > - run mvn clean > - run mvn site > Check the absolute URL. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-254) Error when using an absolute URL in a menu item in site.xml
[ http://jira.codehaus.org/browse/MSITE-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-254: -- Affects Version/s: (was: 2.0) > Error when using an absolute URL in a menu item in site.xml > > > Key: MSITE-254 > URL: http://jira.codehaus.org/browse/MSITE-254 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: relative links >Reporter: Alexander Hars > > When defining the following menu item in site.xml, then the last menu item is > not rendered properly as an absolute URL. > Its href is empty: > > > > > http://maven.apache.org/maven2/"/> > > The problem seems to be rooted somewhere in $decoration.body.menus. > The problem does not occur for links! > Steps to reproduce: > - Create a new maven project using the site Archetype. > - Modify the menu section in the site.xml as shown above by adding an > absolute URL. > - run mvn clean > - run mvn site > Check the absolute URL. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-229) Links in site.xml get translated to ../../../
[ http://jira.codehaus.org/browse/MSITE-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-229. - Assignee: Dennis Lundberg Resolution: Duplicate I have added an FAQ entry for this. > Links in site.xml get translated to ../../../ > - > > Key: MSITE-229 > URL: http://jira.codehaus.org/browse/MSITE-229 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: relative links >Affects Versions: 2.0-beta-5 > Environment: Linux FC6 Sun Java (build 1.5.0_10-b03, mixed mode, > sharing) >Reporter: Mykel Alvis >Assignee: Dennis Lundberg >Priority: Minor > Attachments: site.xml > > > In Site.xml for a project (that has a parent POM) > > http://sirdsite.dsths.ad.dstcorp.net/"; /> > http://www.apache.org/"; /> > http://maven.apache.org/maven2/"/> > > Gets rendered as > > SIRD Site > | > http://www.apache.org/";>Apache > | > http://maven.apache.org/maven2/";>Maven 2 > > " http://sirdsite.dsths.ad.dstcorp.net/"; != "../../.." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-197) poweredBy Logo links don't work
[ http://jira.codehaus.org/browse/MSITE-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-197: -- Attachment: MSITE-197.zip Another try, this time without the generated site in it. > poweredBy Logo links don't work > --- > > Key: MSITE-197 > URL: http://jira.codehaus.org/browse/MSITE-197 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: relative links >Affects Versions: 2.0-beta-5 >Reporter: Henning Schmiedehausen >Priority: Minor > Attachments: MSITE-197.zip > > > I added the following poweredBy Item to my site: > >href="http://velocity.apache.org"; > img="/images/pbv90x30.png" /> > > This gets rendered out to > > src="images/pbv90x30.png" /> > > > The href link is empty. When debugging, it seems that any URL given to the > logo href attribute gets silently removed. Using href="foobar" works, > href="http://www.apache.org/"; does not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-197) poweredBy Logo links don't work
[ http://jira.codehaus.org/browse/MSITE-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-197: -- Attachment: (was: MSITE-197.zip) > poweredBy Logo links don't work > --- > > Key: MSITE-197 > URL: http://jira.codehaus.org/browse/MSITE-197 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: relative links >Affects Versions: 2.0-beta-5 >Reporter: Henning Schmiedehausen >Priority: Minor > Attachments: MSITE-197.zip > > > I added the following poweredBy Item to my site: > >href="http://velocity.apache.org"; > img="/images/pbv90x30.png" /> > > This gets rendered out to > > src="images/pbv90x30.png" /> > > > The href link is empty. When debugging, it seems that any URL given to the > logo href attribute gets silently removed. Using href="foobar" works, > href="http://www.apache.org/"; does not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-197) poweredBy Logo links don't work
[ http://jira.codehaus.org/browse/MSITE-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-197: -- Attachment: MSITE-197.zip Here's a small project that displays this behavior. The default config has a href="" on the poweredBy logo, because the url in the pom is the same as the url for the poweredBy logo. If you change the url in the pom to the maven.apache.org one that is currently commented out, you will see that the href on the poweredBy logo will be different. > poweredBy Logo links don't work > --- > > Key: MSITE-197 > URL: http://jira.codehaus.org/browse/MSITE-197 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: relative links >Affects Versions: 2.0-beta-5 >Reporter: Henning Schmiedehausen >Priority: Minor > Attachments: MSITE-197.zip > > > I added the following poweredBy Item to my site: > >href="http://velocity.apache.org"; > img="/images/pbv90x30.png" /> > > This gets rendered out to > > src="images/pbv90x30.png" /> > > > The href link is empty. When debugging, it seems that any URL given to the > logo href attribute gets silently removed. Using href="foobar" works, > href="http://www.apache.org/"; does not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-197) poweredBy Logo links don't work
[ http://jira.codehaus.org/browse/MSITE-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-197. - Assignee: Dennis Lundberg Resolution: Duplicate > poweredBy Logo links don't work > --- > > Key: MSITE-197 > URL: http://jira.codehaus.org/browse/MSITE-197 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: relative links >Affects Versions: 2.0-beta-5 >Reporter: Henning Schmiedehausen >Assignee: Dennis Lundberg >Priority: Minor > Attachments: MSITE-197.zip > > > I added the following poweredBy Item to my site: > >href="http://velocity.apache.org"; > img="/images/pbv90x30.png" /> > > This gets rendered out to > > src="images/pbv90x30.png" /> > > > The href link is empty. When debugging, it seems that any URL given to the > logo href attribute gets silently removed. Using href="foobar" works, > href="http://www.apache.org/"; does not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-215) creates broken links for parents parent
[ http://jira.codehaus.org/browse/MSITE-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112741 ] Dennis Lundberg commented on MSITE-215: --- I tried your example project and can confirm the described wrong behavior, when used with maven-site-plugin 2.0-beta-5. However, if I use the latest 2.0-beta-6-SNAPSHOT, it seems to work as expected. Only one parent link shows up in the menu of banana-baby and it goes to banana-daddy. There is no link to banana-grandpa in the menu of banana-baby. Jörg, can you confirm this? > creates broken links for parents parent > --- > > Key: MSITE-215 > URL: http://jira.codehaus.org/browse/MSITE-215 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: multi module >Reporter: Jörg Hohwiller > Attachments: banana-world.zip > > > In a multi-project environment with modules that again have modules > (project/module1/module1A) the not only creates the > direct parent but all parents (see issue MSITE-136) what seems perfect to me. > Anyways only the link of the direct parent works for me. All other links are > broken. I use "mvn site:stage -DstagingDirectory=". > If I use -DstagingDirectory=/foo/bar then the link for "module1" is > "/foo/bar//module1/index.html" what is correct. But the link > for "project" is "/foo//index.html" but it should be > "/foo/bar//index.html". > Besides I do NOT want to have the "" what is automatically > produced from the "" of the POM, but is required for > site:stage to work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DOXIA-181) Confluence ParagraphBlockParser does not offer lines to other parsers
[
http://jira.codehaus.org/browse/DOXIA-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl closed DOXIA-181.
---
Assignee: Lukas Theussl
Resolution: Fixed
Patch applied, thanks!
> Confluence ParagraphBlockParser does not offer lines to other parsers
> -
>
> Key: DOXIA-181
> URL: http://jira.codehaus.org/browse/DOXIA-181
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Confluence
>Affects Versions: 1.0-alpha-9
>Reporter: Dave Syer
>Assignee: Lukas Theussl
> Fix For: 1.0-beta-1
>
> Attachments: mylyn-context.zip, paragraph-delegation-patch.txt
>
>
> Confluence ParagraphBlockParser does not offer lines to other parsers. There
> is a TODO in the source code. Test cases would include
> {code}
> {anchor:before}
> h1. Section Title
> {code}
> should render the anchor in a separate paragraph, and
> {code}
> A paragraph
> * with nested list
> * items
> should render as a list
> {code}
> A paragraph
> * with nested list
> * items
> should render as a list
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MANTTASKS-88) Add the ability to download javadoc dependencies
[ http://jira.codehaus.org/browse/MANTTASKS-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MANTTASKS-88: --- Fix Version/s: (was: 2.0.8) > Add the ability to download javadoc dependencies > - > > Key: MANTTASKS-88 > URL: http://jira.codehaus.org/browse/MANTTASKS-88 > Project: Maven 2.x Ant Tasks > Issue Type: Improvement > Components: dependencies task >Affects Versions: 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.6, 2.0.7 > Environment: Linux JDK 1.5 >Reporter: Eric Hartmann >Assignee: Herve Boutemy >Priority: Minor > Attachments: patch.txt > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > The ant task cannot download the javadocs files of dependencies. > Here a small patch to add this enhancement the same way of downloading > sources. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1796) resourceaccelerate 1.0-rc1
resourceaccelerate 1.0-rc1 -- Key: MAVENUPLOAD-1796 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1796 Project: maven-upload-requests Issue Type: Task Reporter: fabrizio giustina Resource Accelerate is a J2EE web application filter that provides three significant performance enhancements to web applications that use CSS, JavaScript, and shared images in a simple, easy to use package. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-45) Ability to create an ear/war/zip from site
[ http://jira.codehaus.org/browse/MSITE-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-45: - Affects Version/s: 2.0-beta-5 Summary: Ability to create an ear/war/zip from site (was: abilitiy to create an ear/war/zip from site) > Ability to create an ear/war/zip from site > -- > > Key: MSITE-45 > URL: http://jira.codehaus.org/browse/MSITE-45 > Project: Maven 2.x Site Plugin > Issue Type: New Feature >Affects Versions: 2.0-beta-5 >Reporter: Brett Porter >Assignee: Dennis Lundberg > Attachments: MSITE-45-maven-site-plugin.patch, patch.txt > > > I think they should be standalone goals, like in m1 > site:ear -> create ear > site:war -> create war > site:zip -> create zip > I think this one might be a lower priority. I will postpone it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-45) Ability to create an ear/war/zip from site
[ http://jira.codehaus.org/browse/MSITE-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112750 ] Dennis Lundberg commented on MSITE-45: -- I have applied Matthew's patch, with minor adjustments. The only notable change I made was to change the artifactType from "site" to "jar" in the call to projectHelper.attachArtifact(...). Otherwise the installed attached site would get a .site file ending. > Ability to create an ear/war/zip from site > -- > > Key: MSITE-45 > URL: http://jira.codehaus.org/browse/MSITE-45 > Project: Maven 2.x Site Plugin > Issue Type: New Feature >Affects Versions: 2.0-beta-5 >Reporter: Brett Porter >Assignee: Dennis Lundberg > Attachments: MSITE-45-maven-site-plugin.patch, patch.txt > > > I think they should be standalone goals, like in m1 > site:ear -> create ear > site:war -> create war > site:zip -> create zip > I think this one might be a lower priority. I will postpone it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MANTTASKS-87) Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml will cause a "Error downloading parent pom" error
[ http://jira.codehaus.org/browse/MANTTASKS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MANTTASKS-87. -- Resolution: Fixed Fix Version/s: 2.0.8 this should be fixed now: can you check it? having a testcase of a pom successfully building but not downloading its parent would help too, to be sure such a regression don't arrive in the future > Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml > will cause a "Error downloading parent pom" error > - > > Key: MANTTASKS-87 > URL: http://jira.codehaus.org/browse/MANTTASKS-87 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: POM Integration >Affects Versions: 2.0.7 > Environment: WindowsXP > Ant version 1.7.0 >Reporter: Jeff Campbell >Assignee: Herve Boutemy >Priority: Blocker > Fix For: 2.0.8 > > > Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml > will cause a "Error downloading parent pom" error. > This WAS NOT a bug with version 2.0.6 of the maven-ant-tasks (new issue to > maven-ant-tasks-2.0.7.jar and still an issue with the latest > maven-ant-tasks-2.0.8-SNAPSHOT.jar (as of the writting of this bug)). > Just to see if I had done something wrong with the pom.xml file I tried to > run a Maven goal against the pom.xml file. I found that if I run "mvn clean" > from this same directory (where the build.xml and pom.xml file is located), > using Maven-2.0.7, I get a build successfull (it was able to find the parent > pom.xml file... so this seems to be isolated to JUST the maven-ant-task not > being able to find the parent pom.xml) > Sample of the pom.xml file > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > 4.0.0 > intuit.sbconnect > sbclogin > 1.0.3 > SBCLogin > > > mygroup > CommonPOM > 1.0.2 > > > > > myothergroup > myartifact > 1.0 > > > > Line in Ant build.xml file that causes the error: > > Error that occurs when this line is executed in ant: > Error downloading parent pom: Missing: > -- > 1) mygroup:CommonPOM:pom:1.0.2 > Path to dependency: > 1) unspecified:unspecified:jar:0.0 > 2) mygroup:CommonPOM:pom:1.0.2 > -- > 1 required artifact is missing. > for artifact: > unspecified:unspecified:jar:0.0 > from the specified remote repositories: > central (http://repo1.maven.org/maven2) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MANTTASKS-86) Resolution of java.net dependencies
[ http://jira.codehaus.org/browse/MANTTASKS-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MANTTASKS-86. -- Resolution: Cannot Reproduce if you still have a problem, please reopen and help me reproduce it > Resolution of java.net dependencies > --- > > Key: MANTTASKS-86 > URL: http://jira.codehaus.org/browse/MANTTASKS-86 > Project: Maven 2.x Ant Tasks > Issue Type: Bug >Affects Versions: 2.0.6 >Reporter: Werner Guttmann > Attachments: build.bat, build.xml, pom.xml > > > I am trying to use the Ant task for Maven with the root Maven POM for > the Castor project for download the dependencies and place them into a > lib directory. > What I have observed is that there's a few dependencies missing when I > run the corresponding Ant target. But if I use Maven for the build > process, the missing JARs are downloaded as well and placed into my > local repository. > I have tried to define remoteRepository entries for the java.net and the > Maven 2 java.net repositories (where e.g. java.transaction:jta:1.1.1B > resides), but this does not make a difference. > Any idea what I could try in addition ? Having said that, all other > dependencies are resolved and copied without any problems. It looks like > it's just the dependencies that are not synced globally that create a > problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MANTTASKS-92) setting from $M2_HOME/conf/settings.xml not respected
[
http://jira.codehaus.org/browse/MANTTASKS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112754
]
Herve Boutemy commented on MANTTASKS-92:
please run Ant with "-v" option to get verbose output: you'll see if a
settings.xml file is read
$ANT_HOME/etc/settings.xml should be read if the file is not found in ~/.ant
nor ~/.m2
> setting from $M2_HOME/conf/settings.xml not respected
> ---
>
> Key: MANTTASKS-92
> URL: http://jira.codehaus.org/browse/MANTTASKS-92
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Components: dependencies task
>Affects Versions: 2.0.7
>Reporter: Richard Ziegler
>
> || $M2_HOME/conf/settings.xml || build.xml ||
> | {code:xml}
>
> c:/.m2repo
> ...
>
> {code} | {code:xml}
>
> filesetId="runtime.deps"
> useScope="runtime">
>
>
>...
> {code}|
> The default localRepository location is used despite having
> set in the site settings.xml
> The same is true when set in $ANT_HOME/etc/settings.xml. I know this because
> when I invoke my ant target, I see ~/.m2/repository get created, when it
> shouldn't.
> However, when is specified in ~/.m2/settings.xml or
> ~/.ant/settings.xml, it works. Unfortunatly this is not an option as I need
> to configure this at the site installation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-45) Ability to create an ear/war/zip from site
[ http://jira.codehaus.org/browse/MSITE-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112756 ] Dennis Lundberg commented on MSITE-45: -- I have deployed a new 2.0-beta-6-SNAPSHOT that includes this new jar-mojo. Please give it a try and post your thoughts here. Just run 'mvn site:jar' to try it. Is this enough or do you feel that the other archive types should be supported as well? > Ability to create an ear/war/zip from site > -- > > Key: MSITE-45 > URL: http://jira.codehaus.org/browse/MSITE-45 > Project: Maven 2.x Site Plugin > Issue Type: New Feature >Affects Versions: 2.0-beta-5 >Reporter: Brett Porter >Assignee: Dennis Lundberg > Attachments: MSITE-45-maven-site-plugin.patch, patch.txt > > > I think they should be standalone goals, like in m1 > site:ear -> create ear > site:war -> create war > site:zip -> create zip > I think this one might be a lower priority. I will postpone it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MDEP-119) build-classpath should create destination directory for the classpath file
build-classpath should create destination directory for the classpath file
--
Key: MDEP-119
URL: http://jira.codehaus.org/browse/MDEP-119
Project: Maven 2.x Dependency Plugin
Issue Type: Improvement
Components: build-classpath
Affects Versions: 2.0-alpha-4
Reporter: Adrian Hempel
Assignee: Brian Fox
Priority: Minor
I am binding the build-classpath goal to the generate-resources phase, as
follows:
{code:xml}
maven-dependency-plugin
build-classpath
generate-resources
build-classpath
${project.build.outputDirectory}/com/atlassian/bamboo/agent/classserver/Agent.classpath
{code}
However, it fails, because the target directory doesn't exist:
bq. {{[INFO] Error while opening/closing classpath file
'/Users/ahempel/workarea/private/atlassian/bamboo/trunk/bamboo-agent-classserver/target/classes/com/atlassian/bamboo/agent/classserver/Agent.classpath':
java.io.FileNotFoundException:
/Users/ahempel/workarea/private/atlassian/bamboo/trunk/bamboo-agent-classserver/target/classes/com/atlassian/bamboo/agent/classserver/Agent.classpath
(No such file or directory)}}
The build-classpath goal can be improved by creating the missing directory,
rather than throwing a FileNotFoundException.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MANTTASKS-86) Resolution of java.net dependencies
[ http://jira.codehaus.org/browse/MANTTASKS-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112768 ] Werner Guttmann commented on MANTTASKS-86: -- Sorry, I did only get a message after you closed this issue. I will be back with an answer in a few hours ... > Resolution of java.net dependencies > --- > > Key: MANTTASKS-86 > URL: http://jira.codehaus.org/browse/MANTTASKS-86 > Project: Maven 2.x Ant Tasks > Issue Type: Bug >Affects Versions: 2.0.6 >Reporter: Werner Guttmann > Attachments: build.bat, build.xml, pom.xml > > > I am trying to use the Ant task for Maven with the root Maven POM for > the Castor project for download the dependencies and place them into a > lib directory. > What I have observed is that there's a few dependencies missing when I > run the corresponding Ant target. But if I use Maven for the build > process, the missing JARs are downloaded as well and placed into my > local repository. > I have tried to define remoteRepository entries for the java.net and the > Maven 2 java.net repositories (where e.g. java.transaction:jta:1.1.1B > resides), but this does not make a difference. > Any idea what I could try in addition ? Having said that, all other > dependencies are resolved and copied without any problems. It looks like > it's just the dependencies that are not synced globally that create a > problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MANTTASKS-86) Resolution of java.net dependencies
[ http://jira.codehaus.org/browse/MANTTASKS-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112769 ] Werner Guttmann commented on MANTTASKS-86: -- Looks like attached (by coincidence) a POM that did not include the dependency in question anymore, as they have been moved to another module. I'll re-attach a new POM in a few minutes. > Resolution of java.net dependencies > --- > > Key: MANTTASKS-86 > URL: http://jira.codehaus.org/browse/MANTTASKS-86 > Project: Maven 2.x Ant Tasks > Issue Type: Bug >Affects Versions: 2.0.6 >Reporter: Werner Guttmann > Attachments: build.bat, build.xml, pom.xml > > > I am trying to use the Ant task for Maven with the root Maven POM for > the Castor project for download the dependencies and place them into a > lib directory. > What I have observed is that there's a few dependencies missing when I > run the corresponding Ant target. But if I use Maven for the build > process, the missing JARs are downloaded as well and placed into my > local repository. > I have tried to define remoteRepository entries for the java.net and the > Maven 2 java.net repositories (where e.g. java.transaction:jta:1.1.1B > resides), but this does not make a difference. > Any idea what I could try in addition ? Having said that, all other > dependencies are resolved and copied without any problems. It looks like > it's just the dependencies that are not synced globally that create a > problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MANTTASKS-86) Resolution of java.net dependencies
[
http://jira.codehaus.org/browse/MANTTASKS-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112770
]
Werner Guttmann commented on MANTTASKS-86:
--
Simply add the followinf dependency to the given POM:
{noformat}
javax.transaction
jta
1.0.1B
{noformat}
and see whether you get a 10th JAR downloaded, i.e. the one for the JTA API.
> Resolution of java.net dependencies
> ---
>
> Key: MANTTASKS-86
> URL: http://jira.codehaus.org/browse/MANTTASKS-86
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
>Affects Versions: 2.0.6
>Reporter: Werner Guttmann
> Attachments: build.bat, build.xml, pom.xml
>
>
> I am trying to use the Ant task for Maven with the root Maven POM for
> the Castor project for download the dependencies and place them into a
> lib directory.
> What I have observed is that there's a few dependencies missing when I
> run the corresponding Ant target. But if I use Maven for the build
> process, the missing JARs are downloaded as well and placed into my
> local repository.
> I have tried to define remoteRepository entries for the java.net and the
> Maven 2 java.net repositories (where e.g. java.transaction:jta:1.1.1B
> resides), but this does not make a difference.
> Any idea what I could try in addition ? Having said that, all other
> dependencies are resolved and copied without any problems. It looks like
> it's just the dependencies that are not synced globally that create a
> problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MANTTASKS-86) Resolution of java.net dependencies
[ http://jira.codehaus.org/browse/MANTTASKS-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Guttmann reopened MANTTASKS-86: -- > Resolution of java.net dependencies > --- > > Key: MANTTASKS-86 > URL: http://jira.codehaus.org/browse/MANTTASKS-86 > Project: Maven 2.x Ant Tasks > Issue Type: Bug >Affects Versions: 2.0.6 >Reporter: Werner Guttmann > Attachments: build.bat, build.xml, pom.xml > > > I am trying to use the Ant task for Maven with the root Maven POM for > the Castor project for download the dependencies and place them into a > lib directory. > What I have observed is that there's a few dependencies missing when I > run the corresponding Ant target. But if I use Maven for the build > process, the missing JARs are downloaded as well and placed into my > local repository. > I have tried to define remoteRepository entries for the java.net and the > Maven 2 java.net repositories (where e.g. java.transaction:jta:1.1.1B > resides), but this does not make a difference. > Any idea what I could try in addition ? Having said that, all other > dependencies are resolved and copied without any problems. It looks like > it's just the dependencies that are not synced globally that create a > problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
