[jira] Created: (MINVOKER-3) Invoker always returns 0 on Windows due to cmd.exe and exit /b in mvn.bat
Invoker always returns 0 on Windows due to cmd.exe and exit /b in mvn.bat - Key: MINVOKER-3 URL: http://jira.codehaus.org/browse/MINVOKER-3 Project: Maven 2.x Invoker Plugin Issue Type: Bug Environment: Windows XP Reporter: Barrie Treloar Assignee: John Casey Priority: Blocker Attachments: MVINOKER-3-patch.txt The mvn.bat file uses "exit /b %ERROR_CODE%" and as described in the mailing list discussion http://www.nabble.com/maven-invoker-plexus-utils%3A-Problems-with-Windows-and-%22cmd.exe%22-always-returning-0-exit-code.-tf3699374s177.html#a10347292 will cause cmd.exe to always return 0 (indicating success) instead of propagating the result code of the invoked command. Patch and unit tests included. Summary: Added "MAVEN_TERMINATE_CMD" set to "on" as environment variable for MavenCommandLineBuilder. While this is a Windows specific fix, it should not impact other environments. Upgraded CommandLine to use createArg instead of deprecated createArguments, in the process fixing all "FIXME"s. To fix PLXUTILS-31 require upgrade of plexus-utils org.codehaus.plexus plexus-utils 1.4.2-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] Commented: (NMAVEN-43) Deploy project artifacts
[ http://jira.codehaus.org/browse/NMAVEN-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95770 ] Evan Worley commented on NMAVEN-43: --- Shane, I haven't seen corruption but I am curious as to what could be going on. The only thing we changed in the assembly itself is the encoding of the VERSION-SNAPSHOT in the "informationalVersion" attribute of the AssemblyInfo. Let me know if there is anything we can do to help the investigation. -Evan > Deploy project artifacts > - > > Key: NMAVEN-43 > URL: http://jira.codehaus.org/browse/NMAVEN-43 > Project: NMaven > Issue Type: New Feature >Reporter: Shane Isbell > Attachments: deploy-patch.txt > > > The user can sync their built artifacts to a Maven repository -- 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: (MRRESOURCES-23) Introduce a parameter to define the scopes of the libraries to be included in the NOTICE licensing.
Introduce a parameter to define the scopes of the libraries to be included in
the NOTICE licensing.
---
Key: MRRESOURCES-23
URL: http://jira.codehaus.org/browse/MRRESOURCES-23
Project: Maven 2.x Remote Resources Plugin
Issue Type: Improvement
Affects Versions: 1.0-alpha-5
Reporter: Stefano Bagnara
Priority: Minor
I use the assembly plugin to create the following artifacts:
1) a source package including the whole source tree (including ALL the
dependencies: also test dep).
2) a binary jar only package
3) a binary + runtime dependencies package
I currently include the NOTICE/LICENSE by adding
{code}
target/maven-shared-archive-resources/META-INF/
/
NOTICE
LICENSE
{code}
it would be cool if the remote resource plugin could "better" collaborate with
the assembly plugin by including a correct NOTICE depending on assembled
depenendencies, but for basic usage it would be enough to have a parameter to
define what is the scope of the dependencies to be listed.
E.g: in my jar only distribution I don't need to make a list of runtime
depenendecies (I don't include them), in the binary package I only need to
include the runtime dependencies, in the complete-source distribution I need to
include test/compile/runtime dependencies disclaimers.
--
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: (MJAVADOC-94) The javadoc option "-sourcetab" should be passed as "-linksourcetab"
[
http://jira.codehaus.org/browse/MJAVADOC-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-94.
---
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 2.3
fixed
> The javadoc option "-sourcetab" should be passed as "-linksourcetab"
>
>
> Key: MJAVADOC-94
> URL: http://jira.codehaus.org/browse/MJAVADOC-94
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitry Katsubo
>Assignee: Vincent Siveton
>Priority: Trivial
> Fix For: 2.3
>
>
> I suppose, the following code
> {code:title=AbstractJavadocMojo.java}
> addArgIfNotEmpty( arguments, "-sourcetab", sourcetab, SINCE_JAVADOC_1_5 );
> {code}
> should be replaced with
> {code:title=AbstractJavadocMojo.java}
> addArgIfNotEmpty( arguments, "-linksourcetab", sourcetab, SINCE_JAVADOC_1_4_2
> );
> {code}
> However, I do not see this option in output of {{mvn -X javadoc:javadoc}}.
> Also, I think, that options {{-linksource}} and {{-linksourcetab}} should be
> added under equal conditions, but I am confused, that sources can be linked
> only in "online" mode -- just on the contary, sources are available offine.
> Or do I miss something 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] Closed: (MJAVADOC-95) Confusing and configuration options
[
http://jira.codehaus.org/browse/MJAVADOC-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-95.
---
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 2.3
It is only a Seperation of Concerns (Soc)
reportOutputDirectory implies that you configure a section in your
pom.
outputDirectory is more used by the configuration in the
section.
Default values are :
reportOutputDirectory = ${project.reporting.outputDirectory}/apidocs
outputDirectory = ${project.build.directory}/apidocs
jarOutputDirectory = ${project.build.directory}
> Confusing and configuration options
> -
>
> Key: MJAVADOC-95
> URL: http://jira.codehaus.org/browse/MJAVADOC-95
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Wish
>Affects Versions: 2.1
>Reporter: Dmitry Katsubo
>Assignee: Vincent Siveton
>Priority: Minor
> Fix For: 2.3
>
>
> There are two confoguration options, which are a bit confusing:
> * {{}} used by {{mvn javadoc:javadoc}}
> * {{}} used by {{mvn javadoc:jar}}
> Can they get an equal meaning and usage? Please, concider the
> [multiproject|http://maven.apache.org/plugins/maven-eclipse-plugin/reactor.html]
> configuration example below. The aim is to generate javadoc HTML and jar as
> follows:
> {noformat}
> my-project
> +- docs
> +- javadoc
> | +- my-lib-1.0
> | | +- index.html
> | | ...
> | +- my-lib-api-1.0
> | | +- index.html
> | | ...
> | +- my-lib-1.0-javadoc.jar
> | +- my-lib-api-1.0-javadoc.jar
> ...
> my-lib
> +- src
> | +- java
> +- target
> |
> ...
> my-lib-api
> +- src
> | +- java
> +- target
> |
> ...
> {noformat}
> I am using the following configuration in {{my-project/pom.xml}}:
> {code:xml}
>
>
>
> true
> org.apache.maven.plugins
> maven-javadoc-plugin
>
>
>
> ../my-project/docs/javadoc/${project.artifactId}-${project.version}
>
> ../my-project/docs/javadoc/${project.artifactId}-${project.version}
> ../my-project/docs/javadoc
> 1.5
> true
> 4
>
>
>
>
>
> ../my-lib
> ../my-lib-api
>
> {code}
--
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: (SCM-313) Check out command fails to report an error
Check out command fails to report an error
--
Key: SCM-313
URL: http://jira.codehaus.org/browse/SCM-313
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-provider-bazaar
Affects Versions: 1.0-rc1
Reporter: Kohsuke Kawaguchi
BazaarCheckOutCommand line 71 has the following code:
{noformat}
// Do the actual checkout
String[] checkout_cmd = new String[]{BRANCH_CMD, url,
checkoutDir.getAbsolutePath()};
BazaarConsumer checkout_consumer = new BazaarConsumer( getLogger() );
BazaarUtils.execute( checkout_consumer, getLogger(),
checkoutDir.getParentFile(), checkout_cmd );
// Do inventory to find list of checkedout files
String[] inventory_cmd = new String[]{INVENTORY_CMD};
BazaarCheckOutConsumer consumer = new BazaarCheckOutConsumer(
getLogger(), checkoutDir );
ScmResult result = BazaarUtils.execute( consumer, getLogger(),
checkoutDir, inventory_cmd );
return new CheckOutScmResult( consumer.getCheckedOutFiles(), result );
{noformat}
This code doesn't check for the error in the branch command, so when that fails
the error is not reported 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] Commented: (MSITE-194) xdoc's gets rendered in the HTML body, not in head
[ http://jira.codehaus.org/browse/MSITE-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95776 ] lacton commented on MSITE-194: -- The issue is in version 2.0.6 too. > xdoc's gets rendered in the HTML body, not in head > -- > > Key: MSITE-194 > URL: http://jira.codehaus.org/browse/MSITE-194 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 >Reporter: Brett Porter > Fix For: 2.0-beta-7 > > -- 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: (SCM-314) BazaarScmProviderRepository doesn't work with file URL on Windows
BazaarScmProviderRepository doesn't work with file URL on Windows
-
Key: SCM-314
URL: http://jira.codehaus.org/browse/SCM-314
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-provider-bazaar
Affects Versions: 1.0-rc1
Reporter: Kohsuke Kawaguchi
new BazaarScmProviderRepository("file:///c:/program
files/cygwin/tmp/test").getURI() returns "file://c:\program
files\cygwin\tmp\test", which Bazaar rejects as
{noformat}
bzr: ERROR: Invalid url supplied to transport: 'file://c:\\program
files\\cygwin\\tmp\\test/': Win32 UNC path urls have form file://HOST/path
{noformat}
Any reason why getURI() method is not implemented as follows?
{noformat}
public String getURI()
{
return orgUrl;
}
{noformat}
--
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: (MSITE-230) Spurious in generated section
Spurious in generated section --- Key: MSITE-230 URL: http://jira.codehaus.org/browse/MSITE-230 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 2.0-beta-6 Environment: Linux, java version "1.4.2-02" Reporter: lacton Priority: Minor The string "" appears before each element of the project.body.head tag of the site.xml file. Example follows. <-- pom.xml --> 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 org.hello hello 1.0 Hello <-- src/site/site.xml --> <-- index.html generated by 'mvn site' --> Hello - About ... ... -- 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: (MJAVADOC-106) Dependencies with scope "runtime" or "provided" are not used in the javadoc classpath
[ http://jira.codehaus.org/browse/MJAVADOC-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95777 ] Vincent Siveton commented on MJAVADOC-106: -- Christophe, Could you provide us a test case for this? I need to investigate... Thanks! > Dependencies with scope "runtime" or "provided" are not used in the javadoc > classpath > - > > Key: MJAVADOC-106 > URL: http://jira.codehaus.org/browse/MJAVADOC-106 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Christophe DENEUX > > Hi, > I have a class inherited from an hibernate class. So my project contains a > dependency onto Hibernate with the default scope, and an other dependencies > needed by Hibernate with scope=runtime and/or provided. > My javadoc plugin is configured to use the doclet Umlgraph. > At the report generation I have an error telling that classes are not found. > These classes are contained in dependencies with scope=runtime/provided. If I > change the scope to compile, that works fine. > After investigation in the source code, it seems to me that only dependencies > with scope=compile are used. > Can you take into account dependencies with scope=runtime/provided, or > propose configuration parameters to set these artifacts. > Christophe DENEUX > Capgemini Sud - France - Nice -- 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: (NMAVEN-43) Deploy project artifacts
[ http://jira.codehaus.org/browse/NMAVEN-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95780 ] Shane Isbell commented on NMAVEN-43: Okay, I found the problem. During a deploy the assembly, say NMaven.Logging-0.14-20070513.170342-4.dll, contained the pom.xml file, not the .NET assembly. The DeployMojo is using mavenProject.getFile() (the returned value is the pom file) as the artifact to deploy, instead of mavenProject.getArtifact().getFile() . I will check in the change and then we should be good to go. > Deploy project artifacts > - > > Key: NMAVEN-43 > URL: http://jira.codehaus.org/browse/NMAVEN-43 > Project: NMaven > Issue Type: New Feature >Reporter: Shane Isbell > Attachments: deploy-patch.txt > > > The user can sync their built artifacts to a Maven repository -- 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: (NMAVEN-52) As Part of Life-Cycle NMaven Should Verify That All Assemblies in Local Repo Are Valid
As Part of Life-Cycle NMaven Should Verify That All Assemblies in Local Repo Are Valid -- Key: NMAVEN-52 URL: http://jira.codehaus.org/browse/NMAVEN-52 Project: NMaven Issue Type: Improvement Reporter: Shane Isbell Priority: Minor As part of the life-cycle NMaven should verify that all assemblies entering the local repo (through resolving from a remote repo) and exiting the repo (deploying) are valid assemblies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MNG-2872) Don't append artifactId when parent pom already has artifactId in URL
[
http://jira.codehaus.org/browse/MNG-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95276
]
M. Rohrmoser edited comment on MNG-2872 at 5/13/07 1:12 PM:
I ran into this one, too.
despite http://maven.apache.org/guides/mini/guide-site.html saying
"Note: the trailing slash in the URL above indicates that any subprojects that
inherit this value should append their artifact ID to the path instead of using
it as-is."
this seems not to be honoured if the is
defined in a inherited (parent) pom.
was:
I ran into this one, too.
despite http://wiki.intranet.1and1.com/bin/view/GMXDev/DevSWI saying
"Note: the trailing slash in the URL above indicates that any subprojects that
inherit this value should append their artifact ID to the path instead of using
it as-is."
this seems not to be honoured if the is
defined in a inherited (parent) pom.
> Don't append artifactId when parent pom already has artifactId in URL
> -
>
> Key: MNG-2872
> URL: http://jira.codehaus.org/browse/MNG-2872
> Project: Maven 2
> Issue Type: Wish
>Affects Versions: 2.0.5
>Reporter: Papick G. Taboada
>Priority: Trivial
>
> I want to define the url for all my projects from one central pom. the pom
> project itself has the same url structure as the child projects.
> This is for all urls that can be inherited, e.g. distribution site,
> deployment url, etc.
> I would like to specify some complete url like
> protocol:/my.server.com/some/path/to/the/${groupId}/${artifactId}
> For example, with the actual implementation I get either the parent pom site
> deployed to the groupId directory, or I get the child projects deployed to
> the grouId/artifactId/artifactId directory.
> At the moment I have add the urls on every project, although they always have
> the same pattern.
--
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: (MINSTALL-18) Bad algorithm to decide if the main artifact is to be installed or not
[
http://jira.codehaus.org/browse/MINSTALL-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sanchez updated MINSTALL-18:
---
Fix Version/s: (was: 2.2)
2.3
> Bad algorithm to decide if the main artifact is to be installed or not
> --
>
> Key: MINSTALL-18
> URL: http://jira.codehaus.org/browse/MINSTALL-18
> Project: Maven 2.x Install Plugin
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Vincent Massol
> Fix For: 2.3
>
>
> Here' s what's in InstallMojo's execute method:
> {code}
> // Here, we have a temporary solution to MINSTALL-3
> (isDirectory() is true if it went through compile
> // but not package). We are designing in a proper solution
> for Maven 2.1
> if ( file != null && !file.isDirectory() )
> {
> installer.install( file, artifact, localRepository );
> }
> else if ( !attachedArtifacts.isEmpty() )
> {
> getLog().info( "No primary artifact to install,
> installing attached artifacts instead." );
> }
> {code}
> This fails if we're building a JAR with no sources but with an attached
> artifact and only the attached artifact is created (this is the case when
> using the clover plugin). In that case, the install mojo tries to install the
> main artifact which doesn't exist).
> The error is in "!file.isDirectory". In the case of a jar with no sources,
> this directory will not have been created...
--
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: (MINSTALL-37) Add support to force install:install to use a specific version
[ http://jira.codehaus.org/browse/MINSTALL-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez updated MINSTALL-37: --- Fix Version/s: (was: 2.2) 2.3 > Add support to force install:install to use a specific version > -- > > Key: MINSTALL-37 > URL: http://jira.codehaus.org/browse/MINSTALL-37 > Project: Maven 2.x Install Plugin > Issue Type: New Feature >Affects Versions: 2.2 >Reporter: Jason Dillon >Assignee: Brian Fox > Fix For: 2.3 > > Attachments: MINSTALL-37.diff > > > Allow the install:install goal to force the version of artifacts (including > attached). -- 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: (MINSTALL-30) Command Line parameter 'version' does not override pom file
[
http://jira.codehaus.org/browse/MINSTALL-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sanchez updated MINSTALL-30:
---
Fix Version/s: (was: 2.2)
2.3
> Command Line parameter 'version' does not override pom file
> ---
>
> Key: MINSTALL-30
> URL: http://jira.codehaus.org/browse/MINSTALL-30
> Project: Maven 2.x Install Plugin
> Issue Type: Bug
>Affects Versions: 2.1
> Environment: maven 2.0.4
> maven-install-plugin 2.1
>Reporter: Johan Fischer
> Fix For: 2.3
>
>
> Hi,
> I'm trying to override the version number in the pom using the CLI params
> -Dversion but the install plugin still uses the pom version creating a
> mismatched of the installed jar file:
> example:
> pom version: SHIP_VERSION
> {noformat}
> $ mvn -X -Dversion=1.4.1_2 install
> Error stacktraces are turned on.
> Maven version: 2.0.4
> [DEBUG] Building Maven user-level plugin registry from:
> '/home/jfischer/.m2/plugin-registry.xml'
> [DEBUG] Building Maven global-level plugin registry from:
> '/opt/maven/conf/plugin-registry.xml'
> [INFO] Scanning for projects...
> [DEBUG] Searching for parent-POM: cmss:parent::1.0.0-SNAPSHOT of project:
> cmss-libs:cmcrc-favlib:jar:SHIP_VERSION in relative path: ../pom.xml
> [DEBUG] Parent-POM: cmss:parent::1.0.0-SNAPSHOT not found in relative path:
> ../pom.xml
> [DEBUG] Retrieving parent-POM: cmss:parent::1.0.0-SNAPSHOT for project:
> cmss-libs:cmcrc-favlib:jar:SHIP_VERSION from the repository.
> [DEBUG] Skipping disabled repository central
> [DEBUG] parent: resolved to version 1.0.0-20060516.064917-2 from repository
> cmss
> [INFO]
>
> [INFO] Building Java SMARTS lib
> [INFO]task-segment: [install]
> [INFO]
>
> <--- snip --->
> DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-compiler-plugin:2.0.1:compile' -->
> [DEBUG] (f) basedir = /home/jfischer/cmcrc/cmss/libs/favlib
> [DEBUG] (f) buildDirectory = /home/jfischer/cmcrc/cmss/libs/favlib/target
> [DEBUG] (f) classpathElements =
> [/home/jfischer/cmcrc/cmss/libs/favlib/target/classes,
> /home/jfischer/.m2/repository/cmss-libs/jelte-util/1.0.0/jelte-util-1.0.0.j
> ar]
> [DEBUG] (f) compileSourceRoots =
> [/home/jfischer/cmcrc/cmss/libs/favlib/src/main/java]
> [DEBUG] (f) compilerId = javac
> [DEBUG] (f) debug = true
> [DEBUG] (f) fork = false
> [DEBUG] (f) optimize = false
> [DEBUG] (f) outputDirectory =
> /home/jfischer/cmcrc/cmss/libs/favlib/target/classes
> [DEBUG] (f) outputFileName = cmcrc-favlib-1.4.1_2
> [DEBUG] (f) projectArtifact = cmss-libs:cmcrc-favlib:jar:SHIP_VERSION
> [DEBUG] (f) showDeprecation = false
> [DEBUG] (f) showWarnings = false
> [DEBUG] (f) staleMillis = 0
> [DEBUG] (f) verbose = false
> [DEBUG] -- end configuration --
> <--- snip --->
> [DEBUG]
> org.apache.maven.plugins:maven-install-plugin:maven-plugin:2.1:runtime
> (selected for runtime)
> [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven:maven-project:jar:2.0:runtime (selected for
> runtime)
> [DEBUG]
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime
> (selected for runtime)
> [DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected
> for runtime)
> [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven:maven-profile:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven:maven-model:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven:maven-model:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0:runtime (selected
> for runtime)
> [DEBUG]
> org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime (selected
> for runtime)
> [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0:runtime
> (selected for runtime)
> [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0:runtime (selected
> for runtime)
> [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime
> (selected for runtime)
> [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0:runtime
> (selected for runtime)
> [DEBUG]
[jira] Closed: (MINSTALL-37) Add support to force install:install to use a specific version
[ http://jira.codehaus.org/browse/MINSTALL-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MINSTALL-37. - Resolution: Won't Fix The general consensus seems to be that this should not be added. > Add support to force install:install to use a specific version > -- > > Key: MINSTALL-37 > URL: http://jira.codehaus.org/browse/MINSTALL-37 > Project: Maven 2.x Install Plugin > Issue Type: New Feature >Affects Versions: 2.2 >Reporter: Jason Dillon >Assignee: Brian Fox > Fix For: 2.3 > > Attachments: MINSTALL-37.diff > > > Allow the install:install goal to force the version of artifacts (including > attached). -- 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: (MRM-329) The Reports link gives an HTTP 500
[
http://jira.codehaus.org/browse/MRM-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95787
]
Arnaud Heritier commented on MRM-329:
-
There's no common interface for reports data :-(
We can do something like that :
${report.name}
${result.groupId}:${result.artifactId}:${result.version}:${result.type} :
${result.message}
.
But it's not really nice
> The Reports link gives an HTTP 500
> --
>
> Key: MRM-329
> URL: http://jira.codehaus.org/browse/MRM-329
> Project: Archiva
> Issue Type: Bug
> Components: reporting
>Affects Versions: 1.0-alpha-1
>Reporter: Napoleon Esmundo C. Ramirez
>Assignee: Joakim Erdfelt
>Priority: Blocker
> Fix For: 1.0-alpha-1
>
>
> Clicking the Reports link in the side navigation menu displays the following
> (edited/snipped stacktrace):
> HTTP ERROR: 500
> RequestURI=/admin/reports.action
> Caused by: javax.el.PropertyNotFoundException: The class
> 'org.apache.maven.archiva.reporting.artifact.OldArtifactReport' does not have
> the property 'groupId'.
> at javax.el.BeanELResolver.getBeanProperty(BeanELResolver.java:574)
> at javax.el.BeanELResolver.getValue(BeanELResolver.java:280)
> at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:143)
> at com.sun.el.parser.AstValue.getValue(AstValue.java:118)
> at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:192)
> at
> org.apache.jasper.runtime.PageContextImpl.evaluateExpression(PageContextImpl.java:974)
> at
> org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp._jspx_meth_c_forEach_0(org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp:143)
> at
> org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp._jspService(org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp:85)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373)
--
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: (MRM-338) Fix dependencies convergence between archiva projects
Fix dependencies convergence between archiva projects - Key: MRM-338 URL: http://jira.codehaus.org/browse/MRM-338 Project: Archiva Issue Type: Task Affects Versions: 1.0-alpha-1 Reporter: Arnaud Heritier Priority: Minor commons-logging:commons-logging 1.0.4 org.apache.maven.archiva:archiva-webapp 1.1 org.apache.maven.archiva:archiva-database hsqldb:hsqldb 1.7.3.3 org.apache.maven.archiva:archiva-converter 1.8.0.7 org.apache.maven.archiva:archiva-artifact-reports org.apache.maven.archiva:archiva-database org.apache.maven.archiva:archiva-scheduled org.apache.derby:derby 10.1.3.1 org.apache.maven.archiva:archiva-plexus-runtime org.apache.maven.archiva:archiva-security org.apache.maven.archiva:archiva-webapp 10.2.1.6 org.apache.maven.archiva:archiva-database org.codehaus.plexus:plexus-component-api 1.0-alpha-20 org.apache.maven.archiva:archiva-common org.apache.maven.archiva:archiva-configuration org.apache.maven.archiva:archiva-converter org.apache.maven.archiva:archiva-plexus-runtime org.apache.maven.archiva:archiva-proxy org.apache.maven.archiva:archiva-repository-layer org.apache.maven.archiva:archiva-scheduled org.apache.maven.archiva:archiva-webapp 1.0-alpha-22 org.apache.maven.archiva:archiva-cli org.codehaus.plexus:plexus-container-default 1.0-alpha-20 org.apache.maven.archiva:archiva-artifact-reports org.apache.maven.archiva:archiva-common org.apache.maven.archiva:archiva-configuration org.apache.maven.archiva:archiva-converter org.apache.maven.archiva:archiva-database org.apache.maven.archiva:archiva-indexer org.apache.maven.archiva:archiva-metadata-reports org.apache.maven.archiva:archiva-model org.apache.maven.archiva:archiva-plexus-runtime org.apache.maven.archiva:archiva-project-reports org.apache.maven.archiva:archiva-proxy org.apache.maven.archiva:archiva-report-manager org.apache.maven.archiva:archiva-repository-layer org.apache.maven.archiva:archiva-scheduled org.apache.maven.archiva:archiva-webapp 1.0-alpha-22 org.apache.maven.archiva:archiva-cli It should be fixed by setting all versions in the parent pom using the dependencyManagement. -- 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: (NMAVEN-53) Creating New .NET Maven Plugins Should Not Require Adding an Entry within NMaven's net-dependencies.xml File
Creating New .NET Maven Plugins Should Not Require Adding an Entry within NMaven's net-dependencies.xml File Key: NMAVEN-53 URL: http://jira.codehaus.org/browse/NMAVEN-53 Project: NMaven Issue Type: New Feature Reporter: Shane Isbell The net-dependencies.xml file is used internally for NMaven to resolve .NET assemblies and .NET Maven plugins. Third-Party developers should be able to create there own net-dependencies.xml file (this would probably be auto-generated as part of the plugin generation) and have it read by NMaven. As it stands now, they have to either recompile NMaven or unjar dotnet-core, change the file and then repackage. -- 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: (NMAVEN-54) Support for Attaching Platform Metadata to Assemblies
Support for Attaching Platform Metadata to Assemblies - Key: NMAVEN-54 URL: http://jira.codehaus.org/browse/NMAVEN-54 Project: NMaven Issue Type: New Feature Reporter: Shane Isbell Priority: Minor This feature is a superset of classifer support. It will allow the developer to attach meta-data to the assembly, specifying a range of information, including targeted platform, OS, architecture, vendor, vendor version, framework version, java version, as well as custom attributes. Most of this info is already used within the compiler component but we now need a way for discovery and resolving of dependent assemblies based on this same info. Most likely, this will be an expansion of the net-dependencies.xml file. NMaven would need to look through an assemblies meta-data within the net-dependencies.xml file to decide if it should be included within a compile, test, resolve, etc. -- 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: (MRM-339) Roles aren't created if the repository isn't created within the web UI
Roles aren't created if the repository isn't created within the web UI -- Key: MRM-339 URL: http://jira.codehaus.org/browse/MRM-339 Project: Archiva Issue Type: Bug Affects Versions: 1.0-alpha-1 Reporter: Arnaud Heritier If we create some repositories directly in the archiva.xml config file, we don't have the roles to observe or manage these repositories. -- 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: (MRM-338) Fix dependencies convergence between archiva projects
[ http://jira.codehaus.org/browse/MRM-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MRM-338. --- Assignee: Arnaud Heritier Resolution: Fixed Fix Version/s: 1.0-alpha-1 All versions of dependencies are now set in the parent pom > Fix dependencies convergence between archiva projects > - > > Key: MRM-338 > URL: http://jira.codehaus.org/browse/MRM-338 > Project: Archiva > Issue Type: Task >Affects Versions: 1.0-alpha-1 >Reporter: Arnaud Heritier >Assignee: Arnaud Heritier >Priority: Minor > Fix For: 1.0-alpha-1 > > > commons-logging:commons-logging > 1.0.4 > org.apache.maven.archiva:archiva-webapp > 1.1 > org.apache.maven.archiva:archiva-database > hsqldb:hsqldb > 1.7.3.3 > org.apache.maven.archiva:archiva-converter > 1.8.0.7 > org.apache.maven.archiva:archiva-artifact-reports > org.apache.maven.archiva:archiva-database > org.apache.maven.archiva:archiva-scheduled > org.apache.derby:derby > 10.1.3.1 > org.apache.maven.archiva:archiva-plexus-runtime > org.apache.maven.archiva:archiva-security > org.apache.maven.archiva:archiva-webapp > 10.2.1.6 > org.apache.maven.archiva:archiva-database > org.codehaus.plexus:plexus-component-api > 1.0-alpha-20 > org.apache.maven.archiva:archiva-common > org.apache.maven.archiva:archiva-configuration > org.apache.maven.archiva:archiva-converter > org.apache.maven.archiva:archiva-plexus-runtime > org.apache.maven.archiva:archiva-proxy > org.apache.maven.archiva:archiva-repository-layer > org.apache.maven.archiva:archiva-scheduled > org.apache.maven.archiva:archiva-webapp > 1.0-alpha-22 > org.apache.maven.archiva:archiva-cli > org.codehaus.plexus:plexus-container-default > 1.0-alpha-20 > org.apache.maven.archiva:archiva-artifact-reports > org.apache.maven.archiva:archiva-common > org.apache.maven.archiva:archiva-configuration > org.apache.maven.archiva:archiva-converter > org.apache.maven.archiva:archiva-database > org.apache.maven.archiva:archiva-indexer > org.apache.maven.archiva:archiva-metadata-reports > org.apache.maven.archiva:archiva-model > org.apache.maven.archiva:archiva-plexus-runtime > org.apache.maven.archiva:archiva-project-reports > org.apache.maven.archiva:archiva-proxy > org.apache.maven.archiva:archiva-report-manager > org.apache.maven.archiva:archiva-repository-layer > org.apache.maven.archiva:archiva-scheduled > org.apache.maven.archiva:archiva-webapp > 1.0-alpha-22 > org.apache.maven.archiva:archiva-cli > It should be fixed by setting all versions in the parent pom using the > dependencyManagement. -- 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: (MRM-329) The Reports link gives an HTTP 500
[ http://jira.codehaus.org/browse/MRM-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95794 ] Arnaud Heritier commented on MRM-329: - The other type used here seems to be : ArchivaArtifact > The Reports link gives an HTTP 500 > -- > > Key: MRM-329 > URL: http://jira.codehaus.org/browse/MRM-329 > Project: Archiva > Issue Type: Bug > Components: reporting >Affects Versions: 1.0-alpha-1 >Reporter: Napoleon Esmundo C. Ramirez >Assignee: Joakim Erdfelt >Priority: Blocker > Fix For: 1.0-alpha-1 > > > Clicking the Reports link in the side navigation menu displays the following > (edited/snipped stacktrace): > HTTP ERROR: 500 > RequestURI=/admin/reports.action > Caused by: javax.el.PropertyNotFoundException: The class > 'org.apache.maven.archiva.reporting.artifact.OldArtifactReport' does not have > the property 'groupId'. > at javax.el.BeanELResolver.getBeanProperty(BeanELResolver.java:574) > at javax.el.BeanELResolver.getValue(BeanELResolver.java:280) > at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:143) > at com.sun.el.parser.AstValue.getValue(AstValue.java:118) > at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:192) > at > org.apache.jasper.runtime.PageContextImpl.evaluateExpression(PageContextImpl.java:974) > at > org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp._jspx_meth_c_forEach_0(org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp:143) > at > org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp._jspService(org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp:85) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373) -- 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: (MRM-212) configure checksum policy for proxied repository
[ http://jira.codehaus.org/browse/MRM-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak updated MRM-212: Fix Version/s: 0.9 > configure checksum policy for proxied repository > > > Key: MRM-212 > URL: http://jira.codehaus.org/browse/MRM-212 > Project: Archiva > Issue Type: Improvement > Components: remote proxy >Reporter: nicolas de loof >Priority: Critical > Fix For: 0.9, 1.0 > > Attachments: 2006-10-26-checksum-policy.patch, MRM-212.patch > > > Some artifact on repo1.maven.org have bad checksum. This need fix, but this > also make archiva not usable as a replacement for maven-proxy. > As maven itself allow to configure a checksum policy, a new configuration > parameter on proxied repo would be nice. -- 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: (MRM-340) release:prepare fails due to missing archiva-webapp
release:prepare fails due to missing archiva-webapp --- Key: MRM-340 URL: http://jira.codehaus.org/browse/MRM-340 Project: Archiva Issue Type: Bug Components: build Affects Versions: 0.9 Reporter: Wendy Smoak During release:prepare, the build fails with: [INFO] Building Archiva Web Application [INFO]task-segment: [clean, integration-test] ... [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.maven.archiva ArtifactId: archiva-applet Version: 0.9-alpha-2 Reason: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.archiva -DartifactId=archiva-applet -Dversion=0.9-alpha-2 -Dpackaging=jar -Dfile=/path/to/file org.apache.maven.archiva:archiva-applet:jar:0.9-alpha-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] Updated: (MRM-340) release:prepare fails due to missing archiva-applet
[ http://jira.codehaus.org/browse/MRM-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak updated MRM-340: Summary: release:prepare fails due to missing archiva-applet (was: release:prepare fails due to missing archiva-webapp) Arnaud determined that this is due to the 'provided' scope we use on the applet to keep it from being included in the webapp. He suggested adding a dependency on archiva-applet to the config for the dependency plugin. > release:prepare fails due to missing archiva-applet > --- > > Key: MRM-340 > URL: http://jira.codehaus.org/browse/MRM-340 > Project: Archiva > Issue Type: Bug > Components: build >Affects Versions: 0.9 >Reporter: Wendy Smoak > > During release:prepare, the build fails with: > [INFO] Building Archiva Web Application > [INFO]task-segment: [clean, integration-test] > ... > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > GroupId: org.apache.maven.archiva > ArtifactId: archiva-applet > Version: 0.9-alpha-2 > Reason: Unable to download the artifact from any repository > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.apache.maven.archiva > -DartifactId=archiva-applet > -Dversion=0.9-alpha-2 -Dpackaging=jar -Dfile=/path/to/file > org.apache.maven.archiva:archiva-applet:jar:0.9-alpha-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] Commented: (MRM-340) release:prepare fails due to missing archiva-applet
[
http://jira.codehaus.org/browse/MRM-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95796
]
Arnaud Heritier commented on MRM-340:
-
We could add a dependency for the plugin like :
org.apache.maven.archiva
archiva-applet
${archiva.version}
For me, with maven 2.0.6, the order seems to be good even if we don't add this
dependency in the plugin and we have the scope provided in the project
dependency.
Perhaps it's a problem in maven 2.0.5...
> release:prepare fails due to missing archiva-applet
> ---
>
> Key: MRM-340
> URL: http://jira.codehaus.org/browse/MRM-340
> Project: Archiva
> Issue Type: Bug
> Components: build
>Affects Versions: 0.9
>Reporter: Wendy Smoak
>
> During release:prepare, the build fails with:
> [INFO] Building Archiva Web Application
> [INFO]task-segment: [clean, integration-test]
> ...
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Failed to resolve artifact.
> GroupId: org.apache.maven.archiva
> ArtifactId: archiva-applet
> Version: 0.9-alpha-2
> Reason: Unable to download the artifact from any repository
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.maven.archiva
> -DartifactId=archiva-applet
> -Dversion=0.9-alpha-2 -Dpackaging=jar -Dfile=/path/to/file
> org.apache.maven.archiva:archiva-applet:jar:0.9-alpha-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] Commented: (MRM-339) Roles aren't created if the repository isn't created within the web UI
[ http://jira.codehaus.org/browse/MRM-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95797 ] Arnaud Heritier commented on MRM-339: - Same thing if I delete the database. All my repositories are created but I have no role in the users part. > Roles aren't created if the repository isn't created within the web UI > -- > > Key: MRM-339 > URL: http://jira.codehaus.org/browse/MRM-339 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-alpha-1 >Reporter: Arnaud Heritier > > If we create some repositories directly in the archiva.xml config file, we > don't have the roles to observe or manage these repositories. -- 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: (MRM-339) Roles aren't created if the repository isn't created within the web UI
[ http://jira.codehaus.org/browse/MRM-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95798 ] Arnaud Heritier commented on MRM-339: - It can be related to this problem. I add the "Global Observer" role to guest but I can't access to my repositories. > Roles aren't created if the repository isn't created within the web UI > -- > > Key: MRM-339 > URL: http://jira.codehaus.org/browse/MRM-339 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-alpha-1 >Reporter: Arnaud Heritier > > If we create some repositories directly in the archiva.xml config file, we > don't have the roles to observe or manage these repositories. -- 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-1532) Upload org.hibernate:hibernate-annotations:jar:3.3.0.ga to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95799 ] Nathan Hamblen commented on MAVENUPLOAD-1532: - This also requires hibernate-commons-annotations.jar, which hasn't been uploaded. > Upload org.hibernate:hibernate-annotations:jar:3.3.0.ga to ibiblio > -- > > Key: MAVENUPLOAD-1532 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1532 > Project: maven-upload-requests > Issue Type: Task >Reporter: Craig Condit >Assignee: Carlos Sanchez > > http://randomcoder.com/projects/maven-uploads/hibernate-annotations-3.3.0.ga-bundle.jar > http://www.hibernate.org/ > Relational Persistence for Java - Annotations support -- 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: (WAGON-82) wagon-webdav does not set http-proxy correctly
[ http://jira.codehaus.org/browse/WAGON-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95802 ] Joakim Erdfelt commented on WAGON-82: - I've considered making the protocol on wagon-webdav 'dav' (normal http) and 'davs' (secure/https) respectively. Would that ease your pain? (bakwards compatibility is a must, obviously) > wagon-webdav does not set http-proxy correctly > -- > > Key: WAGON-82 > URL: http://jira.codehaus.org/browse/WAGON-82 > Project: wagon > Issue Type: Bug > Components: wagon-webdav >Affects Versions: 1.0-beta-2 > Environment: any system >Reporter: Marc Wilhelm >Priority: Blocker > Attachments: wagon-webdav.patch > > > Webdav connections through a http-proxy are currently not possible. > The webdav provider opens first a connection to the target system and checks > after this, if a proxy should be used. > To fix this in the method > "org.apache.maven.wagon.providers.webdav.WebdavWagon#openConnection()" the > call "webdavResource = new CorrectedWebdavResource( httpURL );" must be > changed into "webdavResource = new CorrectedWebdavResource( );" and after > configuring the http-proxy the method call > "webdavResource.setHttpURL(httpURL);" must be added. -- 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-2985) DefaultWagonManager does not safely remove TransferListeners from the wagon
[ http://jira.codehaus.org/browse/MNG-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95804 ] Carlos Sanchez commented on MNG-2985: - you are missing Wagonnoop class in the patch > DefaultWagonManager does not safely remove TransferListeners from the wagon > --- > > Key: MNG-2985 > URL: http://jira.codehaus.org/browse/MNG-2985 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.1-alpha-1 > Environment: osx intel, java 5 >Reporter: Abel Muiño > Attachments: MNG-2985-maven-artifact.patch > > > The method "getRemoteFile()" registers several transfer listeners, but never > removes them. > The method "putRemoteFile()" might left transfer listeners registered if an > exception is raised. > The results is that executing those method repeteadly continously increments > the number of listeners. When embedded, the problem is specially relevant > (see http://jira.codehaus.org/browse/MNGECLIPSE-302). > Attached is a patch with test cases. -- 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: (NMAVEN-55) FxCop Maven Plugin
FxCop Maven Plugin -- Key: NMAVEN-55 URL: http://jira.codehaus.org/browse/NMAVEN-55 Project: NMaven Issue Type: New Feature Reporter: Shane Isbell Priority: Minor Maven plugin for FxCop (code analysis tool). The license for FxCop is Microsoft EULA: we can't distribute the FxCop assemblies, so this will need to be installed by the user. -- 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: (NMAVEN-3) Deploy NMaven Snapshot into Repo
[ http://jira.codehaus.org/browse/NMAVEN-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95806 ] Shane Isbell commented on NMAVEN-3: --- We've finally have support for snapshots, as well as a deploy plugin for NMaven; the capability is now available there without any manual steps. I'm going to bump this task up in priority and get the first snapshot out in June (as we are long overdue). > Deploy NMaven Snapshot into Repo > > > Key: NMAVEN-3 > URL: http://jira.codehaus.org/browse/NMAVEN-3 > Project: NMaven > Issue Type: Task >Reporter: Shane Isbell >Priority: Minor > > I have gotten numerous requests to get the NMaven snapshots up in a repo. The > Java components and plugins can use the release manager, but I will need to > manually deploy the .NET assemblies that the maven plugins use. -- 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: (CONTINUUM-1270) Release artifacts are missing license and notice files
Release artifacts are missing license and notice files -- Key: CONTINUUM-1270 URL: http://jira.codehaus.org/browse/CONTINUUM-1270 Project: Continuum Issue Type: Task Affects Versions: 1.1-alpha-1 Reporter: Wendy Smoak The Continuum build does not package license and notice files in the jars or the .tar.gz distribution. This was recently fixed in Archiva, the same configuration can be used 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] Commented: (MJAR-72) Option to include source within the jar artifact
[ http://jira.codehaus.org/browse/MJAR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95807 ] Joerg Schaible commented on MJAR-72: You can simply declare the sources as resources. > Option to include source within the jar artifact > > > Key: MJAR-72 > URL: http://jira.codehaus.org/browse/MJAR-72 > Project: Maven 2.x Jar Plugin > Issue Type: New Feature > Environment: maven 2.0.6, jdk 1.6 >Reporter: Brill Pappin > > I know it's fairly easy to create a separate source jar that contain the java > source, but I've run across a case where I want to include the source along > with the classes in the same jar. > In this case the jars are GWT modules which use the source to compile the > java code into javascript. -- 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
