[jira] Updated: (MNG-3475) Some directories are not basedir aligned
[
http://jira.codehaus.org/browse/MNG-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-3475:
---
Attachment: base-directory-alignment.patch
Overlooked unalignment.
> Some directories are not basedir aligned
>
>
> Key: MNG-3475
> URL: http://jira.codehaus.org/browse/MNG-3475
> Project: Maven 2
> Issue Type: Bug
> Components: POM
>Affects Versions: 2.0.8
>Reporter: Benjamin Bentmann
> Attachments: base-directory-alignment.patch
>
>
> The output from
> {code:xml}
> ${project.build.sourceDirectory}
> ${project.build.testSourceDirectory}
> ${project.build.scriptSourceDirectory}
> ${project.build.directory}
> ${project.build.outputDirectory}
> ${project.build.testOutputDirectory}
> ${project.reporting.outputDirectory}
> {code}
> delivers something like
> {noformat}
> [echo] M:\maven\z\antrun\src\main\java
> [echo] M:\maven\z\antrun\src\test\java
> [echo] src/main/scripts
> [echo] M:\maven\z\antrun\target
> [echo] M:\maven\z\antrun\target\classes
> [echo] M:\maven\z\antrun\target\test-classes
> [echo] target/site
> {noformat}
> revealing that neither the script source directory nor the reporting output
> directory are basedir aligned.
--
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-3475) Some directories are not basedir aligned
[
http://jira.codehaus.org/browse/MNG-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-3475:
---
Attachment: (was: base-directory-alignment.patch)
> Some directories are not basedir aligned
>
>
> Key: MNG-3475
> URL: http://jira.codehaus.org/browse/MNG-3475
> Project: Maven 2
> Issue Type: Bug
> Components: POM
>Affects Versions: 2.0.8
>Reporter: Benjamin Bentmann
> Attachments: base-directory-alignment.patch
>
>
> The output from
> {code:xml}
> ${project.build.sourceDirectory}
> ${project.build.testSourceDirectory}
> ${project.build.scriptSourceDirectory}
> ${project.build.directory}
> ${project.build.outputDirectory}
> ${project.build.testOutputDirectory}
> ${project.reporting.outputDirectory}
> {code}
> delivers something like
> {noformat}
> [echo] M:\maven\z\antrun\src\main\java
> [echo] M:\maven\z\antrun\src\test\java
> [echo] src/main/scripts
> [echo] M:\maven\z\antrun\target
> [echo] M:\maven\z\antrun\target\classes
> [echo] M:\maven\z\antrun\target\test-classes
> [echo] target/site
> {noformat}
> revealing that neither the script source directory nor the reporting output
> directory are basedir aligned.
--
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: (MANT-38) Use reporting output directory configured in POM
Use reporting output directory configured in POM
Key: MANT-38
URL: http://jira.codehaus.org/browse/MANT-38
Project: Maven 2.x Ant Plugin
Issue Type: Improvement
Affects Versions: 2.0
Reporter: Benjamin Bentmann
Priority: Minor
{{maven-build.xml}} hardcodes {{${maven.build.dir\}/site}} instead of
evaluating {{${project.reporting.outputDirectory\}}}.
--
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: (MANT-38) Use reporting output directory configured in POM
[
http://jira.codehaus.org/browse/MANT-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MANT-38.
-
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 2.1
Fixed in [r639969|http://svn.apache.org/viewvc?view=rev&revision=639969].
> Use reporting output directory configured in POM
>
>
> Key: MANT-38
> URL: http://jira.codehaus.org/browse/MANT-38
> Project: Maven 2.x Ant Plugin
> Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 2.1
>
>
> {{maven-build.xml}} hardcodes {{${maven.build.dir\}/site}} instead of
> evaluating {{${project.reporting.outputDirectory\}}}.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3478) Use expression ${project.build.directory} instead of hard-coding "target" in super POM
Use expression ${project.build.directory} instead of hard-coding "target" in
super POM
--
Key: MNG-3478
URL: http://jira.codehaus.org/browse/MNG-3478
Project: Maven 2
Issue Type: Improvement
Components: POM
Affects Versions: 2.0.8
Reporter: Benjamin Bentmann
Priority: Trivial
Attachments: project-build-dir.patch
The super POM hard-codes several paths to "target/...". Re-using
{{project.build.directory}} for those paths would ease customization.
--
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: (MANT-39) Always specify source/target options for javac
Always specify source/target options for javac -- Key: MANT-39 URL: http://jira.codehaus.org/browse/MANT-39 Project: Maven 2.x Ant Plugin Issue Type: Bug Affects Versions: 2.0 Reporter: Benjamin Bentmann Priority: Minor The [maven-compiler-plugin|http://maven.apache.org/plugins/maven-compiler-plugin/] defaults to source=1.3 and target=1.1. In constrast, Ant's [javac tasks|http://ant.apache.org/manual/CoreTasks/javac.html] defaults to the setting of the executing JVM. -- 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: (MANT-39) Always specify source/target options for javac
[ http://jira.codehaus.org/browse/MANT-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MANT-39. - Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 2.1 Fixed in [r639986|http://svn.apache.org/viewvc?view=rev&revision=639986]. > Always specify source/target options for javac > -- > > Key: MANT-39 > URL: http://jira.codehaus.org/browse/MANT-39 > Project: Maven 2.x Ant Plugin > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 2.1 > > > The > [maven-compiler-plugin|http://maven.apache.org/plugins/maven-compiler-plugin/] > defaults to source=1.3 and target=1.1. In constrast, Ant's [javac > tasks|http://ant.apache.org/manual/CoreTasks/javac.html] defaults to the > setting of the executing JVM. -- 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: (MANT-40) Use includes/excludes configured for Surefire when running tests
Use includes/excludes configured for Surefire when running tests
Key: MANT-40
URL: http://jira.codehaus.org/browse/MANT-40
Project: Maven 2.x Ant Plugin
Issue Type: Improvement
Affects Versions: 2.0
Reporter: Benjamin Bentmann
Right now, the includes/excludes for tests are hard-coded to
{code:xml}
{code}
This should be taken from the [Surefire
config|http://maven.apache.org/plugins/maven-surefire-plugin/examples/inclusion-exclusion.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] Closed: (MANT-40) Use includes/excludes configured for Surefire when running tests
[
http://jira.codehaus.org/browse/MANT-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MANT-40.
-
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 2.1
Fixed in [r639990|http://svn.apache.org/viewvc?view=rev&revision=639990].
> Use includes/excludes configured for Surefire when running tests
>
>
> Key: MANT-40
> URL: http://jira.codehaus.org/browse/MANT-40
> Project: Maven 2.x Ant Plugin
> Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
> Fix For: 2.1
>
>
> Right now, the includes/excludes for tests are hard-coded to
> {code:xml}
>
>
> {code}
> This should be taken from the [Surefire
> config|http://maven.apache.org/plugins/maven-surefire-plugin/examples/inclusion-exclusion.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] Closed: (MANT-7) "test" target should support running a single test - just like mvn test does
[ http://jira.codehaus.org/browse/MANT-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MANT-7. Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 2.1 Fixed in [r640004|http://svn.apache.org/viewvc?view=rev&revision=640004] as proposed by Matt. > "test" target should support running a single test - just like mvn test does > > > Key: MANT-7 > URL: http://jira.codehaus.org/browse/MANT-7 > Project: Maven 2.x Ant Plugin > Issue Type: Improvement >Reporter: Matt Raible >Assignee: Benjamin Bentmann > Fix For: 2.1 > > > > > > > > > > > > > > -- 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: (MANT-6) "test" targets should fail if junit.jar not present
[
http://jira.codehaus.org/browse/MANT-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MANT-6.
Assignee: Benjamin Bentmann
Resolution: Won't Fix
Fix Version/s: 2.1
bq. IMO, it's better to fail than to not run the tests.
That might have been a good choice for the initial design of the plugin.
Introducing this behavior now would cause unexpected build failures for
existing users so we should stick with the simple warning.
Nevertheless, one can always make the build fail by customizing the
{{build.xml}}. I extended the site docs in
[r640016|http://svn.apache.org/viewvc?view=rev&revision=640016] to provide a
copy&paste snippet for this.
> "test" targets should fail if junit.jar not present
> ---
>
> Key: MANT-6
> URL: http://jira.codehaus.org/browse/MANT-6
> Project: Maven 2.x Ant Plugin
> Issue Type: Improvement
>Reporter: Matt Raible
>Assignee: Benjamin Bentmann
> Fix For: 2.1
>
>
> IMO, it's better to fail than to not run the tests.
> property="junit.present"/>
>
--
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: (MPIR-86) Customizable Team list report
[ http://jira.codehaus.org/browse/MPIR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg moved MSITE-198 to MPIR-86: --- Affects Version/s: (was: 2.0-beta-5) Key: MPIR-86 (was: MSITE-198) Project: Maven 2.x Project Info Reports Plugin (was: Maven 2.x Site Plugin) > Customizable Team list report > - > > Key: MPIR-86 > URL: http://jira.codehaus.org/browse/MPIR-86 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement >Reporter: Roberto Lo Giacco > > It would be nice and useful to allow for Team list report customization at > least in terms of which columns to display and which to hide. > In my experience the URL, Organization,Organization URL, Time Zone, Actual > Time (GMT) and Properties columns are pratically unused and eats space. > In an optimal view it would be practical to include only columns for which > there is at least a value in one of the rows, automatically excluding the > columns never valorized. > If you can redirect me and give some hints I can contribute myself the > correction. -- 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: (MPIR-87) Show repositories an artifact is deployed to as a report
[ http://jira.codehaus.org/browse/MPIR-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg moved MSITE-214 to MPIR-87: --- Affects Version/s: (was: 2.0-beta-5) Key: MPIR-87 (was: MSITE-214) Project: Maven 2.x Project Info Reports Plugin (was: Maven 2.x Site Plugin) > Show repositories an artifact is deployed to as a report > > > Key: MPIR-87 > URL: http://jira.codehaus.org/browse/MPIR-87 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Environment: All >Reporter: Tim Pizey > > Google can get one to the website for an artifact, but discovering which > repository it is deployed to seems to rely upon asking on IRC, > extracting the target repositories and creating a standard report would fix > this. -- 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-306) [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader.
[ http://jira.codehaus.org/browse/MSITE-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-306. - Resolution: Incomplete > [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in > any resource loader. > > > Key: MSITE-306 > URL: http://jira.codehaus.org/browse/MSITE-306 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 >Reporter: Alexandre Navarro >Priority: Minor > > I always get the error below: > [INFO] Velocimacro : initialization starting. > [INFO] Velocimacro : adding VMs from VM library template : > VM_global_library.vm > [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in > any resource loader. > [INFO] Velocimacro : error using VM library template VM_global_library.vm : > org.apache.velocity.exception.ResourceNotFoundException: Unable to find > resource 'VM_global_library.vm' > [INFO] Velocimacro : VM library template macro registration complete. > this does not seem to affect my site generation. > I get rid of this because my build server (Luntbuild/Quickbuild) thinks there > is an error. > thanks, > Alexandre > PS : The same bug was reported before > http://jira.codehaus.org/browse/MSITE-286 > normally it mght be fixed in 2.0-beta-6 but it not true (not 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] Closed: (MSITE-272) Too much irrelevant information generated at INFOduring execution of Site goal
[
http://jira.codehaus.org/browse/MSITE-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MSITE-272.
-
Resolution: Incomplete
> Too much irrelevant information generated at INFOduring execution of Site goal
> --
>
> Key: MSITE-272
> URL: http://jira.codehaus.org/browse/MSITE-272
> Project: Maven 2.x Site Plugin
> Issue Type: Improvement
>Affects Versions: 2.0-beta-5, 2.0-beta-6
>Reporter: William Ferguson
>
> Executing 'mvn site:site' generates a lot of noise, much of it internal
> Velocity engine debug which is output at INFO level in the plugin.
> Example (taken from the staging of 2.0-beta-6):
> {code}
> D:\Modules\hubbub-log4j>mvn site
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Building hubbub-log4j
> [INFO]task-segment: [site]
> [INFO]
>
> [INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking for
> updates from maven-staging
> [INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking for
> updates from central
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-site-plugin/2.0-beta-6/maven-site-plugin-2.0-beta-6.pom
> Downloading:
> http://people.apache.org/~dennisl/staging-repository-site-plugin//org/apache/maven/plugins/maven-site-plugin/2.0-beta-6/maven-site-plugin-2.0
> -beta-6.jar
> 118K downloaded
> [INFO] Setting property: classpath.resource.loader.class =>
> 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
> [INFO] Setting property: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [INFO] **
> [INFO] Starting Jakarta Velocity v1.4
> [INFO] RuntimeInstance initializing.
> [INFO] Default Properties File:
> org\apache\velocity\runtime\defaults\velocity.properties
> [INFO] Default ResourceManager initializing. (class
> org.apache.velocity.runtime.resource.ResourceManagerImpl)
> [INFO] Resource Loader Instantiated:
> org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
> [INFO] ClasspathResourceLoader : initialization starting.
> [INFO] ClasspathResourceLoader : initialization complete.
> [INFO] ResourceCache : initialized. (class
> org.apache.velocity.runtime.resource.ResourceCacheImpl)
> [INFO] Default ResourceManager initialization complete.
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach
> [INFO] Created: 20 parsers.
> [INFO] Velocimacro : initialization starting.
> [INFO] Velocimacro : adding VMs from VM library template :
> VM_global_library.vm
> [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in
> any resource loader.
> [INFO] Velocimacro : error using VM library template VM_global_library.vm :
> org.apache.velocity.exception.ResourceNotFoundException: Unable to find resou
> rce 'VM_global_library.vm'
> [INFO] Velocimacro : VM library template macro registration complete.
> [INFO] Velocimacro : allowInline = true : VMs can be defined inline in
> templates
> [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may
> NOT replace previous VM definitions
> [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be
> global in scope if allowed.
> [INFO] Velocimacro : initialization complete.
> [INFO] Velocity successfully started.
> [INFO] Setting property: classpath.resource.loader.class =>
> 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
> [INFO] Setting property: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [INFO] **
> [INFO] Starting Jakarta Velocity v1.4
> [INFO] RuntimeInstance initializing.
> [INFO] Default Properties File:
> org\apache\velocity\runtime\defaults\velocity.properties
> [INFO] Default ResourceManager initializing. (class
> org.apache.velocity.runtime.resource.ResourceManagerImpl)
> [INFO] Resource Loader Instantiated:
> org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
> [INFO] ClasspathResourceLoader : initialization starting.
> [INFO] ClasspathResourceLoader : initialization complete.
> [INFO] Re
[jira] Closed: (MSITE-235) named references don't work, regression from beta-5
[
http://jira.codehaus.org/browse/MSITE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MSITE-235.
-
Resolution: Won't Fix
Spaces are not allowed in anchors.
> named references don't work, regression from beta-5
> ---
>
> Key: MSITE-235
> URL: http://jira.codehaus.org/browse/MSITE-235
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-6
>Reporter: Brett Porter
>
> src/site/apt/guides/introduction/introduction-to-the-pom.apt
> May be because of spaces?
> This works in beta-5:
> * {{{introduction-to-the-pom.html#What is a POM}What is a POM}}?
> ...
> * {What is a POM}?
> But not in 2.0-SNAPSHOT.
--
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-202) Language bundle not found for empty pom project
[ http://jira.codehaus.org/browse/MSITE-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-202. - Resolution: Cannot Reproduce > Language bundle not found for empty pom project > --- > > Key: MSITE-202 > URL: http://jira.codehaus.org/browse/MSITE-202 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: internationalization >Reporter: Kenney Westerhof > > for a POM project, no modules, no src/site, the following error is generated: > Added 'maven-site-plugin/src/test/projects/site-plugin-test13/'. > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Unnamed - > org.apache.maven.plugins.site-plugin-test:site-plugin-test12:pom:1.0 > [INFO]task-segment: [site] > [INFO] > > [WARNING] Unable to get resource > 'org.apache.maven.plugins:maven-plugins:pom:4-SNAPSHOT' from repository > java.net (https://maven-repository.dev.java.net/nonav/repository/) > [WARNING] POM for 'commons-collections:commons-collections:pom:3.1:runtime' > is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 > POM. > [INFO] Setting property: classpath.resource.loader.class => > 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. > [INFO] Setting property: velocimacro.messages.on => 'false'. > [INFO] Setting property: resource.loader => 'classpath'. > [INFO] Setting property: resource.manager.logwhenfound => 'false'. > [INFO] [site:site] > [INFO] artifact org.apache.maven.skins:maven-default-skin: checking for > updates from java.net > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] Can't find bundle for base name site-plugin, locale en > [INFO] > > [INFO] Trace > java.util.MissingResourceException: Can't find bundle for base name > site-plugin, locale en > at > org.codehaus.plexus.i18n.DefaultI18N.cacheBundle(DefaultI18N.java:394) > at > org.codehaus.plexus.i18n.DefaultI18N.getBundle(DefaultI18N.java:157) > at > org.codehaus.plexus.i18n.DefaultI18N.getString(DefaultI18N.java:206) > at > org.apache.maven.plugins.site.AbstractSiteMojo.populateReportsMenu(AbstractSiteMojo.java:412) > at > org.apache.maven.plugins.site.AbstractSiteRenderingMojo.locateDocuments(AbstractSiteRenderingMojo.java:608) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:116) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:95) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:435) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:391) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:178) > at > org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:797) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:404) > 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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351) > [INFO] > > [INFO] Total time: 11 seconds > [INFO] Finished at: Mon Dec 18 10:50:53 CET 2006 > [INFO] Fina
[jira] Closed: (MSITE-199) Add publishDate position "none"
[ http://jira.codehaus.org/browse/MSITE-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-199. - Assignee: Dennis Lundberg Resolution: Fixed Fix Version/s: 2.0-beta-7 Added this to the documentation. > Add publishDate position "none" > --- > > Key: MSITE-199 > URL: http://jira.codehaus.org/browse/MSITE-199 > Project: Maven 2.x Site Plugin > Issue Type: Improvement > Components: site descriptor >Affects Versions: 2.0-beta-5 >Reporter: Jukka Zitting >Assignee: Dennis Lundberg >Priority: Trivial > Fix For: 2.0-beta-7 > > > The current examples/sitedescriptor page only documents the values left, > right, navigation-top, navigation-bottom, and bottom for the "position" > option of the element. It would be nice to also be able to > disable the publish date. > It turns out that the current default template in doxia-site-renderer will > work perfectly if given the position option "none", since it doesn't match > any of the predefined alternatives. > > I'd like to propose documenting this behaviour in examples/sitedescriptor and > adding a note about the option in the doxia source. -- 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-10) add rsync deploy to site
[ http://jira.codehaus.org/browse/MSITE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-10: - Issue Type: New Feature (was: Bug) > add rsync deploy to site > > > Key: MSITE-10 > URL: http://jira.codehaus.org/browse/MSITE-10 > Project: Maven 2.x Site Plugin > Issue Type: New Feature > Components: site:deploy >Reporter: Brett Porter > -- 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-143) SCP works for deploy goal, but not for site-deploy
[ http://jira.codehaus.org/browse/MSITE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-143. - Assignee: Dennis Lundberg Resolution: Duplicate Fix Version/s: 2.0-beta-7 > SCP works for deploy goal, but not for site-deploy > -- > > Key: MSITE-143 > URL: http://jira.codehaus.org/browse/MSITE-143 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: site:deploy >Affects Versions: 2.0-beta-5 >Reporter: Jacob Robertson >Assignee: Dennis Lundberg > Fix For: 2.0-beta-7 > > Attachments: patch-MSITE-143.txt > > > The linux admins did everything necessary to get the deploy goal to work, and > now I have to go back to them and try and figure out why the "site-deploy" > goal says "Auth failed". Why does deploy work just fine with scp, but not > site-deploy? My environment is such that my deploy repository and my deploy > site directories are in the same parent directory, and have the exact same > permissions. But one goal fails to upload, and the other doesn't... -- 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-163) The modules menu is not inherited
[ http://jira.codehaus.org/browse/MSITE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-163: -- Summary: The modules menu is not inherited (was: site modules menu does not inherit) > The modules menu is not inherited > - > > Key: MSITE-163 > URL: http://jira.codehaus.org/browse/MSITE-163 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: inheritance >Affects Versions: 2.0-beta-4 > Environment: ubuntu linux / debian linux >Reporter: Andrew Williams > Fix For: 2.0-beta-7 > > > if I have a site.xml in a parent project that contains the line ref="modules" inherit="top" /> it is not inherited by child projects. > works, as does parent. > This happens when the parent project has no modules of its own. -- 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-131) Not inheriting the site settings for distributionManagement from a super pom
[ http://jira.codehaus.org/browse/MSITE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128269#action_128269 ] Dennis Lundberg commented on MSITE-131: --- Can someone please attach a small project that reproduces this issue? > Not inheriting the site settings for distributionManagement from a super pom > > > Key: MSITE-131 > URL: http://jira.codehaus.org/browse/MSITE-131 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: inheritance >Reporter: Malcolm Wong Ho > -- 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: (MJAVADOC-181) Javadoc report not generated for multi-module project if run from parent level.
[ http://jira.codehaus.org/browse/MJAVADOC-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg moved MSITE-309 to MJAVADOC-181: Affects Version/s: (was: 2.0-beta-6) Component/s: (was: multi module) Key: MJAVADOC-181 (was: MSITE-309) Project: Maven 2.x Javadoc Plugin (was: Maven 2.x Site Plugin) > Javadoc report not generated for multi-module project if run from parent > level. > --- > > Key: MJAVADOC-181 > URL: http://jira.codehaus.org/browse/MJAVADOC-181 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug > Environment: W2K, JDK 6u5, Maven 2.0.8 >Reporter: André Fügenschuh > Attachments: maven-site-javadoc-testcase.zip > > > For the following project design (s. attached testcase): > parent > \- library// javadoc:aggregate! > \- module-a > \- module-b > \- application > javadoc report for 'library' is *not* generated (not invoked), if 'mvn site' > is > called at 'parent' level (but is properly done if run at 'library' level > itself). -- 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-25) mvn site:site ignores server configuration in settings.xml
[ http://jira.codehaus.org/browse/MSITE-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Akolkar updated MSITE-25: --- Attachment: MSITE-25-02.patch Thanks for taking a look at this. Your changes make sense to me, but you have introduced a bug in the process of making those modifications. Specifically, the key for all entries added to the serverConfigurationMap is now the required repositoryId, and effectively that means the last non-null configuration from the settings in iteration order is returned as the configuration. Please reopen this ticket and apply the one liner patch attached as MSITE-25-02.patch Thanks again for your time. > mvn site:site ignores server configuration in settings.xml > -- > > Key: MSITE-25 > URL: http://jira.codehaus.org/browse/MSITE-25 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Reporter: Alan Cabrera >Assignee: Dennis Lundberg >Priority: Critical > Fix For: 2.0-beta-7 > > Attachments: MSITE-25-01.patch, MSITE-25-02.patch, > MSITE-25.sample.pom.xml, MSITE-25.settings.xml.fragment.txt, MSITE-25.txt, > patch-MSITE-25-artifact-manager.diff, patch-MSITE-25-site-plugin.diff > > > mvn site:site ignores parts of my settings.xml: > > livetribe-website > 664 > 775 > > plink > pscp > > livetribe > > It uses the username when ssh but does not invoke plink. > [INFO] [site:deploy] > Using private key: C:\Documents and Settings\adc\.ssh\id_dsa > scpexe://repo.livetribe.org/home/projects/livetribe/public_html/maven/ - > Session: Opened > Executing command: ssh -i "C:\Documents and Settings\adc\.ssh\id_dsa" -o > "BatchMode yes" [EMAIL PROTECTED] "mkdir -p > /home/projects/livetribe/public_html/maven/." > scpexe://repo.livetribe.org/home/projects/livetribe/public_html/maven/ - > Session: Disconnecting > scpexe://repo.livetribe.org/home/projects/livetribe/public_html/maven/ - > Session: Disconnected -- 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-25) mvn site:site ignores server configuration in settings.xml
[ http://jira.codehaus.org/browse/MSITE-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128272#action_128272 ] Dennis Lundberg commented on MSITE-25: -- Thanks for catching that Rahul. Your second patch has now been applied and a new SNAPSHOT has been deployed. > mvn site:site ignores server configuration in settings.xml > -- > > Key: MSITE-25 > URL: http://jira.codehaus.org/browse/MSITE-25 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Reporter: Alan Cabrera >Assignee: Dennis Lundberg >Priority: Critical > Fix For: 2.0-beta-7 > > Attachments: MSITE-25-01.patch, MSITE-25-02.patch, > MSITE-25.sample.pom.xml, MSITE-25.settings.xml.fragment.txt, MSITE-25.txt, > patch-MSITE-25-artifact-manager.diff, patch-MSITE-25-site-plugin.diff > > > mvn site:site ignores parts of my settings.xml: > > livetribe-website > 664 > 775 > > plink > pscp > > livetribe > > It uses the username when ssh but does not invoke plink. > [INFO] [site:deploy] > Using private key: C:\Documents and Settings\adc\.ssh\id_dsa > scpexe://repo.livetribe.org/home/projects/livetribe/public_html/maven/ - > Session: Opened > Executing command: ssh -i "C:\Documents and Settings\adc\.ssh\id_dsa" -o > "BatchMode yes" [EMAIL PROTECTED] "mkdir -p > /home/projects/livetribe/public_html/maven/." > scpexe://repo.livetribe.org/home/projects/livetribe/public_html/maven/ - > Session: Disconnecting > scpexe://repo.livetribe.org/home/projects/livetribe/public_html/maven/ - > Session: Disconnected -- 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-284) getRelativePath fails on non-normalized inputs
[ http://jira.codehaus.org/browse/MSITE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-284. - Assignee: Dennis Lundberg Resolution: Fixed Fix Version/s: 2.0-beta-7 The patch has been modified and applied to maven-doxia-tools, where this code now resides. Thanks! Please check r640091 that everything looks OK. > getRelativePath fails on non-normalized inputs > -- > > Key: MSITE-284 > URL: http://jira.codehaus.org/browse/MSITE-284 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: relative links >Affects Versions: 2.0-beta-6 >Reporter: Benjamin Bentmann >Assignee: Dennis Lundberg >Priority: Minor > Fix For: 2.0-beta-7 > > Attachments: normalized-paths.patch > > > The algo in AbstractSiteMojo.getRelativePath() assumes that its input paths > are both normalized and produces wrong output if it gets something like > "dir/../dir". Attached is a simple unit test and a fix for the method itself. > FYI, non-normalized path are easily created by Maven if one has a > non-Maven-like directory layout with > project/ > project-parent/ > project-module-1/ > where simple string/path concatenation produces a path like > "project/project-module-1/../project-parent" when referencing the parent POM > from the module POM. > Path/URL transformations like normalization/relativization/resolution are > quite ubiquitous in Maven. Isn't there a nice util class around that prevents > each and every plugin developer to reimplement those error-prone methods? -- 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-284) getRelativePath fails on non-normalized inputs
[ http://jira.codehaus.org/browse/MSITE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128276#action_128276 ] Benjamin Bentmann commented on MSITE-284: - bq. Please check r640091 that everything looks OK. Seems like. > getRelativePath fails on non-normalized inputs > -- > > Key: MSITE-284 > URL: http://jira.codehaus.org/browse/MSITE-284 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: relative links >Affects Versions: 2.0-beta-6 >Reporter: Benjamin Bentmann >Assignee: Dennis Lundberg >Priority: Minor > Fix For: 2.0-beta-7 > > Attachments: normalized-paths.patch > > > The algo in AbstractSiteMojo.getRelativePath() assumes that its input paths > are both normalized and produces wrong output if it gets something like > "dir/../dir". Attached is a simple unit test and a fix for the method itself. > FYI, non-normalized path are easily created by Maven if one has a > non-Maven-like directory layout with > project/ > project-parent/ > project-module-1/ > where simple string/path concatenation produces a path like > "project/project-module-1/../project-parent" when referencing the parent POM > from the module POM. > Path/URL transformations like normalization/relativization/resolution are > quite ubiquitous in Maven. Isn't there a nice util class around that prevents > each and every plugin developer to reimplement those error-prone methods? -- 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: (MANT-22) Make it possible to run the package target without tests
[ http://jira.codehaus.org/browse/MANT-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MANT-22. - Assignee: Benjamin Bentmann Resolution: Fixed Fixed in [r640113|http://svn.apache.org/viewvc?view=rev&revision=640113], by means of evaluating "maven.test.skip" as proposed by Vincent. > Make it possible to run the package target without tests > > > Key: MANT-22 > URL: http://jira.codehaus.org/browse/MANT-22 > Project: Maven 2.x Ant Plugin > Issue Type: Improvement >Affects Versions: 2.0-beta-1 > Environment: Gentoo Linux >Reporter: Petteri Räty >Assignee: Benjamin Bentmann > Fix For: 2.1 > > Attachments: maven-ant-plugin-dist-target.patch > > > When packaging stuff for Gentoo linux it is our packaging policy to give the > user the choice whether he/she wants to run the unit tests or not. Nowadays > as quite a few projects only use maven as their build system we use ant:ant > to generate build.xml files and do your packaging using that (at least until > we can get maven to properly build from source and integrate repositories to > our system etc. which has proved not so easy). The problem with the generated > build.xml files is that it always forces the tests for the package target. > For this reason I wrote a patch that changes the default target to dist that > just depends on the package and test targets. -- 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: (MNGSITE-43) Create writing style guidelines
Create writing style guidelines
---
Key: MNGSITE-43
URL: http://jira.codehaus.org/browse/MNGSITE-43
Project: Maven Project Web Site
Issue Type: New Feature
Reporter: Benjamin Bentmann
(The following text was ripped from MSITE-281)
Make changes (mostly typographic) intended to improve readability/consistency
of the documentation. Some of the rules I chose to follow are surely
controversial and a matter of taste:
- Hyperlinks should be readable/understandable without their surrounding
context (a best practice for web design, e.g. see [Stanford Online
Accessibility Program|http://soap.stanford.edu/show.php?contentid=46])
- Headline style capitalization for page/section titles (see also
[Capitalization of Headings and
Titles|http://www.tc-forum.org/topicmai/ml03capi.htm])
- Double quotation marks instead of single quots for quoted text ([Quotation
Marks and Direct
Quotations|http://www.informatics.sussex.ac.uk/department/docs/punctuation/node30.html])
- Proper casing for acronyms (e.g. POM instead of pom, but {{scp}} if one wants
to refer to the protocol part of a URL literally)
- Monospaced font for file/path names, URLs, plugin goals, command prompts
- Uppercase first letter for plugin names (it might just be my German habit,
but I consider "the Clean Plugin" more understandable than "the clean plugin"
since I can realize the reference to a name more quickly)
It might by worth to create some guidelines (house-style) that Maven developers
can follow for their documentation, similar to the [Maven Plugin Documentation
Standard|http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Documentation] and
the code formatter style.
--
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-281) Employ consistent typesetting/formatting
[
http://jira.codehaus.org/browse/MSITE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MSITE-281.
-
Assignee: Dennis Lundberg
Resolution: Fixed
Fix Version/s: 2.0-beta-7
Patch applied Thanks!
There were a couple of hunks that failed when I applied the patch, in index.apt
and faq.fml, but I think I managed to get them in manually.
I also reordered the plugin goals according to your suggestion.
As for the guidelines I opened another issue for that: MNGSITE-43.
> Employ consistent typesetting/formatting
>
>
> Key: MSITE-281
> URL: http://jira.codehaus.org/browse/MSITE-281
> Project: Maven 2.x Site Plugin
> Issue Type: Improvement
>Affects Versions: 2.0-beta-6
>Reporter: Benjamin Bentmann
>Assignee: Dennis Lundberg
>Priority: Minor
> Fix For: 2.0-beta-7
>
> Attachments: site.patch
>
>
> Well, typesetting/formatting surely belongs to the "peanuts" of life. This
> issue is a small attempt to raise sensibility for this topic.
> The attached patch contains various minor (mostly typographic) changes
> intended to improve readability/consistency of the documentation. Some of the
> rules I chose to follow are surely controversial and a matter of taste:
> - Hyperlinks should be readable/understandable without their surrounding
> context (a best practice for web design, e.g. see [Stanford Online
> Accessibility Program|http://soap.stanford.edu/show.php?contentid=46])
> - Headline style capitalization for page/section titles (see also
> [Capitalization of Headings and
> Titles|http://www.tc-forum.org/topicmai/ml03capi.htm])
> - Double quotation marks instead of single quots for quoted text ([Quotation
> Marks and Direct
> Quotations|http://www.informatics.sussex.ac.uk/department/docs/punctuation/node30.html])
> - Proper casing for acronyms (e.g. POM instead of pom, but {{scp}} if one
> wants to refer to the protocol part of a URL literally)
> - Monospaced font for file/path names, URLs, plugin goals, command prompts
> - Uppercase first letter for plugin names (it might just be my German habit,
> but I consider "the Clean Plugin" more understandable than "the clean plugin"
> since I can realize the reference to a name more quickly)
> Indepedently from the patch getting rejected or not, it might by worth to
> create some guidelines (house-style) that Maven developers can follow for
> their documentation, similar to the [Maven Plugin Documentation
> Standard|http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Documentation]
> and the code formatter style.
> @Dennis: I did not re-order the plugin goals in {{index.apt}} this time,
> although I would recommend so. To me, the current order seems quite random,
> e.g. why is site:site listed after site:deploy when one usually would invoke
> site:site first? I consider the following order (not optimal but just) more
> intuitiv as it groups related goals:
> - site:site
> - site:site-deploy
> - site:run
> - site:stage
> - site:stage-deploy
> - site:attach-descriptor
--
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: (MWAR-131) Ability to deploy the content of WEB-INF/classes as a classified artifact
[ http://jira.codehaus.org/browse/MWAR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128283#action_128283 ] Wendy Smoak commented on MWAR-131: -- Added a faq describing (but advising against) the new functionality. (r640119) IMO this contradicts the best practice of "one artifact per pom". And what will it mean to declare a dependency on a jar (with a classifier) when the associated pom has packaging=war? > Ability to deploy the content of WEB-INF/classes as a classified artifact > - > > Key: MWAR-131 > URL: http://jira.codehaus.org/browse/MWAR-131 > Project: Maven 2.x War Plugin > Issue Type: Improvement >Affects Versions: 2.1-alpha-1 >Reporter: Stephane Nicoll >Assignee: Stephane Nicoll > Fix For: 2.1-alpha-2 > > > If the server-side code of a war project need to be reused somewhere, we need > to deploy the content of the WEB-INF/classes to be able to use it as a > dependency -- 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-3478) Use expression ${project.build.directory} instead of hard-coding "target" in super POM
[
http://jira.codehaus.org/browse/MNG-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox closed MNG-3478.
--
Resolution: Won't Fix
I thought exactly the same when I was working with the super-pom. It doesn't
get interpolated correctly and breaks everything. I forget the exact error, but
it failed horribly when I tried to use that version.
> Use expression ${project.build.directory} instead of hard-coding "target" in
> super POM
> --
>
> Key: MNG-3478
> URL: http://jira.codehaus.org/browse/MNG-3478
> Project: Maven 2
> Issue Type: Improvement
> Components: POM
>Affects Versions: 2.0.8
>Reporter: Benjamin Bentmann
>Priority: Trivial
> Attachments: project-build-dir.patch
>
>
> The super POM hard-codes several paths to "target/...". Re-using
> {{project.build.directory}} for those paths would ease customization.
--
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: (MEV-579) org/hibernate/hibernate-tools maven-metadata.xml missing 3.2.x releases
[ http://jira.codehaus.org/browse/MEV-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-579. -- Assignee: Carlos Sanchez Resolution: Fixed > org/hibernate/hibernate-tools maven-metadata.xml missing 3.2.x releases > --- > > Key: MEV-579 > URL: http://jira.codehaus.org/browse/MEV-579 > Project: Maven Evangelism > Issue Type: Bug > Components: Invalid Metadata >Reporter: Jing Xue >Assignee: Carlos Sanchez > -- 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: (MEV-580) testng maven-metadata.xml missing 5.6 and 5.7 releases
[ http://jira.codehaus.org/browse/MEV-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-580. -- Assignee: Carlos Sanchez Resolution: Fixed > testng maven-metadata.xml missing 5.6 and 5.7 releases > -- > > Key: MEV-580 > URL: http://jira.codehaus.org/browse/MEV-580 > Project: Maven Evangelism > Issue Type: Bug > Components: Invalid Metadata >Reporter: Jing Xue >Assignee: Carlos Sanchez > -- 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: (MAVENUPLOAD-1946) Upload ImageInfo 1.9
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1946. --- Assignee: Carlos Sanchez Resolution: Incomplete > Upload ImageInfo 1.9 > > > Key: MAVENUPLOAD-1946 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1946 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: Michael Osipov >Assignee: Carlos Sanchez > > Version 1.9 contains important fixes. Upload is appreciated! -- 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: (MAVENUPLOAD-1957) GNU-HylaFAX
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1957. --- Assignee: Carlos Sanchez Resolution: Fixed > GNU-HylaFAX > --- > > Key: MAVENUPLOAD-1957 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1957 > Project: maven-upload-requests > Issue Type: Task >Reporter: Steven Jardine >Assignee: Carlos Sanchez > > I would like to add GNU-HylaFAX to the maven repository. I have set up a > repository on the sourceforge server. It is located at > scp://shell.sourceforge.net/home/groups/g/gn/gnu-hylafax/m2repo > Please add us to the automatic sync list. Thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1968) JDom 1.1 is out
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128288#action_128288 ] Carlos Sanchez commented on MAVENUPLOAD-1968: - please read the instructions http://maven.apache.org/guides/mini/guide-central-repository-upload.html > JDom 1.1 is out > --- > > Key: MAVENUPLOAD-1968 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1968 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: Mirko Steinle > > Hello! > JDom has released a major version (1.1) last november. Could you please > upload it? > All files can be found at http://www.jdom.org/ > Thank you very much. > Mirko > P.S. I am only a user of JDom, but I guess the team won't have anything > against seeing their latest release uploaded... -- 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: (MAVENUPLOAD-1967) "net.sf.flatpack","[EMAIL PROTECTED]:/home/groups/o/ob/objectlabkit/htdocs/m2-repo","rsync_ssh","Marcin Jekot","[EMAIL PROTECTED]",,
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1967. --- Assignee: Carlos Sanchez Resolution: Fixed > "net.sf.flatpack","[EMAIL > PROTECTED]:/home/groups/o/ob/objectlabkit/htdocs/m2-repo","rsync_ssh","Marcin > Jekot","[EMAIL PROTECTED]",, > - > > Key: MAVENUPLOAD-1967 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1967 > Project: maven-upload-requests > Issue Type: Task >Reporter: Marcin Jekot >Assignee: Carlos Sanchez > -- 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: (MAVENUPLOAD-1971) Please sync com.capgemini.platina groupId with central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1971. --- Assignee: Carlos Sanchez Resolution: Fixed fixed, but there is a new (easier) config for syncs for next time http://maven.apache.org/guides/mini/guide-central-repository-upload.html > Please sync com.capgemini.platina groupId with central > -- > > Key: MAVENUPLOAD-1971 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1971 > Project: maven-upload-requests > Issue Type: Wish >Reporter: nicolas de loof >Assignee: Carlos Sanchez > Attachments: platina.sh > > > I've created for my company (capgemini) some maven components and corporate > POM. > They're distributed under apache license, so I'd like them to get deployed on > central. -- 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: (MAVENUPLOAD-1978) Please add org.jsecurity to the automatically synch'd repos
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1978. --- Assignee: Carlos Sanchez Resolution: Fixed > Please add org.jsecurity to the automatically synch'd repos > --- > > Key: MAVENUPLOAD-1978 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1978 > Project: maven-upload-requests > Issue Type: Task >Reporter: Les Hazlewood >Assignee: Carlos Sanchez > > "org.jsecurity","[EMAIL > PROTECTED]:/home/groups/j/js/jsecurity/htdocs/m2repo","rsync_ssh","Les > Hazlewood","[EMAIL PROTECTED]",, > Thanks! > Les -- 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: (MAVENUPLOAD-1975) Please add org.dbunit to syched repos
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1975. --- Assignee: Carlos Sanchez Resolution: Fixed > Please add org.dbunit to syched repos > - > > Key: MAVENUPLOAD-1975 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1975 > Project: maven-upload-requests > Issue Type: Task >Reporter: Roberto Lo Giacco >Assignee: Carlos Sanchez > > "org.dbunit","[EMAIL > PROTECTED]:/home/groups/d/db/dbunit/htdocs/m2repo","rsync_ssh","Roberto Lo > Giacco","[EMAIL PROTECTED]",, -- 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: (MAVENUPLOAD-1962) gwt-rolodex (a cool, tiny image browsing widget for gwt) up on public maven
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1962. --- Assignee: Carlos Sanchez Resolution: Fixed > gwt-rolodex (a cool, tiny image browsing widget for gwt) up on public maven > --- > > Key: MAVENUPLOAD-1962 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1962 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Chris Jones >Assignee: Carlos Sanchez > Attachments: gwt-rolodex-1.1-bundle.jar > > > As far as the domain goes, I work for yesmail. The best I can do in terms of > proof is that I've put our demo applications for this widget on a yesmail > site: > http://devcenter.yesmail.com/com.yesmail.gwt.helpmoviedemo.RolodexDemoApp/RolodexDemoApp.html > Yesmail has also signed a corporate CLA with google for contributions to gwt > () > I've also attached the bundle file for convenience > Thanks! -- 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: (MAVENUPLOAD-1964) Upload Joda-Time jsptags 1.0.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1964. --- Assignee: Carlos Sanchez Resolution: Fixed you should setu pa autmoated synced repo, it will be easier for you and me > Upload Joda-Time jsptags 1.0.2 > -- > > Key: MAVENUPLOAD-1964 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1964 > Project: maven-upload-requests > Issue Type: Task >Reporter: Stephen Colebourne >Assignee: Carlos Sanchez > > http://joda-time.sourceforge.net/joda-time-jsptags-1.0.2-bundle.jar > http://joda-time.sourceforge.net/contrib/jsptags > http://joda-time.sourceforge.net/contrib/jsptags/team-list.html > > Bundle includes source and javadoc files for maven 2 -- 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: (MAVENUPLOAD-1963) Mockito 1.2 upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1963. --- Assignee: Carlos Sanchez Resolution: Fixed > Mockito 1.2 upload request > -- > > Key: MAVENUPLOAD-1963 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1963 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Igor Czechowski >Assignee: Carlos Sanchez > > http://mockito.googlecode.com/svn/branches/1.2/maven/mockito-all-1.2-bundle.jar > http://code.google.com/p/mockito/ > http://code.google.com/u/iczechowski/ > I'm a project member in Mockito and want to use the org.mockito groupId > You can see my name listed in Project members section at > http://code.google.com/p/mockito/ and additionally at > http://code.google.com/u/iczechowski/ > The bundle has no external dependencies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1965) Upload JMesa
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128291#action_128291 ] Carlos Sanchez commented on MAVENUPLOAD-1965: - your project uses dependencies that are not in the repo like xhtmlrenderer you need to request the upload of them first (in any case nobody can use your project as the deps are not present) > Upload JMesa > > > Key: MAVENUPLOAD-1965 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1965 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Jeff Johnston > > I was hoping that you could upload JMesa to the Maven repositories. > This is where the project can be found. > http://code.google.com/p/jmesa > My user name of extremecomponents is all over the project, but here is the > official link: > http://code.google.com/u/extremecomponents/ > I appreciate your help! > -Jeff Johnston -- 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: (MAVENUPLOAD-1969) Upload of NekoHTML 1.9.6.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1969. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload of NekoHTML 1.9.6.2 > -- > > Key: MAVENUPLOAD-1969 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1969 > Project: maven-upload-requests > Issue Type: Task >Reporter: Marc Guillemot >Assignee: Carlos Sanchez > > http://nekohtml.sourceforge.net/tmp/nekohtml-1.9.6.2-bundle.jar > http://nekohtml.sourceforge.net/ > Upload of new version of NekoHTML to allow it to be used (among others) by > HtmlUnit. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1961) rhino-js-1.7R1 upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128293#action_128293 ] Carlos Sanchez commented on MAVENUPLOAD-1961: - see http://maven.apache.org/guides/mini/guide-central-repository-upload.html > rhino-js-1.7R1 upload request > - > > Key: MAVENUPLOAD-1961 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1961 > Project: maven-upload-requests > Issue Type: Task >Reporter: Marc Guillemot >Assignee: Carlos Sanchez > > Downloaded from http://www.mozilla.org/rhino/download.html > New features in 1.7R1 can be found at > http://developer.mozilla.org/en/docs/New_in_Rhino_1.7R1 -- 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: (MAVENUPLOAD-1961) rhino-js-1.7R1 upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1961. --- Assignee: Carlos Sanchez Resolution: Fixed it takes time to do the manual uploads. You can setup an automatic repo for faster upload > rhino-js-1.7R1 upload request > - > > Key: MAVENUPLOAD-1961 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1961 > Project: maven-upload-requests > Issue Type: Task >Reporter: Marc Guillemot >Assignee: Carlos Sanchez > > Downloaded from http://www.mozilla.org/rhino/download.html > New features in 1.7R1 can be found at > http://developer.mozilla.org/en/docs/New_in_Rhino_1.7R1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1974) Upload Saxon 9.0.0.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128294#action_128294 ] Carlos Sanchez commented on MAVENUPLOAD-1974: - i can sync automatically net.sf.saxon from your account in the apache server from now on, but you need to check that everything is correct the poms For instance http://repo1.maven.org/maven2/net/sf/saxon/saxon-xpath/8.7/saxon-xpath-8.7.pom For reference this is the sync config "net.sf.saxon","[EMAIL PROTECTED]:/x1/home/rfeng/public_html/tuscany/maven","rsync_ssh","Luciano Resende","[EMAIL PROTECTED]",, > Upload Saxon 9.0.0.2 > > > Key: MAVENUPLOAD-1974 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1974 > Project: maven-upload-requests > Issue Type: Bug >Reporter: Luciano Resende > > The Tuscany project has a dependency on saxon 9.0.0.2 and needs it available > in a maven repo. > We have already contact the Saxon owner for authorization, and he said he is > OK, but won't do it. > > http://sourceforge.net/mailarchive/message.php?msg_id=46DAF629.8090908%40apache.org > Artifact information below > A temporary repository was created at : >http://people.apache.org/~rfeng/tuscany/maven/ > A archive is available at : >http://people.apache.org/~rfeng/tuscany/maven/saxon.tar.gz -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MAVENUPLOAD-1974) Upload Saxon 9.0.0.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128294#action_128294 ] carlos edited comment on MAVENUPLOAD-1974 at 3/22/08 11:40 PM: --- i can sync automatically net.sf.saxon from your account in the apache server from now on, but you need to check that everything is correct the poms For instance your saxon-xpath has no dependencies and the previous version does http://repo1.maven.org/maven2/net/sf/saxon/saxon-xpath/8.7/saxon-xpath-8.7.pom http://people.apache.org/~rfeng/tuscany/maven/net/sf/saxon/saxon-xpath/9.0.0.2/saxon-xpath-9.0.0.2.pom For reference this is the sync config "net.sf.saxon","[EMAIL PROTECTED]:/x1/home/rfeng/public_html/tuscany/maven","rsync_ssh","Luciano Resende","[EMAIL PROTECTED]",, was (Author: carlos): i can sync automatically net.sf.saxon from your account in the apache server from now on, but you need to check that everything is correct the poms For instance http://repo1.maven.org/maven2/net/sf/saxon/saxon-xpath/8.7/saxon-xpath-8.7.pom For reference this is the sync config "net.sf.saxon","[EMAIL PROTECTED]:/x1/home/rfeng/public_html/tuscany/maven","rsync_ssh","Luciano Resende","[EMAIL PROTECTED]",, > Upload Saxon 9.0.0.2 > > > Key: MAVENUPLOAD-1974 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1974 > Project: maven-upload-requests > Issue Type: Bug >Reporter: Luciano Resende > > The Tuscany project has a dependency on saxon 9.0.0.2 and needs it available > in a maven repo. > We have already contact the Saxon owner for authorization, and he said he is > OK, but won't do it. > > http://sourceforge.net/mailarchive/message.php?msg_id=46DAF629.8090908%40apache.org > Artifact information below > A temporary repository was created at : >http://people.apache.org/~rfeng/tuscany/maven/ > A archive is available at : >http://people.apache.org/~rfeng/tuscany/maven/saxon.tar.gz -- 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: (MAVENUPLOAD-1970) Karora Cooee 1.1 Upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1970. --- Assignee: Carlos Sanchez Resolution: Fixed > Karora Cooee 1.1 Upload > --- > > Key: MAVENUPLOAD-1970 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1970 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Daniel Murley >Assignee: Carlos Sanchez > > http://www.karora.org/maven-repository/bundles/cooee-1.1-bundle.jar > http://www.karora.org > http://www.karora.org/projects/cooee/team-list.html > Thank you! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1977) maven-license-plugin-1.2.1 upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128295#action_128295 ] Carlos Sanchez commented on MAVENUPLOAD-1977: - proof of owning the domain mathieucarbou.com ? see http://maven.apache.org/guides/mini/guide-central-repository-upload.html > maven-license-plugin-1.2.1 upload request > - > > Key: MAVENUPLOAD-1977 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1977 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Mathieu Carbou > Attachments: maven-license-plugin-1.2.1-bundle.jar, > maven-license-plugin-1.2.2-bundle.jar > > > -- Project URL: > http://code.google.com/p/maven-license-plugin/ > -- Project developer and owner: > Mathieu Carbou > [EMAIL PROTECTED] -- 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: (MAVENUPLOAD-1976) Please Upload SAC 1.3
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1976. --- Assignee: Carlos Sanchez Resolution: Fixed > Please Upload SAC 1.3 > - > > Key: MAVENUPLOAD-1976 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1976 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Daniel Gredler >Assignee: Carlos Sanchez > > SAC is a standard interface for CSS parsers from the W3C. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1973) Upload of maven-deployment-package-plugin
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128297#action_128297 ] Carlos Sanchez commented on MAVENUPLOAD-1973: - there is no requirements about name, just suggestions. if you still want to get it uploaded leave a comment > Upload of maven-deployment-package-plugin > - > > Key: MAVENUPLOAD-1973 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1973 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Siamak Haschemi > > http://kent.dl.sourceforge.net/sourceforge/mvn-dp-plugin/maven-deployment-package-plugin-0.1.0-bundle.jar > https://sourceforge.net/projects/mvn-dp-plugin/ > https://sourceforge.net/project/memberlist.php?group_id=221773 > I'm a developer in maven-deployment-package-plugin, please upload! -- 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-25) mvn site:site ignores server configuration in settings.xml
[ http://jira.codehaus.org/browse/MSITE-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128298#action_128298 ] Rahul Akolkar commented on MSITE-25: Thank you, I can confirm that the latest SNAPSHOT you deployed (specifically, 2.0-beta-7-20080322.205020-4 in the apache m2-snap-repo) fixes the problem for me. > mvn site:site ignores server configuration in settings.xml > -- > > Key: MSITE-25 > URL: http://jira.codehaus.org/browse/MSITE-25 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Reporter: Alan Cabrera >Assignee: Dennis Lundberg >Priority: Critical > Fix For: 2.0-beta-7 > > Attachments: MSITE-25-01.patch, MSITE-25-02.patch, > MSITE-25.sample.pom.xml, MSITE-25.settings.xml.fragment.txt, MSITE-25.txt, > patch-MSITE-25-artifact-manager.diff, patch-MSITE-25-site-plugin.diff > > > mvn site:site ignores parts of my settings.xml: > > livetribe-website > 664 > 775 > > plink > pscp > > livetribe > > It uses the username when ssh but does not invoke plink. > [INFO] [site:deploy] > Using private key: C:\Documents and Settings\adc\.ssh\id_dsa > scpexe://repo.livetribe.org/home/projects/livetribe/public_html/maven/ - > Session: Opened > Executing command: ssh -i "C:\Documents and Settings\adc\.ssh\id_dsa" -o > "BatchMode yes" [EMAIL PROTECTED] "mkdir -p > /home/projects/livetribe/public_html/maven/." > scpexe://repo.livetribe.org/home/projects/livetribe/public_html/maven/ - > Session: Disconnecting > scpexe://repo.livetribe.org/home/projects/livetribe/public_html/maven/ - > Session: Disconnected -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1972) please upload GWT 1.4.62
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128299#action_128299 ] Carlos Sanchez commented on MAVENUPLOAD-1972: - dont create bundles for things that are not bundles, put them in a repository to be synced (like the apache /home/nicolas/rsync-to-central) > please upload GWT 1.4.62 > > > Key: MAVENUPLOAD-1972 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1972 > Project: maven-upload-requests > Issue Type: Wish >Reporter: nicolas de loof > > Google guys just released GWT 1.4.62 > (http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/bd5cbb7a0d5b60aa/b85b6c2157aa26cb) > I'd like to update the codehaus GWT plugin to use this version > The bundle contains server and runtime jars + development jars for windows, > linux, mac and macOS leopard -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1976) Please Upload SAC 1.3
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128300#action_128300 ] Daniel Gredler commented on MAVENUPLOAD-1976: - Thanks Carlos! > Please Upload SAC 1.3 > - > > Key: MAVENUPLOAD-1976 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1976 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Daniel Gredler >Assignee: Carlos Sanchez > > SAC is a standard interface for CSS parsers from the W3C. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1977) maven-license-plugin-1.2.1 upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128301#action_128301 ] Mathieu Carbou commented on MAVENUPLOAD-1977: - Oups sorry, i forgot this point Since the project is hosted at http://code.google.com/p/maven-license-plugin/, would it be ok if it is renamed to com.google.code as for the package names and group id, so that it is deployed to: http://repo1.maven.org/maven2/com/google/code/maven-license-plugin (like Guice) Thanks ! > maven-license-plugin-1.2.1 upload request > - > > Key: MAVENUPLOAD-1977 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1977 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Mathieu Carbou > Attachments: maven-license-plugin-1.2.1-bundle.jar, > maven-license-plugin-1.2.2-bundle.jar > > > -- Project URL: > http://code.google.com/p/maven-license-plugin/ > -- Project developer and owner: > Mathieu Carbou > [EMAIL PROTECTED] -- 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
